0

I have a WSUS 3.0 SP2 environment, using Server-side trageting, but some clients are getting a registry entry for TargetGroup, as if they were managed using Client-side targeting. Interestingly the TargetGroup name is not even vaguely valid - is a seemingly random string, over 255 char long, and so fails without attempting to connect to anything. I have never used Client-side targeting.

Have searched the GPO's applying to these targets, and manually deleted the TargetGroup entry to see if the GPO would re-populate it, but it remains blank. Sometime in the next 30 days or so (when i go to test patches again), the clients stop responding, and the registry entries have changed again.

Note is only some clients, but seems to be the same ones each time.

Any clues would be appreciated, Justin

Improve this question
5
  • Were these clients deployed from an image?
    – joeqwerty
    May 23, 2017 at 2:35
  • Yep. After imaging, we run a batch to delete and re-create the SoftwareDistribution and CatRoot2 folders, and then restart the wsus service and run wuauclt.exe /resetauthorization /detectnow
    – Justin Gillfeather
    May 24, 2017 at 3:08
  • I should have asked if you Sysprep the image. If not then the clients will have a duplicate SUS ID, which may be contributing to your problem. You need each client to create a new SUS ID. You can use the linked script to do so. - gallery.technet.microsoft.com/scriptcenter/…
    – joeqwerty
    May 24, 2017 at 3:13
  • Thanks Joe, have given that a crack and so-far, so-good - 4 hours later the PC is reporting to WSUS and is notifying of pending updates. Will update again in 18 hours, cheers
    – Justin Gillfeather
    May 25, 2017 at 5:11
  • Hmm. No joy, TargetGroup has been repopulated from somewhere and the WSUS host has been reset to the Microsoft host. Doesn't seem to he GPO related, i can deleted the TargetGroup registry setting and gpupate /force the clients, and get the expected, correct result (i.e. no TargetGroup and internal WSUS URL). Then sometime in the next 24 hours it gets reset back to a TargetGroup and the MSFT WSUS URL.
    – Justin Gillfeather
    May 26, 2017 at 3:29

1 Answer 1

Reset to default
0

Never did get to the bottom of this. The units that were incurring the issue have since been re-imaged, and I was careful to manually remove them from WSUS before re-creating PC's with the same computer name. Both have since re-joined the WSUS host without incident - Justin.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .