You've deployed Delivery Optimization settings and perhaps even a Microsoft Connected Cache node to reduce network traffic on Patch Tuesday. But things aren't working as expected. You aren't seeing g...
@AndrewMcN_SFRS, yeah, you've hit a reporting quirk. The GoupID GUID you will see in the DO log will not be the actual GroupID. There's some obfuscation happening.
Other than this quirk, do you see peering results as you would expect per group?
Thanks for replying. Sorry if I wasn't clear. Unless you're talking about some additional obfuscation, I know all about the obfuscation. In fact, I wasted months thinking my decoding wasn't working because I just couldn't find matches to my DHCP GroupID's. That was the story I TL;DR'd above.
I'm saying there's obfuscated GroupID's in there that don't match any of the expected sources. I'm saying there's at least two obfuscated GroupID's being associated with single devices. Shouldn't that be impossible??? WUfB Reports is picking the wrong/unknown/mysterious obfuscated GroupID's. The ones we can't decode. The report tells me nothing I can use.
When I refer to the GroupID in the DO client log, I mean the already obfuscated one. I can see that the DO client appears correct. Yet this other obfuscated GroupID has been attached to the device within the WUfB reports data. The report template shows most of our results with these mysterious obfuscated GroupID's that match none of the standard origins.
In this snapshot, only one of the obfuscated GroupID's actually matches something:
It's the one that starts "24g1". That's our AD Domain. That shouldn't even be appearing at all. I have unique DHCP GroupID's for every one of our sites. Group Policy tells the clients to use Download Mode 2 (GroupID). I don't even know what that obfuscated GroupID is with the most clients in it. Nothing I hash matches it.