Forum Discussion
WVD logon issues. The Group Policy Client Service failed the sign-in. Access is denied.
Appears that there is a new FSLogix update, although it doesn't specifically address this. It only came out yesterday but curious if anybody is going to try this soon.
https://docs.microsoft.com/en-us/fslogix/whats-new
CaptainReboot Thanks for alerting us all to this, disappointing it didn't come from Guido or someone from MS.
Looks like this is the line that covers it:
- FSLogix now correctly handles cases where the Windows Profile SVC refCount registry value is set to an unexpected value.
We only have one server and it's production so unable to test yet, will be good to see how others get on.
Lee_E Hello. Sorry for the issue you are experiencing. We released a fix for the public preview a few weeks ago please check :FSLogix 2201 Public Preview Update 1 is now available - Microsoft Tech Community
That issue has restarted our QA process. Unfortunately we cannot commit to a date until it meets our quality bar. I'll keep you all posted here. Sorry for the inconveniences that this is causing.
- Since this preview was January, I know there's a subsequent issue with it, and it's now March can we have an update please? I have a few affected users who log on when I'm not working, due to time zones and me being the only IT person in the business. I can't have them not working until I get back to work, imagine if I was on leave for a week.
Did anybody get access to the private preview download yet? I requested it and it said within 24 hours I should get a response. Curious if that's accurate.
- Hello Everyone. We released a new Fslogix public preview version which contains the fix for RefCount issue. Please feel free to test it and let us how this goes.
https://techcommunity.microsoft.com/t5/azure-virtual-desktop/the-fslogix-2201-public-preview-is-now-available/m-p/3070794
https://docs.microsoft.com/en-us/fslogix/whats-new#fslogix-2201-public-preview-29804843478 Lee_EThanks, missed that line. We have a few test and UAT environments. I might throw it on there but it doesn't get used much. We also have a production pool that we've seen it on that only a handful of us in IT uses, so I might do that as well as I just saw the error myself this morning and did the reg change manually to see if it would work (which it did).
