The Elevated Rights Deployment utility in the Systems Management Server 2003 Service Pack 1 Administration Feature Pack does not move registry entries

The Elevated Rights Deployment utility (Run_once.exe) does not move registry entries that are located in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVesion\RunOnce registry subkey to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\RunOnce registry subkey. Also, the Elevated Rights Deployment utility does not move any registry entries that are located in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVesion\RunOnceEx registry subkey to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\RunOnceEx registry subkey.
Note The Elevated Rights Deployment utility is included in the Microsoft Systems Management Server (SMS) 2003 Service Pack 1 (SP1) Administration Feature Pack.

These symptoms occur if the called program returns an exit code that is not zero (0). For example, these symptoms occur if you use the following command by using the Elevated Rights Deployment utility:Note You run the previous command in the Command box on the Command Line page in the Elevated Rights Deployment utility. When you run the previous command, the Dasetup.exe program returns an exit code of 3010 (Restart is required).

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have SMS 2003 Service Pack 1 (SP1) installed before you apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Installation instructions

To install this hotfix, follow these steps:

1. Create a shared folder in a location that can be accessed by the SMS site servers.
2. Copy the Adminpack2003-kb893174-x86-enu.exe hotfix file to the shared folder that you created in step 1.
3. On each SMS primary server in your environment, log on by using an account that has administrative credentials.
4. Quit the SMS Administrator Console.
5. On each primary server, connect to the shared folder that contains the hotfix, double-click the Adminpack2003-kb893174-x86-enu.exe hotfix file, and then follow the instructions on the screen.

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

For more information about the standard terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base: