A
Andy F
Hi
I am having the problem described in the KB article
319909, however I am experiencing it with terminal
services clients on a windows 2000 server with service
pack 4 and Citrix Metaframe XP installed. A couple of
scenarios are as follows;
1. A new user logs on to the server via a thin client and
receives his new default profile. When he logs off he
suffers the symptoms described in the article, his profile
is not written back to his profile location. Any attempt
to manually delete the profile from the server shows that
the usrclass.dat is in use. However, if he then logs back
in and out again the profile is written away and the
logoff process runs as per normal.
2. In the meantime, if the user then logs on and off a
standard W2K PC (which happens frequently in my school
environment), when he uses the terminal services again he
suffers the same error, only this time logging off and on
does not cure the fault and his profile remains on the
server indefinitely, along with his loaded registry key.
The only work around that I haven't tried is using the
terminal services tab on the user account to direct the
terminal services profiles to a different location. This
would not be ideal and still doesn't get passed the
problem with the initial logon. Any ideas?
Thanks
Andy
I am having the problem described in the KB article
319909, however I am experiencing it with terminal
services clients on a windows 2000 server with service
pack 4 and Citrix Metaframe XP installed. A couple of
scenarios are as follows;
1. A new user logs on to the server via a thin client and
receives his new default profile. When he logs off he
suffers the symptoms described in the article, his profile
is not written back to his profile location. Any attempt
to manually delete the profile from the server shows that
the usrclass.dat is in use. However, if he then logs back
in and out again the profile is written away and the
logoff process runs as per normal.
2. In the meantime, if the user then logs on and off a
standard W2K PC (which happens frequently in my school
environment), when he uses the terminal services again he
suffers the same error, only this time logging off and on
does not cure the fault and his profile remains on the
server indefinitely, along with his loaded registry key.
The only work around that I haven't tried is using the
terminal services tab on the user account to direct the
terminal services profiles to a different location. This
would not be ideal and still doesn't get passed the
problem with the initial logon. Any ideas?
Thanks
Andy