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...
My latest issue is that I wanted to monitor GroupID based "consumption" via WUfB Reports, but the obfuscated GroupID's shown in the reports mostly remain a mystery. Can you please shed some light on what's going on?
I've got a defined GroupID in every subnet and policy telling the endpoints to use it. Out of the 9 displayed obfuscated GroupID's, only one of them pops out of the hashing process to reveal itself as our AD Domain SID. None of the others match DHCP, Entra tenant, AD site names, or DNS domains. Unfortunately, the AD Domain SID one isn't the largest.
I decided to try and find out what the largest obfuscated GroupID was. It has around 1,600 endpoints in it. I tracked down several devices with this obfuscated GroupID and found their locations to be random from my perspective. Each DHCP subnet confirmed as having a GroupID in the scope options.
I then focused on one device and grabbed its DO log. There I found a completely different obfuscated GroupID to the one associated in the WUfB report. Low and behold, that obfuscated GroupID in its log was an exact match for the DHCP scope option-supplied GroupID.
Looking at the WUfB report data, an agent captured that the sample device had two different obfuscated GroupID's associated with it:
Agent finds multiple GroupID's associated to the same device
In this example the device had 8 rows matching the expected obfuscated GroupID, but just one with the mysterious obfuscated GroupID that 1,600 devices have also been linked to.
Where are these obfuscated GroupID's coming from because they do not match the published documentation for what they should be?
Clearly there's a pattern, given 1,600 all got the same one. Is it the shared Public IP? That's the only correlation I could guess here after all the other possible matches failed.
Why is this happening? The clients themselves appear to show that they are correctly using the DHCP scope option.
Could this also explain why peer selection was not sticking to GroupID as expected? I've had to lock it down to the subnet restriction, and this prevents clients on the same site/different subnet from peering.
Nearly all endpoints are Windows 11 25H2, kept up-to-date by Autopatch.
@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.