Solved

Migrating SBS 2003 to a new SBS 2003 installation

Posted on 2011-03-22
5
300 Views
Last Modified: 2012-05-11
Hi, I have a SBS 2003 server (partially installed - no exchange server). There is an SQL server with an instance running.

AD is existing in that server and everyone (win xp clients) login daily. Shared folders and some folder redirections.

I would like to re-install SBS 2003 and enable exchange server. With the new physical server, I want to however retain the AD from the old server and also the SQL server instance. Otherwise, the rest can be managed such as Shared Folders.

Can someone advise how best to approach this?
0
Comment
Question by:binele
  • 2
  • 2
5 Comments
 
LVL 22

Expert Comment

by:Larry Struckmeyer MVP
ID: 35188531
SBS allows for reinstalling the included application from Add Remove.  If there is any reason you can't do that, I recommend a swing migration. Keeps the same domain, the same AD, the same server name and the same IP, moves all the data, shares and permissions with virtually no down time, and no loss of anything should you have to start over.  And you get one of the most experienced SBS MVP's to hold your hand.

www.sbsmigration.com
0
 
LVL 57

Expert Comment

by:Cliff Galiher
ID: 35211661
Since it sounds like you are moving to new hardware (you mentioned a new physical server in your question) I'd definitely recommend a swing migration. This will ensure you preserve the "personal" stuff (AD, files, etc) but also have a clean install with stable components which other bare-metal transition methods may not provide.

-Cliff
0
 

Author Comment

by:binele
ID: 35211711
Is this the correct one?

Fundamentally, the current "SBS" server ... even though it says it's an SBS, there's no add exchange. No SBS manager etc.

 Swing
0
 

Author Comment

by:binele
ID: 35211712
By the way, what will this do? Is this like an executable which will take care of everything?
0
 
LVL 57

Accepted Solution

by:
Cliff Galiher earned 500 total points
ID: 35211748
I'd get the SBS 2003 to SBS 2003 kit even though you don't have Exchange. SBS has certain AD restrictions that the SBS-specific kit will walk you through. You can simply skip exchange-related steps. Plus it comes with 90 days of support so, since you are in a rather unique situation, you can get some extra help when you run into unique stoppages.

No, it is not an executable. It is a kit. It is documentation, strategy, and a set of tools to complete the job. But no migration, as complex as they are, can be *completely* automated, so this provides an iterative process to get you to a new platform while preserving the important stuff in a systematic way that protects your existing infrastructure.

-Cliff
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
This article runs through the process of deploying a single EXE application selectively to a group of user.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

831 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question