擬化檔案網域控制站疑難排解Virtualized Domain Controller Troubleshooting

適用於:Windows Server 2016、Windows Server 2012 R2、Windows Server 2012Applies To: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012

本主題提供疑難排解模擬的網域控制站功能詳細的方法。This topic provides detailed methodology on troubleshooting the virtualized domain controller feature.

簡介Introduction

以改善您的疑難排解技術最重要的方式是實驗室測試的組建,並嚴格檢查 [正常運作的案例。The most important way to improve your troubleshooting skills is build a test lab and rigorously examine normal, working scenarios. 如果您遇到錯誤,有更多明顯並了解,因為您,並需要實心基本知識網域控制站升級的運作方式的簡單。If you encounter errors, they are more obvious and easy to understand, since you then have a solid foundation of how domain controller promotion works. 這也可讓您建置您分析及網路分析技巧。This also allows you to build your analysis and network analysis skills. 這會所有分散式的系統技術,不只是模擬的網域控制站部署。This goes for all distributed systems technologies, not just virtualized domain controller deployment.

重要進階疑難排解網域控制站設定的項目︰The critical elements to advanced troubleshooting of domain controller configuration are:

  1. 線性分析加上焦,並注意詳細資料。Linear analysis combined with focus and attention to detail.

  2. 了解網路擷取分析Understanding network capture analysis

  3. 了解建登Understanding the built-in logs

第一次並第二種超出範圍本主題中,但第三個可以將某些詳細資料所述。The first and second are beyond the scope of this topic, but the third can be explained in some detail. 模擬的網域控制站疑難排解需要邏輯和線性的方法。Virtualized domain controller troubleshooting requires a logical and linear method. 關鍵在於接近使用所提供的資料的問題,以及您已登入與提供的輸出用完時,只信複雜的工具和分析。The key is to approach the issue using the data provided and only resort to complex tools and analysis when you have exhausted the provided output and logging.

網域控制站複製疑難排解擬化檔案Troubleshooting virtualized domain controller cloning

這區段鍵盤保護蓋:This sections covers:

疑難排解策略模擬的網域控制站複製依照此一般格式:The troubleshooting strategy for virtualized domain controller cloning follows this general format:

virtual 俠疑難排解

疑難排解工具Tools for Troubleshooting

登入選項Logging Options

建登的最重要的網域控制站複製問題的疑難排解工具。The built-in logs are the most important tool for troubleshooting issues with domain controller cloning. 所有的這些登的功能和最大的詳細資訊,預設設定。All of these logs are enabled and configured for maximum verbosity, by default.

操作Operation 登入Log
複製Cloning 事件 viewer\Windows logs\System- Event viewer\Windows logs\System
事件 viewer\Applications 和服務 logs\Directory 服務- Event viewer\Applications and services logs\Directory Service
-%systemroot%\debug\dcpromo.log- %systemroot%\debug\dcpromo.log
促銷Promotion -%systemroot%\debug\dcpromo.log- %systemroot%\debug\dcpromo.log
事件 viewer\Applications 和服務 logs\Directory 服務- Event viewer\Applications and services logs\Directory Service
事件 viewer\Windows logs\System- Event viewer\Windows logs\System
事件 viewer\Applications 和服務 logs\File 複寫服務- Event viewer\Applications and services logs\File Replication Service
事件 viewer\Applications 和服務 logs\DFS 複寫- Event viewer\Applications and services logs\DFS Replication

工具和疑難排解網域控制站設定的命令Tools and Commands for Troubleshooting Domain Controller Configuration

若要登不解釋問題的疑難排解,使用下列工具做為起點:To troubleshoot issues not explained by the logs, use the following tools as a starting point:

  • Dcdiag.exeDcdiag.exe

  • Repadmin.exeRepadmin.exe

  • 網路監視器 3.4Network Monitor 3.4

一般方法,以取得疑難排解網域控制站複製General Methodology for Troubleshooting Domain Controller Cloning

  1. VM 開機至 DS 修復模式 (DSRM)?Is the VM booting into DS Repair Mode (DSRM)? 這表示疑難排解必要。This indicates troubleshooting is necessary. 若要在 DSRM 登入,請使用。 \Administrator帳號,並在指定 DSRM 密碼。To log on in DSRM, use .\Administrator account and specify the DSRM password.

    1. 檢查 Dcpromo.log。Examine the Dcpromo.log.

      1. 是否初始複製步驟成功,但無法網域控制站升級?Did initial cloning steps succeed but domain controller promotion fail?

      2. 錯誤指定本機網域控制站或 AD DS 環境中,使用的問題,例如從肯定傳回錯誤?Do errors indicate issues with the local domain controller or with the AD DS environment, such as errors returned from the PDC emulator?

    2. 檢查 [系統和 Directory 服務事件登 dccloneconfig.xml 和 CustomDCCloneAllowList.xmlExamine the System and Directory Services event logs and the dccloneconfig.xml and CustomDCCloneAllowList.xml

      1. 不相容應用程式需要是 CustomDCCloneAllowList.xml 允許清單?Does an incompatible application need to be in the CustomDCCloneAllowList.xml allow list?

      2. 複製或不正確 dccloneconfig.xml 中 IP 位址或電腦名稱是?Is the IP address or computer name either duplicated or invalid in the dccloneconfig.xml?

      3. 無效的 Active Directory 網站 dccloneconfig.xml 中嗎?Is the Active Directory site invalid in the dccloneconfig.xml?

      4. IP 位址未設定 dccloningconfig.xml 中,有可用的任何 DHCP 伺服器嗎?Is the IP address not set in the dccloningconfig.xml and there is no DHCP server available?

      5. 而且肯定 online 可透過 RPC 通訊協定嗎?Is the PDC emulator online and available through the RPC protocol?

      6. 複製網域控制站群組成員為網域控制站嗎?Is the domain controller a member of the Cloneable Domain Controllers group? 權限允許建立自己的複本 DC設定為網域根嗎?Is the permission Allow a DC to create a clone of itself set on the domain root for that group?

      7. Dccloneconfig.xml 檔案是否包含避免正確剖析語法錯誤?Does the Dccloneconfig.xml file contain syntax errors that prevent correct parsing?

      8. Hypervisor 支援?Is the hypervisor supported?

      9. 複製開始成功後,是否網域控制站促銷失敗?Did domain controller promotion fail after cloning began successfully?

      10. 已自動自訂網域控制站名稱 (9999) 超過人數嗎?Was the maximum number of auto-generated domain controller names (9999) exceeded?

      11. 重複的 MAC 地址?Is the MAC address duplicated?

  2. 做為來源俠相同是複製主機名稱嗎?Is host name of the clone the same as the source DC?

    1. 是否有 Dccloneconfig.xml 檔案中的其中一個允許的位置?Is there a Dccloneconfig.xml file in one of the allowed locations?
  3. VM 開機進入標準模式和複製完成後,但無法正確運作的網域控制站嗎?Is the VM booting into normal mode and cloning completed, but the domain controller is not functioning correctly?

    1. 第一次,請檢查是否主機名稱變更上複製。First check if the host name is changed on the clone. 如果不同的主機名稱,請複製最少部分完成。If the host name is different, cloning has at least partially completed.

    2. 網域控制站是否有來源網域控制站 dccloneconfig.xml,從重複的 IP 位址,但期間複製已離線來源網域控制站?Does the domain controller have a duplicate IP address of the source domain controller from the dccloneconfig.xml, but the source domain controller was offline during cloning?

    3. 如果您的網域控制站廣告,視為您不需要複製會有任何一般後促銷問題問題。If the domain controller is advertising, treat the issue as any normal post-promotion issue you would have without cloning.

    4. 如果您的網域控制站不廣告,檢查 Directory 服務、 系統、 應用程式、 檔案複寫和 DFS 複寫事件登後升級的錯誤。If the domain controller is not advertising, examine the Directory Service, System, Application, File Replication and DFS Replication event logs for post-promotion errors.

停用 DSRM 開機Disabling DSRM Boot

一旦開機進入 DSRM 任何錯誤,因為診斷失敗的原因及 dcpromo.log 不會指出的複製無法重試,如果修正失敗的原因 DSRM 旗標重設。Once booted into DSRM due to any error, diagnose the cause for failure and if the dcpromo.log does not indicate that cloning cannot be retried, fix the cause for failure and reset the DSRM flag. 失敗的複製不會傳回至標準模式自己在下一步重新開機。您必須以再試一次複製移除 DS 還原模式開機旗標。A failed clone does not return to normal mode on its own on the next reboot; you must remove the DS Restore Mode boot flag in order to try cloning again. 所有的這些步驟會需要以提升權限的系統管理員身分執行。All of these steps require running as an elevated administrator.

移除 DSRM Msconfig.exe 使用Removing DSRM with Msconfig.exe

若要關閉使用 GUI DSRM 開機,請使用 「 系統設定工具:To turn DSRM boot off using a GUI, use the System Configuration tool:

  1. 執行 msconfig.exeRun msconfig.exe

  2. 開機索引標籤,在開機選項,取消選取安全開機(它已選取的選項Active Directory 修復功能)On the Boot tab, under Boot Options, de-select Safe boot (it is already selected with the option Active Directory repair enabled)

  3. 按一下 [確定] 並重新出現提示時Click OK and restart when prompted

移除 DSRM Bcdedit.exe 與Removing DSRM with Bcdedit.exe

若要關閉 DSRM 開機從命令列,請使用開機設定資料儲存區編輯器:To turn DSRM boot off from the command-line, use the Boot Configuration Data Store Editor:

  1. 打開 CMD 提示並執行:Open a CMD prompt and run:

    Bcdedit.exe /deletevalue safeboot  
    
  2. 重新播放的電腦:Restart the computer with:

    Shutdown.exe /t /0 /r  
    

注意

Bcdedit.exe 也適用於 Windows PowerShell 主機。Bcdedit.exe also works in a Windows PowerShell console. 有命令:The commands there are:

Bcdedit.exe /deletevalue 安全開機Bcdedit.exe /deletevalue safeboot

電腦重新開機Restart-computer

伺服器 Core 和事件登入Server Core and the Event Log

事件登包含許多關於模擬的網域控制站複製作業有用的資訊。The event logs contain much of the useful information about virtualized domain controller cloning operations. 根據預設,Windows Server 2012 的電腦安裝是 Server Core 安裝,這表示不圖形介面,因此,不執行本機事件檢視器嵌入式管理單元的方式。By default, a Windows Server 2012 computer installation is a Server Core installation, which means there is no graphical interface and therefore, no way to run the local Event Viewer snap-in.

若要檢視事件登執行 Server Core 安裝的伺服器上:To review the event logs on a server running a Server Core installation:

  • 在本機上執行的 Wevtutil.exe 工具Run the Wevtutil.exe tool locally

  • 在本機上執行 PowerShell cmdlet 取得-WinEventRun PowerShell cmdlet Get-WinEvent locally

  • 如果您有支援 Windows 進階免 「 事件登入遠端管理 」 群組 (或相當於連接埠) 允許輸入的通訊,您可以管理從遠端使用 Eventvwr.exe、 wevtutil.exe 或取得-Winevent 事件登入。If you have enabled the Windows Advanced Firewall rules for the "Remote Event Log Management" groups (or equivalent ports) to allow inbound communication, you can manage the event log remotely using Eventvwr.exe, wevtutil.exe, or Get-Winevent. 這可以使用 Windows PowerShell 3.0 NETSH.exe、 群組原則或設定為 NetFirewallRule cmdlet 新 Server Core 安裝完成。This can be done on Server Core installation using NETSH.exe, Group Policy, or the new Set-NetFirewallRule cmdlet in Windows PowerShell 3.0.

警告

請勿在 DSRM 時,圖形殼層新增到電腦。Do not attempt to add the graphical shell back to the computer while it is in DSRM. Windows 維護堆疊 (CBS) 無法正常運作,同時在安全模式 」 或 「 DSRM。Windows servicing stack (CBS) cannot operate correctly while in Safe Mode or DSRM. 若要新增的功能或在 DSRM 中的角色嘗試而不完成,而且的電腦保持在不穩定的狀態,直到它通常會開機。Attempts to add features or roles while in DSRM will not complete and leave the computer in an unstable state until it is booted normally. 因為在 DSRM 模擬的網域控制站複製一樣,無法開機,且應該不會開機通常會在大部分的環境,很難安全地新增的圖形殼層。Since a virtualized domain controller clone in DSRM cannot boot normally, and should not be booted normally under most circumstances, it is impossible to safely add the graphical shell. 如此一來不支援,可讓您無法使用的伺服器。Doing so is unsupported and may leave you with an unusable server.

特定的問題進行疑難排解Troubleshooting Specific Problems

事件Events

所有模擬的網域控制站複製事件寫入複製網域控制站 VM Directory 服務事件登入。All virtualized domain controller cloning events write to the Directory Services event log of the clone domain controller VM. 應用程式、 檔案複寫服務及 DFS 複寫事件登也可能包含失敗複製實用疑難排解資訊。The Application, File Replication Service, and DFS Replication event logs may also contain useful troubleshooting information for failed cloning. 以肯定 RPC 通話期間失敗可能會提供肯定事件登入。Failures during the RPC call to the PDC emulator may be available in the event log on the PDC emulator.

以下是 Windows Server 2012 複製特定 Directory 服務事件登入,資訊與建議的解析度的錯誤事件。Below are the Windows Server 2012 cloning-specific events in the Directory Services event log, with notes and suggested resolutions for errors.

Directory 服務事件登入Directory Services Event Log
事件編號Event ID 21602160
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 本機* 找到 virtual 網域控制站複製設定檔。The local * has found a virtual domain controller cloning configuration file.

在找到 virtual 網域控制站複製設定檔: %1The virtual domain controller cloning configuration file is found at: %1

差 virtual 網域控制站複製設定檔表示本機 virtual 網域控制站其他 virtual 網域控制站的複本。The existence of the virtual domain controller cloning configuration file indicates that the local virtual domain controller is a clone of another virtual domain controller. * 複製本身將會開始。The * will start to clone itself.
筆記與解析度Notes and resolution 如果未預期,是成功的事件和的問題。This is a success event and only an issue if unexpected. 檢查 DSA 運作 Directory、 %systemroot%\ntds 和根的任何本機或卸除式磁碟 dcclconeconfig.xml 檔案。Examine the DSA Working Directory, %systemroot%\ntds, and root of any local or removable disks for the dcclconeconfig.xml file.
事件編號Event ID 21612161
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 本機* 找不到 virtual 網域控制站複製設定檔。The local * did not find the virtual domain controller cloning configuration file. 不複製的 DC 本機電腦。The local machine is not a cloned DC.
筆記與解析度Notes and resolution 如果未預期,是成功的事件和的問題。This is a success event and only an issue if unexpected. 檢查 DSA 運作 Directory、 %systemroot%\ntds 和根的任何本機或卸除式磁碟 dcclconeconfig.xml 檔案。Examine the DSA Working Directory, %systemroot%\ntds, and root of any local or removable disks for the dcclconeconfig.xml file.
事件編號Event ID 21622162
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message Virtual 網域控制站複製失敗。Virtual domain controller cloning failed.

請登入系統事件登和 %systemroot%\debug\dcpromo.log 如需詳細資訊,在 [對應至複製嘗試 virtual 網域控制站的錯誤事件。Please check events logged in System event logs and %systemroot%\debug\dcpromo.log for more information on errors that correspond to the virtual domain controller cloning attempt.

錯誤碼: %1Error code: %1
筆記與解析度Notes and resolution 遵循訊息的指示,這項錯誤會 catchall。Follow message instructions, this error is a catchall.
事件編號Event ID 21632163
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message DsRoleSvc 服務已複製本機 virtual 網域控制站開始。DsRoleSvc service was started to clone the local virtual domain controller.
筆記與解析度Notes and resolution 如果未預期,是成功的事件和的問題。This is a success event and only an issue if unexpected. 檢查 DSA 運作 Directory、 %systemroot%\ntds 和根的任何本機或卸除式磁碟 dcclconeconfig.xml 檔案。Examine the DSA Working Directory, %systemroot%\ntds, and root of any local or removable disks for the dcclconeconfig.xml file.
事件編號Event ID 21642164
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 若要開始 DsRoleSvc 服務複製本機 virtual 網域控制站失敗。 failed to start the DsRoleSvc service to clone the local virtual domain controller.
筆記與解析度Notes and resolution 檢查服務 DS 角色伺服器服務 (DsRoleSvc) 的設定,並確定其開始輸入設定為手動。Examine the service settings for the DS Role Server service (DsRoleSvc) and ensure its start type is set to manual. 驗證無第三方程式造成 [開始] 的這項服務。Validate that no third party program is preventing the start of this service.
事件編號Event ID 21652165
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 開始在本機 virtual 網域控制站複製的討論串中有失敗。 failed to start a thread during the cloning of the local virtual domain controller.

錯誤碼: %1Error code:%1

錯誤訊息: %2Error message:%2

執行緒 3%名稱:Thread name:%3
筆記與解析度Notes and resolution 連絡 Microsoft Product 支援Contact Microsoft Product Support
事件編號Event ID 21662166
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 需要起始重新開機一次插入 DSRM RPCSS 服務。 needs RPCSS service to initiate rebooting into DSRM. 等待 RPCSS 初始化失敗執行的狀態。Waiting for RPCSS to initialize into a running state failed.

錯誤碼: %1Error code:%1
筆記與解析度Notes and resolution 檢查服務 RPC 伺服器服務 (Rpcss) 的設定和系統事件登入Examine the System event log and service settings for the RPC Server service (Rpcss)
事件編號Event ID 21672167
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 無法初始化 virtual 網域控制站知識。 could not initialize virtual domain controller knowledge. 查看先前事件登入的項目,如需詳細資訊。See previous event log entry for details.

其他資料Additional Data

失敗碼: %1Failure code:%1
筆記與解析度Notes and resolution 遵循訊息的指示,這項錯誤會 catchall。Follow message instructions, this error is a catchall.
事件編號Event ID 21682168
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService

DC 支援 hypervisor 上執行。The DC is running on a supported hypervisor. 偵測到 VM 代來電顯示。VM Generation ID is detected.

目前值 VM 代 ID: %1Current value of VM Generation ID: %1
筆記與解析度Notes and resolution 如果未預期,是成功的事件和的問題。This is a success event and only an issue if unexpected.
事件編號Event ID 21692169
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 不還有偵測到的任何 VM 代來電顯示。There is no VM Generation ID detected. 實體機器、 向下層級的版本 HYPER-V,或不支援 VM 代 ID hypervisor 裝載 DCThe DC is hosted on a physical machine, a down-level version of Hyper-V, or a hypervisor that does not support the VM Generation ID.

其他資料Additional Data

失敗碼檢查 VM 代 %1 時傳回Failure code returned when checking VM Generation ID:%1
筆記與解析度Notes and resolution 如果您不打算複製,是成功事件。This is a success event if not intending to clone. 否則,請檢查 [系統事件登入並檢視 hypervisor product 支援文件。Otherwise, examine the System event log and review hypervisor product support documentation.
事件編號Event ID 21702170
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 警告Warning
訊息Message 偵測到代 ID 變更。A Generation ID change has been detected.

代來電顯示快取中 DS (舊值): %1Generation ID cached in DS (old value):%1

代 ID 目前在 VM (新值): %2Generation ID currently in VM (new value):%2

一樣快照的應用程式、 一樣匯入操作後或即時移轉作業之後,就會發生代 ID 變更。The Generation ID change occurs after the application of a virtual machine snapshot, after a virtual machine import operation or after a live migration operation. 將會建立新的叫用 ID 復原網域控制站。 will create a new invocation ID to recover the domain controller. 應還原模擬的網域控制站使用一樣的快照。Virtualized domain controllers should not be restored using virtual machine snapshots. 支援的方法來還原或復原 content 的 Active Directory Domain Services 資料庫是還原所做的 Active Directory Domain Services 注意備份應用程式的系統狀態備份。The supported method to restore or rollback the content of an Active Directory Domain Services database is to restore a system state backup made with an Active Directory Domain Services aware backup application.
筆記與解析度Notes and resolution 如果您要複製,這是成功事件。This is a success event if intending to clone. 否則,請檢查系統事件登入。Otherwise, examine the System event log.
事件編號Event ID 21712171
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 偵測不代 ID 變更。No Generation ID change has been detected.

代來電顯示快取中 DS (舊值): %1Generation ID cached in DS (old value):%1

代 ID 目前在 VM (新值): %2Generation ID currently in VM (new value):%2
筆記與解析度Notes and resolution 如果您不打算複製,是成功的事件和應該會出現在模擬 DC 重新開機。This is a success event if not intending to clone, and should be seen at every reboot of a virtualized DC. 否則,請檢查系統事件登入。Otherwise, examine the System event log.
事件編號Event ID 21722172
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 朗讀 msDS GenerationId 網域控制站的電腦物件的屬性。Read the msDS-GenerationId attribute of the Domain Controller's computer object.

msDS-GenerationId 屬性的值: %1msDS-GenerationId attribute value:%1
筆記與解析度Notes and resolution 如果您要複製,這是成功事件。This is a success event if intending to clone. 否則,請檢查系統事件登入。Otherwise, examine the System event log.
事件編號Event ID 21732173
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 無法讀取 msDS-GenerationId 網域控制站的電腦物件的屬性。Failed to read the msDS-GenerationId attribute of the Domain Controller's computer object. 這可能因為資料庫交易失敗,或在本機資料庫代 id 不存在。This may be caused by database transaction failure, or the generation id does not exist in the local database. 之後帶領或俠不 virtual 網域控制站 msDS GenerationId 不存在期間的第一次重新開機。The msDS-GenerationId does not exist during the first reboot after dcpromo or the DC is not a virtual domain controller.

其他資料Additional Data

失敗碼: %1Failure code:%1
筆記與解析度Notes and resolution 這是成功事件,如果您要複製並在第一次 VM 重新開機之後並複製已完成。This is a success event if intending to clone and it is the first VM reboot after cloning has completed. 也可以在非 virtual 網域控制站忽略它。It can also be ignored on non-virtual Domain controllers. 否則,請檢查系統事件登入。Otherwise, examine the System event log.
事件編號Event ID 21742174
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message DC 是 virtual 網域控制站複製都還原 virtual 網域控制站開發進程的快照。The DC is neither a virtual domain controller clone nor a restored virtual domain controller snapshot.
筆記與解析度Notes and resolution 如果您不打算複製,是成功事件。This is a success event if not intending to clone. 否則,請檢查系統事件登入。Otherwise, examine the System event log.
事件編號Event ID 21752175
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 支援的平台上,有 virtual 網域控制站複製設定檔。Virtual domain controller clone configuration file exists on an unsupported platform.
筆記與解析度Notes and resolution 這是時找到 dccloneconfig.xml VM 代編號找不到,例如所在的電腦上或不支援 VM 代 ID hypervisor 時找到的 dccloneconfig.xml 檔案This occurs when a dccloneconfig.xml is found but a VM Generation-ID could not be found, such as when a dccloneconfig.xml file is found on a physical computer or on a hypervisor that does not support VM Generation-ID.
事件編號Event ID 21762176
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 重新命名 virtual 網域控制站複製設定檔。Renamed virtual domain controller clone configuration file.

其他資料Additional Data

舊檔案名稱: %1Old file name:%1

新檔案名稱: %2New file name:%2
筆記與解析度Notes and resolution 如預期般時開機來源 VM 備份,因為已經不會變更 VM 代 ID 重新命名。Rename expected when booting a source VM back up, because the VM Generation ID has not changed. 如此可防止來源網域控制站嘗試複製。This prevents the source domain controller from trying to clone.
事件編號Event ID 21772177
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 重新命名 virtual 網域控制站複製設定檔失敗。Renaming virtual domain controller clone configuration file failed.

其他資料Additional Data

檔案名稱: %1File name:%1

失敗碼: %%32Failure code:%2 %3
筆記與解析度Notes and resolution 重新命名嘗試時預期的來源 VM 開機備份,因為 VM 代 ID 已經不會變更。Rename attempt expected when booting a source VM back up, because the VM Generation ID has not changed. 如此可防止來源網域控制站嘗試複製。This prevents the source domain controller from trying to clone. 手動重新命名檔案,並調查安裝第三方你,可能會阻止重新命名檔案。Manually rename the file and investigate installed third party products that may be preventing the file rename.
事件編號Event ID 21782178
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 偵測到 virtual 網域控制站複製設定檔案,但 VM 代 ID 不已變更。Detected virtual domain controller clone configuration file, but VM Generation ID has not been changed. 本機俠是俠複製來源。The local DC is the clone source DC. 重新命名複製設定檔。Rename the clone configuration file.
筆記與解析度Notes and resolution 時,有開機來源 VM 備份,因為已經不會變更 VM 代來電顯示。Expected when booting a source VM back up, because the VM Generation ID has not changed. 如此可防止來源網域控制站嘗試複製。This prevents the source domain controller from trying to clone.
事件編號Event ID 21792179
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message MsDS-GenerationId 物件的屬性網域控制站的電腦已設定為下列參數:The msDS-GenerationId attribute of the Domain Controller's computer object has been set to the following parameter:

GenerationID 屬性: %1GenerationID attribute:%1
筆記與解析度Notes and resolution 如果未預期,是成功的事件和的問題。This is a success event and only an issue if unexpected.
事件編號Event ID 21802180
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 警告Warning
訊息Message 無法將 msDS-GenerationId 網域控制站的電腦物件的屬性。Failed to set the msDS-GenerationId attribute of the Domain Controller's computer object.

其他資料Additional Data

失敗碼: %1Failure code:%1
筆記與解析度Notes and resolution 檢查 Dcpromo.log 和系統事件登入。Examine the System event log and Dcpromo.log. 查詢特定 MS TechNet、 MS 微軟,與 MS 部落格,以判斷其一般還久的意義,以及然後疑難排解錯誤會根據這些結果。Lookup the specific error in MS TechNet, MS Knowledgebase, and MS blogs to determine its usual meaning, and then troubleshoot based on those results.
事件編號Event ID 21822182
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 事件內部: 被要求複製遠端 DSA Directory 服務:Internal event: The Directory Service has been asked to clone a remote DSA:
筆記與解析度Notes and resolution 如果未預期,是成功的事件和的問題。This is a success event and only an issue if unexpected.
事件編號Event ID 21832183
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 事件內部: * 完成要求複製遠端 Directory 系統代理程式。Internal event: * completed the request to clone the remote Directory System Agent.

原始俠名稱: %3Original DC name:%3

要求複製俠名稱: %4Request clone DC name:%4

要求複製 DC 網站: %5Request clone DC site:%5

其他資料Additional Data

錯誤: %值 1 %2Error value:%1 %2
筆記與解析度Notes and resolution 如果未預期,是成功的事件和的問題。This is a success event and only an issue if unexpected.
事件編號Event ID 21842184
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 建立網域控制站 account 複製俠失敗。 failed to create a domain controller account for the cloned DC.

原始俠名稱: %1Original DC name:%1

允許的數目複製 DC:%2Allowed number of cloned DC:%2

上的 [由複製的網域控制站帳號數限制* 超過。The limit on the number of domain controller accounts that can be generated by cloning *was exceeded.
筆記與解析度Notes and resolution 如果網域控制站不會降級,根據命名規格單一來源網域控制站名稱只會自動產生 9999 時間。A single source domain controller name can only automatically generate 9999 times if domain controllers are not demoted, based on the naming convention. 使用的不同名稱 DC 產生新的唯一名稱或複製 XML 中的項目。Use the element in the XML to generate a new unique name or clone from a differently named DC.
事件編號Event ID 21912191
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 若要停用 DNS 更新下列登錄值設成。 set the following registry value to disable DNS updates.

登錄鍵: %1Registry Key:%1

登錄值: %2Registry Value: %2

登錄數值資料: %3Registry Value data: %3

複製程序,在本機電腦可能會有一小段時間複製來源電腦相同電腦的名稱。During the cloning process, the local machine may have the same computer name as the clone source machine for a short time. DNS A AAAA 記錄登記會停用在這段期間,因此戶端找不到本機電腦目前正在進行複製傳送要求。DNS A and AAAA record registration are disabled during this period so clients cannot send requests to the local machine undergoing cloning. 複製程序將會複製完成後,再試一次讓 DNS 更新。The cloning process will enable DNS updates again after cloning is completed.
筆記與解析度Notes and resolution 如果未預期,是成功的事件和的問題。This is a success event and only an issue if unexpected.
事件編號Event ID 21922192
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 將下列登錄值來停用 DNS 更新失敗。 failed to set the following registry value to disable DNS updates.

登錄鍵: %1Registry Key:%1

登錄值: %2Registry Value: %2

登錄數值資料: %3Registry Value data: %3

錯誤碼: %4Error code:%4

錯誤訊息: %5Error message:%5

複製程序,在本機電腦可能會有一小段時間複製來源電腦相同電腦的名稱。During the cloning process, the local machine may have the same computer name as the clone source machine for a short time. DNS A AAAA 記錄登記會停用在這段期間,因此戶端找不到本機電腦目前正在進行複製傳送要求。DNS A and AAAA record registration are disabled during this period so clients cannot send requests to the local machine undergoing cloning.
筆記與解析度Notes and resolution 檢查應用程式和系統事件登。Examine Application and System event logs. 調查第三方應用程式可能會封鎖登錄更新。Investigate third party application that may be blocking registry updates.
事件編號Event ID 21932193
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 設定,可讓 DNS 更新登錄下列值。 set the following registry value to enable DNS updates.

登錄鍵: %1Registry Key:%1

登錄值: %2Registry Value: %2

登錄數值資料: %3Registry Value data: %3

複製程序,在本機電腦可能會有一小段時間複製來源電腦相同電腦的名稱。During the cloning process, the local machine may have the same computer name as the clone source machine for a short time. DNS A AAAA 記錄登記會停用在這段期間,因此戶端找不到本機電腦目前正在進行複製傳送要求。DNS A and AAAA record registration are disabled during this period so clients cannot send requests to the local machine undergoing cloning.
筆記與解析度Notes and resolution 如果未預期,是成功的事件和的問題。This is a success event and only an issue if unexpected.
事件編號Event ID 21942194
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 下列登錄將值設為讓 DNS 更新失敗。 failed to set the following registry value to enable DNS updates.

登錄鍵: %1Registry Key:%1

登錄值: %2Registry Value: %2

登錄數值資料: %3Registry Value data: %3

錯誤碼: %4Error code:%4

錯誤訊息: %5Error message:%5

複製程序,在本機電腦可能會有一小段時間複製來源電腦相同電腦的名稱。During the cloning process, the local machine may have the same computer name as the clone source machine for a short time. DNS A AAAA 記錄登記會停用在這段期間,因此戶端找不到本機電腦目前正在進行複製傳送要求。DNS A and AAAA record registration are disabled during this period so clients cannot send requests to the local machine undergoing cloning.
筆記與解析度Notes and resolution 檢查應用程式和系統事件登。Examine Application and System event logs. 調查第三方應用程式可能會封鎖登錄更新。Investigate third party application that may be blocking registry updates.
事件編號Event ID 21952195
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 將開機 DSRM 失敗。Failed to set DSRM boot.

錯誤碼: %1Error code:%1

錯誤訊息: %2Error message:%2

當 virtual 網域控制站複製無法或 virtual 網域控制站複製設定檔會出現在未受支援 hypervisor、 在本機電腦將會到 DSRM 重新開機進行疑難排解。When virtual domain controller cloning failed or virtual domain controller clone configuration file appears on a non-supported hypervisor, the local machine will reboot into DSRM for troubleshooting. 設定 DSRM 開機失敗。Setting DSRM boot failed.
筆記與解析度Notes and resolution 檢查應用程式和系統事件登。Examine Application and System event logs. 調查第三方應用程式可能會封鎖登錄更新。Investigate third party application that may be blocking registry updates.
事件編號Event ID 21962196
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 無法讓關機權限。Failed to enable shutdown privilege.

錯誤碼: %1Error code:%1

錯誤訊息: %2Error message:%2

當 virtual 網域控制站複製無法或 virtual 網域控制站複製設定檔會出現在未受支援 hypervisor、 在本機電腦將會到 DSRM 重新開機進行疑難排解。When virtual domain controller cloning failed or virtual domain controller clone configuration file appears on a non-supported hypervisor, the local machine will reboot into DSRM for troubleshooting. 讓關閉雲端失敗。Enabling shutdown privilege failed.
筆記與解析度Notes and resolution 檢查應用程式和系統事件登。Examine Application and System event logs. 調查第三方應用程式可能會封鎖權限使用量。Investigate third party application that may be blocking privilege usage.
事件編號Event ID 21972197
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 無法起始系統關機。Failed to initiate system shutdown.

錯誤碼: %1Error code:%1

錯誤訊息: %2Error message:%2

當 virtual 網域控制站複製無法或 virtual 網域控制站複製設定檔會出現在未受支援 hypervisor、 在本機電腦將會到 DSRM 重新開機進行疑難排解。When virtual domain controller cloning failed or virtual domain controller clone configuration file appears on a non-supported hypervisor, the local machine will reboot into DSRM for troubleshooting. 起始系統關機失敗。Initiating system shutdown failed.
筆記與解析度Notes and resolution 檢查應用程式和系統事件登。Examine Application and System event logs. 調查第三方應用程式可能會封鎖權限使用量。Investigate third party application that may be blocking privilege usage.
事件編號Event ID 21982198
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 無法建立或修改下列複製的 DC 物件。 failed to create or modify the following cloned DC object.

其他資料:Additional data:

物件:Object:

%1%1

錯誤值: %2Error value: %2

%3%3
筆記與解析度Notes and resolution 查詢特定 MS TechNet、 MS 微軟,與 MS 部落格,以判斷其一般還久的意義,以及然後疑難排解錯誤會根據這些結果。Lookup the specific error in MS TechNet, MS Knowledgebase, and MS blogs to determine its usual meaning, and then troubleshoot based on those results.
事件編號Event ID 21992199
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 無法建立下列複製的 DC 物件,因為已經有物件。 failed to create the following cloned DC object because the object already exists.

其他資料:Additional data:

來源俠:Source DC:

%1%1

物件:Object:

%2%2
筆記與解析度Notes and resolution 驗證 dccloneconfig.xml 未指定現有的網域控制站或複本 dccloneconfig.xml 有編輯名稱若不使用多個複製上。Validate the dccloneconfig.xml did not specify an existing domain controller or that copies of the dccloneconfig.xml have been used on multiple clones without editing the name. 如果仍未預期衝突,判斷的系統管理員升級。連絡它們討論是否應該降級現有的網域控制站,接著現有的網域控制站中繼資料,或是複製應該使用不同名稱。If the collision is still unexpected, determine which administrator promoted it; contact them to discuss if the existing domain controller should be demoted, the existing domain controller metadata cleaned, or if the clone should use a different name.
事件編號Event ID 22032203
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 複製過去 virtual 網域控制站失敗。Last virtual domain controller cloning failed. 這就是第一個在重新開機之後,然後,這應該是於複製重試。This is the first reboot since then so this should be a re-try of the cloning. 但是,有兩 virtual 網域控制站複製設定檔,也偵測到一樣代 ID 變更。However, neither virtual domain controller clone configuration file exists nor virtual machine generation ID change is detected. DSRM 開機。Boot into DSRM.

複製過去 virtual 網域控制站無法: %1Last virtual domain controller cloning failed:%1

有 virtual 網域控制站複製設定檔: %2Virtual domain controller clone configuration file exists:%2

偵測到一樣代 ID 變更: %3Virtual machine generation ID change is detected:%3
筆記與解析度Notes and resolution 如果複製失敗之前,因為遺失或不正確 dccloneconfig.xml 如預期般Expected if cloning failed previously, due to missing or invalid dccloneconfig.xml
事件編號Event ID 22102210
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 無法建立複製網域控制站的物件。failed to create objects for clone domain controller.

其他資料:Additional data:

複製 Id: %6Clone Id: %6

複製網域控制站名稱: %1Clone domain controller name: %1

再試一次進度: %2Retry loop: %2

值例外: %3Exception value: %3

錯誤值: %4Error value: %4

DSID: %5DSID: %5
筆記與解析度Notes and resolution 檢視系統和 Directory 服務事件登和 dcpromo.log 如需詳細資訊複製失敗的原因。Review the System and Directory Services event logs and the dcpromo.log for further details on why cloning failed.
事件編號Event ID 22112211
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 建立複製網域控制站的物件。has created objects for clone domain controller.

其他資料:Additional data:

複製 Id: %3Clone Id: %3

複製網域控制站名稱: %1Clone domain controller name: %1

再試一次進度: %2Retry loop: %2
筆記與解析度Notes and resolution 如果未預期,是成功的事件和的問題。This is a success event and only an issue if unexpected.
事件編號Event ID 22122212
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 開始建立網域控制站複製物件。started to create objects for the clone domain controller.

其他資料:Additional data:

複製 Id: %1Clone Id: %1

複製名稱: %2Clone name: %2

複製網站: %3Clone site: %3

複製 RODC: %4Clone RODC: %4
筆記與解析度Notes and resolution 如果未預期,是成功的事件和的問題。This is a success event and only an issue if unexpected.
事件編號Event ID 22132213
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 建立新的唯讀網域控制站複製 KrbTgt 物件。created a new KrbTgt object for Read-Only domain controller cloning.

其他資料:Additional data:

複製 Id: %1Clone Id: %1

新的 KrbTgt 物件 Guid: %2New KrbTgt Object Guid: %2
筆記與解析度Notes and resolution 如果未預期,是成功的事件和的問題。This is a success event and only an issue if unexpected.
事件編號Event ID 22142214
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 將會建立複製網域控制站電腦物件。will create a computer object for the clone domain controller.

其他資料:Additional data:

複製 Id: %1Clone Id: %1

原始網域控制站: %2Original domain controller: %2

複製網域控制站: %3Clone domain controller: %3
筆記與解析度Notes and resolution 如果未預期,是成功的事件和的問題。This is a success event and only an issue if unexpected.
事件編號Event ID 22152215
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 將會在下列網站中新增複製網域控制站。will add the clone domain controller in the following site.

其他資料:Additional data:

複製 Id: %1Clone Id: %1

網站: %2Site: %2
筆記與解析度Notes and resolution 如果未預期,是成功的事件和的問題。This is a success event and only an issue if unexpected.
事件編號Event ID 22162216
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 將會建立容器複製網域控制站伺服器。will create a servers container for the clone domain controller.

其他資料:Additional data:

複製 Id: %1Clone Id: %1

伺服器容器: %2Servers Container: %2
筆記與解析度Notes and resolution 如果未預期,是成功的事件和的問題。This is a success event and only an issue if unexpected.
事件編號Event ID 22172217
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 將會建立複製網域控制站伺服器物件。will create a server object for the clone domain controller.

其他資料:Additional data:

複製 Id: %1Clone Id: %1

伺服器物件: %2Server Object: %2
筆記與解析度Notes and resolution 如果未預期,是成功的事件和的問題。This is a success event and only an issue if unexpected.
事件編號Event ID 22182218
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 將會建立複製網域控制站 NTDS 設定物件。will create a NTDS Settings object for the clone domain controller.

其他資料:Additional data:

複製 Id: %1Clone Id: %1

物件: %2Object: %2
筆記與解析度Notes and resolution 如果未預期,是成功的事件和的問題。This is a success event and only an issue if unexpected.
事件編號Event ID 22192219
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 將會建立複製唯讀網域控制站連接物件。will create connection objects for the clone Read-Only domain controller.

其他資料:Additional data:

複製 Id: %1Clone Id: %1
筆記與解析度Notes and resolution 如果未預期,是成功的事件和的問題。This is a success event and only an issue if unexpected.
事件編號Event ID 22202220
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 將會建立複製唯讀網域控制站 SYSVOL 物件。will create SYSVOL objects for the clone Read-Only domain controller.

其他資料:Additional data:

複製 Id: %1Clone Id: %1
筆記與解析度Notes and resolution 如果未預期,是成功的事件和的問題。This is a success event and only an issue if unexpected.
事件編號Event ID 22212221
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 無法產生隨機複製的網域控制站的密碼。failed to generate a random password for the cloned domain controller.

其他資料:Additional data:

複製 Id: %1Clone Id: %1

複製網域控制站名稱: %2Clone domain controller name: %2

錯誤: %3%4Error: %3 %4
筆記與解析度Notes and resolution 檢查 [系統事件登入,如需詳細資訊為何無法建立電腦密碼。Examine the system event log for further details on why the machine account password could not be created.
事件編號Event ID 22222222
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 無法複製的網域控制站設定密碼。failed to set password for the cloned domain controller.

其他資料:Additional data:

複製 Id: %1Clone Id: %1

複製網域控制站名稱: %2Clone domain controller name: %2

錯誤: %3%4Error: %3 %4
筆記與解析度Notes and resolution 檢查 [系統事件登入,如需詳細資訊為何無法設定電腦密碼。Examine the system event log for further details on why the machine account password could not be set.
事件編號Event ID 22232223
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 複製的網域控制站成功設定電腦密碼。successfully set machine account password for the cloned domain controller.

其他資料:Additional data:

複製 Id: %1Clone Id: %1

複製網域控制站名稱: %2Clone domain controller name: %2

總重試次數: %3Total retry times: %3
筆記與解析度Notes and resolution 如果未預期,是成功的事件和的問題。This is a success event and only an issue if unexpected.
事件編號Event ID 22242224
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message Virtual 網域控制站複製失敗。Virtual domain controller cloning failed. 下列 %1 管理服務帳號存在複製電腦:The following %1 Managed Service Account(s) exist on the cloned machine:

%2%2

適用於複製成功,必須移除所有管理服務帳號。For cloning to succeed, all Managed Service Accounts must be removed. 這可以使用移除-ADComputerServiceAccount PowerShell cmdlet。This can be done using the Remove-ADComputerServiceAccount PowerShell cmdlet.
筆記與解析度Notes and resolution 使用獨立 MSAs 時的預期 (不群組 MSA)。Expected when using standalone MSAs (not group MSA). 執行移除 account 事件建議,請依照下列-不正確撰寫。Do not follow the event advice to remove the account - it is incorrectly written. 使用 [解除安裝 AdServiceAccount- http://technet.microsoft.com/library/hh852310Use Uninstall-AdServiceAccount - http://technet.microsoft.com/library/hh852310.

第一次在 Windows Server 2008 R2 推出的-獨立 MSAs 所取代群組 MSAs (gMSA) 與 Windows Server 2012 中。Standalone MSAs - first released in Windows Server 2008 R2 - were replaced in Windows Server 2012 with group MSAs (gMSA). GMSAs 支援複製。GMSAs support cloning.
事件編號Event ID 22252225
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 下列安全性原則的快取機密資料已順利從本機網域控制站移除:The cached secrets of the following security principal have been successfully removed from local domain controller:

%1%1

複製唯讀網域控制站之後, 機密複製來源唯讀網域控制站之前快取的資料將被移除複製的網域控制站。After cloning a read-only domain controller, secrets which were previously cached on the cloning source read-only domain controller will be removed on the cloned domain controller.
筆記與解析度Notes and resolution 如果未預期,是成功的事件和的問題。This is a success event and only an issue if unexpected.
事件編號Event ID 22262226
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 無法從本機網域控制站移除下列安全性原則的快取的密碼:Failed to remove cached secrets of the following security principal from local domain controller:

%1%1

錯誤: %2 (%3)Error: %2 (%3)

之後複製唯讀網域控制站,機密先前已複製降低風險攻擊,可以從遭竊,或危害複製取得認證,以移除上複製來源唯讀網域控制站需要在快取的資料。After cloning a read-only domain controller, secrets which were previously cached on the cloning source read-only domain controller need to be removed on the clone in order to decrease the risk that an attacker can obtain those credentials from stolen or compromised clone. 如果您的安全性原則高度授權的帳號,並針對這應該受,請使用進行 rootDSE 作業 rODCPurgeAccount 手動清除其可在本機網域控制站。If the security principal is a highly privileged account and should be protected against this, please use rootDSE operation rODCPurgeAccount to manually clear its secrets on local domain controller.
筆記與解析度Notes and resolution 檢查 [系統及 Directory 服務事件登的其他相關資訊。Examine the System and Directory Services event logs for further information.
事件編號Event ID 22272227
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 例外嘗試移除本機網域控制站的快取的密碼。Exception is raised while trying to remove cached secrets from local domain controller.

其他資料:Additional data:

值例外: %1Exception value: %1

錯誤值: %2Error value: %2

DSID: %3DSID: %3

之後複製唯讀網域控制站,機密先前已複製降低風險攻擊,可以從遭竊,或危害複製取得認證,以移除上複製來源唯讀網域控制站需要在快取的資料。After cloning a read-only domain controller, secrets which were previously cached on the cloning source read-only domain controller need to be removed on the clone in order to decrease the risk that an attacker can obtain those credentials from stolen or compromised clone. 如果這些安全性原則的任何高度授權的帳號,並針對這應該受,請使用進行 rootDSE 作業 rODCPurgeAccount 手動清除其可在本機網域控制站。If any of these security principals is a highly privileged account and should be protected against this, please use rootDSE operation rODCPurgeAccount to manually clear its secrets on local domain controller.
筆記與解析度Notes and resolution 檢查 [系統及 Directory 服務事件登的其他相關資訊。Examine the System and Directory Services event logs for further information.
事件編號Event ID 22282228
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 在這個網域控制站的 Active Directory 資料庫一樣代 ID 是不同目前此一樣的值。The Virtual machine generation ID in the Active Directory database of this domain controller is different from the current value of this virtual machine. 不過,virtual 網域控制站複製設定檔 (DCCloneConfig.xml) 找不到,網域控制站複製不嘗試。However, a virtual domain controller clone configuration file (DCCloneConfig.xml) could not be located so domain controller cloning was not attempted. 如果複製作業網域控制站的目的是,請確定該 DCCloneConfig.xml 所提供的其中一個支援的位置。If a domain controller cloning operation was intended, please ensure that a DCCloneConfig.xml is provided in any one of the supported locations. 此外,此網域控制站的 IP 位址和其他網域控制站的 IP 位址衝突。In addition, the IP address of this domain controller conflicts with another domain controller's IP address. 若要確保發生任何服務中斷,已設定的網域控制站 DSRM 到開機。To ensure no disruptions in service occur, the domain controller has been configured to boot into DSRM.

其他資料:Additional data:

重複的 IP 位址: %1The duplicate IP address: %1
筆記與解析度Notes and resolution 這個保護機制停止重複的網域控制站時可能 (將不時使用 DHCP,例如)。This protection mechanism stops duplicate domain controllers when possible (it will not when using DHCP, for example). 將有效 DcCloneConfig.xml 檔案新增、 移除 DSRM 旗標和重新嘗試複製Add a valid DcCloneConfig.xml file, remove the DSRM flag, and re-attempt cloning
事件編號Event ID 2921829218
來源Source Microsoft Windows-對-DSROLE-伺服器Microsoft-Windows-DirectoryServices-DSROLE-Server
嚴重性Severity 錯誤Error
訊息Message Virtual 網域控制站複製失敗。Virtual domain controller cloning failed. 無法完成複製作業,複製的網域控制站重新開機至 Directory 服務還原模式 (DSRM)。The cloning operation could not be completed and the cloned domain controller was rebooted into Directory Services Restore Mode (DSRM).

請核取先前登入事件和 %systemroot%\debug\dcpromo.log 錯誤對應的詳細資訊的 virtual 網域控制站複製嘗試和可以重新使用此複製映像。Please check previously logged events and %systemroot%\debug\dcpromo.log for more information on errors that correspond to the virtual domain controller cloning attempt and whether or not this clone image can be reused.

如果有一或多個登入的項目,表示無法重試複製程序,必須確實損壞映像。If one or more log entries indicate that the cloning process cannot be retried, the image must be securely destroyed. 否則您可能會修正的錯誤、 清除 DSRM 開機旗標和開機通常;在重新開機,時將會重試複製操作。Otherwise you may fix the errors, clear the DSRM boot flag, and reboot normally; upon reboot, the cloning operation will be retried.
筆記與解析度Notes and resolution 檢視系統和 Directory 服務事件登和 dcpromo.log 如需詳細資訊複製失敗的原因。Review the System and Directory Services event logs and the dcpromo.log for further details on why cloning failed.
事件編號Event ID 2921929219
來源Source Microsoft Windows-對-DSROLE-伺服器Microsoft-Windows-DirectoryServices-DSROLE-Server
嚴重性Severity 資訊Informational
訊息Message Virtual 網域控制站複製成功。Virtual domain controller cloning succeeded.
筆記與解析度Notes and resolution 如果未預期,是成功的事件和的問題。This is a success event and only an issue if unexpected.
事件編號Event ID 2924829248
來源Source Microsoft Windows-對-DSROLE-伺服器Microsoft-Windows-DirectoryServices-DSROLE-Server
嚴重性Severity 錯誤Error
訊息Message 若要取得 Winlogon 通知 virtual 網域控制站複製失敗。Virtual domain controller cloning failed to obtain Winlogon Notification. 傳回的錯誤碼是 %1 (%2)。The returned error code is %1 (%2).

如需有關這個錯誤的詳細資訊,請檢查 %systemroot%\debug\dcpromo.log 對應複製嘗試 virtual 網域控制站的錯誤。For more information on this error, please review %systemroot%\debug\dcpromo.log for errors that correspond to the virtual domain controller cloning attempt.
筆記與解析度Notes and resolution 連絡 Microsoft Product 支援Contact Microsoft Product Support
事件編號Event ID 2924929249
來源Source Microsoft Windows-對-DSROLE-伺服器Microsoft-Windows-DirectoryServices-DSROLE-Server
嚴重性Severity 錯誤Error
訊息Message Virtual 網域控制站複製無法剖析 virtual 網域控制站設定檔。Virtual domain controller cloning failed to parse virtual domain controller configuration file.

傳回的 HRESULT 程式碼是 %1。The returned HRESULT code is %1.

設定檔是: 2%The configuration file is:%2

請設定檔中修正的錯誤,然後再試一次複製作業。Please fix the errors in the configuration file and retry the cloning operation.

如需有關這個錯誤,請查看 %systemroot%\debug\dcpromo.log。For more information about this error, please see %systemroot%\debug\dcpromo.log.
筆記與解析度Notes and resolution 檢查使用 XML 編輯器語法錯誤 dclconeconfig.xml 檔案和 DCCloneConfigSchema.xsd 架構檔案。Examine the dclconeconfig.xml file for syntax errors using an XML editor and the DCCloneConfigSchema.xsd schema file.
事件編號Event ID 2925029250
來源Source Microsoft Windows-對-DSROLE-伺服器Microsoft-Windows-DirectoryServices-DSROLE-Server
嚴重性Severity 錯誤Error
訊息Message Virtual 網域控制站複製失敗。Virtual domain controller cloning failed. 有軟體或複製 virtual 網域控制站在目前支援的服務不會存在 virtual 網域控制站複製允許的應用程式清單中。There are software or services currently enabled on the cloned virtual domain controller that are not present in the allowed application list for virtual domain controller cloning.

以下是遺失的項目:Following are the missing entries:

%2%2

(如果有的話) %1 用來做定義的包含清單。%1 (if any) was used as the defined inclusion list.

如果有非複製安裝的應用程式無法完成複製作業。The cloning operation cannot be completed if there are non-cloneable applications installed.

請執行 Active Directory PowerShell Cmdlet 取得-ADDCCloningExcludedApplicationList 以查看哪些應用程式安裝複製在電腦上,但不是包含在允許清單中,並將他們新增到允許清單中,如果有相容 virtual 網域控制站複製。Please run Active Directory PowerShell Cmdlet Get-ADDCCloningExcludedApplicationList to check which applications are installed on the cloned machine, but not included in the allow list, and add them to the allow list if they are compatible with virtual domain controller cloning. 如果這些應用程式的任何不相容 virtual 網域控制站複製,請將它們解除安裝再重新嘗試複製作業。If any of these applications are not compatible with virtual domain controller cloning, please uninstall them before re-trying the cloning operation.

允許應用程式清單檔案,CustomDCCloneAllowList.xml,依據以下搜尋順序; 搜尋 virtual 網域控制站複製程序使用的第一個檔案,找到和其他所有人會忽略:The virtual domain controller cloning process searches for the allowed application list file, CustomDCCloneAllowList.xml, based on the following search order; the first file found is used and all others are ignored:

1.登錄值名稱: HKey_Local_Machine\System\CurrentControlSet\Services\NTDS\Parameters\AllowListFolder1. The registry value name: HKey_Local_Machine\System\CurrentControlSet\Services\NTDS\Parameters\AllowListFolder

2.DSA 運作 Directory 資料夾所在的相同 directory2. The same directory where the DSA Working Directory folder resides

3.%windir%\NTDS3. %windir%\NTDS

4.讀取/寫入卸除式媒體順序的磁碟機代號根的磁碟機。4. Removable read/write media in order of drive letter at the root of the drive
筆記與解析度Notes and resolution 請依照下列指示訊息Follow the message instructions
事件編號Event ID 2925129251
來源Source Microsoft Windows-對-DSROLE-伺服器Microsoft-Windows-DirectoryServices-DSROLE-Server
嚴重性Severity 錯誤Error
訊息Message 若要重設複製電腦的 IP 位址 virtual 網域控制站複製失敗。Virtual domain controller cloning failed to reset the IP addresses of the clone machine.

傳回的錯誤碼是 %1 (%2)。The returned error code is %1 (%2).

這個錯誤可能是由錯誤網路設定區段中 virtual 網域控制站設定檔中。This error might be caused by misconfiguration in network configuration sections in the virtual domain controller configuration file.

請查看 %systemroot%\debug\dcpromo.log 的詳細資訊的 IP 位址期間 virtual 網域控制站複製嘗試重設為等於錯誤。Please see %systemroot%\debug\dcpromo.log for more information about errors that correspond to IP addresses resetting during virtual domain controller cloning attempts.

http://go.microsoft.com/fwlink/?LinkId=208030 找到重設電腦的 IP 位址複製電腦上的詳細資訊Details on resetting machine IP addresses on the cloned machine can be found at http://go.microsoft.com/fwlink/?LinkId=208030
筆記與解析度Notes and resolution 請確認無效,而且不重複的原始的來源電腦設定中 dccloneconfig.xml IP 資訊。Verify the IP information set in the dccloneconfig.xml is valid and does not duplicate the original source machine.
事件編號Event ID 2925329253
來源Source Microsoft Windows-對-DSROLE-伺服器Microsoft-Windows-DirectoryServices-DSROLE-Server
嚴重性Severity 錯誤Error
訊息Message Virtual 網域控制站複製失敗。Virtual domain controller cloning failed. 複製網域控制站無法複製電腦的複製的電腦的主要網域中找到主要網域控制站 (PDC) 操作主機。The clone domain controller was unable to locate the primary domain controller (PDC) operations master in the cloned computer's home domain of the cloned machine.

傳回的錯誤碼是 %1 (%2)。The returned error code is %1 (%2).

請確認主要網域控制站首頁網域中的複製電腦已指派給動態網域控制站、 是 online 和正常運作。Please verify that the primary domain controller in the home domain of the cloned machine is assigned to a live domain controller, is online, and is operational. 請確認複製的電腦 LDAP 日 RPC 連接主要網域控制站需要連接埠和通訊協定。Verify that the cloned machine has LDAP/RPC connectivity to the primary domain controller over the required ports and protocols.
筆記與解析度Notes and resolution 驗證複製的網域控制站 IP 和資訊 DNS 設定。Validate the cloned domain controller IP and DNS information is set. 使用 Dcdiag.exe /test:locatorcheck 驗證 online PDCE 時,請使用 Nltest.exe /server:* * /dclist:* 有效 RPC,以取得網路擷取從 PDCE 複製失敗時和分析資料傳輸。Use Dcdiag.exe /test:locatorcheck to validate if the PDCE is online, use Nltest.exe /server:* /dclist: to valid RPC, obtain a network capture from the PDCE while cloning fails and analyze the traffic.
事件編號Event ID 2925429254
來源Source Microsoft Windows-對-DSROLE-伺服器Microsoft-Windows-DirectoryServices-DSROLE-Server
嚴重性Severity 錯誤Error
訊息Message 繫結至主要網域控制站 %1 virtual 網域控制站複製失敗。Virtual domain controller cloning failed to bind to the primary domain controller %1.

傳回的錯誤碼是 %2 (%3)。The returned error code is %2 (%3).

請確認主要網域控制站 %1 是 online 正常運作。Please verify that the primary domain controller %1 is online and is operational. 請確認複製的電腦 LDAP 日 RPC 連接主要網域控制站需要連接埠和通訊協定。Verify that the cloned machine has LDAP/RPC connectivity to the primary domain controller over the required ports and protocols.
筆記與解析度Notes and resolution 驗證複製的網域控制站 IP 和資訊 DNS 設定。Validate the cloned domain controller IP and DNS information is set. 使用 Dcdiag.exe /test:locatorcheck 驗證 online PDCE 時,請使用 Nltest.exe /server:* * /dclist:* 有效 RPC,以取得網路擷取從 PDCE 複製失敗時和分析資料傳輸。Use Dcdiag.exe /test:locatorcheck to validate if the PDCE is online, use Nltest.exe /server:* /dclist: to valid RPC, obtain a network capture from the PDCE while cloning fails and analyze the traffic.
事件編號Event ID 2925529255
來源Source Microsoft Windows-對-DSROLE-伺服器Microsoft-Windows-DirectoryServices-DSROLE-Server
嚴重性Severity 錯誤Error
訊息Message Virtual 網域控制站複製失敗。Virtual domain controller cloning failed.

嘗試建立主要網域控制站 %1 所需的影像被複製物件傳回錯誤 %2 (%3)。An attempt to create objects on the primary domain controller %1 required for the image being cloned returned error %2 (%3).

請確認複製的網域控制站複製本身的權限。Please verify that the cloned domain controller has privilege to clone itself. 檢查有 Directory 服務事件登入主要網域控制站 %1 中相關事件。Check for related events in the Directory Service event log on primary domain controller %1.
筆記與解析度Notes and resolution 查詢特定 MS TechNet、 MS 微軟,與 MS 部落格,以判斷其一般的意義,以及然後疑難排解錯誤會根據這些結果。Lookup the specific error in MS TechNet, MS Knowledgebase, and MS blogs to determine its typical meaning, and then troubleshoot based on those results.
事件編號Event ID 2925629256
來源Source Microsoft Windows-對-DSROLE-伺服器Microsoft-Windows-DirectoryServices-DSROLE-Server
嚴重性Severity 錯誤Error
訊息Message 將開機設定 Directory 服務還原模式旗標到失敗,錯誤代碼 %1。An attempt to set the Boot into Directory Services Restore Mode flag failed with error code %1.

請查看 %systemroot%\debug\dcpromo.log 有關更多的錯誤。Please see %systemroot%\debug\dcpromo.log for more information about errors.
筆記與解析度Notes and resolution 檢查服務 Directory 登入和 dcpromo.log 如需詳細資訊。Examine the Directory Services log and dcpromo.log for details. 檢查應用程式和系統事件登。Examine Application and System event logs. 調查第三方應用程式可能會封鎖權限使用量。Investigate third party application that may be blocking privilege usage.
事件編號Event ID 2925729257
來源Source Microsoft Windows-對-DSROLE-伺服器Microsoft-Windows-DirectoryServices-DSROLE-Server
嚴重性Severity 錯誤Error
訊息Message 已完成 virtual 網域控制站複製。Virtual domain controller cloning has done. 將電腦重新開機失敗,錯誤代碼 %1。An attempt to reboot the machine failed with error code %1.

請重新開機才能完成作業複製。Please reboot the machine to finish the cloning operation.
筆記與解析度Notes and resolution 檢查應用程式和系統事件登。Examine Application and System event logs. 調查第三方應用程式可能會封鎖權限使用量。Investigate third party application that may be blocking privilege usage.
事件編號Event ID 2926429264
來源Source Microsoft Windows-對-DSROLE-伺服器Microsoft-Windows-DirectoryServices-DSROLE-Server
嚴重性Severity 錯誤Error
訊息Message 清除開機至 Directory 服務還原模式旗標失敗,錯誤代碼 %1。An attempt to clear the Boot into Directory Services Restore Mode flag failed with error code %1.

請查看 %systemroot%\debug\dcpromo.log 有關更多的錯誤。Please see %systemroot%\debug\dcpromo.log for more information about errors.
筆記與解析度Notes and resolution 檢查服務 Directory 登入和 dcpromo.log 如需詳細資訊。Examine the Directory Services log and dcpromo.log for details. 檢查應用程式和系統事件登。Examine Application and System event logs. 調查第三方應用程式可能會封鎖權限使用量。Investigate third party application that may be blocking privilege usage.
事件編號Event ID 2926529265
來源Source Microsoft Windows-對-DSROLE-伺服器Microsoft-Windows-DirectoryServices-DSROLE-Server
嚴重性Severity 資訊Informational
訊息Message Virtual 網域控制站複製成功。Virtual domain controller cloning succeeded. 重新命名 virtual 網域控制站複製設定檔 %1%2。The virtual domain controller cloning configuration file %1 has been renamed to %2.
筆記與解析度Notes and resolution 不適用,這是成功事件。N/A, this is a success event.
事件編號Event ID 2926629266
來源Source Microsoft Windows-對-DSROLE-伺服器Microsoft-Windows-DirectoryServices-DSROLE-Server
嚴重性Severity 錯誤Error
訊息Message Virtual 網域控制站複製成功。Virtual domain controller cloning succeeded. 嘗試重新命名 virtual 網域控制站複製設定檔 %1 失敗,錯誤代碼 %2 (%3)。The attempt to rename virtual domain controller cloning configuration file %1 failed with error code %2 (%3).
筆記與解析度Notes and resolution 手動重新命名 dccloneconfig.xml 檔案。Manually rename the dccloneconfig.xml file.
事件編號Event ID 2926729267
來源Source Microsoft Windows-對-DSROLE-伺服器Microsoft-Windows-DirectoryServices-DSROLE-Server
嚴重性Severity 錯誤Error
訊息Message Virtual 網域控制站複製無法檢查 virtual 網域控制站複製允許的應用程式] 清單。Virtual domain controller cloning failed to check the virtual domain controller cloning allowed application list.

傳回的錯誤碼是 %1 (%2)。The returned error code is %1 (%2).

可能會發生這個錯誤,語法複製時發生錯誤允許清單檔案 (目前檢查檔案: %3)。This error might be caused by a syntax error in the clone allow list file (The file currently being checked is: %3). 如需有關這個錯誤,請查看 %systemroot%\debug\dcpromo.log。For more information about this error, please see %systemroot%\debug\dcpromo.log.
筆記與解析度Notes and resolution 請依照下列指示事件Follow the event instructions
錯誤訊息Error Messages

有失敗模擬的網域控制站複製; 不直接互動式錯誤所有複製資訊登入系統 Directory 服務登並網域控制站升級登入 dcpromo.log。There are no direct interactive errors for failed virtualized domain controller cloning; all cloning information logs in the System and Directory Services logs and the domain controller promotion logs in dcpromo.log. 不過,如果伺服器開機進入 DS 還原模式,調查立即在升級或複製失敗。However, if the server boots into DS Restore Mode, investigate immediately, as promotion or cloning failed.

Dcpromo.log 是第一個地方以檢查複製失敗。The dcpromo.log is the first place to check for cloning failure. 根據列出失敗,可能必須後續檢視 Directory 服務及系統登進一步的診斷資訊。Depending on the failure listed, it may be necessary to subsequently review Directory Services and System logs for further diagnosis.

已知的問題,以及案例的支援Known Issues and Support Scenarios

以下是在 Windows Server 2012 開發程序期間常見的問題。The following are common issues seen during the Windows Server 2012 development process. 這些問題」的設計」,並具有有效的因應措施或更適合技巧,以避免使用它們首先。All of these issues are "by design" and have either a valid workaround or more appropriate technique to avoid them in the first place. 某些可能解析較新版本的 Windows Server 2012 中。Some may be resolved in later releases of Windows Server 2012.

問題Issue 複製 DSRM 失敗Cloning fails, DSRM
症狀Symptoms 複製開機進入 Directory 服務還原模式Clone boots into Directory Services Restore Mode
解析度和筆記Resolution and Notes 驗證所有區段部署擬化檔案網域控制站區段遵循的步驟,適用於疑難排解網域控制站複製一般方法Validate all steps followed from sections Deploying Virtualized Domain Controller section and General Methodology for Troubleshooting Domain Controller Cloning

以 kb 為單位 2742844 所述。Described in KB 2742844.
問題Issue 當您使用 DHCP 複製額外的 IP 租用Extra IP leases when using DHCP to clone
症狀Symptoms 在成功複製 DC 使用 DHCP 之後, 複製的第一次開機需要 DHCP 租賃。After successfully cloning a DC and using DHCP, the first boot of the clone takes a DHCP lease. 然後時伺服器會重新命名為 DC 重新啟動,所需的第二個 DHCP 租賃。Then when the server is renamed and restarted as a DC, it takes a second DHCP lease. 不發行的第一個 IP 位址,以及您最後使用 「 幻像 「 租用The first IP address is not released and you end up with a "phantom" lease
解析度和筆記Resolution and Notes 手動 delete dhcp 未使用的地址租用或允許通常會到期。Manually delete the unused address lease in DHCP or allow it to expire normally. 以 kb 為單位 2742836 所述。Described in KB 2742836.
問題Issue 很長的延遲之後複製到 DSRM 失敗Cloning fails into DSRM after very long delay
症狀Symptoms 複製會顯示在 「 X 網域控制站複製是 %的完成度 」 的之間 8 到 15 分鐘的時間。Cloning appears to pause at "Domain controller cloning is at X% completion" for between 8 and 15 minutes. 之後,複製失敗,並會開機至 DSRM。After this, the cloning fails and boots into DSRM.
解析度和筆記Resolution and Notes 複製的電腦無法取得動態 IP 位址 DHCP 或 SLAAC,或使用重複的 IP 位址,或 PDC 找不到。The cloned computer cannot get a dynamic IP address from DHCP or SLAAC, or is using a duplicate IP address, or cannot find the PDC. 複製執行多個重試次數會導致延遲。Multiple retry attempts performed by cloning lead to the delay. 解析允許複製的網路問題。Resolve the networking issue to allow cloning.

以 kb 為單位 2742844 所述。Described in KB 2742844.
問題Issue 複製未重新建立的所有服務主體名稱Cloning does not recreate all service principal names
症狀Symptoms 如果一組三個部分服務主體名稱 (SPN) 包含同時 NetBIOS 名稱連接埠和連接埠不相同 NetBIOS 名稱、 非連接埠項目不重新建立的新的電腦名稱。If a set of three-part service principal names (SPN) includes both a NetBIOS name with a port and an otherwise identical NetBIOS name without a port, the non-port entry is not recreated with the new computer name. 例如:For example:

customspn 日 DC1:200 / 符號 app1 無效使用這個重新建立的新的電腦名稱customspn/DC1:200/app1 INVALID USE OF SYMBOLS this is recreated with the new computer name

customspn 日 DC1 日 app1 符號無效使用未重新建立的新的電腦名稱customspn/DC1/app1 INVALID USE OF SYMBOLS this is not recreated with the new computer name

完整的名稱會重新建立並重新建立 Spn 三個部分不會無論連接埠。Fully qualified names are recreated and SPNs without three parts are recreated, regardless of ports. 例如,這些會重新建立成功複製上:For example, these are recreated successfully on the clone:

customspn / 符號 DC1:202 無效使用這個重新建立customspn/DC1:202 INVALID USE OF SYMBOLS this is recreated

customspn 日 DC1 無效使用的符號這個重新建立customspn/DC1 INVALID USE OF SYMBOLS this is recreated

customspn/DC1.corp.contoso.com:202 符號無效使用這個重新建立的名稱customspn/DC1.corp.contoso.com:202 INVALID USE OF SYMBOLS this is recreated name

customspn/DC1.corp.contoso.com 符號無效使用這個重新建立customspn/DC1.corp.contoso.com INVALID USE OF SYMBOLS this is recreated
解析度和筆記Resolution and Notes 這是一項限制的網域控制站重新命名程序在 Windows 中,而不只是在複製。This is a limitation of the domain controller rename process in Windows, not just in cloning. 三個部分 SPN 不是由任何案例中重新命名邏輯操作處理。Three-part SPNS are not handled by the renaming logic in any scenario. 為他們建立任何缺少 Spn 視不受影響,如此一來,最隨附的 Windows 服務。Most included Windows services are unaffected by this, as they recreate any missing SPNs as needed. 其他應用程式可能需要手動輸入修正問題的相關 SPN。Other applications may require manually entering the SPN to resolve the issue.

以 kb 為單位 2742874 所述。Described in KB 2742874.
問題Issue 複製失敗時,會開機至 DSRM,一般的網路錯誤Cloning fails, boots into DSRM, general networking errors
症狀Symptoms 複製開機進入 Directory 服務修復模式。Clone boots into Directory Services Repair Mode. 有一般網路錯誤。There are general networking errors.
解析度和筆記Resolution and Notes 確定新複製未重複靜態指派來源網域控制站; 的 MAC 位址您可以看到 VM 是否使用來執行這個命令的來源和複製虛擬機器 hypervisor 主機上靜態的 MAC 位址:Ensure that the new clone does not have a duplicate static MAC address assigned from the source domain controller; you can see if a VM uses static MAC addresses by running this command on the hypervisor host for both the source and clone virtual machines:

VMName 取得-VM 的測試-vm和 #124;取得-VMNetworkAdapter 與 #124;fl Get-VM -VMName *test-vm | Get-VMNetworkAdapter | fl *

變更唯一靜態位址的 MAC 地址,或切換到使用動態 MAC 位址。Change the MAC address to a unique static address or switch to using dynamic MAC addresses.

以 kb 為單位 2742844 所述的方式Described in KB 2742844
問題Issue 複製失敗時,為重複的來源 DC 會開機至 DSRMCloning fails, boots into DSRM as a duplicate of the source DC
症狀Symptoms 新的複製開機時不需要複製。A new clone boots up without cloning. Dccloneconfig.xml 不會重新命名,並開始 DS 還原模式中的伺服器。The dccloneconfig.xml is not renamed and the server starts in DS Restore Mode. 會顯示錯誤 2164 Directory 服務事件登入The Directory Services event log shows Error 2164

若要開始 DsRoleSvc 服務複製本機 virtual 網域控制站失敗。 failed to start the DsRoleSvc service to clone the local virtual domain controller.
解析度和筆記Resolution and Notes 檢查服務 DS 角色伺服器服務 (DsRoleSvc) 的設定,並確定其開始輸入設定為手動。Examine the service settings for the DS Role Server service (DsRoleSvc) and ensure its start type is set to Manual. 驗證無第三方程式造成 [開始] 的這項服務。Validate that no third party program is preventing the start of this service.

了解如何回收這個次要網域控制站同時確保取得複寫輸出更新的詳細資訊,會看到 Microsoft 知識庫文章 2742970。For more information about how to reclaim this secondary DC while ensuring that updates get replicated outbound, see Microsoft KB article 2742970.
問題Issue 複製失敗時,會開機至 DSRM,8610 錯誤Cloning fails, boots into DSRM, error 8610
症狀Symptoms 複製開機進入 Directory 服務還原模式。Clone boots into Directory Services Restore Mode. 帶領.log 顯示 8610 錯誤 (也就是 ERROR_DS_ROLE_NOT_VERIFIED 8610 或 0x21A2)Dcpromo .log shows 8610 error (which is ERROR_DS_ROLE_NOT_VERIFIED 8610 or 0x21A2)
解析度和筆記Resolution and Notes 如果可以找到 PDC,但無法執行的允許本身擔任不足複寫會發生。Will happen if the PDC can be discoverable but it has not performed sufficient replication to allow itself to assume the role. 例如,如果複製開始和其他系統管理員會 PDCE FSMO 角色移動到新的 DC。For example, if cloning is started and another administrator moves the PDCE FSMO role to a new DC.

以 kb 為單位 2742916 所述。Described in KB 2742916.
問題Issue 複製失敗時,會開機至 DSRM,一般的網路錯誤Cloning fails, boots into DSRM, general networking errors
症狀Symptoms 複製開機進入 Directory 服務還原模式。Clone boots into Directory Services Restore Mode. 有一般網路錯誤。There are general networking errors.
解析度和筆記Resolution and Notes 確定新複製未重複靜態指派來源網域控制站; 的 MAC 位址您可以看到 VM 是否使用來執行這個命令的來源和複製虛擬機器 HYPER-V 主機上靜態的 MAC 位址:Ensure that the new clone does not have a duplicate static MAC address assigned from the source domain controller; you can see if a VM uses static MAC addresses by running this command on the Hyper-V host for both the source and clone virtual machines:

VMName 取得-VM 的測試-vm和 #124;取得-VMNetworkAdapter 與 #124;fl Get-VM -VMName *test-vm | Get-VMNetworkAdapter | fl *

變更唯一靜態位址的 MAC 地址,或切換到使用動態 MAC 位址。Change the MAC address to a unique static address or switch to using dynamic MAC addresses.

以 kb 為單位 2742844 所述。Described in KB 2742844.
問題Issue 複製失敗時,會開機至 DSRMCloning fails, boots into DSRM
症狀Symptoms 複製開機進入 Directory 服務修復模式Clone boots into Directory Services Repair Mode
解析度和筆記Resolution and Notes 請確定 dccloneconfig.xml 包含架構定義 (看到 sampledccloneconfig.xml、 行 2):Ensure that the dccloneconfig.xml contains the schema definition (see sampledccloneconfig.xml, line 2):

< d3c:DCCloneConfig xmlns:d3c="uri:microsoft.com:schemas:DCCloneConfig] ><d3c:DCCloneConfig xmlns:d3c="uri:microsoft.com:schemas:DCCloneConfig">

以 kb 為單位 2742844 所述的方式Described in KB 2742844
問題Issue 無法登入伺服器會使用錯誤登入 DSRMNo logon servers are available error logging into DSRM
症狀Symptoms 複製開機進入 Directory 服務修復模式。Clone boots into Directory Services Repair Mode. 您嘗試登入收到錯誤訊息:You attempt to logon and receive error:

目前有不登入伺服器可服務登入要求There are currently no logon servers are available to service the logon request
解析度和筆記Resolution and Notes 請確定您的系統管理員 DSRM 帳號,並不核對登入。Ensure you logon with the DSRM administrator account, and not the domain account. 使用向左箭號,然後輸入的使用者名稱:Use the left arrow and type a user name of:

。 \administrator.\administrator

以 kb 為單位 2742908 所述的方式Described in KB 2742908
問題Issue 複製來源失敗到 DSRM,錯誤Clone Source fails into DSRM, error
症狀Symptoms 複製,期間失敗 8437 「 建立俠複製物件 PDC 無法在 」 (0x20f5)During cloning, fails 8437 "Create clone DC objects on PDC failed" (0x20f5)
解析度和筆記Resolution and Notes 重複的電腦名稱是在 DCCloneConfig.xml 做為來源俠或設定現有俠。Duplicate computer name was set in DCCloneConfig.xml as the source DC or an existing DC. 電腦名稱也必須 NetBIOS 電腦名稱的格式 (15 字元或較少,不 FQDN)。The computer name also needs to be in the NetBIOS computer name format (15 characters or fewer, not an FQDN).

修正檔案 dccloneconfig.xml 設定唯一、 有效的名稱。Fix the dccloneconfig.xml file by setting a unique, valid name.

以 kb 為單位 2742959 所述的方式Described in KB 2742959
問題Issue 新 addccloneconfigfile 錯誤 「 索引超出範圍 」New-addccloneconfigfile error "index was out of range"
症狀Symptoms 當新 addccloneconfigfile cmdlet 執行的是,您收到錯誤訊息:When running the new-addccloneconfigfile cmdlet, you receive error:

指數超出範圍。Index was out of range. 必須非負和小於的收藏大小。Must be non-negative and less than the size of the collection.
解析度和筆記Resolution and Notes 系統管理員提升權限 Windows PowerShell 主控台中,您必須執行 cmdlet。You must run the cmdlet in an administrator-elevated Windows PowerShell console. 錯誤的原因是在電腦上系統管理員本機群組成員資格缺乏。This error is caused by lack of local administrator group membership on the computer.

以 kb 為單位 2742927 所述的方式Described in KB 2742927
問題Issue 複製重複俠失敗Cloning fails, duplicate DC
症狀Symptoms 複製開機,而不需要複製,現有的來源 DC 重複項目Clone boots without cloning, duplicates existing source DC
解析度和筆記Resolution and Notes 電腦複製開始使用,但不包含任何支援的位置,DcCloneConfig.xml 檔案並不了來源網域控制站的重複的 IP 位址。The computer was copied and started but does not contain a DcCloneConfig.xml file in any of the supported locations, and did not have a duplicate IP address with the source domain controller. 為了避免資料遺失 DC 必須正確移除。The DC must be correctly removed in order to avoid data loss.

以 kb 為單位 2742970 所述的方式Described in KB 2742970
問題Issue 新 ADDCCloneConfigFile 失敗,並伺服器時,無法運作的錯誤它會檢查來源網域控制站不 GC 是否複製網域控制站群組成員。New-ADDCCloneConfigFile fails with The server is not operational error when it checks if the source domain controller is a member of the Cloneable Domain controllers group if a GC is not available.
症狀Symptoms 新增-ADDCCloneConfigFile 建立 dccloneconfig.xml 檔案執行的是,當您收到錯誤訊息:When running New-ADDCCloneConfigFile to create a dccloneconfig.xml file, you receive error:

程式碼-伺服器不操作Code - The server is not operational
解析度和筆記Resolution and Notes 從您執行新-ADDCCloneConfigFile 並確認該的來源網域控制站在複製網域控制站群組成員資格已經複製到該 GC 伺服器驗證 GC 連接。Verify connectivity to a GC from the server where you run New-ADDCCloneConfigFile and verify that the membership of the source domain controller in the Cloneable Domain Controllers group has replicated to that GC.

清除位置 GC 或俠可能已被離線最近案例俠定位器快取的方式執行下列命令:Run the following command as a means of flushing the DC locator cache for cases where a GC or DC may have been taken offline recently:

程式碼-nltest /dsgetdc: /GC /FORCECode - nltest /dsgetdc: /GC /FORCE

進階疑難排解Advanced Troubleshooting

這個模組設法教導進階疑難排解,透過使用登某些解釋所發生的範例,以。This module seeks to teach advanced troubleshooting by using working logs as samples, with some explanation of what occurred. 如果您了解成功模擬的網域控制站作業的外觀,失敗明顯地在您的環境中。If you understand what a successful virtualized domain controller operation looks like, failures become obvious in your environment. 這些登的出示來源的遞增訂單以如預期般(即使是警告和錯誤) 的活動相關複製的網域控制站在每個登入。These logs are presented by their source, with the ascending order of expected events (even when they are warnings and errors) related to a cloned domain controller within each log.

複製網域控制站Cloning a Domain Controller

複製網域控制站使用 DHCP,以取得 IP 位址、 複製 SYSVOL 在此範例中,使用 FRS 或 DFSR (所需的查看適當的登入,) 首先,並使用空白 dccloneconfig.xml 檔案。In this example, the clone domain controller uses DHCP to get an IP address, replicates SYSVOL using FRS or DFSR (see the appropriate log as necessary), is a global catalog, and uses a blank dccloneconfig.xml file.

Directory 服務事件登入Directory Services Event Log

Directory 服務登入包含大部分事件基礎複製操作資訊。The Directory Services log contains the majority of event-based cloning operational information. Hypervisor 變更 VM 新一代 ID 及 NTDS 服務筆記它,然後失效 RID 集區變更叫用 id。The hypervisor changes the VM-Generation ID and the NTDS service notes it, then invalidates the RID pool and changes the invocation ID. 設定新的 VM 新一代 ID 和伺服器會複寫 Active Directory 輸入資料。The new VM-Generation ID is set and the server replicates Active Directory data inbound. DFSR 服務已停止和刪除裝載 SYSVOL 其資料庫,強迫未經授權的同步輸入。The DFSR service is stopped and its database that hosts SYSVOL is deleted, forcing a non-authoritative sync inbound. 調整 USN 高浮水印。The USN high watermark is adjusted.

事件編號Event ID 來源Source 訊息Message
21602160 ActiveDirectory_DomainServiceActiveDirectory_DomainService 本機 Active Directory Domain Services 發現 virtual 網域控制站複製設定檔。The local Active Directory Domain Services has found a virtual domain controller cloning configuration file.

在找到 virtual 網域控制站複製設定檔:The virtual domain controller cloning configuration file is found at:

\DCCloneConfig.xml\DCCloneConfig.xml

差 virtual 網域控制站複製設定檔表示本機 virtual 網域控制站其他 virtual 網域控制站的複本。The existence of the virtual domain controller cloning configuration file indicates that the local virtual domain controller is a clone of another virtual domain controller. Active Directory Domain Services 將會開始複製本身。The Active Directory Domain Services will start to clone itself.
21912191 ActiveDirectory_DomainServiceActiveDirectory_DomainService Active Directory Domain Services 設定下列登錄值來停用 DNS 更新。Active Directory Domain Services set the following registry value to disable DNS updates.

登錄鍵:Registry Key:

SYSTEM\CurrentControlSet\Services\Netlogon\ParametersSYSTEM\CurrentControlSet\Services\Netlogon\Parameters

登錄值:Registry Value:

UseDynamicDnsUseDynamicDns

登錄數值資料:Registry Value data:

00

複製程序,在本機電腦可能會有一小段時間複製來源電腦相同電腦的名稱。During the cloning process, the local machine may have the same computer name as the clone source machine for a short time. DNS A AAAA 記錄登記會停用在這段期間,因此戶端找不到本機電腦目前正在進行複製傳送要求。DNS A and AAAA record registration are disabled during this period so clients cannot send requests to the local machine undergoing cloning. 複製程序將會複製完成後,再試一次讓 DNS 更新。The cloning process will enable DNS updates again after cloning is completed.
21912191 ActiveDirectory_DomainServiceActiveDirectory_DomainService Active Directory Domain Services 設定下列登錄值來停用 DNS 更新。Active Directory Domain Services set the following registry value to disable DNS updates.

登錄鍵:Registry Key:

SYSTEM\CurrentControlSet\Services\Dnscache\ParametersSYSTEM\CurrentControlSet\Services\Dnscache\Parameters

登錄值:Registry Value:

RegistrationEnabledRegistrationEnabled

登錄數值資料:Registry Value data:

00

複製程序,在本機電腦可能會有一小段時間複製來源電腦相同電腦的名稱。During the cloning process, the local machine may have the same computer name as the clone source machine for a short time. DNS A AAAA 記錄登記會停用在這段期間,因此戶端找不到本機電腦目前正在進行複製傳送要求。DNS A and AAAA record registration are disabled during this period so clients cannot send requests to the local machine undergoing cloning. 複製程序將會複製完成後,再試一次讓 DNS 更新。The cloning process will enable DNS updates again after cloning is completed.

「 資訊 2 月 7 日 2012年 3:12:49 PM Microsoft-Windows-ActiveDirectory_DomainService 2191 內部設定 「 Active Directory Domain Services 下列登錄將值設為停用 DNS 更新。"Information 2/7/2012 3:12:49 PM Microsoft-Windows-ActiveDirectory_DomainService 2191 Internal Configuration" Active Directory Domain Services set the following registry value to disable DNS updates.

登錄鍵:Registry Key:

SYSTEM\CurrentControlSet\Services\Tcpip\ParametersSYSTEM\CurrentControlSet\Services\Tcpip\Parameters

登錄值:Registry Value:

DisableDynamicUpdateDisableDynamicUpdate

登錄數值資料:Registry Value data:

11

複製程序,在本機電腦可能會有一小段時間複製來源電腦相同電腦的名稱。During the cloning process, the local machine may have the same computer name as the clone source machine for a short time. DNS A AAAA 記錄登記會停用在這段期間,因此戶端找不到本機電腦目前正在進行複製傳送要求。DNS A and AAAA record registration are disabled during this period so clients cannot send requests to the local machine undergoing cloning. 複製程序將會複製完成後,再試一次讓 DNS 更新。The cloning process will enable DNS updates again after cloning is completed.
21722172 ActiveDirectory_DomainServiceActiveDirectory_DomainService 朗讀 msDS GenerationId 網域控制站的電腦物件的屬性。Read the msDS-GenerationId attribute of the Domain Controller's computer object.

msDS-GenerationId 屬性的值:msDS-GenerationId attribute value:

21702170 ActiveDirectory_DomainServiceActiveDirectory_DomainService 偵測到代 ID 變更。A Generation ID change has been detected.

代來電顯示快取中 DS (舊值):Generation ID cached in DS (old value):



代目前中 ID VM (新值):Generation ID currently in VM (new value):



一樣快照的應用程式、 一樣匯入操作後或即時移轉作業之後,就會發生代 ID 變更。The Generation ID change occurs after the application of a virtual machine snapshot, after a virtual machine import operation or after a live migration operation. Active Directory Domain Services 會建立新的叫用 ID 復原網域控制站。Active Directory Domain Services will create a new invocation ID to recover the domain controller. 應還原模擬的網域控制站使用一樣的快照。Virtualized domain controllers should not be restored using virtual machine snapshots. 支援的方法來還原或復原 content 的 Active Directory Domain Services 資料庫是還原所做的 Active Directory Domain Services 注意備份應用程式的系統狀態備份。The supported method to restore or rollback the content of an Active Directory Domain Services database is to restore a system state backup made with an Active Directory Domain Services aware backup application.
11091109 ActiveDirectory_DomainServiceActiveDirectory_DomainService 已變更此 directory 伺服器呼叫識別碼屬性。The invocationID attribute for this directory server has been changed. 在建立備份之的時間的最高更新序號如下:The highest update sequence number at the time the backup was created is as follows:

呼叫識別碼屬性 (舊值):InvocationID attribute (old value):



呼叫識別碼屬性 (新值):InvocationID attribute (new value):



更新的序號:Update sequence number:



呼叫識別碼 directory 伺服器還原備份媒體,從時變更設定為主控寫入應用程式 directory 磁碟分割、 已繼續一樣快照套用之後,在一樣匯入作業,或之後即時移轉作業。The invocationID is changed when a directory server is restored from backup media, is configured to host a writeable application directory partition, has been resumed after a virtual machine snapshot has been applied, after a virtual machine import operation, or after a live migration operation. 應還原模擬的網域控制站使用一樣的快照。Virtualized domain controllers should not be restored using virtual machine snapshots. 還原或回復到支援的方法的 Active Directory Domain Services 資料庫 content 是還原進行備份 Active Directory Domain Services 感知應用程式的系統狀態備份。The supported method to restore or rollback the content of an Active Directory Domain Services database is to restore a system state backup made with an Active Directory Domain Services-aware backup application.
10001000 ActiveDirectory_DomainServiceActiveDirectory_DomainService Microsoft Active Directory Domain Services 開機完成。Microsoft Active Directory Domain Services startup complete.
13941394 ActiveDirectory_DomainServiceActiveDirectory_DomainService 已經清除所有 Active Directory Domain Services 資料庫防止更新的問題。All problems preventing updates to the Active Directory Domain Services database have been cleared. Active Directory Domain Services 資料庫的新更新的成功。New updates to the Active Directory Domain Services database are succeeding. 此時網路登入服務。The Net Logon service has restarted
21632163 ActiveDirectory_DomainServiceActiveDirectory_DomainService DsRoleSvc 服務已複製本機 virtual 網域控制站開始。DsRoleSvc service was started to clone the local virtual domain controller.
326326 NTDS ISAMNTDS ISAM NTDS (536) NTDSA: 資料庫引擎連接資料庫 (1、 C:\Windows\NTDS\ntds.dit)。NTDS (536) NTDSA: The database engine attached a database (1, C:\Windows\NTDS\ntds.dit). (時間 = 0 秒)(Time=0 seconds)

內部的時間順序: 0.000 [1] 0.000 [2]、 0.000 [3]、 [4] 0.000、 0.000 [5]、 [6] 0.016、 0.000 [7]、 0.000 [8]、 [9] 0.000、 0.000 [10]、 0.000 [11]、 [12] 0.000。Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.000, [4] 0.000, [5] 0.000, [6] 0.016, [7] 0.000, [8] 0.000, [9] 0.000, [10] 0.000, [11] 0.000, [12] 0.000.

儲存快取︰ 1Saved Cache: 1
103103 NTDS ISAMNTDS ISAM NTDS (536) NTDSA: 資料庫引擎停止 (0) 的執行個體。NTDS (536) NTDSA: The database engine stopped the instance (0).

不正常關機: 0Dirty Shutdown: 0

內部的時間順序: 0.000 [1] 0.000 [2]、 0.000 [3]、 [4] 0.000、 0.032 [5]、 [6] 0.000、 0.000 [7]、 0.000 [8]、 0.031 [9]、 0.000 [10]、 0.000 [11]、 [12] 0.000、 0.000 [13]、 [14] 0.000、 0.000 [15]。Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.000, [4] 0.000, [5] 0.032, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.031, [10] 0.000, [11] 0.000, [12] 0.000, [13] 0.000, [14] 0.000, [15] 0.000.
102102 NTDS ISAMNTDS ISAM NTDS (536) NTDSA: 資料庫引擎 (6.02.8225.0000) 新執行個體 (0) 開始。NTDS (536) NTDSA: The database engine (6.02.8225.0000) is starting a new instance (0).
105105 NTDS ISAMNTDS ISAM NTDS (536) NTDSA: 資料庫引擎會開始新的執行個體 (0)。NTDS (536) NTDSA: The database engine started a new instance (0). (時間 = 0 秒)(Time=0 seconds)

內部的時間順序: 0.016 [1] 0.000 [2]、 0.015 [3]、 [4] 0.078、 [5] 0.000、 0.000 [6]、 [7] 0.000、 0.000 [8]、 [9] 0.046、 0.000 [10]、 0.000 [11]。Internal Timing Sequence: [1] 0.016, [2] 0.000, [3] 0.015, [4] 0.078, [5] 0.000, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.046, [10] 0.000, [11] 0.000.
10041004 ActiveDirectory_DomainServiceActiveDirectory_DomainService Active Directory Domain Services 成功關機。Active Directory Domain Services was shut down successfully.
102102 NTDS ISAMNTDS ISAM NTDS (536) NTDSA: 資料庫引擎 (6.02.8225.0000) 新執行個體 (0) 開始。NTDS (536) NTDSA: The database engine (6.02.8225.0000) is starting a new instance (0).
326326 NTDS ISAMNTDS ISAM NTDS (536) NTDSA: 資料庫引擎連接資料庫 (1、 C:\Windows\NTDS\ntds.dit)。NTDS (536) NTDSA: The database engine attached a database (1, C:\Windows\NTDS\ntds.dit). (時間 = 0 秒)(Time=0 seconds)

內部的時間順序: 0.000 [1] 0.015 [2]、 0.016 [3]、 [4] 0.000、 0.031 [5]、 [6] 0.000、 0.000 [7]、 0.000 [8]、 [9] 0.000、 0.000 [10]、 [11] 0.000、 0.000 [12]。Internal Timing Sequence: [1] 0.000, [2] 0.015, [3] 0.016, [4] 0.000, [5] 0.031, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.000, [10] 0.000, [11] 0.000, [12] 0.000.

儲存快取︰ 1Saved Cache: 1
105105 NTDS ISAMNTDS ISAM NTDS (536) NTDSA: 資料庫引擎會開始新的執行個體 (0)。NTDS (536) NTDSA: The database engine started a new instance (0). (時間 = 1 秒)(Time=1 seconds)

內部的時間順序: 0.031 [1] 0.000 [2]、 0.000 [3]、 [4] 0.391、 [5] 0.000、 0.000 [6]、 [7] 0.000、 0.000 [8]、 [9] 0.031、 0.000 [10]、 0.000 [11]。Internal Timing Sequence: [1] 0.031, [2] 0.000, [3] 0.000, [4] 0.391, [5] 0.000, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.031, [10] 0.000, [11] 0.000.
11091109 ActiveDirectory_DomainServiceActiveDirectory_DomainService 已變更此 directory 伺服器呼叫識別碼屬性。The invocationID attribute for this directory server has been changed. 在建立備份之的時間的最高更新序號如下:The highest update sequence number at the time the backup was created is as follows:

呼叫識別碼屬性 (舊值):InvocationID attribute (old value):



呼叫識別碼屬性 (新值):InvocationID attribute (new value):



更新的序號:Update sequence number:



呼叫識別碼 directory 伺服器還原備份媒體,從時變更設定為主控寫入應用程式 directory 磁碟分割、 已繼續一樣快照套用之後,在一樣匯入作業,或之後即時移轉作業。The invocationID is changed when a directory server is restored from backup media, is configured to host a writeable application directory partition, has been resumed after a virtual machine snapshot has been applied, after a virtual machine import operation, or after a live migration operation. 應還原模擬的網域控制站使用一樣的快照。Virtualized domain controllers should not be restored using virtual machine snapshots. 還原或回復到支援的方法的 Active Directory Domain Services 資料庫 content 是還原進行備份 Active Directory Domain Services 感知應用程式的系統狀態備份。The supported method to restore or rollback the content of an Active Directory Domain Services database is to restore a system state backup made with an Active Directory Domain Services-aware backup application.
11681168 ActiveDirectory_DomainServiceActiveDirectory_DomainService 內部錯誤: Active Directory Domain Services 錯誤。Internal error: An Active Directory Domain Services error has occurred.

其他資料Additional Data

錯誤值 (小數點):Error value (decimal):

22

錯誤值 (十六進位):Error value (hexadecimal):

22

內部 ID:Internal ID:

70116587011658
11101110 ActiveDirectory_DomainServiceActiveDirectory_DomainService 首先這個網域控制站升級將會延遲下列間隔。Promotion of this domain controller to a global catalog will be delayed for the following interval.

間隔 (分鐘):Interval (minutes):

55

這樣可以準備需要的 directory 磁碟分割通用通知時,所需此延遲。This delay is necessary so that the required directory partitions can be prepared before the global catalog is advertised. 在登錄中,您可以指定 directory 系統代理程式之前重點首先本機網域控制站等待秒數。In the registry, you can specify the number of seconds that the directory system agent will wait before promoting the local domain controller to a global catalog. 如需全球 Catalog 延遲廣告登錄值,查看資源套件散發系統指南For more information about the Global Catalog Delay Advertisement registry value, see the Resource Kit Distributed Systems Guide
103103 NTDS ISAMNTDS ISAM NTDS (536) NTDSA: 資料庫引擎停止 (0) 的執行個體。NTDS (536) NTDSA: The database engine stopped the instance (0).

不正常關機: 0Dirty Shutdown: 0

內部的時間順序: 0.000 [1] 0.000 [2]、 0.000 [3]、 [4] 0.000、 0.047 [5]、 [6] 0.000、 0.000 [7]、 0.000 [8]、 0.016 [9]、 0.000 [10]、 0.000 [11]、 [12] 0.000、 0.000 [13]、 [14] 0.000、 0.000 [15]。Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.000, [4] 0.000, [5] 0.047, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.016, [10] 0.000, [11] 0.000, [12] 0.000, [13] 0.000, [14] 0.000, [15] 0.000.
10041004 ActiveDirectory_DomainServiceActiveDirectory_DomainService Active Directory Domain Services 成功關機。Active Directory Domain Services was shut down successfully.
15391539 ActiveDirectory_DomainServiceActiveDirectory_DomainService Active Directory Domain Services 無法停用軟體的磁碟寫入快取下列硬碟上。Active Directory Domain Services could not disable the software-based disk write cache on the following hard disk.

硬碟:Hard disk:

c:c:

可能會遺失資料系統失敗Data might be lost during system failures
21792179 ActiveDirectory_DomainServiceActiveDirectory_DomainService MsDS-GenerationId 物件的屬性網域控制站的電腦已設定為下列參數:The msDS-GenerationId attribute of the Domain Controller's computer object has been set to the following parameter:

GenerationID 屬性:GenerationID attribute:

21732173 ActiveDirectory_DomainServiceActiveDirectory_DomainService 無法讀取 msDS-GenerationId 網域控制站的電腦物件的屬性。Failed to read the msDS-GenerationId attribute of the Domain Controller's computer object. 這可能因為資料庫交易失敗,或在本機資料庫代 id 不存在。This may be caused by database transaction failure, or the generation id does not exist in the local database. 之後帶領或俠不 virtual 網域控制站 msDS GenerationId 不存在期間的第一次重新開機。The msDS-GenerationId does not exist during the first reboot after dcpromo or the DC is not a virtual domain controller.

其他資料Additional Data

失敗碼:Failure code:

66
10001000 ActiveDirectory_DomainServiceActiveDirectory_DomainService Microsoft Active Directory Domain Services 開機完成,6.2.8225.0 版本Microsoft Active Directory Domain Services startup complete, version 6.2.8225.0
13941394 ActiveDirectory_DomainServiceActiveDirectory_DomainService 已經清除所有 Active Directory Domain Services 資料庫防止更新的問題。All problems preventing updates to the Active Directory Domain Services database have been cleared. Active Directory Domain Services 資料庫的新更新的成功。New updates to the Active Directory Domain Services database are succeeding. 此時網路登入服務。The Net Logon service has restarted.
11281128 ActiveDirectory_DomainServiceActiveDirectory_DomainService 1128 認知一致性檢查 」 複寫連接已從下列來源 directory 服務建立本機 directory 服務。1128 Knowledge Consistency Checker "A replication connection was created from the following source directory service to the local directory service.

來源 directory 服務:Source directory service:

DATA-CN = NTDS 設定]CN=NTDS Settings,

本機 directory 服務:Local directory service:

DATA-CN = NTDS 設定]CN=NTDS Settings,

其他資料Additional Data

原因代碼:Reason Code:

0x20x2

建立點內部 ID:Creation Point Internal ID:

f0a025df0a025d
19991999 ActiveDirectory_DomainServiceActiveDirectory_DomainService 來源 directory 服務已最佳化的更新序號 (USN) 出示目的地 directory 服務。The source directory service has optimized the update sequence number (USN) presented by the destination directory service. 來源和目的地 directory 服務有常見複寫合作夥伴。The source and destination directory services have a common replication partner. 目的地 directory 服務是最新的常見問題︰ 複寫合作夥伴,並安裝來源 directory 服務使用此合作夥伴的備份。The destination directory service is up to date with the common replication partner, and the source directory service was installed using a backup of this partner.

目的地 directory 服務 ID:Destination directory service ID:

()()

一般 directory 服務 ID:Common directory service ID:



常見的屬性 USN:Common property USN:



如此一來,最新的向量的目的地 directory 服務已使用下列設定。As a result, the up-to-dateness vector of the destination directory service has been configured with the following settings.

先前的物件 USN:Previous object USN:

00

先前屬性 USN:Previous property USN:

00

資料庫 GUID:Database GUID:



物件 USN:Object USN:



屬性 USN:Property USN:

系統事件登入System Event Log

下一步的複製操作指示位於系統事件登入。The next indications of cloning operations are in the System Event log. Hypervisor 告訴來賓電腦已複製或還原的開發進程的快照,為網域控制站立即使其 RID 集區,以避免稍後複製安全性原則。As the hypervisor tells the guest computer that it was cloned or restored from a snapshot, the domain controller immediately invalidates its RID pool to avoid duplicating security principals later. 複製繼續,各種預期的作業和訊息會顯示,大部分操作開始和停止的服務,某些預期這造成錯誤。As cloning proceeds, various expected operations and messages appear, mostly around services starting and stopping and some expected errors caused by this. 當您完成整體複製成功系統事件登入資訊。When completed the System event log notes overall cloning success.

事件編號Event ID 來源Source 訊息Message
1665416654 薩姆-directory-服務Directory-Services-SAM 已無效 account 識別碼 (Rid) 的集區。A pool of account-identifiers (RIDs) has been invalidated. 這可能是因為預期如下:This may occur in the following expected cases:

1.網域控制站是從備份還原。1. A domain controller is restored from backup.

2.網域控制站執行一樣會還原的快照。2. A domain controller running on a virtual machine is restored from snapshot.

3.系統管理員已手動失效集區3. An administrator has manually invalidated the pool
70367036 服務控制管理員Service Control Manager Active Directory Domain Services 服務進入執行的狀態。The Active Directory Domain Services service entered the running state.
70367036 服務控制管理員Service Control Manager Kerberos 鍵 Distribution 中心服務輸入執行的狀態。The Kerberos Key Distribution Center service entered the running state.
30963096 NetlogonNetlogon 找不到此網域主要網域控制站。The primary Domain Controller for this domain could not be located.
70367036 服務控制管理員Service Control Manager 安全性帳號管理員服務輸入執行的狀態。The Security Accounts Manager service entered the running state.
70367036 服務控制管理員Service Control Manager 伺服器服務輸入執行的狀態。The Server service entered the running state.
70367036 服務控制管理員Service Control Manager Netlogon 服務輸入執行的狀態。The Netlogon service entered the running state.
70367036 服務控制管理員Service Control Manager Active Directory Web 服務服務進入執行的狀態。The Active Directory Web Services service entered the running state.
70367036 服務控制管理員Service Control Manager DFS 複寫服務輸入執行的狀態。The DFS Replication service entered the running state.
70367036 服務控制管理員Service Control Manager 檔案複製服務輸入執行的狀態。The File Replication Service service entered the running state.
1453314533 Microsoft-Windows-DfsSvcMicrosoft-Windows-DfsSvc 建置所有命名空間已經 DFS。DFS has finished building all namespaces.
1453114531 Microsoft-Windows-DfsSvcMicrosoft-Windows-DfsSvc 完成初始化 DFS 伺服器。DFS server has finished initializing.
70367036 服務控制管理員Service Control Manager DFS 命名空間服務進入執行的狀態。The DFS Namespace service entered the running state.
70237023 服務控制管理員Service Control Manager 間的訊息中心服務終止錯誤如下:The Intersite Messaging service terminated with the following error:

指定的伺服器無法執行要求的作業。The specified server cannot perform the requested operation.
70367036 服務控制管理員Service Control Manager 間的訊息中心服務輸入停止的狀態。The Intersite Messaging service entered the stopped state.
58065806 NetlogonNetlogon 動態更新已在這個網域控制站手動停用。Dynamic updates have been manually disabled on this domain controller.

使用者動作USER ACTION

重新設定使用動態更新,或是手動新增 DNS 記錄從檔案 '%systemroot%\system32\config\netlogon.dns' DNS 資料庫這個網域控制站 」。Reconfigure this domain controller to use dynamic updates or manually add the DNS records from the file '%SystemRoot%\System32\Config\Netlogon.dns' to the DNS database."
1665116651 薩姆-directory-服務Directory-Services-SAM 新的 account 識別碼集區要求失敗。The request for a new account-identifier pool failed. 成功要求之前,將會重試作業。The operation will be retried until the request succeeds. 錯誤The error is

FSMO 操作失敗。The requested FSMO operation failed. 無法連絡目前 FSMO 擁有者。The current FSMO holder could not be contacted.
70367036 服務控制管理員Service Control Manager 輸入的 DNS 伺服器服務執行的狀態。The DNS Server service entered the running state.
70367036 服務控制管理員Service Control Manager DS 角色伺服器服務輸入執行的狀態。The DS Role Server service entered the running state.
70367036 服務控制管理員Service Control Manager Netlogon 服務輸入停止的狀態。The Netlogon service entered the stopped state.
70367036 服務控制管理員Service Control Manager 檔案複製服務輸入停止的狀態。The File Replication Service service entered the stopped state.
70367036 服務控制管理員Service Control Manager Kerberos 鍵 Distribution 中心服務輸入停止的狀態。The Kerberos Key Distribution Center service entered the stopped state.
70367036 服務控制管理員Service Control Manager DNS 伺服器服務輸入停止的狀態。The DNS Server service entered the stopped state.
70367036 服務控制管理員Service Control Manager Active Directory Domain Services 服務輸入停止的狀態。The Active Directory Domain Services service entered the stopped state.
70367036 服務控制管理員Service Control Manager Netlogon 服務輸入執行的狀態。The Netlogon service entered the running state.
70407040 服務控制管理員Service Control Manager 停用來從自動開始變更 [開始] 畫面的 Active Directory Domain Services 服務類型。The start type of the Active Directory Domain Services service was changed from auto start to disabled.
70367036 服務控制管理員Service Control Manager Netlogon 服務輸入停止的狀態。The Netlogon service entered the stopped state.
70367036 服務控制管理員Service Control Manager 檔案複製服務輸入執行的狀態。The File Replication Service service entered the running state.
2921929219 對 DSROLE 伺服器DirectoryServices-DSROLE-Server Virtual 網域控制站複製成功。Virtual domain controller cloning succeeded.
2922329223 對 DSROLE 伺服器DirectoryServices-DSROLE-Server 這個伺服器現在已網域控制站。This server is now a Domain Controller.
2926529265 對 DSROLE 伺服器DirectoryServices-DSROLE-Server Virtual 網域控制站複製成功。Virtual domain controller cloning succeeded. 複製設定檔 C:\Windows\NTDS\DCCloneConfig.xml virtual 網域控制站已 C:\Windows\NTDS\DCCloneConfig.20120207-151533.xml 以重新命名。The virtual domain controller cloning configuration file C:\Windows\NTDS\DCCloneConfig.xml has been renamed to C:\Windows\NTDS\DCCloneConfig.20120207-151533.xml.
10741074 User32User32 此程序 C:\Windows\system32\lsass.exe (DC2) 已車載機起始 DC2 的電腦重新開機,代表使用者 NT AUTHORITY\SYSTEM 原因如下: 作業系統: 重新設定 (計劃中)The process C:\Windows\system32\lsass.exe (DC2) has initiated the restart of computer DC2 on behalf of user NT AUTHORITY\SYSTEM for the following reason: Operating System: Reconfiguration (Planned)

程式碼的原因︰ 0x80020004Reason Code: 0x80020004

關機類型: 重新開機Shutdown Type: restart

意見: 」Comment: "
帶領。登入DCPROMO.LOG

Dcpromo.log 包含實際促銷複製的一部分無法描述 Directory 服務事件登入。The Dcpromo.log contains the actual promotion portion of cloning that the Directory Services event log does not describe. 登入不提供的事件登入的項目傳授的解釋層級,因為模組的此一節包含其他附注。Since the log does not provide the level of explanation that the event log entries impart, this section of the module contains additional annotation.

升級程序表示複製開始,DC 在其目前的組態刪除,並重新升級使用現有的廣告資料庫 (更像是 IFM 升級),然後 DC 複製輸入的變更 delta 的廣告且 SYSVOL,和複製已完成。The promotion process means that the cloning starts, the DC is scrubbed of its current configuration and re-promoted using the existing AD database (much like an IFM promotion), then the DC replicates inbound change deltas of AD and SYSVOL, and cloning is complete.

注意

登入可讀性,本單元已修改日期欄中移除。The log has been modified in this module for readability, by removing the date column.

注意

進一步解釋 dcpromo.log 看到瞭解與疑難排解 AD DS 簡化管理 Windows Server 2012 中。For further explanation of the dcpromo.log see the Understand and Troubleshoot AD DS Simplified Administration in Windows Server 2012.

http://go.microsoft.com/fwlink/p/?LinkId=237244http://go.microsoft.com/fwlink/p/?LinkId=237244

  • 複製型促銷 [開始]Start clone-based promotion

  • 設定 Directory 服務還原模式旗標伺服器會不會開機備份通常為原始的複製和原因命名或 Directory 服務衝突,Set the Directory Services Restore Mode flag so that the server does not boot back up normally as the original clone and cause naming or Directory Service collisions

  • 更新服務 Directory 事件登入Update the Directory Services event log

15:14:01 [INFO] vDC Cloneing: Setting Boot into DSRM flag succeeded.  
15:14:01 [WARNING] Cannot get user Token for Format Message: 1725l  
15:14:01 [INFO] vDC Cloning: Created vDCCloningUpdate event.  
15:14:01 [INFO] vDC Cloning: Created vDCCloningComplete event.  
  • 因此,不會通知的網域控制站停止 NetLogon 服務Stop the NetLogon service so that the domain controller does not advertise
15:14:01 [INFO] Stopping service NETLOGON  
15:14:01 [INFO] ControlService(STOP) on NETLOGON returned 1(gle=0)  
15:14:01 [INFO] DsRolepWaitForService: waiting for NETLOGON to enter one of 7 states  
15:14:01 [INFO] DsRolepWaitForService: QueryServiceStatus on NETLOGON returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:02 [INFO] DsRolepWaitForService: QueryServiceStatus on NETLOGON returned 1 (gle=0), SvcStatus.dwCS=1  
15:14:02 [INFO] DsRolepWaitForService: exiting because NETLOGON entered STOPPED state  
15:14:02 [INFO] DsRolepWaitForService(for any end state) on NETLOGON service returned 0  
15:14:02 [INFO] ControlService(STOP) on NETLOGON returned 0(gle=1062)  
15:14:02 [INFO] Exiting service-stop loop after service NETLOGON entered STOPPED state  
15:14:02 [INFO] StopService on NETLOGON returned 0  
15:14:02 [INFO] Configuring service NETLOGON to 1 returned 0  
15:14:02 [INFO] Updating service status to 4  
15:14:02 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
  • 檢查 dccloneconfig.xml 管理員指定自訂設定檔。Examine the dccloneconfig.xml file for administrator-specified customizations.

  • 在此範例案例是空白的檔案,因此專自動到 [所有設定,而且自動 IP 位址所需的網路In this sample case it is a blank file, so all settings are automatically generated and automatic IP addressing is required from the network

15:14:02 [INFO] vDC Cloning: Clone config file C:\Windows\NTDS\DCCloneConfig.xml is considered to be a blank file (containing 0 bytes)  
15:14:02 [INFO] vDC Cloning: Parsing clone config file C:\Windows\NTDS\DCCloneConfig.xml returned HRESULT 0x0  
  • 確認您不有任何服務或不是 DefaultDCCloneAllowList.xml 或 CustomDCCloneAllowList.xml 的安裝程式Validate that there are no services or programs installed that are not part of the DefaultDCCloneAllowList.xml or CustomDCCloneAllowList.xml
15:14:02 [INFO] vDC Cloning: Checking allowed list:  
15:14:03 [INFO] vDC Cloning: Completed checking allowed list:  
15:14:03 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
  • 由於系統管理員不指定 IP 資訊,讓 DHCP 網路介面卡Enable DHCP on the network adapters, since IP information was not specified by the administrator
15:14:03 [INFO] vDC Cloning: Enable DHCP:  
15:14:03 [INFO] WMI Instance: Win32_NetworkAdapterConfiguration.Index=12  
15:14:03 [INFO] Method: EnableDHCP  
15:14:03 [INFO] HRESULT code: 0x0 (0)  
15:14:03 [INFO] Return Value: 0x0 (0)  
15:14:03 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
15:14:03 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
  • 找出肯定Locate the PDC emulator

  • 設定 (在本案例自動產生) 複製的網站Set the clone's site (automatically generated in this case)

  • 設定複製的名稱 (在本案例自動產生)Set the clone's name (automatically generated in this case)

15:14:03 [INFO] vDC Cloning: Found PDC. Name: DC1.root.fabrikam.com  
15:14:04 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
15:14:04 [INFO] vDC Cloning: Winlogon UI Notification #1: Domain Controller cloning is at 5% completion...  
15:14:05 [INFO] vDC Cloning: Winlogon UI Notification #2: Domain Controller cloning is at 10% completion...  
15:14:05 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
15:14:05 [INFO] Site of the cloned DC: Default-First-Site-Name  
  • 建立新的複製電腦物件Create the new clone computer object

  • 重新命名的複製符合新名稱Rename the clone to match the new name

15:14:05 [INFO] vDC Cloning: Clone DC objects are created on PDC.  
15:14:05 [INFO] Name of the cloned DC: DC2-CL0001  
15:14:05 [INFO] DsRolepSetRegStringValue on System\CurrentControlSet\Services\NTDS\Parameters\CloneMachineName to DC2-CL0001 returned 0  
15:14:05 [INFO] vDC Cloning: Save CloneMachineName in registry: 0x0 (0)  
  • 提供促銷設定,根據先前 dccloneconfig.xml 或自動代規則Provide the promotion settings, based on previous dccloneconfig.xml or automatic generation rules
15:14:05 [INFO] vDC Cloning: Promotion parameters setting:  
15:14:05 [INFO] DNS Domain Name: root.fabrikam.com  
15:14:05 [INFO] Replica Partner: \\DC1.root.fabrikam.com  
15:14:05 [INFO] Site Name: Default-First-Site-Name  
15:14:05 [INFO] DS Database Path: C:\Windows\NTDS  
15:14:05 [INFO] DS Log Path: C:\Windows\NTDS  
15:14:05 [INFO] SysVol Root Path: C:\Windows\SYSVOL  
15:14:05 [INFO] Account: root.fabrikam.com\DC2-CL0001$  
15:14:05 [INFO] Options: DSROLE_DC_CLONING (0x800400)  
  • [開始升級]Start promotion
15:14:05 [INFO] Promote DC as a clone  
15:14:05 [INFO] vDC Cloning: Winlogon UI Notification #3: Domain Controller cloning is at 15% completion...  
15:14:05 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
15:14:05 [INFO] vDC Cloning: Winlogon UI Notification #4: Domain Controller cloning is at 16% completion...  
15:14:05 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
15:14:05 [INFO] Validate supplied paths  
15:14:05 [INFO] Validating path C:\Windows\NTDS.  
15:14:05 [INFO] Path is a directory  
15:14:05 [INFO] Path is on a fixed disk drive.  
15:14:05 [INFO] Validating path C:\Windows\NTDS.  
15:14:05 [INFO] Path is a directory  
15:14:05 [INFO] Path is on a fixed disk drive.  
15:14:05 [INFO] Validating path C:\Windows\SYSVOL.  
15:14:05 [INFO] Path is on a fixed disk drive.  
15:14:05 [INFO] Path is on an NTFS volume  
15:14:05 [INFO] vDC Cloning: Winlogon UI Notification #5: Domain Controller cloning is at 17% completion...  
15:14:05 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
15:14:05 [INFO] Start the worker task  
15:14:05 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
15:14:05 [INFO] vDC Cloning: Winlogon UI Notification #6: Domain Controller cloning is at 20% completion...  
15:14:05 [INFO] Request for promotion returning 0  
15:14:05 [INFO] vDC Cloning: Winlogon UI Notification #7: Domain Controller cloning is at 21% completion...  
15:14:05 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
  • 停止和設定的所有 AD DS 相關服務 NTDS、 NTFRS 日 DFSR、 \ [KDC (DNS)Stop and configure all of the AD DS-related services (NTDS, NTFRS/DFSR, KDC, DNS)

注意

關閉拍攝一段時間 DNS 服務會如預期般在本案例中,它會使用已不再提供更之前停止-NTDS 服務的廣告整合區域看到模組的此一節所述稍後 DNS 事件。The DNS service taking a long time to shutdown is expected in this scenario, as it is using AD-integrated zones that were no longer available even before the NTDS service stopped - see the DNS events described later in this section of the module.

15:14:15 [INFO] Stopping service NTDS  
15:14:15 [INFO] Stopping service NtFrs  
15:14:15 [INFO] ControlService(STOP) on NtFrs returned 1(gle=0)  
15:14:15 [INFO] DsRolepWaitForService: waiting for NtFrs to enter one of 7 states  
15:14:15 [INFO] DsRolepWaitForService: QueryServiceStatus on NtFrs returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:16 [INFO] DsRolepWaitForService: QueryServiceStatus on NtFrs returned 1 (gle=0), SvcStatus.dwCS=1  
15:14:16 [INFO] DsRolepWaitForService: exiting because NtFrs entered STOPPED state  
15:14:16 [INFO] DsRolepWaitForService(for any end state) on NtFrs service returned 0  
15:14:16 [INFO] ControlService(STOP) on NtFrs returned 0(gle=1062)  
15:14:16 [INFO] Exiting service-stop loop after service NtFrs entered STOPPED state  
15:14:16 [INFO] StopService on NtFrs returned 0  
15:14:16 [INFO] Configuring service NtFrs to 1 returned 0  
15:14:16 [INFO] Stopping service Kdc  
15:14:16 [INFO] ControlService(STOP) on Kdc returned 1(gle=0)  
15:14:16 [INFO] DsRolepWaitForService: waiting for Kdc to enter one of 7 states  
15:14:16 [INFO] DsRolepWaitForService: QueryServiceStatus on Kdc returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:17 [INFO] DsRolepWaitForService: QueryServiceStatus on Kdc returned 1 (gle=0), SvcStatus.dwCS=1  
15:14:17 [INFO] DsRolepWaitForService: exiting because Kdc entered STOPPED state  
15:14:17 [INFO] DsRolepWaitForService(for any end state) on Kdc service returned 0  
15:14:17 [INFO] ControlService(STOP) on Kdc returned 0(gle=1062)  
15:14:17 [INFO] Exiting service-stop loop after service Kdc entered STOPPED state  
15:14:17 [INFO] StopService on Kdc returned 0  
15:14:17 [INFO] Configuring service Kdc to 1 returned 0  
15:14:17 [INFO] Stopping service DNS  
15:14:17 [INFO] ControlService(STOP) on DNS returned 1(gle=0)  
15:14:17 [INFO] DsRolepWaitForService: waiting for DNS to enter one of 7 states  
15:14:17 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:18 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:19 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:20 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:21 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:22 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:23 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:24 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:25 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:26 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:27 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:28 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:29 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:30 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:31 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:32 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:33 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:34 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:35 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:36 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:37 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:38 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:39 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:40 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:41 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:42 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:43 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:44 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:45 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:46 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:47 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:48 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:49 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:50 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:51 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:52 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:53 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:54 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:55 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:56 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:57 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:58 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:14:59 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=3  
15:15:00 [INFO] DsRolepWaitForService: QueryServiceStatus on DNS returned 1 (gle=0), SvcStatus.dwCS=1  
15:15:00 [INFO] DsRolepWaitForService: exiting because DNS entered STOPPED state  
15:15:00 [INFO] DsRolepWaitForService(for any end state) on DNS service returned 0  
15:15:00 [INFO] ControlService(STOP) on DNS returned 0(gle=1062)  
15:15:00 [INFO] Exiting service-stop loop after service DNS entered STOPPED state  
15:15:00 [INFO] StopService on DNS returned 0  
15:15:00 [INFO] Configuring service DNS to 1 returned 0  
15:15:00 [INFO] ControlService(STOP) on NTDS returned 1(gle=1062)  
15:15:00 [INFO] DsRolepWaitForService: waiting for NTDS to enter one of 7 states  
15:15:00 [INFO] DsRolepWaitForService: QueryServiceStatus on NTDS returned 1 (gle=0), SvcStatus.dwCS=3  
15:15:01 [INFO] DsRolepWaitForService: QueryServiceStatus on NTDS returned 1 (gle=0), SvcStatus.dwCS=1  
15:15:01 [INFO] DsRolepWaitForService: exiting because NTDS entered STOPPED state  
15:15:01 [INFO] DsRolepWaitForService(for any end state) on NTDS service returned 0  
15:15:01 [INFO] ControlService(STOP) on NTDS returned 0(gle=1062)  
15:15:01 [INFO] Exiting service-stop loop after service NTDS entered STOPPED state  
15:15:01 [INFO] StopService on NTDS returned 0  
15:15:01 [INFO] Configuring service NTDS to 1 returned 0  
15:15:01 [INFO] Configuring service NTDS  
15:15:01 [INFO] Configuring service NTDS to 64 returned 0  
15:15:01 [INFO] vDC Cloning: Winlogon UI Notification #8: Domain Controller cloning is at 22% completion...  
15:15:01 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
15:15:01 [INFO] vDC Cloning: Winlogon UI Notification #9: Domain Controller cloning is at 25% completion...  
15:15:01 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
  • 強制 NT5DS (NTP) 時間同步處理的其他網域控制站 (通常是 PDCE)Force NT5DS (NTP) time synchronization with another domain controller (typically the PDCE)
15:15:02 [INFO] Forcing time sync  
  • 請連絡擁有來源網域控制站 account 複製的網域控制站Contact a domain controller that holds the source domain controller account of the clone

  • 清除任何的現有 Kerberos 門票Flush any existing Kerberos tickets

15:15:02 [INFO] Searching for a domain controller for the domain root.fabrikam.com that contains the account DC2$  
15:15:02 [INFO] Located domain controller DC1.root.fabrikam.com for domain root.fabrikam.com  
15:15:02 [INFO] vDC Cloning: Winlogon UI Notification #10: Domain Controller cloning is at 26% completion...  
15:15:02 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
15:15:02 [INFO] Directing kerberos authentication to DC1.root.fabrikam.com returns 0  
15:15:02 [INFO] DsRolepFlushKerberosTicketCache() successfully flushed the Kerberos ticket cache  
15:15:02 [INFO] vDC Cloning: Winlogon UI Notification #11: Domain Controller cloning is at 27% completion...  
15:15:02 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
15:15:02 [INFO] Using site Default-First-Site-Name for server \\DC1.root.fabrikam.com  
15:15:02 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
15:15:02 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
  • 停止 NetLogon 服務,並將其開始輸入Stop the NetLogon service and set its start type
15:15:02 [INFO] Stopping service NETLOGON  
15:15:02 [INFO] Stopping service NETLOGON  
15:15:02 [INFO] vDC Cloning: Winlogon UI Notification #12: Domain Controller cloning is at 29% completion...  
15:15:02 [INFO] ControlService(STOP) on NETLOGON returned 1(gle=0)  
15:15:02 [INFO] DsRolepWaitForService: waiting for NETLOGON to enter one of 7 states  
15:15:02 [INFO] DsRolepWaitForService: QueryServiceStatus on NETLOGON returned 1 (gle=0), SvcStatus.dwCS=3  
15:15:03 [INFO] DsRolepWaitForService: QueryServiceStatus on NETLOGON returned 1 (gle=0), SvcStatus.dwCS=1  
15:15:03 [INFO] DsRolepWaitForService: exiting because NETLOGON entered STOPPED state  
15:15:03 [INFO] DsRolepWaitForService(for any end state) on NETLOGON service returned 0  
15:15:03 [INFO] ControlService(STOP) on NETLOGON returned 0(gle=1062)  
15:15:03 [INFO] Exiting service-stop loop after service NETLOGON entered STOPPED state  
15:15:03 [INFO] StopService on NETLOGON returned 0  
15:15:03 [INFO] Configuring service NETLOGON to 1 returned 0  
15:15:03 [INFO] Stopped NETLOGON  
15:15:03 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
15:15:03 [INFO] vDC Cloning: Winlogon UI Notification #13: Domain Controller cloning is at 30% completion...  
  • 設定為自動執行 DFSR 日 NTFRS 服務Configure the DFSR/NTFRS services to run automatically

  • Delete 強制 SYSVOL 的非授權同步服務接下來開始時他們現有資料庫檔案Delete their existing database files to force non-authoritative sync of SYSVOL when the service next starts

15:15:03 [INFO] Configuring service DFSR  
15:15:03 [INFO] Configuring service DFSR to 256 returned 0  
15:15:03 [INFO] Configuring service NTFRS  
15:15:03 [INFO] Configuring service NTFRS to 256 returned 0  
15:15:03 [INFO] Removing DFSR Database files for SysVol  
15:15:03 [INFO] Removing FRS Database files in C:\Windows\ntfrs\jet  
15:15:03 [INFO] Removed C:\Windows\ntfrs\jet\log\edb.log  
15:15:03 [INFO] Removed C:\Windows\ntfrs\jet\log\edbres00001.jrs  
15:15:03 [INFO] Removed C:\Windows\ntfrs\jet\log\edbres00002.jrs  
15:15:03 [INFO] Removed C:\Windows\ntfrs\jet\log\edbtmp.log  
15:15:03 [INFO] Removed C:\Windows\ntfrs\jet\ntfrs.jdb  
15:15:03 [INFO] Removed C:\Windows\ntfrs\jet\sys\edb.chk  
15:15:03 [INFO] Removed C:\Windows\ntfrs\jet\temp\tmp.edb  
15:15:04 [INFO] Created system volume path  
15:15:04 [INFO] Configuring service DFSR  
15:15:04 [INFO] Configuring service DFSR to 128 returned 0  
15:15:04 [INFO] Configuring service NTFRS  
15:15:04 [INFO] Configuring service NTFRS to 128 returned 0  
15:15:04 [INFO] vDC Cloning: Winlogon UI Notification #14: Domain Controller cloning is at 40% completion...  
15:15:04 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
  • 開始使用現有的 NTDS 資料庫檔案在升級程序Start the promotion process using the existing NTDS database file

  • 連絡 RID 主機Contact the RID Master

注意

AD DS 未實際上安裝服務以下,這是舊版檢測登入The AD DS service is not actually installed here, this is legacy instrumentation in the log

15:15:04 [INFO] Installing the Directory Service  
15:15:04 [INFO] Calling NtdsInstall for root.fabrikam.com  
15:15:04 [INFO] Starting Active Directory Domain Services installation  
15:15:04 [INFO] Validating user supplied options  
15:15:04 [INFO] Determining a site in which to install  
15:15:04 [INFO] Examining an existing forest...  
15:15:04 [INFO] Starting a replication cycle between DC1.root.fabrikam.com and the RID operations master (2008r2-01.root.fabrikam.com), so that the new replica will be able to create users, groups, and computer objects...  
15:15:04 [INFO] Configuring the local computer to host Active Directory Domain Services  
15:15:04 [INFO] EVENTLOG (Warning): NTDS General / Service Control : 1539  
Active Directory Domain Services could not disable the software-based disk write cache on the following hard disk.  
Hard disk:  
c:  
Data might be lost during system failures.  
15:15:10 [INFO] EVENTLOG (Informational): NTDS General / Internal Processing : 2041  
Duplicate event log entries were suppressed.  
See the previous event log entry for details. An entry is considered a duplicate if  
the event code and all of its insertion parameters are identical. The time period for  
this run of duplicates is from the time of the previous event to the time of this event.  
Event Code:  
80000603  
Number of duplicate entries:   
2  
15:15:10 [INFO] EVENTLOG (Informational): NTDS General / Internal Configuration : 2121  
This Active Directory Domain Services server is disabling the Recycle Bin. Deleted objects may not be undeleted at this time.  
  • 變更現有的來源電腦資料庫中有叫用 IDChange the existing invocation ID that existed in the source computers database

  • 建立新物件 NTDS 設定的這個複製Create a new NTDS Settings object for this clone

  • 複製 AD 物件 delta 從合作夥伴網域控制站在Replicate in AD object delta from the partner domain controller

注意

即使所有物件複寫都列,這是 subsume 更新所需的只中繼資料。Even though all objects are listed as replicated, this is just metadata needed to subsume the updates. 複製 NTDS 資料庫中的所有變更的物件已存在,並不需要複製再試一次,就像使用 ifm 升級。All the unchanged objects in the cloned NTDS database already exist and do not require replication again, just like using IFM-based promotion.

15:15:10 [INFO] EVENTLOG (Informational): NTDS Replication / Replication : 1109  
The invocationID attribute for this directory server has been changed. The highest update sequence number at the time the backup was created is as follows:  
InvocationID attribute (old value):  
24e7b22f-4706-402d-9b4f-f2690f730b40  
InvocationID attribute (new value):  
f74cefb2-89c2-442c-b1ba-3234b0ed62f8  
Update sequence number:  
20520  
The invocationID is changed when a directory server is restored from backup media, is configured to host a writeable application directory partition, has been resumed after a virtual machine snapshot has been applied, after a virtual machine import operation, or after a live migration operation. Virtualized domain controllers should not be restored using virtual machine snapshots. The supported method to restore or rollback the content of an Active Directory Domain Services database is to restore a system state backup made with an Active Directory Domain Services-aware backup application.  
15:15:10 [INFO] EVENTLOG (Error): NTDS General / Internal Processing : 1168  
Internal error: An Active Directory Domain Services error has occurred.  
Additional Data  
Error value (decimal):  
2  
Error value (hexadecimal):  
2  
Internal ID:  
7011658  
15:15:11 [INFO] Creating the NTDS Settings object for this Active Directory Domain Controller on the remote AD DC DC1.root.fabrikam.com...  
15:15:11 [INFO] Replicating the schema directory partition  
15:15:11 [INFO] Replicated the schema container.  
15:15:12 [INFO] Active Directory Domain Services updated the schema cache.  
15:15:12 [INFO] Replicating the configuration directory partition  
15:15:12 [INFO] Replicating data CN=Configuration,DC=root,DC=fabrikam,DC=com: Received 2612 out of approximately 2612 objects and 94 out of approximately 94 distinguished name (DN) values...  
15:15:12 [INFO] Replicated the configuration container.  
15:15:13 [INFO] Replicating critical domain information...  
15:15:13 [INFO] Replicating data DC=root,DC=fabrikam,DC=com: Received 109 out of approximately 109 objects and 35 out of approximately 35 distinguished name (DN) values...  
15:15:13 [INFO] Replicated the critical objects in the domain container.  
  • 填入磁碟分割 GC 所需的任何缺少的更新Populate the GC partitions as needed with any missing updates

  • 完成升級的重大部分 AD DSComplete the critical AD DS portion of the promotion

15:15:13 [INFO] EVENTLOG (Informational): NTDS General / Global Catalog : 1110  
Promotion of this domain controller to a global catalog will be delayed for the following interval.  
Interval (minutes):  
5  
This delay is necessary so that the required directory partitions can be prepared before the global catalog is advertised. In the registry, you can specify the number of seconds that the directory system agent will wait before promoting the local domain controller to a global catalog. For more information about the Global Catalog Delay Advertisement registry value, see the Resource Kit Distributed Systems Guide.  
15:15:14 [INFO] EVENTLOG (Informational): NTDS General / Service Control : 1000  
Microsoft Active Directory Domain Services startup complete, version 6.2.8225.0   
15:15:15 [INFO] Creating new domain users, groups, and computer objects  
15:15:16 [INFO] Completing Active Directory Domain Services installation  
15:15:16 [INFO] NtdsInstall for root.fabrikam.com returned 0  
15:15:16 [INFO] DsRolepInstallDs returned 0  
15:15:16 [INFO] Installed Directory Service  
  • 完成 SYSVOL 輸入的的複寫Complete the inbound replication of SYSVOL
15:15:16 [INFO] vDC Cloning: Winlogon UI Notification #15: Domain Controller cloning is at 60% completion...  
15:15:16 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
15:15:18 [INFO] Completed system volume replication  
15:15:18 [INFO] vDC Cloning: Winlogon UI Notification #16: Domain Controller cloning is at 70% completion...  
15:15:18 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
15:15:18 [INFO] SetProductType to 2 [LanmanNT] returned 0  
15:15:18 [INFO] Set the product type  
15:15:18 [INFO] vDC Cloning: Winlogon UI Notification #17: Domain Controller cloning is at 71% completion...  
15:15:18 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
15:15:18 [INFO] vDC Cloning: Winlogon UI Notification #18: Domain Controller cloning is at 72% completion...  
15:15:18 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
15:15:18 [INFO] Set the system volume path for NETLOGON  
15:15:18 [INFO] vDC Cloning: Winlogon UI Notification #19: Domain Controller cloning is at 73% completion...  
15:15:18 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
15:15:18 [INFO] Replicating non critical information  
15:15:18 [INFO] User specified to not replicate non-critical data  
15:15:18 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
15:15:18 [INFO] vDC Cloning: Winlogon UI Notification #20: Domain Controller cloning is at 80% completion...  
15:15:18 [INFO] Stopped the DS  
15:15:18 [INFO] vDC Cloning: Set vDCCloningUpdate event.  
15:15:18 [INFO] vDC Cloning: Winlogon UI Notification #21: Domain Controller cloning is at 90% completion...  
15:15:18 [INFO] Configuring service NTDS  
15:15:18 [INFO] Configuring service NTDS to 16 returned 0  
  • 讓 client DNS 登記Enable client DNS registration
15:15:18 [INFO] vDC Cloning: Set DisableDynamicUpdate reg value to 0 to enable dynamic update records registration.  
15:15:18 [INFO] vDC Cloning: Set UseDynamicDns reg value to 1 to enable dynamic update records registration.  
15:15:18 [INFO] vDC Cloning: Set RegistrationEnabled reg value to 1 to enable dynamic update records registration.  
  • 執行指定 DefaultDCCloneAllowList.xml SYSPREP 模組的項目。Run the SYSPREP modules specified by the DefaultDCCloneAllowList.xml element.
15:15:18 [INFO] vDC Cloning: Running sysprep providers.  
15:15:32 [INFO] vDC Cloning: Completed running sysprep providers.  
  • 複製升級已完成Cloning promotion is complete

  • 移除 DSRM 開機旗標讓伺服器開機通常會在下一次Remove the DSRM boot flag so the server boots normally next time

  • 重新命名 dccloneconfig.xml,讓它不再次朗讀下一個開機。Rename the dccloneconfig.xml so that it is not read again at next bootup

  • 電腦重新開機Restart the computer

15:15:32 [INFO] The attempted domain controller operation has completed  
15:15:32 [INFO] Updating service status to 4  
15:15:32 [INFO] DsRolepSetOperationDone returned 0  
15:15:32 [INFO] vDC Cloning: Set vDCCloningComplete event.  
15:15:32 [INFO] vDC Cloneing: Clearing Boot into DSRM flag succeeded.  
15:15:32 [INFO] vDC Cloning: Winlogon UI Notification #22: Cloning Domain Controller succeeded. Now rebooting...  
15:15:33 [INFO] vDC Cloning: Renamed vDC clone configuration file.  
15:15:33 [INFO] vDC Cloning: The old name is: C:\Windows\NTDS\DCCloneConfig.xml  
15:15:33 [INFO] vDC Cloning: The new name is: C:\Windows\NTDS\DCCloneConfig.20120207-151533.xml  
15:15:34 [INFO] vDC Cloning: Release Ipv4 on interface 'Wired Ethernet Connection 2', result=0.  
15:15:34 [INFO] vDC Cloning: Release Ipv6 on interface 'Wired Ethernet Connection 2', result=0.  
15:15:34 [INFO] Rebooting machine  
Active Directory Web 服務事件登入Active Directory Web Services Event Log

複製發生,NTDS 時。DIT 資料庫通常是長期離線。While cloning is occurring, the NTDS.DIT database is often offline for extended periods. ADWS 服務此登至少一個事件。The ADWS service logs at least one event for this. 複製完成之後,ADWS 服務開始,筆記,但尚未有效的電腦憑證但 (可能或可能不會根據您的環境部署 Microsoft PKI 自動註冊使用或不),再開始新的網域控制站的執行個體。After cloning is complete, the ADWS service starts, notes that there is not yet a valid computer certificate yet (there may or may not be, depending on your environment deploying a Microsoft PKI with auto-enrollment or not) and then starts the instance for the new domain controller.

事件編號Event ID 來源Source 訊息Message
12021202 ADWS 執行個體事件ADWS Instance Events 這台電腦現在裝載指定的 directory 執行個體,但 Active Directory 網頁的服務可能會不服務的方法。This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web 服務定期將會重試這項操作。Active Directory Web Services will retry this operation periodically.

Directory 執行個體: NTDSDirectory instance: NTDS

Directory 執行個體 LDAP 連接埠: 389Directory instance LDAP port: 389

Directory 執行個體 SSL 連接埠: 636Directory instance SSL port: 636
10001000 ADWS 執行個體事件ADWS Instance Events 開始 active Directory Web 服務Active Directory Web Services is starting
10081008 ADWS 執行個體事件ADWS Instance Events Active Directory Web 服務已成功減少其安全性特殊權限Active Directory Web Services has successfully reduced its security privileges
11001100 ADWS 執行個體事件ADWS Instance Events 中指定的值無誤已載入的設定檔的 Active Directory Web 服務一節。The values specified in the section of the configuration file for Active Directory Web Services have been loaded without errors.
14001400 ADWS 執行個體事件ADWS Instance Events ADWS 憑證事件 「 Active Directory Web 服務找不到伺服器的憑證,以指定的憑證的名稱。ADWS Certificate Events"Active Directory Web Services could not find a server certificate with the specified certificate name. 憑證,才能使用 SSL 日 TLS 連接。A certificate is required to use SSL/TLS connections. 若要使用 SSL 日 TLS 連接,確認有效的伺服器驗證憑證的受信任憑證授權單位已安裝在電腦上。To use SSL/TLS connections, verify that a valid server authentication certificate from a trusted Certification Authority (CA) is installed on the machine.

憑證的名稱︰Certificate name:
11001100 ADWS 執行個體事件ADWS Instance Events 中指定的值無誤已載入的設定檔的 Active Directory Web 服務一節。The values specified in the section of the configuration file for Active Directory Web Services have been loaded without errors.
12001200 ADWS 執行個體事件ADWS Instance Events Active Directory Web 服務為現在提供服務指定的 directory 執行個體。Active Directory Web Services is now servicing the specified directory instance.

Directory 執行個體: NTDSDirectory instance: NTDS

Directory 執行個體 LDAP 連接埠: 389Directory instance LDAP port: 389

Directory 執行個體 SSL 連接埠: 636Directory instance SSL port: 636
DNS 伺服器事件登入DNS Server Event Log

DNS 服務會簡短預期的中斷時遇到複製發生,請在 DNS 服務仍在執行時離線 AD DS 資料庫。The DNS service will experience brief expected outages while cloning occurs, as the DNS service is still running while the AD DS database is offline. 這是使用 Active Directory 整合 DNS,但不是是否使用標準主要或次要 DNS。This occurs if using Active Directory Integrated DNS, but not if using Standard Primary or Secondary DNS. 這些錯誤登入多個時間。These errors log multiple times. 複製完成後,請 DNS 會上恢復正常。After cloning completes, DNS comes back online normally.

事件編號Event ID 來源Source 訊息Message
40134013 DNS 伺服器服務DNS-Server-Service DNS 伺服器正在等待通知的 directory 初始同步已經完成的 Active Directory Domain Services (AD DS)。The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. 完成初始同步是因為 DNS 重要的資料可能尚未會複寫加入網域控制站的 DNS 伺服器服務才能開始。The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. 如果事件 AD DS 事件木頭中的指示 DNS 名稱解析發生問題,請考慮將這個網域中的其他 DNS 伺服器的 IP 位址新增到 DNS 伺服器清單中的 [這部電腦網際網路通訊協定屬性。If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. 這個事件將會登入之前 AD DS 發出初始同步已成功完成 10 分鐘。This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.
40154015 DNS 伺服器服務DNS-Server-Service DNS 伺服器發生嚴重錯誤的 Active Directory。The DNS server has encountered a critical error from the Active Directory. 檢查 Active Directory 正常運作。Check that the Active Directory is functioning properly. (這可能會是空白) 的延伸的錯誤偵錯資訊 」 」 」。The extended error debug information (which may be empty) is """". 事件資料會包含錯誤。The event data contains the error.
40004000 DNS 伺服器服務DNS-Server-Service 打開 Active Directory 無法 DNS 伺服器。The DNS server was unable to open Active Directory. 此 DNS 伺服器設定為取得並使用此區域 directory 資訊,無法載入而它的區域。This DNS server is configured to obtain and use information from the directory for this zone and is unable to load the zone without it. 檢查 Active Directory 正常運作,並重新載入的區域。Check that the Active Directory is functioning properly and reload the zone. 事件資料是錯誤碼。The event data is the error code.
40134013 DNS 伺服器服務DNS-Server-Service DNS 伺服器正在等待通知的 directory 初始同步已經完成的 Active Directory Domain Services (AD DS)。The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. 完成初始同步是因為 DNS 重要的資料可能尚未會複寫加入網域控制站的 DNS 伺服器服務才能開始。The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. 如果事件 AD DS 事件木頭中的指示 DNS 名稱解析發生問題,請考慮將這個網域中的其他 DNS 伺服器的 IP 位址新增到 DNS 伺服器清單中的 [這部電腦網際網路通訊協定屬性。If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. 這個事件將會登入之前 AD DS 發出初始同步已成功完成 10 分鐘。This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.
22 DNS 伺服器服務DNS-Server-Service 開始 DNS 伺服器。The DNS server has started.
44 DNS 伺服器服務DNS-Server-Service 完成區域的背景載入 DNS 伺服器。The DNS server has finished the background loading of zones. 允許的他們個人的區域的設定,現在已有 DNS 更新及區域轉送,所有區域。All zones are now available for DNS updates and zone transfers, as allowed by their individual zone configuration.
檔案複製服務事件登入File Replication Service Event Log

複製檔案服務同步處理非系統授權的合作夥伴期間複製。The File Replication Service synchronizes non-authoritatively from a partner during cloning. 複製這樣的優勢刪除 NTFRS 資料庫檔案並保持不變,作為預先植資料 SYSVOL 到。Cloning accomplishes this by deleting the NTFRS database files and leaving the contents of SYSVOL untouched, for use as pre-seeded data. 若要同步的兩個嘗試會如預期般。The two attempts to synchronize are expected.

事件編號Event ID 來源Source 訊息Message
1356213562 NtFrsNtFrs 以下是摘要的警告與檔案複寫服務雖然輪詢 FRS 複本的網域控制站 DC2.root.fabrikam.com 設定設定資訊時發生錯誤。Following is the summary of warnings and errors encountered by File Replication Service while polling the Domain Controller DC2.root.fabrikam.com for FRS replica set configuration information.

無法為網域控制站連結。Could not bind to a Domain Controller. 將會再試一次在下一個輪詢循環Will try again at next polling cycle
1350213502 NtFrsNtFrs 停止檔案複寫服務。The File Replication Service is stopping.
1356513565 NtFrsNtFrs 檔案複寫服務初始化從另一部網域控制站的資料與系統磁碟區。File Replication Service is initializing the system volume with data from another domain controller. 此程序完成之前電腦 DC2 無法加入網域控制站。Computer DC2 cannot become a domain controller until this process is complete. 然後將會為 SYSVOL 共用系統磁碟區。The system volume will then be shared as SYSVOL.

若要檢查 SYSVOL 共用,請在命令提示字元中,輸入To check for the SYSVOL share, at the command prompt, type:

共用網路net share

在檔案複寫服務完成初始設定程序,會出現 SYSVOL 共用。When File Replication Service completes the initialization process, the SYSVOL share will appear.

系統磁碟區的初始設定可能需要一些時間。The initialization of the system volume can take some time. 是的數據量中的系統磁碟區,可供使用的其他網域控制站,並網域控制站複寫間隔而定。The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers.
1350113501 NtFrsNtFrs 開始檔案複寫服務The File Replication Service is starting
1350213502 NtFrsNtFrs 停止檔案複寫服務。The File Replication Service is stopping.
1350313503 NtFrsNtFrs 檔案複製服務已停止。The File Replication Service has stopped.
1356513565 NtFrsNtFrs 檔案複寫服務初始化從另一部網域控制站的資料與系統磁碟區。File Replication Service is initializing the system volume with data from another domain controller. 此程序完成之前電腦 DC2 無法加入網域控制站。Computer DC2 cannot become a domain controller until this process is complete. 然後將會為 SYSVOL 共用系統磁碟區。The system volume will then be shared as SYSVOL.

若要檢查 SYSVOL 共用,請在命令提示字元中,輸入To check for the SYSVOL share, at the command prompt, type:

共用網路net share

在檔案複寫服務完成初始設定程序,會出現 SYSVOL 共用。When File Replication Service completes the initialization process, the SYSVOL share will appear.

系統磁碟區的初始設定可能需要一些時間。The initialization of the system volume can take some time. 是的數據量中的系統磁碟區,可供使用的其他網域控制站,並網域控制站複寫間隔而定。The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers.
1350113501 NtFrsNtFrs 開始工作檔案複寫服務。The File Replication Service is starting.
1355313553 NtFrsNtFrs 檔案複寫服務順利加入這台電腦複本下列設定:The File Replication Service successfully added this computer to the following replica set:

「 網域系統磁碟區 (SYSVOL 共用) 」"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"

這個事件和相關的資訊如下所示:Information related to this event is shown below:

電腦 DNS 名稱Computer DNS name is

複本設定成員名稱Replica set member name is

複本設定根路徑Replica set root path is

臨時 directory 路徑複本Replica staging directory path is

已正常運作的路徑複本Replica working directory path is
1352013520 NtFrsNtFrs 將檔案複製服務移動既有的檔案到* \NtFrs_PreExisting___See_EventLog。The File Replication Service moved the preexisting files in to *\NtFrs_PreExisting___See_EventLog.

複製檔案服務可能 delete 中的檔案* 隨時 \NtFrs_PreExisting___See_EventLog。The File Replication Service may delete the files in *\NtFrs_PreExisting___See_EventLog at any time. 檔案可以複製全新儲存刪除從* \NtFrs_PreExisting___See_EventLog。Files can be saved from deletion by copying them out of *\NtFrs_PreExisting___See_EventLog. 如果已經有一些其他複製合作夥伴這些檔案將檔案複製到 c:\windows\sysvol\domain 可能導致衝突名稱。Copying the files into c:\windows\sysvol\domain may lead to name conflicts if the files already exist on some other replicating partner.

有時候,檔案複寫服務可能複製檔案的* \NtFrs_PreExisting___See_EventLog 到 而不是複製檔案的其他複製協力廠商。In some cases, the File Replication Service may copy a file from *\NtFrs_PreExisting___See_EventLog into instead of replicating the file from some other replicating partner.

空間可以隨時復原刪除中的檔案的* \NtFrs_PreExisting___See_EventLog。 」Space can be recovered at any time by deleting the files in *\NtFrs_PreExisting___See_EventLog."
1350813508 NtFrsNtFrs 他檔案複寫服務時發生問題,讓從複寫* \\ 使用he File Replication Service is having trouble enabling replication from *\\ to for using the

DNS name \\.DNS name \\. 將會持續 FRS 重試。FRS will keep retrying.

以下是一些您將會看到這個警告的原因。Following are some of the reasons you would see this warning.

[1] FRS 無法正確地將 DNS 名稱解析* \\ 來自此電腦。[1] FRS cannot correctly resolve the DNS name *\\ from this computer.

[不執行 FRS 2] * \\ [2] FRS is not running on *\\.

[所有的網域控制站尚未複寫 Active Directory Domain Services 進行這個複本中的 3] 拓撲資訊。[3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.

連接,每修正這個問題之後,您會看到其他事件登入訊息,指出已建立的連接後,就會出現這個事件登入的訊息。This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
1350913509 NtFrsNtFrs 檔案複寫服務已支援複寫從* \\ 重複重試後。The File Replication Service has enabled replication from *\\ to for after repeated retries.
1351613516 NtFrsNtFrs 檔案複寫服務不讓電腦* 的網域控制站變得。The File Replication Service is no longer preventing the computer * from becoming a domain controller. 已成功初始化系統磁碟區,已經通知 Netlogon 服務,系統磁碟區現在已經準備好 SYSVOL 共用。The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL.

輸入 「 共用網路] 來檢查是否有 SYSVOL 分享。 」Type "net share" to check for the SYSVOL share."
DFS 複寫事件登入DFS Replication Event Log

DFSR 服務同步處理非系統授權的合作夥伴期間複製。The DFSR services synchronizes non-authoritatively from a partner during cloning. 複製這樣的優勢刪除 DFSR 資料庫檔案並保持不變,作為預先植資料 SYSVOL 到。Cloning accomplishes this by deleting the DFSR database files and leaving the contents of SYSVOL untouched, for use as pre-seeded data. 若要同步的兩個嘗試會如預期般。The two attempts to synchronize are expected.

事件編號Event ID 來源Source 訊息Message
10041004 DFSRDFSR 開始 DFS 複寫服務。The DFS Replication service has started.
13141314 DFSRDFSR DFS 複寫服務成功設定的偵錯登入的檔案。The DFS Replication service successfully configured the debug log files.

其他資訊:Additional Information:

偵錯登入的檔案路徑: C:\Windows\debugDebug Log File Path: C:\Windows\debug
61026102 DFSRDFSR DFS 複寫服務已成功已經登記完畢 WMI 提供者The DFS Replication service has successfully registered the WMI provider
12061206 DFSRDFSR DFS 複寫服務順利連絡網域控制站 DC2.corp.contoso.com 存取設定的資訊。The DFS Replication service successfully contacted domain controller DC2.corp.contoso.com to access configuration information.
12101210 DFSRDFSR 成功設定傳入複寫要求 RPC 其實 DFS 複寫服務。The DFS Replication service successfully set up an RPC listener for incoming replication requests.

其他資訊:Additional Information:

連接埠: 0 」Port: 0"
46144614 DFSRDFSR 在本機路徑 C:\Windows\SYSVOL\domain 初始化 SYSVOL DFS 複寫服務,並執行初始複寫正在等待。The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. 複寫的資料夾會維持在初始同步狀態複寫其合作夥伴使用。The replicated folder will remain in the initial synchronization state until it has replicated with its partner. 如果在升級為網域控制站伺服器,網域控制站不會通知和這個問題之前解析為網域控制站運作。If the server was in the process of being promoted to a domain controller, the domain controller will not advertise and function as a domain controller until this issue is resolved. 如果指定的合作夥伴也是在初始同步狀態下,或共用違規此伺服器上同步處理合作夥伴,這可能會發生。This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the synchronization partner. 如果發生 SYSVOL 移轉期間這個事件 DFS 複寫的檔案複製服務 (FRS),請變更不會複寫出辨識這個問題之前。If this event occurred during the migration of SYSVOL from File Replication Service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. 這會造成 SYSVOL 資料夾變成與其他網域控制站不同步此伺服器上。This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.

其他資訊:Additional Information:

複製的資料夾的名稱︰ SYSVOL 分享Replicated Folder Name: SYSVOL Share

複製的資料夾 ID:Replicated Folder ID:

複寫群組的名稱︰ 網域系統磁碟區Replication Group Name: Domain System Volume

複寫群組 ID:Replication Group ID:

會員 ID:Member ID:

唯讀模式: 0Read-Only: 0
46044604 DFSRDFSR DFS 複寫服務順利初始化在本機路徑 C:\Windows\SYSVOL\domain SYSVOL 複寫資料夾。The DFS Replication service successfully initialized the SYSVOL replicated folder at local path C:\Windows\SYSVOL\domain. 這個成員已完成合作夥伴 dc1.corp.contoso.com SYSVOL 的初始同步的處理。This member has completed initial synchronization of SYSVOL with partner dc1.corp.contoso.com. 若要檢查有任何 SYSVOL 共用,請打開在命令提示字元視窗,然後輸入 「 」 網路共用 」 」。To check for the presence of the SYSVOL share, open a command prompt window and then type ""net share"".

其他資訊:Additional Information:

複製的資料夾的名稱︰ SYSVOL 分享Replicated Folder Name: SYSVOL Share

複製的資料夾 ID:Replicated Folder ID:

複寫群組的名稱︰ 網域系統磁碟區Replication Group Name: Domain System Volume

複寫群組 ID:Replication Group ID:

會員 ID:Member ID:

同步合作夥伴:Sync partner:

疑難排解模擬的網域控制站安全還原Troubleshooting virtualized domain controller safe restore

疑難排解工具Tools for Troubleshooting

登入選項Logging Options

建登的最重要的網域控制站安全快照還原問題的疑難排解工具。The built-in logs are the most important tool for troubleshooting issues with domain controller safe snapshot restore. 所有的這些登的功能和最大的詳細資訊,預設設定。All of these logs are enabled and configured for maximum verbosity, by default.

操作Operation 登入Log
快照建立Snapshot creation 事件 viewer\Applications 和服務 logs\Microsoft\Windows\Hyper-V-背景工作- Event viewer\Applications and services logs\Microsoft\Windows\Hyper-V-Worker
快照還原Snapshot restore 事件 viewer\Applications 和服務 logs\Directory 服務- Event viewer\Applications and services logs\Directory Service
事件 viewer\Windows logs\System- Event viewer\Windows logs\System
事件 viewer\Windows logs\Application- Event viewer\Windows logs\Application
事件 viewer\Applications 和服務 logs\File 複寫服務- Event viewer\Applications and services logs\File Replication Service
事件 viewer\Applications 和服務 logs\DFS 複寫- Event viewer\Applications and services logs\DFS Replication
事件 viewer\Applications 和服務 logs\DNS- Event viewer\Applications and services logs\DNS
事件 viewer\Applications 和服務 logs\Microsoft\Windows\Hyper-V-背景工作- Event viewer\Applications and services logs\Microsoft\Windows\Hyper-V-Worker

工具和疑難排解網域控制站設定的命令Tools and Commands for Troubleshooting Domain Controller Configuration

若要登不解釋問題的疑難排解,使用下列工具做為起點:To troubleshoot issues not explained by the logs, use the following tools as a starting point:

  • Dcdiag.exeDcdiag.exe

  • Repadmin.exeRepadmin.exe

  • 網路監視器 3.4Network Monitor 3.4

一般的網域控制站安全還原進行疑難排解的方法General Methodology for Troubleshooting Domain Controller Safe Restore

  1. 安全快照還原預期,但有問題嗎?Is the safe snapshot restore expected, but having issues?

    1. 檢查服務 Directory 事件登入Examine the Directory Services event log

      1. 有快照還原錯誤嗎?Are there snapshot restore errors?

      2. 有 AD 複寫錯誤嗎?Are there AD replication errors?

    2. 檢查 [系統事件登入Examine the System event log

      1. 有通訊錯誤嗎?Are there communication errors?

      2. 有 AD 錯誤嗎?Are there AD errors?

  2. 是安全的快照還原未預期嗎?Is the safe snapshot restore unexpected?

    1. 檢查以判斷人員或造成回復 hypervisor 稽核登Examine the hypervisor audit logs to determine who or what caused a rollback

    2. 連絡 hypervisor 的所有系統管理員,並詢問它們至於人員復原 VM 不通知Contact all administrators of the hypervisor and interrogate them as to who rolled back the VM without notification

  3. 伺服器實作 USN 復原保護並不安全還原嗎?Is the server implementing USN rollback protection and not safely restoring?

    1. 檢查服務 Directory 事件登入不支援 hypervisor 或整合服務Examine the Directory Services event log for an unsupported hypervisor or integration services

    2. 檢查作業系統,並驗證執行 Windows Server 2012 嗎?Examine the operating system and validate running Windows Server 2012?

特定的問題進行疑難排解Troubleshooting Specific Problems

事件Events

所有擬化檔案網域控制站安全快照還原事件寫入還原的網域控制站 VM Directory 服務事件登入。All virtualized domain controller safe snapshot restore events write to the Directory Services event log of the restored domain controller VM. 應用程式,系統、 檔案複寫服務及 DFS 複寫事件登也可能包含失敗還原疑難排解有用的資訊。The Application, System, File Replication Service, and DFS Replication event logs may also contain useful troubleshooting information for failed restores.

以下是 Windows Server 2012 安全還原特定的事件 Directory 服務事件登入。Below are the Windows Server 2012 safe restore-specific events in the Directory Services event log.

事件編號Event ID 21702170
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 警告Warning
訊息Message 偵測到代 ID 變更。A Generation ID change has been detected.

代來電顯示快取中 DS (舊值): %1Generation ID cached in DS (old value):%1

代 ID 目前在 VM (新值): %2Generation ID currently in VM (new value):%2

一樣快照的應用程式、 一樣匯入操作後或即時移轉作業之後,就會發生代 ID 變更。The Generation ID change occurs after the application of a virtual machine snapshot, after a virtual machine import operation or after a live migration operation. 將會建立新的叫用 ID 復原網域控制站。 will create a new invocation ID to recover the domain controller. 應還原模擬的網域控制站使用一樣的快照。Virtualized domain controllers should not be restored using virtual machine snapshots. 支援的方法來還原或復原 content 的 Active Directory Domain Services 資料庫是還原所做的 Active Directory Domain Services 注意備份應用程式的系統狀態備份。The supported method to restore or rollback the content of an Active Directory Domain Services database is to restore a system state backup made with an Active Directory Domain Services aware backup application.
筆記與解析度Notes and resolution 如果需要快照,是成功事件。This is a success event if the snapshot was expected. 否則,請檢查背景 V 於工作事件登入,或連絡 hypervisor 系統管理員。If not, examine the Hyper-V-Worker event log or contact the hypervisor administrator.
事件編號Event ID 21742174
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message DC 是 virtual 網域控制站複製都還原 virtual 網域控制站開發進程的快照。The DC is neither a virtual domain controller clone nor a restored virtual domain controller snapshot.
筆記與解析度Notes and resolution 實體網域控制站或模擬的網域控制站的快照不會還原的開始時的預期的事件Expected event when starting physical domain controllers or virtualized domain controllers not restored from snapshot
事件編號Event ID 21812181
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 交易中止因為一樣會還原到先前的狀態。The transaction was aborted due to the virtual machine being reverted to a previous state. 這是在一樣快照的應用程式、 一樣匯入進行操作之後,或之後即時移轉作業。This occurs after the application of a virtual machine snapshot, after a virtual machine import operation, or after a live migration operation.
筆記與解析度Notes and resolution 還原快照時預期般運作。Expected when restoring a snapshot. 交易追蹤 VM 代 ID 變更Transactions track the VM Generation ID changing
事件編號Event ID 21852185
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 停止 FRS 或 DFSR 所用服務複寫 SYSVOL 資料夾。 stopped the FRS or DFSR service used to replicate the SYSVOL folder.

服務的名稱︰ %1Service name:%1

Active Directory 偵測到的裝載的網域控制站一樣還原到先前的狀態。Active Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. 必須初始化未經授權還原 SYSVOL 複本本機上。 must initialize a non-authoritative restore on the local SYSVOL replica. 這會的停止 FRS 或 DFSR 服務使用複寫 SYSVOL 資料夾並開始它值觸發還原至適當登錄與執行。This is performed by stopping the FRS or DFSR service used to replicate the SYSVOL folder and starting it with the appropriate registry keys and values to trigger the restore. 重新開始 FRS 或 DFSR 服務時事件 2187年將會登入。Event 2187 will be logged when FRS or DFSR service is restarted.
筆記與解析度Notes and resolution 還原快照時預期般運作。Expected when restoring a snapshot. 在這個網域控制站所有 SYSVOL 資料會都取代合作夥伴 DC 的複本。All SYSVOL data on this domain controller is replaced with a partner DC's copy.
事件編號Event ID 21862186
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 若要停止 FRS 或 DFSR 所用服務複寫 SYSVOL 資料夾失敗。 failed to stop the FRS or DFSR service used to replicate the SYSVOL folder.

服務的名稱︰ %1Service name:%1

錯誤碼: %2Error code:%2

錯誤訊息: %3Error message:%3

Active Directory 偵測到的裝載的網域控制站一樣還原到先前的狀態。Active Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. 必須初始化未經授權還原 SYSVOL 複本本機上。 must initialize a non-authoritative restore on the local SYSVOL replica. 這是停止 FRS 或 DFSR 複寫服務使用複寫 SYSVOL 資料夾,然後將它開始值觸發還原至適當登錄與。This is done by stopping the FRS or DFSR replication service used to replicate the SYSVOL folder and then starting it with the appropriate registry keys and values to trigger the restore. 無法停止目前執行的服務,且無法完成未經授權還原。 failed to stop the current running service and cannot complete the non-authoritative restore. 請手動執行未經授權還原。Please perform a non-authoritative restore manually.
筆記與解析度Notes and resolution 檢查 [系統、 FRS 及 DFSR 事件登的其他相關資訊。Examine the System, FRS and DFSR event logs for further information.
事件編號Event ID 21872187
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 開始使用複寫 SYSVOL 資料夾 FRS 或 DFSR 服務。 started the FRS or DFSR service used to replicate the SYSVOL folder.

服務的名稱︰ %1Service name:%1

Active Directory 偵測到的裝載的網域控制站一樣還原到先前的狀態。Active Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. 需要初始化未經授權還原 SYSVOL 複本本機上。 needed to initialize a non-authoritative restore on the local SYSVOL replica. 這是的停止 FRS 或 DFSR 服務使用複寫 SYSVOL 資料夾並開始它值觸發還原至適當登錄與。This was done by stopping the FRS or DFSR service used to replicate the SYSVOL folder and starting it with the appropriate registry keys and values to trigger the restore.
筆記與解析度Notes and resolution 還原快照時預期般運作。Expected when restoring a snapshot. 在這個網域控制站所有 SYSVOL 資料會都取代合作夥伴 DC 的複本。All SYSVOL data on this domain controller is replaced with a partner DC's copy.
事件編號Event ID 21882188
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 若要開始使用複寫 SYSVOL 資料夾 FRS 或 DFSR 服務失敗。 failed to start the FRS or DFSR service used to replicate the SYSVOL folder.

服務的名稱︰ %1Service name:%1

錯誤碼: %2Error code:%2

錯誤訊息: %3Error message:%3

Active Directory 偵測到的裝載的網域控制站一樣還原到先前的狀態。Active Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. 需要初始化未經授權還原 SYSVOL 複本本機上。 needs to initialize a non-authoritative restore on the local SYSVOL replica. 這是的停止複寫 SYSVOL 用於 FRS 或 DFSR 服務或開頭適當的登錄和觸發還原值。This is done by stopping the FRS or DFSR service used to replicate the SYSVOL and starting it with appropriate registry keys and values to trigger the restore. 開始 FRS 或 DFSR 所用服務將 SYSVOL 資料夾複寫失敗,無法完成未經授權還原。 failed to start the FRS or DFSR service used to replicate the SYSVOL folder and cannot complete the non-authoritative restore. 請手動執行未經授權還原並重新開機服務。Please perform a non-authoritative restore manually and restart the service.
筆記與解析度Notes and resolution 檢查 [系統、 FRS 及 DFSR 事件登的其他相關資訊。Examine the System, FRS and DFSR event logs for further information.
事件編號Event ID 21892189
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 設定 SYSVOL 複本初始化期間未經授權還原登錄下列值: set the following registry values to initialize SYSVOL replica during a non-authoritative restore:

登錄鍵: %1Registry Key:%1

登錄值: %2Registry Value: %2

登錄數值資料: %3Registry Value data: %3

Active Directory 偵測到的裝載的網域控制站一樣還原到先前的狀態。Active Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. 需要初始化未經授權還原 SYSVOL 複本本機上。 needs to initialize a non-authoritative restore on the local SYSVOL replica. 這是的停止 FRS 或 DFSR 服務使用複寫 SYSVOL 資料夾並開始它值觸發還原至適當登錄與。This is done by stopping the FRS or DFSR service used to replicate the SYSVOL folder and starting it with the appropriate registry keys and values to trigger the restore.
筆記與解析度Notes and resolution 還原快照時預期般運作。Expected when restoring a snapshot. 在這個網域控制站所有 SYSVOL 資料會都取代合作夥伴 DC 的複本。All SYSVOL data on this domain controller is replaced with a partner DC's copy.
事件編號Event ID 21902190
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 無法設定 SYSVOL 複本初始化期間未經授權還原登錄下列值: failed to set the following registry values to initialize the SYSVOL replica during a non-authoritative restore:

登錄鍵: %1Registry Key:%1

登錄值: %2Registry Value: %2

登錄數值資料: %3Registry Value data: %3

錯誤碼: %4Error code:%4

錯誤訊息: %5Error message:%5

Active Directory 偵測到的裝載網域控制站一樣還原到先前的狀態。Active Directory detected that the virtual machine that hosts the domain controller role was reverted to a previous state. 需要初始化未經授權還原 SYSVOL 複本本機上。 needs to initialize a non-authoritative restore on the local SYSVOL replica. 這是的停止 FRS 或 DFSR 服務使用複寫 SYSVOL 資料夾並開始它值觸發還原至適當登錄與。This is done by stopping the FRS or DFSR service used to replicate the SYSVOL folder and starting it with the appropriate registry keys and values to trigger the restore. 設定上述登錄值失敗,無法完成未經授權還原。 failed to set the above registry values and cannot complete the non-authoritative restore. 請手動執行未經授權還原。Please perform a non-authoritative restore manually.
筆記與解析度Notes and resolution 檢查應用程式和系統事件登。Examine Application and System event logs. 調查第三方應用程式可能會封鎖登錄更新。Investigate third party applications that may be blocking registry updates.
事件編號Event ID 22002200
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message Active Directory 偵測到的裝載的網域控制站一樣還原到先前的狀態。Active Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. 將目前的網域控制站初始化複寫。 initializes replication to bring the domain controller current. 完成複寫事件 2201年將會登入。Event 2201 will be logged when the replication is finished.
筆記與解析度Notes and resolution 還原快照時預期般運作。Expected when restoring a snapshot. 標記輸入 AD 複寫的開頭。Marks the beginning of inbound AD replication.
事件編號Event ID 22012201
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message Active Directory 偵測到的裝載的網域控制站一樣還原到先前的狀態。Active Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. 已完成複寫將目前的網域控制站。 has finished replication to bring the domain controller current.
筆記與解析度Notes and resolution 還原快照時預期般運作。Expected when restoring a snapshot. 標示輸入 AD 複寫的結尾。Marks the end of inbound AD replication.
事件編號Event ID 22022202
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message Active Directory 偵測到的裝載的網域控制站一樣還原到先前的狀態。Active Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. 將最新的網域控制站複寫失敗。 failed replication to bring the domain controller up-to-date. 下一步定期複寫之後,將會更新的網域控制站。The domain controller will be updated after next periodic replication.
筆記與解析度Notes and resolution 檢查 Directory 服務和系統事件登。Examine the Directory Services and System event logs. 使用 repadmin.exe 嘗試強迫複寫,並記下的任何失敗。Use repadmin.exe to attempt forcing replication and note any failures.
事件編號Event ID 22042204
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 偵測到一樣代收到的變更 has detected a change of virtual machine generation ID. 變更表示 virtual 網域控制站的已經還原到先前的狀態。The change means that the virtual domain controller has been reverted to a previous state. 將會執行下列操作保護還原網域控制站分歧可能的資料免於和保護安全性主體的 Sid 重複建立: will perform the following operations to protect the reverted domain controller against possible data divergence and to protect creation of security principals with duplicate SIDs:

建立新的叫用 IDCreate a new invocation ID

使目前 RID 集區Invalidate current RID pool

將會在下一步輸入複寫驗證故障的擁有權。Ownership of the FSMO roles will be validated at next inbound replication. 這項視窗期間如果網域控制站保留 FSMO 的角色,該角色將無法使用。During this window if the domain controller held a FSMO role, that role will be unavailable.

開始 SYSVOL 複寫服務還原操作。Start SYSVOL replication service restore operation.

[開始]︰ 複寫將還原網域控制站帶到最新狀態。Start replication to bring the reverted domain controller to the most current state.

要求 RID 新集區。Request a new RID pool.
筆記與解析度Notes and resolution 還原快照時預期般運作。Expected when restoring a snapshot. 這解釋所有各種重設安全還原程序的一部分會發生的作業。This explains all the various reset operations that will occur as part of the safe restore process.
事件編號Event ID 22052205
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 失效目前 RID 集區之後 virtual 網域控制站還原到先前的狀態。 invalidated current RID pool after virtual domain controller was reverted to previous state.
筆記與解析度Notes and resolution 還原快照時預期般運作。Expected when restoring a snapshot. 必須網域控制站有 travelled 的時間,他們可能有已經發出損壞本機 RID 集區。The local RID pool must be destroyed as the domain controller has time travelled and they may have already been issued.
事件編號Event ID 22062206
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤ERROR
訊息Message 無法 virtual 網域控制站還原到先前的狀態後失效目前 RID 集區。 failed to invalidate current RID pool after virtual domain controller was reverted to previous state.

其他資料:Additional data:

錯誤碼: %1Error code: %1

錯誤值: %2Error value: %2
筆記與解析度Notes and resolution 檢查 Directory 服務和系統事件登。Examine the Directory Services and System event logs. 確認移除主要 online 可以達到從此使用 Dcdiag.exe /test:ridmanager 伺服器Validate that the RID Master is online can be reached from this server using Dcdiag.exe /test:ridmanager
事件編號Event ID 22072207
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤ERROR
訊息Message 無法還原之後 virtual 網域控制站還原到先前的狀態。 failed to restore after virtual domain controller was reverted to previous state. 已要求到 DSRM 重新開機。A reboot into DSRM was requested. 請檢查前的事件的詳細資訊。Please check previous events for more information.
筆記與解析度Notes and resolution 檢查 Directory 服務和系統事件登。Examine the Directory Services and System event logs.
事件編號Event ID 22082208
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 資訊Informational
訊息Message 刪除 DFSR 資料庫未經授權還原程序期間初始化 SYSVOL 複本。 deleted DFSR databases to initialize SYSVOL replica during a non-authoritative restore.
筆記與解析度Notes and resolution 還原快照時預期般運作。Expected when restoring a snapshot. 這可以確保 DFSR 非系統授權的合作夥伴俠同步 SYSVOL。This guarantees DFSR non-authoritatively synchronizes SYSVOL from a partner DC. 請注意,任何其他 DFSR 複寫資料夾 SYSVOL 所在的磁碟區上也非系統授權方式將會同步 (網域控制站不建議使用主機自訂 DFSR 設定 SYSVOL 所在的磁碟區)。Note that any other DFSR Replicated Folders on the same volume as SYSVOL will also non-authoritatively sync (domain controllers are not recommended to host custom DFSR sets on the same volume as SYSVOL).
事件編號Event ID 22092209
來源Source Microsoft-Windows-ActiveDirectory_DomainServiceMicrosoft-Windows-ActiveDirectory_DomainService
嚴重性Severity 錯誤Error
訊息Message 無法 delete DFSR 資料庫。 failed to delete DFSR databases.

其他資料:Additional data:

錯誤碼: %1Error code: %1

錯誤值: %2Error value: %2

Active Directory 偵測到的裝載的網域控制站一樣還原到先前的狀態。Active Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. 需要初始化未經授權還原 SYSVOL 複本本機上。 needs to initialize a non-authoritative restore on the local SYSVOL replica. 適用於 DFSR,這是停止 DFSR 服務、 移除 DFSR 資料庫,與重新開始服務。For DFSR, this is done by stopping the DFSR service, deleting DFSR databases, and re-starting the service. 重新 DFSR 時將會重建資料庫,並開始初始同步。Upon restarting DFSR will rebuild the databases and start the initial sync.
筆記與解析度Notes and resolution 檢查 DFSR 事件登入。Examine the DFSR event log.

錯誤訊息Error Messages

有任何直接互動式錯誤失敗模擬的網域控制站安全快照還原。所有複製資訊登 Directory 服務事件登入。There are no direct interactive errors for failed virtualized domain controller safe snapshot restore; all cloning information logs in the Directory Services event logs. 當然,任何重要的複寫或伺服器廣告錯誤的表現形式症狀其他地方。Naturally, any critical replication or server advertising errors manifest themselves as symptoms elsewhere.

已知的問題,以及案例的支援Known Issues and Support Scenarios

適用於疑難排解網域控制站安全還原一般方法通常適合用來大部分的問題進行疑難排解。The General Methodology for Troubleshooting Domain Controller Safe Restore are usually adequate to troubleshoot most issues.

問題Issue 最近安全還原的網域控制站無法建立新的安全性原則Cannot create new security principals on recently safe restored domain controller
症狀Symptoms 還原之後快照,嘗試使用的網域控制站無法建立新的安全性原則 (使用者、 電腦、 群組):After restoring a snapshot, attempts to create a new security principal (user, computer, group) on that domain controller fail with:

錯誤 0x2010Error 0x2010

Directory 服務無法配置相關的 id。The directory service was unable to allocate a relative identifier.
解析度和筆記Resolution and Notes 還原的電腦的過時掌握移除主機 FSMO 的角色被因為此問題。This issue is caused by the restored computer's stale knowledge of the RID Master FSMO role. 如果角色移到這個或其他網域控制站快照已拍攝的後再還原,還原的網域控制站不會有 RID 主版知識之前完成初始複寫。If the role moved to this or another domain controller after a snapshot was taken and then later restored, the restored domain controller will not have knowledge of the RID master until initial replication has completed.

修正的相關問題,讓完成 AD 複寫還原的網域控制站輸入。To resolve the issue, allow AD replication to complete inbound to the restored domain controller. 如果仍然無法運作,確認所有網域控制站都有之俠主控移除主機相同正確知識。If still not working, validate that all domain controllers have the same correct knowledge of which DC hosts the RID Master.
問題Issue 還原的網域控制站不要共用 SYSVOL 通知Restored domain controllers do not share SYSVOL, advertise
症狀Symptoms 還原快照之後, 一或多個 Dc 不執行動作通知、 不分享 sysvol,並不具有最新狀態 SYSVOL 內容After restoring a snapshot, one or more DCs do not advertise, do not share sysvol, and do not have up to date SYSVOL contents
解析度和筆記Resolution and Notes DC 上游合作夥伴不具有正確複寫 DFSR 或 FRS 運作 SYSVOL 複本The DC's upstream partners do not have a working SYSVOL replica that is correctly replicating with DFSR or FRS. 無關安全還原此問題,但可能會顯示為安全還原的問題,請客戶不知道的影響未還原網域控制站的其他複寫問題,所以This issue is unrelated to safe restore but is likely to manifest as a safe restore issue, because the customer was unaware of the other replication issue affecting un-restored DCs

進階疑難排解Advanced Troubleshooting

這個模組設法教導進階疑難排解,透過使用登某些解釋所發生的範例,以。This module seeks to teach advanced troubleshooting by using working logs as samples, with some explanation of what occurred. 如果您了解成功模擬的網域控制站作業的外觀,失敗明顯地在您的環境中。If you understand what a successful virtualized domain controller operation looks like, failures become obvious in your environment. 這些登的出示來源的遞增訂單以如預期般事件相關複製的網域控制站在每個登入。These logs are presented by their source, with the ascending order of expected events related to a cloned domain controller within each log.

還原網域控制站為何使用 DFSR SYSVOLRestoring a Domain Controller that Replicates SYSVOL Using DFSR

Directory 服務事件登入Directory Services Event Log

Directory 服務登入包含大部分操作資訊的安全還原。The Directory Services log contains the majority of safe restore operational information. Hypervisor 變更 VM 新一代 ID 及 NTDS 服務筆記它,然後失效 RID 集區變更叫用 id。The hypervisor changes the VM-Generation ID and the NTDS service notes it, then invalidates the RID pool and changes the invocation ID. 新 VM 新一代 ID 是設定和伺服器複製輸入廣告的資料。The new VM-Generation ID is set and the servers replicates AD data inbound. DFSR 服務已停止和刪除裝載 SYSVOL 其資料庫,強迫未經授權的同步輸入。The DFSR service is stopped and its database that hosts SYSVOL is deleted, forcing a non-authoritative sync inbound. 調整 USN 高浮水印。The USN high watermark is adjusted.

事件編號Event ID 來源Source 訊息Message
21702170 ActiveDirectory_DomainServiceActiveDirectory_DomainService 偵測到代 ID 變更。A Generation ID change has been detected.

代來電顯示快取中 DS (舊值):Generation ID cached in DS (old value):



代目前中 ID VM (新值):Generation ID currently in VM (new value):



一樣快照的應用程式、 一樣匯入操作後或即時移轉作業之後,就會發生代 ID 變更。The Generation ID change occurs after the application of a virtual machine snapshot, after a virtual machine import operation or after a live migration operation. Active Directory Domain Services 會建立新的叫用 ID 復原網域控制站。Active Directory Domain Services will create a new invocation ID to recover the domain controller. 應還原模擬的網域控制站使用一樣的快照。Virtualized domain controllers should not be restored using virtual machine snapshots. 支援的方法來還原或復原 content Active Directory Domain Services 資料庫的是還原所做的 Active Directory Domain Services 注意備份應用程式的系統狀態備份。 」The supported method to restore or rollback the content of an Active Directory Domain Services database is to restore a system state backup made with an Active Directory Domain Services aware backup application."
21812181 ActiveDirectory_DomainServiceActiveDirectory_DomainService 交易中止因為一樣會還原到先前的狀態。The transaction was aborted due to the virtual machine being reverted to a previous state. 這是在一樣快照的應用程式、 一樣匯入進行操作之後,或之後即時移轉作業。This occurs after the application of a virtual machine snapshot, after a virtual machine import operation, or after a live migration operation.
22042204 ActiveDirectory_DomainServiceActiveDirectory_DomainService Active Directory Domain Services 偵測一樣代收到的變更Active Directory Domain Services has detected a change of virtual machine generation ID. 變更表示 virtual 網域控制站的已經還原到先前的狀態。The change means that the virtual domain controller has been reverted to a previous state. Active Directory Domain Services 將會執行下列操作保護還原網域控制站分歧可能的資料免於和保護安全性主體的 Sid 重複建立:Active Directory Domain Services will perform the following operations to protect the reverted domain controller against possible data divergence and to protect creation of security principals with duplicate SIDs:

建立新的叫用 IDCreate a new invocation ID

使目前 RID 集區Invalidate current RID pool

將會在下一步輸入複寫驗證故障的擁有權。Ownership of the FSMO roles will be validated at next inbound replication. 這項視窗期間如果網域控制站保留 FSMO 的角色,該角色將無法使用。During this window if the domain controller held a FSMO role, that role will be unavailable.

開始 SYSVOL 複寫服務還原操作。Start SYSVOL replication service restore operation.

[開始]︰ 複寫將還原網域控制站帶到最新狀態。Start replication to bring the reverted domain controller to the most current state.

要求 RID 新集區。 」Request a new RID pool."
21812181 ActiveDirectory_DomainServiceActiveDirectory_DomainService 交易中止因為一樣會還原到先前的狀態。The transaction was aborted due to the virtual machine being reverted to a previous state. 這是在一樣快照的應用程式、 一樣匯入進行操作之後,或之後即時移轉作業。This occurs after the application of a virtual machine snapshot, after a virtual machine import operation, or after a live migration operation.
11091109 ActiveDirectory_DomainServiceActiveDirectory_DomainService 已變更此 directory 伺服器呼叫識別碼屬性。The invocationID attribute for this directory server has been changed. 在建立備份之的時間的最高更新序號如下:The highest update sequence number at the time the backup was created is as follows:

呼叫識別碼屬性 (舊值):InvocationID attribute (old value):



呼叫識別碼屬性 (新值):InvocationID attribute (new value):



更新的序號:Update sequence number:



呼叫識別碼 directory 伺服器還原備份媒體,從時變更設定為主控寫入應用程式 directory 磁碟分割、 已繼續一樣快照套用之後,在一樣匯入作業,或之後即時移轉作業。The invocationID is changed when a directory server is restored from backup media, is configured to host a writeable application directory partition, has been resumed after a virtual machine snapshot has been applied, after a virtual machine import operation, or after a live migration operation. 應還原模擬的網域控制站使用一樣的快照。Virtualized domain controllers should not be restored using virtual machine snapshots. 還原或回復到支援的方法的 Active Directory Domain Services 資料庫 content 是還原進行備份 Active Directory Domain Services 感知應用程式的系統狀態備份。 」The supported method to restore or rollback the content of an Active Directory Domain Services database is to restore a system state backup made with an Active Directory Domain Services-aware backup application."
21792179 ActiveDirectory_DomainServiceActiveDirectory_DomainService MsDS-GenerationId 物件的屬性網域控制站的電腦已設定為下列參數:The msDS-GenerationId attribute of the Domain Controller's computer object has been set to the following parameter:

GenerationID 屬性:GenerationID attribute:

22002200 ActiveDirectory_DomainServiceActiveDirectory_DomainService Active Directory 偵測到的裝載的網域控制站一樣還原到先前的狀態。Active Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. Active Directory Domain Services 初始化複寫將目前的網域控制站。Active Directory Domain Services initializes replication to bring the domain controller current. 完成複寫事件 2201年將會登入。Event 2201 will be logged when the replication is finished.
22012201 ActiveDirectory_DomainServiceActiveDirectory_DomainService Active Directory 偵測到的裝載的網域控制站一樣還原到先前的狀態。Active Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. 完成將目前的網域控制站複寫 active Directory Domain Services。Active Directory Domain Services has finished replication to bring the domain controller current.
21852185 ActiveDirectory_DomainServiceActiveDirectory_DomainService Active Directory Domain Services 停止 FRS 或 DFSR 所用服務複寫 SYSVOL 資料夾。Active Directory Domain Services stopped the FRS or DFSR service used to replicate the SYSVOL folder.

服務的名稱︰Service name:

DFSRDFSR

Active Directory 偵測到的裝載的網域控制站一樣還原到先前的狀態。Active Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. Active Directory Domain Services 必須初始化未經授權還原 SYSVOL 複本本機上。Active Directory Domain Services must initialize a non-authoritative restore on the local SYSVOL replica. 這會的停止 FRS 或 DFSR 服務使用複寫 SYSVOL 資料夾並開始它值觸發還原至適當登錄與執行。This is performed by stopping the FRS or DFSR service used to replicate the SYSVOL folder and starting it with the appropriate registry keys and values to trigger the restore. 事件 2187年將會登入重新開始 FRS 或 DFSR 服務時。 」Event 2187 will be logged when FRS or DFSR service is restarted."
22082208 ActiveDirectory_DomainServiceActiveDirectory_DomainService Active Directory Domain Services 刪除 DFSR 資料庫未經授權還原程序期間初始化 SYSVOL 複本。Active Directory Domain Services deleted DFSR databases to initialize SYSVOL replica during a non-authoritative restore.

Active Directory 偵測到的裝載的網域控制站一樣還原到先前的狀態。Active Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. Active Directory Domain Services 需要初始化未經授權還原 SYSVOL 複本本機上。Active Directory Domain Services needs to initialize a non-authoritative restore on the local SYSVOL replica. 適用於 DFSR,這是停止 DFSR 服務、 移除 DFSR 資料庫,與重新開始服務。For DFSR, this is done by stopping the DFSR service, deleting DFSR databases, and re-starting the service. 重新 DFSR 時將會重建資料庫,並開始初始同步。Upon restarting DFSR will rebuild the databases and start the initial sync. ""
21872187 ActiveDirectory_DomainServiceActiveDirectory_DomainService Active Directory Domain Services 開始 FRS 或 DFSR 所用服務複寫 SYSVOL 資料夾。Active Directory Domain Services started the FRS or DFSR service used to replicate the SYSVOL folder.

服務的名稱︰Service name:

DFSRDFSR

Active Directory 偵測到的裝載的網域控制站一樣還原到先前的狀態。Active Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. Active Directory Domain Services 需要初始化未經授權還原 SYSVOL 複本本機上。Active Directory Domain Services needed to initialize a non-authoritative restore on the local SYSVOL replica. 這是的停止 FRS 或 DFSR 服務使用複寫 SYSVOL 資料夾並開始它值觸發還原至適當登錄與。This was done by stopping the FRS or DFSR service used to replicate the SYSVOL folder and starting it with the appropriate registry keys and values to trigger the restore. ""
15871587 ActiveDirectory_DomainServiceActiveDirectory_DomainService 這項服務 directory 已還原或已設定為裝載應用程式 directory 磁碟分割。This directory service has been restored or has been configured to host an application directory partition. 如此一來,其複寫身分已變更。As a result, its replication identity has changed. 合作夥伴要求複寫對使用我們舊的身分。A partner has requested replication changes using our old identity. 已經調整開始的序號。The starting sequence number has been adjusted.

目的地 directory 服務下列物件 GUID 要求變更開始之前,在當地 directory 服務已從備份的媒體還原的 USN USN 相對應。The destination directory service corresponding to the following object GUID has requested changes starting at a USN that precedes the USN at which the local directory service was restored from backup media.

物件 GUID:Object GUID:

()()

還原同時 USN:USN at the time of restore:



如此一來,最新的向量的目的地 directory 服務已使用下列設定。As a result, the up-to-dateness vector of the destination directory service has been configured with the following settings.

先前資料庫 GUID:Previous database GUID:



先前的物件 USN:Previous object USN:



先前屬性 USN:Previous property USN:



新的 GUID 資料庫:New database GUID:



新的物件 USN:New object USN:



新的屬性 USN:New property USN:

系統事件登入System Event Log

系統事件登入記下的電腦提供離線一樣回 online 同步處理時間主機時,就會發生的時間。The System event log notes that the machine time that occurs when bringing an offline virtual machine back online and synchronizing with host time. RID 集區失效且 DFSR 或 FRS 服務會重新起始。The RID pool invalidates and the DFSR or FRS services are restarted.

事件編號Event ID 來源Source 訊息Message
11 核心-一般Kernel-General 已變更系統時間,以嗎?The system time has changed to ? < 快照時間日日期 >from <snapshot time/date>.

變更理由: 應用程式或系統元件變更的時間。Change Reason: An application or system component changed the time.
1665416654 薩姆-directory-服務Directory-Services-SAM 已無效 account 識別碼 (Rid) 的集區。A pool of account-identifiers (RIDs) has been invalidated. 這可能是因為預期如下:This may occur in the following expected cases:

1.網域控制站是從備份還原。1. A domain controller is restored from backup.

2.網域控制站執行一樣會還原的快照。2. A domain controller running on a virtual machine is restored from snapshot.

3.系統管理員的身分,以手動方式有失效集區。3. An administrator has manually invalidated the pool.

查看 http://go.microsoft.com/fwlink/?LinkId=226247 如需詳細資訊。See http://go.microsoft.com/fwlink/?LinkId=226247 for more information.
70367036 服務控制管理員Service Control Manager DFS 複寫服務輸入停止的狀態。The DFS Replication service entered the stopped state.
70367036 服務控制管理員Service Control Manager DFS 複寫服務輸入執行的狀態。The DFS Replication service entered the running state.
應用程式事件登入Application Event Log

應用程式筆記 DFSR 資料庫停止並開始。The Application event log notes the DFSR database stopping and starting.

事件編號Event ID 來源Source 訊息Message
103103 ESENTESENT \.\C:\System Volume Information\DFSR\database DFSRs (1360)_\dfsr.db: 資料庫引擎停止 (0) 的執行個體。DFSRs (1360) \\.\C:\System Volume Information\DFSR\database_\dfsr.db: The database engine stopped the instance (0).

不正常關機: 0Dirty Shutdown: 0

內部的時間順序: 0.000 [1] 0.000 [2]、 0.000 [3]、 [4] 0.000、 0.141 [5]、 [6] 0.000、 0.000 [7]、 0.000 [8]、 [9] 0.000、 0.000 [10]、 0.016 [11]、 0.000 [12]、 [13] 0.000、 0.000 [14]、 0.000 [15]。Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.000, [4] 0.000, [5] 0.141, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.000, [10] 0.000, [11] 0.016, [12] 0.000, [13] 0.000, [14] 0.000, [15] 0.000.
102102 ESENTESENT \.\C:\System Volume Information\DFSR\database DFSRs (532)_\dfsr.db: 資料庫引擎 (6.02.8189.0000) 的新執行個體 (0) 開始。DFSRs (532) \\.\C:\System Volume Information\DFSR\database_\dfsr.db: The database engine (6.02.8189.0000) is starting a new instance (0).
105105 ESENTESENT \.\C:\System Volume Information\DFSR\database DFSRs (532)_\dfsr.db: 資料庫引擎會開始新的執行個體 (0)。DFSRs (532) \\.\C:\System Volume Information\DFSR\database_\dfsr.db: The database engine started a new instance (0). (時間 = 0 秒)(Time=0 seconds)

內部的時間順序: 0.000 [1] 0.000 [2]、 0.000 [3]、 [4] 0.000、 0.000 [5]、 [6] 0.000、 0.000 [7]、 0.000 [8]、 [9] 0.031、 0.000 [10]、 [11] 0.000。Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.000, [4] 0.000, [5] 0.000, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.031, [10] 0.000, [11] 0.000.
\.\C:\System Volume Information\DFSR\database DFSRs (532)_\dfsr.db: 資料庫引擎建立新的資料庫 (\.\C:\System Volume Information\DFSR\database 1,_\dfsr.db)。DFSRs (532) \\.\C:\System Volume Information\DFSR\database_\dfsr.db: The database engine created a new database (1, \\.\C:\System Volume Information\DFSR\database_\dfsr.db). (時間 = 0 秒)(Time=0 seconds)

內部的時間順序: 0.000 [1] 0.000 [2]、 0.016 [3]、 [4] 0.062、 [5] 0.000、 0.016 [6]、 [7] 0.000、 0.000 [8]、 [9] 0.015、 0.000 [10]、 0.000 [11]。Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.016, [4] 0.062, [5] 0.000, [6] 0.016, [7] 0.000, [8] 0.000, [9] 0.015, [10] 0.000, [11] 0.000.
DFS 複寫事件登入DFS Replication Event Log

DFSR 服務已停止和資料庫包含 SYSVOL 刪除,強迫未經授權的同步處理輸入。The DFSR service is stopped and the database that contains SYSVOL is deleted, forcing a non-authoritative synchronization inbound.

事件編號Event ID 來源Source 訊息Message
10061006 DFSRDFSR 停止 DFS 複寫服務。The DFS Replication service is stopping.
10081008 DFSRDFSR DFS 複寫服務已停止。The DFS Replication service has stopped.
10021002 DFSRDFSR 開始工作 DFS 複寫服務。The DFS Replication service is starting.
10041004 DFSRDFSR 開始 DFS 複寫服務。The DFS Replication service has started.
13141314 DFSRDFSR DFS 複寫服務成功設定的偵錯登入的檔案。The DFS Replication service successfully configured the debug log files.

其他資訊:Additional Information:

偵錯登入的檔案路徑: C:\Windows\debugDebug Log File Path: C:\Windows\debug
61026102 DFSRDFSR DFS 複寫服務已成功已經登記完畢 WMI 提供者。The DFS Replication service has successfully registered the WMI provider.
12061206 DFSRDFSR DFS 複寫服務順利聯繫的網域控制站* 來存取設定的資訊。The DFS Replication service successfully contacted domain controller * to access configuration information.
12101210 DFSRDFSR 成功設定傳入複寫要求 RPC 其實 DFS 複寫服務。The DFS Replication service successfully set up an RPC listener for incoming replication requests.

其他資訊:Additional Information:

連接埠: 0Port: 0
46144614 DFSRDFSR 在本機路徑 C:\Windows\SYSVOL\domain 初始化 SYSVOL DFS 複寫服務,並執行初始複寫正在等待。The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. 複寫的資料夾會維持在初始同步狀態複寫其合作夥伴使用。The replicated folder will remain in the initial synchronization state until it has replicated with its partner. 如果在升級為網域控制站伺服器,網域控制站不會通知和這個問題之前解析為網域控制站運作。If the server was in the process of being promoted to a domain controller, the domain controller will not advertise and function as a domain controller until this issue is resolved. 如果指定的合作夥伴也是在初始同步狀態下,或共用違規此伺服器上同步處理合作夥伴,這可能會發生。This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the synchronization partner. 如果發生 SYSVOL 移轉期間這個事件 DFS 複寫的檔案複製服務 (FRS),請變更不會複寫出辨識這個問題之前。If this event occurred during the migration of SYSVOL from File Replication Service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. 這會造成 SYSVOL 資料夾變成與其他網域控制站不同步此伺服器上。This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.

其他資訊:Additional Information:

複製的資料夾的名稱︰ SYSVOL 分享Replicated Folder Name: SYSVOL Share

複製的資料夾 ID:Replicated Folder ID:

複寫群組的名稱︰ 網域系統磁碟區Replication Group Name: Domain System Volume

複寫群組 ID:Replication Group ID:

會員 ID:Member ID:

唯讀模式: 0Read-Only: 0
46044604 DFSRDFSR DFS 複寫服務順利初始化在本機路徑 C:\Windows\SYSVOL\domain SYSVOL 複寫資料夾。The DFS Replication service successfully initialized the SYSVOL replicated folder at local path C:\Windows\SYSVOL\domain. 這個成員已完成合作夥伴 dc1.corp.contoso.com SYSVOL 的初始同步的處理。This member has completed initial synchronization of SYSVOL with partner dc1.corp.contoso.com. 若要檢查有任何 SYSVOL 共用,請打開在命令提示字元視窗,然後輸入 「 網路共用 」。To check for the presence of the SYSVOL share, open a command prompt window and then type "net share".

其他資訊:Additional Information:

複製的資料夾的名稱︰ SYSVOL 分享Replicated Folder Name: SYSVOL Share

複製的資料夾 ID:Replicated Folder ID:

複寫群組的名稱︰ 網域系統磁碟區Replication Group Name: Domain System Volume

複寫群組 ID:Replication Group ID:

會員 ID:Member ID:

同步合作夥伴:Sync partner:

還原網域控制站為何使用 FRS SYSVOLRestoring a Domain Controller that Replicates SYSVOL Using FRS

檔案複寫事件登入此時使用而不是 DFSR 事件登入。The File Replication Event log is used instead of the DFSR event log in this case. 應用程式也會將 FRS 相關的不同事件。The Application event log also writes different FRS-related events. 否則,Directory 服務和系統事件登入訊息通常都相同,並在同一個訂單以之前所述。Otherwise, the Directory Services and System Event log messages are generally the same and in the same order as previously described.

檔案複製服務事件登入File Replication Service Event Log

FRS 服務已停止,且重新起始非系統授權同步 SYSVOL D2 BURFLAGS 值。The FRS service is stopped and restarted with a D2 BURFLAGS value to non-authoritatively synchronize SYSVOL.

事件編號Event ID 來源Source 訊息Message
1350213502 NTFRSNTFRS 停止檔案複寫服務。The File Replication Service is stopping.
1350313503 NTFRSNTFRS 檔案複製服務已停止。The File Replication Service has stopped.
1350113501 NTFRSNTFRS 開始檔案複寫服務The File Replication Service is starting
1351213512 NTFRSNTFRS 複製檔案服務偵測到的磁碟機上的電腦 DC4 directory c:\windows\ntfrs\jet 讓的磁碟寫入快取。The File Replication Service has detected an enabled disk write cache on the drive containing the directory c:\windows\ntfrs\jet on the computer DC4. 檔案複寫服務可能無法修復磁碟機的電源中斷重大更新將會失去時。The File Replication Service might not recover when power to the drive is interrupted and critical updates are lost.
1356513565 NTFRSNTFRS 檔案複寫服務初始化從另一部網域控制站的資料與系統磁碟區。File Replication Service is initializing the system volume with data from another domain controller. 此程序完成之前電腦 DC4 無法加入網域控制站。Computer DC4 cannot become a domain controller until this process is complete. 然後將會為 SYSVOL 共用系統磁碟區。The system volume will then be shared as SYSVOL.

若要檢查 SYSVOL 共用,請在命令提示字元中,輸入To check for the SYSVOL share, at the command prompt, type:

共用網路net share

在檔案複寫服務完成初始設定程序,會出現 SYSVOL 共用。When File Replication Service completes the initialization process, the SYSVOL share will appear.

系統磁碟區的初始設定可能需要一些時間。The initialization of the system volume can take some time. 是的系統磁碟區,可供使用的其他網域控制站,以及複寫之間的時間間隔網域控制站的資料量而定。 」The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers."
1352013520 NTFRSNTFRS 將檔案複製服務移動既有的檔案* \NtFrs_PreExisting___See_EventLog。The File Replication Service moved the preexisting files in * to \NtFrs_PreExisting___See_EventLog.

複製檔案服務可能 delete 中的檔案* 隨時 \NtFrs_PreExisting___See_EventLog。The File Replication Service may delete the files in *\NtFrs_PreExisting___See_EventLog at any time. 檔案可以複製全新儲存刪除從* \NtFrs_PreExisting___See_EventLog。Files can be saved from deletion by copying them out of *\NtFrs_PreExisting___See_EventLog. 複製檔案到* 如果已經有一些其他複製合作夥伴這些檔案名稱衝突可能導致。Copying the files into * may lead to name conflicts if the files already exist on some other replicating partner.

有時候,檔案複寫服務可能複製檔案的* \NtFrs_PreExisting___See_EventLog 到 而不是複製檔案的其他複製協力廠商。In some cases, the File Replication Service may copy a file from *\NtFrs_PreExisting___See_EventLog into instead of replicating the file from some other replicating partner.

空間可以隨時復原刪除中的檔案的* \NtFrs_PreExisting___See_EventLog。Space can be recovered at any time by deleting the files in *\NtFrs_PreExisting___See_EventLog.
1355313553 NTFRSNTFRS 檔案複寫服務順利加入這台電腦複本下列設定:The File Replication Service successfully added this computer to the following replica set:

「 網域系統磁碟區 (SYSVOL 共用) 」"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"

這個事件和相關的資訊如下所示:Information related to this event is shown below:

電腦 DNS 名稱]]Computer DNS name is ""

複本設定成員名稱]]Replica set member name is ""

複本設定根路徑 」]Replica set root path is ""

執行的路徑複本]* * ]Replica staging directory path is " "

已正常運作的路徑複本]]Replica working directory path is ""
1355413554 NTFRSNTFRS 檔案複寫服務順利新增連接到複本組如下:The File Replication Service successfully added the connections shown below to the replica set:

「 網域系統磁碟區 (SYSVOL 共用) 」"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"

從輸入]]Inbound from ""

輸出到]]Outbound to ""

詳細資訊,可能會出現在後續事件登入訊息。More information may appear in subsequent event log messages.
1351613516 NTFRSNTFRS 檔案複寫服務不會再從成為網域控制站讓電腦 DC4。The File Replication Service is no longer preventing the computer DC4 from becoming a domain controller. 已成功初始化系統磁碟區,已經通知 Netlogon 服務,系統磁碟區現在已經準備好 SYSVOL 共用。The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL.

輸入 「 共用網路] 來檢查是否有 SYSVOL 共用。Type "net share" to check for the SYSVOL share.
應用程式事件登入Application Event Log

FRS 資料庫停止開始,並會清除 D2 BURFLAGS 作業。The FRS database stops and starts, and is purged due to the D2 BURFLAGS operation.

事件編號Event ID 來源Source 訊息Message
327327 ESENTESENT (1424) ntfrs 資料庫引擎分離資料庫 (1、 c:\windows\ntfrs\jet\ntfrs.jdb)。ntfrs (1424) The database engine detached a database (1, c:\windows\ntfrs\jet\ntfrs.jdb). (時間 = 0 秒)(Time=0 seconds)

內部的時間順序: 0.000 [1] 0.015 [2]、 0.000 [3]、 [4] 0.000、 0.000 [5]、 0.516 [6]、 [7] 0.000、 0.000 [8]、 [9] 0.000、 0.000 [10]、 0.063 [11]、 [12] 0.000。Internal Timing Sequence: [1] 0.000, [2] 0.015, [3] 0.000, [4] 0.000, [5] 0.000, [6] 0.516, [7] 0.000, [8] 0.000, [9] 0.000, [10] 0.000, [11] 0.063, [12] 0.000.

恢復快取: 0Revived Cache: 0
103103 ESENTESENT (1424) ntfrs 資料庫引擎停止 (0) 的執行個體。ntfrs (1424) The database engine stopped the instance (0).

不正常關機: 0Dirty Shutdown: 0

內部的時間順序: 0.000 [1] 0.000 [2]、 0.000 [3]、 [4] 0.000、 0.000 [5]、 [6] 0.000、 0.000 [7]、 0.000 [8]、 0.031 [9]、 0.000 [10]、 0.016 [11]、 [12] 0.000、 0.000 [13]、 [14] 0.047、 0.000 [15]。Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.000, [4] 0.000, [5] 0.000, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.031, [10] 0.000, [11] 0.016, [12] 0.000, [13] 0.000, [14] 0.047, [15] 0.000.
102102 ESENTESENT (3000) ntfrs 資料庫引擎 (6.02.8189.0000) 的新執行個體 (0) 開始。ntfrs (3000) The database engine (6.02.8189.0000) is starting a new instance (0).
105105 ESENTESENT (3000) ntfrs 資料庫引擎會開始新的執行個體 (0)。ntfrs (3000) The database engine started a new instance (0). (時間 = 0 秒)(Time=0 seconds)

內部的時間順序: 0.000 [1] 0.000 [2]、 0.000 [3]、 [4] 0.000、 [5] 0.000、 0.000 [6]、 [7] 0.000、 0.000 [8]、 [9] 0.062、 0.000 [10]、 0.141 [11]。Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.000, [4] 0.000, [5] 0.000, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.062, [10] 0.000, [11] 0.141.
103103 ESENTESENT (3000) ntfrs 資料庫引擎停止 (0) 的執行個體。ntfrs (3000) The database engine stopped the instance (0).

不正常關機: 0Dirty Shutdown: 0

內部的時間順序: 0.000 [1] 0.000 [2]、 0.000 [3]、 [4] 0.000、 0.000 [5]、 [6] 0.000、 0.000 [7]、 0.000 [8]、 0.000 [9]、 0.000 [10]、 0.000 [11]、 [12] 0.000、 0.015 [13]、 [14] 0.000、 0.000 [15]。Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.000, [4] 0.000, [5] 0.000, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.000, [10] 0.000, [11] 0.000, [12] 0.000, [13] 0.015, [14] 0.000, [15] 0.000.
102102 ESENTESENT (3000) ntfrs 資料庫引擎 (6.02.8189.0000) 的新執行個體 (0) 開始。ntfrs (3000) The database engine (6.02.8189.0000) is starting a new instance (0).
105105 ESENTESENT (3000) ntfrs 資料庫引擎會開始新的執行個體 (0)。ntfrs (3000) The database engine started a new instance (0). (時間 = 0 秒)(Time=0 seconds)

內部的時間順序: 0.000 [1] 0.000 [2]、 0.000 [3]、 [4] 0.000、 [5] 0.000、 0.000 [6]、 [7] 0.000、 0.000 [8]、 [9] 0.078、 0.000 [10]、 0.109 [11]。Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.000, [4] 0.000, [5] 0.000, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.078, [10] 0.000, [11] 0.109.
325325 ESENTESENT (3000) ntfrs 資料庫引擎建立新的資料庫 (1、 c:\windows\ntfrs\jet\ntfrs.jdb)。ntfrs (3000) The database engine created a new database (1, c:\windows\ntfrs\jet\ntfrs.jdb). (時間 = 0 秒)(Time=0 seconds)

內部的時間順序: 0.000 [1] 0.000 [2]、 0.016 [3]、 [4] 0.016、 [5] 0.000、 0.015 [6]、 [7] 0.000、 0.000 [8]、 [9] 0.078、 0.016 [10]、 0.000 [11]。Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.016, [4] 0.016, [5] 0.000, [6] 0.015, [7] 0.000, [8] 0.000, [9] 0.078, [10] 0.016, [11] 0.000.
103103 ESENTESENT (3000) ntfrs 資料庫引擎停止 (0) 的執行個體。ntfrs (3000) The database engine stopped the instance (0).

不正常關機: 0Dirty Shutdown: 0

內部的時間順序: 0.000 [1] 0.000 [2]、 0.000 [3]、 [4] 0.000、 0.078 [5]、 [6] 0.000、 0.000 [7]、 0.000 [8]、 0.125 [9]、 0.016 [10]、 0.000 [11]、 [12] 0.000、 0.000 [13]、 [14] 0.000、 0.000 [15]。Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.000, [4] 0.000, [5] 0.078, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.125, [10] 0.016, [11] 0.000, [12] 0.000, [13] 0.000, [14] 0.000, [15] 0.000.
102102 ESENTESENT (3000) ntfrs 資料庫引擎 (6.02.8189.0000) 的新執行個體 (0) 開始。ntfrs (3000) The database engine (6.02.8189.0000) is starting a new instance (0).
105105 ESENTESENT (3000) ntfrs 資料庫引擎會開始新的執行個體 (0)。ntfrs (3000) The database engine started a new instance (0). (時間 = 0 秒)(Time=0 seconds)

內部的時間順序: 0.016 [1] 0.000 [2]、 0.000 [3]、 [4] 0.094、 [5] 0.000、 0.000 [6]、 [7] 0.000、 0.000 [8]、 [9] 0.032、 0.000 [10]、 0.000 [11]。Internal Timing Sequence: [1] 0.016, [2] 0.000, [3] 0.000, [4] 0.094, [5] 0.000, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.032, [10] 0.000, [11] 0.000.
326326 ESENTESENT (3000) ntfrs 資料庫引擎連接資料庫 (1、 c:\windows\ntfrs\jet\ntfrs.jdb)。ntfrs (3000) The database engine attached a database (1, c:\windows\ntfrs\jet\ntfrs.jdb). (時間 = 0 秒)(Time=0 seconds)

內部的時間順序: 0.000 [1] 0.015 [2]、 0.000 [3]、 [4] 0.000、 0.016 [5]、 0.015 [6]、 [7] 0.000、 0.000 [8]、 [9] 0.000、 0.000 [10]、 0.000 [11]、 [12] 0.000。Internal Timing Sequence: [1] 0.000, [2] 0.015, [3] 0.000, [4] 0.000, [5] 0.016, [6] 0.015, [7] 0.000, [8] 0.000, [9] 0.000, [10] 0.000, [11] 0.000, [12] 0.000.

儲存快取︰ 1Saved Cache: 1