- last edited on
I'm working on a new Workplace configuration based on Windows 10, Azure AD and Intune. Users should be able to Join their Windows 10 device to Azure AD and auto-enrolled to Intune. So far so good. We still are in transition migrating our date to SharePoint, so users should have access to the data shares, unfortunately, the first time after the users logs in (after joining Azure AD during oobe wizard), they have no access to the on-premise shares. However, after the second logon, the users has access to the shares. I guess there is no kerberos ticket to authenticate againt the on-premise AD after first time log on. I wondering if this is normal behaviour, or should this normall worked the first time?
01-04-2019 06:50 AM
01-04-2019 06:56 AM
PIN didn't worked at all. I also forced the users to use password. I think you should configure Hybrid Windows Hello before you can use PIN to authenticate with your local AD. This is only working with a Windows 2016 DC.
01-04-2019 07:03 AM
01-04-2019 07:06 AM
03-05-2019 09:49 PM
@Chris Webb we also had to spend some time to get it to work but we got it working now. There were some caveats that is not clearly mentioned in the articles. Are you trying to get it to work using key based or certificate based?