| Author | Messages | |
AD000001293
Posts:0
 | | 09/04/2005 1:15 AM |
| Hi! I have a huge task to do. I have three separate Windows Server 2003 forests, each with a single domain (and Exchange 2003 servers to boot). I have to combine all three into a single forest and end up with just one root domain, with the other two as child domains of the first.
Is there any way (by hook or by crook) to do this? Pointers to third-party apps are very much appreciated.
Thanks,
Jan | | | |
| prenouf
Posts:2
| | 09/04/2005 1:47 AM |
| That is just the domain piece, there are likely some Exchange points to make, but I'll let some of the Exchange folks here tackle that piece. The same should hold true though, setup some new Exchange servers within your new root forests Exchange Org and migrate the mailboxes to those servers.
That is some pretty high level information there though, there is quite a lot to do with this type of initiative and a lot to keep track of. A good high level place to start is this MS Document:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepKit/cead3dc3-4920-4b7a-b6fe-6111d44110b3.mspx
Phil
On 9/3/05, Chaves, Jan Amcil L. wrote:
Hi! I have a huge task to do. I have three separate Windows Server 2003 forests, each with a single domain (and Exchange 2003 servers to boot). I have to combine all three into a single forest and end up with just one root domain, with the other two as child domains of the first.
Is there any way (by hook or by crook) to do this? Pointers to third-party apps are very much appreciated.Thanks,Jan | | | |
| AD000001293
Posts:0
| | 09/04/2005 3:18 AM |
| Thanks, Phil.
I thought so too. This is my method of last resort.
Actually, if it weren't for the exchange servers I would gladly do it this way.
I wish there was a better (and easier) way to do this, especially since these implementations span four different countries.
Jan
-----Original Message-----
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx
To: ActiveDir@xxxxxxxxxxxxxxxxxx
Sent: Sun Sep 04 09:46:49 2005
Subject: Re: [ActiveDir] Moving forest root domains to child domains in another forest
Your best bet is going to be to create two new child domains in one of the forests and migrate all the objects from the other two domains. This is a pretty common domain restructuring task so there is a lot of information out there about how to do these kinds of migrations. You can use ADMT to do the migrations (it is a free tool from Microsoft), or you could look into 3rd party migration tools from someone like Quest or NetIQ (the two most popular).
That is just the domain piece, there are likely some Exchange points to make, but I'll let some of the Exchange folks here tackle that piece. The same should hold true though, setup some new Exchange servers within your new root forests Exchange Org and migrate the mailboxes to those servers.
That is some pretty high level information there though, there is quite a lot to do with this type of initiative and a lot to keep track of. A good high level place to start is this MS Document:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepKit/cead3dc3-4920-4b7a-b6fe-6111d44110b3.mspx
Phil
On 9/3/05, Chaves, Jan Amcil L. wrote:
Hi! I have a huge task to do. I have three separate Windows Server 2003 forests, each with a single domain (and Exchange 2003 servers to boot). I have to combine all three into a single forest and end up with just one root domain, with the other two as child domains of the first.
Is there any way (by hook or by crook) to do this? Pointers to third-party apps are very much appreciated.
Thanks,
Jan | | | |
| prenouf
Posts:2
| | 09/04/2005 3:51 AM |
| Commissioning new servers shouldn't be a problem. My worry is consolidating the Exchange enviromnents during the domain migration.The largest of the three domains spans 3 cities, each with a clustered Exchange 2003 server, with each server cluster in a different Exchange administative group.
I guess no 3rd party app can move an Exchange cluster accross forests and organizations at the same time :)So I really have to literally take a trip around the globe, rebuilding servers and clusters as I go. This is going to be a long trip..
Jan-----Original Message-----From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx
To: ActiveDir@xxxxxxxxxxxxxxxxxxSent: Sun Sep 04 15:41:29 2005
Subject: Re: [ActiveDir] Moving forest root domains to child domains in another forestWell, I wouldn't say ample hardware is required, but you will need to have some servers available to setup the new environment. A pretty typical approach is to use a few servers to setup an initial environment then as you free old servers up through the migration you rebuild them into the new environment to support additional resources. How many servers you need to start off with would depend on the size of your environment.
Setting up a whole new environment would be nice though :)PhilOn 9/4/05, Brian Desmond wrote: You'd be well off to bite the bullet and buy the Quest stuff. It will be able to take care of most of this in a moderately painless (much opposed to not very paineless writing scripts and such by hand). You'll need ample hardware to duplicate everything you have in the new setup.
Thanks, Brian Desmond brian@xxxxxxxxxxxxxxxx
c - 312.731.3132
________________________________ From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx
[
mailto:ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Phil Renouf Sent: Saturday, September 03, 2005 9:47 PM To:
ActiveDir@xxxxxxxxxxxxxxxxxx Subject: Re: [ActiveDir] Moving forest root domains to child domains in another forest
Your best bet is going to be to create two new child domains in one of the forests and migrate all the objects from the other two domains. This is a pretty common domain restructuring task so there is a lot of information out there about how to do these kinds of migrations. You can use ADMT to do the migrations (it is a free tool from Microsoft), or you could look into 3rd party migration tools from someone like Quest or NetIQ (the two most popular).
That is just the domain piece, there are likely some Exchange points to make, but I'll let some of the Exchange folks here tackle that piece. The same should hold true though, setup some new Exchange servers within your new root forests Exchange Org and migrate the mailboxes to those servers.
That is some pretty high level information there though, there is quite a lot to do with this type of initiative and a lot to keep track of. A good high level place to start is this MS Document:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepKit/cead3dc3-4920-4b7a-b6fe-6111d44110b3.mspx Phil On 9/3/05, Chaves, Jan Amcil L. > wrote: Hi! I have a huge task to do. I have three separate Windows Server 2003 forests, each with a single domain (and Exchange 2003 servers to boot). I have to combine all three into a single forest and end up with just one root domain, with the other two as child domains of the first.
Is there any way (by hook or by crook) to do this? Pointers to third-party apps are very much appreciated. Thanks, Jan | | | |
| bdesmond
Posts:977
| | 09/04/2005 4:58 AM |
| You™d be well off to bite the bullet and buy the Quest stuff. It
will be able to take care of most of this in a moderately painless (much
opposed to not very paineless writing scripts and such by hand). You™ll
need ample hardware to duplicate everything you have in the new setup.
Thanks,
Brian
Desmond
brian@xxxxxxxxxxxxxxxx
c -
312.731.3132
From:
ActiveDir-owner@xxxxxxxxxxxxxxxxxx [mailto:ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Phil Renouf
Sent: Saturday, September 03, 2005
9:47 PM
To: ActiveDir@xxxxxxxxxxxxxxxxxx
Subject: Re: [ActiveDir] Moving
forest root domains to child domains in another forest
Your best bet is going to be to create two new child domains in one of
the forests and migrate all the objects from the other two domains. This is a
pretty common domain restructuring task so there is a lot of information out
there about how to do these kinds of migrations. You can use ADMT to do the
migrations (it is a free tool from Microsoft), or you could look into 3rd party
migration tools from someone like Quest or NetIQ (the two most popular).
That is just the domain piece, there are likely some Exchange points to
make, but I'll let some of the Exchange folks here tackle that piece. The same
should hold true though, setup some new Exchange servers within your new root
forests Exchange Org and migrate the mailboxes to those servers.
That is some pretty high level information there though, there is quite
a lot to do with this type of initiative and a lot to keep track of. A good
high level place to start is this MS Document:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepKit/cead3dc3-4920-4b7a-b6fe-6111d44110b3.mspx
Phil
On 9/3/05, Chaves,
Jan Amcil L.
wrote:
Hi!
I have a huge task to do. I have three separate Windows Server 2003
forests, each with a single domain (and Exchange 2003 servers to boot). I
have to combine all three into a single forest and end up with just one root
domain, with the other two as child domains of the first.
Is there any way (by hook or by crook) to do this? Pointers to
third-party apps are very much appreciated.
Thanks,
Jan | | | |
| prenouf
Posts:2
| | 09/04/2005 7:43 AM |
| Setting up a whole new environment would be nice though :)
Phil
On 9/4/05, Brian Desmond wrote:
You'd be well off to bite the bullet and buy the Quest stuff. It will be able to take care of most of this in a moderately painless (much opposed to not very paineless writing scripts and such by hand). You'll need ample hardware to duplicate everything you have in the new setup.
Thanks,
Brian Desmond
brian@xxxxxxxxxxxxxxxx
c - 312.731.3132
From:
ActiveDir-owner@xxxxxxxxxxxxxxxxxx [mailto:ActiveDir-owner@xxxxxxxxxxxxxxxxxx]
On Behalf Of Phil RenoufSent: Saturday, September 03, 2005 9:47 PMTo:
ActiveDir@xxxxxxxxxxxxxxxxxxSubject: Re: [ActiveDir] Moving forest root domains to child domains in another forest
Your best bet is going to be to create two new child domains in one of the forests and migrate all the objects from the other two domains. This is a pretty common domain restructuring task so there is a lot of information out there about how to do these kinds of migrations. You can use ADMT to do the migrations (it is a free tool from Microsoft), or you could look into 3rd party migration tools from someone like Quest or NetIQ (the two most popular).
That is just the domain piece, there are likely some Exchange points to make, but I'll let some of the Exchange folks here tackle that piece. The same should hold true though, setup some new Exchange servers within your new root forests Exchange Org and migrate the mailboxes to those servers.
That is some pretty high level information there though, there is quite a lot to do with this type of initiative and a lot to keep track of. A good high level place to start is this MS Document:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepKit/cead3dc3-4920-4b7a-b6fe-6111d44110b3.mspx
Phil
On 9/3/05, Chaves, Jan Amcil L. wrote:
Hi! I have a huge task to do. I have three separate Windows Server 2003 forests, each with a single domain (and Exchange 2003 servers to boot). I have to combine all three into a single forest and end up with just one root domain, with the other two as child domains of the first.
Is there any way (by hook or by crook) to do this? Pointers to third-party apps are very much appreciated.Thanks,Jan | | | |
| AD000001293
Posts:0
| | 09/04/2005 8:35 AM |
| Commissioning new servers shouldn't be a problem. My worry is consolidating the Exchange enviromnents during the domain migration.
The largest of the three domains spans 3 cities, each with a clustered Exchange 2003 server, with each server cluster in a different Exchange administative group.
I guess no 3rd party app can move an Exchange cluster accross forests and organizations at the same time :)
So I really have to literally take a trip around the globe, rebuilding servers and clusters as I go. This is going to be a long trip..
Jan
-----Original Message-----
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx
To: ActiveDir@xxxxxxxxxxxxxxxxxx
Sent: Sun Sep 04 15:41:29 2005
Subject: Re: [ActiveDir] Moving forest root domains to child domains in another forest
Well, I wouldn't say ample hardware is required, but you will need to have some servers available to setup the new environment. A pretty typical approach is to use a few servers to setup an initial environment then as you free old servers up through the migration you rebuild them into the new environment to support additional resources. How many servers you need to start off with would depend on the size of your environment.
Setting up a whole new environment would be nice though :)
Phil
On 9/4/05, Brian Desmond wrote:
You'd be well off to bite the bullet and buy the Quest stuff. It will be able to take care of most of this in a moderately painless (much opposed to not very paineless writing scripts and such by hand). You'll need ample hardware to duplicate everything you have in the new setup.
Thanks,
Brian Desmond
brian@xxxxxxxxxxxxxxxx
c - 312.731.3132
________________________________
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx [mailto:ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Phil Renouf
Sent: Saturday, September 03, 2005 9:47 PM
To: ActiveDir@xxxxxxxxxxxxxxxxxx
Subject: Re: [ActiveDir] Moving forest root domains to child domains in another forest
Your best bet is going to be to create two new child domains in one of the forests and migrate all the objects from the other two domains. This is a pretty common domain restructuring task so there is a lot of information out there about how to do these kinds of migrations. You can use ADMT to do the migrations (it is a free tool from Microsoft), or you could look into 3rd party migration tools from someone like Quest or NetIQ (the two most popular).
That is just the domain piece, there are likely some Exchange points to make, but I'll let some of the Exchange folks here tackle that piece. The same should hold true though, setup some new Exchange servers within your new root forests Exchange Org and migrate the mailboxes to those servers.
That is some pretty high level information there though, there is quite a lot to do with this type of initiative and a lot to keep track of. A good high level place to start is this MS Document:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepKit/cead3dc3-4920-4b7a-b6fe-6111d44110b3.mspx
Phil
On 9/3/05, Chaves, Jan Amcil L. > wrote:
Hi! I have a huge task to do. I have three separate Windows Server 2003 forests, each with a single domain (and Exchange 2003 servers to boot). I have to combine all three into a single forest and end up with just one root domain, with the other two as child domains of the first.
Is there any way (by hook or by crook) to do this? Pointers to third-party apps are very much appreciated.
Thanks,
Jan | | | |
| AD000001293
Posts:0
| | 09/05/2005 2:12 AM |
| Haha good point, Phil :)
Thanks,
Jan
-----Original Message-----
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx
To: ActiveDir@xxxxxxxxxxxxxxxxxx
Sent: Sun Sep 04 23:49:58 2005
Subject: Re: [ActiveDir] Moving forest root domains to child domains in another forest
You could build clusters in your city and ship them out to the remote location, or use something like HP's remote insight board to build the machines remotely.
Or if you're looking for the Airline reward miles you could make a trip around the world ;)
Phil
On 9/4/05, Chaves, Jan Amcil L. wrote:
Commissioning new servers shouldn't be a problem. My worry is consolidating the Exchange enviromnents during the domain migration.
The largest of the three domains spans 3 cities, each with a clustered Exchange 2003 server, with each server cluster in a different Exchange administative group.
I guess no 3rd party app can move an Exchange cluster accross forests and organizations at the same time :)
So I really have to literally take a trip around the globe, rebuilding servers and clusters as I go. This is going to be a long trip..
Jan
-----Original Message-----
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx
To: ActiveDir@xxxxxxxxxxxxxxxxxx
Sent: Sun Sep 04 15:41:29 2005
Subject: Re: [ActiveDir] Moving forest root domains to child domains in another forest
Well, I wouldn't say ample hardware is required, but you will need to have some servers available to setup the new environment. A pretty typical approach is to use a few servers to setup an initial environment then as you free old servers up through the migration you rebuild them into the new environment to support additional resources. How many servers you need to start off with would depend on the size of your environment.
Setting up a whole new environment would be nice though :)
Phil
On 9/4/05, Brian Desmond > wrote:
You'd be well off to bite the bullet and buy the Quest stuff. It will be able to take care of most of this in a moderately painless (much opposed to not very paineless writing scripts and such by hand). You'll need ample hardware to duplicate everything you have in the new setup.
Thanks,
Brian Desmond
brian@xxxxxxxxxxxxxxxx
c - 312.731.3132
________________________________
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx [ mailto:ActiveDir-owner@xxxxxxxxxxxxxxxxxx ] On Behalf Of Phil Renouf
Sent: Saturday, September 03, 2005 9:47 PM
To: ActiveDir@xxxxxxxxxxxxxxxxxx
Subject: Re: [ActiveDir] Moving forest root domains to child domains in another forest
Your best bet is going to be to create two new child domains in one of the forests and migrate all the objects from the other two domains. This is a pretty common domain restructuring task so there is a lot of information out there about how to do these kinds of migrations. You can use ADMT to do the migrations (it is a free tool from Microsoft), or you could look into 3rd party migration tools from someone like Quest or NetIQ (the two most popular).
That is just the domain piece, there are likely some Exchange points to make, but I'll let some of the Exchange folks here tackle that piece. The same should hold true though, setup some new Exchange servers within your new root forests Exchange Org and migrate the mailboxes to those servers.
That is some pretty high level information there though, there is quite a lot to do with this type of initiative and a lot to keep track of. A good high level place to start is this MS Document:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepKit/cead3dc3-4920-4b7a-b6fe-6111d44110b3.mspx >
Phil
On 9/3/05, Chaves, Jan Amcil L. > > wrote:
Hi! I have a huge task to do. I have three separate Windows Server 2003 forests, each with a single domain (and Exchange 2003 servers to boot). I have to combine all three into a single forest and end up with just one root domain, with the other two as child domains of the first.
Is there any way (by hook or by crook) to do this? Pointers to third-party apps are very much appreciated.
Thanks,
Jan | | | |
| GuidoG
Posts:113
| | 09/05/2005 5:48 AM |
| > but not
quite that intimate to all fit in a single domain ... slow links connect
global sites thus necessitating the split in the
domains
you'd need more arguments for us to be able to follow your
decisionmaking - usually there's many more reasons to keep things in a single
domain, than there are to split them up. Especially if you have Exchange
in the forest requiring good connectivity to GCs anyways.
How many sites do you have, how slow are your links and how
many users are you talking about in each of your current forests? Who is
going to manage the forest and the different domains?
/Guido
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx
[mailto:ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Chaves, Jan
Amcil L.Sent: Montag, 5. September 2005 14:37To:
ActiveDir@xxxxxxxxxxxxxxxxxxSubject: Re: [ActiveDir] Moving forest
root domains to child domains in another forest
Right. Mostly for administrative and exchange consolidation. And
to implement a logically consistent naming convention.The domains are
related enough to put into a single forest, but not quite that intimate to all
fit in a single domain, due to raidcal differences in GPOs, etc. Not to mention
slow links connect global sites thus necessitating the split in the
domains.Our objective, just recently revised, is to come up with an
empty forest root and three (possibly more) child domains under it. And then
build exchange around the forest.Jan-----Original
Message-----From: ActiveDir-owner@xxxxxxxxxxxxxxxxxxTo:
ActiveDir@xxxxxxxxxxxxxxxxxxSent: Mon Sep 05 16:07:23 2005Subject: RE:
[ActiveDir] Moving forest root domains to child domains in another
forestcan you mention some of your reasons WHY you want to merge your
three forests in the way you describe?I certainly understand that you
might want to consolidate, but why in the world would you want to go from three
single-domain forests to one forest with a root + 2 child domains, leaving you
with managing three domains? I'd actually vote that this is worse
than what you have right now. If you do consolidate, then I'd suggest you
migrate the objects from those two forests directly to the existing root of your
third forest, leaving you with a single domain to
manage./Guido________________________________From:
ActiveDir-owner@xxxxxxxxxxxxxxxxxx [mailto:ActiveDir-owner@xxxxxxxxxxxxxxxxxx]
On Behalf Of Chaves, Jan Amcil L.Sent: Sonntag, 4. September 2005
03:15To: ActiveDir@xxxxxxxxxxxxxxxxxxSubject: [ActiveDir] Moving forest
root domains to child domains in another forestHi! I
have a huge task to do. I have three separate Windows Server 2003 forests,
each with a single domain (and Exchange 2003 servers to boot). I have to
combine all three into a single forest and end up with just one root domain,
with the other two as child domains of the first.Is there any way (by
hook or by crook) to do this? Pointers to third-party apps are very much
appreciated.Thanks,Jan | | | |
| AD00000900
Posts:0
| | 09/05/2005 8:32 AM |
| Link speed really has nothing to do with the decision to
split into separate domains. You've got a LOT of control over replication and
really can build a topology that works for just about any WAN design you care to
put out there.
Keeping in mind that forests are the true security
boundary, are you getting any real benefit from moving from 3 forsts to 4
domains?
--------Roger SeielstadE-mail Geek
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx
[mailto:ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Chaves, Jan
Amcil L.Sent: Monday, September 05, 2005 5:37 AMTo:
ActiveDir@xxxxxxxxxxxxxxxxxxSubject: Re: [ActiveDir] Moving forest
root domains to child domains in another forest
Right. Mostly for administrative and exchange consolidation. And
to implement a logically consistent naming convention.The domains are
related enough to put into a single forest, but not quite that intimate to all
fit in a single domain, due to raidcal differences in GPOs, etc. Not to mention
slow links connect global sites thus necessitating the split in the
domains.Our objective, just recently revised, is to come up with an
empty forest root and three (possibly more) child domains under it. And then
build exchange around the forest.Jan-----Original
Message-----From: ActiveDir-owner@xxxxxxxxxxxxxxxxxxTo:
ActiveDir@xxxxxxxxxxxxxxxxxxSent: Mon Sep 05 16:07:23 2005Subject: RE:
[ActiveDir] Moving forest root domains to child domains in another
forestcan you mention some of your reasons WHY you want to merge your
three forests in the way you describe?I certainly understand that you
might want to consolidate, but why in the world would you want to go from three
single-domain forests to one forest with a root + 2 child domains, leaving you
with managing three domains? I'd actually vote that this is worse
than what you have right now. If you do consolidate, then I'd suggest you
migrate the objects from those two forests directly to the existing root of your
third forest, leaving you with a single domain to
manage./Guido________________________________From:
ActiveDir-owner@xxxxxxxxxxxxxxxxxx [mailto:ActiveDir-owner@xxxxxxxxxxxxxxxxxx]
On Behalf Of Chaves, Jan Amcil L.Sent: Sonntag, 4. September 2005
03:15To: ActiveDir@xxxxxxxxxxxxxxxxxxSubject: [ActiveDir] Moving forest
root domains to child domains in another forestHi! I
have a huge task to do. I have three separate Windows Server 2003 forests,
each with a single domain (and Exchange 2003 servers to boot). I have to
combine all three into a single forest and end up with just one root domain,
with the other two as child domains of the first.Is there any way (by
hook or by crook) to do this? Pointers to third-party apps are very much
appreciated.Thanks,Jan | | | |
| TonyTest
Posts:0
| | 09/05/2005 9:57 AM |
| I
(mostly) agree with Roger. You have a high degree of flexibility with
replication control. And with Windows 2003 forest functional level you get
LVR, which obviously helps to reduce the replication overhead. On the
other hand there are some global companies that I know of that do use the
replication boundary of domains to reduce bandwidth utilization on slow
links. Fast and cheap WAN connections are not yet widely available in
all parts of the world.
Tony
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx
[mailto:ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Roger
SeielstadSent: Tuesday, 6 September 2005 8:30 a.m.To:
ActiveDir@xxxxxxxxxxxxxxxxxxSubject: RE: [ActiveDir] Moving forest
root domains to child domains in another forest
Link speed really has nothing to do with the decision to
split into separate domains. You've got a LOT of control over replication and
really can build a topology that works for just about any WAN design you care to
put out there.
Keeping in mind that forests are the true security
boundary, are you getting any real benefit from moving from 3 forsts to 4
domains?
--------Roger SeielstadE-mail Geek
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx
[mailto:ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Chaves, Jan
Amcil L.Sent: Monday, September 05, 2005 5:37 AMTo:
ActiveDir@xxxxxxxxxxxxxxxxxxSubject: Re: [ActiveDir] Moving forest
root domains to child domains in another forest
Right. Mostly for administrative and exchange consolidation. And
to implement a logically consistent naming convention.The domains are
related enough to put into a single forest, but not quite that intimate to all
fit in a single domain, due to raidcal differences in GPOs, etc. Not to mention
slow links connect global sites thus necessitating the split in the
domains.Our objective, just recently revised, is to come up with an
empty forest root and three (possibly more) child domains under it. And then
build exchange around the forest.Jan-----Original
Message-----From: ActiveDir-owner@xxxxxxxxxxxxxxxxxxTo:
ActiveDir@xxxxxxxxxxxxxxxxxxSent: Mon Sep 05 16:07:23 2005Subject: RE:
[ActiveDir] Moving forest root domains to child domains in another
forestcan you mention some of your reasons WHY you want to merge your
three forests in the way you describe?I certainly understand that you
might want to consolidate, but why in the world would you want to go from three
single-domain forests to one forest with a root + 2 child domains, leaving you
with managing three domains? I'd actually vote that this is worse
than what you have right now. If you do consolidate, then I'd suggest you
migrate the objects from those two forests directly to the existing root of your
third forest, leaving you with a single domain to
manage./Guido________________________________From:
ActiveDir-owner@xxxxxxxxxxxxxxxxxx [mailto:ActiveDir-owner@xxxxxxxxxxxxxxxxxx]
On Behalf Of Chaves, Jan Amcil L.Sent: Sonntag, 4. September 2005
03:15To: ActiveDir@xxxxxxxxxxxxxxxxxxSubject: [ActiveDir] Moving forest
root domains to child domains in another forestHi! I
have a huge task to do. I have three separate Windows Server 2003 forests,
each with a single domain (and Exchange 2003 servers to boot). I have to
combine all three into a single forest and end up with just one root domain,
with the other two as child domains of the first.Is there any way (by
hook or by crook) to do this? Pointers to third-party apps are very much
appreciated.Thanks,Jan
This e-mail message has been scanned for Viruses and Content and cleared by
NetIQ MailMarshal at Gen-i Limited | | | |
| AD000001293
Posts:0
| | 09/05/2005 12:39 PM |
| Right. Mostly for administrative and exchange consolidation. And to implement a logically consistent naming convention.
The domains are related enough to put into a single forest, but not quite that intimate to all fit in a single domain, due to raidcal differences in GPOs, etc. Not to mention slow links connect global sites thus necessitating the split in the domains.
Our objective, just recently revised, is to come up with an empty forest root and three (possibly more) child domains under it. And then build exchange around the forest.
Jan
-----Original Message-----
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx
To: ActiveDir@xxxxxxxxxxxxxxxxxx
Sent: Mon Sep 05 16:07:23 2005
Subject: RE: [ActiveDir] Moving forest root domains to child domains in another forest
can you mention some of your reasons WHY you want to merge your three forests in the way you describe?
I certainly understand that you might want to consolidate, but why in the world would you want to go from three single-domain forests to one forest with a root + 2 child domains, leaving you with managing three domains?
I'd actually vote that this is worse than what you have right now. If you do consolidate, then I'd suggest you migrate the objects from those two forests directly to the existing root of your third forest, leaving you with a single domain to manage.
/Guido
________________________________
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx [mailto:ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Chaves, Jan Amcil L.
Sent: Sonntag, 4. September 2005 03:15
To: ActiveDir@xxxxxxxxxxxxxxxxxx
Subject: [ActiveDir] Moving forest root domains to child domains in another forest
Hi! I have a huge task to do. I have three separate Windows Server 2003 forests, each with a single domain (and Exchange 2003 servers to boot). I have to combine all three into a single forest and end up with just one root domain, with the other two as child domains of the first.
Is there any way (by hook or by crook) to do this? Pointers to third-party apps are very much appreciated.
Thanks,
Jan | | | |
| djambo
Posts:0
| | 09/07/2005 2:53 AM |
| Oliver
On 9/5/05, Tony Murray wrote:
I (mostly) agree with Roger. You have a high degree of flexibility with replication control. And with Windows 2003 forest functional level you get LVR, which obviously helps to reduce the replication overhead. On the other hand there are some global companies that I know of that do use the replication boundary of domains to reduce bandwidth utilization on slow links. Fast and cheap WAN connections are not yet widely available in all parts of the world.
Tony
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx [mailto:
ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Roger SeielstadSent: Tuesday, 6 September 2005 8:30 a.m.To:
ActiveDir@xxxxxxxxxxxxxxxxxx
Subject: RE: [ActiveDir] Moving forest root domains to child domains in another forest
Link speed really has nothing to do with the decision to split into separate domains. You've got a LOT of control over replication and really can build a topology that works for just about any WAN design you care to put out there.
Keeping in mind that forests are the true security boundary, are you getting any real benefit from moving from 3 forsts to 4 domains?
--------Roger SeielstadE-mail Geek
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx [mailto:
ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Chaves, Jan Amcil L.Sent: Monday, September 05, 2005 5:37 AMTo:
ActiveDir@xxxxxxxxxxxxxxxxxxSubject: Re: [ActiveDir] Moving forest root domains to child domains in another forest
Right. Mostly for administrative and exchange consolidation. And to implement a logically consistent naming convention.The domains are related enough to put into a single forest, but not quite that "intimate" to all fit in a single domain, due to raidcal differences in GPOs, etc. Not to mention slow links connect global sites thus necessitating the split in the domains.
Our objective, just recently revised, is to come up with an empty forest root and three (possibly more) child domains under it. And then build exchange around the forest.Jan-----Original Message-----
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxxTo:
ActiveDir@xxxxxxxxxxxxxxxxxxSent: Mon Sep 05 16:07:23 2005Subject: RE: [ActiveDir] Moving forest root domains to child domains in another forestcan you mention some of your reasons WHY you want to merge your three forests in the way you describe?
I certainly understand that you might want to consolidate, but why in the world would you want to go from three single-domain forests to one forest with a root + 2 child domains, leaving you with managing three domains?
I'd actually vote that this is worse than what you have right now. If you do consolidate, then I'd suggest you migrate the objects from those two forests directly to the existing root of your third forest, leaving you with a single domain to manage.
/Guido________________________________From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx
[mailto:ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Chaves, Jan Amcil L.Sent: Sonntag, 4. September 2005 03:15
To: ActiveDir@xxxxxxxxxxxxxxxxxxSubject: [ActiveDir] Moving forest root domains to child domains in another forest
Hi! I have a huge task to do. I have three separate Windows Server 2003 forests, each with a single domain (and Exchange 2003 servers to boot). I have to combine all three into a single forest and end up with just one root domain, with the other two as child domains of the first.
Is there any way (by hook or by crook) to do this? Pointers to third-party apps are very much appreciated.Thanks,Jan
This e-mail message has been scanned for Viruses and Content and cleared by NetIQ MailMarshal at Gen-i Limited | | | |
|
|