Re: Pros/Cons of computer account deletions

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



If you are using AD DNS and DHCP, you should delte any computer in your
AD if it is no longer to be used. If you rename the computer, at the
computer, no need to touch the AD account. But if you physically remove
the PC from the network, delete it's AD account from the OU. There is
no problem with doing so as it relates to DNS and DHCP.

"Un joining" the domain is another method, which will "delete" the
account from the domain. It is basically doing the same thing.

.



Relevant Pages

  • Re: dynamic DNS not working.
    ... and before I wasn't using an account but have since created an account, ... user full control on the DNS servers with no change. ... the DHCP and removed from the client, ... option available in the DHCP server? ...
    (microsoft.public.windows.server.dns)
  • Re: DHCP security breach
    ... So you are saying that your servers are using DHCP and also ... Have your servers handle their own DNS registrations. ... Microsoft recommends to run DHCP under a low privilege account. ...
    (microsoft.public.win2000.security)
  • Re: DNSAPI Error and corrupt DNS records
    ... But...will it fix the fact that the computer account is not "right" on the ... DNS server list: ... Sent update to server: 10.153.3.50 ... Are these machines DHCP based or static? ...
    (microsoft.public.windows.server.networking)
  • Re: Old DNS records not purging - Scavenge
    ... > level in DNS for several zones. ... their old records when you rename them. ... And if a record is registered by DHCP, only the DHCP server can de-register ... dynamic updates, only the machine that registered the record can de-register ...
    (microsoft.public.windows.server.dns)
  • Re: DHCP security breach
    ... Microsoft recommends to run DHCP under a low privilege account. ... ACL that this account must have on DNS zones. ... What permissions should I give to the DHCP account on my DNS zone? ...
    (microsoft.public.win2000.security)