We have an existing Windows 2003 server (upgraded from NT 4) and we need to
move the Active Directory / Domain to a new replacement server.

We tried adding the new machine to the existing active directory domain then
taking it offline and seizing all of the FSMO roles. We then installed DNS on
the new machine and recreated the forward zones (AD-Integrated) for the
active directory but we can't change their replication scope so that seems
like a lost cause.

So does anyone know if there is the an easy way of moving the Active
Directory to the new machine or alternatively just fixing the DNS problem ?

> We tried adding the new machine to the existing active directory domain
> then
> taking it offline and seizing all of the FSMO roles. We


Why take it offline and seize the FSMO roles?

Why not transfer the FSMO roles w/ the DC online. Are you trying to make a
copy that will never connect to the original domain?


DDS

"Mr Hives" <MrHives@discussions.microsoft.com> wrote in message
news:AAA9705E-1674-4371-87A6-52A7B0C6CA67@microsoft.com...
> We have an existing Windows 2003 server (upgraded from NT 4) and we need
> to
> move the Active Directory / Domain to a new replacement server.
>
> We tried adding the new machine to the existing active directory domain
> then
> taking it offline and seizing all of the FSMO roles. We then installed DNS
> on
> the new machine and recreated the forward zones (AD-Integrated) for the
> active directory but we can't change their replication scope so that seems
> like a lost cause.
>
> So does anyone know if there is the an easy way of moving the Active
> Directory to the new machine or alternatively just fixing the DNS problem
> ?
>

I've sorted it now. I think the problem was down to me being a bit hasty with
the removal of the old server and not leaving a long enough time gap between
FSMO role transfers, DNS setup, etc. I also left the original server online
this time and ran dcpromo to demote it. All seem to be well but it's not 100%
finished yet so there's still time for something else to got wrong.

"Danny Sanders" wrote:

> > We tried adding the new machine to the existing active directory domain
> > then
> > taking it offline and seizing all of the FSMO roles. We
>
>
> Why take it offline and seize the FSMO roles?
>
> Why not transfer the FSMO roles w/ the DC online. Are you trying to make a
> copy that will never connect to the original domain?
>
>
> DDS
>
> "Mr Hives" <MrHives@discussions.microsoft.com> wrote in message
> news:AAA9705E-1674-4371-87A6-52A7B0C6CA67@microsoft.com...
> > We have an existing Windows 2003 server (upgraded from NT 4) and we need
> > to
> > move the Active Directory / Domain to a new replacement server.
> >
> > We tried adding the new machine to the existing active directory domain
> > then
> > taking it offline and seizing all of the FSMO roles. We then installed DNS
> > on
> > the new machine and recreated the forward zones (AD-Integrated) for the
> > active directory but we can't change their replication scope so that seems
> > like a lost cause.
> >
> > So does anyone know if there is the an easy way of moving the Active
> > Directory to the new machine or alternatively just fixing the DNS problem
> > ?
> >
>
>
>