Windows SBS 2003 to 2011 SBS Migration

Ok, so it looks like ony of my small clients is going to approve new hardware soon and they are currently on SBS 2003

I plan to migrate them to SBS 2011 using this awesome little gem

Now, my question is most likely simple but I would like to have everything covered as I never dealt with SBS that much as most of my work was done with full blown 2003/2008 etc.

Now, this client does not currently have Exchange so I obviously skip that task. I will be implementing exchange on the new SBS 2011 Std though. The current "mail" server uses MDaemon to relay email to local clients (ugh).

I also don't have any Fax data to migrate (skip as well)

So how much time am I looking at here for this migration? I will do the work in the evenings so no user disruption. This really appears to be rather straight forward. Any tips?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Will you be importing any mail into Exchange?
Only tips I recommend, don't skip any steps on the guide. No matter how small the step seems. Have your certificate ready to import and instructions laid out for that import process. Other than that, its straight forward with moving data. The actual process itself will take 4-5 hours. The migration of data, more/less depending on your amount of data.

Its very straight forward
dswope79Author Commented:
Yeah, I am sure I will import once the migration is complete and stable. So far it appears MDaemon pulls email from which assume is their provider

I assume this based on the logs

Mon 2012-04-02 17:36:36: ----------
Mon 2012-04-02 17:36:37: [-1:9193] MultiPOP collecting mail from ( for (Kelley White)
Mon 2012-04-02 17:36:37: [-1:9193] MultiPOP collected mail will be removed from remote host!
Mon 2012-04-02 17:36:37: [-1:9193] Attempting MultiPOP connection to [ : 110]
Mon 2012-04-02 17:36:37: [-1:9193] A-record resolution of [] in progress (DNS Server:
Mon 2012-04-02 17:36:37: [-1:9193] TTL=(35) A=[]
Mon 2012-04-02 17:36:37: [-1:9193] Attempting MultiPOP connection to [ : 110]
Mon 2012-04-02 17:36:37: [348:9193] Waiting for socket connection...
Mon 2012-04-02 17:36:37: [348:9193] Socket connection established
Mon 2012-04-02 17:36:37: [348:9193] Waiting for protocol initiation...
Mon 2012-04-02 17:36:37: [348:9193] +OK POP server ready H mius7
Mon 2012-04-02 17:36:37: [348:9193] USER
Mon 2012-04-02 17:36:37: [348:9193] +OK password required for user ""
Mon 2012-04-02 17:36:37: [348:9193] PASS ******
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Yes it looks like that, should be no problem. As long as you can get pst's, exchange will be happy.
Alan HardistyCo-OwnerCommented:
All my SBS 03 to SBS migrations have taken 3 days which is made up as follows:

Day 1 - Prepare SBS 03 server for migration by installing updates / patches and checking pre-requisites.  Build new server in migration mode and Migrate Mailboxes / Public Folders.
Day 2 - Continue with migration and then over night, migrate the data across.
Day 3 - Complete migration, kill Exchange on the old server, demote the server and remove from the LAN.

Without Exchange - you are probably looking at a minimum of 2 days - if you haven't done one before, I would suggest about 3 days - 4 possibly to make sure all is going well and you are not pushing yourself too hard.

The big factor will be the amount of data to migrate.  I have had some mailboxes that didn't finish migrating over night and that caused delays, but I changed the schedule and re-visited the following week (allowing the weekend for the mailboxes to migrate).
I completed, without mailbox migration, a complete SBS2003 to SBS2011 migration in about 12 hours. The domain had 25 users on it. This was with about 500GB of data. The initial push (install of the software, running updates, and configuration) took about 8 hours. The data migration and remappings took 3-4 hours. Naturally, I had the new server ready to go and the old server prepped and ready as well.

It is always a good idea to allow for extra time though, just in case.
dswope79Author Commented:
I am talking no more than 15-20 users and considering the current SBS 2003 sits on a single 200GB HDD with 80GB free. Users shared folders are currently 47GB in size, no Exchange.

So we are not talking about a huge migration here but I want to ensure this migration is as planned and carefully approached as I would a 1,000 user migration (dramatic I know).
Are you doing the work in the evening or weekend?
Alan HardistyCo-OwnerCommented:
I would have said 2 days tops then.
I don't blame you, and it is not dramatic. SBS can be very picky and "vocal" if not done right. Follow the guide, plane for 12-16 hours, no problems done! Dont forget to change firewall rules for Exchange and OWA.
dswope79Author Commented:
I will most likely do the work in the evening with no users on the network. Something like, Friday, Saturday, Sunday and be onsite first thing Monday to assist with any issues.
Alan HardistyCo-OwnerCommented:
Sounds perfect.  Less trouble when the users are not about to get in the way.

Plus - some of us Experts are about at weekends if you get stuck and need any help!
Oh, you will have plenty of time. Use scripts to migrate data so you don't have to babysit. You will be done by Saturday afternoon
dswope79Author Commented:
OK, everyone remember that this client is NOT currently utilizing Exchange so that entire task will be skipped.

1.   Health Checks on Small Business Server 2003 (make sure all patches applied), check  
      AD health with DCDIAG
2.   Configure SBS2003 for single NIC
3.   Run Migration Preparation tool on SBS2003 & Create Answer File
4.   Administrative User Creation

5.   Setting data locations (I will skip Exchange and SharePoint tasks, point shared folders to new location, user redirected docs to new location, update location as well)

6.   Configure the Network

*skip steps 7 and 8*
7.   Configure the Internet Address
8.   Migrate Exchange Mailboxes and Settings

9.   Remove Legacy Group Policies and Logon Settings
10.  Migrate users' Shared Data

*skip Step 11*
11.  Migrate Fax Data

12.  Migrate Users and Groups

*skip step 13*
13.  Uninstall Exchange 2003 from Small Business Server 2003

14.  Check Transfer of the 5 FSMO roles to SBS2011
15.  DCPROMO SBS 2003 server so it is no longer a domain controller and remove from network
Looks good - nice game plan!
When you migrate, it will pull the FSMO roles automatically. You don't have to demote the old one right away, you have 21 days. I would leave it on for a couple days, just to be sure everything is migrated.
dswope79Author Commented:
As far as any data copying, I have Robocopy on hand but perhaps if you happen to have specific scripts, I am all for it and please share.
I don't have them in front of me. But I use Robocopy GUI -

Simple and easy to create. It gives you a GUI to select the options you want, hit save, it creates the script. Just run it after that.
Alan HardistyCo-OwnerCommented:
Running the wizard on the SBS server will give you all the guidance you need for copying etc.  It suggests using robocopy and that is all I have ever used too.
It would be something like this - dont remember and I am at work rightnow -

robocopy "E:\test" \\server1\share /MIR /W:20 /R:15 /LOG: \\server2\share

Check the syntax to be certain
dswope79Author Commented:
Ugh! This Netgear Firewall FVS338 is the current DHCP server, that's gotta go
Yes, SBS2011 will pull the DHCP roll automatically. It will set it up for you.
dswope79Author Commented:
Yeah? I would think remove the DHCP roll from the Firewall, install the DHCP service. Set the scope, done

Then again, I could be slow minded and be clueless and the mnigration will ask if I want it to be the DHCP server? Otherwise my approach is to get DHCP off the firewall and move it to the DC
No, what I am saying is that SBS2011 will set it up for you automatically during the migration. You definitely want SBS2011 to manage it, not the firewall!
dswope79Author Commented:
Hey, i'm all for automation buddy..not arguing that at all. If it will identify the Netgear as the current DHCP server and make the switch to the DC and leave the netgear as the's all good.
haha - I wish it would make me a ham sandwich too about 3am 10 hours into a migration! ;-)
Alan HardistyCo-OwnerCommented:
If you can also lose the FVS338 out of the loop I would recommend it - we had nothing but trouble with them on our customer sites and are glad we switched to Draytek 2820n's.
dswope79Author Commented:
Got the authorization for the purchase of the new server today. I will be putting this plan into action soon.

Turns out they are currently using MDaemon for POP3 relay, going full Exchange after this goes to SBS 2011 so any recommendations there?

I priced out the SSL certificate through Comodo and SPAM filtering with Postini, network solutions houses the domain name.
I usually purchase through GoDaddy, and the clients I server, I have always recommend MXLogic, personal preference. I had some clients that had issues with Postini, but like I said, personal preference.

Just run the options to convert them into PST files, and you will have no issues.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
dswope79Author Commented:
Right now they have an email provider from

I have never heard of them, it's only 10 email accounts too.
Alan HardistyCo-OwnerCommented:
How much is your Comodo SSL Cert going to cost you?  If it is more than $60 per year then I would look elsewhere towards a GoDaddy Reseller account.

1and1 are a large email company - not one of my favourites, but pretty reliable apparently.

If the Postini spam filtering costs more than $239 for the first year and/or more than $99 the second year (current pricing), then I would consider switching to using internal Spam Filtering using Vamsoft ORF.

If you do opt for Postini - make sure they can reject emails destined for Invalid Recipients as if they can't, then you will end up on a Blacklist and may have problems sending emails.  Seen this happen too many times to want to use them myself.  Not sure if it is bad config or a lack of ability to Filter Invalid Recipients, but be warned.
dswope79Author Commented:
Comodo SSL cert for 3yrs is $705, Postini is $12 per account
Alan HardistyCo-OwnerCommented:
Ouch!  I buy a 3 year cert for $180 and all SBS servers I have are totally happy :)

Postini at $12 per account is good, but after 3 years you will have spent $360 vs the $239 for Vamsoft and if you don't renew, which isn't compulsory, you are saving money from year 2 onwards.  If you also add more users to your server - Vamsoft couldn't care less!
dswope79Author Commented:
Good advice, I can look into the alternatives. I will check into your suggestions tomorrow.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.