Remote Desktop Loading\Unloading and Printer Sessions issue

By ZadeyTech ·
OS: windows 2003 Server 2003 SP1
Program: Remote Desktop \ Printers

Users that are utilizing RDP Client (the latest) to log on to the server are experiencing extended profile loading\unloading.
I installed UPHClean.exe and it logs the issue to the Event Viewer. These are some of the errors:

EventID 1501 Source: Userenv

The following handles opened in user profile hive servername\username (S-1-5-21-601176114-22604**871-370163669-1032) are preventing the profile from unloading:

winlogon.exe (5752)
HKCU\Printers\DevModePerUser (0x364)

EventID 1517 Source: Userenv

Windows saved user Iservername\username registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.

This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

EventID 1401 Source: UPHClean

The following handles in user profile hive IPDMEZ0301MIA\dsunno (S-1-5-21-601176114-22604**871-370163669-1032) have been remapped because they were preventing the profile from unloading successfully:

winlogon.exe (3476)
HKCU\Printers\DevModePerUser (0x364)

When this happens a few things result:

1. The user will call me telling me how they had trouble logging on or off the server
2. They couldn't see their printer or had trouble printing so they tried logging off to get back on but it was delayed as above
3. The spooler jumps up to 50% of the CPU
4. If they DO make it back onto the server, the printers from the previous session is still in the printers\faxes folder
5. this happens if people time out on the server and then log back in as well.

Does anyone have any suggestions on what I can do to make sure that the profiles are unloading and taking the printer with it? Even if they time out? I know that's what UPHClean.exe is supposed to do, and it's helping - but the issue is still there.

Thank you for all your help!! =)

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Share your knowledge

Related Discussions

Related Forums