mandate profiles

[bill s via WinServerKB.com]

I created a custom profile and uploaded it to my Winser2k server Okay. In AD
I brought up the profile of the user I wanted to use the stored profile I
customized and typed the path to where it can find it. Out of 20 PC's all but
three seem to find the profile Okay......the other 3 cannot find it and after
searching for many minutes states that it cannot find profile and reverts
back to the log on screen. Can this be a permission issue somewhere???? It's
the same 3 machines that have the problem.

 

[Herb Martin]

I created a custom profile and uploaded it to my Winser2k server Okay. In
AD
I brought up the profile of the user I wanted to use the stored profile I
customized and typed the path to where it can find it. Out of 20 PC's all
but
three seem to find the profile Okay......the other 3 cannot find it and
after
searching for many minutes states that it cannot find profile and reverts
back to the log on screen. Can this be a permission issue somewhere????

Yes, and this may even be most likely since:

1) Were the machine unable to authenticate either itself
or the user it would never find (out about) the profile.

2) Some machines do find the profile so presumably you
have typed in the path (of the directory NOT the file name
itself) correctly AND you have shared the correct area on
the server.

3) Generally a profile is NOT "totally" mandatory IF it is
MERELY a missing SERVER unless you take special
steps so even that re-inforces the idea that these specific
users cannot reach the profile due to permissions which
DOES cause a failed logon.

It's
the same 3 machines that have the problem.

Same three machine OR users?

Check the permissions for the USERS on the SHARE and on
NTFS permissions of the FILES.

 

[bill s via WinServerKB.com]

Permissions seem to be Okay....both share and file.
It seems to be the same user and the same 3 machines. After looking further I
noticed that the option to "change type" in the profile section on the local
machine has the "roaming profile" greyed out and seems to be locked on "local
only".....Is this the problem and why would one of the 2 options be greyed
out???
Thanks

I created a custom profile and uploaded it to my Winser2k server Okay. In
AD

[quoted text clipped - 5 lines]

searching for many minutes states that it cannot find profile and reverts
back to the log on screen. Can this be a permission issue somewhere????

Yes, and this may even be most likely since:

1) Were the machine unable to authenticate either itself
or the user it would never find (out about) the profile.

2) Some machines do find the profile so presumably you
have typed in the path (of the directory NOT the file name
itself) correctly AND you have shared the correct area on
the server.

3) Generally a profile is NOT "totally" mandatory IF it is
MERELY a missing SERVER unless you take special
steps so even that re-inforces the idea that these specific
users cannot reach the profile due to permissions which
DOES cause a failed logon.

It's
the same 3 machines that have the problem.

Same three machine OR users?

Check the permissions for the USERS on the SHARE and on
NTFS permissions of the FILES.

 

[Herb Martin]

Permissions seem to be Okay....both share and file.

We cannot help if you say "seem to be ok" rather than
give specifics so we must assume they are in fact correct
and move one to the next...

It seems to be the same user and the same 3 machines. After looking
further I
noticed that the option to "change type" in the profile section on the
local
machine has the "roaming profile" greyed out and seems to be locked on
"local
only".....Is this the problem and why would one of the 2 options be greyed
out???

Usually because either it was a Local profile (never changed).

Since a local profile that is NOT set as a roaming profile cannot
be changed to roaming; so chances are this user is not correctly
authenticating or able to access the profile SHARE or NTFS
files due to permissions.

If the user doesn't authenticate (but uses cached credentials) they
will never discover the "roaming profile" setting you changed.

If the user cannot get to the share/server then perhaps that is the
same effect (but I don't know for sure in that case and you say
the permissions are "ok".)


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

I created a custom profile and uploaded it to my Winser2k server Okay. In
AD

[quoted text clipped - 5 lines]

searching for many minutes states that it cannot find profile and
reverts
back to the log on screen. Can this be a permission issue somewhere????

Yes, and this may even be most likely since:

1) Were the machine unable to authenticate either itself
or the user it would never find (out about) the profile.

2) Some machines do find the profile so presumably you
have typed in the path (of the directory NOT the file name
itself) correctly AND you have shared the correct area on
the server.

3) Generally a profile is NOT "totally" mandatory IF it is
MERELY a missing SERVER unless you take special
steps so even that re-inforces the idea that these specific
users cannot reach the profile due to permissions which
DOES cause a failed logon.

It's
the same 3 machines that have the problem.

Same three machine OR users?

Check the permissions for the USERS on the SHARE and on
NTFS permissions of the FILES.