0

Ran into an issue that I am drawing a blank on. Running WSUS on Server 2016 standalone domain server. Loaded from 2016 Roles/Features. Here's the kicker, on a 2008 AD.

I have the OU set up and the GPO and one test PC is under GPO control for windows update.

I added the OU group to WSUS but the PC is not listed (Win10 Pro, 1803). Its been the weekend and no update.

Options setting in WSUS is to user Group Policy. Am I missing a new setting or something to get the PC to show up on Server 2016 WSUS?

UPDATE:

enter image description here

enter image description here

enter image description here

enter image description here

enter image description here

17
  • You haven't given us nearly enough details. Running WSUS on Server 2016 standalone domain server. - That's a confusing statement. Is this server joined to the domain or not? I have the OU set up and the GPO and one test PC is under GPO control for windows update. - What settings did you specifically configure in the GPO? I added the OU group to WSUS but the PC is not listed. - What OU group? Did you configure the WSUS group name in the GPO? Did you create the corresponding group in WSUS? Did you configure the GPO to direct client machines to the WSUS server?
    – joeqwerty
    May 21, 2018 at 20:00
  • Yes the server is joined to the domain. The OU group in WSUS is the same one created in AD for this purpose. Policy is Computer Config\AdminTemp\WindowsComponent\WindowsUpdate\ 3 - ConfigureAutoUpdates,SpecifyIntranetMSupdateServLocation, EnableClient-sideTargeting. I post an update to the OP in a few with some screen shots. And yes I believe its configured correctly in both place unless I missed something.
    – htm11h
    May 21, 2018 at 20:06
  • The target group in WSUS isn't an actual AD security group. It's simply a name so that clients know which WSUS target group to populate. You need to configure the GPO to specify the WSUS target group name and you need to create the target group in WSUS.
    – joeqwerty
    May 21, 2018 at 20:14
  • Please see the images uploaded isn't that what is displayed?
    – htm11h
    May 21, 2018 at 20:16
  • 1
    OK, so we've identified the problem. The GPO is not being applied because of security filtering. What is the Security Filtering set to in the GPO?
    – joeqwerty
    May 22, 2018 at 18:05

1 Answer 1

0

Once you have all of your GPO settings in and double-checked, you'll probably need to issue "gpupdate /force" from an Administrative command prompt on your windows machine. The machine will likely reboot, after which it should show (at least initially) in the "uncategorized" WSUS computers group.

Sometimes a computer won't show if another instance of Windows with the same name (either the same machine from a different install or a different machine altogether) had previously existed on the WSUS server. Your best bet then is to delete the old WSUS registration and re-run the GPO update. If that doesn't work, there ought to be an error message in the Event Viewer related to why.

2
  • So there is no OLD installation here, this is a new set up, and only one test PC ever added. I have tried to run gpudate /force a number of times over the past few days and have rebooted both WSUS server and client, not the domain GPO server though as the GPO is being applied.
    – htm11h
    May 22, 2018 at 15:35
  • In that case, do you have any messages in Event Viewer related to GPO processor or WSUS? On either client or server? May 22, 2018 at 17:52

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.