Link to home
Start Free TrialLog in
Avatar of kdubendorf
kdubendorfFlag for United States of America

asked on

Migrate from Windows 2003 Server to SBS 2003???

I have an installation of a single Windows 2003 Server (Standard) that is out of disk space.  It serves about 15 ysers. I'm upgrading the disk system, removing the existing SATA drives and replacing them with a Adaptec RAID Card and larger SATA drives configured for RAID 10.   During this change out I'm looking to deploy Exchange 2003, so I'm seriously looking to move to SBS 2003.  I'm planning on keeping the domain and server name the same.   I doubt that I can migrate active directory to the new box, can this be done?   Is there anyway that I can reuse the existing user profiles on the XP Pro client computers?
ASKER CERTIFIED SOLUTION
Avatar of Lee W, MVP
Lee W, MVP
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of kdubendorf

ASKER

The problem is we're dealing with one server here.   So once I replace the disks the server / domain controller is gone unless I restore onto the new disk array.
I'll review the article in more depth.  I see why you recommended it.   I'll be back.
Think OUTSIDE the box.  (Sort of).  Get yourself a copy of Virtual Server, Virtual PC, VMWare, and install another 2003 DC (run it off a workstation).  Then you can rebuild your existing server with SBS.  Just remember to properly transfer FSMO roles and the Global Catalog before demoting and removing the original DC prior to the rebuild.
Got the Virtual Server and Installed 2003 on it.  Are there any instructions that you would recommend for transfering the FSMO and GC?  
Attempted to transfer the FSMO and GC but had an Active Directory Conflict.    New temporary server was R2 and kept getting messages telling me that the R2 Active Directory is incompatible with the R2 Active Directory.   Next time I'll do this it should save a lot of time.
You mean a message about Schema versions?  What exactly happened?  The schema message is normal - there's a second ADPREP that must be run on the R2 Second CD.