SCCM not pushing out software updates from disruption points

[FN-GM]

Hello,

 

We are a MAT and use SCCM. I have attached a copy of our topology. SCCM will only deploy software updates (ie Windows updates) to school 1. Computers at school 2 & 3 schools are suck as "client check passed/active" in the deployment status. Software application deployment and OSD via PXE works fine and the clients are picking up the data from the correct DP (so boundaries are ok). School 1 works ok with software updates.

 

I have tried deleting the software update group, package and deployment and creating new and it doesn't make a difference.

 

Does anyone have any ideas please?

 

Thanks

[sparkeh]

Have you looked at the various updates logs on one of the affected clients?

 

Off the top of my head something like updatedeployment.log and the evaluation log will be useful

[Steve21]

Are you trying to make 2/3 come back to 1 for updates or download direct from their own sites?

 

If you want them to download from their own ones, did you set the update group to get deployed to both 2/3 DPs? And those clients have the policy to get Updates from their local one? Are the DPs actually receiving the update groups?

 

If you wanted them to come back to 1 does it have downloads enabled over slow links etc?

 

Steve

Edited October 10, 2017 by Steve21

[FN-GM]

All the DP will use the same package but it will be copied locally onto the local school DP from the package source shared folder. The package is set to go to all DP's and I can confirm it is on there.

 

I haven't looked at the logs. Will have a look.

[FN-GM]

This is the single error in the log

 

GetUpdateInfo - failed to get targeted update, error = 0x87d00215. UpdatesDeploymentAgent 11/10/2017 08:33:34 3328 (0x0D00)

 

I have looked this up and the posts on the internet are saying the client is looking at the wrong addresses in the WSUS settings in the registry (HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate). I have checked this and the settings are correct and match working machines.

[Steve21]

I'm not really sure how you're setting this up here. (as in how you want it to work)

 

The standard way to do it would be deploy SUPs to the two secondary sites, which then replicate the main one, and those clients within the boundaries are set to use the local SUP. If you're pointing all the clients via Registry back to the PrimarySite (1) they'll pull info across from the SUP.

 

Deploying via a DP should work fine, but I'm not sure why you're talking about copying the files across locally (unless just a phrase you used) as it should automatically distribute the content to the DPs for you.

 

When the clients try to update, what's it saying in their location logs about connecting to SUPs/DPs etc?

 

Steve

[FN-GM]

We only have 1 SCCM site, but have 3 physical sites (buildings) in the topology. Isn't the SUP designed to sync with WSUS? So you would only have 1 per SCCM site.

 

When I say copying the files, I am talking about when using the distribute content wizard.

 

It is pickup up the correct DP in the logs. Other stuff like Package deployment and OSD still work ok.

[FN-GM]

This is driving me nuts. I can't find whats going on. I have reinstalled the DP's and it hasn't made a difference.

[Steve21]

If you want to throw up (or email if it's easier) a set of logs across happy to have a dig through, but not much to say without finding the details/errors in log I'm afraid

 

Steve

[FN-GM]

I might do that, but I think I am onto something. I have this in a log. The computer is in a Maintenance Window and has one assigned to a collection it is a member of. I also set the software update deployment to install outside of the Window.

 

No current service window available to run updates assignment with time required = 1 UpdatesDeploymentAgent 16/10/2017 16:30:00 6372 (0x18E4)

 

 

I might delete the maintenance window and recreate it.

Edited October 16, 2017 by FN-GM

[FN-GM]

I recreated the the Maintenance Windows and they are slowly picking themselves backup now. Bit of an odd one!