Oops! One more thing: When we set the path for the profile (and this works whether we let the user create the roaming profile by having the path set first or we create the folder ourselves before the user logs on) we normally call it something like "user.pro", rather than just "user."
When the roaming profile is created, it also creates a separate folder just called "user" and the My Documents folder is in that location, rather than in "user.pro." I don't understand this behavior either, but this is the location in which the My Documents folder has no permissions. The "user" folder does have correct permissions, but My Documents does not. I don't know if this sheds any light at all... Thanks, Matt Hoffman -----Original Message----- From: Matt Hoffman [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 20, 2003 5:39 PM To: NT 2000 Discussions Subject: Having trouble with 2003 Server TS Roaming Profiles Hello, We've been having trouble with our roaming terminal server profiles for our users. The server is 2003 Server with all hotfixes up to date. Users log on to the server via TSWEB, and get a desktop environment with access to Office XP applications, including Outlook. We can create new roaming user profiles by setting the profile path in AD Users & Computers, make the settings changes we need, including setting up Outlook to look for the user account via Exchange server. Then log the user off and the profile is created, ready to be used again. However, we get a strange problem when the user must change their password at next logon; the system logs the user back on with the Default User profile once the user changes their password. The user no longer can use their roaming profile. All settings changes, files, folders, shortcuts, etc. are long gone. They remain in the roaming profile itself, but are not available to the user. The behavior is consistent whether the user is an administrator or locked down. One thing that I've seen is that the My Documents folder is not available to anyone. No permissions have been created at all (at least that we can see). Perhaps the fact that this folder is "permissionsless" is the problem. I've seen a number of knowledgebase articles that have some similar problems listed but none that seems to handle this particular problem. Does anyone have any suggestions for things that we can try? Thanks! Matt Hoffman ------ You are subscribed as [EMAIL PROTECTED] Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=nt2000&text_mode=&lang=e nglish To unsubscribe send a blank email to %%email.unsub%% ------ You are subscribed as [EMAIL PROTECTED] Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=nt2000&text_mode=&lang=english To unsubscribe send a blank email to [EMAIL PROTECTED]
