Jase_x
asked on
Windows 2003 Terminal Server - Problems Writing Profiles Back To Server
Hi folks,
I was hoping someone could help. We are experiencing problems with users logging out of our Windows 2003 Terminal Server.
Essentially logging in and loading the roaming profile causes no problem however on logout the user is presented with the following error message
"Windows cannot update your roaming profile. Possible causes of this error include network problems or insufficient security rights. If this problem persists, contact your network administrator.
DETAIL - The operation completed successfully."
Things I have tried to date:
Checking and reseting permissions on these directorys
1) TSProfiles (Root of all TSProfiles) Currently allowing Domain Admins, Domain Users, CREATOR OWNER, SYSTEM = Full Control (NTFS and sharelevel)
2) Users Profile Directory, Currently allowing Domain Admins, Domain Users, CREATOR OWNER, SYSTEM = Full Control
3) Users Profile Directory, Currently allowing Domain Admins, Domain Users, CREATOR OWNER, SYSTEM = Full Control
In the case of 2/3 the owner is the user in question.
When enabling logging an error is reported regarding writing ntuser.ini back to the terminal server however when I do this as the user or the administrator I can remove the file no problems at all.
Bit of a weird one I know, this appears to be occuring for a few users. The server in question is a recently built machine and has only really started undertaking any real use this is why the problem has only just shown up.
If you need any more info from me please let me know.
Kind regards,
I was hoping someone could help. We are experiencing problems with users logging out of our Windows 2003 Terminal Server.
Essentially logging in and loading the roaming profile causes no problem however on logout the user is presented with the following error message
"Windows cannot update your roaming profile. Possible causes of this error include network problems or insufficient security rights. If this problem persists, contact your network administrator.
DETAIL - The operation completed successfully."
Things I have tried to date:
Checking and reseting permissions on these directorys
1) TSProfiles (Root of all TSProfiles) Currently allowing Domain Admins, Domain Users, CREATOR OWNER, SYSTEM = Full Control (NTFS and sharelevel)
2) Users Profile Directory, Currently allowing Domain Admins, Domain Users, CREATOR OWNER, SYSTEM = Full Control
3) Users Profile Directory, Currently allowing Domain Admins, Domain Users, CREATOR OWNER, SYSTEM = Full Control
In the case of 2/3 the owner is the user in question.
When enabling logging an error is reported regarding writing ntuser.ini back to the terminal server however when I do this as the user or the administrator I can remove the file no problems at all.
Bit of a weird one I know, this appears to be occuring for a few users. The server in question is a recently built machine and has only really started undertaking any real use this is why the problem has only just shown up.
If you need any more info from me please let me know.
Kind regards,
ASKER
How do chap,
I hear what you are saying and indeed this was the first thing I checked,. The user is indeed the owner and has full control of the folder in question. System/Creator Owner and Domain admins also have access to this directory (full control)
UPHClean is installed also. Didn't appear to make too much difference but again I have used it to some success.
The call is also logged with Microsoft. Who to be honest don't appear to know either !
Any ideas ?
I hear what you are saying and indeed this was the first thing I checked,. The user is indeed the owner and has full control of the folder in question. System/Creator Owner and Domain admins also have access to this directory (full control)
UPHClean is installed also. Didn't appear to make too much difference but again I have used it to some success.
The call is also logged with Microsoft. Who to be honest don't appear to know either !
Any ideas ?
OK.. Are these brand new users, or existing users having the problem? If they all received cloned profiles, I'm assuming that the permissions on the registry were modified before the cloned profile was handed out to each of the users, right?
ASKER
Hi Guys,
McAfee was to blame, Version 8.5.0 was stopping remote update of system files (I.e. NTUSER.INI) I've made a new policy group which has stopped this from occuring in the future.
Is there anyway I can close this now and refund the points ?
Cheers for your input anyways.
- Jamie
McAfee was to blame, Version 8.5.0 was stopping remote update of system files (I.e. NTUSER.INI) I've made a new policy group which has stopped this from occuring in the future.
Is there anyway I can close this now and refund the points ?
Cheers for your input anyways.
- Jamie
McAfee? You use McAfee in a corporate environment? :-P LOL
ASKER
It's not my choice but yes, with the delicious E-Policy thang. This partially explains my high blood pressure ;)
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Also, if you have not done so, you should run UPHClean on all multi-user machines. Download it from: http://www.microsoft.com/downloadS/details.aspx?FamilyID=1b286e6d-8912-4e18-b570-42470e2f3582&displaylang=en
Verify the directory permissions, and install UPHclean. If the problems continues to present, we'll dig deeper.