<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
0D50Z00008G7UydSAFOkta Classic EngineLifecycle ManagementAnswered2024-04-18T09:06:20.000Z2017-07-20T13:38:50.000Z2019-08-07T21:41:53.000Z
Error provisioning active_directory user: A device attached to the system is not functioning.
Hello,

 

I have a Okta group that is being pushed to our AD isntance via the "Push Groups" section. I have a script that auto creates new users and pushes them to Okta via the API, then Okta pushes the new users to AD. For some reason I am now getting this error (Error provisioning active_directory user: A device attached to the system is not functioning) when trying to push the user. Any idea on why this is? AD agents are up and running, I can push the group sucessfully but can't push a user.

 

Thanks!

  • Sam Johnson (Customer)

    Turns out that error will show up when you try and push a samAccountName that is more than 20 characters long.
  • y36bk (y36bk)

    I thought the same thing, but the error moved from "Application assignments encountered errors" to "Profile push updates encountered errors" after I changed the SAM Name to 20 characters or smaller.
  • Sam Johnson (Customer)

    That's weird. Something else is happening for you then. Once I put the samAccountName down under 20 characters it went right through.
  • um0tn (um0tn)

    Is there any resolution to this? I'm having the same issue with 3 users. We edited the SAMAccountname to be shorter than 20 characters, retried the push, and the issue was moved from "Application assignments encountered errors" to "Profile push updates encountered errors".

This question is closed.
Loading
Error provisioning active_directory user: A device attached to the system is not functioning.