Forum Discussion
FSlogix Profile associating to wrong Azure Machine registration
Hello,
We have Citrix non persistent VDI setup with FSLogix profile management. We use MS Office only for Word and Excel - there is no Outlook or Teams setup. We have hybrid deployment with we do not sync Non persistent VDI OU to Azure. Machines register as users' devices when they log in to MS Office only.
During DR exercise we moved users from Production datacenter and DR datacenter Citrix Storefront. Machine name of these non-persistent windows 2019 VDIs on both ends have different names. The FSLogix profile from Prod was Robocopy to DR file share.
There are two issues
1- That when user Office token tries renewing it shows in Azure User logs that it was attempted using the old VDI machines name. The activation then fails with 62ubh error. To resolve we can remove the old machine's associated to the user's under the Azure profile and then remove Microsoft.AAD.BrokerPlugin_vnggnktrrj file in C:\%Userprofile%\AppData\Local\Packages. Have the user reboot and then reactivate office.
2- At that point after it takes two tries, it times out with CA0000 error, that device could not be registered- but user gets logged in to MS Office. The VDI from DR never registers in Azure under the user's name under Devices. No issue DSREGCMD /Status and machine has SCP access. We are not resetting the Profiles because it takes time copying their setup preferences.
6 Replies
Keep in mind that profile copying may carry stale registration data; a fresh profile or a way to reset device registration info may be necessary in some cases.
Hello, thanks for your response. Any recommendation around how to achieve the following "a fresh profile or reset device registration "
Thanks.
I do have identity roaming enabled in FSlogix. Shouldn't that help?
Thank you for your responses.
To get clarity on your comments and to give more explanation on my end: -
I do have 'Identity roaming' enabled in FSlogix, which I think should counter this issue of different machine names - or am I wrong about that? Isn't this mechanism (roaming identity) setup to support Non-Persistent VDI sessions and launching a new machine every time, randomly from the pool?
Added Information - All the machines in each Datacenter are spun from a single base image though with different names in each end. There were no issues with Mutiple Office activation until the users were moved from one datacenter to another.
Office Activation and device registration are linked to the Azure AD device registration process, which can be impacted by cached info, machine name changes, or profile data.
Changing machine names can cause Office and Azure AD to see these as new devices, but if the old registration persists or the registration isn't cleaned properly, conflicts occur.
