Outlook 365 app error 1001 on RDS environment ( FSLogix)

Anonymous
2023-07-07T08:25:49+00:00

Hello,

We encounter an issue with M365 apps (Outlook, Work, Excel) on a specific environment ( Remote Desktop Service)

Sometime, when an user open his application (Outlook for instance) on a RDS, an authentification pop and ask for credentials. If the user enter his credentials, he encounter a 1001 error.

« We encountered an issue [1001] »

https://learn-attachment.microsoft.com/api/attachments/5a947921-955a-4688-ad93-acc305bf77c6?platform=QnA

We already try some step to resolve the issue that help in some case but not all the case, and not defintely for a same user ( Issue occur again) :

  • Clear folder C:\Users*yourusername*\AppData\Local\Microsoft\OneAuth and  C:\Users*yourusername*\AppData\Local\Microsoft\IdentityCache
  • Move the user from 1 TSE server to an other TSE)e
  • Clear FSlogix User profil ( The specific one link to FSLogix Office 365 Container technology )

The main issue is that the error can occur again few day laterfor the same user.

We also generate some log from M365 apps client during the signin process with this link to help : https://learn.microsoft.com/en-us/office/troubleshoot/diagnostic-logs/how-to-enable-office-365-proplus-uls-logging

In the log I find the reference to the 1001 error but the log is a bit complex to understand or analyse.

0xa3e4	Microsoft Outlook	Identity Authentication Client	48cmb	Monitorable	OneAuth log {"Message": "[MSAL:0004]\tERROR  \tErrorInternalImpl:134\tCreated an error: 58tm1, StatusInternal::Unexpected, InternalEvent::None, Error Code 2147942403, Context '(pii)'", "IsError": true}	

07/07/2023 09:04:21.440	OUTLOOK (0x8b30)	0xa3e4	Microsoft Outlook	Identity Authentication Client	48cmb	Monitorable	OneAuth log {"Message": "[OneAuth:Error:58tm1:db6d7d6e-a557-4465-a968-a874c5e456e5] (Code:1001) An unexpected error occurred.", "IsError": true}	

07/07/2023 09:04:21.440	OUTLOOK (0x8b30)	0xa3e4	Microsoft Outlook	Identity Authentication Client	48cmb	Monitorable	OneAuth log {"Message": "[OneAuth:Error:9vdpp:db6d7d6e-a557-4465-a968-a874c5e456e5] Unexpected error code: 1001", "IsError": true}

Environment :

  • Microsoft FSLogix version : 2.9.7654.46150
  • Office version : version 2305 build 16501.20228
  • OS version : Windows Server 2019 Standard 1809 build 17763.4499
Outlook | Windows | Classic Outlook for Windows | For home

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

278 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-07-10T03:06:02+00:00

    We don't use FSLogix, but do have roaming profiles on our RDS 2019. That said this has been our configuration for some time and its never been an issue before. Microsoft have obviously changed something!

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  2. Anonymous
    2023-11-08T15:19:34+00:00

    I haven't posted on this for a few weeks now and wanted to give a quick update. Unfortunately, this is likely not going to help many but our client was so frustrated with the situation, we had to do something drastic and migrate everyone off of FSLogix and back onto roaming profiles. Combined with all our other implemented fixes and moving to roaming profiles, the issue is gone.

    However, part of me feels we put in an adequate workaround beforehand, but it was one of those situations where the client was fed up with testing and wouldn't let us continue. From what I saw, I think we did figure it out, but it was too late. I wish I had more details / testing under my belt, but here's the list of things we did.

    1. Computer GPO to deploy reg key to block AAD Workplace Join

    HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin; BlockAADWorkplaceJoin DWORD = 1

    HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin; AutoWorkplaceJoin DWORD = 0

    1. Microsoft 365 Apps for Business EN-US (x86) = 16.0.16827.20166
    2. FSLogix version BEFORE uninstalling = 2.9.8612.60056
    3. Computer GPO to block and hide Office updates

    Computer Configuration\Policies\Administrative Templates\Microsoft Office 2016\Updates

    Enable automatic updates = Disabled

    Hide option to enable or disable updates = Enabled

    Hide update notifications = Enabled

    1. User and Computer GPO to deploy reg key to alter the behavior for a federated user account so that the password is saved in Credential Manager (not sure if this did much honestly, but it was a live policy we added somewhere along the way).

    Computer + User Configuration\Preferences\Windows Settings\Registry

    HKCU\Software\Microsoft\Office\16.0\Common\Identity; NoDomainUser = 1

    1. FSLogix RoamIdentity = Enabled
    2. Users that were problematic before we made the above change, we scripted the removal of the following folders at next login until they were all purged. Once these were removed, the next login, 1001s were gone.

    C:\users$user\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy

    C:\users$user\AppData\Local\Microsoft\IdentityCache

    C:\users$user\AppData\Local\OneAuth

    A few other notes... with all the above changes we made, during our troubleshooting, we DID downgrade Office and FSLogix to a version another one of our clients was using with no issues, and it still didn't fix things. In regards to downgrading Office, it actually made things worse because instead of being prompted to log in every single time they open Office, it wouldn't prompt at all, but it would also consider their login not working, so users were completely locked out when we did this. I don't recall the versions without digging through months of tickets and emails. We also tried Office 2019 and it also did not work.

    Hope this helps. I'm moving on from this issue, it's been close to 6 weeks of pain, stress, and frustration, and I don't have it in me anymore to think about this. GG Microsoft. Thanks everyone who helped along the way.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2023-10-09T17:01:27+00:00

    Our 1001 errors stem from Workplace Join enabled on our VDIs and we should not have. We have been getting 1001 errors pretty consistently for a little over a month now. After this implementation, they have stopped and have so for approx 2 weeks. Here's what we noticed and what we did.

    Our environment uses multi-session servers. Server 2019.
    Some clients use profile containers, some use Citrix Profile Management. Both were having 1001 errors.

    Because we had workplace join enabled in our non-persistent environment, every time someone authenticated and workplace joined, a duplicate device entry was created with the Hostnames of all our non-persistent VDIs. I saw this in Microsoft Entra, under devices. We had hundreds of Stale Devices, all dupes of our VDI hostnames. And hundreds of unmanaged devices in the same state. I removed all of those.

    This article here clued me in to that and also the potential problems it may cause.

    https://learn.microsoft.com/en-us/azure/active-directory/devices/howto-device-identity-virtual-desktop-infrastructure 

    Quotation from the article:

    "Failure to manage stale devices can lead to pressure increase on your tenant quota usage consumption and potential risk of service interruption, if you run out of tenant quota. You should follow the guidance documented below when deploying non persistent VDI environments to avoid this situation."

    Also the registry entry it states to ensure that is set:

    "When using non-persistent VDI, if you want to prevent adding a work or school account, ensure the following registry key is set:
    HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin: "BlockAADWorkplaceJoin"=dword:00000001"

    "

    I set that key, via GPO on our VDIs.

    After setting that registry key, new profiles authenticate without incident and more smoothly. There's no more attempt to WPJ. However, existing profiles that were created before the registry key above were set, still attempt to workplace join. With WPJ disabled via GPO, profiles in this state will attempt to WPJ, but eventually time out and auth successfully. (the little WPJ box just sits and spins for a minute or so) To address this, I made a batch script that deletes all the M365 authentication locations. This way we don't have to delete the entire user profile. The script definitely takes a more "scorched earth" approach. I run this within the logged-in user context. I then log off the user, log back in, attempt to authenticate again. It's usually successful. If not, I delete the entire profile under mail in control panel and try again.

    Here's the batch. Please use at your own risk:

    "
    :: @echo off

    setlocal

    :: Delete directories

    rd /s /q "%userprofile%\AppData\Local\Microsoft\IdentityCache"

    rd /s /q "%userprofile%\AppData\Local\Packages\Microsoft.AccountsControl_cw5n1h2txyewy"

    rd /s /q "%userprofile%\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy"

    rd /s /q "%userprofile%\AppData\Local\Microsoft\TokenBroker"

    rd /s /q "%userprofile%\AppData\Local\Microsoft\OneAuth"

    rd /s /q "%userprofile%\Appdata\Local\Packages\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy"

    :: Search for and delete TokenBroker directories

    FOR /D /R "%localappdata%\Packages" %%D IN (*\AC\TokenBroker) DO (

    IF EXIST "%%D" (

    echo Deleting: %%D

    rd /s /q "%%D"

    )

    )

    :: Delete registry keys

    reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\AAD" /f

    reg delete "HKCU\Software\Microsoft\WindowsNT\CurrentVersion\WorkPlaceJoin" /f

    reg delete "HKCU\Software\Microsoft\Office\16.0\Common\Identity\Identities" /f

    reg delete "HKCU\Software\Microsoft\IdentityCRL" /f

    endlocal

    echo Script completed.

    pause
    "
    Note:

    -You'll need to disable the GPO "Prevent access to registry editing tools" for a bit if you want to prevent access denied when deleting those registry keys.

    Other things I've found:
    If you're including/excluding folders in your profiles after log off, make sure these two folders are included, or users will be asked to authenticate every fresh login.

    'AppData\Local\Microsoft\OneAuth'

    'AppData\Local\Packages\Microsoft.AccountsControl_cw5n1h2txyewy'

    That's it. Maybe that makes sense. I hope that helps someone. I saw someone post in this thread that their 1001 errors just went away. Maybe this wasn't the cause and MS fixed something on their side. Either way, WPJ should not be enabled in an Non-Persistant VDI env per Microsoft, so at the very least, we're no longer getting duplicate and stale devices in Entra and the auth process is as it should be.

    Summary:

    1001 errors seem to occur during the WPJ process. Does your env need Workplace Join? If not, turn it off with the reg key above, then fix your existing profiles by nuking all M365 auth locations, and reauthenticate.

    This fix appears to be working for us.

    For simplification I have narrowed down the specific changes that are required:

    Add from admin account:

    HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin: "BlockAADWorkplaceJoin"=dword:00000001"

    Sign out of all Office apps on affected user account.

    Open regedit on affected account and delete the following:

    HKCU\Software\Microsoft\Windows\CurrentVersion\AAD

    HKCU\Software\Microsoft\WindowsNT\CurrentVersion\WorkPlaceJoin

    Delete the following folders from affected user's appdata:

    %userprofile%\AppData\Local\Microsoft\TokenBroker"

    %userprofile%\AppData\Local\Microsoft\OneAuth"

    %userprofile%\AppData\Local\Microsoft\IdentityCache"

    Open Word, sign in, account should sign in without issue.

    After this all Office apps should now be signed in automatically or the sign in should work without issues.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2023-09-19T10:23:59+00:00

    Interesting to know that this isn't a fslogix only problem but rather a terminal server / M365 problem. Let's indeed hope they finally start fixing things instead of focussing on introducing new features...

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  5. Anonymous
    2023-07-10T10:17:27+00:00

    I have the exact same issue. Only have this with this client and not with any other of our RDS deployments.

    Server 2019, fslogix latest version, load balancing 2 RDS servers. Each extra added mailbox gives the error 1001. Then I have to remove the AADbrokerPlugin folder in appdata\local\packages and sign-out/sign-in to fix it. Only then they get the prompt so sign-in into the other mailboxes.

    I have disabled the (default setting now) for the roamingidentity parameter.

    Both RDS servers are also AzureAD joined (hybrid) and SSO has been enabled.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments