Article ID: 886687 - View products that this article applies to.
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:
(http://support.microsoft.com/kb/256986/ )Description of the Microsoft Windows Registry
Microsoft Systems Management Server (SMS) 2003 cannot update the source list for a previously installed Windows Installer-based program. This symptom occurs even if the advertised Windows Installer-based program is run by a user with the correct permissions. Additionally, depending on your SMS configuration, error messages may be logged in the Srcupdatemgr.log file on the SMS client computer :
(http://support.microsoft.com/kb/831198/ )Software packages do not install on Systems Management Server 2003 clients
This problem occurs because the "Always Install with Elevated Privileges" Windows Installer Group Policy setting is enabled. In this case, users with limited permissions cannot access the update source list for the installed program. This causes SMS to fail when it tries to update the source list for all per-user non-managed installations by using the context of the user with limited permissions.
Important We recommend that you do not enable the "Always Install with Elevated Privileges" Group Policy setting. Any computer that has the " Always Install with Elevated Privileges" Group Policy setting enabled is a potential security risk.
Service pack informationTo resolve this problem, obtain the latest service pack for Systems Management Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/885643/ )How To obtain the latest Systems Management Server 2003 service pack
Hotfix informationA 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:
http://support.microsoft.com/contactus/?ws=supportNote 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.
PrerequisitesNo prerequisites are required.
Restart requirementYou do not have to restart your computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes. 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.
Date Time Version Size File name -------------------------------------------------------------- 14-Jun-2004 17:50 220.127.116.11 254,455 Deployac.exe 25-Dec-2003 15:35 274,944 Sms2003ac-kb886687-x86.msp 25-Dec-2003 13:30 2.50.2726.154 40,960 Smsse.dll 25-Dec-2003 15:35 2.50.2726.155 169,984 Srcupdatemgr.dll 05-Nov-2004 01:23 558 Smsconfig.inf 25-Dec-2003 13:30 2.50.2726.154 40,960 Smsse.dll
SMS 2003 Service Pack 1
Date Time Version Size File name -------------------------------------------------------------- 14-Jun-2004 17:50 18.104.22.168 254,455 Deployac.exe 20-Oct-2004 11:10 3,204 Patch.ini 20-Oct-2004 11:10 282,112 Sms2003ac-sp1-kb886687-x86.msp 25-Dec-2003 13:30 2.50.2726.154 40,960 Smsse.dll 20-Oct-2004 11:10 2.50.3174.1115 178,176 Srcupdatemgr.dll 15-Dec-2004 20:37 562 Smsconfig.inf 25-Dec-2003 13:30 2.50.2726.154 40,960 Smsse.dll
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 successfully install this hotfix, you must create new registry sub key, and then enable the "Enable user to browse for source while elevated Windows Installer Group Policy setting .To do this, follow these steps:
Microsoft has confirmed that this is a problem 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:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates