Issue with AVD User Profile – FSLogix Not Recreating
Hi all, We have a user who has repeatedly reported that their settings and favorites are not loading in AVD. To troubleshoot, we deleted the user’s FSLogix profile from our storage account to allow it to recreate automatically. However, the profile is not being recreated. We are operating in a hybrid environment, and the user is part of a group assigned the Storage File Data SMB Share Elevated Contributor role. From the profile logs, we found the following error: FindFile failed for path: \\<redacted>.file.core.windows.net\userprofiles\<redacted>\Profile*.VHD (Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced.) What are some likely causes and additional troubleshooting steps we should take?
FSlogix Profile Disconnects
Hi, Just wondering has seen this issue with their AVD instances and FSlogix in regards to profile container disconnects. We have version 3.25.822.19044 and my theory is that computers that go into sleep mode (due to power timeouts) are not cleanly triggering the disconnect procedure for the container to be cleanly disconnected. We have noticed this by the users .VHDX.metadata file not deleting on their log off. It's also not releasing the Handles and Leases for their containers, making them sign in with a temp profile if they try again. We are just running a standard regedit profile setup based on this page, https://learn.microsoft.com/en-us/fslogix/concepts-configuration-examples Just seeing if anyone else has any fixes in place? Or is this a known issue. Thanks Josh.AVD with FSLogix - profiles not loading
Setup AVD with FSLogix several months back and profiles had been loading fine. About a month ago, profiles stopped loading and the logs show "Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced." This is in regards to connecting to the profile share path. If I manually try to go to that path, I receive the same error. The accounts do have a password, so it shouldn't be anything to do with a blank password. There are no sign-in time restrictions enforced on these accounts. What's left is a "policy restriction", which is kind of vague. Things I've tried: update to latest FSLogix verify permissions on profile storage enabled these in local policy: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options ‘Accounts: Limit local account use of blank passwords to console logon only‘ = disabled Computer Configuration > Administrative Templates > System > Credentials Delegation ‘Restrict delegation of credentials to remote servers‘ = disabled I have a ticket open with MS support for 3 weeks now, but thus far they've been completely useless.
FSLogix FontSmoothing Issue
I'm running into an issue where I can't get the fontsmoothing option to stay on when running FSLogix. If I stop both FSLogix services on the golden image of the VM then it stays but once I turn the FSLogix services back on that setting is reverted back. Anyone else run into this issue or have a solution?
Outlook 2021 Phänomen in Verbindung mit Server 2019 und FSLogix
Guten Tag Liebe Community, ich habe hier aktuell einen Fall der mich Haare verlieren lässt. Zur Umgebung: RDS-Umgebung mit FSLogix (Funktioniert an sich Super!) FSLogix: Aktuelle Version (2.9.8171.14983) Windows Server 2019 komplett durchgepatcht (Komplette Umgebung ist WS2019) 3x Terminalserver Office LTSC 2021 aktueller Patch (16.0.14332.20279) 32bit (32bit wird benötigt wegen DATEV) Exchange Online User Arbeiten ausschließlich auf den RDS Hosts -> Client Computer sind Intel NUCs und ThinClients (Alles Win10) Zum Problem: Haben letztens ein Upgrade von Office 2016 auf 2021 bekommen. Ich also: Office 2016 mittels OffScrub Tool deinstalliert und Office 2021 installiert mithilfe des Office Bereitstellungstools. Office funktioniert, nur Outlook nicht zu 100%. Hier haben wir folgendes Problem: Viele User bekommen keine Verbindung zu ihrem Postfach -> Outlook versucht die Moderne Auth. zu öffnen und bekommt das nicht hin, das Fenster schließt sich direkt. Ich habe schon etliches Versucht: EnabelADAL 1/0 WAMOverride... etc., div. Tools seitens MS ausgeführt und und und. Bei der Basis Auth. kommt man sogar in einen Login-Loop. Wenn man ein neues Outlook Profil anlegt, schafft Outlook es nicht mal in die Cloud zu verbinden. "Es konnte keine Sichere Verbindung hergestellt werden" Witzig: wenn man die @x.onmicrosoft.com Adresse nimmt, geht das ganze -> man kann sich da einiges hintricksen -> Ist aber absolut nicht Sinn der Sache und führt letztendlich wieder in die selbe Problematik. Ich habe dann die Userprofile Neuangelegt -> Outlook läuft -> Aber nur auf einem der 3 Terminalservern, auf welchem Outlook aktuell Funktioniert ist reines Glück. Hat hier wer Erfahrung, eventuell sogar das selbe Problem gehabt oder hat mir einen Tipp welche Einstellungen ich noch Prüfen kann? Ich danke Vorab!!! Ich habe hier schon etliche Zeit verbracht und sehe vor lauter Bäumen den Wald nicht mehr.FSLogix error
Hi, i built a WVD hostpool over a month ago and has worked as a test, then after either making some GPO changes or using a maintenance script on the profile disks i am getting the below error However I only get it on certain VM's, when i look in regedit/localuser/fslogix/profiles the profile relating to the trouble user seem to be pointing to the VHDX of another user, I have tried deleting the profile from the VM and the VHD but it still creates with the incorrect details. The GPO i Changed was to not put VHDX's in a container folder so all vhds are in one folder, this was so that the maintenance script could run through all vhds. however that doesnt explain why it would still work on other VM's, can anyone advise
