SMS to SCCM Upgrade (Boundaries Question)
We're moving to SCCM from SMS. The plan is to reassign the site code on blocks of computers, get the computers under SCCM management and then do the client upgrade in blocks as well. Is it necessary to add the boundaries to SCCM at the same time that I use the "Assignsitecode" executable to change the site code on the computers that I'll be moving over? I need to move the computers in groups. I can't do them all at once. Once all my clients are moved over, I'd remove the boundaries in SMS and add them in SCCM and then proceed with client upgrades. In testing, when I change the site code, it 'appears' to fall under the management of the the SCCM server, even if I haven't assigned the ip address boundary for that specific machine. My question comes as a result of how the boundaries are defined in SMS (done before I took it over) Under the SMS Boundaries there is an "AD Site" for each of our remote offices (3) and two "IP subnets" for our campus. This is prohibiting me from doing a controlled cutover to our SCCM environment.Thanks, Dino
November 11th, 2011 10:42am

You can remove the boundaries from SMS 2003, clients can still be managed without any boundaries. You can still deploy packages to the SMS 2003 clients, they just act as being in a slow boundary.Kent Agerlund | My blogs: and | Twitter @Agerlund | Linkedin: /kentagerlund
Free Windows Admin Tool Kit Click here and download it now
November 11th, 2011 1:00pm

Kent, Thanks. What about the SCCM part? Can I change the site code, assigning them to the SCCM 2007 environment and let 2007 manage them and also handle software distribution without expanding the boundaries on SCCM 2007 until after I get all the clients moved over? Thanks, DinoThanks, Dino
November 14th, 2011 7:59am

you need boundaries to assign the clients.Kent Agerlund | My blogs: and | Twitter @Agerlund | Linkedin: /kentagerlund
Free Windows Admin Tool Kit Click here and download it now
November 14th, 2011 8:00am

Kent, In testing, I'm using the 'assignsitecode' app, running it on clients in our SMS 2003 environment via a package deployment and assigning the new site code for our SMMC 2007 environment. That seems to be working as far as moving them over. What am I not getting from your answers? based on your responses I seem to be missing something. DinoThanks, Dino
November 14th, 2011 8:04am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics