"hozzie" <hoz***@discussions.microsoft.com> wrote in message
news:6DCF61B2-80E7-49B3-89DD-178A23A7B69E@microsoft.com...
> In the past I've always ran the DCPROMO on site to pull down active
> directory, then fully configure.
>
> Has anyone DCPROMO in local site, then changed the IP settings to a remote
> subnet?
>
> I know I'll need to move server in sites and services.  But has anyone
> encountered replication or DNS problems doing this task?
>
> The issue is that I have a remote site with a faulty domain controller and
> it will be more cost effective and less time consuming to configure new
> machine locally, change IP settings to remote site, then ship for a user
> to
> connect, before completing final tests remotely.
>
> Any comments are appreciated.

"Marcin" <marcin@community.nospam> wrote in message
news:OPcSoKB$JHA.1336@TK2MSFTNGP05.phx.gbl...
> You should be able to do this - although you will need to move manually
> the domain controller to the appropriate site (also make sure to verify
> that its SRV records are registered in appropriate, site-specific parts of
> the DNS namespace.
> If you want to avoid this, you can create a local subnet, assign it to the
> remote site, and install/promo the DC while connected to it. Afterwards,
> you would simply need to change its IP address and modify the
> corresponding DNS A/PTR records...
> On a related subject, make sure that the carrier you choose has proper
> security measures in place...
>
> hth
> Marcin
>
> "hozzie" <hoz***@discussions.microsoft.com> wrote in message
> news:6DCF61B2-80E7-49B3-89DD-178A23A7B69E@microsoft.com...
>> In the past I've always ran the DCPROMO on site to pull down active
>> directory, then fully configure.
>>
>> Has anyone DCPROMO in local site, then changed the IP settings to a
>> remote
>> subnet?
>>
>> I know I'll need to move server in sites and services.  But has anyone
>> encountered replication or DNS problems doing this task?
>>
>> The issue is that I have a remote site with a faulty domain controller
>> and
>> it will be more cost effective and less time consuming to configure new
>> machine locally, change IP settings to remote site, then ship for a user
>> to
>> connect, before completing final tests remotely.
>>
>> Any comments are appreciated.
>
>

> In the past I've always ran the DCPROMO on site to pull down active
> directory, then fully configure.
>
> Has anyone DCPROMO in local site, then changed the IP settings to a
> remote subnet?
>
> I know I'll need to move server in sites and services.  But has anyone
> encountered replication or DNS problems doing this task?
>
> The issue is that I have a remote site with a faulty domain controller
> and it will be more cost effective and less time consuming to
> configure new machine locally, change IP settings to remote site, then
> ship for a user to connect, before completing final tests remotely.
>
> Any comments are appreciated.
>

"Meinolf Weber [MVP-DS]" wrote:

> Hello hozzie,
>
> You can change the ip address from a DC without any problem when you control
> that changes are correct in all DNS zones and the subfolders. Do not forget
> to change, if used, some application servers that maybe use an ip address
> instead of a server name.
>
> Also you have to adjust AD sites and services and maybe the clients need
> the new ip address if the server is also DNS server. Just change the ip,
> run ipconfig /flushdns and ipconfig /registerdns and restart the netlogon
> service. Then check replication.
>
> 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
>
>
> > In the past I've always ran the DCPROMO on site to pull down active
> > directory, then fully configure.
> >
> > Has anyone DCPROMO in local site, then changed the IP settings to a
> > remote subnet?
> >
> > I know I'll need to move server in sites and services.  But has anyone
> > encountered replication or DNS problems doing this task?
> >
> > The issue is that I have a remote site with a faulty domain controller
> > and it will be more cost effective and less time consuming to
> > configure new machine locally, change IP settings to remote site, then
> > ship for a user to connect, before completing final tests remotely.
> >
> > Any comments are appreciated.
> >
>
>
>

"Anderson Lacruz" wrote:

> It's important to verify if the domain controller is a DNS server as well
> with active directory integrated zone, modify the server options of the scope
> or scopes of the DHCP, because probably scopes were using the old DNS IP.
> Finally, as somebody told before you have to be careful with the LDAP
> applications which are working with the old IP instead of the FQDN of the
> domain.
>
> Regards
>
> Anderson Lacruz
>
> "Meinolf Weber [MVP-DS]" wrote:
>
> > Hello hozzie,
> >
> > You can change the ip address from a DC without any problem when you control
> > that changes are correct in all DNS zones and the subfolders. Do not forget
> > to change, if used, some application servers that maybe use an ip address
> > instead of a server name.
> >
> > Also you have to adjust AD sites and services and maybe the clients need
> > the new ip address if the server is also DNS server. Just change the ip,
> > run ipconfig /flushdns and ipconfig /registerdns and restart the netlogon
> > service. Then check replication.
> >
> > 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
> >
> >
> > > In the past I've always ran the DCPROMO on site to pull down active
> > > directory, then fully configure.
> > >
> > > Has anyone DCPROMO in local site, then changed the IP settings to a
> > > remote subnet?
> > >
> > > I know I'll need to move server in sites and services.  But has anyone
> > > encountered replication or DNS problems doing this task?
> > >
> > > The issue is that I have a remote site with a faulty domain controller
> > > and it will be more cost effective and less time consuming to
> > > configure new machine locally, change IP settings to remote site, then
> > > ship for a user to connect, before completing final tests remotely.
> > >
> > > Any comments are appreciated.
> > >
> >
> >
> >

> Thanks for all your comments - much appreciated.
>
> "Anderson Lacruz" wrote:
>
>> It's important to verify if the domain controller is a DNS server as
>> well with active directory integrated zone, modify the server options
>> of the scope or scopes of the DHCP, because probably scopes were
>> using the old DNS IP. Finally, as somebody told before you have to be
>> careful with the LDAP applications which are working with the old IP
>> instead of the FQDN of the domain.
>>
>> Regards
>>
>> Anderson Lacruz
>>
>> "Meinolf Weber [MVP-DS]" wrote:
>>
>>> Hello hozzie,
>>>
>>> You can change the ip address from a DC without any problem when you
>>> control that changes are correct in all DNS zones and the
>>> subfolders. Do not forget to change, if used, some application
>>> servers that maybe use an ip address instead of a server name.
>>>
>>> Also you have to adjust AD sites and services and maybe the clients
>>> need the new ip address if the server is also DNS server. Just
>>> change the ip, run ipconfig /flushdns and ipconfig /registerdns and
>>> restart the netlogon service. Then check replication.
>>>
>>> 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
>>>> In the past I've always ran the DCPROMO on site to pull down active
>>>> directory, then fully configure.
>>>>
>>>> Has anyone DCPROMO in local site, then changed the IP settings to a
>>>> remote subnet?
>>>>
>>>> I know I'll need to move server in sites and services.  But has
>>>> anyone encountered replication or DNS problems doing this task?
>>>>
>>>> The issue is that I have a remote site with a faulty domain
>>>> controller and it will be more cost effective and less time
>>>> consuming to configure new machine locally, change IP settings to
>>>> remote site, then ship for a user to connect, before completing
>>>> final tests remotely.
>>>>
>>>> Any comments are appreciated.
>>>>