at end of initial account creation \ azure AD authentication, azure account not recognized for Remote Assist?

(1) Share

Report

Posted on by Barry Cavanaugh

When I provision a new hololens2 and give it to a user - we proceed through the initial sign in on the device...the user successfully establishes a log in to my company's authentication scheme that also successfully integrates with AAD. The user establishes IRIS scanning OK and PIN OK...wifi connection is good, etc.

...but, immediately proceeding to the last step, wearing the hololens2, when the user then attempts to use Remote Assist, the user's account is applied to remote assist but the error says that there is a problem and to "try again"

...but if we walk away and try hours later (usually the next day), we find that remote assist then DOES accept the account and remote assist works great.

In all cases, we make sure ahead-of-time that a remote assistance license has been assigned to the user.

is there a known delay in syncing accounts for enablement of remote assist?

Thanks

Barry

I have the same question (0)