Re: Remote Office Configuration

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I am sorry...you miss understand
the branch office only has a Win2k DC, no Exchange at this location.
The HQ has Exchange 2003, this is the only Exchange server in our
network.

Would it be easier to bring into the branch office a second DC and
depmote the current Win2k DC?

Thanks


Jorge Silva wrote:
Assuming that the Destination Forest has Windows and exchange 2003, and the
source forest has Windows and exchange 2000.

The best that you can do with 2 different forests in this scenario, is to
create a two way external trust, which is non transitive.



- To migrate accounts and mailboxes from one Exchange 2000 or Exchange 2003
forest to a separate Exchange 2000 or Exchange 2003 forest, it is
recommended that you first use the Active Directory Migration Tool (ADMT),
followed by the Exchange Migration Wizard.

- First, run ADMT to create active user accounts in Active Directory. It is
recommended that you select the option for migrating security identifiers
(SIDs) so that ADMT adds the source account's SID to the new target
account's SID history attribute. (Migration Wizard uses the SID to match
mailboxes).

- It is also recommended that you do not disable the user account in the
source forest when you run ADMT. Exchange 2003 does not support disabled
mailbox accounts without associated external account.

- After you migrate the accounts, use Migration Wizard to migrate mailboxes.
If you migrated SIDs when you ran ADMT, Migration Wizard uses the SIDs to
match mailboxes to the new accounts and converts the accounts to
mailbox-enabled user accounts. If you did not migrate the SIDs , Migration
Wizard cannot match a mailbox to an account; instead, the wizard creates a
disabled user account to associate with the mailbox.

Active Directory Migration Tool (ADMT).

http://www.microsoft.com/downloads/details.aspx?familyid=788975b1-5849-4707-9817-8c9773c25c6c&displaylang=en



--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"kunundrum" <dstubbs@xxxxxxxxxx> wrote in message
news:1149874575.552787.9330@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks for the reply....what will be the inpact to the current Win2k
Server? Is it better for us to bring in a Win2k3 server then demote the
Win2k Server?

Thanks again



Jorge Silva wrote:
Hi

The Problem
==============
Remote Office A was setup a few years back by a different network
administrator who setup this location as a separate domain from HQ. So
now, we want to migrate to one domain so that we may utilize Exchange
network wide.

Not possible to merge one forest into another you have to migrate.




--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"kunundrum" <dstubbs@xxxxxxxxxx> wrote in message
news:1149863525.306492.28590@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,
I have a question regarding what is the best choice for a remote office
setup.

Network Overview
==============
My network consists of three sites all connect via internal 512Kbps
VSAT system. All routable we can ping each site via IP.

· HQ = 1DC Win2k3, 1 Exchange Win2k3, 25-30 users (192.168.1.x)
· Remote Office A = 1DC Win2k, 25-30 users (192.168.2.x)
· Remote Office B = WinXP Pro, 4-8 users (192.168.3.x)

The Problem
==============
Remote Office A was setup a few years back by a different network
administrator who setup this location as a separate domain from HQ. So
now, we want to migrate to one domain so that we may utilize Exchange
network wide.

The Question
==============
What would be my best course of action?

Should try and utilize the existing (production) Win2k DC and simply
change domains?
Pros/Cons?

Should I configure a separate DC and bring it to the site and demote
the existing Win2k DC? I still want to use the existing Win2k DC for
DNS and file sharing.
Pros/Cons?

I guess I am looking for the path of least impact to the end users as
well as the most functional option.

.

Relevant Pages

  • Re: Install new hardware for SBS 2003
    ... I agree Cliff and having done a Swing migration myself I can attest to the ... his plan would not work. ... then the new accounts would obviously cause a mismatch...and ... have to get the current Exchange mail over too. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange 5.5
    ... stuff cause the builtin accounts aren't migrated and all seemed ok. ... then you have no upgrade path. ... It's strictly a migration. ... > and want to upgrade Exchange but migrate the Windows accounts, ...
    (microsoft.public.exchange.setup)
  • NT 4 Exchange 5.5 to AD and Exchange 2003
    ... have completed migration of user accounts, sid histories, ... Installation of Exchange 2003 in AD domain on new server ... accounts to this location in a sub org called recipients. ... In the root org is also a sub org called users to which it ...
    (microsoft.public.exchange2000.setup.installation)
  • Re: Integrating a newly acquired subsidiary of a big corporation.
    ... I wouldn't use CSVDE because of delimiter problems, but LDIFDE is ... accounts, so groups should be migrated after the accounts. ... because of GUID ties to the source exchange ... I found when I used the exchange migration wizard on the source ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD merge with exchange 2007 srv, can ADMT do it?
    ... > ADMT will do user and computer account migration. ... > "Exchange cross forest migration" and you will find some documentations. ... I usually do put together step by step docs such as this, to help folks in the newsgroups, but I haven't yet with this procedure because besides being scattered and the procedure having many facets, my notes are customer specific with domain names, user accounts, passwords, etc, that it will take me some time to go through to compile it into one doc, and I do apologize I am short on time to do anything with this at this point. ...
    (microsoft.public.windows.server.active_directory)