Re: Moving exchange

Hi,

Thanks for posting in our newsgroup.

From your description, I know that you want to move Exchange on SBS 2003 to
a new server. If I am off-base, please don't hesitate to let me know.

The SBS 2003 is integrated with Exchange, SharePoint, SQL 2005, ISA on one
server, we cannot only move Exchange to another server. At this point, I
recommend you to migrate the SBS 2003 from old hardware to new server.

Note: Please backup your SBS server before this migration.

Please take the following steps:

1. Start the installation of SBS 2003 from CD #1 or the DVD on the new
hardware. Once the operating system is installed, the server will reboot
and the integrated setup will try to continue, at that point click cancel
to stop the integrated setup.

Important: You must cancel the setup up at this point. Continuing with the
normal integrated setup will not allow the server to join an existing
domain.

2. On the new SBS server, configure a static IP on the LAN network card and
make sure to point DNS to the old SBS server hosting active directory zone.

3. Run DCPROMO on the new SBS 2003 server to join it into the existing
domain, do not create a new forest, and do not create a child domain.
Install DNS, do not change any DNS settings yet.

A. Open Start and select Run.
B. Type DCPROMO and click OK.
C. Click Next 2 times.
D. In the Domain Controller Type, select "Additional Domain Controller for
an existing domain", click Next.
E. Provide the Domain Administrator''s credentials and click Next.
F. Provide the Fully Qualified Domain Name for the Active Directory domain
namespace you are trying to join. For example, CONTOSO.LOCAL. If in doubt,
you can click Browse to select the proper domain. After typing in or
selecting the domain, click Next.
G. Accept the defaults for the Database and Log Folders. Click Next.
H. Accept the defaults for the Shared System Volume. If you need to change
it you will need to point it to an NTFS volume. Click Next.
I. Provide the Directory Services Restore Mode Administrator Password. This
is the password you would use in Directory Services Restore Mode or when
using the Recovery Console. After providing the password twice, click Next
to continue.
J. Click Next in the Summary screen to start the process. The process may
take several minutes.
K. Click Finish to complete the dcpromo and select Restart Now.
L. After the reboot, log on to the SBS server. The server should be a
Domain Controller. To Confirm that:

a. Open a Command Prompt
b. Type Gettype on the command prompt followed by enter/return
c. The output of that command should read as follows:

Host Name: ServerName
Name: Windows Server 2003 for Small Business Server
Version: 5.2 Build 3790
Role: Domain Controller
Components: Not Installed

d. Type Exit followed by enter/return to close the Command Prompt

M. Install the DNS server service.

a. Open Start, Control Panel, Add/Remove Programs
b. Select Add/Remove Windows Components
c. Open networking Services to display the subcomponents and put a check
next to DNS. Click Ok to accept the selection and then Next to proceed.
d. Click Finish to complete the process.

4. Make the new SBS server an Active Directory Global Catalog Server.
Remove the global catalogues from the old SBS 2003 server on this site.

A. On the new SBS server start the Active Directory Sites and Services
snap-in. To start the snap-in, click Start, point to Administrative Tools,
and then click "Active Directory Sites and Services".
B. In the console tree, expand Sites, and then expand
Default-First-Site-Name.
C. Double-click Servers, click SBS server, right-click NTDS Settings, and
then click Properties.
D. On the General tab, click to select the "Global catalog" check box to
assign the role of global catalog to this server.
E. Restart the SBS Server.

Allow sufficient time for the account and the schema information to
replicate to the new global catalog server before you remove the global
catalog from the old SBS server.

Wait for Event 1119 or Event 1869 that should be logged in the Directory
Services log in Event Viewer with a description that states that the
computer is now advertising itself as a global catalog server.

To remove the Global Catalog from the old SBS server after it has
successfully been moved to the new server, follow these steps:

A. On the new SBS server start the Active Directory Sites and Services
snap-in. To start the snap-in, click Start, point to Administrative Tools,
and then click "Active Directory Sites and Services".
B. In the console tree, expand Sites, and then expand
Default-First-Site-Name.
C. Double-click Servers, click on your old SBS server, right-click NTDS
Settings, and then click Properties.
D. On the General tab, click to de-select the "Global catalog" check box to
assign the role of global catalog to this server. (Ignore these steps if
the checkbox was not selected to start with).
E. Restart the old SBS Server after de-selecting the Global Catalog option.

Again, allow sufficient time for the account and the schema information to
replicate to the new global catalog server before you remove the global
catalog from the old SBS server.

For more information:

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

5. Transfer the FSMO roles to the new SBS 2003 server:

Transferring the Domain-Specific Roles: RID, PDC, and Infrastructure Master
---------------------------------------------------------------------------

A. On the new SBS server Click Start, point to Administrative Tools, and
then click "Active Directory Users and Computers".
B. Right-click "Active Directory Users and Computers" icon, and then click
All Tasks->Operation Masters.
C. In the Change Operations Master dialog box, click the appropriate tab
(RID, PDC, or Infrastructure) for the role you want to transfer. (you will
go through each)
D. Click Change in the Change Operations Master dialog box.
E. Click Yes to confirm that you want to transfer the role.
F. Click OK.
G. Go through steps d-f for each of the 3 roles.
H. Click Close to close the dialog box.

Transferring the Domain Naming Master role
------------------------------------------

A. On the new SBS server Click Start, point to Administrative Tools, and
then click "Active Directory Domains and Trusts".
B. Right-click "Active Directory Domains and Trusts", and then click
Operation Masters.
C. In the Change Operations Master dialog box, click Change.
D. Click Yes to confirm that you want to transfer the role.
E. Click OK.
F. Click Close to close the dialog box.

Transferring the Schema Master Role
-----------------------------------

You can use the Schema Master tool to transfer the role. However, the
Schmmgmt.dll dynamic-link library must be registered in order to make the
Schema tool available as an MMC snap-in.

Registering the Schema Tool

A. On the new SBS server, Click Start, and then click Run.
B. Type "regsvr32 schmmgmt.dll" (without the quotation marks), and then
click OK. A message should be displayed stating that the registration was
successful.

Transferring the Schema Master Role

A. On the new SBS server, Click Start, click run, type "mmc" (without the
quotation marks), and then click OK.
B. On the Console menu, click File, Add/Remove Snap-in.
C. Click Add.
D. Click Active Directory Schema.
E. Click Add.
F. Click Close to close the Add Standalone Snap-in dialog box.
G. Click OK to add the snap-in to the console.
H. Right-click the Active Directory Schema icon, and then click Change
Domain Controller.
I. Click Specify Domain Controller, type the name of the domain controller
that will be the new role holder (the new SBS server), and then click OK.
J. Right-click Active Directory Schema, and then click Operation Masters.
K. In the Change Schema Master dialog box, click Change.
L. Click Yes.
M. Click OK
N. Click Close to close the dialog box.

For more information:

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

6. Move the Site License Server to the new SBS 2003 server.

A. On the new SBS server, click Start, point to Administrative Tools, and
then click "Active Directory Sites and Services".
B. In the console tree, expand Sites, and then select
Default-First-Site-Name.
C. On the right panel open the properties for Licensing Site settings.
D. Click on Change and select the newly installed SBS server.
E. Click Ok to close.

For more information:

273475 Licensing in Windows 2000 and Differences with Windows NT
http://support.microsoft.com/?id=273475

7. Wait for replication to properly create the active directory objects on
the new server, this may take some time depending on the active directory
size, you can the Directory Service log in the event viewer to verify its
functionality. The SBS 2003 Integrated setup may not continue if
replication has not completed or has failed.

As a test, open Active Directory Users and Computers on the old SBS server
and create a new test user, wait a few minutes and open Active Directory
Users and Computers on the new server and confirm the object has been
replicated.

You can also force replication as a test by following these steps:

A. On the new SBS server, click Start, point to Administrative Tools, and
then click "Active Directory Sites and Services".
B. In the console tree, click "NTDS Settings" for the old SBS server that
you want to force replication from.
C. In the details pane, right-click the connection that you want to
replicate directory information over, and then click "Replicate Now".

8. Change the DNS settings on all your client computers to point to the new
SBS server as their primary DNS server. Also make the change on the new SBS
server itself.

A. On the new SBS server, open the properties for the internal LAN adapter.
B. Select Internet Protocol (TCP/IP) and click Properties.
C. Change the preferred DNS server to point to its internal IP address.

NOTE: If the clients are using DHCP issued IP addresses, you should shut
down the DHCP service on the old SBS server and install DHCP on the new
server. Then configure the new DHCP server to issue the new server''s IP as
the clients'' ONLY DNS server.

9. On the SBS 2003 server insert SBS CD #1 and continue with the integrated
setup of SBS 2003 and its components.

10. Perform the following tasks to move the Exchange data:

A. In the old SBS server, open ESM (Exchange System Manager), go to
Recipients, Recipient Update Services, edit the entries to point to the new
SBS server.
B. From ESM, Administrative Groups, Routing Groups, First routing group,
Connectors, edit the properties of your SMTP connector (if present) and
change the local bridgehead to the new SBS server. (Display routing groups
needs to be enabled in ESM, in properties of the Exchange organization)
C. From ESM, Administrative Groups, Routing Groups, First routing group,
Connectors, members, make the new SBS server the Master. (Display routing
groups needs to be enabled in ESM, in properties of the Exchange
organization)
D. From ESM, Administrative Groups, First administrative group, Servers,
Server Name (Old Server), First Storage Group, Mailbox Store, Mailboxes,
select all the mailboxes, then open Exchange Tasks (right click), and
select Move Mailbox, select the new SBS server to re-home all the
mailboxes. The public folders should replicate to the new server.
E. Allow for replication time, and then take the old SBS server offline.

Hope this helps.

Please feel free to let me know if you have any questions or if you need
further assistance.

Best regards,

Robert Li(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.

--------------------
<From: "Steve" <newsgroup@xxxxxxxxxx>
<References: <C4DD5506-0481-4976-8594-A24E092F7A32@xxxxxxxxxxxxx>
<Subject: Re: Moving exchange
<Date: Mon, 16 Apr 2007 15:06:23 -0700
<Lines: 17
<X-Priority: 3
<X-MSMail-Priority: Normal
<X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
<X-RFC2646: Format=Flowed; Original
<Message-ID: <OIX75NHgHHA.1244@xxxxxxxxxxxxxxxxxxxx>
<Newsgroups: microsoft.public.windows.server.sbs
<NNTP-Posting-Host: pool-71-164-0-17.sttlwa.fios.verizon.net 71.164.0.17
<Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
<Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:30566
<X-Tomcat-NG: microsoft.public.windows.server.sbs
<
<Your SBS does at least have AD etc. in addition to Exchange. You might
<consider a swing migration from old to new: www.sbsmigration.com.
<
<"AJ" <AJ@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
<news:C4DD5506-0481-4976-8594-A24E092F7A32@xxxxxxxxxxxxxxxx
<> I'm new to SBS so here goes the question.
<>
<> I have a SBS that so far only hosts Exchange. The box is pretty old and I
<> have a new one to replace it. I've moved exchange before to a server
with
<> the
<> same name using the Disasterrecovery option and it worked like a charm.
<>
<> Does it work pretty much the same in SBS?
<>
<> Thanks.
<
<
<

.

Relevant Pages

  • Re: dns problem on sbs2003
    ... SBS 2003 machine as an additional domain controller of a Windows 2000 ... The new SBS 2003 computer must be a global catalog server and must be the ... On a Windows 2000 domain, you must prepare Active Directory before you ... If you already have Microsoft Exchange Server installed in the ...
    (microsoft.public.windows.server.sbs)
  • Re: Connection to a SAMBA Active Directory
    ... Keep in mind that you're trying to setup a NT4 style trust ... if you setup the Exchange as a resource forest model, ... domain and the Exchange server in another domain will work. ... I am able to define a 2 way Realm trust using the Active Directory ...
    (microsoft.public.exchange.connectivity)
  • Re: So why SBS?
    ... Public folders will be in the next version.. ... The sad part of most of us is that we haven't even tried or practiced a backup/restore and we freak out over a 'single" SBS box when we haven't even tried to restore it from a harddrive. ... Exchange seems to mix its words and titles, the global/generic use of POP and SMTP for just about every Exchange function is dumb, MailEnable understands post office protocol and simple mail transfer protocol in a "meaningfull" way. ... The standard profiles in Server are quite effective assuming you add new users to the correct account in the first place and your note running more than 1 file server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Easy to use second 2000 Server for Exchange?
    ... Existing Exchange 2000 server - therefore have the CALs - so no new ones are ... Frank McCallister SBS MVP ...
    (microsoft.public.windows.server.sbs)
  • Re: So why SBS?
    ... Public folders will be in the next version.. ... If SBS isn't for you...that's fine. ... Mailenable is an example of a freeware or pay for extra's, mail server. ... It is infinitly simpler to configure than Exchange once installed. ...
    (microsoft.public.windows.server.sbs)