When restoring a database, you usually start with restoring a full backup, then any differentials, and finally the transaction logs. You set the database restore mode to WITH NORECOVERY, which allows you to perform these additional restores.
But what if you find out that there's nothing more to restore, leaving you with a database stuck in Restoring mode? Then you only need to run a single T-SQL statement:
RESTORE DATABASE [db_name] WITH RECOVERY
Replace db_name with the name of your database.
Follow the chart below to successfully perform a rolling upgrade of your HA SQL Server cluster.
Domain Naming Master
Also, if your domain is top-level in the AD forest, configure DC1 to sync with external time sources.
To safely remove a node from a Windows 2003 Fail-Over Cluster, follow these steps:
Microsoft has released the Azure Active Directory Connect to the general public. Azure AD Connect replaces (although "incorporates" is a better word) DirSync as the new tool to set up synchronization between your on-premise Active Directory and Azure Active Directory, including Office 365.
The current version of Azure AD Connect is only the beginning. Microsoft has announced a lot more features, which will be made available in the next versions.
More information and installation resources: https://azure.microsoft.com/nl-nl/documentation/articles/active-directory-aadconnect/
Active Directory (AD) integrated DNS zones are not replicated by the DNS server, but replicates through the Active Directory replication mechanism, and uses the same settings for AD replication.
You can trigger replication through Active Directory Sites and Services, or with repadmin.exe on command prompt:
repadmin.exe /replicate target_dc source_dc DC=DomainDnsZones,DC=domain,DC=com
Replace parameters accordingly: