Closed A9G-Data-Droid closed 3 years ago
@A9G-Data-Droid Thanks for your feedback! We will investigate and update as appropriate.
Adding additional information: Not only does the change for FIPS compliance not work, but the documentation is also incorrect. The miiserver.exe.config is not stored relative to %programfiles%, it is stored relative to the data storage directory chosen during AD Connect installation.
Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. Though the scope of our feedback channel here on GitHub covers specific documentation fixes, we can help redirect you to the right support channel to get an answer to your question: [reference to alternative product/service or community endpoint]. Because this issue does not relate to documentation, we are closing this issue. #please-close
The documentation is wrong and needs to be edited. The whole section "Password hash synchronization and FIPS" needs to be edited or removed. It's both technically wrong and doesn't work.
You also failed to fill in the critical detail of your canned message:
redirect you to the right support channel to get an answer to your question: [reference to alternative product/service or community endpoint].
That's where you are supposed to put something helpful.
We are unable to run Azure-AD connect with FIPS mode on. The workaround cited on this page isn't working. Sync still fails until FIPS mode is disabled on the system. This is an unacceptable solution.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.