SMS: How to Disable the Restart Now/Don't Restart Now Message (186412)

MORE INFORMATION

The message displays because services are started that keep a lock on files that need to be upgraded. During the upgrade process, a temporary file is placed in the directory. You must restart your system because after you restart, the temporary file becomes the active file that the service utilizes and the temporary file disappears.

Example

If Wuser32.exe is in use during the upgrade, a temporary file, called Wuser32.exe$sms00$, is placed in the Windows NT directory. After the reboot has occurred, the file is gone.

Disabling the Window

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it.

To prevent the window from appearing on the clients, you must edit the following registry key on the site server:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\components
   \SMS_CLIENT_CONFIG_MANAGER registry key.

   Value = Prompt For Restart.
   A setting of 1 (default) will force the message to appear.
   Changing this value to 0 will eliminate the prompt for reboot.
				

CAUTION: This change will actually make a change in the client's registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Sms\Client Services\Reboot Required. There is a value for Prompt For Restart that is created based on the Site Server setting at the time that the client was installed or upgraded.

The upgrade can be run from the \\SMS Logon Server\Sms_Shr\Upgrade.bat file. For additional information about forcing site-wide updates to upgrade all clients, please see the following article in the Microsoft Knowledge Base: