Re: Migrating sbs 2003 to sbs 2008
- From: "Charlie Russel - MVP" <charlie@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 4 Jan 2009 09:28:20 -0800
A perfectly legitimate choice. But for many, it would end up losing many settings, and creating pain. For others, not a huge issue. But I'd be very careful about documenting the current situation carefully and thoroughly, in case something gets missed when you recreate.
--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel
"jaseinatl" <jaseinatl@xxxxxxxxx> wrote in message news:2408cce1-22e1-4443-bae0-53cecc53088a@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
My issue with following the migration steps is that I didn't want to
copy all of the errors and misc. garbage in my Active Directory to my
new server. I started completely from scratch and it took about two
hours to install and configure.
Here are the steps I took:
* Setup SBS2008 with an answer file (piece of cake)
* Did my updates, solved some install issues...nothing difficult
* Created new user accounts for each user and assigned them to the
User with Admin Links group--not because they will do any
administration, but because they want to be able to install printers,
for example and they aren't worried about security.
From each workstation:
* login as the primary user and launch Outlook 2007
* Export the root mail file and subfolders to a .pst file on C:
\Profiles\{username} *
* logged off
* logged in as the local Administrator
* Created a new local user
* assigned new local user to local Administrator group
* logged off
* logged in as new local user (to setup the user profile only)
* logged off
* logged in as local Administrator.
* copied all files in C:/Documents and Settings/{username}/ --
except ntuser.dat and ntanything files
* pasted those files to the new local user profile, replacing anything
that was there.
* left the domain, joined a workgroup
* shut down the PC
When all 5 workstations were done, I disconnected my existing server
from the switch, and connected my new server.
Now, again, from each workstation:
* Turn the PC ON (it gets an IP address from the new server using
DHCP even though it's assigned to a workgroup)
* Login as local Administrator
* launch a browser and type //connect
* follow the instructions to launch the application
* When it asks if I am installing for me or for others, select others
and assign the new local profile you created to the appropriate new
user account
* Let it reboot a couple of times
* Login to the new domain
* Launch Outlook and import your PST file.
DONE.
Works like a charm with the exception of printers. I just manually
assigned network printers since my server doesn't want to communcate
with them for some reason.
I did it minutes before folks arrived in the office and didn't have
any problems. My total down time was about 30 minutes.
Just my input. It seems so much easier than troublshooting the mess
that I inherited on a 512K PowerEdge SC430...blech....
jase
.
- References:
- Migrating sbs 2003 to sbs 2008
- From: Firestone
- Re: Migrating sbs 2003 to sbs 2008
- From: Charlie Russel - MVP
- Re: Migrating sbs 2003 to sbs 2008
- From: Iamnotno6
- Re: Migrating sbs 2003 to sbs 2008
- From: Charlie Russel - MVP
- Re: Migrating sbs 2003 to sbs 2008
- From: jaseinatl
- Migrating sbs 2003 to sbs 2008
- Prev by Date: Re: Terminal Server - alternatives
- Next by Date: Re: Terminal Server - alternatives
- Previous by thread: Re: Migrating sbs 2003 to sbs 2008
- Next by thread: Re: Migrating sbs 2003 to sbs 2008
- Index(es):
Relevant Pages
|
