Edge Browser and FSLogix Profile Container Enterprise Sync problem

Alberto Pérez Pastor 1 Reputation point
2022-12-23T19:12:32.737+00:00

We cannot make work Edge sync with AAD accounts on RDSH 2019 with FSLOGIX containers.

The first time a user login on the server it works fine but any subsequent login leaves Edge in "no sync" state. The only solution is to logoff on the edge profile and login again. No matter if we connect the user to the very same server he login in the first place. We've been searching the internet for days with no luck.

If we exclude the user and connect several times to the same server it works always fine.

Could anyone help me?

Summary
Transport State Disabled
Disable Reasons Waiting for sync url
Sync Feature Enabled false
Setup In Progress false
Auth Error OK since browser startup
Sync Account Type AAD
Version Info
Client Version Microsoft Edge Windows 108.0.1462.54 (c2998c8c661724d797c22f48cf555a2bef5029ee)
Environment Info
Server URL
Server Environment no_env-no_ver
Fetch Result AUTH_FAILURE
Fetch Message EDGE_AUTH_ERROR: 6, 2, 0
Identity
Sync Client ID Uninitialized
Invalidator Client ID Uninitialized
Username
Sync Consent true
Credentials
Requested Token 2022-12-23 20:01:54 +01
Received Token Response 2022-12-23 20:01:54 +01
Last Token Request Result OK
Has Token false
Next Token Request 2022-12-23 20:09:46 +01
Last Token Error EDGE_AUTH_ERROR: 6, 2, 0
Credentials for Key
Requested Token 2022-12-23 20:01:17 +01
Received Token Response 2022-12-23 20:01:19 +01
Last Token Request Result OK
Has Token false
Next Token Request 2022-12-23 20:08:54 +01
Last Token Error EDGE_AUTH_ERROR: 6, 2, 0
MSA Account Key Status
Download Key Result Uninitialized
Net Error Code Uninitialized
HTTP Response Code Uninitialized
Process Key Result Uninitialized
Set Key Result Uninitialized
Fetched Key Count 0
AAD Account Key Status
Pack/Unpack Key Result Uninitialized
Last MIP Result Uninitialized
Last Key Status Uninitialized
New Key State Uninitialized
Key Commit Response Uninitialized
Set Key Result Uninitialized
Packed/Unpacked Key Count 0
Local State
Server Connection not attempted
Last Synced Never
Sync First-Time Setup Complete true
Sync Cycle Ongoing false
Local Sync Backend Enabled false
Local Backend Path Uninitialized
Seen FRE Sync Consent false
Confirmed FRE Sync Consent false
Network
Throttled or Backoff false
Retry Time Uninitialized
Notifications Enabled false
Encryption
Explicit Passphrase false
Passphrase Required false
Cryptographer Ready To Encrypt false
Cryptographer Has Pending Keys false
Encrypted Types Uninitialized
Has Keystore Key false
Next Key Request Time Uninitialized
Keystore Migration Time Uninitialized
Passphrase Type Uninitialized
Explicit passphrase Time Uninitialized
Trusted Vault Migration Time Uninitialized
Trusted Vault Version/Epoch 0
Status from Last Completed Session
Sync Source Uninitialized
GetKey Step Result Uninitialized
Download Step Result Uninitialized
Commit Step Result Uninitialized
Running Totals
Notifications Received 0
Updates Downloaded 0
Tombstone Updates 0
Reflected Updates 0
Successful Commits 0
Conflicts Resolved: Client Wins 0
Conflicts Resolved: Server Wins 0
Transient Counters (this cycle)
Server Conflicts 0
Committed Items 0
Transient Counters (last cycle of last completed session)
Updates Downloaded 0
Committed Count 0

Microsoft Edge
Microsoft Edge
A Microsoft cross-platform web browser that provides privacy, learning, and accessibility tools.
2,223 questions
FSLogix
FSLogix
A set of solutions that enhance, enable, and simplify non-persistent Windows computing environments and may also be used to create more portable computing sessions when using physical devices.
472 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Yu Zhou-MSFT 12,936 Reputation points Microsoft Vendor
    2022-12-26T07:14:51.72+00:00

    Hi @Alberto Pérez Pastor

    From the edge://sync-internals information you provide, I think Last Token Error EDGE_AUTH_ERROR: 6, 2, 0 is the main issue. From the official doc, it's an identity issue and you need to sign into the browser with a valid account. So in this situation, you need to sign into Edge profile again to fix the issue.


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Regards,
    Yu Zhou

    0 comments No comments

  2. Alberto Pérez 1 Reputation point
    2022-12-26T08:29:02.513+00:00

    The credentials used on the previous desktop session were correct. It seams to be something related to WAM and FSLOGIX profiles.

    We had to force Edge to use Oneauth and disable WAM. After that, it works on any server part of the collection without any issue but that is a workaround because we cannot use WAM.

    It also happened on Outlook 2019 client. It asked for credentials on any new Desktop session and the solution was to disable WAM and enable ADAL.