Replacing a server on the domain - query

[Lex]

Should I envisage a problem if I have two servers and only one of them are on the domain.

I want to remove one of them and replace it with the other server and called it the same name on the same IP address.

Am I right saying there shouldn't be any problem in theory?

 

[Lex]

What roles does the server have?

Member server. It's just going to run sql server. It's going to be used as a test server for development.

 

[Lex]

All you will need to do is remove the old server from the domain, and then disconnect the network cable, or change the IP address, setup the other machine on the network ideally with the same IP and re-join it to the domain.

Shouldn't be a problem.

all good. Until i reminded the lamer DBA that it was a 32bit version i installed as that was the disk he gave me. Now i gotto go back through it all and install the 64bit as he made a mistake. Bit school boy i guess i should have checked before the install.

 

[Lex]

All you will need to do is remove the old server from the domain, and then disconnect the network cable, or change the IP address, setup the other machine on the network ideally with the same IP and re-join it to the domain.

Shouldn't be a problem.

The Network Consultant said that it screwed up Active Directory with multiple SIDs. Could this be true? And how can i check this error is true to which he says? I don't believe him.

 

[Lex]

When you join the new machine to the domain it will get a new SID. As long as the SIDS are unqiue then shouldn't be a problem.

If you are worried about it then you can always remove the first machine from the domain first of all to remove it from AD.

I built 4 machines off the same VMWare image. As the base image has no Domain join then although 4-5 machines have the same SID initially, when it joins the Domain they get seperate unique SID. As such all 4 machines run fine on my domain.

If there are two duplicae SIDS, how do you remove a SID from AD domain?
How can i check a Servers SID? And where would i see this error?

 

[Lex]

IIRC SIDs have been totally dynamic since the introduction of AD away from NT4, so I don't think you need to worry about that.

Burnsy

It's not me that's bothered. It's the network consultant who thinks it bares high significance in terms of AD.

 

[Lex]

If you delete the old server from AD (you need to do this as they won't have the same GUIDs) and redomain the new one with the same name and IP you won't have a problem with SIDs.

Burnsy

okay. But how can i SEE that there is a SIDs problem? in the first place? Where would this error be located?