Time to migrate your 2007 SCCM envoirment to 2012. The first thing you might think of is how to push out the new client and how and when to configure boundaries.
First of all configure the client push settings on the 2012 site.
Then go to Installation Properties and configure the new 2012 site code:
SMSSITECODE=Sitecode and also i added my Fallback Status Point FSP=server.local This will tell the computer/client what site they will assign to.
Configure the boundaries at your new SCCM12 site and assign it to a boundary Group.
At this time you will now be able to push out the new client using client push or GPO. Remember to place the package to your DP.
Remember to uncheck the Auto assigment under Client Push Installation Properties, why? Because you don’t want both sites to auto assign their clients.
|Site assignment||Site assignment is used by clients that use automatic site assignment to find an appropriate site to join, based on the clients current network location. After a client assigns to a site, the client will not change that site assignment. For example, if the client roams to a new network location that is represented by a boundary in a boundary group with a different site assignment, the client’s assigned site will remain unchanged.When Active Directory System Discovery discovers a new resource, network information for the discovered resource is evaluated against the boundaries in boundary groups. This process associates the new resource with an assigned site for use by the client push installation method.|
|Content location||Content location is used by clients to identify available distribution points or state migration points, based upon the client’s current network location|