A list containing the majority of Citrix App Layering support articles collated to make this page a one stop place for you to search for and find information regarding any issues you have with the product and its related dependencies.
The page is updated daily with new support articles and information. Articles will change from time and if information here is outdated or incorrect please let me know using the comments. Links may also expire or change so if you find broken links, please again let me know. For each issue, known product versions affected are recorded however that does not mean products versions that aren’t listed are not affected.
There is a search box that you can use if looking for a specific fault. For example if you have an error code or error message, use that to perform a search. You can also use your browsers search feature which will perform a search against the whole page based on the words you enter.
App Layering:
| wdt_ID | Brief Description of Issue | Brief Description of Fix | Applicable Product Versions Affected (if known) | Link to supplemental Support Article(s) |
|---|---|---|---|---|
| 20 | Whilst logged on to the App Layering Management Console, you get unexpected errors and disconnects. From the console you may also see "Connectivity Failure" or "No connection to Layering Service". | Reboot the Enterprise Layer Manager appliance. This allows the internal services to reconnect to each other and is the most likely solution. | Citrix App Layering 4.x. | https://support.citrix.com/article/CTX226405 |
| 21 | Windows 10 major upgrade may result in new Recovery Volume partition. | Make sure to remove the volume using diskpart before finalising the OS layer. Failure to do so could result in desktops failing to boot correctly. This also applies to booting Virtual Machines via PVS. | https://support.citrix.com/article/CTX226407 | |
| 22 | "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED CVhdMP.sys" message when booting images created by App Layering via Citrix Provisioning Services. | 1. Check the NIC slot number if using ESX. 2. Make sure Target Device hardware is not too different from the Packaging Machine. 3. Check publishing Platform layer hypervisor version is set correctly for the hypervisor you are using. 4. Make sure E1000 NICs are not in use. 5. If using Hyper-V, create the Platform layer on a Packaging Machine that has a Legacy NIC attached. | http://www.jgspiers.com/0x0000007e-bnistack-failed-vmware/ | |
| 24 | When publishing an image to PVS, you receive the following error: "A failure occurred while publishing the image to PVS server servername (servername.fqdn). Error: The operation being requested was not performed because the user has not logged on to the network. The specified service does not exist. (Exception from HRESULT: 0x800704DD)". | Uninstall then install the App Layering agent again. Try running the install media locally instead of over the network. | https://discussions.citrix.com/topic/388589-after-upgrade-to-app-layering-43-publish-to-pvs-79-failing/ | |
| 25 | You receive various App-V related issues including publishing issues. | Upgrade to App Layering 4.4+ | Citrix App Layering 4.2 and 4.3. | |
| 26 | Unable to import Windows 10 gold image into App Layering. During the import job, you receive the following error: "The CachePoint Appliance could not import the gold image VM to create the Operating System Layer. Error is: Failed to copy folders recursively". | The import fails if the gold image has Windows Updates from Feburary 2017 and newer installed. From the gold image, delete file "Microsoft.MicrosoftOfficeHub". | https://support.citrix.com/article/CTX222733 | |
| 27 | When trying to create or edit a connector, you receive a "Authentication Failed (401)" error. This is a problem caused by long-running Active Directory queries inside the ELM appliance create a database lock that causes the rest of the connector transaction to timeout. | Upgrade to App Layering 4.3+. This version introduces some improvements however some issues still remain. | https://support.citrix.com/article/CTX224176 | |
| 28 | When clicking the search box within Outlook 2016/2013 in an Elastic Layered image, a prompt for credentials is displayed and an installer launches and hangs. | Install the Windows Search Service in a new OS layer version. | https://support.citrix.com/article/CTX224077 | |
| 29 | You receive error "Failed to probe partitions from virtual disk" when importing the OS layer. This is most often seen when importing a XenServer Windows 10 gold image that was exported as an OVF, however could happen to any image. | Extend the gold image virtual disk by 1GB. Don't extend the partition within Windows. | https://support.citrix.com/article/CTX223716 | |
| 30 | When creating a layer, you get the following error: "Failed to execute script: vCenter returned an unexpected failure. A specified parameter was not correct". | This issue was due to attempts at creating a layer on ESXi 5.1 which is not supported by App Layering. You must point App Layering connectors to ESXi 5.5+ hosts. | https://support.citrix.com/article/CTX223690 |
adzm
September 11, 2018Where did you get the information for the “On Server OS VDAs created via App Layering, you notice that Remote Desktop grace period expire and no licenses are available for connecting users, even though you have the VDAs pointed to an RD license server which has licenses available.”
Would like to know more information about how you figured that out.
George Spiers
September 11, 2018That was something I discovered in a production environment I manage. The RDS time-bomb key needed to be deleted.
Another fix/workaround is to place the Platform Layer Packaging VM in an OU that receives RDS license server information from Group Policy, so that the information is captured in the Platform Layer.
adzm
September 11, 2018I opened an incident with Microsoft support. They had someone on the line that was familiar w/ Unidesk. When I deleted that key from the platform layer then the XA server boots up w/o the key and then after the first user rdps or launches an app from the server the key returns.
That is a good thing because Microsoft engineer explained the grace period resets to 120 days and you will be ok if your license server is down for whatever reason. Otherwise removing it only from the OS layer you will get 0 days grace when running:
wmic /namespace:\\root\CIMV2\TerminalServices PATH Win32_TerminalServiceSetting WHERE (__CLASS !=””) CALL GetGracePeriodDays
Matthias
June 19, 2019We have the platform layer within the OU to receive the licensing information. The information is also set via gpedit.msc. But after booting the VDA from the image the message “The RD Licensing grace period has expired and the service has not registered with a license server with installed licenses. A RD Licensing server is required for continuous operation. A Remote Desktop Session Host server can operate without a license server for 120 days after initial start up.” appears in the Event Viewer. The grace period days als decreases. The RDSH licensing diagnoser shows no error. The message in the Event Viewer doesn’t show up if the VDAs rebooted without reset of the disks to keep the changes.
Is it normal behaviour that the grace period decreases with applied licensing information?
Thanks!
George Spiers
June 20, 2019It’s not normal to get those messages. You could try deleting the REG_BINARY from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod. You will have to take Full Control permissions of the GracePeriod key which is fine. Also make sure the licensing configuration is correct through both gpedit.msc and aligns to User CALs or Device CALs, with the correct RD License Server FQDN. Another option is to rebuilt the Platform layer including these steps.
Matthias
June 24, 2019Thanks for the reply. I analyzed a little bit more:
The “The RD Licensing grace period has expired and the service has not registered with a license server with installed licenses. A RD Licensing server is required for continuous operation. A Remote Desktop Session Host server can operate without a license server for 120 days after initial start up.” appears always, when they Registry key HKLM\SYSTEM\CurrentControlSet\Control\terminal Server\RCM\Licensing Core\LicensingMode is set to “5” (default). When set to “4” (per User license mode) the message doesn’t show up in Event Viewer.
Mike
August 1, 2019Hey George, seeing similar behavior in an environment but it is intermittent every few days a server may boot up and log an event at boot ID:1068 “The RD Licensing mode has not been configured”.
If i reboot the problem server it comes up fine and is accessible.
Is that the behavior you have witnessed?
This is an MCS environment with App Layering. I’ve never had to do this with MCS or PVS in the past.
Interestingly even though the license server policy is per user (mode 4), both a working and non-working server reports the license mode as 5 (per device) in the grace period key.
George Spiers
August 8, 2019Any time I had this problem I rebuilt the Platform layer and made sure to apply the Terminal Server licensing configuration to the Packaging Machine before finalising the layer.
Nick Daniels
April 10, 2019We have a problem with the PATH system variable. We have several application layers, each of which updates the PATH variable but because of the “last layer wins” only the PATH variable from the latest layer is in the image so things like ORACLE_HOME don’t exist in the final image.
Citrix’s suggestion is to make a note (manually) of all the application layers that update the path and then for every image (template\layer combination) create another layer containing that path variable that’s valid for THAT layer combination.
I can’t even imagine what an Elastic layer would do in this scenario.
Is there a better solution ?
Thanks
George Spiers
April 11, 2019No I would not create App layers for that. Why don’t you use Group Policy?
Venkat
August 14, 2019Hey George, When creating a new MCS Catalog, App Layer created VDA machine in v Sphere is not available in studio for selection.
George Spiers
August 18, 2019Is the machine in a Resource Pool in vSphere?
Venkat
August 22, 2019Thanks for your response Geroge!!
yes, they are in the same Resource Pool in vSphere, and what I noticed is that master image is now showing in the studio, but it took 3 days to reflect in Studio.
This issue is still persistent, I deployed Win10 1809 & 1709 yesterday using App Layering those 2 templates also not showing in the studio now. I removed XdConfig custom attribute and even rebooted DDC like last time, but no luck. Maybe I need to give a few more days for this also:). I am not sure what is happening in the back-end.
Venkat
August 22, 2019My bad, it fixed after changing resource pool. thanks George
Ravi
November 19, 2019Hi George, Getting a black screen in win10-1809 User layer published images, Initial logon is fine, vhd is creating in the share, but if I log out and logon for 2nd time I’m getting the black screen.
George Spiers
December 3, 2019What version of App Layering? Does it happen with just the OS layer and User layer attached e.g. no App layers?
Ben Tusa
January 6, 2020Is there a trick to fix the IE rendering issue when creating a new connector?
George Spiers
February 17, 2020What issue is that?
Ben Tusa
February 17, 2020I’ve learned it may be an issue when using IE in Server 2016
https://ibb.co/qNz2xWs