server connections: quitĦ.Type “select operation target” Enter. Note: Windows Server 2003 Service Pack 1 eliminates the need for the above step.ĥ.Type “quit” Enter to return you to the metadata cleanup: prompt. server connections: connect to server Server2Ĭonnected to Server2 using credentials of locally logged on user. metadata cleanup: connectionsĤ.At the server connections: type “connect to server Server“ Enter, where Server is working domain controller, to clean up the metadata of the failed DC. ntdsutil: metadata cleanupģ.At the metadata cleanup: type “connections” Enter. Run NTDSUTIL.EXE – commands of NTDSUTIL will be opened PS D:\>ntdsutilĢ.At the Ntdsutil: type “metadata cleanup” Enter. We need to use NTDSUTIL.EXE (already part of Windows Server 2012 with installed DC).ġ. In other words make primary domain controller from Server2. The goal is to seize roles from Server1 to Server2 and remove old server computer account from AD. Finally use of NTDSUTIL will help but steps needed are quite hard so here are the steps. I started to seize the roles, but it is not so easy task when FSMO role holder is dead server. It is not easy task, because first of all it is needed to seize FSMO role to live domain controller. First of all I needed to install the server with same name and promote it to DC. Everything is lost, but one last DC in forest. SSD disk as system drive on Exchange server DC is not a good idea and one of my friends wanted to have it. Server2 was only DC GC Sharepoint server. Before error there was 1 Exchange server 2013 DC (Server1) and second server with backup DC (Server2).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |