I had a thread started a few weeks back but can not seem to find it. Anyway, The problem we have been experiencing is after installing MS03-026 on our Citrix servers we have had repeat problems with profiles not unloading. The issue has been taken to Microsoft weeks ago and they have many cases open. It seems that if you disable the windows installer service this goes away. Anonymous users are effected the most and often we will see anon users with the format anon000.servername. Microsoft is able to reproduce the problem and they are working on a fix.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Profile unload issue after installing MS03-026 3
- Thread starter DDILL
- Start date
HI DDIL,
Tried disabling windows installer and that didn't fix the problem for us.
We do have a work around though for when this happens:
1. I used getsid to find the SID of the offending user.
(getsid \\servername anonxxx )
2. net stop spooler (stop the print spooler)
3. In regedt32 opened HKUsers and unload that orpaned classes key of the users sid.
you should find that users can now use that anonxxx profile that was causeing errors now it will be called anonxxx.servername but it will work. later you can reboot the server and delete the stuck profile.
We can also repicate the problem.
1 logon to the server and pause your print queue on the citrix server.
2. fill the print queue with some big jobs >1mb
3. now unpause your print queue and log off the server while the jobs are copying down to your local machine. Disconnect the network cable if you have to.
now you should have a nice broken profile to test with.
Hope this helps.
Microsoft are currently getting us to try different versions of termsrv.exe I'll let you know if any actually work.
Tried disabling windows installer and that didn't fix the problem for us.
We do have a work around though for when this happens:
1. I used getsid to find the SID of the offending user.
(getsid \\servername anonxxx )
2. net stop spooler (stop the print spooler)
3. In regedt32 opened HKUsers and unload that orpaned classes key of the users sid.
you should find that users can now use that anonxxx profile that was causeing errors now it will be called anonxxx.servername but it will work. later you can reboot the server and delete the stuck profile.
We can also repicate the problem.
1 logon to the server and pause your print queue on the citrix server.
2. fill the print queue with some big jobs >1mb
3. now unpause your print queue and log off the server while the jobs are copying down to your local machine. Disconnect the network cable if you have to.
now you should have a nice broken profile to test with.
Hope this helps.
Microsoft are currently getting us to try different versions of termsrv.exe I'll let you know if any actually work.
-
3
- Thread starter
- #3
Interesting.... I did notice that sometimes there was alot of handles open from termsrv.exe. Also, the windows installer does not make since as to why a specific driver could produce the problem for us. I had fixed the "specific driver" problem by using the native windows driver. It will be interesting to find out what this is from.
- Thread starter
- #4
stalinx,
When you disabled windows installer did you reboot after and remove all profile directories before allowing people to log in? I received a hot fix from MS for this and am trying it out. I have not had one problem since I disabled windows installer but you have to clean the profiles after or you will still have issues. I know, I did not clean up one of my servers and had the problem with windows installer disabled.
When you disabled windows installer did you reboot after and remove all profile directories before allowing people to log in? I received a hot fix from MS for this and am trying it out. I have not had one problem since I disabled windows installer but you have to clean the profiles after or you will still have issues. I know, I did not clean up one of my servers and had the problem with windows installer disabled.
Sorry been on holiday.
Yeh we are still working through the problem with MS =(
they have given us a ton of hotfixes to try, none of which have really worked.
We are also running the UPH Clean utility now thanks to MS, it clears the stuck profiles but still alerts in the event log each time, and it's not 100% succesful it's cut our problem by about 95%. But the occasional one slips through.
We tried upgrading some of our servers to SP4 and that didn't help either. We are currently running some bebug software for MS in an attempt to get something out of them.
I'm pretty sure I cleared all the profiles before disabling the windows installer but I'm not 100% so I'll give it a try again today and post the result.
Yeh we are still working through the problem with MS =(
they have given us a ton of hotfixes to try, none of which have really worked.
We are also running the UPH Clean utility now thanks to MS, it clears the stuck profiles but still alerts in the event log each time, and it's not 100% succesful it's cut our problem by about 95%. But the occasional one slips through.
We tried upgrading some of our servers to SP4 and that didn't help either. We are currently running some bebug software for MS in an attempt to get something out of them.
I'm pretty sure I cleared all the profiles before disabling the windows installer but I'm not 100% so I'll give it a try again today and post the result.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question