I had a user who used a laptop at home using a local profile for about a
week and she used the fax and scan feature at home with absolutely no
issues.....I joined her Windows Vista Ultimate machine to our domain,
and walla, I got the same message whenever you clicked on the wfs menu
item off of the start menu:

"Windows Fax and Scan cannot run as it cannot access your documents
folder. Please ensure that Windows Fax and Scan can access that
folder."

No documents were moved to the root or anywhere else. She simply tried
to access this feature from her new domain profile with no success.
Note I also had her attempt to login with her old local profile and the
wfs did the same exact thing, giving the same error message. Also note
that ALL users that tried to access this had full admin rights on the
machine, and I also attempted to run the wfs with THE administrator
account. Again the only thing that was done was the machine was added
to the domain and nothing else.

The above error message is completely useless as it just points to the
executable that runs the wfs....there doesn't appear to be a location to
change where the documents folder its looking for is located. Because
of this issue I had to actually format the system and start from
scratch.

Did I miss something that I could've done??


--
Jasonw
Posted via http://www.vistaheads.com

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]
"Jasonw" wrote in message
...

I had a user who used a laptop at home using a local profile for about a
week and she used the fax and scan feature at home with absolutely no
issues.....I joined her Windows Vista Ultimate machine to our domain,
and walla, I got the same message whenever you clicked on the wfs menu
item off of the start menu:

"Windows Fax and Scan cannot run as it cannot access your documents
folder. Please ensure that Windows Fax and Scan can access that
folder."

No documents were moved to the root or anywhere else. She simply tried
to access this feature from her new domain profile with no success.
Note I also had her attempt to login with her old local profile and the
wfs did the same exact thing, giving the same error message. Also note
that ALL users that tried to access this had full admin rights on the
machine, and I also attempted to run the wfs with THE administrator
account. Again the only thing that was done was the machine was added
to the domain and nothing else.

The above error message is completely useless as it just points to the
executable that runs the wfs....there doesn't appear to be a location to
change where the documents folder its looking for is located. Because
of this issue I had to actually format the system and start from
scratch.

Did I miss something that I could've done??


--
Jasonw
Posted via http://www.vistaheads.com

'Russ Valentine [MVP-Outlook Wrote:
;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???


--
Jasonw
Posted via http://www.vistaheads.com

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]
"Jasonw" wrote in message
...

'Russ Valentine [MVP-Outlook Wrote:
;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???


--
Jasonw
Posted via http://www.vistaheads.com

I suspect your right, as thats exactly what I was thinking. In my job, I
deal with employees all the time who bring their personal computers to
work and I join them to the domain. I've had nothing but problems with
these vista systems. With XP you could simply copy over an entire
profile and overwrite the new profile and it worked beautifully...with
Vista it has been nothing but a nightmare.

With this case with the WFS, I didn't do any of the moving of profiles,
because that has broken machines before....I just logged in with the
domain profile after giving the user admin rights and moved over a few
docs/pics from backup....but nothing OS wise was changed or moved.

I'm thinking that this was probably my first user that used the WFS in
a local profile that I joined to a domain, that then tried to use it
again in the domain profile...so it is very possible that this could
happen again. I'd be interested how often this would happen in a test
environment.

And unfortunately the error message that Vista gives you is completely
useless, and gives you absolutely NO hint at how to resolve the issue.
When you say blow away fax accounts, and create a new one from scratch,
I have no idea how to do that.....I guess I could do a google search and
see what I come up with. I sure hope that works if this problem happens
again, as a 3 hour job of formatting and reconfiguring the computer is
very time consuming and seems like overkill.

The security in Vista seems over the top, but maybe thats just me.

'Russ Valentine [MVP-Outlook Wrote:
;895739']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]
"Jasonw" wrote in message
...

'Russ Valentine [MVP-Outlook Wrote:
;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???


--
Jasonw
Posted via http://www.vistaheads.com



--
Jasonw
Posted via http://www.vistaheads.com