Exchange 2010 Service Pack 2 and Same SID issue on a VM
Hello Everyone,
we still runs Exchange 2010 and haven't upgraded to SP1 or SP2 because of an issue with same SID issue and exchange can possibly brake if 2 exchange server share same SID. unfortunately when we built the Exchange servers, we cloned from one to another and our CAS and HT share same SID.
Is this still an issue if i upgrade to SP2? i don't want my Exchange to brake. does anyone upgrade exchange server share same SID and encounter any issues?
Thanks for your help in advance!
we still runs Exchange 2010 and haven't upgraded to SP1 or SP2 because of an issue with same SID issue and exchange can possibly brake if 2 exchange server share same SID. unfortunately when we built the Exchange servers, we cloned from one to another and our CAS and HT share same SID.
Is this still an issue if i upgrade to SP2? i don't want my Exchange to brake. does anyone upgrade exchange server share same SID and encounter any issues?
Thanks for your help in advance!
ASKER
No, i dont have any issues with these servers now. Our CAS and HT same SID and its been like this for almost 2 years without any issues
The Service Pack is not going to make any difference to the operation of the Servers.
You mentioned you cloned your Exchange 2010 server, did you follow any of the recommended methods for cloning an Exchagne 2010 server? I have never tried cloning an Exchange server myself for fear of duplicate SIDS and other issues? What the orginal issues sysprep'd. From the articles below other have not cloned the OS but exported and imported various Exchange configs..
http://technet.microsoft.com/en-us/library/aa996008(v=exchg.141).aspx
http://exchangeserverpro.com/clone-mailbox-database-configuration
http://technet.microsoft.com/en-us/library/aa996008(v=exchg.141).aspx
http://exchangeserverpro.com/clone-mailbox-database-configuration
ASKER
i haven't cloned any exchange server after exchange installed. i cloned the windows server and installed exchange separately. But now CAS and HT share same SID.
All objects must have a unique SID in AD otherwise you will run into network authentication problems. I'm a bit puzzled at the fact that your are not having any network problem given the fact you have two server with the same SID.
Can you please upload the results of the following commands:
1) dcdiag /v/e >c:\dcdiag.txt
2) Result of the "check duplicate sid" command, from NTDSUTIL http://support.microsoft.com/kb/315062
Can you please upload the results of the following commands:
1) dcdiag /v/e >c:\dcdiag.txt
2) Result of the "check duplicate sid" command, from NTDSUTIL http://support.microsoft.com/kb/315062
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
it's not normal for two servers to have the same SID!
have a read of this Article
The Machine SID Duplication Myth