Sun, Nov 8 2009 20:48
bradley
Migration Step Fourteen: It's moving time!
http://msmvps.com/blogs/bradley/archive/2009/11/07/just-a-reminder-of-all-of-the-key-migration-resources.aspx
Migrate settings and data to the new server. Follow the instructions on pages 28 through 70 in the Microsoft migration document.
Change where to store data on the Destination Server
Configure the network
Configure the Internet address and leave IPv6 enabled. If you disable it improperly or incorrectly, you will see numerous network issues, including Exchange failing to start. For more information see this blog post on the Microsoft Web site (http://blogs.technet.com/sbs/archive/2008/10/24/issues-after-disabling-ipv6-on-your-nic-on-sbs-2008.aspx ).
Migrate network settings
Migrate certificates
Migrate Exchange mailboxes and settings
Remove Internet connectors
Migrate POP3 connectors
Move Exchange Server public folders
Move the Offline Address Book
Move mailboxes
Enable circular logging on storage groups
Remove legacy Group Policy objects and logon settings
Remove old logon scripts
Remove old Group Policy objects
Migrate users' shared data
Configure a new shared volume on the Destination Server
Copy users' shared folders to the Destination Server
Copy additional shared folders to the Destination Server
Migrate the internal Web site
Steps performed on the Source Server
Steps performed on the Destination Server
Migrate fax data
Migrate user accounts and groups
Enable folder redirection on the Destination Server
Migrate SQL Server data
Install a new instance of SQL Server 2008
Migrate a SharePoint instance of SQL Server 2000 Standard
Migrate a SharePoint instance of SQL Server 2005 Workgroup
Migrate a SQL Server 2000 instance or SQL Server 2005 instance to SQL Server 2008
Specify SQL Server collation settings
Migrate Terminal Service licensing server
Okay that's not all of step 14.... so let's take this a bit at a time.
First off I'm going to add a drive to the newly built SBS 2008 so that we have a place for the Data drive.
Mikael Nystrom (www.thirdtier.net ) said the other day that when you add another drive, add additional drives via SCSI. Make the first drive an IDE drive. It allows you to hot add harddrives without rebooting the box.
You will have to go into computer management and convert the drive.
Also don't forget on the new server, just because the mouse and everything works, don't forget to install the HyperV integration:
Networking driver on 'SBS 2008' loaded but has a different version from the server. Server version 3.2 Client version 0.2 (Virtual machine ID ED1469AD-4443-436F-9BF6-E695AF0AA786). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.
In the event logs you can see that indicating that I have not.
Click OK and then it will want to boot the box.
Now on to moving the data from the old server to the new server:
On page 28 of the migration doc it talks about folder redirection. In my firm we don't do folder redirection because we train folks not to store stuff on the local harddrives
Configure folder redirection on the Destination Server
When the Windows SBS 2008 installation finishes, the users’ folder redirection data on the Destination Server is on drive C. If you use folder redirection on the Source Server or if you plan to start using folder redirection when you finish migrating to Windows SBS 2008, you should move the users’ redirected data to another partition or hard disk drive. For instructions, see Change where to store data on the Destination Server.
After you move the users’ redirected data, you should edit the Folder Redirection Group Policy object on the Destination Server to change the location of the users’ redirected data from the Source Server to the Destination Server. After you finish migrating user accounts and groups, you will enable folder redirection on the Destination Server.
On a production server you'll want to move the WSUS, the Data and the Exchange to other drives. Depending on how you set up servers, you may want multiple drives for this purpose. I'm going to be very simple for purposes of the test migration and not make multiple drives. On a real production server you'll want to slice and dice depending on your needs and storage space.
To change where to store data on the Destination Server
|
1. On the Migration Wizard Home page, click Change where to store data on the Destination Server, and then click Next.
2. If you do not want to change where to store data at this time, click Skip this task, and then click Next.
3. If you want to change where to store data, click each data type to start the Move Data Folders Wizard, and then follow the instructions in the wizard.
4. When you finish changing where to store data, return to the Migration Wizard, click Task Complete, and then click Next.
|
We're going to move the data locations....
So I'll choose to move all of this data over
Before we do this, we should backup the server
As a FYI if you start to move WSUS soon after ABC's Brothers and Sisters is on at 10:00 p.m., that's also the same time that the WSUS starts it's sync schedule.
So if you try to move the data location, it will say "oops sorry, I'm not going to let you"
Okay I'm impatient tonight so I stopped the WSUS sync and moved the WSUS data location.
So now we tick off "task completed" and go on to the next one
Filed under: Migration
![[There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not.]](http://www.sbslinks.com/images/headertop.png "There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not!")