{"id":1324,"date":"2011-04-01T13:57:33","date_gmt":"2001-01-01T01:00:00","guid":{"rendered":"http:\/\/inswwdev.azurewebsites.net\/au\/insights\/uncategorized\/citrix-fixes-you-need-to-know-about\/"},"modified":"2023-08-07T04:56:38","modified_gmt":"2023-08-07T04:56:38","slug":"citrix-fixes-you-need-to-know-about","status":"publish","type":"post","link":"https:\/\/www.insentragroup.com\/us\/insights\/geek-speak\/modern-workplace\/citrix-fixes-you-need-to-know-about\/","title":{"rendered":"Citrix Fixes You Need To Know About"},"content":{"rendered":"

Citrix UPM has killed your start menu<\/span><\/h3>\n

Citrix User Profile Manager is great, until it kills your start menu in a published desktop or stops functioning and causes profile failures.<\/p>\n

As a Citrix Consultant at Insentra I deliver a \u00a0high number of designs, assessments and builds over the course of a year and often come across what I affectionately call an \u2018interesting feature enhancement\u2019 (IFE; AKA killer bug).<\/p>\n

One IFE we have seen in a couple of environments lately is where users on a XenApp 7.15 CU2 desktop delivered on Windows Server 2016 lose the ability to access the Start Menu and notification area in their desktop.\u00a0 This can present as just the Start menu access failing for a user, or the server presenting a grey screen to all users and admins when they access it.<\/p>\n

For those who find this one, or anyone building a XenApp environment on LTSR 7.15 CU2, check out the Citrix article\u00a0<\/span>https:\/\/support.citrix.com\/article\/CTX235399<\/a>\u00a0<\/span>\u2013 it says limited release for XenDesktop but, as per normal Citrix KB articles, it also fixed the issue under XenApp 7.15 CU2 and 7.17 for Windows Server 2016 and Windows 10.<\/p>\n

The issue is that the Citrix User Profile Manager removes the keys that the users use for part of the customisation of their Start Menu but it\u2019s a HKLM hive entry that\u2019s altered so the impact is server wide:<\/p>\n

\u201cHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersion\u201d \u201cAppReadiness\u201d and \u201cAppxAppxAllUserStore\u201d<\/p>\n

\"\"<\/p>\n

Citrix indicate a workaround to just recreate the keys on the impacted server, but this doesn\u2019t help the user experience while you deploy and test the new version of UPM. So, in addition to the Citrix workaround, you can also block the rights for the system from removing the hives through group policy deployment.\u00a0 This way you can implement a quick fix while the new image release is being tested and should reduce the amount of reactive work you will need to perform with recreating the hives.<\/p>\n

The entry in the GPO needs to be under the following:<\/p>\n