2008 domain controller rename

i recently renamed a one of my 2008 domain controllers. everything
seems to be working correctly but when i have a look at the spn's
either from adsiedit or setspn -l it shows both old and new server
name records. i manually deleted the old name spn's but they came
back.

i renamed a total of 2 and both are doing the same thing.

neither one is a fsmo holder

Howdie!

RC schrieb:
> i recently renamed a one of my 2008 domain controllers. everything
> seems to be working correctly but when i have a look at the spn's
> either from adsiedit or setspn -l it shows both old and new server
> name records. i manually deleted the old name spn's but they came
> back.
>
> i renamed a total of 2 and both are doing the same thing.

How did you go about removing the old records? Did you remove the DNS
records specifically or in addition to the SPNs held by the machine?

Cheers,
Florian
--
Microsoft MVP - Group Policy
eMail: prename [at] frickelsoft [dot] net.
blog: http://www.frickelsoft.net/blog.
ANY advice you get on the Newsgroups should be tested thoroughly in your
lab.

using adsiedit i removed all the old spn's. also manually deleted the
old dns records that were still lingering.

I believe I resolved the issue:

After renaming the DC, the following attribute had a value with the
old name (msDS-AdditionalDnsHostName). i remove the value and
restarted the ADDS services. so far so good.

not sure why the rename went so sloppy. I used the netdom command and
everything changed without any problems whatsoever. the only issue was
the amount of time it took to sync throughout the forest. I guess I
should make a note of this if there is a need to rename another dc.

Hello RC,

Even if renaming is supported i would try to avoid this in any case.

Also you should follow exactly the steps described in:
http://technet.microsoft.com/en-us/l...51(WS.10).aspx

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> I believe I resolved the issue:
>
> After renaming the DC, the following attribute had a value with the
> old name (msDS-AdditionalDnsHostName). i remove the value and
> restarted the ADDS services. so far so good.
>
> not sure why the rename went so sloppy. I used the netdom command and
> everything changed without any problems whatsoever. the only issue was
> the amount of time it took to sync throughout the forest. I guess I
> should make a note of this if there is a need to rename another dc.
>

i agree but it was needed.

That is the article I used for this operation. I am very familiar with
the proceedure and have done so in the past without any issue. I
should have dug deeped into the associated attributes on the obj as I
would have resolved the issue in a couple minutes vs a couple hours.

in the end no harm done. just annoying to say the least.

again thanks!