SMS: How to Enable Remote Control Logging for WUSER in SMS 2.0

This article was previously published under Q195859
This article has been archived. It is offered "as is" and will no longer be updated.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
In addition to the mainstream logging of the Install.log and Remctrl.logfiles, a very low level of client-side remote tools logging is available tolog all transactions during remote transactions. This level of logging isdisabled by default, and can only be enabled by creating a registry value.Although very detailed information is captured by this WUSER logging, nopasswords or encrypted information is passed. The results of this file areonly for use by Microsoft Product Support Services in troubleshooting transaction or connection-level problems.
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To confirm that the client has received and installed the Remote Controlcomponents, check for the existence of an Install.log file in the %windir%\MS\SMS\Clicomp\RemCtrl directory.

This installation log file indicates all of the steps taken during theinstallation (or removal) of the Remote Control components, includingregistry key creation and security. Because the installation log file iscreated at the completion of Remote Control installation, the existence ofthis Install.log file indicates that the client side installation wassuccessful.

Additionally, the standard Remote Control log file is stored at thefollowing location:
This "live" Remote Control log file is a more detailed file that logs nearly every action the client side Remote Control system carries out. Among the many detailed items it records are:
  • Operating system and local client languages.
  • Actions taken by the Hardware Munger.
  • Actions taken by the periodic Security Munger.
  • Active sites participating in site setting reconciliation.
  • Installation and De-installation triggers.
This log file is essential in tracking down any sort of Remote Control,installation, or removal problem.

As for installation, the existence of both the Install.log file and thecompletion message at the bottom of the Remctrl.log file indicates thesuccess of the Remote Control installation.

WUSER logging features can be enabled by setting the following registry keyor .ini file. In each case, logging can be disabled by either removing theentry or setting it to FALSE (0). Take care when using this feature,because logging will continue indefinitely, and the client-side agent willbe slowed while this special type of low-level logging is active.

For 32-bit clients (WUSER32), set (or create) a registry setting in thefollowing key:
   HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Client\Client Components\Remote Control				
Name this value LogToFile (be sure to match the capitalization exactly; thecase is important!) as a REG_DWORD set to 1. Changes to the Windows NTWUSER32 agent are dynamic, so within a moment of setting the registrysetting, a Wuser32.log file should start being created. This Wuser32.log file will be located in the %WinNT%\MS\SMS\Clicomp\Remctrl directory.

For 32-bit (WUSER32) client computers running Windows 95 or Windows 98, set(or create) a registry setting in the following key:
   HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Client\Client Components\Remote Control				
Name this value LogToFile (be sure to match the capitalization exactly; thecase is important!) as a REG_DWORD set to 1. This is not dynamic, so youmust shut down and restart the Windows 95 or Windows 98 WUSER32 agent. Whenthe computer restarts, look for a resulting log file called Wuser32.log. This Wuser32.log file will be located in the %WinNT%\MS\SMS\Clicomp\Remctrl directory.

For Windows 3.1 or Windows for Workgroups 3.11 16-bit clients (WUSER), addan entry to the [Client Components - Remote Control] section of theSmsrc16.ini file that reads "LogToFile=1". You must shut down and restartthe agent before WUSER logging will begin. After the computer restarts,look for a log file called Wuser.log.

Because of the way Win16 Client Services handles .ini files, this settingwill be overwritten each time initial or full-maintenance cycle of ClientServices runs. To prevent this, either disable logon scripts or make sureno Manual Discovery (SMSMAN16) is performed on this workstation during thetime logging is in effect. Note that this is true only for Win16.

Enabling WUSER logging will result in either a Wuser32.log (on computersrunning Windows NT, Windows 95, or Windows 98) or Wuser.log (on computersrunning Windows 3.1x) being created somewhere in the local (client) filesystem. This log file will be overwritten (started anew) with each restartof the WUSER agent, so be sure to preserve any WUSER log files beforeshutting down (or stopping) and restarting the client agent.
prodsms turn turned on off win win95 win98 win9x 95 98 9x

Article ID: 195859 - Last Review: 10/11/2013 15:42:30 - Revision: 3.1

  • Microsoft Systems Management Server 2.0 Standard Edition
  • kbnosurvey kbarchive kbinfo kbremoteprog KB195859