How to properly move DHCP/WINS databases between Servers??

[plucky duck]

What is the proper procedure for doing so?

Also, I've tried specifying a user as a recovery agent. I can get to the part where I can successfully set him as the recovery agent, but when it comes time for him to decrypt a user-encrypted file, it always says "access is denied". Any ideas guys? The user's file is created and encrypted after a recovery agent is designated.

Also, one last thing, is it me or does DFS in W2K VERY flaky? I've done many labs in the past, and only on two occasions did it work (and it took awfully long too).


Thx.
Plucky

[DVNT1]

I'll pick one to answer...

DHCP:
1) stop & disable DHCP on server1
2) install & authorize DHCP on server2
3) copy %systemroot%\system2\DHCP from server1 to server2
4) Start DHCP on server1 and recompile all scopes

[plucky duck]

Now I'm assuming the above steps wouldn't be performed during business operations? Otherwise you'd be disrupting client needs by killing the DHCP server.

What does reconciling of the scope do?? Does it verify something??

Thx.
Plucky

[DVNT1]

Acutally the chances of disrupting clients may be very small on a DHCP move. It mostly depends on the IP lease time. The default of 8 days would allow plenty of time to move the DHCP data/server.

Typically DHCP clients try to renew the lease when half of the lease time has expired.

basic example...

1) DHCP client gets IP address
2) four days later client tries to renews the IP address
3) two more days pass and the client trys again
4) one more day passes and the client trys again
5) 12 hrs. pass...trys again
6) 6 hours...trys again
etc...

If at any time the lease is renewed then the clients start trying to renew again after four days (half the lease time).

If the lease fully expires, the client it gives up the IP address and typically quits trying. Windows 98 and newer clients give themselves an APIPA assigned address at that point.

If any client are restarted without the DHCP server being available then they will continue to use their previous IP address while trying to renew as explained in the previous example.


You should reconcile the scope to fix inconsistencies, such as incorrect or missing information for client IP addresses that are stored in scope lease information.