Forums on Intune, SCCM, and Windows 11

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!

PENDING SCCM client push Error 0x80072f76

  • Thread starter Thread starter Aneesh
  • Start date Start date
  • Replies Replies 6
  • Views Views 6K

Aneesh

New Member
Messages
1
Reaction score
0
Points
1
Hi,
We have recently implemented a new sccm infrastructure with a primary site and a secondary site (for the branch location). Boundary groups are created with IP subnets / AD site and associated with appropriate sccm sites. The system discovery works fine, the secondary site clients are assigned with the secondary site code during discovery and the clients which comes under primary site are assigned with primary site code. As it is a testing phase we have not enabled automatic client deployment.

The issue is when we do client push to the clients assigned with secondary site (or manually initiated a client push from the secondary site), it fails with the below errors during the BITS download -
BG error context is 5
Download Update: A recoverable error has occurred. A retry attempt will be made. Error: 0x80072f76, Description The requested header was not found, Context: The error occurred while the remote file was being processed.." .
I have checked the ccmsetup.log file in the client machine and confirmed that it detects correct MP and DP (secondary site).

When we manually select the primary site and push the client to the same station (discovered by the secondary site code), it works fine. Also, during the installation it detects the secondary site as DP and fetches the required installation files via BITS from the secondary site servers. It uses the primary site server only to copy the initial files like mobileclient.tcf and ccmsetup.exe. In this case these 2 files need to come over WAN to the secondary site clients (rest BITS transfer is via local DP, secondary site). We would like to avoid this.

As the installation is successful when assigning from the primary site and the client deployment files are downloading from the local dp (secondary), we dont think there is a network/proxy/boundary/av block/ issue with the secondary site. But something somewhere is wrong.



Aneesh
 
Last edited:
I had the same issue and this is how I solved it:

1 - First of all make sure that your Windows Firewall Service is Running.
Windows Firewall should be turned off but the AV Service should be running. It's to do with the way it allows traffic in basically until the "disabled" service really disables itself you're blocking traffic and when it's on it'll let it through.

2 - Since the download jobs are using BITS, then try to copy the Client Folder locally to the PC and run it locally.
I used the following commands:
cd c:\users\<user>\desktop\client
ccmsetup.exe source c:\users\<user>\desktop\client

3 - Check if you need to repair the WMI if you're getting an error of 0x8004100e

You can use the following batch script file:

cd /d %windir%\System32\Wbem
net stop winmgmt

sc sdset winmgmt D:(A;;CCDCLCSWRPWPDTLOCRRC;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;DA)(A;;CCDCLCSWRPWPDTLOCRRC;;;PU)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;SY)

REM REG IMPORT %windir%\WBEM.reg

winmgmt /clearadap
winmgmt /kill
winmgmt /unregserver
winmgmt /regserver
winmgmt /resyncperf

del %windir%\System32\Wbem\Repository /Q
del %windir%\System32\Wbem\AutoRecover /Q

for %%i in (*.dll) do Regsvr32 -s %%i
for %%i in (*.mof,*.mfl) do Mofcomp %%i
wmiadap.exe /Regsvr32
wmiapsrv.exe /Regsvr32
wmiprvse.exe /Regsvr32

net start winmgmt


Let me know if it works.
 
I had the same issue and this is how I solved it:

1 - First of all make sure that your Windows Firewall Service is Running.
Windows Firewall should be turned off but the AV Service should be running. It's to do with the way it allows traffic in basically until the "disabled" service really disables itself you're blocking traffic and when it's on it'll let it through.

2 - Since the download jobs are using BITS, then try to copy the Client Folder locally to the PC and run it locally.
I used the following commands:
cd c:\users\<user>\desktop\client
ccmsetup.exe source c:\users\<user>\desktop\client

3 - Check if you need to repair the WMI if you're getting an error of 0x8004100e

You can use the following batch script file:

cd /d %windir%\System32\Wbem
net stop winmgmt

sc sdset winmgmt D:(A;;CCDCLCSWRPWPDTLOCRRC;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;DA)(A;;CCDCLCSWRPWPDTLOCRRC;;;PU)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;SY)

REM REG IMPORT %windir%\WBEM.reg

winmgmt /clearadap
winmgmt /kill
winmgmt /unregserver
winmgmt /regserver
winmgmt /resyncperf

del %windir%\System32\Wbem\Repository /Q
del %windir%\System32\Wbem\AutoRecover /Q

for %%i in (*.dll) do Regsvr32 -s %%i
for %%i in (*.mof,*.mfl) do Mofcomp %%i
wmiadap.exe /Regsvr32
wmiapsrv.exe /Regsvr32
wmiprvse.exe /Regsvr32

net start winmgmt


Let me know if it works.

It is NOT recommend to KILL WMI like that. Bad things can happen, if you do it.
 
It is NOT recommend to KILL WMI like that. Bad things can happen, if you do it.
Well obviously yes, but I had no choice since I had a critical server and I needed to fix the WMI since it was causing a lot of problems.

However and as I mentioned the main solution would be to check the AV service if it was running.
 
Well obviously yes, but I had no choice since I had a critical server and I needed to fix the WMI since it was causing a lot of problems.

However and as I mentioned the main solution would be to check the AV service if it was running.
Server are even more important that you don't do this. Did you run WMIdiag first?
Honestly for server I would contact MS Support as many bad things can happen if WMI is blown away like this.
 
Server are even more important that you don't do this. Did you run WMIdiag first?
Honestly for server I would contact MS Support as many bad things can happen if WMI is blown away like this.


Well of course, yes I did run WMIdiag and the report was a disaster.

Additionally, and for your information, I used this method on MANY SERVERS not just on the one where the WMIDiag gave many errors in the report, and besides when checking wmimgmt.msc I could see that it was failing to connect to Local Computer.

Hope my answer is clear to you. :)
 
Last edited:

Forum statistics

Threads
7,171
Messages
27,990
Members
18,297
Latest member
Kahnrym

Trending content

Back
Top