Re: Automatic workstation domain registration w/ new AD server?
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Mon, 26 Feb 2007 17:12:01 -0600
"Chris Lukowski" <ChrisLukowski@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4333F424-3D0B-431E-BA2B-07095F77A285@xxxxxxxxxxxxxxxx
We just upgraded from an NT4 domain to a Win2K3 AD domain. Instead of our
domain being just [company] as it was in NT4, our domain is now
[company].local . Our workstations have no problem signing on to the new
domain (at least we assume they're signing onto our new PDC and not our
old
NT4 BDC that still is live) but when I go to the My Computer Properties it
still shows the domain as [company] and not [company].local.
It is showing the name you put on the clients -- that is perfectly fine.
You really have TWO names for the domain, one DNS and one legacy
NetBIOS name, generally these should be similar, e.g., company and
company.local with the leftmost DNS label used for the NetBIOS
version.
Please don't
tell me that we have to go to every PC and manually change the domain.
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.
I've
also noticed that these PCs aren't sending any dynamic DNS records to our
new
DNS server via DHCP. Only the PCs we've manually changed the domain are
doing
this. Hmm. Please help.
That is (partly) because you have not yet set the Primary DNS Suffix (above)
in
the SYSTEM CONTROL panel.
--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)
.
- Prev by Date: Re: Trust between two Forests Fail
- Next by Date: Re: Active Directory in an Internal Network Containing Firewalls
- Previous by thread: Re: Error when trying to run DCPROMO on Windows 2003 R2
- Next by thread: Re: Automatic workstation domain registration w/ new AD server?
- Index(es):
Relevant Pages
|
Loading