Justin Gillfeather's questions

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

Anyone uing AD Connect Sync Health in a non-Express setup yet?

I have a the Sync Health agent installed, and connected to AAD, but am getting an error - in the Sync Error applet it shows "Latest data is not available". AD Connect itself seems fine, my objects are syncing aok.

Interestingly, the DC at the on-premise end shows no Event Log entries in the Microsoft Azure AD Sync/Debug and Sync/Operational logs - not only no errors, no entries at all. Maybe its an issue at the on-premise end?

Any suggestions welcomed, Justin