|
I agree with Daniel – I believe that netsh
will do a fine job of migrating scopes and scope options but not leases.
However, leases should not be too much of an issue so long as you instruct the
DHCP server to perform conflict detection (assumes that ICMP is not blocked on
your network). A set of commands something like the
following perform the migration for you. From a command prompt on the existing DHCP
server: Netsh dhcp server \\existing_dhcp_server export c:\dhcp_info.txt
all From a command prompt on the new DHCP
server: Netsh dhcp server \\existing_dhcp_server import \\existing_dhcp_server\c$\dhcp_info.txt
all Now keep in mind that this will export
everything and import everything. I would suggest ensuring that the new DHCP
server is at the time of import not authorized in the AD or at least in a state
that no clients will attempt to use it. After the import you can retrofit any
of the imported data as necessary, such as altering or removing scopes or
options. If you need to be more selective about
what you export from the existing server, you will want to use the dump command
instead and the massage the output so that you can use the add command on the
new DHCP server. HTH Aric From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Conrad, Daniel C Mr. Nortel
Government Solutions Past experience, NETSH will migrate the scopes but you use the backup/restore
process for the leases (if you want them). D From:
[EMAIL PROTECTED] on behalf of Matheesha Weerasinghe Havent
played with it for a while so I cant answer unless I fire up a |
Title: Re: [ActiveDir] DHCP migration(OT)
- RE: [ActiveDir] DHCP migr... Bernard, Aric
- Re: [ActiveDir] DHCP... Tom Kern
- RE: [ActiveDir] ... deji
- RE: [ActiveDir] ... Ken Schaefer
- RE: [ActiveDir] DHCP... Conrad, Daniel C Mr. Nortel Government Solutions
