<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D51Y00007UlMALSA3Okta Classic EngineUniversal DirectoryAnswered2024-04-16T11:06:52.000Z2020-01-06T22:50:05.000Z2020-01-08T20:26:27.000Z

r6xx3 (r6xx3) asked a question.

How to handle local Windows machines after moving to UD

When moving away from an AD setup, what is the best way to ensure local Windows machines being used are forcing password changes at the same time as UD / Okta? I know a local security policy can be set seperately on the Windows machine but that makes me concerned for the potential of more frequent password changes. It also implies to me that perhaps a user would change their UD password to one thing and a next time their local machine prompts them to change it to something else. How does this work, what is best practice??


  • OktaU.83617 (Florida Cancer Specialists)

    I'm gonna take a stab here and say this isn't going to work well or at all as Windows machines globally will only obey Active Directory Domain GPOs. Managing or enforcing Windows machine policies using Okta isn't something Okta is can do. Maybe eventually but the focus now is identity.

    Selected as Best
  • OktaU.83617 (Florida Cancer Specialists)

    I'm gonna take a stab here and say this isn't going to work well or at all as Windows machines globally will only obey Active Directory Domain GPOs. Managing or enforcing Windows machine policies using Okta isn't something Okta is can do. Maybe eventually but the focus now is identity.

    Selected as Best
This question is closed.
Loading
How to handle local Windows machines after moving to UD