Hi All, We are going to migrate from SMS 2003 SP3 to SCCM 2007 SP2. please let me know what and all issues will occur and what and all issues we have to face for this migration. few of them i noticed..if any other issues..please let me know. currently we 1 central site and 14 primary sites. and we are planing to move to sql cluster environment. 1) we have to migrate from sms 2003 to sccm2007 with out distrubing production environment (any inputs regarding this, which is the best way) 2) client migration (sms client to sccm client) in all user's desktop? please let me know is there any other issues will occur (need to face?) and is there any other features we can configure and use for better production environment compare to sms? please let me know the issue we will face from sms to sccm migration..as i need to prepare doc and submit to my lead.

Which route do you want to go? The inplace or side by side one: http://technet.microsoft.com/en-us/library/bb681075.aspx?

Hi, You have two choices 1) I-place upgrade after business hours 2) Side-by-side migration using the link provided by Torsten I prefer the Side-by-side, that allows you to install ConfigMgr. on new hardware. You will have time to test new packages, images etc without leaving any disturbing the production environment. Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

I want to go for side by side migration, as i cannot provide downtime, as it is 24/7 business.. if i go for side by side..what issue will occur genarally... and currently i have sms 2003 with sql 2005. can i install sccm 2007 sp2 on sql 2008 directly OR first i need to install sql 2005 and migrate to sql 2008? and if i install sql 2008 directly..is sms 2003 database will support in Sql 2008 for backup/recovery? please advice....

Hello - I have seen most of the huge corp clients go with I-place upgrade as there are lot of cost involvement (in side by side upgrades) to set up 1 central and 14 primary servers (obviously, in different geographical locations). But from risk perspective Side by Side upgrade is better approach. If you are going with I-place upgrade then please take care of below points 1. Try upgrades in test lab. 2. Always do TestDBUpgrade for DB compatibility before upgrades. 3. Keep two or three good backup (obviously) for primary servers. 4. All the inventory will get re synced so just monitor the back logs on the servers. 5. Complete the prerequisites 1 day before upgrade. 6. Etc…. as per your environment, criticality and SLA.Anoop C Nair

Thanks Anoop ,Torsten and kent.... we have a call with microsoft tomorrow..what and all questions we can ask them interms of SCCM 2007 migration...to clarify the things.. Thanks in advance.

OK sure. Best of Luck !! That is better as Microsoft can provide you the detailed case study depends upon your environment and requirement.Anoop C Nair

Can you suggest some queries interms of sccm 2007 migration which i can ask to microsoft people ?