SMS: Advertised Program Does Not Run with 10003 Status Message

ID: Q235205

The information in this article applies to:

Microsoft Systems Management Server versions 2.0, 2.0 SP1

SYMPTOMS

When you attempt to advertise a program to Systems Management Server (SMS) 2.0 clients, the program may not run and a 10003 status message may be reported for the Advertisement status. The Smsapm32.log file on clients on which the issue occurs may log the following entry:

SCHED DATA : CAPScheduleData :: SetChangableData( C1UP0416, C1UP0416 ) APM
ACCOUNT MGR : ERROR: NetUserGetLocalGroups failed for user DOM\SOFTDIST (1722) APM
ACCOUNT MGR : WARNING: Could not ascertain rights for user 'DOM\SOFTDIST' APM
SCHED DATA : Return code = 0x525; The specified user does not exist. APM

This problem occurs only when the following conditions exist:

The SMS site server is a member server in a domain.

A valid Windows NT Software Installation account has been specified in SMS Administrator Console.

A program specifies that the Windows NT Software Installation account should be used.

The program is advertised to Windows NT clients.

Account lockout is enabled in the domain.

Domain controllers in the domain have the SMS client software installed.

CAUSE

The local workstation's SMSCliToknAcct& account credentials are being used to request authentication for the specified Windows NT Software Installation account. These credentials are invalid for the domain account of the same name. If account lockout is enabled, the account is locked out. When the account is locked out, advertised programs that specify use of the Windows NT Software Installation account do not run.

Note that this account may also be locked out for other reasons. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

Q231399 SMSCliToknAcct& and/or SMSCliSvcAcct Accounts Locked Out

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

The English-language version of this fix should have the following file attributes or later:


   Date      Time    Version    Size     File name     Platform
   ------------------------------------------------------------
   09/24/99  5:36PM  1380.1043  209,776  Smsapm32.exe  i386
   10/04/99  8:19PM  1380.1053  364,880  Apasetup.exe  i386
   10/04/99  8:21PM  1380.1053  67       Compver.ini   i386

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, follow these steps on the Systems Management Server site server:

Stop the SMS_SITE_COMPONENT_MANAGER service.

Stop the SMS_EXECUTIVE service.

Copy the updated Compver.ini file to the Inboxes\Clicomp.src\Smsapm32 folder.

Copy the hotfix Apasetup.exe file to the Inboxes\Clicomp.src\Smsapm32\Platform folder.

Copy the hotfix Smsapm32.exe file to the SMS\Bin\Platform folder.

Start the SMS_SITE_COMPONENT_MANAGER service.

Start the SMS_EXECUTIVE service.

NOTE: The default Client Configuration Installation Manager (CCIM) polling interval is 23 hours. Therefore, it may take up to 23 hours for the hotfix 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 about the proper syntax to use with these tools, see the Resource Kit documentation.

Additional query words: prodsms token smsclitokacct advertisement failure

Keywords : kbSMS200 kbSMS200bug kbAdvertisement kbPackage kbSMSAdmin
Version : winnt:2.0,2.0 SP1
Platform : winnt
Issue type : kbbug