Merge pull request #67974 from billmath/csat2

renaming file

Author: ktoliver

.openpublishing.redirection.json

@@ -16972,7 +16972,12 @@
     },
     {
       "source_path": "articles/active-directory/connect/active-directory-aadconnectsync-operations.md",
-      "redirect_url": "/azure/active-directory/hybrid/how-to-connect-sync-operations",
+      "redirect_url": "/azure/active-directory/hybrid/how-to-connect-sync-staging-server",
+      "redirect_document_id": false
+    },
+	    {
+      "source_path": "articles/active-directory/hybrid/how-to-connect-sync-operations.md",
+      "redirect_url": "/azure/active-directory/hybrid/how-to-connect-sync-staging-server",
       "redirect_document_id": false
     },
     {

articles/active-directory/hybrid/TOC.yml

@@ -248,8 +248,8 @@
       href: how-to-connect-health-alert-catalog.md
   - name: Manage Azure AD Connect Sync  
     items:
-    - name: Manage operational task
-      href: how-to-connect-sync-operations.md
+    - name: Staging server and disaster recovery
+      href: how-to-connect-sync-staging-server.md
     - name: Best practices for changing the default configuration
       href: how-to-connect-sync-best-practices-changing-default-configuration.md
     - name: Change the default configuration

articles/active-directory/hybrid/how-to-connect-install-automatic-upgrade.md

@@ -96,7 +96,7 @@ Here is a list of the most common messages you find. It does not list all, but t
 | UpgradeNotSupportedNonMsolAccount |The [AD DS Connector account](reference-connect-accounts-permissions.md#ad-ds-connector-account) is not the default MSOL_ account anymore. |
 | UpgradeNotSupportedNotConfiguredSignInMethod | When setting up AAD Connect, you chose *Do Not Configure* when selecting the sign-on method. | 
 | UpgradeNotSupportedPtaSignInMethod | You have selected Pass-through Authentication as the sign-in method. |
-| UpgradeNotSupportedStagingModeEnabled |The server is set to be in [staging mode](how-to-connect-sync-operations.md#staging-mode). |
+| UpgradeNotSupportedStagingModeEnabled |The server is set to be in [staging mode](how-to-connect-sync-staging-server.md). |
 | UpgradeNotSupportedUserWritebackEnabled |You have enabled the [user writeback](how-to-connect-preview.md#user-writeback) feature. |
 
 ## Next steps

articles/active-directory/hybrid/how-to-connect-install-custom.md

@@ -361,7 +361,7 @@ It is possible to setup a new sync server in parallel with staging mode. It is o
 
 While in staging mode, it is possible to make required changes to the sync engine and review what is about to be exported. When the configuration looks good, run the installation wizard again and disable staging mode. Data is now exported to Azure AD from this server. Make sure to disable the other server at the same time so only one server is actively exporting.
 
-For more information, see [Staging mode](how-to-connect-sync-operations.md#staging-mode).
+For more information, see [Staging mode](how-to-connect-sync-staging-server.md).
 
 ### Verify your federation configuration
 Azure AD Connect verifies the DNS settings for you when you click the Verify button.

articles/active-directory/hybrid/how-to-connect-install-roadmap.md

@@ -44,7 +44,7 @@ You can find the download for Azure AD Connect on [Microsoft Download Center](ht
 |After installation | [Verify the installation and assign licenses](how-to-connect-post-installation.md)|
 
 ### Learn more about Install Azure AD Connect
-You also want to prepare for [operational](how-to-connect-sync-operations.md) concerns. You might want to have a stand-by server so you easily can fail over if there is a [disaster](how-to-connect-sync-operations.md#disaster-recovery). If you plan to make frequent configuration changes, you should plan for a [staging mode](how-to-connect-sync-operations.md#staging-mode) server.
+You also want to prepare for [operational](how-to-connect-sync-operations.md) concerns. You might want to have a stand-by server so you easily can fail over if there is a [disaster](how-to-connect-sync-staging-server.md#disaster-recovery). If you plan to make frequent configuration changes, you should plan for a [staging mode](how-to-connect-sync-staging-server.md) server.
 
 |Topic |Link|  
 | --- | --- |

articles/active-directory/hybrid/how-to-connect-installation-wizard.md

@@ -68,7 +68,7 @@ When you select this option, all the directories in your configuration are liste
 ![Page with a list of all directories in the environment](./media/how-to-connect-installation-wizard/refreshschema.png)
 
 ## Configure staging mode
-This option allows you to enable and disable staging mode on the server. More information about staging mode and how it is used can be found in [Operations](how-to-connect-sync-operations.md#staging-mode).
+This option allows you to enable and disable staging mode on the server. More information about staging mode and how it is used can be found in [Operations](how-to-connect-sync-staging-server.md).
 
 The option shows if staging is currently enabled or disabled:  
 ![Option that is also showing the current state of staging mode](./media/how-to-connect-installation-wizard/stagingmodecurrentstate.png)

articles/active-directory/hybrid/how-to-connect-sync-feature-scheduler.md

@@ -51,7 +51,7 @@ If you see **The sync command or cmdlet is not available** when you run this cmd
 * **PurgeRunHistoryInterval**. The time operation logs should be kept. These logs can be reviewed in the synchronization service manager. The default is to keep these logs for 7 days.
 * **SyncCycleEnabled**. Indicates if the scheduler is running the import, sync, and export processes as part of its operation.
 * **MaintenanceEnabled**. Shows if the maintenance process is enabled. It updates the certificates/keys and purges the operations log.
-* **StagingModeEnabled**. Shows if [staging mode](how-to-connect-sync-operations.md#staging-mode) is enabled. If this setting is enabled, then it suppresses the exports from running but still run import and synchronization.
+* **StagingModeEnabled**. Shows if [staging mode](how-to-connect-sync-staging-server.md) is enabled. If this setting is enabled, then it suppresses the exports from running but still run import and synchronization.
 * **SchedulerSuspended**. Set by Connect during an upgrade to temporarily block the scheduler from running.
 
 You can change some of these settings with `Set-ADSyncScheduler`. The following parameters can be modified:

articles/active-directory/hybrid/how-to-connect-sync-operations.md renamed to articles/active-directory/hybrid/how-to-connect-sync-staging-server.md

@@ -6,21 +6,20 @@ documentationcenter: ''
 author: billmath
 manager: daveba
 editor: ''
-
 ms.assetid: b29c1790-37a3-470f-ab69-3cee824d220d
 ms.service: active-directory
 ms.devlang: na
 ms.topic: conceptual
 ms.tgt_pltfrm: na
 ms.workload: identity
-ms.date: 07/13/2017
+ms.date: 02/27/2018
 ms.subservice: hybrid
 ms.author: billmath
 
 ms.collection: M365-identity-device-management
 ---
-# Azure AD Connect sync: Operational tasks and consideration
-The objective of this topic is to describe operational tasks for Azure AD Connect sync.
+# Azure AD Connect: Staging server and disaster recovery
+With a server in staging mode, you can make changes to the configuration and preview the changes before you make the server active. It also allows you to run full import and full synchronization to verify that all changes are expected before you make these changes into your production environment.
 
 ## Staging mode
 Staging mode can be used for several scenarios, including:
@@ -29,8 +28,6 @@ Staging mode can be used for several scenarios, including:
 * Test and deploy new configuration changes.
 * Introduce a new server and decommission the old.
 
-With a server in staging mode, you can make changes to the configuration and preview the changes before you make the server active. It also allows you to run full import and full synchronization to verify that all changes are expected before you make these changes into your production environment.
-
 During installation, you can select the server to be in **staging mode**. This action makes the server active for import and synchronization, but it does not run any exports. A server in staging mode is not running password sync or password writeback, even if you selected these features during installation. When you disable staging mode, the server starts exporting, enables password sync, and enables password writeback.
 
 > [!NOTE]
@@ -55,7 +52,7 @@ To apply this method, follow these steps:
 
 #### Prepare
 1. Install Azure AD Connect, select **staging mode**, and unselect **start synchronization** on the last page in the installation wizard. This mode allows you to run the sync engine manually.
-   ![ReadyToConfigure](./media/how-to-connect-sync-operations/readytoconfigure.png)
+   ![ReadyToConfigure](./media/how-to-connect-sync-staging-server/readytoconfigure.png)
 2. Sign off/sign in and from the start menu select **Synchronization Service**.
 
 #### Configuration
@@ -92,7 +89,7 @@ The export.csv file contains all changes that are about to be exported. Each row
 #### Switch active server
 1. On the currently active server, either turn off the server (DirSync/FIM/Azure AD Sync) so it is not exporting to Azure AD or set it in staging mode (Azure AD Connect).
 2. Run the installation wizard on the server in **staging mode** and disable **staging mode**.
-   ![ReadyToConfigure](./media/how-to-connect-sync-operations/additionaltasks.png)
+   ![ReadyToConfigure](./media/how-to-connect-sync-staging-server/additionaltasks.png)
 
 ## Disaster recovery
 Part of the implementation design is to plan for what to do in case there is a disaster where you lose the sync server. There are different models to use and which one to use depends on several factors including:

articles/active-directory/hybrid/how-to-dirsync-upgrade-get-started.md

@@ -67,7 +67,7 @@ The following change cannot be upgraded. If you have this configuration, the upg
 
 ![Upgrade blocked](./media/how-to-dirsync-upgrade-get-started/analysisblocked.png)
 
-In those cases, the recommendation is to install a new Azure AD Connect server in [staging mode](how-to-connect-sync-operations.md#staging-mode) and verify the old DirSync and new Azure AD Connect configuration. Reapply any changes using custom configuration, as described in [Azure AD Connect Sync custom configuration](how-to-connect-sync-whatis.md).
+In those cases, the recommendation is to install a new Azure AD Connect server in [staging mode](how-to-connect-sync-staging-server.md) and verify the old DirSync and new Azure AD Connect configuration. Reapply any changes using custom configuration, as described in [Azure AD Connect Sync custom configuration](how-to-connect-sync-whatis.md).
 
 The passwords used by DirSync for the service accounts cannot be retrieved and are not migrated. These passwords are reset during the upgrade.
 
@@ -159,12 +159,12 @@ When you install Azure AD Connect on a new server, the assumption is that you wa
      These options can be seen on this screen:  
      ![Enter your Azure AD credentials](./media/how-to-dirsync-upgrade-get-started/advancedsettings.png)
 7. Click **Next**.
-8. On the **Ready to configure** page, leave the **Start the synchronization process as soon as the configuration completes** checked. The server is now in [staging mode](how-to-connect-sync-operations.md#staging-mode) so changes are not exported to Azure AD.
+8. On the **Ready to configure** page, leave the **Start the synchronization process as soon as the configuration completes** checked. The server is now in [staging mode](how-to-connect-sync-staging-server.md) so changes are not exported to Azure AD.
 9. Click **Install**.
 10. After the installation has completed, sign out and sign in again to Windows before you use Synchronization Service Manager, Synchronization Rule Editor, or try to make any other configuration changes.
 
 > [!NOTE]
-> Synchronization between Windows Server Active Directory and Azure Active Directory begins, but no changes are exported to Azure AD. Only one synchronization tool can be actively exporting changes at a time. This state is called [staging mode](how-to-connect-sync-operations.md#staging-mode).
+> Synchronization between Windows Server Active Directory and Azure Active Directory begins, but no changes are exported to Azure AD. Only one synchronization tool can be actively exporting changes at a time. This state is called [staging mode](how-to-connect-sync-staging-server.md).
 
 ### Verify that Azure AD Connect is ready to begin synchronization
 To verify that Azure AD Connect is ready to take over from DirSync, you need to open **Synchronization Service Manager** in the group **Azure AD Connect** from the start menu.
@@ -180,7 +180,7 @@ In the application, go to the **Operations** tab. On this tab, confirm that the
 
 Review the result from these operations and ensure there are no errors.
 
-If you want to see and inspect the changes that are about to be exported to Azure AD, then read how to verify the configuration under [staging mode](how-to-connect-sync-operations.md#staging-mode). Make required configuration changes until you do not see anything unexpected.
+If you want to see and inspect the changes that are about to be exported to Azure AD, then read how to verify the configuration under [staging mode](how-to-connect-sync-staging-server.md). Make required configuration changes until you do not see anything unexpected.
 
 You are ready to switch from DirSync to Azure AD when you have completed these steps and are happy with the result.
 

articles/active-directory/hybrid/how-to-upgrade-previous-version.md

@@ -58,7 +58,7 @@ The two servers can use different versions. For example, the active server that
 ![Staging server](./media/how-to-upgrade-previous-version/stagingserver1.png)
 
 > [!NOTE]
-> Some customers prefer to have three or four servers for this scenario. When the staging server is upgraded, you don't have a backup server for [disaster recovery](how-to-connect-sync-operations.md#disaster-recovery). With three or four servers, you can prepare one set of primary/standby servers with the new version, which ensures that there is always a staging server that's ready to take over.
+> Some customers prefer to have three or four servers for this scenario. When the staging server is upgraded, you don't have a backup server for [disaster recovery](how-to-connect-sync-staging-server.md#disaster-recovery). With three or four servers, you can prepare one set of primary/standby servers with the new version, which ensures that there is always a staging server that's ready to take over.
 
 These steps also work to move from Azure AD Sync or a solution with FIM + Azure AD Connector. These steps don't work for DirSync, but the same swing migration method (also called parallel deployment) with steps for DirSync is in [Upgrade Azure Active Directory sync (DirSync)](how-to-dirsync-upgrade-get-started.md).
 
@@ -67,8 +67,8 @@ These steps also work to move from Azure AD Sync or a solution with FIM + Azure
 2. If you've made a custom configuration and your staging server doesn't have it, follow the steps under [Move a custom configuration from the active server to the staging server](#move-a-custom-configuration-from-the-active-server-to-the-staging-server).
 3. If you're upgrading from an earlier release of Azure AD Connect, upgrade the staging server to the latest version. If you're moving from Azure AD Sync, then install Azure AD Connect on your staging server.
 4. Let the sync engine run full import and full synchronization on your staging server.
-5. Verify that the new configuration didn't cause any unexpected changes by using the steps under "Verify" in [Verify the configuration of a server](how-to-connect-sync-operations.md#verify-the-configuration-of-a-server). If something isn't as expected, correct it, run the import and sync, and verify the data until it looks good, by following the steps.
-6. Switch the staging server to be the active server. This is the final step "Switch active server" in [Verify the configuration of a server](how-to-connect-sync-operations.md#verify-the-configuration-of-a-server).
+5. Verify that the new configuration didn't cause any unexpected changes by using the steps under "Verify" in [Verify the configuration of a server](how-to-connect-sync-staging-server.md#verify-the-configuration-of-a-server). If something isn't as expected, correct it, run the import and sync, and verify the data until it looks good, by following the steps.
+6. Switch the staging server to be the active server. This is the final step "Switch active server" in [Verify the configuration of a server](how-to-connect-sync-staging-server.md#verify-the-configuration-of-a-server).
 7. If you're upgrading Azure AD Connect, upgrade the server that's now in staging mode to the latest release. Follow the same steps as before to get the data and configuration upgraded. If you upgraded from Azure AD Sync, you can now turn off and decommission your old server.
 
 ### Move a custom configuration from the active server to the staging server