Domain Controller Not receiving SCCM Windows Updates

Ive got a couple of DCs which are not seeing any SCCM Windows patches, they both have a GPO pointing them to a WSUS server, Ive checked the Windows update logs and it states something about a proxy issue but I doubt servers need a proxy to be set for WSUS/SCCM updates. Any ideas on where I should start?
Jon MAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Lawrence TsePrinciple ConsultantCommented:
Then do your domain controllers have SCCM client deployed?  The WSUS is managed by SCCM or standalone?
David Johnson, CD, MVPRetiredCommented:
the default is to NOT have the SCCM client deployed to DC's. You have to enable the checkbox to include Domain Controllers

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Lawrence TsePrinciple ConsultantCommented:
If you have SCCM client ALREADY deployed to the domain controller, you need to aware that previous GPO pointing to legacy WSUS will interfere SCCM patch deployment, since SCCM agent will attempt to write patch download location to a computer (including domain controller) but it is FORCED rewritten by GPO.

If only domain controller is having this problem, this this might be because of group policy inheritance, since domain controller is having different group policy inheritance path than other domain computers.
Lawrence TsePrinciple ConsultantCommented:
The reason of SCCM client deployment is not including domain controller by default, is to avoid unnecessary tasks, including application deployment to be run on domain controller unexpectedly.  Once agent is deployed, the operations of SCCM client agent on domain controller is similar to that on normal client.

I suspect this is a GPO problem instead.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.