This message was deleted.
# citrix-vads
Slackbot
04/23/2020, 3:18 PMThis message was deleted.
j
James Rankin
04/23/2020, 3:43 PMHave you used SetFTA or just trying to get it to work natively?
d
Dennis Parker
04/23/2020, 5:22 PMTried using the SetFTA utility, but the client doesn't want to force browser settings for everybody, and we don't want to manage that as users switch browsers. I'm not 100% certain the outcome of the SetFTA tool because it would set at every login, which isn't ideal either, but could work well enough.
And again, it works for "upgraded" profiles, so just seems odd that it would not work for new profiles. I am only attempting with default browser, and I know I can't publish the built-in default selector in 2019, which is a pain now too.
r
Robert Magasi
04/23/2020, 5:36 PMThere is a private fix for it.
d
Dennis Parker
04/23/2020, 5:52 PMSweet. I'll let my co-worker know.
Dennis Parker
04/23/2020, 6:18 PMIs there a fix number I can provide to support? They aren't being helpful in looking for it.
Dennis Parker
04/23/2020, 6:40 PMSounds like Citrix is going to develop a new private for our environment. Appreciate the responses.
c
Cormac Long
04/23/2020, 9:12 PM@Dennis Parker do you have a fix number by any chance? I am seeing something similar and I am using setdefaultbrowser.
d
Dennis Parker
04/23/2020, 9:19 PMI don't yet, I will update when I get a fix. I am out of the office on Friday, so expect Monday or as soon as they get the fix.
Dennis Parker
04/28/2020, 7:11 PMCitrix came back with upgrade to 2003. I said no, I am LTSR. Waiting for response to that.
Dennis Parker
05/06/2020, 2:42 PMCitrix provided a Private fix, but no fix number, this morning. It is an updated UserProfileManager.exe.
This is the explanation and instructions for use from Citrix:
The reason this is happening is because the inherit permissions on HKCU\Software\Microsoft were removed by UPM 1912.
Instructions for deployment:
• New users that logon with the private UPM in place will not see this issue.
• For existing users, manually enable the permission inheritance of ALL APPLICATION PACKAGES to the HKEY_CURRENT_USER\SOFTWARE\Microsoft registry key:
• Log on to the VDA with the target user account.
• Open Registry Editor.
• Navigate to HKEY_CURRENT_USER\SOFTWARE\Microsoft.
• Right-click the Microsoft key*,* select Permissions -> Advanced, and select Enable inheritance, Select the check box to apply the permissions to all child objects.
• Click Apply and OK in sequence.
If you’re planning to remain on LTSR this fix will be available in the upcoming 1912 CU1 release expected this quarter. This fix is also included in the CR release 2003.