Re: Windows Fax and Scan cannot run as it cannot access your documents folder

[Russ Valentine [MVP-Outlook]]

You cannot move your Documents folder to the root of any drive.

 

[Russ Valentine [MVP-Outlook]]

There is more to your story than you have revealed. The precise steps you
used to move your Documents folder would be nice to know. Just make sure you
never place it in the root of any drive. If you do, WFS will never find it.

 

[Russ Valentine [MVP-Outlook]]

Just because it isn't in the Help file doesn't mean it isn't so.

 

[Russ Valentine [MVP-Outlook]]

I already posted the solution. Microsoft has documented the issues that WFS
is facing when the documents folder is redirected to the root of a drive
(e.g. d:\). A quick workaround is to move the documents folder to a folder
under the root of the drive (e.g. to d:\DocumentFolder) with the option to
move all existing documents to the new location. This should allow WFS to
work.

 

[Russ Valentine [MVP-Outlook]]

FYI. Everyone else has been able to do this without a problem. I've seen no
repros so far on your description. Neither have the developers to my
knowledge.

 

[Russ Valentine [MVP-Outlook]]

Sounds like a permissions issue. Have you checked those settings? I suspect
the permissions changed when you logged onto the domain.

 

[Russ Valentine [MVP-Outlook]]

I've seen no one report this particular issue before so I can't say. I still
strongly suspect that WFS is still trying to access its default folder
locations for the previous fax account but is unable to under the new logged
on user token. Vista places a lot more restrictions on remembered
credentials (in fact it can't use them because of the security risk).
Perhaps you should have blown away any existing fax accounts then configured
a new one from scratch after joining the domain.
--
Russ Valentine
[MVP-Outlook]

;894945']Sounds like a permissions issue. Have you checked those
settings? I suspect
the permissions changed when you logged onto the domain.
--
Russ Valentine
[MVP-Outlook]

Immediately after joining the domain, even before I rebooted I gave her
domain account full admin rights on the machine, so she never logged
into her profile without full admin rights.

After it failed in BOTH profiles, I also gave the new domain user full
ownership of the previous local profiles documents folder....I have to
admit that it is kind of hard to figure out setting up permissions when
you don't know which folder the wfs is attempting to access???? Was it
trying to access the previous users documents that the wfs was accessing
before or was it trying to access the new domain users documents??? I
guess I'll never know since it doesn't appear that Vista shows you
anywhere in its os where the wfs is pointing.

Note that on this same system, after formatting the laptop, and joining
the same exact domain and loading the exact same software on the laptop
exactly as I did before, but not using the wfs in the original local
profile, the wfs worked perfectly in the domain profile. Is it possible
that if you use the wfs in a local profile with a local account first,
it won't work after joining a domain? Is there something else I was
supposed to do besides the giving of full admin rights on the machine???