RE: Hardware Migration - tips?

Hello Customer,

Thank you for posting here.

According to your description, I understand that you want to migrate your
SBS 2003 to a new bigger hard disk. If I have misunderstood the problem,
please don't hesitate to let me know.

Based on my knowledge, there is no easy way to migrate SBS to new hardware.
Generally we have 3 methods to migrate SBS to new hardware:

Note: We do not support SBS migration with disk clone software.

1. A disaster recovery method

By this method, you need to manually restore Exchange data, SharePoint
Data, contents in Users shared folders. This method can complete rebuild
the same server on new machine.

2. FSMO Role transfer method

By this method, you need to use a standard version of Windows 2003 as
interim.

3. A third-party method

The steps on http://www.smallbizserver.net/DesktopDefault.aspx?tabid=99 are
detailed; however, we still recommend you do a backup prior to beginning.
In case the procedure fails, we can restore the System to the original
status. Since it is a third-party method, the suggestions on it are not
officially supported. As my personal experience, it is easy to follow and
efficient.

Meanwhile, the swing migration is also very famous, you can refer to:
http://www.sbsmigration.com/migration-projects.php#what-is-a-swing-migration

Now, I will list the detailed steps to 1 and 2 methods. Please refer to it.

I. Disaster Recovery

Backup: If you do not have a good backup of your original server, please
follow the backup steps to backup the server data.

1. Open "Exchange System Manager", navigate to "Servers"\<Server
Name>\"First Storage Group"\"Mailbox Store". Right-click it and choose
"Properties". In the properties window, click "database" tab. Write down
the path of the database file and streaming file. Also check the path of
the public folder database files.

2. Open ''Services'' console in ''Administrative Tools''. Stop ''Microsoft
Exchange Information Store'' service. If the exchange database files are
stored in the default path (c:\program files\Exchsrvr\mdbdata\), open
Windows Explorer, navigate to the Exchange database folder, and then save
the .edb files and .stm files to a folder on another disk partition or a
shared folder on a internal workstation

3. Open Windows Explorer. If "Users Shared Folders" is on C:\ drive, copy
it to another disk partition or a shared folder of on a internal
workstation.

4. If you are using the SBS 2003 built-in SharePoint site (Companyweb), you
may refer to the following KB article to move the database file:

827701 How to perform a disaster recovery operation of SharePoint Services
http://support.microsoft.com/?id=827701

5. Backup other data which you want to restore to the new installation.

Restore:

1. Insert SBS 2003 CD#1 into the CD driver. Boot the machine by using the
CD-Rom. Install SBS 2003 server. (Format original system drive)

2. Create new user accounts (duplicate the original accounts) by using Add
Users Wizard.

3. Open Services Console, stop "Microsoft Exchange Information Store"
service. Open "Exchange System Manager", navigate to "Servers"\<Server
Name>\"First Storage Group". Right-click it and choose "Properties". Select
the database folder. (The original database files should be copied to this
folder).

4. Open Exchange System Manager. Navigate to "Servers"\<Server Name>\"First
Storage Group"\"Mailbox Store". Right-click it and choose "Properties".
Click "Database" tab and check "This database can be overwritten by a
restore" option. Also check this option for "Public folder store".

5. Open Services console, start "Microsoft Exchange Information Store"
service. In Exchange System Manager console, right-click "Mailbox store"
and choose "Mount Store". Also mount the public folder store.

6. In Exchange System Manager console, expand "Mailbox Store". Right-click
"Mailboxes" folder and choose "Run Cleanup Agent". After doing this, you
will see the mailboxes with red crosses in the right panel. Right-click
each mailbox and choose "Reconnect". Connect the mailboxes to the current
user accounts.

7. Restore the contents in Users shared folders.

8. Follow the KB 827701 to restore the SharePoint site.

The above steps will help you reinstall the SBS 2003 server. To preserve
client user profiles and settings that was on the original domain to the
new SBS 2003 installation, a manual way is documented in the KB article:

314045 HOW TO: Restore a User Profile in Windows 2000
http://support.microsoft.com/?id=314045

Another way is to create a local profile, copy the original domain profile
to the local profile, and then let the "Setup Computer" wizard do the task
"map local profile to new domain profile" for you.

As long as you create your computer accounts using the server manager's "to
do list" you will be prompted to migrate profile information. When you join
the workstations to the domain by using the web site (ie
http://servername/connectcomputer) part of the process of joining the
domain will allow you to migrate user settings. However, to use this
method, you need to make sure that the profile you want to migrate from is
a local user profile (Not a previous domain profile):

1. Before joining the client to SBS 2K3 domain, create a local profile, and
then copy the old domain profile to a local profile.

2. Add the SBS Server into the network

3. Use the Setup Computer Wizard in SBS 2003 to join the (now) XP Pro
machines to the SBS domain: Server Management, Standard Management, Client
Computers, Set Up Client Computers.

4. On the client, access http//<Server name>/connectcomputer to bring up
the Setup Computer Wizard, it will then allow you to map domain user
accounts to local profiles on the machine thus preserving your profiles:
"Assign Users to this Computes and Migrate their Profiles".

5. You will Add a domain account to "Users assigned to this computer!/, and
then choose the existing local user profile in the "Current User Settings".
By Default, the value for "Current User Settings" is "None".

For the detailed steps, please refer to the following documents:

http://www.microsoft.com/technet/prodtechnol/sbs/2000/maintain/bkuprcvr.mspx

http://download.microsoft.com/download/1/1/6/11671e4d-fb21-489c-870f-db36fd2
1a7d2/SBS_MoveDataFolders.DOC

Backing Up and Restoring Windows Small Business Server 2003
http://www.microsoft.com/downloads/details.aspx?FamilyID=487736f8-f6f5-436d-
a82d-0c8d66e2a634&DisplayLang=en

II. FSMO transfer method

0. Make a full backup of the SBS 2003 server.

1. Use Exmerge.exe on the SBS 2003 server to export all mailboxes to PST
files. To do so, you can refer to the following articles:

174197 XADM: Microsoft Exchange Mailbox Merge Program (Exmerge.exe)
Information
http://support.microsoft.com/?id=174197

327304 HOW TO: Use ExMerge to Upgrade to Exchange 2000
http://support.microsoft.com/?id=327304

273642 ExMerge Does Not Work Unless You Have Receive As and Send As
Permissions
http://support.microsoft.com/?id=273642

2. In Outlook at a client computer, create PST files and move all public
folders to the PST files as a backup.

3. Install Windows 2003 on the new server box (you should use a retail
version of Windows 2003 CD, not the SBS CD #1) and join in the SBS domain

4. Run DCPromo and set it up as additional domain controller in the SBS
domain. More info how how to do this:

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechn
ol/sbs/maintain/addsrvrs.asp

5. Transfer the roles from the old SBS install to the new server. More info
on how to do this:

255690 HOW TO: View and Transfer FSMO Roles in the Graphical User Interface
http://support.microsoft.com/?id=255690

324801 HOW TO: View and Transfer FSMO Roles in Windows Server 2003
http://support.microsoft.com/?id=324801

255504 Using Ntdsutil.exe to Seize or Transfer FSMO Roles to a Domain
Controller
http://support.microsoft.com/?id=255504

6. Set the New Server as GC (Global Catalog Server). To set a DC as a GC,
you can follow the steps in the following MS Knowledge Base article:

816105 HOW TO: Create or Move a Global Catalog in Windows Server 2003
http://support.microsoft.com/?id=816105

7. Remove Exchange attributes (not mailbox) from all users by choose the
Exchange Task in "AD User and computers". If you find that you only have
the three items (Delete Mailbox, Move Mailbox and Enable Instant
messages.), you can just ignore them. This step is only to make sure to
remove all other attributes you have configured for users.

8. Stop the Information Store service on Old Server to take the databases
out of use.

9. Stop DHCP on SBS 2003, install DNS (make it AD Integrated so that it
will replicate all DNS information from the SBS server) and DHCP on the new
Windows 2003 server and then configure the DHCP scope the same as SBS 2003.

10. Configure the new server to point to itself for DNS. Configure all the
client computers to point to the new server as DNS. If you are using DHCP
to issue DNS server settings, you should configure your new DHCP server to
reflect the changes.

11. After making sure the clients can successfully, open AD User and
Computers, connect to the new server and remove the SBS 2003 server account
from the Domain Controllers container.

12. Take the old SBS server offline

13. Insert SBS 2003 Disc 1 on the new server to run SBS setup until
finished (be sure the organization information for Exchange is *exactly*
the same as on the old server)

14. Run through your To Do List to get on the client add packs, configure
Internet connection, etc.

15. Apply service packs and patches so the new server will be at the same
update level as the old server

16. Use the exmerge.exe tool to import the mailboxes from the PST files.
For public folders, you can import them in from the PST files in Outlook at
the client side.

17. Use the backup restore procedure for Sharepoint service to move the
content database from old SBS 2K3 to new SBS 2k3. You can follow this
article

829112 How to back up and restore http://companyweb data in Windows Small
http://support.microsoft.com/?id=829112

If you have further questions or concerns, please feel free to let me know.

Thanks and have a nice day!

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Date: Wed, 10 Oct 2007 17:28:49 +0100
| From: Neil Rashbrook <neil@xxxxxxxxxxxxxxx>
| User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6)
Gecko/20040113 Netscape7/7.05
| X-Accept-Language: en-gb, en, en-us
| MIME-Version: 1.0
| Subject: Hardware Migration - tips?
| Content-Type: text/plain; charset=us-ascii; format=flowed
| Content-Transfer-Encoding: 7bit
| Message-ID: <OVkRlq1CIHA.4584@xxxxxxxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.windows.server.sbs
| NNTP-Posting-Host: parkwaycs-218.adsl.newnet.co.uk 80.175.250.218
| Lines: 1
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:68492
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| I want to migrate an SBS 2003 installation from a 72GB disk to a 360GB
| disk. Unfortunately my disk cloning software doesn't seem to like doing
| this. I suppose I could treat it as a disaster recovery, and do OBDR
| from the tape backup, but I'm sure there must be an easier way? Can I
| install a minimal system onto the 360GB disk, then XCOPY the files, then
| do a restore of the system state to complete the migration?
|

.

Relevant Pages

  • RE: need to migrate a older win 2003 srvr sbs to newer one
    ... as I assume I should reading upon Windows Server 2003 inside out book. ... there are three method to move the SBS 2k3 to new ... Also check the path of the public folder database ... Another way is to create a local profile, ...
    (microsoft.public.windows.server.migration)
  • RE: Strange problems after move to new machine
    ... If you do not have a good backup of your original server, ... Also check the path of the public folder database ... If you are using the SBS 2003 built-in SharePoint site, ... Another way is to create a local profile, ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS2003 changed hardware
    ... For your situation, the old server hardware has failed, we only have to do ... the Disaster Recovery of SBS if you have full backup of your SBS. ... Another way is to create a local profile, ...
    (microsoft.public.windows.server.sbs)
  • Re: Newbie with a smallbiz2000 installation, check my config?
    ... profile path under Documents & Settings. ... It first tries to create a folder ... folders from a user's profile to a location on your server. ... Chad A. Gross - SBS MVP ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Move SBS 2003 to a new server
    ... there are three method to move the SBS 2k3 to new hardware. ... If you do not have a good backup of your original server, please follow the backup steps to backup the server data. ... Also check the path of the public folder database files. ... Another way is to create a local profile, copy the original domain profile to the local profile, and then let the "Setup Computer" ...
    (microsoft.public.backoffice.smallbiz)
Loading