SMSINST: Duplicate SMS IDs Exist After a Package Is Deployed
Article ID: 183398
Article Last Modified on 6/14/2005
APPLIES TO
- Microsoft Systems Management Server 1.2 Standard Edition
- Microsoft Systems Management Server 1.0 Standard Edition
This article was previously published under Q183398
SYMPTOMS
After a package is created with Systems Management Server Installer and
deployed to clients, duplicate SMS IDs appear in the database. The client
was correctly configured (with a unique SMS ID) before the package was
deployed.
CAUSE
If a repackage occurs on a reference computer, that has the Systems
Management Server client software installed and the SMS_INVENTORY_AGENT
runs during the repackage phase, Sms.ini is updated by the
SMS_INVENTORY_AGENT and the repackage process detects a change in Sms.ini
file. The Sms.ini file is then inserted into the compile script and is
subsequently distributed to the clients receiving the job.
The \Ms\Sms\Logs directory will also have updated files which are detected.
WORKAROUND
- Do not install the Systems Management Server client on the reference
computer.
- Manually remove the Sms.ini file entry from the destination computer
after the second phase of the repackage. To remove the Sms.ini file,
perform the following steps:
- In the Application Files dialog box, click the Files tab.
- Under Destination Computer, select the Application folder.
- Select Sms.ini and click the Delete File button.
MORE INFORMATION
If the package is actually deployed to clients, they will all obtain the
same SMS ID. Each client should be uninstalled (<Logon.srv>\Deinstal.bat)
and their Sms.ini files removed before reinstalling the client software.
STATUS
This behavior is by design.
Additional query words: prodsms sms uninstall uninstalled remove removed deinstall deinstalled
Keywords: kbbug kbnofix KB183398