"kobiianardo" <kobiianardo@newsgroup> wrote in message news:ea45c2f1-7b78-4452-b76b-82f1bdf4d063@newsgroup
> the question is the subject: we want all the computers to start up the
> same way (files, computer settings, apps, stuff-the-i-cant-imagine-but-
> will-matter-on-a-computer), the following are some contexts if you
> have any tips, thanks!
> im migrating from SBS2k3 on an old machine to a new machine with
> Server2008 enterprise. we dont have anyone with experience here. we
> have around 15 computers.
> old server: our domain controller, DHCP, DNS, and file storage thing,
> (and bunch of other stuff that we dont care for.)
> new server: we want this one to replace the old one, pretty much just
> file sharing. consider the following plans:
> Plan A - new domain:
> over the weekend, copy data files from old server, somehow copy all
> the user settings. make all the computers join the new domain. (this i
> think i can do except how to preserve the files)
> Plan B - old domain preserving:
> bring the new computer up as a DC to the old server, copy files, and
> make personal settings transfer, somehow yank out the old server and
> hope everything will work fine. (all we want from the migration is
> files + personal settings)
> Plan C - blank.
> Mainly asking about how to do Plan A, since that's the one we'll
> likely be doing.
There are a number of ways to do this. My main question is, with 15 users, why would you want to spend the time and additional money to move away from SBS? There are numerous features SBS provides that non-SBS does not. You also *must* (I use the term loosely) have two domain controllers if moving to regular windows. This is for fault tolerance. This is not a requirement for SBS.
Assuming SBS is handling your emails, what will you do with your user's emails? If you want to go with Exchange, that is an additional charge, and it is not cheap, compared to having it built-in with SBS. The last I looked, SBS 2008 Std including user licenses, is around $1500 for approx 15 users. I think you will get a much better administration and user experience with SBS 2008 Std Edition.
However, if you already have planned on doing this, this does require expertise knowledge of Windows and related experience. Below you will find my notes on 'moving away from SBS.'
Also, since this is related to SBS, it may have been better to post it in the SBS newsgroup/forum. I Cross-Posted this for you to the SBS newsgroup. Just check back here for responses, but when you respond, please use the "Reply-All" so it is sent to both newsgroups. If you do not have that feature with Google Groups, copy and paste the following into the Newsgroup list you want to send/post to:
Moving away from SBS:
SBS 2003 to Server 2008/Exchange 2007
Discusses the Windows Small Business Server 2003 R2 Transition Pack, as well as guidelines in moving from SBS http://social.technet.microsoft.com/...1-65720c1019f5
Microsoft Windows Small Business Server R2: Windows Small Business, Jul 11, 2006. [PDF about the Transition Pack, how to acquire it, etc]
The Windows Small Business Server 2003 R2 Transition Pack helps your business grow as your technology grows... http://www.microsoft.com/WindowsServ...ransition.mspx
The black hole of the transition pack - THE OFFICIAL BLOG OF THE ...SBS 2003 has a 'transition pack'. A method that you can upgrade from SBS ... Installed
the Transition pack on SBS SP1 Premium (running SQL but not ISA). ... http://msmvps.com/blogs/bradley/arch.../11/80849.aspx
The Official SBS Blog : Activation Loop After Completing the SBS ....[Today's tip comes to us from Damian Leibaschoff ]
We've seen a few cases now where a server is in an activation loop (activation never completes ... http://blogs.technet.com/sbs/archive...tion-pack.aspx
Replace SBS 2003 with Windows Server 2008 & Exchange 2007 http://social.technet.microsoft.com/...f-636bdbf13eda
If you don't want to purchase the pack, you can manually do it. Basically, here's the 30,000 foot view if you want to keep the same domain name:
1. Promoting a 2008 or 2003 server to a DC (installing DNS, DHCP, WINS, etc).
2. Installing a separate server for Exchange into the org.
3. Move mailboxes
4. If using SQL, installing a separate server for SQL and move the databases
5. Move any other apps over
6. Unplug the SBS
7. Move FSMO roles over
8. Manually remove SBS' Exchange instance out of the org
If you don't want to keep the same domain name, then you would install a fresh 2008 server, Exchange 2007 on another, etc. You can export/import the user accounts using LDIFDE or CSV method. Use Exmerge two-step, or PSTs to export/import mailboxes. You can manually re-target profiles with the new user account or use a third party profile tool.
There's a another migration method that you may have heard about through the grapevine, but it's not supported nor follows Microsoft legal compliance for SBS, so I won't mention it.
Don't forget, minimal recommendation is to have two DCs per domain. It's to your advantage.
How to deal with User's Profiles
As for users profiles, the easiest way is to manually disjoin, then join the machines to the new domain. Have the user logon with their new account, then logoff. This will create a local profile. Then logon as the domain admin, go into Computer Properties (Right click My Computer, properties, Advanced), then select User Settings (or Profiles), and you should see the profiles that currently exist. Select to copy the user's previous profile to the new profile, and adjusting permissions for the new user to use it.
You can also use the User State Migration Tool to migrate the profile. Windows 7 includes it but not the previous operating systems.
Description of the User State Migration Tool for Windows XP ...The User State Migration tool (USMT) includes the same functionality as the Files and Settings Transfer Wizard, but also permits administrators to fully .... http://support.microsoft.com/kb/321197
User State Migration Tool 3.0 - You can use Microsoft® Windows® User State Migration Tool (USMT) 3.0 to migrate user files and settings during large deployments of Microsoft Windows XP and ...
How Do I: User State Migration Tool?The User State Migration Tool (USMT) for Windows 7 is now part of the Windows Automated Installation Kit (AIK) and provides fast and flexible options to ... http://technet.microsoft.com/en-us/w.../dd572169.aspx
User State Migration Tool - Video - 3 min 14 sec - Mar 17, 2009. The User State Migration Tool (USMT) for Windows 7 is now part of the Windows Automated Installation Kit (AIK) and provides fast and flexible options ... http://technet.microsoft.com/windows/dd572169.aspx
Windows 7 Walkthrough: User State Migration Tool - Video http://www.microsoft.com/downloads/d...displaylang=en
Windows Easy Transfer for transferring from Windows XP (32 bit) to Windows 7 http://www.microsoft.com/downloads/d...displaylang=en
Download details: (Older Version 2.62) Windows User State Migration Tool (USMT) version ...Jul 22, 2006 ... Microsoft® Windows® User State Migration Tool (USMT) version 2.6.2 migrates user files and settings during large deployments of Windows 2000 ... http://www.microsoft.com/downloads/d...5-4B69B97DF7AE
This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.
Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution.
Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com
for regional support phone numbers.