I am having an issue with clients running a TS with USMT capture. I have 66 SMPs in our Single Primary Site SCCM 2012 SP1. We have one Boundary Group that has 15 DP/SMP servers on it that represents locations that are connected by a 6GB fiber ring. Then I have 51 other boundary groups that are smaller WAN connected locations, each boundary group has a DP/SMP server on site to accommodate clients at those locations.
I am using boundaries created by AD forest discovery. I have 12 AD sites that I have in one boundary group called PS1 which is used for site assignment only there are no content servers listed for that BG. The other boundary groups were created using the IP range Boundaries that were created when AD Forest Discovery did its thing.
My issue is that Clients in the smaller sites don't seem to understand the Boundary Groups for SMP purposes. I can see in the SMSTS log that the client sends a request to the MP for a list of available state migration points. I can see the client received 160338 byte response. The list parses out and I can see a list of all the SMPs, the AD site for that server and one (not all) of the "subnets" associated with that SMP. That there are subnets in the message is strange because the boundaries are actually IP Ranges. Also the list as I look at it in CMTrace is truncated and doesn't seem complete.
But instead of knowing which SMP to go to the Client seems to begin attempting to log into each SMP until it finds one that it can get into then uses it. I can see the client begin to download the USMT package from the correct DP while it prepares to ignore the SMP located on that same server and go across 2 wan links to put the USMT capture on a machine that is clearly not in its boundary group.
I can paste logs here, but it might help to understand better the process of SMP selection. Also some of the networks in AD sites and services are large class B networks like 10.173.0.0\16 but in reality the client computers at that site are being subnetted into Class C networks. Which might be an issue, but the boundaries created when AD Forest Discovery runs are setup as IP Ranges.
I have validated that each boundary created is in only one boundary group and each DP/SMP is only in one boundary group.
Anyone know how SMP selection really works?