By using this site, you agree to the Privacy Policy.
Accept
EnterinITEnterinITEnterinIT
  • HOME
  • IT PRO
  • TECH
  • MICROSOFT
    • Azure
    • ConfigMgr/SCCM
    • DPM
    • Orchestrator
    • Hyper-V
    • Microsoft Edge Insider
    • MSI
    • Office 365
    • Office Insider
    • Power BI
    • Skype
    • SQL Server
    • Teams
  • WINDOWS
    • Windows Admin Center
    • Windows Client
    • Windows Server
  • SCCM Query Collection List
Reading: SCCM 0x80200014
Font ResizerAa
EnterinITEnterinIT
Font ResizerAa
  • HOME
  • IT PRO
  • TECH
  • MICROSOFT
  • WINDOWS
  • SCCM Query Collection List
Search
  • HOME
  • IT PRO
  • TECH
  • MICROSOFT
    • Azure
    • ConfigMgr/SCCM
    • DPM
    • Orchestrator
    • Hyper-V
    • Microsoft Edge Insider
    • MSI
    • Office 365
    • Office Insider
    • Power BI
    • Skype
    • SQL Server
    • Teams
  • WINDOWS
    • Windows Admin Center
    • Windows Client
    • Windows Server
  • SCCM Query Collection List
Configuration Manager Query Collection List
ConfigMgr

SCCM 0x80200014

Published: February 11, 2024
2 Min Read
SHARE

SCCM 0x80200014 CcmSetup failed with error code.

Looking at ccmsetup.log file showed some proper hints to fix this issue.

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

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 to install the client agent with the following command line. CCMSetup /mp:<mp name> /BITSPriority:LOW SMSSITECODE=<sitecode> FSP=<fsp name>. The bits priority specifies the download priority when client installation files are downloaded over an HTTP connection. The values can either be HIGH, LOW, FOREGROUND, or NORMAL.

Note: 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.

TAGGED:System CenterSystem Center Configuration ManagerTechnical Preview
Previous Article Microsoft Teams Jira Server Integration
Next Article Configuration Manager Query Collection List SCCM Task Sequencing Environment Failed with Error Code 0x80220005
Leave a Comment Leave a Comment

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Translation

English中文(简体)DanskNederlandsFrançaisDeutschItaliano한국어PolskiPortuguêsRomânăEspañolУкраїнська
by Transposh - translation plugin for wordpress

Popular Posts

System Requirements for Windows Server 2016
Windows Server
Configuration Manager Query Collection List
Configuration Manager Query Collection List
ConfigMgr
Structured/Managed Navigation enabled on Modern Pages in Classic Team Sites
Tech
SCCM Failed to get DP locations as the expected version from MP
ConfigMgr

Recent Posts

Installing and Configuring Fail2ban for SSH Protection on Ubuntu 24.04
Linux
Enabling and Configuring FirewallD on AlmaLinux
Linux
User Creation and SSH Key Setup in AlmaLinux
Linux
How to reset password on AlmaLinux
Linux

© 2023 EnterinIT

Go to mobile version
Welcome Back!

Sign in to your account

Username or Email Address
Password

Lost your password?