SMS: Multiple Advertisements to the Same Program or Package Do Not Receive Run Status
ID: Q247230
|
The information in this article applies to:
-
Microsoft Systems Management Server versions 2.0, 2.0 SP1
SYMPTOMS
When you create multiple advertisements for the same program or package, 'run' status is only reported for the first advertisement. The remaining advertisements receive no run status at all. If the first advertisement is subsequently removed, 'orphan' status continues to be reported on it, and not for the remaining advertisements.
RESOLUTION
A supported fix that corrects this problem is now available from Microsoft, but
it has not been fully regression tested and should be applied only to systems
experiencing this specific problem. If you are not severely affected by this
specific problem, Microsoft recommends that you wait for the next Systems Management Server service pack
that contains this fix.
To resolve this problem immediately, contact Microsoft Product Support Services
to obtain the fix. For a complete list of Microsoft Product Support Services
phone numbers and information on support costs, please go to the following
address on the World Wide Web:
http://www.microsoft.com/support/supportnet/overview/overview.asp
CAUTION: Do not apply this hotfix if you have previously applied the Client Hotfix Bundle described in the following Microsoft Knowledge Base article (this hotfix is included in the bundle and reinstallation can cause client and/or site system problems):
Q246527 SMS: Systems Management Server 2.0 Service Pack 1 Client Hotfix Bundle
The English-language version of this fix should have the following file attributes or later:
Date Time Version Size File name Platform
-------------------------------------------------------------
11/23/99 11:25AM 1380.1081 367,007 Apasetup.exe i386
11/23/99 11:30AM 1380.1081 67 Compver.ini i386
11/23/99 11:23AM 1380.1081 209,264 Smsapm32.exe i386
11/23/99 11:25AM 1380.1081 629,289 Apasetup.exe Alpha
11/23/99 11:30AM 1380.1081 67 Compver.ini Alpha
11/23/99 11:23AM 1380.1081 279,824 Smsapm32.exe Alpha
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.
STATUS
Microsoft has confirmed this to be a problem in Systems Management Server version 2.0.
MORE INFORMATION
To install the hotfix, perform one of the following procedures:
Using The Hotfix Installer
i386 Platforms Only
- Copy the hotfix directory structure to a share on your network. Q247230.exe is a Microsoft Windows Installer file that updates specific files on your site server.
- Log on to your site server using an account with administrative privileges.
- On the site server, close the SMS Administrator console.
- Start Q247230.exe and follow the directions in the wizard. The file can be run in quiet mode using the /s switch.
Manual Installation
- Stop the SMS_EXECUTIVE and SMS_SITE_COMPONENT_MANAGER services on the site server.
- Copy the updated APASetup.exe file to the <Sms_root_directory>\Inboxes\Clicomp.src\Smsapm32\<Platform> folder.
- Copy the updated Compver.ini file to the <Sms_root_directory>\Inboxes\Clicomp.src\Smsapm32 folder.
- Copy the Smsapm32.exe file to the <Sms_root_directory>\Bin\<Platform> folder.
- Start the SMS_SITE_COMPONENT_MANAGER and SMS_EXECUTIVE services. When the Client Access points and Logon points have been updated, the clients may be updated.
NOTE: The default Client Configuration Installation Manager (CCIM) polling interval is 23 hours. Therefore, it may take up to
23 hours for the hotfixed files to be propagated to the clients. To speed up
this process, you can stop and restart the SMS Client Service on each client.
You can also create a software distribution for one of the Resource Kit tools
Setevnt.exe or Cliutils.exe along with the appropriate parameter(s) to start a
CCIM work cycle. For information on the proper syntax to use with these tools,
see the Resource Kit documentation.
Additional query words:
prodsms apm offer
Keywords : kbSMS200bug kbSMS200fix kbAdvertisement
Version : winnt:2.0,2.0 SP1
Platform : winnt
Issue type : kbbug