Thanks for the reply and the information.
I am sure that I have tried this already but I will try again.
Do you know of a resource that explains in detail what processes occur when
the DHCP Server services are stopped and restarted?
Thanks
"Doug Sherman [MVP]" wrote:
> Check server properties and see if a backup path is set - try forcing a
> backup. See:
>
> http://technet2.microsoft.com/Window...7-7639-483e-b7
> 8e-b88202f6f5191033.mspx
>
> and
>
> http://technet2.microsoft.com/Window...f-9e06-48f6-ab
> 67-050ff95307101033.mspx
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>
> "LLDallas" <(E-Mail Removed)> wrote in message
> news:B517E64A-C499-409E-ACC7-(E-Mail Removed)...
> > Environment:
> > Windows Server 2003
> > Active Directory
> >
> > Server Roles:
> > DC
> > DHCP/DNS server
> > Application server
> >
> > Background:
> > When server was productionalized, the DHCP configuration was migrated from
> a
> > NT4 PDC (via DHCPexim) and imported into the Win2k3 server via 'netsh dhcp
> > server import <name.txt> all'
> >
> > Issue:
> > For some reason, the DNS scope options were not migrated to the Win2k3
> DHCP
> > server. Seemingly, this was not a serious issue because we are able to
> simply
> > add the settings manually. The manual modification works. However, the
> issue
> > is that whenever DHCP services are restarted (due to reboot, etc) the
> > original configuration of the DHCP server is returned. The original
> > configuration, of course, does not include the DNS scope options.
> >
> > Request:
> > Please reply with the method/workaround/fix to enable the DHCP
> configuration
> > with the correct scope options to also be the restore configuration.
> >
> > Thanks
> >
> >
> >
> >
> >
>
>
>