Merge AD after Aquisition

It has been proposed that our existing AD (domain.a.com) is merged to new
parent company domain. I have never been involved in a similar project and
was looking for some advice on the steps that may be involved so that I am
prepped.

Currently we run our own DNS / WINS / DHCP / Exchange.

Exchange is to be replaced. I believe we will retain a local DC (whether
this is an existing server that joins the new domain or a server provided by
the parent company I am unsure).

I know there are a lot of unknowns. If anyone has some real world experience
on similar projects and can advise on how it might go then I would value your
comments.

Kind Regards,
Phil.

Hello Philip,

Check out ADMT, depending on the OS:
3.0:
http://www.microsoft.com/downloads/d...displaylang=en

http://www.microsoft.com/downloads/d...displaylang=en

3.1:
http://www.microsoft.com/downloads/d...displaylang=en

http://www.microsoft.com/downloads/d...displaylang=en


Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> It has been proposed that our existing AD (domain.a.com) is merged to
> new parent company domain. I have never been involved in a similar
> project and was looking for some advice on the steps that may be
> involved so that I am prepped.
>
> Currently we run our own DNS / WINS / DHCP / Exchange.
>
> Exchange is to be replaced. I believe we will retain a local DC
> (whether this is an existing server that joins the new domain or a
> server provided by the parent company I am unsure).
>
> I know there are a lot of unknowns. If anyone has some real world
> experience on similar projects and can advise on how it might go then
> I would value your comments.
>
> Kind Regards,
> Phil.

"Philip" <> wrote in message
news:A887A590-ED86-4C19-9A81-...
> It has been proposed that our existing AD (domain.a.com) is merged to new
> parent company domain. I have never been involved in a similar project and
> was looking for some advice on the steps that may be involved so that I am
> prepped.
>
> Currently we run our own DNS / WINS / DHCP / Exchange.
>
> Exchange is to be replaced. I believe we will retain a local DC (whether
> this is an existing server that joins the new domain or a server provided
> by
> the parent company I am unsure).
>
> I know there are a lot of unknowns. If anyone has some real world
> experience
> on similar projects and can advise on how it might go then I would value
> your
> comments.
>
> Kind Regards,
> Phil.


There is a lot behind this and definitely need more specifics. If you have
your own AD forest, there is no way it will be 'mergred' rather the only
option is to migrate (uisng ADMT, as Meinolf supplied links and how-to's
for) your users, computer and groups, into their domain in their forest. If
they will still provide you administrative access, then it appears they will
provide you with a child domain they will have to setup, then you would
migrate (onve again using ADMT), into the new domain. As for Exchange,
depending on the versions, you will more than likely need Exmerge for
Ex2003, or the move-mailbox uitility in Ex 2007, once everything's been
migrated.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer


For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

"Efficiency is doing things right; effectiveness is doing the right
things." - Peter F. Drucker
http://twitter.com/acefekay

Thanks for the response. Yes we have our own AD Forest. It is unclear whether
I will be provided with administrative access. I get the feeling that they
will manage AD and not permit me access so migration to their domain using
ADMT seems the way it will go. Currently we deploy software via GP + have
numerous scripts / security groups (Global + Local), distribution groups
etc.....AD is structured Site OU / Department OU with Computer OU / User OU
within each department OU.

We also run SQL (domain account used for services) + SSRS uses AD security
groups to control access to the reports server.

Many Thanks,
Phil.

If using ADMT to migrate computers would desktops simply join the new domain
without the need to export/import settings (local profiles)?

"Ace Fekay [Microsoft Certified Trainer]" wrote:

> "Philip" <> wrote in message
> news:A887A590-ED86-4C19-9A81-...
> > It has been proposed that our existing AD (domain.a.com) is merged to new
> > parent company domain. I have never been involved in a similar project and
> > was looking for some advice on the steps that may be involved so that I am
> > prepped.
> >
> > Currently we run our own DNS / WINS / DHCP / Exchange.
> >
> > Exchange is to be replaced. I believe we will retain a local DC (whether
> > this is an existing server that joins the new domain or a server provided
> > by
> > the parent company I am unsure).
> >
> > I know there are a lot of unknowns. If anyone has some real world
> > experience
> > on similar projects and can advise on how it might go then I would value
> > your
> > comments.
> >
> > Kind Regards,
> > Phil.
>
>
> There is a lot behind this and definitely need more specifics. If you have
> your own AD forest, there is no way it will be 'mergred' rather the only
> option is to migrate (uisng ADMT, as Meinolf supplied links and how-to's
> for) your users, computer and groups, into their domain in their forest. If
> they will still provide you administrative access, then it appears they will
> provide you with a child domain they will have to setup, then you would
> migrate (onve again using ADMT), into the new domain. As for Exchange,
> depending on the versions, you will more than likely need Exmerge for
> Ex2003, or the move-mailbox uitility in Ex 2007, once everything's been
> migrated.
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
> Microsoft Certified Trainer
>
>
> For urgent issues, you may want to contact Microsoft PSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> "Efficiency is doing things right; effectiveness is doing the right
> things." - Peter F. Drucker
> http://twitter.com/acefekay
>
>

Hello Philip,

If everything works fine it should. I recommend that you create a test system
BEFORE to get familiar with ADMT and the procedures.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Thanks for the response. Yes we have our own AD Forest. It is unclear
> whether I will be provided with administrative access. I get the
> feeling that they will manage AD and not permit me access so migration
> to their domain using ADMT seems the way it will go. Currently we
> deploy software via GP + have numerous scripts / security groups
> (Global + Local), distribution groups etc.....AD is structured Site OU
> / Department OU with Computer OU / User OU within each department OU.
>
> We also run SQL (domain account used for services) + SSRS uses AD
> security groups to control access to the reports server.
>
> Many Thanks,
> Phil.
> If using ADMT to migrate computers would desktops simply join the new
> domain without the need to export/import settings (local profiles)?
>
> "Ace Fekay [Microsoft Certified Trainer]" wrote:
>
>> "Philip" <> wrote in message
>> news:A887A590-ED86-4C19-9A81-...
>>
>>> It has been proposed that our existing AD (domain.a.com) is merged
>>> to new parent company domain. I have never been involved in a
>>> similar project and was looking for some advice on the steps that
>>> may be involved so that I am prepped.
>>>
>>> Currently we run our own DNS / WINS / DHCP / Exchange.
>>>
>>> Exchange is to be replaced. I believe we will retain a local DC
>>> (whether
>>> this is an existing server that joins the new domain or a server
>>> provided
>>> by
>>> the parent company I am unsure).
>>> I know there are a lot of unknowns. If anyone has some real world
>>> experience
>>> on similar projects and can advise on how it might go then I would
>>> value
>>> your
>>> comments.
>>> Kind Regards,
>>> Phil.
>> There is a lot behind this and definitely need more specifics. If you
>> have your own AD forest, there is no way it will be 'mergred' rather
>> the only option is to migrate (uisng ADMT, as Meinolf supplied links
>> and how-to's for) your users, computer and groups, into their domain
>> in their forest. If they will still provide you administrative
>> access, then it appears they will provide you with a child domain
>> they will have to setup, then you would migrate (onve again using
>> ADMT), into the new domain. As for Exchange, depending on the
>> versions, you will more than likely need Exmerge for Ex2003, or the
>> move-mailbox uitility in Ex 2007, once everything's been migrated.
>>
>> -- Ace
>>
>> This posting is provided "AS-IS" with no warranties or guarantees and
>> confers no rights.
>>
>> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
>> Microsoft Certified Trainer
>>
>> For urgent issues, you may want to contact Microsoft PSS directly.
>> Please check http://support.microsoft.com for regional support phone
>> numbers.
>>
>> "Efficiency is doing things right; effectiveness is doing the right
>> things." - Peter F. Drucker
>> http://twitter.com/acefekay

"Philip" <> wrote in message
news:5F1A5523-350B-42F5-A01A-...
> Thanks for the response. Yes we have our own AD Forest. It is unclear
> whether
> I will be provided with administrative access. I get the feeling that they
> will manage AD and not permit me access so migration to their domain using
> ADMT seems the way it will go. Currently we deploy software via GP + have
> numerous scripts / security groups (Global + Local), distribution groups
> etc.....AD is structured Site OU / Department OU with Computer OU / User
> OU
> within each department OU.
>
> We also run SQL (domain account used for services) + SSRS uses AD security
> groups to control access to the reports server.
>
> Many Thanks,
> Phil.
>
> If using ADMT to migrate computers would desktops simply join the new
> domain
> without the need to export/import settings (local profiles)?
>

Phil,

In many migrations/acquisitions, that is usually the case. The other company
will usually take over and migrated employee roles will be re-evaluated for
their positions in the new environment. I am not totally surprised that you
will not have admin rights.

ADMT has provisions to opt to migrate computer accounts, groups, etc, so
yes, it has that option. With SIDHistory option, it will allow the old users
to use their old resources during the migration. However, ADMT will put
users into a target OU on the new side, where they will have to re-org the
users into their own current OU structure, whatever that may be on their
end. It will not follow the source because that is a specific design to each
domain.

SQL will need to moved manually, and the credentials adjusted to the new
domain.

Ace

Many thanks for taking time to reply to my post.
Phil.

"Ace Fekay [Microsoft Certified Trainer]" wrote:

> "Philip" <> wrote in message
> news:5F1A5523-350B-42F5-A01A-...
> > Thanks for the response. Yes we have our own AD Forest. It is unclear
> > whether
> > I will be provided with administrative access. I get the feeling that they
> > will manage AD and not permit me access so migration to their domain using
> > ADMT seems the way it will go. Currently we deploy software via GP + have
> > numerous scripts / security groups (Global + Local), distribution groups
> > etc.....AD is structured Site OU / Department OU with Computer OU / User
> > OU
> > within each department OU.
> >
> > We also run SQL (domain account used for services) + SSRS uses AD security
> > groups to control access to the reports server.
> >
> > Many Thanks,
> > Phil.
> >
> > If using ADMT to migrate computers would desktops simply join the new
> > domain
> > without the need to export/import settings (local profiles)?
> >
>
> Phil,
>
> In many migrations/acquisitions, that is usually the case. The other company
> will usually take over and migrated employee roles will be re-evaluated for
> their positions in the new environment. I am not totally surprised that you
> will not have admin rights.
>
> ADMT has provisions to opt to migrate computer accounts, groups, etc, so
> yes, it has that option. With SIDHistory option, it will allow the old users
> to use their old resources during the migration. However, ADMT will put
> users into a target OU on the new side, where they will have to re-org the
> users into their own current OU structure, whatever that may be on their
> end. It will not follow the source because that is a specific design to each
> domain.
>
> SQL will need to moved manually, and the credentials adjusted to the new
> domain.
>
> Ace
>
>

"Philip" <> wrote in message
newsA8865BA-8888-4AB5-BFA6-...
> Many thanks for taking time to reply to my post.
> Phil.
>


You are welcome, Phil. I hope it helped.

--
Ace