• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 396
  • Last Modified:

SBS 2003 migration to 2011 suggestions, part 2


I have opened the same question here before http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/Q_28017386.html , but that topic turned into discussion (which I appreciate very much!) about the common sense in my plan.

But as I am FORCED into doing it NOT PROPERLY, please, I ask this time only for technical details on how to proceed with the following. Please, do not discuss how and why my method is not good. Thanx.

The mission goal:
Migrate old SBS 2003 to new SBS 2011 on new hardware.
Migrate ONLY the following roles/parts:
- 40 users
- shared folders with permissions
Nothing else!

The users are NOT joined into domain (it was a failure of previous admin), so they only have 40 users in AD, and the same usernames/passwords on all 40 computers.
This part I will leave intact in this first step of migration. I will do full migration of users and move them all to domain LATER.

My main concerns:
since I am migrating really crappy setup system, I would like to migrate ONLY the needed roles, which are user SID's and shared folders.
Is it possible somehow to NOT migrate Exchange, SharePoint and WSUS (because I assume there is a lot of crap in old config)?

Again - I WILL start this migration this Friday, so I need tech support.
Andrej Pirman
Andrej Pirman
  • 3
1 Solution
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
To migrate user with SID you can use ADMT between forests

What do you plan for Exchange or Mailbox\PF data ?

- Rancy
Andrej PirmanAuthor Commented:
Both old and new are SBS servers.
The old is SBS 2003 and does not employ Exchange, WSUS nor SharePoint.

The new one is SBS 2011 and in the first step I only intend to replace old hardware to avoid failure. The important is that on Monday morning all 40 users would start working as before.

I would not migrate them into domain at this stage, because it is too messy and I would not finish from Saturday till Monday.
I will also configure Exchange later for all users on new server.
Andrej PirmanAuthor Commented:
I will withdraw this question, because it is not relevant to my case anymore. I decided to go with fresh install for many reasons.

But for the sake of my curiosity, I did clone the original server and did TEST migration from SBS 2003 to SBS 2011, but without Exchange and SharePoint (also without companyweb).

I followed this document:
First, I uninstalled Exchange from old SBS 2003, so it would not mess with migration. This procedure requested Disk 2 of original SBS 2003 installation to finish.

After old SBS 2003 was fully patched, I checked it many times with "dcdiag.exe" and "netdiag.exe". Repaired minor issues BEFORE i proceed with migration.

Then I ran new SBS 2011 installation in MIGRATION mode.

Then on new SBS 2011 I created NEW "Domain Admin" user, meanig other than defautl Administrator, because you must run SBS Migration Wizard with other user, not defautl Administrator. Don't ask me why.

User accounts were successfully replicated, FSMO roles too. The only step of approx. 12 steps of SBS 2011 Migration Wizard were:

- Move settings and data to the Destination Server
However, the migrated users, security groups, and distribution lists are not automatically displayed in the Windows SBS 2011 Standard Console. For information about how to make these items appear in the Windows SBS 2011 Standard Console, see http://technet.microsoft.com/en-us/library/gg563796.aspx 
BEFORE I ran this wizard, I went to new SBS 2011 Group Policy, which defines Password length and complexity and set NO complex passwords and minimum length of 4 characters, so to match weak password habits on old server.

- Move users' shared data
Only data and folders (with permissions) were copied, so I used this trick http://technet.microsoft.com/en-us/library/gg563797.aspx to copy SHARE settings and permissions over from old to new server.

I then prematurely FINISHED the migration wizard, telling it to take final steps.

Then used the ADSI Edit utility to delete the Enterprise Recipient Update Service, which will be recreated on new server http://technet.microsoft.com/en-us/library/gg563804.aspx 

Decomissioned old server with "dcpromo", did NOT select "This is the last domain server in domain", and after old SBS 2003 was just joined to domain, I moved it over to Workgroup.
Deleted all occurencies of OLD SBS from DNS in new one.

Then changed IP of new server with "Network Wizard" to match the old one, aded CNAME in DNS to manually route all requests for OLD server's NAME to new name...
And, guess what - Everything was working as expected!

True is, that I have had a dozen of Warnings and issues in Event Log, also few crashes of MMC on new server, but I am not sure it was related to migration itself.
Andrej PirmanAuthor Commented:
Found the answer myself, and noone else provided feedback worth rewarding.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now