RE: SBS 2003 to 2011
I have done two SBS2003 -- SBS2011 swings via the sbsmigration method (17 users at one site, 55 at the other) and highly recommend this method. If unsure of the inherited SBS2003 environment the new domain method might be the better way. Either way it's a lot of work, one of them has you disjoining/rejoining machines and re-creating user accounts, groups and passwords, etc. the other has you making sure the source environment is sound enough to do the swing. Dave -Original Message- From: Greg Sweers [mailto:gswe...@acts360.com] Sent: Thursday, July 05, 2012 4:10 PM To: NT System Admin Issues Cc: jmajorow...@gmail.com Subject: RE: SBS 2003 to 2011 http://www.networkmigrationworkbook.com/ We have used his and Jeff Middleton to come up with our own checklist that varies client to client, but the majority of it is sound. We are doing less and less of this as we are migrating our clients to cloud solutions... (Okay so they are really just hosted solutions)...s. Cloud gets them excited. Our last several SBS Migrations had literally zero downtime to our customer and we completed it faster than any other migration strategies we used before. Looks like I wont be doing much more of the SBS migrations going forward though with the latest from MS. Greg Sweers CEO ACTS360.com P.O. Box 1193 Brandon, FL 33509 813-657-0849 Office 813-758-6850 Cell 813-341-1270 Fax -Original Message- From: jesse-r...@wi.rr.com [mailto:jesse-r...@wi.rr.com] Sent: Thursday, July 05, 2012 6:39 PM To: NT System Admin Issues Cc: jmajorow...@gmail.com Subject: Re: SBS 2003 to 2011 Would you be willing to share that set of instructions you already came up with, privately? Understanble if you rather not... Original Message: - From: Jim Majorowicz jmajorow...@gmail.com Date: Thu, 5 Jul 2012 12:28:39 -0700 To: ntsysadmin@lyris.sunbelt-software.com Subject: Re: SBS 2003 to 2011 We've taken to using the New Domain method for our last 4 conversions, the last for an office of 18 users. So much so, that we've worked out a pretty good set of instructions for the cutovers. Even Jeff's SBSMIGRATION method has it's drawbacks. No matter what method you use, make your own set of checklists. That way you've got everything covered. On Wed, Jul 4, 2012 at 9:18 AM, Jesse Rink jesse-r...@wi.rr.com wrote: 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 it's 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, it'd 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 don't 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 I'm 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. I've heard so many horror stories about the Microsoft method that I'm very leary about doing it (this is just one example of MANY issues like this I've 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
Re: SBS 2003 to 2011
We've taken to using the New Domain method for our last 4 conversions, the last for an office of 18 users. So much so, that we've worked out a pretty good set of instructions for the cutovers. Even Jeff's SBSMIGRATION method has it's drawbacks. No matter what method you use, make your own set of checklists. That way you've got everything covered. On Wed, Jul 4, 2012 at 9:18 AM, Jesse Rink jesse-r...@wi.rr.com wrote: 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 it’s 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, it’d 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 don’t 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 I’m 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… I’ve heard so many horror stories about the Microsoft method that I’m very leary about doing it (this is just one example of MANY issues like this I’ve 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 listmana...@lyris.sunbeltsoftware.com 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 listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
Re: SBS 2003 to 2011
Would you be willing to share that set of instructions you already came up with, privately? Understanble if you rather not... Original Message: - From: Jim Majorowicz jmajorow...@gmail.com Date: Thu, 5 Jul 2012 12:28:39 -0700 To: ntsysadmin@lyris.sunbelt-software.com Subject: Re: SBS 2003 to 2011 We've taken to using the New Domain method for our last 4 conversions, the last for an office of 18 users. So much so, that we've worked out a pretty good set of instructions for the cutovers. Even Jeff's SBSMIGRATION method has it's drawbacks. No matter what method you use, make your own set of checklists. That way you've got everything covered. On Wed, Jul 4, 2012 at 9:18 AM, Jesse Rink jesse-r...@wi.rr.com wrote: 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 listmana...@lyris.sunbeltsoftware.com 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 listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin mail2web.com What can On Demand Business Solutions do for you? http://link.mail2web.com/Business/SharePoint ~ 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 listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
RE: SBS 2003 to 2011
http://www.networkmigrationworkbook.com/ We have used his and Jeff Middleton to come up with our own checklist that varies client to client, but the majority of it is sound. We are doing less and less of this as we are migrating our clients to cloud solutions... (Okay so they are really just hosted solutions)...s. Cloud gets them excited. Our last several SBS Migrations had literally zero downtime to our customer and we completed it faster than any other migration strategies we used before. Looks like I wont be doing much more of the SBS migrations going forward though with the latest from MS. Greg Sweers CEO ACTS360.com P.O. Box 1193 Brandon, FL 33509 813-657-0849 Office 813-758-6850 Cell 813-341-1270 Fax -Original Message- From: jesse-r...@wi.rr.com [mailto:jesse-r...@wi.rr.com] Sent: Thursday, July 05, 2012 6:39 PM To: NT System Admin Issues Cc: jmajorow...@gmail.com Subject: Re: SBS 2003 to 2011 Would you be willing to share that set of instructions you already came up with, privately? Understanble if you rather not... Original Message: - From: Jim Majorowicz jmajorow...@gmail.com Date: Thu, 5 Jul 2012 12:28:39 -0700 To: ntsysadmin@lyris.sunbelt-software.com Subject: Re: SBS 2003 to 2011 We've taken to using the New Domain method for our last 4 conversions, the last for an office of 18 users. So much so, that we've worked out a pretty good set of instructions for the cutovers. Even Jeff's SBSMIGRATION method has it's drawbacks. No matter what method you use, make your own set of checklists. That way you've got everything covered. On Wed, Jul 4, 2012 at 9:18 AM, Jesse Rink jesse-r...@wi.rr.com wrote: 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 it's 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, it'd 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 don't 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 I'm 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. I've heard so many horror stories about the Microsoft method that I'm very leary about doing it (this is just one example of MANY issues like this I've 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 listmana...@lyris.sunbeltsoftware.com 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 listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin mail2web.com
RE: SBS 2003 to 2011
Buy the migration pack from sbsmigration.com. Seriously. And no, I don’t get a cut. From: Jesse Rink [mailto:jesse-r...@wi.rr.com] Sent: Wednesday, July 04, 2012 12:19 PM To: NT System Admin Issues Subject: 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 it’s 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, it’d 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 don’t 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 I’m 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… I’ve heard so many horror stories about the Microsoft method that I’m very leary about doing it (this is just one example of MANY issues like this I’ve 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 listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com 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 listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
RE: SBS 2003 to 2011
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:g...@enter.it] 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:jesse-r...@wi.rr.com] 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 listmana...@lyris.sunbeltsoftware.com 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 listmana...@lyris.sunbeltsoftware.com 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 listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
RE: SBS 2003 to 2011
Because he's tested out pretty much every eventuality and is there for almost immediate support. From: HELP_PC [mailto:g...@enter.it] Sent: Wednesday, July 04, 2012 1:21 PM To: NT System Admin Issues Subject: R: SBS 2003 to 2011 Michael Why do you prefer the Jeff's method ? TIA Guido Elia HELPPC - HELPPC SERVICE Da: Michael B. Smith [mailto:mich...@smithcons.com]mailto:[mailto:mich...@smithcons.com] Inviato: mercoledì 4 luglio 2012 19.05 A: NT System Admin Issues Oggetto: RE: SBS 2003 to 2011 Buy the migration pack from sbsmigration.com. Seriously. And no, I don't get a cut. From: Jesse Rink [mailto:jesse-r...@wi.rr.com]mailto:[mailto:jesse-r...@wi.rr.com] Sent: Wednesday, July 04, 2012 12:19 PM To: NT System Admin Issues Subject: 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 it's 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, it'd 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 don't 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 I'm 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... I've heard so many horror stories about the Microsoft method that I'm very leary about doing it (this is just one example of MANY issues like this I've 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 listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com 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 listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com 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 listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com 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 listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
RE: SBS 2003 to 2011
I have done the migration per Microsoft's instructions and would never do it again. Especially if you only have 10 users. Michael Walker Senior Network Engineer Citrus Valley Health Partners 140 W. College Street, Covina, CA 91723 Phone/Fax/Pager: (888) 299-6882 mwal...@mail.cvhp.orgmailto:mwal...@mail.cvhp.org From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Wednesday, July 04, 2012 11:37 AM To: NT System Admin Issues Subject: RE: SBS 2003 to 2011 Because he's tested out pretty much every eventuality and is there for almost immediate support. From: HELP_PC [mailto:g...@enter.it]mailto:[mailto:g...@enter.it] Sent: Wednesday, July 04, 2012 1:21 PM To: NT System Admin Issues Subject: R: SBS 2003 to 2011 Michael Why do you prefer the Jeff's method ? TIA Guido Elia HELPPC - HELPPC SERVICE Da: Michael B. Smith [mailto:mich...@smithcons.com]mailto:[mailto:mich...@smithcons.com] Inviato: mercoledì 4 luglio 2012 19.05 A: NT System Admin Issues Oggetto: RE: SBS 2003 to 2011 Buy the migration pack from sbsmigration.com. Seriously. And no, I don't get a cut. From: Jesse Rink [mailto:jesse-r...@wi.rr.com]mailto:[mailto:jesse-r...@wi.rr.com] Sent: Wednesday, July 04, 2012 12:19 PM To: NT System Admin Issues Subject: 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 it's 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, it'd 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 don't 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 I'm 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... I've heard so many horror stories about the Microsoft method that I'm very leary about doing it (this is just one example of MANY issues like this I've 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 listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com 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 listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com 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 listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http
Re: SBS 2003 to 2011
For 10 users, I am in this camp also. Even more so if I didn't set up the original environment and inherited it from someone else. On Wed, Jul 4, 2012 at 8:35 PM, James Hill falc...@gmail.com wrote: I like the clean install method for small sites like this. With a larger site the migration makes more sense imo. ** ** James. ** ** *From:* Jesse Rink [mailto:jesse-r...@wi.rr.com] *Sent:* Thursday, 5 July 2012 2:19 AM *To:* NT System Admin Issues *Subject:* 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 it’s 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, it’d 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 don’t 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 I’m 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… I’ve heard so many horror stories about the Microsoft method that I’m very leary about doing it (this is just one example of MANY issues like this I’ve 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 listmana...@lyris.sunbeltsoftware.com 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 listmana...@lyris.sunbeltsoftware.com 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 listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
