One of the user reported an issue related to SCCM client agent installation. The user was running SCCM 2012 R2 in his setup and was unable to install client agent. However he mentioned that this issue was not occurring on all machines but just few. Out of 270 machines, around 260 machines got the client agents installed. Seems like he also tried installing the client agent manually but was unsuccessful. He also did a bit of troubleshooting and found that the ccmSetup failed with error code 0x80200014.
Looking at ccmsetup.log file showed some proper hints to fix this issue. Below are some of lines from ccmsetup.log file. If you notice the error is related to BITS. While the error reads “BITS 2.5 or later is required” this wasn’t true. The user mentioned that the OS did have BITS installed. The OS was patched with latest updates as well.
Searching this error leads to a Microsoft article that talks about this error. The solutions to this issue are mentioned at the end of this post.
BITS job creation failed with 80200014. Unable to check BITS version ccmsetup. This operating system does not contain the correct version of BITS. BITS 2.5 or later is required. Failed to open to WMI namespace '\\.\root\ccm' (80041002) Failed to get client version for sending state messages. Error 0x80041002 ccmsetup. Params to send '5.0.8239.1502 Deployment This operating system does not contain the correct version of BITS. BITS 2.5 or later is required.' A Fallback Status Point has not been specified and no client was installed. Message with STATEID='321' will not be sent. Failed to send status 321. Error (87D00215) CcmSetup failed with error code 0x80200014 ccmsetup
As per Microsoft “This problem occurs because Microsoft Background Intelligent Transfer Service (BITS) version. The BITS version 2.5 or a later version must be installed before you can install the System Center 2012 Configuration Manager client.”
CcmSetup failed with error code 0x80200014
If you come across CCMSetup failed with error code 0x80200014 issue, you can perform the following steps.
- Note that BITS version 4.0 is included in Windows 7. Furthermore if you find that BITS is not installed on the machine, install it first and then install the client agent.
- The second method that you can try is install the client agent with following command line. CCMSetup /mp:<mp name> /BITSPriority:LOW SMSSITECODE=<sitecode> FSP=<fsp name>. The bitspriority specifies the download priority when client installation files are downloaded over an HTTP connection. The values can either HIGH, LOW, FOREGROUND or NORMAL.
The user mentioned that second method worked fine. Installing client agent using /BITSPriority:LOW switch in the command did the trick. Using the command mentioned in the second step, the agent was installed successfully.