time-clock-circle multiple-users-1 bin-paper-1 smiley-indifferent view-off alert-diamond envelope-letter rating-star network-browser pencil-write ticket-1 button-record headphones-customer-support close synchronize-arrows-1 common-file-stack close-quote arrow-down-2 multiple-circle attachment-1 folder-file-1 disable smiley-indifferent shield-warning love-it smiley-smile-1_1 check-circle-1 time-clock-midnight floppy-disk view smiley-unhappy book-star lock-unlock-1 arrow-right-1 archive smiley-unhappy send-email-1 hierarchy-9 open-quote add-circle-bold search remove-circle cog-1 filter-1 hyperlink-2 analytics-pie-2 flying-insect-honey navigation-menu-horizontal pencil-1 smiley-thrilled check-1 arrow-up-1 lock-2 navigation-menu add layout-module-1 archive arrow-left-1 wench arrow-down-1 multiple-neutral-1 expand-6 close drawer-send alarm-bell-1 social-media-twitter keyboard-arrow-up ticket-1 copy-paste rating-star download-thick-bottom information-circle smiley-sad-1 single-neutral-actions remove-square-1 file-code pencil-1 keyboard-arrow-down smiley-sad-1 cog single-neutral add-circle move-to-top list-bullets expand-6 undo tags-double smiley-happy view-1 messages-bubble-square print-text add-square smiley-happy credit-card-1 envelope-letter diagram-fall-down

System Recovery of server with Active Directory role

How to avoid a USN rollback condition

To avoid a USN rollback condition with a recovered Active Directory (AD) server in an environment with one or more additional AD servers, follow the steps below. These steps were provided by Microsoft and then modified for use with our System Recovery Environment (SRE) bootable media. 

  1. Recover the system using the SRE bootable media as described in the kb Computer System Recovery (BMR). Prior to booting the system normally the first time after completing the system recovery you must edit the registry to indicate the AD database was restored from backup. Do not allow the domain controller to restart and boot in normal mode before the registry edit takes place. If you restart and the recovered AD server begins to start in normal mode, turn off the machine to prevent it from completing startup. Microsoft recommends pressing F8 during the initial boot up sequence to initiate the advanced boot option called DSRM that may not be present on the recovered system. Instead, we can boot into the SRE environment again to edit the registry, before the first normal boot of the system. So, after system recovery using the SRE and the prompt to reboot is accepted, the system should still be configured to boot using the SRE. If so, you should see a prompt to 'press any key to boot from CD...' The SRE gives you a short period of time to confirm booting into the SRE. Press the space bar when you see the message to press any key to boot. If you miss the time period and the system starts to boot normally, power off the system and repeat the process until you boot into the SRE.
  2. Open Registry Editor. To open Registry Editor, on the SRE menu, select the second item to open a command prompt. Type regedit and hit enter. In Registry Editor, click on HKEY_LOCAL_MACHINE, then go to File menu and click 'Load Hive'. Navigate to the restored Windows\System32\config folder and select the SYSTEM file. The restored Windows directory could be on the C: drive but the SRE may have assigned it a different drive letter. Click Open. Give it the name RecoveredSYSTEM.
  3. Expand the following path: HKEY_LOCAL_MACHINE\RecoveredSYSTEM\CurrentControlSet\Services\NTDS\Parameters. (If there is no CurrentControlSet but there is a CurrentControlSet1, use it instead.) Look for a value named DSA Previous Restore Count. If the value is there, make a note of the setting value. If the value is not there, the setting is equal to the default, which is zero. Do not add a value if you do not see one there.
  4. Right-click the Parameters key, click New, and then click DWORD (32-bit) Value.
  5. Type the new name Database restored from backup, exactly as shown, and then press ENTER.
  6. Double-click the value that you just created to open the Edit DWORD (32-bit) Value dialog box, and then type 1 in the Value data box. 
  7. Restart the domain controller in normal mode.
  8. When the domain controller restarts, open Event Viewer. To open Event Viewer, click Start, click Control Panel, double-click Administrative Tools, and then double-click Event Viewer.
  9. Expand Application and Services Logs, and then click the Directory Services log. Ensure that events appear in the details pane.
  10. Right-click the Directory Services log, and then click Find. In Find what, type 1109, and then click Find Next.
  11. You should see at least an Event ID 1109 entry. If you do not see this entry, proceed to the next step. Otherwise, double-click the entry, and then review the text confirming that the update was made to the InvocationID:
  12. Active Directory has been restored from backup media, or has been configured to host an application partition. The invocationID attribute for this directory server has been changed. The highest update sequence number at the time the backup was created is <time> InvocationID attribute (old value):<Previous InvocationID value> InvocationID attribute (new value):<New InvocationID value> Update sequence number:<USN> The InvocationID is changed when a directory server is restored from backup media or is configured to host a writeable application directory partition. 
  13. Close Event Viewer.
  14. Use Registry Editor to verify that the value in DSA Previous Restore Count is equal to the previous value plus one. If this is not the correct value and you cannot find an entry for Event ID 1109 in Event Viewer, verify that the domain controller’s service packs are current. You cannot try this procedure again on the same VHD. You can try again on a copy of the VHD or a different VHD that has not been started in normal mode by starting over at step 1.
  15. Close Registry Editor.