Breakdown of Registry Values

Although the client-side Remote Control icon (SMSrc.cpl) is the preferred method for changing client-side Remote Control settings, it is still useful to know where the registry settings for these items are located.

The settings listed in the following table include all the switches that control which Remote Control features are available for a client computer. In nearly all cases, a value of 1 means that the feature is enabled. A value of 0 means that the feature is disabled.


Table 9.1 Remote Control Registry Settings

Registry SettingDefault ValueNotes
Allow Chat1 
Allow File Transfer1 
Allow Ping Test1 
Allow Reboot1 
Allow Remote Execute1 
Allow Takeover1 
Allow DOS Diagnostics1Not used with Window NT
Allow Windows Diagnostics1Not used with Window NT
Audible Signal10 = none,
1 = repeatedly,
2 = only at beginning and end.
CommandLine-IP-IP, -TCP, -IPX, -Lx
CompressionType0 0 = RLE, 1 = LZ, 2 = Auto
Control Level1 
Indicator Type10 = System Tray indicator (ignored on Windows NT 3.51 and Windows 3.1x clients because there is no system tray),
1 = High Security Indicator.
LanaNum0 
LogToFile1This is not set by default, but it can be added to start logging.
Permission Required1 
PermittedViewers“Administrators…”User Groups permitted to use Remote Control.
Use IDIS0Screen acceleration, 0 [OFF] by default.
Use Local Settings0 
Visible Signal1 

These settings are dynamically polled by the Windows NT Remote Control Agent, but they are not polled by the Windows 95, Windows 98, or Win16 agents. Changes made through the Remote Control icon (SMSrc.cpl) are applied immediately to the running agent. This functionality effectively makes the Windows 95, Windows 98, and Win16 agents just as “smart” as the 32-bit agent, provided that settings are changed through the Remote Control icon, not just simply placed into the registry.

This means that changes made to these registry settings (not the Remote Control icon) will take effect immediately on Windows NT, but on Windows 95 and Win16 clients they will not take effect until you stop and restart the Wuser service. (For more information, see “Stopping and Restarting Wuser and Wuser32.”)