This page contains Troubleshooting articles for the ConfigMgr 2012 Client.

  • CCMeval failing on Windows 8/ Windows Server 2012 Clients and resetting the WMI repository
  • Problem:

    I have noticed that CCMeval is failing on my Windows 8/ Windows Server 2012 clients and the WMI repository is being reset all the time. [More...]

    Close

  • Client not using the Management Point specified during CCMSetup /mp:
  • Problem:

    I’ve installed some clients and specified the “/mp:<management_point_name>” command-line switch during CCMSetup. However, post installation my client is not using the Management Point specified. [More...]

    Close

  • ‘ERROR: Failed to publish sms client to WSUS, error = 0x80131622′ when deploying the ConfigMgr 2012 Client as a Software Update
  • Problem:

    I am trying to deploy the ConfigMgr 2012 client by doing a software update deployment. However, the client is not being published to the software update point and if I look in the “WCM.log” I see the following:

    ERROR: Failed to publish sms client to WSUS, error = 0x80131622 [More...]

    Close

  • ‘This operating system does not contain the correct version of BITS. BITS 2.5 or later is required’ error when installing the ConfigMgr 2012 Client
  • Problem:

    I’m trying to install the ConfigMgr 2012 Client but the installation fails. If I look in the CCMSetup.log I see the following lines:

    This operating system does not contain the correct version of BITS. BITS 2.5 or later is required.
    Sending Fallback Status Point message, STATEID='321'.
    State message with TopicType 800 and TopicId {0D94311F-CB7B-4E73-94B1-75878081111C} has been sent to the FSPCcmSetup failed with error code 0x80004005
    [More...]

    Close