Migrating to Small Business Server 2008
January 21st, 2009 Posted in Tech | No Comments »This is an account of my experiences in a fairly convoluted migration from SBS 2003 to SBS 2008.
Background
In our environment we have a Small Business Server 2003 running on a fairly beefy quad-core Xeon system and an additional Domain Controller running Server 2003 Standard. With the release of SBS 2008 and its system requirements coupled with potentially available hardware, our migration path was clear: the existing SBS 2003 hardware was the best choice.
Planning
Given the constraints of moving from SBS 2003 to SBS 2008 on the same hardware (i.e. no upgrade option), the best approach was to virtualise SBS 2003 and run it on VMware Server hosted on the Server 2003 DC while the migration was in progress.
After researching some of the possibilities for running SBS 2008, Server 2008 with the Hyper-V role installed was chosen to host a SBS 2008 virtual machine. Hyper-V Server was considered but due to the need to use software RAID on the host and lack of a local interface made it a non-starter.
Implementation
VMware Converter was installed on the Server 2003 DC and a Physical to Virtual (P2V) conversion was performed of the SBS 2003 machine. Once complete the physical computer was shutdown and the P2V instance was imported into VMware Server 2 which was installed on the additional DC also.
When the SBS 2003 VM was brought online, some minor glitches needed resolved. Running the Connect to the Internet wizard solved most of the issues.
To prepare the destination hardware, Server 2008 Standard was installed on the old physical server and the Hyper-V role configured. A virtual machine was configured and SBS 2008 installed on it using the migration mode answer file as outlined in the SBS migration document.
The above document was followed to perform the entire migration procedure. User shares were migrated, WSS2 companyweb was imported into the new internal website, our existing SSL certificate was moved, as were Exchange mailboxes and public folders.
Conclusion
Moving the existing SharePoint internal website to the new internal website was a fairly involved procedure, yet still a welcome one allowing us to move our site to WSS3.
The legwork involved in getting Exchange migrated was also somewhat frustrating given some problems I ran into with Invalid token errors (80090308) when trying to Move all Replicas of the Public Folders to the Destination server.
There was further frustration and uncertainty when removing Exchange 2003 using the SBS 2003 Setup Wizard which reached a less than clear conclusion when setup had seemingly ran its course:
0xc007041d - The service did not respond to the start or control request in a timely fashion. (EXIFS)
Facility: Microsoft Exchange Setup
ID no: c107041d
Microsoft Exchange Setup
I’m still unsure whether Exchange 2003 ever did remove itself properly from our Domain . . .
Otherwise I am extremely impressed with the ease most steps in the migration process could be performed and found the whole experience much less daunting than my initial reading of the subject.