HelloI have SCCM hierarchy with a lot of primary sites. AD is extended, sites publish their information in AD, boundaries are good and everything is green. I use a sturtup script to install clients with only "ccmsetup.exe" in command line throughout my hierarchy (because this is the only way to automaticaly assign FSP). And it works great! But not always... On some machines ccmsetup cannot find installation files and fail, because it cannot get MP from AD. And i see a very interesting difference in the beginning of ccmsetup.log file on good and on failed computers:GOOD ONE==========[ ccmsetup started in process 1668 ]==========]<![LOG[Version: 4.0.6487.2000]LOG]!><![LOG[GetAdaptersAddressess entry point is supported.]<![LOG[DhcpGetOriginalSubnetMask entry point is supported.]<![LOG[Current AD site of machine is Default-First-Site-Name]<![LOG[Attempting to query AD for assigned site code]<![LOG[Executing query (&(ObjectCategory=MSSMSRoamingBoundaryRange)(|(&(MSSMSRangedIPLow<=167921174)(MSSMSRangedIPHigh>=167921174))))]<![LOG[Executing query (&(ObjectCategory=mSSMSSite)(|(mSSMSRoamingBoundaries=10.2.70.0)(mSSMSRoamingBoundaries=Default-First-Site-Name)))]<![LOG[LSGetAssignedSiteFromAD : Trying to Assign to the Site <G01>]BAD ONE:=====[ ccmsetup started in process 3836 ]==========]<![LOG[Version: 4.0.6487.2000]<![LOG[GetAdaptersAddressess entry point is supported.]<![LOG[DhcpGetOriginalSubnetMask entry point not supported.]<![LOG[Current AD site of machine is Default-First-Site-Name]<![LOG[Attempting to query AD for assigned site code]<![LOG[Executing query (&(ObjectCategory=MSSMSRoamingBoundaryRange)(|(&(MSSMSRangedIPLow<=167920668)(MSSMSRangedIPHigh>=167920668))))]<![LOG[Command line: "ccmsetup.exe" ]<![LOG[Ccmsetup was run without any user parameters specified. Assume AUTO sitecode and run without registering ccmsetup as a service.]and it ends by not founding source and failingThe crucial difference is that bad client does not perform this query Executing query (&(ObjectCategory=mSSMSSite)(|(mSSMSRoamingBoundaries=10.2.70.0)(mSSMSRoamingBoundaries=Default-First-Site-Name)))], which returns a valid MP from AD.But why? The only difference between good and bad computers as I noticed is that the good ones are in 10.2.70.0/24 subnet, and the bad ones are in 10.2.68.0/24 subnet. But Default-First-Site-Name contains neither 10.2.70.0/24 nor 10.2.68.0/24, in contains 10.2.0.0./16 subnet which includes the both. But if you look into the "bad" ccmsetup.log, you'll find Current AD site of machine is Default-First-Site-Name. It seems OK.To be honest I have not yet tried to move machines between subnets - I can't yet.Does anyone have any ideas about this strange (at least for me) behavior?

Have you created a AD boundary = Default-First-Site-Name at all primary sites?Minh.Minh

No, Default-First-Site-Name is the boundary of only one site, other sites have different boundaries (AD sites)