Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

While running multiple Windows Server 2008 R2 RDSH farms we are experiencing an issue where the RDSH servers all are having their Registry bloated to the maximum value 2048MB. Using Sysinternals Registry Usage (ru.exe) we were able to determine over 1000MB of the registry being used up by Samsung Universal Printer related keys.

  • Samsung Universal Print Driver: Version 2.3.90
  • Samsung Universal Print Driver 2: Version 2.50.2.0

Registry Sections where the bloat is occurring: HKEY_USERS.DEFAULT\Software\SSPrint\ spe_\ spd_\ ssp6m\ HKEY_USERS\S-1-5-8\Software\SSPrint\ spe_\ spd_\ ssp6m\

Each of those subkeys has over 500+ keys where Registry Usage is reporting they are taking up 30-40MB each.

Example subkey: HKU.default\software\ssprint\spe__{BCC489E0-E2CA-442B-A5A5-9B849579BE1F}

Looking into the data of the keys "Capabilities", "MUIData", etc. You can definitely tell they are Samsung Universal as the values reference Samsung Universal when you view them.

Taking one of the servers out of the mix I tried cleaning up these keys and was able to. Cleaning the ".Default" section also cleaned the "S-1-5-18" keys, so I'm thinking these are a reference link within the Registry. When I did it I cleared the HKU.default\Printers\DevModes2 as well since this section would not even open in Regedit. In order to remove I had to CLI the to remove the "DevModes2" key and then recreate the key in Regedit.

As soon as I login with an account that has a printer deployed to them with the Samsung Universal Print Driver these keys start appearing and bloat out the registry. Because the registry is so filled up we have been experiencing User Profile issues causing Temporary Profiles to load. When we disabled the ability to have a Temporary Profile the users then may run into a "The User Profile Service service failed the logon. User Profile cannot be loaded." message.

Has anybody out there experienced this issue?

Is there some setting in the Samsung Universal Print Driver to prevent this behavior or to have it clean up after itself?

share|improve this question
    
I feel your pain. HP Universal Drivers weren't much better some years ago, where the spooler would crash with thousands of HP processes running. I'll be watching this question for sure. –  pauska Oct 4 '13 at 19:49
    
Samsung support created a case today when I called in. Hopefully, they will have an answer soon. –  Arachnid Oct 4 '13 at 20:59
    
After some research found the DevModes2 key issue was related to support.microsoft.com/kb/2871131 and we did have the hotfix installed. However, the hotfix doesn't clean up the mess it apparently just keeps it from growing. When it comes to the Samsung SSPrint they are back growing after cleaning up. In order to get the registry down below the 2048MB we had to perform some registry hive cleanup (support.microsoft.com/kb/2498915). Now we're just monitoring and preparing to put servers in drain mode until we have a solution with the Samsung drivers. –  Arachnid Oct 8 '13 at 12:42
    
@Archanid Interesting! How are you monitoring the situation? –  pauska Oct 8 '13 at 14:34
    
Pauska, we have a repeating powershell script setup monitoring the number of users and the logon state (Allow new Logons; Allow reconnections...) that we added the PowerShell commands to lookup the Registry Size and add that to our status tables. Get-WmiObject -Class Win32_Registry -ComputerName {COMPUTERNAME} Now we can have our monitoring page show the number of users, logons status & registry size. –  Arachnid Oct 8 '13 at 17:13
show 5 more comments

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.