gyp8v (gyp8v) asked a question.
Instance locked out after AD move to new server with same network settings
The team managing AD servers has moved them to a new virtual machine with exact same IP information without letting me know.
The only thing that changed is the machine name.
Since then, the Okta instance can't be logged in anymore. The AD agent is still running on a dedicated VM and didn't lose connectivity or cloud.
Could it be that just the machine name change would cause the AD agent to stop authenticating the environment?
Hi @gyp8v (gyp8v),
Thank you for posting on the Okta community page!
I would recommend to try and re-install the AD agent on the VM since this might re-make the connection between Okta and your Active Directory. I have provided bellow a documentation in which it explains how to reinstall the AD agent:
I hope the above information is helpful!
Unluckily I could not regain access to the instance and support didn't want to reset it so I could reconfigure it. I suppose I will need to switch to another IAM product.
Hi Flaviu,
Thanks for the advice. However, I can only download the agent if I (re-)gain access to the instance.
Alex