Hello, We plan to migrate from SMS 2003 on Windows 2003 with a single site with SQL Server 2000 to SCCM 2007 R2 on Windows 2008 SP2 64 Bits . Is there someone has experience for that migration ? What is the best practices for that ? Thanks, L.

Hi, In your case, we talk about the side by side upgrade http://technet.microsoft.com/en-us/library/bb632845.aspxMicrosoft MVP - SCCM

Thanks, In my case, i would like to proceed like that : - Add a new server Windows 2003 with SMS 2003 and add this SMS site like children to existant SITE. - Replicate Collection, packages, advertissement , reports .... - Broken the links from Parents with Child Site. - Install a new Windows 2008 Server with SCCM 2007 - Replicate data with SMS 2003 Child site ??? What do you think about this ? Thanks a lot,n L

Hi, I am not sure why you want to install a new Windows 2003 with SMS 2003 as a child site. You cannot upgrade the OS to Windows 2008. I would: - Upgrade the SQL 2000 server to SQL 2005 SP3 - Inplace upgrade of SMS 2003 to SCCM 2007 - Install a new SCCM 2007 SP2 R2 with SQL 2008 R2 and add that as a child site (perform the replication as you described) - Change the parent/child order and let the data replica to the new site.Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products

In addition, there is also another way : 1# Upgrade the SQL 2000 to SQL 2005 SP3 2# Inplace upgrade of SMS 2003 to SCCM 2007 http://technet.microsoft.com/en-us/library/bb693584.aspx 3# Run the ConfigMgr backup task (http://technet.microsoft.com/en-us/library/bb632797.aspx) Also, you will need to backup all packages you have setup, including the Package source folders because it's not included on the ConfigMgr backup. 4# Rebuild the new machine (keep same name, domain, drive letter, ...) and all requirements (http://technet.microsoft.com/en-us/library/cc431377.aspx). 5# Install ConfigMgr. 6# Restore the backup (http://technet.microsoft.com/en-us/library/bb680456.aspx). To restore all package, you can use PreloadPkgOnSite.exe tool : http://www.microsoft.com/downloads/details.aspx?FamilyID=C36FCDA8-9336-4D44-9568-5530FF7635DD&displaylang=en Microsoft MVP - SCCM

Thanks for your response, Some other information : We have one virtual machine in Windows 2003 with SMS 2003 SP1. We have an other virtual machine in Windows 2003 with SQL Server 2000 . In this SQL , we have other database than SMS DB. We have File Server for Source Package. - Can we be sure that we can upgrade SQL 2000 to 2005 without interrupt the production ? - Is it possible to attach a SCCM 2007 Children Site to SMS 2003 parent site ? - Do you think it's not better to *create a New Server Windows 2003 with SMS 2003 like a children site *Let's replicate *Doing a in place upgrade of this Windows 2003 Children Site ? We want to be sure that we have any interrupt in the production during this upgrade .

It's not possible to attach ConfigMgr as a child site to SMS 2003 parent site, and also keep in mind that it's not supported to upgrade inplace Windows 2003 to Windows 2008 on the SMS 2003 server.Microsoft MVP - SCCM

Sorry i'am going too fast... I meant : - Create a new Windows 2003 Server with SMS 2003 and new server with SQL 2005 - Attache this SMS Site like a children to Parent ( production ) site; - Let's replicate - in place upgrade for this Windows 2003 Children site to SCCM 2007 - Create a new Windows 2008 Server and install SCCM 2007 R2 - Attach this site to Windows 2003 SCCM Site

Sorry i'am going too fast... I meant : - Create a new Windows 2003 Server with SMS 2003 and new server with SQL 2005 - Attache this SMS Site like a children to Parent ( production ) site; - Let's replicate - in place upgrade for this Windows 2003 Children site to SCCM 2007 - Create a new Windows 2008 Server and install SCCM 2007 R2 - Attach this site to Windows 2003 SCCM Site If you will use this method, so to migrate your site to ConfigMgr without interruption you should point clients to the child site code, and it takes time depending on the number of machines, and after the migration you should re-point clients to the ConfigMgr site ... !!!Microsoft MVP - SCCM

If i use this method : - Upgrade the SQL 2000 server to SQL 2005 SP3 - Inplace upgrade of SMS 2003 to SCCM 2007 - Install a new SCCM 2007 SP2 R2 with SQL 2008 R2 and add that as a child site (perform the replication as you described) - Change the parent/child order and let the data replica to the new site. What is the operation that i can do on the pc client ? THanks a lot,