I have a client who is experiencing an issue where...
# microsoft-365
n
I have a client who is experiencing an issue where users can't sign on to Office 365 applications on Windows 11 Multi-User OS. They receive the error message below the first time they click on an Office 365 application. However, it works fine the second time. I ran
dsregcmd /status
, and both
AzureADJoined
and
AzureADprt
are set to "Yes". They are using FSLogix, and Office activation is enabled. I'm not sure what the issue is. Has anyone else encountered this?
d
This happens for us when Office gets updated. Clearing out the path "AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy" before the application launches has improved the situation, but not entirely eliminated it. Some users still get an error, but a different one, but not all. It isn't totally consistent. I'm sure there is some set of authentication tokens that can be cleared, but I haven't been able to figure it all out.
a
Check your Entra ID sign in logs to see if there’s any pointers
j
Make sure the image is removed from Entra ID as part of a sealing process and also make sure the Workplace Join is modified for on startup along with on login. Check the Azure AD Connect and Zero machine settings of my site, here. https://www.jeffriechers.com/wiki/azuread-prt-with-fas-certificates/
n
thanks guys
@Jeff Riechers - you mean this -
👍 1
@Aaron Parker the client doesn't have access to the Entra ID sign-in logs but they access their own sign in logs when they go to users and they are not any error messsages there..is that the same thing as the entra ID logs?
no luck fixing this issue. microsoft took more logs today...let me know if you have anymore suggestions.
j
Hi newbie1998, we are facing the same issues. We suspect the server is losing the ability to encrypt or decrypt keys. At the moment the user gets the error do you see a KeySignTest: Failed for dsregcmd /status ?
j
Is there any chance you are blocking http access to the internet? I ran into an issue today with huge delays on certain apps, and it ended up being Certificate Signing check to digicert and other external entitites.
j
Hi Jeff, we are not blocking outgoing traffic on port 80 or 443. BTW we do not have any sign-in logs about compliant device or similar. But we do experience the error 1001. FYI I just raised 2 tickets, 1 for Office 365 apps and 1 for Windows Server 2019.
Ah, seems our error is just a bit different.
@Joost Sannen - no i don't see KeySignTest: Failed when i run dsregcmd /status
i don't get it should the non-persistent VDA OU be excluded from AD connect synchronization or included? i keep seeing different recommendation from the various articles. #CMNTV99B3 #CK6RVLZ8S
r
Sync the OU the VDAs are in. That has to happen or it will sit in an initializing state. It does a two stage check
n
@Ray Davis - thank you.
👍 1