Re: Automatic workstation domain registration w/ new AD server?

So, just to be clear, what you recommend I do in order to make sure each PC
is "fully" integrated into our domain and therefore able to participate in
secure dynamic DNS updates via DHCP is to go into

System->Computer Name->Change->More->

and add [company].local into the "Primary DNS suffix of this computer"
dialog box with the "Change primary DNS suffix when domain membership
changes" box checked. Am I right? My collegue was actually changing the
domain from [company] to [company].local. I'm not sure if that is a good or
bad way of doing it but I just want to get this right. The good news is that
so far WINS is being used as a backup and everybody is able to authenticate
fine so we can afford to take our time with this. Your help is much
appreciated.

BTW, I noticed on DNS this morning that some new entries were added by
machines that we haven't touched, but the entries are nowhere near the amount
of new DHCP leases we have. Weird.

"Herb Martin" wrote:


"Chris Lukowski" <ChrisLukowski@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6BCD3802-BDDA-4832-9E01-32B703FE9B3A@xxxxxxxxxxxxxxxx

Good news: As long as they authenticate you don't need to do this.

BAD News: You really should change each of these machines to use the
correct Primary DNS Suffix in that SAME dialogs.

Is there a way to push this either through group policy or a DHCP setting?

You can pretty much set anything with a Group Policy but this stuff is
supposed to be set ahead of time and there isn't (to my knowledge) a
preset GPO slot for it.

It can also be set with DHCP scope options approximately but the machines
seem to be much healthier if they have this set manually.

I have never investigated how bad such things are but we get a LOT
of reports here from people who have done it incompletely and are
having trouble -- especially with dynamic registrations -- and I ensure
that all of my machines (and my clients) are set correctly and manually
when they are installed.

Right now the only problem we see is dynamic DNS not working. We have a
WINS
server still up and running so I get the feeling that's why things aren't
uglier than they are. BTW, what does SAME stand for? Thanks for the help!

The "same one" -- I was merely emphasizing that key word and point -- this
stuff needs to be set in the System Control Panel rather than trying to
patch
it on the NIC settings.


--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)



.

Relevant Pages

  • Re: Moved DHCP server to DC, now only works for domain users
    ... Machines get an IP Config before the user can even login in the first ... If a machine got a Config from the Linksys box then it will keep ... "alive" it will try the Linksys box even of the Linksys DHCP Service ...
    (microsoft.public.windows.server.networking)
  • Re: Moved DHCP server to DC, now only works for domain users
    ... Machines get an IP Config before the user can even login in the first ... If a machine got a Config from the Linksys box then it will keep ... "alive" it will try the Linksys box even of the Linksys DHCP Service ...
    (microsoft.public.windows.server.networking)
  • Re: Dnsmasq and resolvconf was Re: AAAARGHHHHH - aptitude hosed my system
    ... >> Disable the DHCP server on the router. ... >> Use a static configuration on the machine with dnsmasq installed. ... If your networked machines all get their network configuration through ...
    (Debian-User)
  • Re: DHCP configuration of superscopes
    ... > clients and a b.local client uses the a.local DHCP server it would ... It won't affect logons since the client side ... the Primary DNS Suffix will be the domain name its ... Kevin Goodnecht (another MVP) discussing it as well: ...
    (microsoft.public.win2000.dns)
  • Re: Continuing internet oddities
    ... From your bellsouth address and the fact that you have DHCP, I presume you are also have to contend with PPPoE. ... Boot the old machine from the SmoothWall CD, follow the installation dialogue, and in twenty or thirty minutes you shall have a firewall/router configured for PPPoE. ... SmoothWall can act as a DHCP server for your local area network; or you may assign static IP addresses to the machines in your LAN. ...
    (Debian-User)