P
Paul Hadfield
Hi all,
Sorry this is quite a long read guys, but it's a weird problem and I wanted
to be sure I included all the details for you to ponder over...
We have a Windows 2000 domain set-up which is comprised of 2 domain
controllers, 2 data servers and 17 load balanced Windows 2000 advanced
servers in Terminal Server Application Mode. Each user that logs onto the
terminal servers has a roaming terminal server profile located on a data
server.
This set-up has been configured and running for around 2 years now with no
real problems, until recently....
Periodically, when setting up new users, some of the terminal services
roaming profiles will not 'roam'. The new user's can log onto the TS servers
OK, the logon script runs fine and the user picks up the default profile as
normal. But when the user logs off, the 'Saving your personal settings'
screen remains on screen for almost a minute (normally it would take 3 - 5
seconds to write the roaming profile back to the data server, or 10 - 15
seconds for a new user that is logging out of a TS server for the first
time). Once the TS session ends, the roaming profile folder on the data
server is empty, and the locally cached profile is still present in the
documents and settings folder (all the TS servers are configured to delete
locally cached profiles at log off).
This locally cached profile will then have two files that will not delete.
They are UsrClass.dat and UsrClass.dat.LOG located in:
C:\Documents and Settings\%UserName%\Local Settings\Application
Data\Microsoft\Windows
The error message tells me that the file may be in use, though Computer
Management - Shared Folders - Open Files reports no occurrence of these
files in use on any server in the domain. Furthermore, if that user logs
back onto this terminal server, their locally cached profile is created in a
new folder named %username%.domain (presumably because of the files being in
use in the previous profile). The only way to delete the locally cached
profile is to reboot the terminal server.
This is not a permissions problem - while the user is logged on, they can
browse to the path where their roaming profile should be stored and can
create/delete files/folders quite happily. Also, creating new users that
have domain admin permissions also experience the same problem.
There is no pattern to what time of day this happens - the network can be
busy or very quiet. Neither does it seem to matter which Terminal Server
they log on to - all seem to have the same problem every now and then.
There are no entries in the event viewer on any of the TS servers that seem
to relate to this.
This is not a domain policy issue - I have created new OU's in the root of
Active Directory with no policy's and set-up test user accounts here - some
have experienced the same problem while others behave correctly.
The size of the roaming profiles are relatively small - less than a few MB
and the TS servers have a gigabit link to the data servers.
Any suggestions are much appreciated.
Paul.
Sorry this is quite a long read guys, but it's a weird problem and I wanted
to be sure I included all the details for you to ponder over...
We have a Windows 2000 domain set-up which is comprised of 2 domain
controllers, 2 data servers and 17 load balanced Windows 2000 advanced
servers in Terminal Server Application Mode. Each user that logs onto the
terminal servers has a roaming terminal server profile located on a data
server.
This set-up has been configured and running for around 2 years now with no
real problems, until recently....
Periodically, when setting up new users, some of the terminal services
roaming profiles will not 'roam'. The new user's can log onto the TS servers
OK, the logon script runs fine and the user picks up the default profile as
normal. But when the user logs off, the 'Saving your personal settings'
screen remains on screen for almost a minute (normally it would take 3 - 5
seconds to write the roaming profile back to the data server, or 10 - 15
seconds for a new user that is logging out of a TS server for the first
time). Once the TS session ends, the roaming profile folder on the data
server is empty, and the locally cached profile is still present in the
documents and settings folder (all the TS servers are configured to delete
locally cached profiles at log off).
This locally cached profile will then have two files that will not delete.
They are UsrClass.dat and UsrClass.dat.LOG located in:
C:\Documents and Settings\%UserName%\Local Settings\Application
Data\Microsoft\Windows
The error message tells me that the file may be in use, though Computer
Management - Shared Folders - Open Files reports no occurrence of these
files in use on any server in the domain. Furthermore, if that user logs
back onto this terminal server, their locally cached profile is created in a
new folder named %username%.domain (presumably because of the files being in
use in the previous profile). The only way to delete the locally cached
profile is to reboot the terminal server.
This is not a permissions problem - while the user is logged on, they can
browse to the path where their roaming profile should be stored and can
create/delete files/folders quite happily. Also, creating new users that
have domain admin permissions also experience the same problem.
There is no pattern to what time of day this happens - the network can be
busy or very quiet. Neither does it seem to matter which Terminal Server
they log on to - all seem to have the same problem every now and then.
There are no entries in the event viewer on any of the TS servers that seem
to relate to this.
This is not a domain policy issue - I have created new OU's in the root of
Active Directory with no policy's and set-up test user accounts here - some
have experienced the same problem while others behave correctly.
The size of the roaming profiles are relatively small - less than a few MB
and the TS servers have a gigabit link to the data servers.
Any suggestions are much appreciated.
Paul.