Recently, our SCCM administrator saw fit to remove the Configuration Manager client from my machine. He has been unable to get the client re-installed, and now he wants me to rebuild my system. I am of the opinion that this issue should be solvable with much less hassle, so I have decided to try resolving the issue myself. Here is what I have found:

Looking up my system in Configuration Manager and opening the Client Check Detail tab, I see "Verify/Remediate client prerequisites."  It also shows a result of "Remediation Failed" with an error code of 0x0320012d.

I then copied the client installation files to my machine and attempted to install the client from the local drive.  Here is what the ccmsetup log showed (In the interest of brevity I am posting only the part of the log that I think might be relevant):

<![LOG[Failed to get assigned site from AD. Error 0x80004005]LOG]!><time="19:11:54.764+360" date="08-18-2015" component="ccmsetup" context="" type="2" thread="5480" file="ccmsetup.cpp:264">

<![LOG[GetADInstallParams failed with 0x80004005]LOG]!><time="19:11:54.764+360" date="08-18-2015" component="ccmsetup" context="" type="3" thread="5480" file="ccmsetup.cpp:304">

<![LOG[Couldn't find an MP source through AD. Error 0x80004005]LOG]!><time="19:11:54.764+360" date="08-18-2015" component="ccmsetup" context="" type="1" thread="5480" file="ccmsetup.cpp:4756">

<![LOG[No valid source or MP locations could be identified to download content from. Ccmsetup.exe cannot continue.]LOG]!><time="19:11:54.764+360" date="08-18-2015" component="ccmsetup" context="" type="3" thread="5480" file="ccmsetup.cpp:4806">

<![LOG[Failed to parse '"C:\Windows\ccmsetup\ccmsetup.exe" ' with error 0x80004005]LOG]!><time="19:11:54.764+360" date="08-18-2015" component="ccmsetup" context="" type="3" thread="5480" file="ccmsetup.cpp:4611">

<![LOG[A Fallback Status Point has not been specified.  Message with STATEID='100' will not be sent.]LOG]!><time="19:11:54.764+360" date="08-18-2015" component="ccmsetup" context="" type="1" thread="5480" file="ccmsetup.cpp:9767">

<![LOG[A Fallback Status Point has not been specified.  Message with STATEID='307' will not be sent.]LOG]!><time="19:11:54.764+360" date="08-18-2015" component="ccmsetup" context="" type="1" thread="5480" file="ccmsetup.cpp:9767">

<![LOG[CcmSetup failed with error code 0x80004005]LOG]!><time="19:11:54.764+360" date="08-18-2015" component="ccmsetup" context="" type="1" thread="5480" file="ccmsetup.cpp:10883">

I did a search on some of the errors shown, and I found the article, which shows exactly the same errors in the same order.

http://www.networksteve.com/enterprise/topic.php/SCCM_2012_Error_:Failed_to_get_assigned_site_from_AD._Error_0x80/?TopicId=94436&Posts=4

The article suggests some solutions, but I have been unable to try all of them.  For example, one solution requires knowing the site code, and I have been unable to determine our site code.

A subsequent attempt to install the client resulted in these entries in the log file:

<![LOG[CreateInstance of CLSID_BackgroundCopyManager failed with 8007042C. Unable to check BITS version]LOG]!><time="00:47:22.651+360" date="08-23-2015" component="ccmsetup" context="" type="3" thread="1640" file="util.cpp:1374">

<![LOG[This operating system does not contain the correct version of BITS. BITS 2.5 or later is required.]LOG]!><time="00:47:22.651+360" date="08-23-2015" component="ccmsetup" context="" type="3" thread="1640" file="ccmsetup.cpp:1957">

<![LOG[A Fallback Status Point has not been specified.  Message with STATEID='321' will not be sent.]LOG]!><time="00:47:22.651+360" date="08-23-2015" component="ccmsetup" context="" type="1" thread="1640" file="ccmsetup.cpp:9767">

<![LOG[Deleted file C:\Windows\ccmsetup\ccmsetup.exe.download]LOG]!><time="00:47:22.651+360" date="08-23-2015" component="ccmsetup" context="" type="1" thread="1640" file="ccmsetup.cpp:9497">

<![LOG[CcmSetup failed with error code 0x8007042c]LOG]!><time="00:47:22.651+360" date="08-23-2015" component="ccmsetup" context="" type="1" thread="1640" file="ccmsetup.cpp:10883">

I know that BITS is a prerequisite, so I did some research on how to determine my version of BITS and found this article:

https://msdn.microsoft.com/en-us/library/aa362837(v=vs.85).aspx

Using the instructions in the article I have determined that I have BITS 4.0.  So I think that the BITS version issue is related more to the fact that BackgroundCopyManager was unable to check the version.

I also ran the WMIDiag utility from Microsoft, and it does find a lot of errors in WMI that it says could prevent WMI from working correctly, so maybe that is the problem.  That log file is a mile long, but I can post it, or parts of it, if needed.

I think that I've gone about as far as I can on my own.  I am looking for guidance on how to fix this issue.  What would you suggest?

--Tom

• Edited by thomasm516 22 hours 19 minutes ago

Your client is unable to connect to a ConfigMgr Management Point to get details to download the client files. Your ConfigMgr admin has gone over the top slightly by asking you to issue rebuild on your device for sure. 

You may however need to go back to the admin and ask for the ConfigMgr install switches that they use to install the product as they may be specifying a MP to talk to and get policy or a sitecode. If they have set up ConfigMgr boundaries correctly for your device and they have extended the schema in AD then you would not need to add any switches to the install command - however this does not look to be the case so you need more info.

One question - is your device in a domain or is it a workgroup PC?

If domain then I would go back to the admin and tell them to make sure boundaries exist for the IP range or AD site that your device is in. Get the MP and Sitecode details then refer to this article for installing the client with the correct switches https://technet.microsoft.com/en-us/library/gg699356.aspx

If workgroup then you definitely need to get the MP details and add in the correct switches.

But to be honest your ConfigMgr admin really needs to get onto this and give you more info or look into the problem themselves.

Rebuild the machine. No way!

Paul,

Thanks for the reply.  My machine is in a domain.

I may have misstated things a bit when I said that the site admin removed the client from my machine.  He was working with a less experienced tech, and it may have been that tech who removed the client.  Regardless, the situation is that it got removed and we have not been able to get it re-installed.

Also, to follow up on the WMI errors that I got when I ran the WMIDiag utility, I did a bit more research on that and found this article:

http://blogs.technet.com/b/askperf/archive/2014/08/08/wmi-repository-corruption-or-not.aspx

The article contains a number of tests to help determine if the WMI repository is corrupt.  I checked as many of the items in the article as I could, and from what I can see, it all looks good.  I don't see any of the listed errors in my Application log, I can run the get-cimclass commands without error, and the winmgmt /verifyrepository command comes back with, "WMI repository is consistent."

However, I did notice one curious item.  Per the article, I checked the objects.data file size and found it to be 16,464 KB.  But I also noticed that the C:\Windows\System32\wbem folder contains two repository folders:

• repository
• repository.001        (The date on this folder is the same date as the last time my machine      communicated with the SCCM server.)

I'm not sure that's relevant, but I thought I would mention it just in case.

I will pursue your recommendations and will report back as soon as I can.

--Tom