Our SMS infrastructure is small. We are moving to SCCM R3. I will build a new SMS Primary site and then upgrade it to SCCM and break the relationship between SMS and SCCM. The finish setting up new SCCM sites, etc. Pretty vanilla. 1. After I setup the new SMS 2003 primary (future SCCM Central site), how long should I wait for replication to move over all the packages/queries/collections, etc to the new SMS 2003 primary site? We have 2 other primary sites and 7 secondary sites. The SQL DB on the central site is about 1GB. 2. We are upgrading from SMS 2003 SP2, to SCCM 2007 R3. Can we reuse site codes from SMS, to SCCM? Our AD heirarchy at our company relies on site codes as defined for AD. These site codes were also used for SMS. If we create new site codes for SCCM, there will be conufion as an office in atlanta in SMS would show up as ATL, but for SCCM it might be ATA. Such a change would confuse many on our networking team if they had to help in/with SCCM. 2b. Once I upgrade the new SMS 2003 primary to the SCCM central site, do I need to shut down the SMS Central site? Can I have the same site code for the SMS central site and SCCM central site?

Hi, 1) Depends on the number of packages that you have. I normally wacth the replication traffic between the two sites (sender.log). I normally let it replicate for at least a day (in a small/medium environment). 2a) You can't have two sites in the same hierachy sharing the site code. I normally never recommend reusing the sitecode. 2b) Same answer as 2a Merry ChristmasKent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund