Computer Accounts do not appear converted completely after NT 4 upgrade to 2000 AD

I updated our NT4 network to 2000 Active Directory, all converted ok, but I
notice most of the workstations did not appear to have updated the DNS
server although all their settings were correct. I exmined the computer
name, the computers which did not update the DNS server, still had the old
workstation name withoout the domain suffix applied.

I read an article, which I can no longer locate, which said that there may
be an issue converting over some of the computer accounts. What I did to
correct this was to remove the computer from the domain, assign to a work
group, then rejoined the domain, added the AD user to the local admins,
restart, then all worked as expected, the compute now had the full dns
suffix and correctly registered the name in dns.

My question is, there are about 200 worksations on this network, is there a
better way to correct this.

thanks
Steve


.

Relevant Pages

  • Re: Which TCP/IP settings critical to join domain?
    ... the DCs are not configured with DNS. ... > the remote workstations lacked, ... > - workstations on the local subnet had no difficulty finding/joining yyy ...
    (microsoft.public.win2000.networking)
  • Re: Which TCP/IP settings critical to join domain?
    ... the DCs are not configured with DNS. ... The workstations in the same subnet as the DCs were able to join the ... >>Our DCs can write SRV records to the backbone DNS servers, ...
    (microsoft.public.win2000.networking)
  • Re: Remote Web Workplace connects to wrong desktop
    ... AD Computer Accounts which is what provides the lists of workstations available for RWW connections and then DNS and WINS tell the network how to resolve that name to and IP address. ... Send via Windows Mail on Vista Ultimate connected to SBS 2003 R2 ...
    (microsoft.public.backoffice.smallbiz)
  • Re: NEWBIE Question
    ... I have a printer on one of the workstations that I want to share, ... DC ONLY pointing to itself for DNS in their IP properties? ... Instead of the website you're using, I suggest to use OEx (Outlook Express ... Microsoft MVP - Windows Server Directory Services ...
    (microsoft.public.windows.server.networking)
  • Re: Very Slow(60mins) XP logon
    ... The DNS on the servers is set to internal only, workstations get their dns through dhcp which also sets them up for internal dns. ... The slow logon happens with any AD account. ...
    (microsoft.public.win2000.networking)