Scott:
1) The clients need to get rebooted after they log on to the AD domain for
the first time. Upon the next reboot the domain name in the Computer Name
tab should change to the DNS domain name - that is if the client
authenticates to the PDC since it's AD 2003.
2) The SUS problem could be related to problem #3.
3) IIRC, NT 4.0 DHCP server does not support DDNS. And no, having an NT 4.0
BDC would not cause this problem, per se. However, if the clients
authenticate to the BDC only, they will not process any GPOs since the BDC
knows nothing about GPOs because it's still NT 4.0.
There might be some other misconfigurations that have not manifested
themselves yet, but fix problem #3 first. And I would suggest you do more
research on the upgrade steps - see
http://www.microsoft.com/windowsserv...g/default.mspx.
Regards,
Martin
MCSA: M
"Scott" <(E-Mail Removed)> wrote in message
news:121301c4fa6c$5e700c70$(E-Mail Removed)...
>I have migrated my NT 4.0 PDC to 2003 and AD. The upgrade
> was successful, and the clients (XPPro) can login into the
> domain. The problems I am having are:
>
> --The domain name on a couple of the existing workstations
> was automatically changed to the DNS name of the domain.
> While others still remain named the NETBios name of the
> domain. (Looking at the Computer Name Properties Tab)
>
> --I also have created a Default Domain Group Policy item
> to direct the clients to my SUS server. Unfortunately,
> none of the clients are using the SUS server, and looking
> to MS for the Updates.
>
> --The dynamic DNS is not updating for the clients. I
> placed the DNS IP Address as the clients primary DNS
> server address, and none are dynamically creating resourse
> records. The DHCP server is on the BDC, running NT 4.0.
>
> Any help would be appreciated!
>
>
>
> I do have a BDC still running NT 4.0, is this why? Or is
> there another cause?
>