D
dhcp dude
since w2k sp1, you can use a special account for dhcp
server to use, in place of the dc machine account. so
dhcp can be on dc and the name hijackig by the dhcp
service is not a problem any more.
however, dhcp has another problem, it become owner of the
names it registered for, and if it is gone, nobody can do
anything on those records any more. the resolution is to
put the dhcp server into a dhcp proxy group. if a dhcp
server sitting on a dc, put it in this group will not be
a good idea, as then all user can change the dc related
records. using the special account, as long as the
account is not removed, everything will still be in
control.
it seems using the special account solved both the
problems, dosn't it?
server to use, in place of the dc machine account. so
dhcp can be on dc and the name hijackig by the dhcp
service is not a problem any more.
however, dhcp has another problem, it become owner of the
names it registered for, and if it is gone, nobody can do
anything on those records any more. the resolution is to
put the dhcp server into a dhcp proxy group. if a dhcp
server sitting on a dc, put it in this group will not be
a good idea, as then all user can change the dc related
records. using the special account, as long as the
account is not removed, everything will still be in
control.
it seems using the special account solved both the
problems, dosn't it?