> very cool so can the tool do the backup and restore all on its own? or do
> i
> need to folow KB 325473 in conjunction with the tool?
>
> Thanks
>
>
> "Joe Cormane" wrote:
>
>> A perfect tool for this is dhcpexim.exe
>>
>>
http://www.microsoft.com/downloads/details.aspx?familyid=3603AE26-81F0-478A-836C-B31ED463AF5E&displaylang=en>>
>>
http://support.microsoft.com/kb/325473>>
>> It works extremely well, though keep in mind that it has some gotchas
>> that
>> are very esasy to remedy:
>>
>>
http://support.microsoft.com/kb/287031>>
>> "skip" <skip[ at ]discussions.microsoft.com> wrote in message
>> news:3B463FB4-DB94-41AB-8B67-82C57991F31A[ at ]microsoft.com...
>> > Hello all
>> >
>> > The internal environment is all 2003 native mode AD all AD server are
>> > 2003
>> > sp1. Currenty we have a 2000 non domain member DHCP server that is
>> > configured
>> > with all internal scopes. The DHCP server is configured to update the
>> > clients
>> > DHCP info in DNS. All DNS zones are configured for secure dynamic
>> > updates.
>> > Because the DHCP server is a non domain member and DNS is confifgured
>> > for
>> > secure updates only how is it possible for the DHCP server to update
>> > the
>> > client machine in DNS?
>> >
>> > Also I am noticing that the ip address that is being assigned via DHCP
>> > to
>> > the XP client is not always the same ip address in DNS and this is
>> > causing
>> > a
>> > name resolution issue.
>> >
>> > I also read that in order for the DHCP server to update the client in
>> > DNS
>> > when secure dynamic updates are enabled that the DHCP server needs to
>> > be
>> > in
>> > the DnsUpdateProxy group, i cant add our DHCP server to this group
>> > because
>> > its a non domain member. I need to get out of this mess how do i backup
>> > the
>> > 2000 non domain member DHCP server and inport all the scop settings
>> > into a
>> > 2003 domain member DHCP server?
>> >
>> > Many thanks
>>
>>
>>