Client components change to "Install Pending" status after you restart the Systems Management Server Client service

This article has been archived. It is offered "as is" and will no longer be updated.
When you install Microsoft Systems Management Server (SMS) 2003 client agents on a Microsoft Windows 2000, Windows XP, or Windows Server 2003-based client computer, the status for some of the agents may change to Install Pending after you restart the SMS Client service or after the Client Component Installation Manager (CCIM) cycle is complete. Additionally, the following information may appear in the Windows\MS\SMS\Logs\Clisvc.log file:
"C:\WINNT\MS\SMS\clicomp\SWDist32\bin\ODPUSR32.exe " - Error : 1314*** WNet User Groups Offer Data Provider - Error launching (#0x3EB)!!!WARNING: Problem starting App (1003). Doing App Verify.
You experience this behavior with the following client agents:
  • The Software Inventory Client Agent
  • The Advertised Programs Client Agent
This issue occurs if both the following conditions are true:
  • The client computer is running the Legacy Client.
  • A domain security policy restricts a required permission of the local SMSCliSvcAcct& account on the client computer.
For example, you experience this behavior if the local SMSCliSvcAcct& account does not have the Replace process level token user rights assignment. The SMSCliSvcAcct& account requires the following user rights assignments:
  • Act as part of the operating system
  • Increase quotas
  • Log on as a service
  • Replace a process level token
  • Shut down the system
To resolve this issue, upgrade the SMS client computers to the SMS 2003 Advanced Client. The issue described in this article does not occur with the Advanced Client because the Advanced Client uses a different security model than the Legacy Client. The Advanced Client runs in the context of the Local System account. Therefore, it does not require additional user accounts or permissions.
To work around this issue, add the correct security rights to the domain security policy for the SMSCliSvcAcct& account. To do so, follow these steps:
  1. Log on to a domain controller.
  2. Click Start, point to Programs, point to Administrative Tools, and then click Domain Security Policy.
  3. Expand Security Settings, expand Local Policies, and then click User Rights Assignment.
  4. In the right pane, double-click a policy. For example, double-click Act as part of the operating system.
  5. If the policy setting is defined, add the SMSCliSvcAcct& account.
  6. When you are finished adding the SMSCliSvcAcct& account to the policy settings that are defined, exit the Domain Security Policy tool.
  7. Let sufficient time pass for the policy changes to replicate throughout the domain.
Additionally, the SMSCliSvcAcct& account must be a member of the local Administrators group on the SMS client computer.
More information
Error code 1314 that appears in the Clisvc.log corresponds to the following error message:
A required privilege is not held by the client.
For additional information about a related issue in SMS 2.0, click the following article number to view the article in the Microsoft Knowledge Base:
295771 SMS: A "Restricted Group" Policy May Prevent SMS Clients from Being Installed
SMS 2003

Article ID: 828371 - Last Review: 01/17/2015 16:08:29 - Revision: 2.0

Microsoft Systems Management Server 2003

  • kbnosurvey kbarchive kbprb KB828371