Pages:1
win2000 ids a profile problems(Click here to view the original thread with full colors/images)
Posted by: Threetall
creating new ids and testing them out. at login I get quote:
Windows cannot create profile directory \\student\profiles\bacchusl.pds. You will be logged on with a local profile only. Changes to the profile will not be propagated to the server. Contact your network administrator.
then it pops upquote:
Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off.
win2000 server fully patched (domain controller maintains normal profile)
win2000 terminal server running Citrix Meta (also backup domain controller)
win2000 NAS (has user home directories and terminal services profiles)
The PDC controls which profile to use depending on which type of machine the user logs in at (thin client or normal). Thic clients log in without problem. But a new user gets the above error when logging in a normal client.
We use roaming profiles.
any ideas? support.microsft.com just offers "...this is a known problem" types of answers without solutions
Posted by: Ritsui
Being that the reported problem is Windows being unable to create the user's profile directory, the first thing to check would be permissions. Does the user creating profiles have sufficient permissions to do everything required to create the profile (in that exact location)?
What are all the differences between the profile options for each type of client?
Posted by: Seker
We also have a windows 2000 server environment and have seen this error a couple of times.
Usually, the folder it tries using has a .pds ending to it like you have in yours. The original (and correct) profile is most likely in the same \\students\profiles\ share, but without the .pds ending. Make sure that's there (and has the correct permissions for that student) and rename the .pds one to some backup folder. Then reboot the laptop or desktop that is trying to access the drive (make sure it has a reliable network connection) and try logging in the student again.
That usually solves the problem for us.
-mike
|
|
