Ive just read a lot of people complaining with the MS migration method and nearly all of them say, I wish I had done a clean install instead by the time the headaches end. No AS400 and very few 3rd party applications, etc. A colleague of mine did the MS method awhile back and had nothing but problems. A 1 day customer visit turned into 4-5 days Ive no interest in that, lol.
From: HELP_PC [mailto:[email protected]] Sent: Wednesday, July 04, 2012 12:14 PM To: NT System Admin Issues Subject: R: SBS 2003 to 2011 Probably good if you dont have any third party software like AS400 connections or other to recreate. The horror story looks to me exaggerate and probably due to the will to skip some MS advices Guido Elia HELPPC - HELPPC SERVICE _____ Da: Jesse Rink [mailto:[email protected]] Inviato: mercoledì 4 luglio 2012 18.19 A: NT System Admin Issues Oggetto: SBS 2003 to 2011 Customer purchased a brand new server to replacing aging SBS 2003 box. I have been going through the Microsoft SBS 2003 -> SBS 2011 migration document and its very lengthy and seems time consuming. I have also read a LOT of horror stories for this migration process and have a colleague who went through it a few months back and said it was awful. It seems like, based on the problems people face when attempting the migration process, itd be easier, and take FAR fewer hours, to just set the new SBS 2011 box up as a new domain by itself. This way I dont even have to touch the old SBS 2003 server at all (even upgrading it with all the required service packs and patches for the MS migration process might take hours, geez). So Im thinking 1. Build new SBS 2011 physical server and setup new domain. 2. Setup new Sonic Wall firewall for internet access (replaces ISA 2004) 3. Login to each of the 9-10 user machines/laptops as the user and . a. Backup their Exchange email to a PST file b. Document mapped drives and locations c. Backup their internet Favorites d. what else might I be missing here? 4. Begin copying over files/data from various network shares/folders from SBS 2003 server to SBS 2011 server and re-create folder shares, setup NTFS permissions, etc. 5. Re-create each of the 9-10 user accounts in the new SBS 2011 domain 6. Un-join each of the 9-10 user machines/laptops from old SBS 2003 domain 7. Join each of the 9-10 user machines/laptops to the new SBS 2011 domain 8. Login to each of the 9-10 user machines/laptops as the user and . a. Import their PST file into the SBS 2011 server b. Re-create mapped drives c. Restore Internet Favorites d. what else might I be missing here? 9. Re-install GFI anti-spam software on SBS 2011 server (was previously installed on SBS 2003) 10. They have 3 member-servers running 2008. I would also need to un-join those from the SBS 2003 domain and join them to the new SBS 2011 domain. 11. Missing anything else? Seems like a workable plan which I can do over a Friday/Saturday Ive heard so many horror stories about the Microsoft method that Im very leary about doing it (this is just one example of MANY issues like this Ive read about: http://www.jephens.com/2011/07/29/upgrading-sbs-2003-to-sbs-2011/) In my scenario of just building a new domain, am I missing anything in my steps 1-12? Thanks J ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
