R
Roger Levy
I've been sniffing DHCP messages and I have a tip that I haven't seen before.
I'd appreciate if some real experts can comment on my observations.
For a networked device that you will clone you should:
1. Disable APIPA for the entire computer as described in KB244268 by adding
Extra Registry Data to your configuration.
2. Execute FBA with all ethernet cables disconnected, or more prescisely with no
DHCP server available.
If you have DHCP available during FBA your target will get a valid DHCP address
and it will "remember" this address such that after deployment every machine
will ask for this address in its initial DHCP Discover message. At best only
one machine can get the address and if the development network is different than
the deployed network, no machines are likely to be able to get that address.
See below for a comparable description of what happens in this case.
If you do not have DHCP available during deployment but you do not disable APIPA
then your target will ask for a 169.254.x.y address in its initial DHCP Discover
message. I observed the following DHCP message scenario in this case (SP2):
Client Discover with 169.254.x.y requested
Server Offer with different address
Client waits 15 seconds
Client Discover with 169.254.x.y requested
Server Offer with different address
Client waits 35 seconds
Client Discover with no specific address requested
Server Offer with an address
Client accepts address, protocol completes
This protocol sequence wastes 50 seconds before the network is ready that are
not wasted if you follow the 2 steps I recommended.
Roger
I'd appreciate if some real experts can comment on my observations.
For a networked device that you will clone you should:
1. Disable APIPA for the entire computer as described in KB244268 by adding
Extra Registry Data to your configuration.
2. Execute FBA with all ethernet cables disconnected, or more prescisely with no
DHCP server available.
If you have DHCP available during FBA your target will get a valid DHCP address
and it will "remember" this address such that after deployment every machine
will ask for this address in its initial DHCP Discover message. At best only
one machine can get the address and if the development network is different than
the deployed network, no machines are likely to be able to get that address.
See below for a comparable description of what happens in this case.
If you do not have DHCP available during deployment but you do not disable APIPA
then your target will ask for a 169.254.x.y address in its initial DHCP Discover
message. I observed the following DHCP message scenario in this case (SP2):
Client Discover with 169.254.x.y requested
Server Offer with different address
Client waits 15 seconds
Client Discover with 169.254.x.y requested
Server Offer with different address
Client waits 35 seconds
Client Discover with no specific address requested
Server Offer with an address
Client accepts address, protocol completes
This protocol sequence wastes 50 seconds before the network is ready that are
not wasted if you follow the 2 steps I recommended.
Roger