"Mrmystery44" <Mrmyster***@discussions.microsoft.com> wrote in message
news:3DB6D2E5-F9D2-466B-9E32-DEE8A5B5B12C@microsoft.com...
> Hi,
>
> I am very new to AD, so I apologize in advance is this is a very basic
> question.
>
> I am supporting computers spread out all over the USA, and have a
> inventory
> of spares if a computer fails.  The installed computers are members of a
> windows 2000 domain.  The spares are also, but are named SPARE001 (etc...)
> and have an ip address on a test/lab network.
>
> If an installed computer fails, what procedure should I use to swap the
> bad
> installed computer with the spare which would require renaming and
> re-addressing the spare (spare uses static IP addresses).
>
> Is it possible to rename and address the computer here on the test/lab
> lan,
> knowing that the moment I readdress it, it will not have any network
> connectivity, or is it better to wait until the computer is at the remote
> site, on the correct network, and rename and address it then?
>
> This was much simpler before the Domain was implemented :)
>
> Thanks,

"Paul Bergson" wrote:

> Why don't you use dhcp with dynamic dns.  When a system fails join the
> machine to the production domain and then ship it out.  If you follow that
> procedure all should work.  Once the machice arrives out in the field plug
> it in and it should be ready to roll.
>
>
>
> --
> Paul Bergson  MCT, MCSE, MCSA, Security+, CNE, CNA, CCA
> http://www.pbbergs.com
>
> Please no e-mails, any questions should be posted in the NewsGroup
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Mrmystery44" <Mrmyster***@discussions.microsoft.com> wrote in message
> news:3DB6D2E5-F9D2-466B-9E32-DEE8A5B5B12C@microsoft.com...
> > Hi,
> >
> > I am very new to AD, so I apologize in advance is this is a very basic
> > question.
> >
> > I am supporting computers spread out all over the USA, and have a
> > inventory
> > of spares if a computer fails.  The installed computers are members of a
> > windows 2000 domain.  The spares are also, but are named SPARE001 (etc...)
> > and have an ip address on a test/lab network.
> >
> > If an installed computer fails, what procedure should I use to swap the
> > bad
> > installed computer with the spare which would require renaming and
> > re-addressing the spare (spare uses static IP addresses).
> >
> > Is it possible to rename and address the computer here on the test/lab
> > lan,
> > knowing that the moment I readdress it, it will not have any network
> > connectivity, or is it better to wait until the computer is at the remote
> > site, on the correct network, and rename and address it then?
> >
> > This was much simpler before the Domain was implemented :)
> >
> > Thanks,
>
>
>

"Mrmystery44" <Mrmyster***@discussions.microsoft.com> wrote in message
news:4F9E0B53-2242-4A3E-B143-959D4FE73831@microsoft.com...
> Paul,
>
> The computer is used for process control.  Security and Controls
> guidelines
> for the company state that the address must be static, I'm assuming
> because a
> lot of old hardware that talks to it probably has hardcoded ip addresses.
> :(
>
> Thanks for the suggestion though.
> MM.
>
>
> "Paul Bergson" wrote:
>
>> Why don't you use dhcp with dynamic dns.  When a system fails join the
>> machine to the production domain and then ship it out.  If you follow
>> that
>> procedure all should work.  Once the machice arrives out in the field
>> plug
>> it in and it should be ready to roll.
>>
>>
>>
>> --
>> Paul Bergson  MCT, MCSE, MCSA, Security+, CNE, CNA, CCA
>> http://www.pbbergs.com
>>
>> Please no e-mails, any questions should be posted in the NewsGroup
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Mrmystery44" <Mrmyster***@discussions.microsoft.com> wrote in message
>> news:3DB6D2E5-F9D2-466B-9E32-DEE8A5B5B12C@microsoft.com...
>> > Hi,
>> >
>> > I am very new to AD, so I apologize in advance is this is a very basic
>> > question.
>> >
>> > I am supporting computers spread out all over the USA, and have a
>> > inventory
>> > of spares if a computer fails.  The installed computers are members of
>> > a
>> > windows 2000 domain.  The spares are also, but are named SPARE001
>> > (etc...)
>> > and have an ip address on a test/lab network.
>> >
>> > If an installed computer fails, what procedure should I use to swap the
>> > bad
>> > installed computer with the spare which would require renaming and
>> > re-addressing the spare (spare uses static IP addresses).
>> >
>> > Is it possible to rename and address the computer here on the test/lab
>> > lan,
>> > knowing that the moment I readdress it, it will not have any network
>> > connectivity, or is it better to wait until the computer is at the
>> > remote
>> > site, on the correct network, and rename and address it then?
>> >
>> > This was much simpler before the Domain was implemented :)
>> >
>> > Thanks,
>>
>>
>>