Networker

[Networker] AW: All Windows Environment?

2011-11-29 10:43:56
Subject: [Networker] AW: All Windows Environment?
From: Sven Boseke <Sven.Boseke AT MATERNA DOT DE>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Tue, 29 Nov 2011 15:43:27 +0000
Hi

i usually find this error when the windows clients  c:\ drive (system drive) is 
nearly full





Mit freundlichen Grüssen / kind regards
Sven Boseke 
---------------------------  sender  --------------------------- 
Mr. Sven Boseke 
Dept. HQS - IT 
Materna GmbH   Information & Communications 
Hauptsitz: Voßkuhle 37, 44141 Dortmund 
Geschäftsführer: Dr. Winfried Materna, Helmut an de Meulen, Ralph Hartwig
Amtsgericht Dortmund HRB 5839 
http://www.materna.de 
-------------------------------------------------------------------- 
phone :   +49 - 231 - 5599 - 8960 
fax   :   +49 - 231 - 5599 - 8851 
email :   sven.boseke AT materna DOT de  
  



-----Ursprüngliche Nachricht-----
Von: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] Im 
Auftrag von Eddie Albert
Gesendet: Dienstag, 29. November 2011 16:36
An: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Betreff: [Networker] All Windows Environment?

Anyone else on the list in a 100% Windows environment? I would like to
discuss "Cannot save Registry key SOFTWARE: 0x000003f8" error and
solutions. What did you do to fix it long term? I do not want to simply
"temp fix" it by rebooting the host. Although that is a required step to
remove the temp registry entries.

 

This is absolutely a Windows OS issue, I have not found a permanent
hotfix, hoping someone out there has. I did read this Microsoft article:

 

http://support.microsoft.com/kb/906952/en-us

 

This problem occurs because temporary registry entries that contain
printer information are not deleted when a user logs off. These
undeleted registry entries accumulate until the default registry hive
file exceeds the registry size limit. On a terminal server, redirected
printers are installed when a user logs on. The SetPrinter function
stores detailed information about the printer in the buffer. When the
user logs off, the printer is uninstalled and the corresponding registry
values that contain printer information are deleted.

To support backward compatibility, the naming conventions for the
registry values that store printer information for the currently logged
on users are different when the SetPrinter function is set to level 2.
For example, when a user manually configures printer settings, the
registry values that are stored under the 

 

HKEY_USERS\.DEFAULT\Printers\DevModes2

registry subkey are similar to the following: 

%ClientName%\%PrinterName% (from %ClientName%) in session SessionName

The registry value that is created by using the earlier naming
convention is similar to the following: 

\\%ClientName%\%PrinterName% (from %ClientName%) in session
SessionName,localspl

 

When the SetPrinter function is set to level 2, the registry entries
that contain printer information appear to be automatically created.
Because the removal process only looks for and deletes registry values
that are manually created, these temporary registry entries are not
deleted when a user logs off.

 

Please hold comments about Win vs Unix, I didn't buy the car, I am only
the mechanic. /grin

 

Any thoughts or suggestions?  Thanks in advance for your time and
attention...

 

Semper fidelis et paratus, /ALE


To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

<Prev in Thread] Current Thread [Next in Thread>