<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
0D54z00008zy0suCAAOkta Classic EngineAdministrationAnswered2024-01-30T19:11:01.000Z2023-03-30T00:17:42.000Z2023-07-05T15:22:06.000Z
  • HI @OktaA.20132 (Customer)​ , Thank you for reaching out to the Okta Community!

     

    Please review AD agent prerequisites and Auto-Update feature limitations. 

    https://help.okta.com/en-us/Content/Topics/Directory/ad-agent-prerequisites.htm

     

    https://help.okta.com/en-us/Content/Topics/Directory/agent-auto-update-limitations.htm

     

    Also try running a query in the system logs for system.agent.auto_update to check for any additional details pertaining to the failure. 

     

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

    --------------------------------

    Community members help others by clicking Like or Select as Best on responses. Try it today.

    Expand Post
  • HarryL.92824 (Customer)

    Hi, we got this error in our log file:

    -----

     

    2023/07/05 17:00:44.366+02:00 Info -- BETTERBEAADC01(13) -- Starting processing of AUTO_UPDATE action rpc::app.active_directory.agent.reply.ok9-jobecs02b.aew1-ok9.internal//1688569257110//ZKWEv3t3cZOLUGckW_zl7QAADCw:3cf2c0ee-4927-4cf5-91cf-ef788241b1e7:.

    2023/07/05 17:00:44.397+02:00 Error -- BETTERBEAADC01(13) -- Auto-update health check failed: Unexpected error

    2023/07/05 17:00:44.397+02:00 Info -- BETTERBEAADC01 at System.DirectoryServices.AccountManagement.UserPrincipal.get_Current()

      at Okta.Agent.Installation.AutoUpdate.AutoUpdateHealthChecker.Check()

    System.DirectoryServices.AccountManagement.NoMatchingPrincipalException received with message The User object for the current user could not be found. You may not have access to it. Source=System.DirectoryServices.AccountManagement InnerException=.

    2023/07/05 17:00:44.397+02:00 Info -- BETTERBEAADC01(13) -- Processing AUTO_UPDATE action (id=rpc::app.active_directory.agent.reply.ok9-jobecs02b.aew1-ok9.internal//1688569257110//ZKWEv3t3cZOLUGckW_zl7QAADCw:3cf2c0ee-4927-4cf5-91cf-ef788241b1e7:) finished, (executionTime=00:00:00.0267133)

    2023/07/05 17:00:44.397+02:00 Info -- BETTERBEAADC01(13) -- Sending action result (FAILURE) for action AUTO_UPDATE (id=rpc::app.active_directory.agent.reply.ok9-jobecs02b.aew1-ok9.internal//1688569257110//ZKWEv3t3cZOLUGckW_zl7QAADCw:3cf2c0ee-4927-4cf5-91cf-ef788241b1e7:)

    Expand Post
    • Hi @HarryL.92824 (Customer)​ , Thank you for reaching out to the Okta Community!

       

      From what I've been able to find, this was a known bug which affected some Okta tenants unable to auto-update from AD Agent version 3.13 and beyond. This was addressed in the new Okta AD Version 3.15.0. I have attached the release notes below:

      https://help.okta.com/en-us/Content/Topics/Settings/Version_Histories/Ver_History_AD_Agent.htm

      'Bug fixes. Active Directory (AD) agent auto-update health check caused auto-update to fail when upgrading from version 3.13.0 to 3.14.0.'

       

      Therefore, unfortunately, you will have to manually upgrade to 3.15.0 and the auto-update issue will be gone for updating from 3.15.0 to the future versions.

       

      If you continue to experience issues, please open a case to work with one our Support Engineers.

       

       

      If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

       

      Hope my answer helps! 

      --------------------------------

      Community members help others by clicking Like or Select as Best on responses. Try it today.

      Expand Post
This question is closed.
Loading
Unable to update okta ad agent via auto-update from okta