I have a customer who uses SMS 2003. We are potentially going to deploy SCCM 2012 in the same domain. I realize there is no direct migration path and it is irrelevant at this stage as migration is not yet in scope, it looks like they may run side-by-side for a while.

The customer does not want to make any changes to their SMS configuration at this stage. Can we still deploy SCCM 2012 and publish information to AD and DNS without impacting SMS? We will potentially have a Windows XP machine reporting to SMS physically sitting next to a Windows 7  machine reporting to SCCM.

If we have overlapping SMS & SCCM boundaries, will the SMS clients continue to only look at the SMS for site assignment and content locations and vice-versa (will the SCCM clients only look to SCCM for assignment and content location)? Basically I want to confirm that SMS & SCCM '12 can exist side by side without interfering with each other.

I've seen other posts on the interwebs (eg http://www.myitforum.com/forums/m237077-print.aspx) however I was looking for some confirmation that is a little more offici

Hi,

The answer that Bechir gave you is correct, using site boundaries in SCCM 2012 for content location only is not considered overlapping. So as long as you don't use the boundaries in SCCM 2012 for site assignment it will work just fine.

The link that Bechir provided contains the information. http://technet.microsoft.com/en-us/library/hh427326.aspx

Regards,
Jrgen

Hi,

The answer that Bechir gave you is correct, using site boundaries in SCCM 2012 for content location only is not considered overlapping. So as long as you don't use the boundaries in SCCM 2012 for site assignment it will work just fine.

The link that Bechir provided contains the information. http://technet.microsoft.com/en-us/library/hh427326.aspx

Regards,
Jrgen

Hi,

Exactly, Use the SMSSITECODE = 111 instead of Auto.

I haven't seen/had or heard of any other issues in these scenarios, no problems with the objects in AD.

I have it setup that way in the environment I am in front of right now.

Regards,
Jrgen

We are in a similar situation, but our 2003 environment has a script that runs in a policy to autoassign the site code.  In the 2012 environment we have only one site and can manually assign the site code.  If we were to go the route recommended in your post, and make sure we set up the boundary group for content location instead of site assignment, will this work for our environment and can we set up boundaries by site or subnet as a result without conflict?  We want to migrate our win7 machines over first and since they are all over the place, I'm trying to set up a boundary for them that won't interfere with the 2003 environment, but I thought we couldn't set up boundaries by AD site or subnet if they were already in use in the older environment.

We are in a similar situation here.  Just in the process of migrating from SMS 2003 to SMS 2012R2.  Both environments are currently operational.  We manually assign site codes to SMS clients, and it's automated for 2012.  

If we disable AD discovery on our 2012 Boundary Groups, and wish to use SCCM Client Push, I understand we can manually assign the site code.  However what if we want to use the Generate CCR tool?  I haven't looked into it if there is a way to manually assign the site code through this utility or not.

Currently we are running into issues that I don't believe is 2012 AD discovery related.  Within the LocationServices.log on some of our SCCM clients, we will have entries of ForestTrust: "NO" ... my understanding is that once this happens, the SCCM client will rotate through and locate another Site Server.  Looking in the ClientLocation.log I notice that the local management point and proxy management point is rotated a few times a day.  The problem we are running into is that some of our SCCM client discover the old SMS MPs via AD and therefore, has none for a period of time, which prevents the client from working properly e.g. no SW Centre, reporting etc.

So my question is, can we disable Publishing to AD from within the SMS Site Servers and not affect current SMS operations, if we're manually assigning site codes to existing SMS clients?  If yes, then can we safely remove the AD entries referring to the SMS site servers, along with any WINS and DNS entries?

Thanks for your assistance.