/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

Unitrends Recovery

Unable to manage Active Directory for a recently restored Domain Controller

ISSUE

You've recently restored an Active Directory domain controller either via WinIR, VMIR or straight restore via host-based or file-based backup.

Upon opening any Active Directory management tools such as Users and Computers (ADUC) and Group Policy Management Console (GPMC), you're presented with the following error: "The specified domain either does not exist or could not be contacted."

User-added image

Or, the error message may be "There are currently no logon servers available to service the logon request."

RESOLUTION

After restoring a domain controller, login and confirm that the SYSVOL share is present. The command to do this is `net share | findstr /b SYSVOL`.
If the SYSVOL share is not present, then you need to perform a series of steps (below) to make it available again, including your group policy objects and scripts.

Log into the domain controller
Open File Explorer and navigate to C:\Windows\SYSVOL\domain\
Follow the link for your domain
Enter folder “NtFrs_PreExisting__See_EventLog”
Copy the content to a new folder on the desktop
Open the Registry Editor and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
Set SysVolReady to 0
In the Registry Editor, navigate to HKLM\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
Set BurFlags to D4
Open services.msc
Restart the “File Replication” service
Copy the data from the new folder (see step #5) back to the folder for your domain location under C:\Windows\SYSVOL\domain\
In the Registry Editor, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
Set SysVolReady to 1
[Optional] Reboot

CAUSE

There can be many causes for this particular condition. In most cases, the domain services did not come up in the proper order on the affected domain controller.

Please keep in mind that restoring a domain controller is not recommended unless you have no other domain controllers in your environment. The majority of situations that we've seen this particular issue in is where a domain controller is spun up in a DR environment.

NOTES

https://support.microsoft.com/en-us/help/290762/using-the-burflags-registry-key-to-reinitialize-file-replication-servi
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/hh147324(v=ws.10)