<div>
The migration preparation tool is not designed to be used on a standard Server 2003. &nbsp;It is for migrating from a SMALL BUSINESS SERVER (either 2003 or 2008).<br />
<br />
You cannot do an automated migration from a standard server to SBS 2011.<br />
<br />
Jeff<br />
TechSoEasy
</div>


<div>
Hmm. I was able to complete the process when I chose not to install the updates. The new server joins the domain but no files get transfered. I should be able to manually migrate shouldn't I? <br />
<br />
Run dcpromo and a few others. I found a guide for server migration bit left it at home
</div>


<div>
I suggest that you do NOT join an SBS to a current domain. &nbsp;It would be way complicated to make that scenario work because the SBS must be the holder of all FSMO roles and be the root of the domain forest.<br />
<br />
What exactly is on your current server? &nbsp;How many users? &nbsp;Computers?<br />
<br />
Do you have Exchange or SQL?<br />
<br />
It would probably be best if you just migrated manually. &nbsp;Set up the SBS the way it is supposed to be done on it's own NEW domain. <br />
(follow this guide: &nbsp;<a href="http://go.microsoft.com/fwlink/?LinkId=212765" rel="ugc">http://go.microsoft.com/fwlink/?LinkId=212765</a>)<br />
<br />
Then if you don't have Exchange or SQL on your current server, manually add all your users and computers to the new SBS Domain and move over your data files.<br />
<br />
Jeff<br />
TechSoEasy<br />
<br />

</div>


<div>
The server is a dell pe from 06 with about 35 computers and 50 users. No exchange or SQL. The new server will have exchange. I think your right the new server would be easier to just migrate manually. I will read the M$ article. Thanks.
</div>


<div>
If all you had was a domain controller/file server then you should easily be able to migrate manually.<br />
<br />
Set up your SBS on a separate domain and IP Subnet. &nbsp;<br />
Turn off the DHCP server you are currently using, to allow the SBS to provide DHCP.<br />
<br />
Then, go to a workstation and log in as the local administrator renew IP settings and then run <a href="http://connect" rel="ugc">http://connect</a>&nbsp;to run the Connection Wizard to get it joined to the new domain.<br />
<br />
The previous user's profile should migrate over via this process as long as you assign that user during the Connection Wizard process.<br />
<br />
If this is successful, then continue with the other workstations.<br />
<br />
If there are problems migrating the local profiles (usually caused by permissions issues), then you can use the free version of ForensIT's migration tool: &nbsp;<a href="http://www.forensit.com/domain-migration.html" rel="ugc">http://www.forensit.com/domain-migration.html</a><br />
<br />
Jeff<br />
TechSoEasy
</div>


<div>
well i was able to get the new server to join the domain. but I can't seem to export the users info over. What I ended up doing was demoting the new DC and re-installing with a new domain. The issue now is I can't get the clients to join the domain. <a href="http://connect" rel="ugc">http://connect</a>&nbsp;does not work nor does the portable media method. I get errors each time even with the .net 4 framework update. <br />
<br />
So now i get time out errors. <br />
The error was: &quot;This operation returned because the timeout period expired.&quot;<br />
(error code 0x000005B4 ERROR_TIMEOUT)<br />
<br />
I have already attempted to resolve with:<br />
<a href="http://support.microsoft.com/kb/331072" rel="ugc nofollow">http://support.microsoft.com/kb/331072</a>&nbsp;these steps.<br />
the DNS address on the client (VISTA) is that of the server and the only thing I can think of is the old server is still on the network and is the DHCP server. I think I need to take that down before I can get it to join. But I am not sure. I have yet to run netdiag /fix but I think that might help too.
</div>


<div>
&quot; the only thing I can think of is the old server is still on the network and is the DHCP server.&quot;<br />
<br />
Absolutely that's a problem.<br />
<br />
You want your SBS to be the DHCP Server. &nbsp;It sets up DHCP automatically.<br />
<br />
You really need to follow the documentation for deploying an SBS environment. &nbsp;If this is your first time using SBS, and you didn't carefully follow the documentation, you may want to start over with it.<br />
<br />
You'll find that here: &nbsp;<a href="http://sbsurl.com/install11" rel="ugc">http://sbsurl.com/install11</a><br />
<br />
Jeff<br />
TechSoEasy<br />

</div>


<div>
I would be curious if you will have problems in the next few weeks as the SBS finds out it is not the holder of the FSMO roles. &nbsp;I'd suspect you will.<br />
<br />
Jeff<br />
TechSoEasy
</div>


<div>
<div class="content wysiwyg-content">
Source Server: windows 2003 R2 standard 32 bit<br />
destination server: SBS 2011 64 bit<br />
<br />
on the source server i was able to run the migration preparation tool with success. The installation was not successful so I ran it again and now it is hanging on the expanding files segment. Its really odd. I will post more info if needed tomorrow.<br />
<br />
I did elect to install updates during installation. 
</div>
</div>


Source Server: windows 2003 R2 standard 32 bit
destination server: SBS 2011 64 bit

on the source server i was able to run the migration preparation tool with success. The installation was not successful so I ran it again and now it is hanging on the expanding files segment. Its really odd. I will post more info if needed tomorrow.

I did elect to install updates during installation. 

standard server to sbs 2011

Small Business Server (SBS) is a line of server operating systems targeted at small businesses by bundling the operating system with a number of other Microsoft products that would normally need to be purchased or licensed separately. The most notable inclusions are Exchange, SQL Server, SharePoint and ISA/TMG (Microsoft's firewall and proxy server).

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

Servers are computing devices that are similar to desktop computers in that they have the same basic components, but are significantly different in size, configuration and purpose. Servers are usually accessed over a network, and many run unattended, without a computer monitor, input device, audio hardware or USB interfaces. Many servers do not have a graphical user interface (GUI), and are configured and managed remotely. Servers typically include hardware redundancy such as dual power supplies, RAID disk systems, and ECC memory, along with extensive pre-boot memory testing and verification. Critical components might be hot swappable, and to guard against overheating, servers might have more powerful fans or use water cooling.