Re: Old data after domain rename

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hello Simon,

I checked the MPS Report you sent me. I think your domain renaming is
totally successful. About the records you found:
1, The DNS srv records you found in the netdiag always have a warning
message indicating the related server name doesn't exist accompanied. Since
the old domain DNS zone is gone, you can remove these srv records safely.
2, I'm not sure why netdiag.log has extra SPN registration records. I
suggest we check them out in AD with adsiedit.msc manually.
3, Regarding the registry keys. I think we can backup first and edit them
to match new domain name manually.

Here're the steps to check server SPN records:
1, Install Support Tools. You can locate the install file in support\tools
in installation disk.
2, Run the command "adsiedit.msc".
3, Locate DC's container in Domain partition.
4, Check the servicePrincipalName in the properties of the DC container.
Since there's no more DNS records pointing clients to DC with the old
domain name, I think it's safe to remove the SPN records with old domain
name.

I hope the information above can address your concerns. If anything is
unclear, please feel free to let us know.

Sean Cai, MCSE2000
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

.

Relevant Pages

  • Very Slow Logon --- Applying Settings Takes forever
    ... I installed a Windows 2000 Server with no DNS and so it did not create the ... Now logging in is unbearably slow and takes forever. ... I remeber I had this problem once before and I had to install DNS and then ... manually create the srv records to fix the slow logon. ...
    (microsoft.public.win2000.security)
  • Re: Adding 2nd Domain Controller- Question
    ... The first DC you install as a DC requires a DNS infrastructure that can ... support dynamic updates and SRV records, so I am fairly sure you ...
    (microsoft.public.windows.server.general)
  • Re: Stupidest Mistake in AD History - Its almost ingenious, almost EVIL
    ... SRV records the NETLOGON service is registering in DNS. ... is it better to install DNS or let AD do it on the fly during DC ...
    (microsoft.public.windows.server.active_directory)
  • Re: Preparing network connection after AD install
    ... I didn't install exchange yet. ... known symptoms of having exchange installed on DC and bad DNS ... Do not place the ISP DNS server or any other DNS on the ...
    (microsoft.public.windows.server.active_directory)
  • Re: Domain users
    ... for the DNS Server. ... User in the Domain and an Administrator in Windows XP still has all its ... > "George Hester" wrote in message ... >>> As a regular user they will not be able to install much of anything. ...
    (microsoft.public.win2000.group_policy)