kanoswrx
Wed May 14 07:45:51 PDT 2008
On May 9, 6:03=A0pm, "Richard Mueller [MVP]" <rlmueller-
nos...@ameritech.nospam.net> wrote:
> <kanos...@gmail.com> wrote in message
>
> news:f96828e3-a0e7-4934-baa8-7acbf0e1097b@m3g2000hsc.googlegroups.com...
>
> >I recently renamed a server, lets just say from ServerA to ServerB.
> > This server was a member of some local groups on another comptuer,
> > lets call this WorkstationA. =A0It was also a member of some groups in
> > AD. =A0 Now all the groups in AD currently show the server with the new
> > name "ServerB". =A0Howerver the local group membership on WorkstationA
> > still shows "ServerA". =A0When I try to remove "ServerA" it lets me
> > delete it just fine, I click Add, type in "ServerB" and it finds it
> > ok, I then see it in the list. =A0But as soon as I click Apply, it
> > changes the name back to "ServerA"
>
> > Does anyone know why this is happening and how to fix it? =A0DNS shows
> > everything is correct, group membership in AD is all correct. =A0It's
> > only this one workstation which keeps showing the old computer name.
>
> > Thanks
>
> A quick guess is that when you renamed the server you changed its Common
> Name from "ServerA" to "ServerB", but left the sAMAcountName as "ServerA$"=
> so the NetBIOS name of the machine is still "ServerA". The local SAM accou=
nt
> database used for local accounts is blind to Common Names (the value of th=
e
> cn attribute) and uses NetBIOS names. When you browse for the computer, th=
e
> object with cn=3DServerB is found by the GUI, but the membership can only =
be
> saved in the local group as ServerA, the NetBIOS name, or actually, <NetBI=
OS
> name of domain>\<NetBIOS name of computer>.
>
> If this is correct, change the sAMAccountName attribute of the server to
> "ServerB$".
>
> --
> Richard Mueller
> MVP Directory Services
> Hilltop Lab -
http://www.rlmueller.net
> --
Thats what I thought at first as well, unfortunetly that wasn't it.
It turns out it just needed more time to update I guess. I let it sit
a couple days and I came back and it was fixed, the new name was
displayed. Go figure.