This message was deleted.
# _general
s
This message was deleted.
👍 3
l
Hey dude, good catch. Have you logged a ticket? Is this the exact repro?
o
Hey Leee! I just found it about an hour ago while doing a change record for my client, i'll be sure to log it with Citrix tomorrow when i'm back at work Steps to repro as follows: 1. 1 - Install CVAD 1912 with UPL on MCS master 2. userInit gets updated as follows: 3. C\Windows\system32\userinit.exe,C\Program Files\Unidesk\Layering Services\LayerInfo.exe, 4. Un-install CVAD 1912 with UPL on MCS master 5. UserInit key is not updated on MCS master 6. VDA log the following for users logging in via ICA The Windows logon process has failed to spawn a user application. Application name: . Command line parameters: C:\Program Files\Unidesk\Layering Services\LayerInfo.exe. Fix is to manually reset the UserInit key to a pre-UPL state: C:\Windows\system32\userinit.exe,
l
I will test it in the 2003 preview and if not fixed can ping it through to product teams. It may already be fixed.
o
Another way to tell, the C:\Program Files\Unidesk folder and it's subs is not removed. I'm guessing they just sped through QA on bolting on UPL to CVAD 1912, and didn't full update the VDA un-install logic. The actual 4 new services added by UPL are fully removed, it's the UserInit key that breaks the bank
l
Sure, I understand. I'd like to get this in 2003 if it's not fixed already. It's a pretty big gotcha.
👍 2
o
Thanks man, and have a good rest of your Sunday 🙂
r
Bro that was a good catch.
o
Thx Ray! This has been a helluva week, 70 hours or so. I'm surprised I had the brain cells left to even troubleshoot. Mind you, I had 3 coffees today 🙂
r
Yes me too 82 to be exact. Deploy Citrix vdi from ground up. To allow remote workers to do there job
o
Just an update, it looks like just removing the offending UserInit key wasn't enough, additional manual removals are required. I'll post an update tomorrow with the additional removal actions required
Nothing new here, but Citrix QA still needs work! If CVAD 1912 is LTSR, the below steps should not be required. I'm not pleased , as in Jan/Feb I was definitely on the pro UPL team. See my blog post: https://www.getvpro.com/2020/01/citrix-upl-and-fslogix-best-of-both.html Anyway, rant aside, here are the steps required to completely remove any trace of CVAD 1912 UPL from a system 1 - From an elevated command prompt run Sc delete Ulayer 2 - Use PSEXEC -I -s "cmd" then open reged32 to amend permissions on below to include local admin group and delete: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Winlogon\Notifications\Components\ULayer 3 - Delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Ulayer 4 - Delete c:\Program Files\Unidesk 5 - Amend HKLM\Software\Micrsosoft\Windows NT\WinLogon\UserInit to be as below (Pay attention to that last "," ! C:\Windows\system32\userinit.exe, That being said, I'm going to re-build any systems where I installed UPL on. Who knows what other mess is left behind by shoddy Citrix QA
I opened a case to Citrix to let them know
Citrix responded really quick! They are adding it their knowledge base. I’m surprised I’m the first to report it. CVAD 1912 is from mid December. Maybe it an odd odd use ? Changing an MCS master that was used to clone UPL enabled machines and then wanting to remove it ? We are getting away from UPL as it’s not the right fit for the client: inconsistent nutanix hosts and a messy AD that is out of my control to fix
l
Good catch, I'm so busy and haven't had time to reproduce it. Nice work man.
👍 1
o
Hey all, it doesn't look like it's fixed in the CVAD 2003 release https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/whats-new/fixed-issues.html Oh well, maybe the next one 🙂
l
:-( are the generating a support article for you? Do you have a case number?
o
Hi Lee! It's #79601031
Not sure if they will create a KB, I will ask
They’ve confirmed an internal KB has been created, but nothing public facing. Hopefully people searching for the ulayer error I noted will find my blog post
l
Finders crossed, Twitter and on here too. At least the calls will be addressed more quickly