SCCM | Intune | Windows 365 | Windows 11 Forums

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED Client installation Fail BG error context is 2 Error: 0x80200010

Status
Not open for further replies.

Kook

Member
Messages
14
Reaction score
0
Points
1
in sccm 2002 siteserver
i have issue with
Windows 10 1903 1909 2004 and higher unable to as below
1.install client
2.deployapplication
3.ADR
But Windows 1607,1703,1709,1803 and 1809 it working.

Download Update: A recoverable error has occurred. A retry attempt will be made. Error: 0x80200010, Description There are currently no active network connections. Background Intelligent Transfer Service (BITS) will try again when an adapter is connected.
, Context: The error occurred in the Background Intelligent Transfer Service (BITS) queue manager.

.
 
Solution
in sccm 2002 siteserver
i have issue with
Windows 10 1903 1909 2004 and higher unable to as below
1.install client
2.deployapplication
3.ADR
But Windows 1607,1703,1709,1803 and 1809 it working.

Download Update: A recoverable error has occurred. A retry attempt will be made. Error: 0x80200010, Description There are currently no active network connections. Background Intelligent Transfer Service (BITS) will try again when an adapter is connected.
, Context: The error occurred in the Background Intelligent Transfer Service (BITS) queue manager.

.


Hello Kook,

The error 0x80200010 will occur if the Background Intelligent Transfer Service (BITS) is not responding due to proxy settings that do not support the...
Hi, i‘m searching for a solution for the same problem. In my environment we upgraded pur sccm clients from Windows 10 1803 to 2004. Before it works perfect but yet the clients does not download policies or applications. The DataTransferService.log shows errors that downloads are not possible- 0x80200010. Same error if i push a client installation. My clients has multiple nics but only the sccm subnet nic has a default gateway. This gateway is also pingable.

Any idea?
 
I tested at a client with only two nics. First one (communication to sccm) has a default gateway. The second one was withiout a gateway. If i add a gateway - bits would work as expected.
 
  • Like
Reactions: mfl
Hi, i‘m searching for a solution for the same problem. In my environment we upgraded pur sccm clients from Windows 10 1803 to 2004. Before it works perfect but yet the clients does not download policies or applications. The DataTransferService.log shows errors that downloads are not possible- 0x80200010. Same error if i push a client installation. My clients has multiple nics but only the sccm subnet nic has a default gateway. This gateway is also pingable.

Any idea?
it same issue gateway can pingable, i try fix gateway it's not work. it's not issue from gateway.
Because this gateway can be used by other clients. (1703, 1709, 1803, 1809 it's working).
 
Can you try to run Get-NetConnectionProfile in Powershell. My problem should be that the IPv4Connectivity shows NoTraffic. With that one BITS should not work.
 
in sccm 2002 siteserver
i have issue with
Windows 10 1903 1909 2004 and higher unable to as below
1.install client
2.deployapplication
3.ADR
But Windows 1607,1703,1709,1803 and 1809 it working.

Download Update: A recoverable error has occurred. A retry attempt will be made. Error: 0x80200010, Description There are currently no active network connections. Background Intelligent Transfer Service (BITS) will try again when an adapter is connected.
, Context: The error occurred in the Background Intelligent Transfer Service (BITS) queue manager.

.


Hello Kook,

The error 0x80200010 will occur if the Background Intelligent Transfer Service (BITS) is not responding due to proxy settings that do not support the HTTP/1.1 protocol. It usually appears when you try to connect to the Microsoft Windows Update.

If you're looking to fix the error 0x80200010 during the SCCM client agent install, the below steps will assist you in troubleshooting the issue,
  • Firstly, press the Win logo + R keys to open the Run command.
  • Then, type the below command in a Run dialog box to access Network connections,
Code:
ncpa.cpl
  • Next, right-click the Ethernet adapter and click Properties.
  • Now, select the Internet Protocol version 4 TCP/IPv4 item and click Properties.
If there's no default gateway address is specified, then the ccmsetup.log file shows up as "There are currently no active network connections."
  • Now, enter the correct default gateway address and click OK to apply.
  • Then, open the ccmsetup.log file using the below path to check client agent has successfully downloaded the files via BITS,
C:\Windows\ccmsetup\Logs\ccmsetup.log
  • Lastly, CcmSetup is exiting with return code 0
Now, the SCCM client agent will install perfectly without any issues. You can also try clearing the BITS queue to troubleshoot the issue.

I hope the above ways help you to resolve the 0x80200010 error code and the server works fine.

----------------------
Regards,
tejtherh4
 
Solution
HI, i had this error and i checked everything was right, Boudary, Boundary Group, Client settings , Firewall Rules, Applied necessary GPO i verified everything but unsuccessfull. i had DC 10.0.1.2/24, SQLDB 10.0.1.3/24 MECMPS 10.0.1.4/24 clients on DHCP. CCM client doesnt install on any machine even if put ip fix. but when i removed all Network Adapters and restarted the VMs added the network adapters again but changed addressing to 192.168.x.x it worked. client installs correctly.

thank you all for your answers regarding this issue, i tried all what suggested here but didnt work. but when i changed VMs IP adresses with other right subnetting it worked.
 

Attachments

  • 1702869842954.gif
    1702869842954.gif
    42 bytes · Views: 8
Can you try to run Get-NetConnectionProfile in Powershell. My problem should be that the IPv4Connectivity shows NoTraffic. With that one BITS should not work.
I know this is a very old topic, but we have the same issue.
A lot of machines showing NoTraffic for their NIC while all other communication is fine, just not SCCM communication.

Did you ever get this solved?
NoTraffic cannot be changed by using Set-NetConnectionProfile and the pc's with issues are running in a 24/7 manufacturing environment, so removing and re-adding NICs etc is not really an option.
 
Hello Kook,

The error 0x80200010 will occur if the Background Intelligent Transfer Service (BITS) is not responding due to proxy settings that do not support the HTTP/1.1 protocol. It usually appears when you try to connect to the Microsoft Windows Update.

If you're looking to fix the error 0x80200010 during the SCCM client agent install, the below steps will assist you in troubleshooting the issue,
  • Firstly, press the Win logo + R keys to open the Run command.
  • Then, type the below command in a Run dialog box to access Network connections,
Code:
ncpa.cpl
  • Next, right-click the Ethernet adapter and click Properties.
  • Now, select the Internet Protocol version 4 TCP/IPv4 item and click Properties.
If there's no default gateway address is specified, then the ccmsetup.log file shows up as "There are currently no active network connections."
  • Now, enter the correct default gateway address and click OK to apply.
  • Then, open the ccmsetup.log file using the below path to check client agent has successfully downloaded the files via BITS,

  • Lastly, CcmSetup is exiting with return code 0
Now, the SCCM client agent will install perfectly without any issues. You can also try clearing the BITS queue to troubleshoot the issue.

I hope the above ways help you to resolve the 0x80200010 error code and the server works fine.

----------------------
Regards,
tejtherh4
Thanks the solution to point me the right direction. This has to do with incorrect default gateway set. In my situation because I am in the vm sandbox, it cannot reach to default gateway I set then the software push failed 0x8004100e on ccm log on the sccm server and 0x80200010 on ccmsetup.log on the client side. All I did to fix it is change the default gateway to my DC in the sandbox then it start pushing the client software.
 
Status
Not open for further replies.

Forum statistics

Threads
6,850
Messages
26,647
Members
17,025
Latest member
mondoobscuro

Latest posts

Back
Top