Disabling Security Munging on a Client

You can use a little-known Remote Tools feature to exclude individual servers or clients from participating in site-wide security reconciliation (munging). In general, security munging is the favored approach for ensuring that all site-wide settings are forced to client computers, and that user changes to the registry are overwritten by the correct site settings.

But if site-wide settings are set to require user permission for each remote function, then server and client computers, where a user is not present to respond to permission prompts, will have a problem. To prevent the site-wide settings from being forced down to these computers, you can create a registry setting that removes them from participation in the munging of site-wide settings. Instead, these clients will rely solely on the user-specified settings set through the Remote Control program in Control Panel and ignore the site-wide settings.

To enable this feature, create a value named UpdateEnabled in the client’s registry under \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS \Client\Client Components\Remote Control, and set the value to NO (note that the NO value is not case-sensitive). On a Win16 client, create an entry in the [Client Components — Remote Control] section in the SMSrc16.ini file called UpdateEnabled=NO. With this setting enabled, the Security Munger on that client will no longer force site-wide settings to be used on the client. The fact that security munging has been disabled will be logged to the Remctrl.log file on the client computer.