Skip to content

Commit 3c5ffd0

Browse files
committed
tweaks
1 parent e6bd8b9 commit 3c5ffd0

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -111,7 +111,7 @@ You may need to perform a failover of the Sync Servers for several reasons, such
111111
- One currently active Azure AD Connect Sync Server
112112
- One staging Azure AD Connect Sync Server
113113

114-
#### Changing Currently Active Sync Server to Staging Mode
114+
#### Change currently Active Sync Server to staging mode
115115

116116
We need to ensure that only one Sync Server is syncing changes at any given time throughout this process. If the currently Active Sync Server is reachable you can perform the below steps to move it to Staging Mode. If it is not reachable, ensure that the server or VM does not regain access unexpectedly either by shutting down the server or isolating it from outbound connections and proceed to the steps on how to change the currently Staging Sync Server to Active Mode.
117117

@@ -148,7 +148,7 @@ From here, there should be no more Export jobs since the change and Full & Delta
148148
> [!div class="mx-imgBorder"]
149149
> ![Screenshot shows Sync Service console on the Active Azure AD Connect dialog box.](media/how-to-connect-sync-staging-server/active-server-sync-server-mgmr.png)
150150
151-
#### Changing Currently Staging Sync Server to Active Mode
151+
#### Change current Staging Sync server to active mode
152152

153153
At this point, all of our Azure AD Connect Sync Servers should be in Staging Mode and not exporting changes.
154154
We can now move our Staging Sync Server to Active mode and actively sync changes.

0 commit comments

Comments
 (0)