New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please consider rewriting these instructions... #32
Comments
HI @knowlesy14 , please submit a pull request with improved instructions and I'll review the updates. Thanks! |
Agreed. I've read this about 10 times and having difficulty with it. And I would like to contribute to a re-write. But I don't fully understand the purpose of this tool. |
Perhaps change out "Pilot / Test" and "Target / Pilot" with "New". |
Here's what I have so far: • Export the Server Configuration of your new or existing Azure AD Connect server by running Get-ADSyncServerConfiguration cmdlet defined in ADSync module shipped with Azure AD Connect. |
• Go to C:\temp\AzureADConnectSyncDocumenter and create a new folder next to Contoso with your company name. |
So then I did some word swaps, but it's kind of confusing at this point. • Copy the configuration export files from the Output folder to a folder under the "Data" directory of the Documenter tool. |
Thanks for taking the time to create this tool! |
Your usecase is simple to explain. The tool's executable expects two sets of input configuration files to be provided in it's "Data" folder, let's call them A and B. In your case B is same as A. So on the commandline you'll be running is: AzureADConnectSyncDocumenterCmd.exe "A" "A". That is all. Again, if your config files are placed in the folder "FABRIKAM\07JUL2021" then you'd run: AzureADConnectSyncDocumenterCmd.exe "FABRIKAM\07JUL2021" "FABRIKAM\07JUL2021".. It's only when you have two different sets of config files and would be interested to understand how the changes are reported and in the PowerShell script that it also produces for recreating sync rules that it becomes super important what you call as A and what you call as B and it can get quite confusing which is A and which is B based on what you are exactly trying to do - promote the change from test to prod, staging to prod, prod to staging, swing migration, etc.. The terminology for naming A=Pilot/Target and B=Production/Baseline is carried over from FIM/MIM world. |
Hi, I couldn't use it as it's confusing. Could you please simplify how to execute the report after export the config files? Maybe a screenshot of it would fix all the confusion. |
After much thought, I've just documented the instructions separately for four different main use cases. Hopefully this is clearer and helpful. |
Would you please provide a link to the documentation instructions for the 4 different main use cases? I don't see it. |
Hi @texaskat, updates were on the wiki tab homepage, but now visible on the project homepage as well. |
Please consider rewriting these instructions. I found them quite hard to follow.
The text was updated successfully, but these errors were encountered: