RE: need to migrate a older win 2003 srvr sbs to newer one
- From: Harry Downs <HarryDowns@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 7 Sep 2006 22:51:01 -0700
Yes and I apologize for mentioning the settings, any file and data
structures, use profiles etc probably even the sid. I beleive I got the sid
procedure nailed down, but basically I wantt oat least save some time
recreating all of this over. I plan to review data , settings etc prior to
doingthis and I wil force client to make full backup of system. prior to this
next big phase. know better there. Should i be spending some needed time
as I assume I should reading upon Windows Server 2003 inside out book . I
willstart again tomorrow waiting on my wife's day surgerey on her foot, like
I am really goingto concentrate there. anyway thank you for the excellent
feedback.
"Vincent Xu [MSFT]" wrote:
Hi,.
Thanks for posting here.
As I understand from your post message, you want to know how to move your
existing SBS 2k3 server to another computer with new hardware. If I am off
base, please do not hesitate to let me know.
Based on my research, there are three method to move the SBS 2k3 to new
hardware. I listed them as following as well as their main features.
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.
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 ''''Properteis''''. 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 dabase 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 us know.
Thanks for your time and I look forward to hearing from you.
Best regards,
Vincent Xu
Microsoft Online Partner Support
======================================================
Get Secure! - www.microsoft.com/security
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================
--------------------
microsoft.public.windows.server.migration:24996Thread-Topic: need to migrate a older win 2003 srvr sbs to newer one
thread-index: AcbShVpX9lQBy8J7Rmuti/bG/JsSIg==
X-WBNR-Posting-Host: 24.195.153.35
From: =?Utf-8?B?SGFycnkgRG93bnM=?= <HarryDowns@xxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: need to migrate a older win 2003 srvr sbs to newer one
Date: Thu, 7 Sep 2006 06:56:01 -0700
Lines: 6
Message-ID: <63D9492E-104F-4830-8633-5AA9774F6A92@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.windows.server.migration
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
itNNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.windows.server.migration
Hi This is Harry Downs, I am bit gunshy and rusty on this one , don't do
tooften, but I nedd to migrate an older G3 Proliant Windows 2003 server sbs
appreciated.a new G5 Proliant. Will all I need to do this task is the File Server
Migration Kit? What about exsiting profiles mapped drvies etc? Any
suggestions other than gtting my head examined would be greatly
THank you in advance
- Follow-Ups:
- RE: need to migrate a older win 2003 srvr sbs to newer one
- From: Vincent Xu [MSFT]
- RE: need to migrate a older win 2003 srvr sbs to newer one
- References:
- RE: need to migrate a older win 2003 srvr sbs to newer one
- From: Vincent Xu [MSFT]
- RE: need to migrate a older win 2003 srvr sbs to newer one
- Prev by Date: RE: local groups vs. domain local groups
- Next by Date: RE: run adprep /forestprep error message" program too vig to fit in memory"
- Previous by thread: RE: need to migrate a older win 2003 srvr sbs to newer one
- Next by thread: RE: need to migrate a older win 2003 srvr sbs to newer one
- Index(es):
Relevant Pages
|