You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,9 +25,11 @@ Prerequisites:
25
25
26
26
How to use the tool:
27
27
28
-
* Download the latest release AzureADConnectSyncDocumenter.zip from the [releases](https://github.com/Microsoft/AADConnectConfigDocumenter/releases) tab under the Code tab tab, UNBLOCK the downloaded zip file and extract the zip file to an empty local folder on a machine which has .NET Framework 4.5 installed.
28
+
* Download the latest release AzureADConnectSyncDocumenter.zip from the [**releases**](https://github.com/Microsoft/AADConnectConfigDocumenter/releases) tab under the Code tab tab.
29
+
* UNBLOCK the downloaded zip file using the **Right Click** | **Properties** menu and then checking the **Unblock** check-box from the **General** tab.
30
+
* Extract the zip file to an empty local folder on a machine which has .NET Framework 4.5 installed.
29
31
* This will extract the Documenter application binaries along with the sample data files for "Contoso".
30
-
* Make sure that the tool runs by double-clicking on the cmd file AzureADConnectSyncDocumenter.cmd.
32
+
* Make sure that the tool runs by double-clicking on the cmd file AzureADConnectSyncDocumenter-Contoso.cmd.
31
33
* Export the Server Configuration of your pilot / test Azure AD Connect sync server by running Get-ADSyncServerConfiguration cmdlet defined in ADSync module shipped with Azure AD Connect.
32
34
33
35
```PowerShell
@@ -38,14 +40,14 @@ How to use the tool:
38
40
```
39
41
40
42
* Copy the configuration export files produced in the previous step to a folder under the "Data" directory of the Documenter tool.
41
-
* e.g. the "Pilot" configuration files for the customer "Contoso" are provided as a sample under the "Data\Contoso\Pilot" folder.
43
+
* e.g. the "Pilot" configuration files for the customer "Contoso" are provided as a sample under the "Data\Contoso\Pilot" folder. This is the folder where the files of the ***to be*** or ***end-state*** configuration are located. So, for example, in a swing migration project the "Pilot" or "Target" configuration will be the configuration of the "old" server, since the goal is to build a new server with the configuration as close to the old server as possible.
42
44
* If you want to document the changes from a specific baseline, export the server configuration of your baseline / production Azure AD Connect server and copy the output to a folder under the Documenter "Data" directory.
43
-
* e.g. the "Production" configuration files for the customer "Contoso" are provided as a sample under the "Data\Contoso\Production" folder.
44
-
*Edit AzureADConnectSyncDocumenter.cmd for the values of "Pilot" and "Production" directories.
45
+
* e.g. the "Production" configuration files for the customer "Contoso" are provided as a sample under the "Data\Contoso\Production" folder. This is the folder where the files of the ***as-is*** or ***baseline*** configuration are located.
46
+
*Make a copy of AzureADConnectSyncDocumenter-Contoso.cmd with a name appropriate for your enviroment (say AzureADConnectSyncDocumenter-Fabrikam.cmd) and edit your copy for the values of "Pilot" and "Production" directories.
45
47
* If you don't have a baseline / production config, specify the same path as the "Pilot" config.
46
-
* Run the updated batch file. Upon successful execution, the generated report will be found in the Documenter "Report" folder.
48
+
* Run your updated updated batch file. Upon successful execution, the generated report will be found in the Documenter "Report" folder.
47
49
48
-
**!!NOTE!!**_**If the names of the connector(s) do(es) not exactly match between the supplied "Pilot" and "Production" configuration files, then before running the tool, "prep" the exported config files by manually editing the xml files located in the "Connectors" folder so that the name of the connector(s) match. The name of the connector is located inside the "name" element at the start of the content.**_
50
+
**!!NOTE!!**_**If the name(s) of the connector(s) do(es) not exactly match between the supplied "Pilot" and "Production" configuration files, then before running the tool, "prep" the exported config files by manually editing the xml files located in the "Connectors" folder so that the name of the connector(s) match. The name of the connector is located inside the "name" element at the start of the content.**_
49
51
50
52
A sample report generated by the tool can be found listed in the [Wiki](https://github.com/Microsoft/AADConnectConfigDocumenter/wiki/Sample-Report) section.
ECHO It seems you may have downloaded the source code instead of a release package. Please download the latest release from https://github.com/Microsoft/AADConnectConfigDocumenter/releases...
0 commit comments