SMS to SCCM Side by Side
I wanted to put together a Blog that will help you with transitioning from SMS2003 one an older server to SCCM2007 on a new server while still maintaining your custom collections and packages. I hope you find this helpful.
Background: Single SMS 2003 site with no child sites. SQL 2005 with SP2 on a single system.
Goal: to move to SCCM 2007 SP2 R3 on new hardware, retain custom groups, packages and reporting.
You will need to install SCCM 2007 in a Primary Site, configure all site systems and settings (except the site boundaries). As a best practice give this a new site code.
Once your new SCCM 2007 server is installed, attach the SMS 2003 site as a child site to SCCM 2007.
Create a standard sender address in both directions
Add the SMS2003 Server to the local group SMS_SitetoSiteConnection_(sitename) group
Do the same for the SCCM2007 server on the SMS 2003 local group
On the SMS 2003 Server configure the parent Site
The Site now appears as a child site in SCCM
Use an existing client installation method at the sms 2003 site to upgrade the client to SCCM 2007 and assign it to the new site.
I create a package and point it to the client installation of the new SCCM2007 Server
Once all clients have been upgraded and reassigned, disable all discovery and client installation methods at the SMS 2003 site.
(Do this for all Discovery Methods you wish to discover)
If your SMS 2003 site has boundaries, you will need to remove them as well as the roaming boundaries from the SMS 2003 site. Make a note of these as you will need them for the next step.
Add the boundaries you just removed from the SMS 2003 site to the SCCM 2007 site.
If the SMS 2003 site is publishing site information to AD DS you will need to disable this.
If the SMS 2003 site system has been registered with WINS you will need to uninstall the site systems that have been published to wins and remove the wins registration from the sms 2003 site systems
Do you need to migrate custom collections or software distribution objects to the new SCCM 2007 site? If so upgrade the SMS 2003 site to configuration manager using the in-place upgrade method.
Since I had some collections and packages I wanted to migrate, I had to upgrade my existing SMS2003 to SCCM.
Detach the upgraded site from the hierachy and attach the new 2007 as a child site of it.
Note (Upgraded site=SMS2003 that you just upgraded and the New 2007 is the SCCM2007 that you first implimented)
(on the server you just upgraded change this setting to Central Site)
(on the original sccm server, change to Report to Parent Site)
Allow the custom collections and software distribution objects to replicate down to the new site.
Go back to your New SCCM server and expand collections as well as your software distribution. You should notice a padlock next to the collections and the software packages. This will show that the sites are communicating.
Let the replication complete. In my lab scenario I let it complete over lunch. In a larger environment it will take a little longer.
Distribute packages to the distribution points on the new site and remove references to distributon points on the old site.
- Detach the upgraded site from the hierachy and reconfigure parent site settings if necessary.
Decomission or reattach the orginal site as required by your upgrade plans.
- The upgrade from SMS to SCCM is now complete.
I hope this blog has helped.