The identifier of the parent virtual disk and the identifier of the differing disk conflict.) OpenVirtualDisk (The virtual disk chain is damaged. The FSlogix logs FSL1.txt Max retries reached. Now I will test this theory during the next Citrix MCS Master Image tests, set my GPP to update instead of replace, and also as mentioned in the comments and in the World of EUC Slack, the new registry value CleanupInvalidSessions. If you don’t manage them via GPP, there is a great change you belong to the group of people, not affected by this problem. Now the real solution would be, to double check how you manage the local FSLogix groups. So in your opinion, I would need to change the GPP to "update" and should try out the new "CleanupInvalidSessions" registry key. I just checked all three affected environments and the GGP is set to "replace". As I manage those groups via Group Policy Preferences (GPP) and choose the mode replace instead of update, these groups get re-created during the Group Policy background refresh, which changes the SID, resulting in the issues described above. According to him, FSLogix uses the SID of the local include/exclude groups now, instead of the name. He encountered the same problems as we did, and during his troubleshooting he discovered an undocumented FSLogix change in version 2009 (.30127). This because the local groups get recreated and get new SIDs. So if the GPO is set up to "replace" instead of "update", it will stop working after a gpupdate within users session. Soon after I published this blog post, Fredrik Endresen contacted my on Twitter, with the following now uses the SID of the local includeexclude groups. The current test (and soon to be productive) environments for all my customers look like this now: The solution to my problem, after lots of different tests, was to downgrade to FSLogix 2004 (.30108) and all problems were instantly gone. I wasn’t able to find anything meaningful in the FSLogix logs, but I post them non the less at the end of the blog post, so someone with the same issue might be able to find this blog post through his favorite search engine. A reboot could solve the problem temporary. (December 8, 2020-KB4593226 (OS Build 14393.4104) )Įvery second day, the test users were unable to login. No in-place upgrade of the FSLogix apps or the Citrix VDA. So all tests were performed on a freshly installed machine catalog. At my Citrix Machine creation services (MCS) customers, I never update machine catalogs, I always replace them with fresh Golden master images installed from scratch via Microsoft Deployment Toolkit (MDT).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |