RE: Migrate sbs200 standalone to enterprise forest
- From: v-xuwen@xxxxxxxxxxxxxxxxxxxx (Vincent Xu [MSFT])
- Date: Wed, 20 Dec 2006 02:05:50 GMT
Hi Mike,
If you just want to migrate SBS 2K domain to a new 2K3 Domain, I would
suggest that you read the whitepaper below. Although it is written for SBS
2K3 migration, you can also use the parts (such as ADMT, Exchange
migration):
Migrating from Small Business Server 2000 or Windows 2000 Server to Windows
Small Business Server 2003
http://www.microsoft.com/downloads/details.aspx?familyid=fa187d1e-8218-4501-
9729-222bd8ebb64c&displaylang=en
For this scenario, I would like to provide the following steps:
1) Perform a full backup of the SBS 2000.
2) Install Windows Server 2003 on a new machine, and then promote it to the
DC of a new domain.
3) Install Exchange Server 2003 (Organization name must be same).
4) Download Active Directory Migration Tool (ADMT) from the following web
page and then install it on the Windows Server 2003.
Active Directory Migration Tool v.2.0
http://www.microsoft.com/downloads/details.aspx?FamilyID=788975b1-5849-4707-
9817-8c9773c25c6c&DisplayLang=en
5) Launch Administrative Tools | Active Directory Migration Tool, and then
follow the steps mentioned in the following KB article to migrate the AD
information:
326480 How to Use Active Directory Migration Tool Version 2 to Migrate from
Windows 2000 to Windows Server 2003
http://support.microsoft.com/?id=326480
You may need to start the Active Directory Migration Tool, click Help
Topics on the Help menu, click the Contents tab, and then click Active
Directory Migration Tool to see how to use ADMT to perform a migration, see
ADMT Help.
6) Determine whether the mail quota for Exchange needs updating:
A. On the source server, click Start, and then click Small Business Server
Administrator Console.
B. Double-click YourExchangeOrganization, double-click Servers,
double-click YourServer, double-click YourStorageGroup, right-click Mailbox
Store, and then click Properties.
C. Click the Limits tab.
D. Review the settings for Issue warning at (KB) and Prohibit send and
receive at (KB). If the quotas are set to something other than 175,000 KB
for the warning and 200,000 KB for the limit for sending and receiving
e-mail, continue to the next step and update the Exchange mail quota
settings on the destination server.
E. On the destination server, click Start, and then click Server Management.
F. Double-click Advanced Management, double-click YourExchangeOrganization,
double-click Servers, double-click YourServer, double-click
YourStorageGroup, right-click Mailbox Store, and then click Properties.
G. On the Limits tab, update the settings for Issue warning at (KB) and
Prohibit send and receive at (KB).Move Exchange mailboxes
7) Move Exchange mailboxes
A. On the destination server, click Start, point to All programs, point to
Microsoft Exchange, point to Deployment, and then click Migration Wizard.
B. In the Exchange Migration Wizard, configure your server by using the
information provided in the following Table:
Wizard page Action
Migration Select Migrate from Microsoft Exchange.
Exchange Server Migration Click Next to continue.
Migration Destination You must accept the default of Migrate to a computer
running Exchange Server.
Source Exchange Server 1. Clear the Exchange 5.5 server check box.
2. For Exchange server name, type the computer name of the source server
(as recorded in "Work*** 1: Source and Destination Computer Information").
3. Type the Administrator account and password.
Migration Information Accept the default of Create/modify mailbox accounts.
Account Migration ? Select the accounts for which you want to migrate the
mailboxes.
? Important considerations for account migration:
? This tool does not support migrating mail for the Administrator account.
To migrate mail for this account, from a client computer, use Outlook to
export the mail to a .pst file and then later import it. You must also
export any mailbox rules for the Administrator account. For more
information about exporting to a .pst file or exporting mailbox rules, see
Outlook Help on the client computer.
? If you are migrating the mailbox for an account, the account must have
been migrated to the server using the User Account Migration Wizard
described earlier in this document.
Container for New Windows Account Browse to
YourDomain\MyBusiness\Users\SBSUsers.
C. Follow the instructions to complete the Exchange Migration Wizard.
For licensing questions, you can call 1-800-426-9400 (select option 4),
Monday through Friday, 6:00 A.M. to 5:30 P.M. (PST) to speak directly to a
Microsoft licensing specialist.
Worldwide customers can use the Guide to Worldwide Microsoft Licensing
Sites http://www.microsoft.com/licensing/index/worldwide.asp to find
contact information in their locations.
Best regards,
Vincent Xu
Microsoft Online Partner Support
======================================================
PLEASE NOTE: The partner managed newsgroups are provided to assist with
break/fix issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
from the web interface: Partner Feedback
from your newsreader: microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
======================================================
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.
======================================================
--------------------
aThread-Topic: Migrate sbs200 standalone to enterprise forest
thread-index: AccjgbaLWzgfzdytRmiGMqxqTvvTXg==
X-WBNR-Posting-Host: 67.70.222.102
From: =?Utf-8?B?TWlrZUc=?= <MikeG@xxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Migrate sbs200 standalone to enterprise forest
Date: Tue, 19 Dec 2006 07:24:02 -0800
Lines: 15
Message-ID: <124D6049-2AA1-4102-A519-8BE9F5FF4129@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.2757
Newsgroups: microsoft.public.windows.server.migration
Path: TK2MSFTNGHUB02.phx.gbl
Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.migration:151
NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
X-Tomcat-NG: microsoft.public.windows.server.migration
I am in the process of rolling out a corporate wide single forest, single
domain AD implementation with Win2003. At one of our locations, we have
ofWin2000 Small Biz Server that I would like to upgrade to a member server
componentsmy new AD domain. The SBS server is NOT using any of the SBSish
andlike SQL, Exch, ISA. It is merely running as its own forest root, DC,
offile/print server. I had hoped to use ADMT to migrate all the users off
makethis box into my new AD domain and then remove AD from the SBS box and
Cleanupit a member server of the new AD and then finally run the Security
can'tWizard to complete this location's migration. However, it appears I
issues.use any of the standard tools because this is an SBS box. How do I get
around this? I have seen references to the "Small Business Server 2000
Migration Pack" but cannot seem to locate it or even confirm it exists.
Unfortunately, I don't even know whether that tool would overcome my
I'd like to find some straightforward way of accomplishing this.
.
- Prev by Date: Re: W2k3 AD migration to W2k3 AD - HELP HELP!!
- Next by Date: RE: Migration question
- Previous by thread: Re: W2k3 AD migration to W2k3 AD - HELP HELP!!
- Next by thread: RE: Migrate sbs200 standalone to enterprise forest
- Index(es):