<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
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D50Z00008G7UzFSAVOkta Classic EngineOkta Integration NetworkAnswered2024-04-30T09:18:25.000Z2018-04-05T21:10:26.000Z2018-07-27T14:38:42.000Z

PeterC.85366 (Customer) asked a question.

April 5, 2018 at 9:10 PM
OneDrive Silent Configuration, ADAL and Okta.
We're attempting to use OneDrive for Buisness silent configuration to facilitate folder redirection to One Drive. I've enabled correct GPO and pushed down the ADAL registry settings and now the test machine can't login. OneDrive.exe crashes and then prompts for login agian. Has anybody else tried this?
  • 4 answers
  • 2.39K views

  • adam.lowe1.4386711186435444E12 (Okta, Inc.)

    That issue is quite curious, and I'm uncertain if this is directly related to Okta causing the behavior without further troubleshoting.  I'd recommend breaking this into smaller components and testing to see if the source of the issue can be further isolated.

     

    I understand this configuration is being pushed via GPO.  Can you try manually applying this configuration without GPO and confirm this works?  If so, then it's likely an issue with GPO.  If not, then we can rule out GPO as the source of the issue.

     

    When OneDrive crashes, is it occurring immediately when trying to authenticate with Okta, or a different event or action that prompts the crash?  If you were to try this configuration with OneDrive without a federated account, does the issue persist?  If so, then the issue is not likely with Okta/authentication.  If it does not, then it may be an issue with OneDrive authenticating via Okta.

     

    As another step that may give more insight, can you also check Okta's System Log for authentication requests at the time of the crash.  This may help determine if the OneDrive client is even reaching a point where it makes an authentication request to Okta before crashing.
    Expand Post

  • j5v7c (j5v7c)

    Hello,

     

    Thanks for posting your inquiry in Okta Community Portal.

     

    If you receive a great answer to your question(s), please help readers find it by marking it the best answer. Hover over the answer and click "Best Answer." 

     

    Thank you,

     

    Dylann Fezeu

    Okta Help Center Team
    Expand Post

  • PeterC.85366 (Customer)

    Adam, I've tried both manually and with GPO and get the same result. I've also made sure that OneDrive is the latest client software etc. 

     

    OneDrive never automatically signs in but with the GPO pushed and when I try to manually sign in I get stuck a screen that says "Please finish signing in with your work or school account." The appcrash error message in the event log mentions ADAL.dll.  
    1.  Faulting application name: OneDrive.exe, version: 18.44.301.6, time stamp: 0x5ab572b3 Faulting module name: ADAL.dll, version: 1.0.2110.526, time stamp: 0x5927ecb7 Exception code: 0xc0000005 Fault offset: 0x0002529a Faulting process id: 0x255c Faulting application start time: 0x01d3d0d9fd151347 Faulting application path: C:\Users\cookp\AppData\Local\Microsoft\OneDrive\OneDrive.exe Faulting module path: C:\Users\cookp\AppData\Local\Microsoft\OneDrive\18.044.0301.0006\ADAL.dll Report Id: fd43e982-d076-4d10-b424-d9ea57a548ed Faulting package full name:  Faulting package-relative application ID:
     I didn't see anything in the Okta Log regarding the sign in either. 

     

    Office 365 support did not seem interested in helping as soon as they heard I was using Okta. 

    Expand Post

  • PeterC.85366 (Customer)

    Follow up on this. It turns out I was using a faulty test computer and that's why the application was crashing. On the new test computer I can manually log in but auto logon still does not function. It looks like the computer must be registered in Azure AD in order for this to happen.
This question is closed.
Loading
OneDrive Silent Configuration, ADAL and Okta.