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 | |
| 31 | When logging on to an image created by App Layering, you may receive message "We were unable to load the required configuration files. You may not be able to access some of your applications. And, any changes you make to application settings or data will not be saved - Unable to find the folder specified". | This can occur when the Elastic Layer SMB share is unreachable. Open Event Viewer and check the Applications log which should contain the error and what path cannot be found. Make sure the path is correctly specific within the Enterprise Layer Manager and you have permissions to access this share. | ||
| 32 | VDA install hangs when installing prerequisites. | Install the Media Foundation feature before installing the VDA. It is recommended to install this feature within the OS Layer. | https://support.citrix.com/article/CTX224744 | |
| 33 | When using vCenter, if a datacenter is inside folders, the App Layering connector cannot see it. | This is a current limitation of App Layering and as a workaround you should temporarily remove the datacenter from folders until the connector has been created. You can safely move the datacenter back once the connector has been created. | https://support.citrix.com/article/CTX223029 | |
| 34 | Elastic Layers are unavailable after logon and the Application Event Log displays error "No Elastic Layer assignments were specified". | Make sure the affected user(s) have read access to the Elastic Layer SMB share. | https://support.citrix.com/article/CTX222163 | |
| 35 | When creating a connector to PVS you receive message "Failed to validate the Domain User and password" and in the unidesk-pvs-connector.log.json file is message "The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests". | Make sure PowerShell Remoting is enabled on each PVS server. | https://support.citrix.com/article/CTX222073 | |
| 36 | The creation of a Packaging Machine or Windows 10 Desktop fails on ESXi 5.5 updates 1 and 2. Since ESXi 5.5 updates 1 and 2 does not support true Windows 10 virtual machines, you have to install Windows 10 on a Windows 8 virtual machine. App Layering will try to create a proper Windows 10 virtual machine, which is not available on the host. The task fails with a "A specified parameter was not correct" error from vSphere when trying to create the virtual machine. | Upgrade to vSphere 6.0 and above which will actuall let you select Windows 10 when creating a virtual machine. | https://support.citrix.com/article/CTX221736 | |
| 37 | Event Logs show error within the Event Viewer System log that reads "Unidesk denied an attempt to rename a directory from one of the read only portions of the file system. Please see the Unidesk Administrator for help". You may also receive an error trying to move a folder to yhe Recycle Bin or when attempting to rename a directory. | This is not an error but rather a limitation of the App Layering filter driver. Citrix refuse to allow you to rename a directory that was originally provided through an OS or Application Layer. A directory which exists entirely in the User Layer can be renamed at any time however a directory that is part of an OS or Application Layer can only be deleted. As well as logging this error to the Event Log, App Layering logs the same entry with directory name to C:\Program Files\Unidesk\Uniservice\Log\Log0.txt. | https://support.citrix.com/article/CTX221726 | |
| 38 | PVS Target Devices failing to activate via KMS and all machines share the same CMID. KMS was not rearmed before finalising the Platform Layer. | Add a new version to the Platform Layer and before finalising run slmgr /dlv followed by slmgr /rearm. | https://support.citrix.com/article/CTX221763 | |
| 39 | You are prompted to reboot due to newly detected hardware. | Look in C:\Windows\inf\setupapi.dev.log which should show you the device that caused the reboot prompt. For exampe, if you have added a second disk, you may first need to create a new Platform Layer and add the second disk to the Packaging Machine so that it is detected and captured in to the layer. | https://support.citrix.com/article/CTX221746 | |
| 40 | Websense not working in a Application Layer. | Websense requires a registry modification to work as a Layer. | https://support.citrix.com/article/CTX221775 | |
| 41 | After an ELM appliance upgrade you cannot open the App Layering Management Console. | Clear your web browsers cache and press CTRL-F5 to force a refresh of the web browser. Some browsers do not clear old Silverlight files when you clear the cache. | https://support.citrix.com/article/CTX221727 | |
| 42 | When using App-V, you receive a blue-screen due to driver AppvStrm.sys. | Upgrade to App Layering 4.1+ | Unidesk 4.0.8. | |
| 43 | The Enterprise Layer Manager appliance requests a file system check (fsck) when recovering from a host or storage interruption. | An unexpected interruption in the operation of an ESX host or an underlying datastore in VMware can damager the root file systems of the ELM. When an operational interruption occurs, the startup process prompts the user to enter the root password in order to repair the damaged file system. Log on to the ELM shell and follow the prompts to run fsck. | https://support.citrix.com/article/CTX221751 | |
| 44 | There is a possible BSOD issue with App Layering 4.2, Office 2016 click-to-run/non click-to-run and Elastic Layering. | Upgrade to App Layering 4.3 which should contain the fix. | App Layering 4.2. | |
| 45 | When finalising a layer you receive error "InvalidDeviceSpec" and the task fails. | This can be caused by making hardware changes to the Packaging Machine which App Layering does not expect such as taking snapshots. Make sure to delete snapshots before finalising the layer. | ||
| 46 | Microsoft Office licensing will break if a user logs on before the Office activation script runs. If a user logs on too early they may see "Please wait while setup configures Microsoft Office" which will fail. | To prevent users from logging on before the script has run, set the "Citrix Broker Service" to "Automatic (Delayed Start)", or else to set a specific delay value via registry, or else define a "Settlement Period" for all desktops in a Delivery Group by using command "Set-BrokerDesktopGroup -SettlementPeriodBeforeUse". | https://support.citrix.com/article/CTX227287 | |
| 47 | Virtual Machines crash with a BSOD referencing "unifltr.sys", which relates to the App Layering Filter driver. | Upgrade to App Layering 4.3. | https://support.citrix.com/article/CTX227081 | |
| 48 | When finalising a layer the task fails with error message "An error occured while finalizing version 'VersionName' of Layer 'LayerName'. Please address this issue and retry: Layer volume label does not follow the required format". | App Layering uses the volume name for disks to identify layers by ID number. You must never change the volume names while editing a layer. If you do, you will run in to this issue. | https://support.citrix.com/article/CTX226913 | |
| 49 | When using the script associated with deploying the ELM to Azure, the script may fail. The PowerShell logs will show "StorageName is not a valid storage account name. Storage account name must be between 3 and 24 characters in length and use numbers and lowe-case letters only". | Shorten the deployment name to between 3 and 15 characters. Also make sure to use numbers and lower case letters only. | https://support.citrix.com/article/CTX226916 | |
| 50 | When configuring the PVS Agent you receive error “Could not create SSL/TLS secure channel”. | Upgrade to App Layering PVS Agent 4.4. | https://support.citrix.com/article/CTX227957 | |
| 51 | Adobe Creative Cloud 2017 does not behave as expected when published as a layer. | Install each individual application individually, as mentioned in the CTX article. | Adobe Creative Cloud 2017. | https://support.citrix.com/article/CTX228123 |
| 52 | Audio does not work for the first logon to a VDA when User Layers are being used. | Upgrade to App Layering 4.5. You will need to republish the images to ensure they are updated with the new App Layering drivers. | Citrix App Layering 4.x. | https://support.citrix.com/article/CTX227094 |
| 53 | Importing an OS Layer from vSphere fails. The task sticks at 0% and then times out. | Check to make sure that the ELM can communicate with the vSphere host over 443. | https://support.citrix.com/article/CTX228486 | |
| 54 | Office and Windows activation does not work after an upgrade to App Layering 4.5 when Elastic Layering is disabled. | Contact Citrix for a private build. | Citrix App Layering 4.5. | https://discussions.citrix.com/topic/389993-windows-2016-activation-issue-since-45/ |
| 55 | Office rearm on Machine Creation Services fails because "kmssetup.cmd" is running multiple times. The "kmssetup.log" file shows that "kmssetup.cmd" is being run multiple times. | kmssetup.cmd and child script "OfficeActivate.cmd" must only be run once at startup. Check your Group or Local Policy startup scripts or other areas to ensure this script is only running once on startup. | https://support.citrix.com/article/CTX229151 | |
| 56 | An App Layering vSphere Connector fails authentication using any username and password. | Uninstall VMware PowerCLI 6.5, downgrading to 5.5. | https://support.citrix.com/article/CTX229178 | |
| 57 | You receive a "One or more PVS configuration is invalid" error on your PVS Connector(s) that may have worked previously. This can occur when creating or editing PVS Connectors. | Check the DNS entries on ELM and make sure they are correct and pointing to healthy DNS servers. | ||
| 58 | kmssetup.cmd will not run if the script is not unblocked. You can verify if the script ran by viewing kmssetup.log. | Unblock the script and all other files from directory "kmsdir" by right-clicking each file -> Properties. Alternatively, PowerShell v3 has a cmdlet which can unblock files. Also confirm that kmssetup.cmd is set as a Startup script via gpedit.msc. | https://support.citrix.com/article/CTX229581 | |
| 59 | The ELM appliance will not boot and gives error "Operating System Not Found". | Make sure the 30GB SCSI boot disk is set to port 0:0. If the port is anything else, ELM will not boot. | https://support.citrix.com/article/CTX229663 | |
| 60 | New tasks do not start for 10 minutes and other tasks seem to hang or become stuck. | This happens when you have increased the number of vCPUs assigned to the ELM appliance above 4. This is currently an issue with ELM on version 4.6 of App Layering. To fix, reduce the vCPU count back down to 4. | Citrix App Layering 4.6. | https://support.citrix.com/article/CTX229710 |
| 61 | The Configuration page "System -> Settings -> Configuration" hangs at "In Progress" and then times out 5 minutes later. | This is caused by increasing the ELM appliance vCPUs above 4. To fix, reduce the vCPU count back down to 4. | Citrix App Layering 4.6. | https://support.citrix.com/article/CTX229709 |
| 62 | During the creation of a Platform Layer on vSphere, you receive error "A timeout occurred waiting for a vsphere task to complete". | Setting the layer cache disk size to a value of "0" is one solution. | https://support.citrix.com/article/CTX229744 | |
| 63 | When creating a new connector, the HTML5 web page does not load and sticks at the initial App Layering icon. | Make sure you are running Internet Explorer 10 or later. | ||
| 64 | When creating machines using MCS and an App Layering master image, you receive error "OS Image Preparation Failed", "ErrorID: ImagePreparationOSRearmFailed" and "InternalErrorMessage: Operating System Licensing Rearm Failed". | Since App Layering takes care of OS Rearms using the "kmssetup.cmd" script, disable OS Rearm as an MCS step by running "Set-ProvServiceConfigurationData -Name ImageManagementPrep_Excluded_Steps -Value OsRearm". | ||
| 65 | After installing VDA 7.15 on a Platform Layer, machines fail to boot with error "Windows cannot verify the digital signature for this file" for file "CtxMcsWbc.sys". | Disable driver signature verification or install the latest Windows OS patches. | https://support.citrix.com/article/CTX229961 | |
| 66 | During an upgrade to version 4.6 of App Layering, the upgrade does not complete. Alternatively if it does complete, you see no layers, | You must roll-back your snapshot and make sure the ELM appliance only has 4vCPU. | https://support.citrix.com/article/CTX229621 | |
| 67 | When importing an OS Layer from vCenter you receive error "Failed to connect to host". | Check that the DNS entries on the Enterprise Layer Manager are pointing to correct DNS servers that can resolve your vCenter FQDN. The DNS server which holds the record must be specified within "DNS1", or else the server specified under "DNS1" must be set to forward requests to an authoritative DNS server if no record is stored locally. Alternatively, if needs be, create an A record if one is not already present, or the DNS server is not part of the same domain as the vCenter host. Once DNS entries have been changed to correct ones and the DNS server specified under "DNS1" can resolve the FQDN, reboot the ELM appliance. | ||
| 68 | "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED CVhdMP.sys" message when booting images created by App Layering via Citrix Provisioning Services. | Create a second version of the Platform Layer. You don't have to make any adjustments to the layer, just create a second, publish the image out to PVS and try booting. | ||
| 69 | The "Citrix App Layering Image Preparation Utility" fails to install on Windows 10 in Azure. The error message you receive is "Unsupported Operating System detected". | Windows 10 is not fully supported by Azure itself at this time, therefore App Layering 4.6 refuses to install the software. It is possible to bypass this, however this is experimental and not supported. | https://support.citrix.com/article/CTX230252 | |
| 70 | When creating a new or editing an existing Connector, the HTML5 page does not load when browsing to the ELM via FQDN. When browsing to the ELM via IP the HTML5 Connector wizard loads fine. | Check that your proxy is not blocking communication to the FQDN Connector page. | ||
| 71 | When the Trend Anti-Virus "Trend Unauthorized Change Prevention" service is enabled, machines may hang on boot, login or randomly during sessions. | You must disable this service as it interfers with registry virtualisation. | https://support.citrix.com/article/CTX230625 | |
| 72 | The "Test SMB File Share" function in App Layering reports "Permissions Incorrect". | App Layering tries SMB 3.0.2, 3.0, 2.1, 2.0 and 1.0 in that order until a successful connection is made. Logging on to the user account you want to use against the SMB share, try manually browsing it using this account to rule out it being an issue with the Enterprise Layer Manager. | https://support.citrix.com/article/CTX230934 | |
| 73 | When finalising a Platform Layer you receive message "It looks like the Packaging Machine has never been powered on". | If you have attached extra disks to the Packaging Machine, remove these or else the layer will not finalise. | https://support.citrix.com/article/CTX226406 | |
| 74 | When publishing an image direct to vSphere or editing a layer, the task stalls but does not fail. Upon rebooting the ELM appliance you receive an error against the task stating "The request was running when the connector service stopped and could not be restarted automatically". | When the ELM reboots in the middle of a task, the Connector also reboots. This error is expected. | https://support.citrix.com/article/CTX231404 | |
| 75 | Citrix App Layering Nutanix Connector does not work with Nutanix AOS 5.5. You may get error "A failure occurred connecting to the Nutanix server" and "sslv3 alert handshake failure". | App Layering only negotiates over SSLv3, which has been disabled in AOS 5.5. Citrix are actively working on a fix and advise to postpone upgrades to AOS 5.5 at this time. | Nutanix AOS 5.5. | https://support.citrix.com/article/CTX231512 |
| 76 | When exporting or importing layers you may receive error "Object reference not set to an instance of an object". | This seems to be an issue related to compatibility with some NetApp filers and the ELM SMB client. If you change the target to different storage, the import/export task will complete. | https://support.citrix.com/article/CTX231695 | |
| 77 | When creating an OS Layer, you cannot see or select the Hyper-V connector. | The Hyper-V connector cannot be used to create/import OS Layers. You still need to manually copy the master image VHD disk to the ELM SMB file share and import from there. | https://support.citrix.com/article/CTX231694 | |
| 78 | A number of messages can appear on the ELM console such as "Receive control failed", "cifs_mount failed", "NBD_DISCONNECT". | These messages can be safely ignored, the full list of messages can be found in the CTX article. | https://support.citrix.com/article/CTX231811 | |
| 79 | When attempting to create your first ever Connector you get a "Page can't be displayed" error message. | Reboot the ELM. This problem happens only on the very first boot of the ELM as sometimes the Connector processes do not start correctly on first boot. | ||
| 80 | When building a Platform Layer you receive error "Item not found: Unable to locate 'PowerShell Session' with an ID of". | This can happen if you have a slow connection between the ELM appliance and SMB file share. You should ensure you have a 10GB connection between both parties. | https://support.citrix.com/article/CTX232136 | |
| 81 | You cannot run "optimize.hta" or "setkmsversion.hta" as an administrator by right-clicking them, even though documentation says to do so. | This is because the files are ".hta" so right-clicking to run as an administrator is not an option. Instead, you can run CMD as an administrator and run the files that way. | https://support.citrix.com/article/CTX232357 | |
| 82 | When creating a Connector and selecting a Virtual Machine Template, upon clicking the "TEST" button you receive error "The virtual machine template cannot have any attached disks. Please detach the disks through your vCenter console". | The Virtual Machine Template will be used by App Layering when creating layers, or when publishing machines direct to the Hypervisor. Since App Layering adds disks itself, there is no need to have any disks on this Virtual Machine. | https://support.citrix.com/article/CTX232426 | |
| 83 | When deploying the App Layering OVA template to an ESX host, the task fails with error "Failed to deploy VM: postNFCData failed: Capacity of uploaded disk is larger than requested". | You have to import the OVA template using vSphere connected to vCenter. You cannot import it direct to an ESX host. | https://support.citrix.com/article/CTX232427 | |
| 84 | After upgrading VMware Tools 10.2.0 or installing VMware View Agent 7.4 on a Platform Layer, on reboot the Packaging Machine blue screens with error "PEN SHARE COUNT". | This is a known issue however for now you must continue to use older versions of the View Agent or VMware Tools. Versions 7.3.1 and 10.1.15 respectively are known to work. It is important to note that VMware View 7.4 requires VMware Tools 10.2.0. | VMware View 7.4 and VMware Tools 10.1.15. | https://support.citrix.com/article/CTX232437 |
| 85 | When importing an OS Layer, the operation fails with error "Windows is hibernated, refused to mount". This is typically seen with Windows 10. | You should disable hibernation completely using command "powercfg -h off" on the gold image. Sometimes even when shutting Windows 10 down, it hibernates instead. | https://support.citrix.com/article/CTX222148 | |
| 86 | The next time you create or edit a layer using a vSphere connector after an ELM upgrade, the task fails with error "Failed to connect to vCenter server. Cannot read property 'root' of undefined". | Reboot the ELM appliance to clear this issue, which is a problem immediately after an upgrade. | https://support.citrix.com/article/CTX232474 | |
| 87 | 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. | This happens when building a Platform Layer which is not at the time of creation receiving any RD Licensing information from Group Policy. In this case, the message "Remote desktop services will stop working in 120 days" is briefly displayed and a time bomb REG_BINARY is created in the registry. On your Platform Layer, remove the time bomb REG_BINARY from "HKLM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod". | ||
| 88 | When publishing images to vSphere and you have a Virtual Machine Template defined within the vSphere Connector, you notice that the VM has two NICs. | Edit your Virtual Machine Template VM and check the NIC. If the NIC is not an "VMXNet3" NIC then this is the problem. As App Layering does not detect a VMXNet3 NIC when publishing the image, it creates a NIC, resulting in two NICs residing on the VM. | https://support.citrix.com/article/CTX233660 | |
| 89 | When backing up the Enterprise Layer Manager on Hyper-V by using DPM (Dapa Protection Manager), the boot disk fills up due to crash dumps in "/var/crash". | DPM can cause processes within ELM to crash resulting in crash dumps appearing in /var/crash. The system does not currently clean those up. Before backing up the ELM with DPM, shut down the ELM first. Citrix are investigating this issue. | https://support.citrix.com/article/CTX233639 | |
| 90 | When Splunk is installed in a layer you see "Event ID 3" from "unifltr" in the Event Log with error "Unidesk denied an attempt to rename a directory from one of the read only portions of the file system". You can see from the uniservice logs that a snapshot folder within the Splunk directory was trying to be renamed. | The snapshot folder must exist outside of the layer. Create a new layer for Splunk but delete the "snapshot" folder from the layer using "Shift+Delete". This folder will then be recreated in the published image where it can be renamed without problem. | https://support.citrix.com/article/CTX233900 | |
| 91 | When remote browsing VDAs that use an App Layering image, explorer crashes. | Citrix are investigating. | https://discussions.citrix.com/topic/394193-remote-explorer-sessions-disappearing-crashing/ | |
| 92 | When upgrading from Windows 10 1703 to 1709 multiple issues arise with Visio and Cotana. | Resetting the User Layer fixed the issues. | https://discussions.citrix.com/topic/394562-unidesk-410020-windows-10-updates | |
| 93 | When a task is force cancelled in App Layering, such as when you create a new Application Layer, any consumed space that operation takes is not freed up. | Allow all existing tasks to complete gracefully and when delete all files from "/mnt/repository/Unidesk/Packaging Disks". | https://support.citrix.com/article/CTX234410 | |
| 94 | With Elastic Layers and Profile Steaming enabled for Citrix Profile Management, the Start Menu does not open amongst other issues when logged on to the VDA. | Upgrade to App Layering 4.12. If you cannot upgrade at this time, either disabling Profile Streaming for Citrix Profile Management or Elastic Layers for App Layering solves the issue. | https://discussions.citrix.com/topic/394715-elastic-layers-and-profile-issues/ | |
| 95 | When booting an image via Provisioning Services on Hyper-V the Target Device blue screens with error "BNIStack failed, network stack could not be initialized". | Before finalising the Platform Layer edit the Packaging Machine, remove the Synthetic network adapter, add the Legacy network adapter, boot the machine and delete all hidden NICs. Finally finalise the layer. | ||
| 96 | ELM refuses to reboot and on the CLI you see "Welcome to emergency mode". | This usually means the repository local volume is damaged. Follow the CTX article to resolve. | https://support.citrix.com/article/CTX234956/ | |
| 97 | The second time you log on to a VDA, Group Policy settings do not apply. Deleting the profile from the Citrix Profile Management store solves the issue temporarily until you have logged in twice or more. | This issue is caused by a bug between Elastic Layering and Citrix Profile Management. A fix will be provided in App Layering 4.11. | https://discussions.citrix.com/topic/395292-app-layering-gpo-problem/ | |
| 99 | Published image (Unidesk Desktop) or Packaging Machine blue-screens with STOP code 0x75640007. | This means that all of the required layers were not mounted by Windows within 10 minutes. Since layers should appear instantly when Windows boots, assumption is made that there is a problem and a blue-screen is performed so the system can try again. Normally this is due to policies or software that blocks access to removable devices and as such affects virtual disks. | https://support.citrix.com/article/CTX226759 | |
| 100 | When installing the App Layering Agent on a PVS server that has a French Windows OS installed, you receive the following failure message: "An error occured when executing netsh". | Upgrade to App Layering 4.5. | https://support.citrix.com/article/CTX225948 | |
| 101 | You are prompted to reboot due to new detected hardware. | Look in C:\Windows\inf\setupapi.dev.log which should show you the device that caused the reboot prompt. For example, if you have added a second disk, you may first need to create a new Platform Layer and add the second disk to the Packaging Machine so that it is detected and captured in to the layer. |
https://support.citrix.com/article/CTX221746 https://support.citrix.com/article/CTX230767 |
|
| 102 | When attempting to change the C:\ drive letter you receive error "Access Denied". | You can't rename the C: drive when using App Layering. | <a href=" https://support.citrix.com/article/CTX235937" target="_blank" rel="noopener"> https://support.citrix.com/article/CTX235937 |
|
| 103 | You may notice that the contents of one or more of your Elastic Layers disappears during a session. The "ulayersvc.log" file contains entry "Can't find the volume. It will be reattached on the next login". | This means that the layer has been detached from the VDA. App Layering does not know why it was detached however it could be due to a file server disconnect from Windows or somethig else detaching the VHD. | https://support.citrix.com/article/CTX235961 | |
| 104 | You notice that after finalising a layer, some folders are empty rather than being preserved. | Starting in App Layering 4.11, 6 folders are never preserved in a layer. These folders are "C:\Windows\Logs", "C:\Windows\System32\LogFiles\WMI", "C:\Windows\Prefetch", "C:\Windows\Panther\Rollback", "C:\$Recycle.Bin" and "C:\Users\*\OneDrive". | Citrix App Layering 4.11. | https://support.citrix.com/article/CTX236075 |
| 105 | UPM profiles break if App Layering Elastic Layering is enabled on an image. You cannot click on the Start Menu or open programs etc. | Upgrade to App Layering 4.12 or else if on an older version and you cannot upgrade at this time, disable "Profile Streaming" if used, as the Profile Streaming filter driver and Elastic Layering filter driver compete with eachother. | https://support.citrix.com/article/CTX234619 |
|
| 106 | When upgrading the VDA from 7.15 LTSR CU1 to 7.15 LTSR CU2 in a Platform Layer you receive error "Object reference not set to an instance of an object". | Run the upgrade as a local administrator. | https://discussions.citrix.com/topic/394868-xendesktop-ltsr-cu2-object-reference-not-set-to-an-instance-of-an-object-vda/ |
|
| 107 | A BSOD occurs when a user logs off a VDA which has Symantec Endpoint Protection layered. | SEP is flagging App Layering drivers as viruses. This will be resolved in App Layering 4.12. | https://discussions.citrix.com/topic/397218-user-layer-with-sep-14x-gets-bsod/ | |
| 108 | When you have multiple NICs attached to PVS Target Devices, the Target Devices hang shortly after boot. | Upgrade to App Layering 4.12 or as a workaround upgrade to at least App Layering 4.10 and add a "KeepConfigValue" DWORD with a value of "0x1" to "HKLM\System\CurrentControlSet\Services\Uniservice" in your Platform Layer(s). | https://support.citrix.com/article/CTX233779 | |
| 109 | When creating a new layer you find that the writeable disk becomes unwriteable. | There is a registry key called "EnableDenyGP" under "HKLM\SYSTEM\CurrentControlSet\Control\Storage" which controls denying acces to removable disks. If this key is populated, Windows will refuse to allow write access to the Package Disk when editing a layer, which causes the filter driver to be unable to allow any write operations. You need to idenfity what is modifying this registry key, | https://support.citrix.com/article/CTX236681 | |
| 110 | Elastic Layers or User Layers do not mount and in the "Ulayersvc.log" file you see an error like "A virtual disk support provider for the specified file was not found". | Check Group Policy for anything under "Device Installation Restrictions". This error normally means that Windows is being blocked from allowing the required Elastic Layer/User Layer disk from being attached. | https://support.citrix.com/article/CTX236767 | |
| 111 | When using the "Office Deployment Tool (ODT)" to deploy Office 365 the installation appears to complete however within "C:\Program Files (x86)\root\Office16" you see maybe only 20 files instead of over 400. | This bug is fixed in a patched version of App Layering 4.12, and will be part of the 4.13 release. | https://support.citrix.com/article/CTX236824 | |
| 112 | Installing the App Layering Agent throws error "System.MissingMethodException". | Uninstall StoreFront from your PVS server. Both StoreFront and the App Layering Agent use different versions of the same modules. | https://support.citrix.com/article/CTX236862 | |
| 113 | When creating a new version of a Platform Layer (which was previously domain joined), you may find that you cannot log on to the Packaging Machine using domain credentials and receive error "The security database on the server does not have a computer account for this workstation trust relationship". | The simplest solution is to rejoin the Platform Layer to the domain when you encounter this issue. Or if using App Layering 4.12 or later, after creating or editing the Platform Layer, manually set the machine name via "Computer -> Properties". The virtualised registry will then capture this setting, overriding whatever is in any boot disk. Another solution is to disable caching on your Connector. | https://support.citrix.com/article/CTX236900 | |
| 114 | When creating a new Application or Platform Layer, the "Message Queuing" service is stopped on the Packaging Machine. | Disable "QMLog" by setting "LogDataCreated" DWORD to "0x0" under "HKLM\SOFTWARE\Microsoft\MSMQ\Parameters". | https://support.citrix.com/article/CTX237029 | |
| 115 | When logging on to the Enterprise Layer Manager console you receive error "The request from does not have a valid session". | Reset Internet Explorer settings and make sure a number of settings are enabled as per the CTX article. | https://support.citrix.com/article/CTX237135 | |
| 116 | When installing software in an Application Layer, you receive error "the specified path is too long". | Upgrade to App Layering 4.13 which contains a fix for this issue. | https://support.citrix.com/article/CTX237323 | |
| 117 | Creating a PVS connector fails with credential validation errors. | The account used in the connector must have administrator rights to PVS. | https://support.citrix.com/article/CTX237476 | |
| 118 | When creating an application layer you receive error "Failed to add one or more required layers to the cache". | Create a new VMware connector and set the cache to 0GB. | https://support.citrix.com/article/CTX237442 | |
| 119 | MMC consoles do not open on a Packaging Machine. For example, you try to run "services.msc" and receive error "The application was unable to start correctly (0xc00002b8)". | Upgrade to App Layering 4.13. | Citrix App Layering 4.12. | |
| 120 | When publishing an image you receive error "A failure occurred while publishing the Layered Image: An error occurred while compositing the layer or image. Please check the available disk space on the local storage or the size of the target machine". | Assigning more disk space to the OS layer than the disk space assigned to the published image solves this issue. | Citrix App Layering 4.13. | https://support.citrix.com/article/CTX237681 |
| 121 | When publishing an image the task fails with error "A failure occurred while publishing the Layered Image: An error occurred while compositing the layer or image. Please check the available space on the local storage or the size of the target image". | Try expanding the size of the Image Template in case the layers part of this template are larger than the size set on the Image Template. Otherwise, follow the CTX article to regenerate the "$MFT". | https://support.citrix.com/article/CTX237940 | |
| 122 | Elastic Layers fail to mount with error code "1069940707/0xC03A001D". | The SMB share which hosts your Elastic Layers is likely residing on a 4KB sector disk. It instead should reside on a 512-byte sector disk. | https://support.citrix.com/article/CTX222079 | |
| 123 | After upgrading OS Machine Tools, "kmssetup.cmd" runs twice at startup. | There is no danger to running kmssetup.cmd twice, but you still should delete the second instance. Create a new OS Layer version, launch "regedit.exe", navigate to "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\Scripts\Startup", delete the key named "1" which contains a reference to kmssetup.cmd. If the "1" key does not reference kmssetup.cmd, navigate through the keys finding the original one and then finding and deleting the secondary instance. | https://support.citrix.com/article/CTX238316 | |
| 124 | When publishing an image to XenServer the task fails with error "An unexpected failure was encountered while calling XenServer. Error: NO_HOSTS_AVAILABLE Args:". | This occurs when XenServer does not have enough resource to host the VM. Check which XenServer host the Connector in App Layering is using to publish images too. This host may not have enough CPU, RAM, or GPU resource to host the new VM. The VM is powered on during publishing, so needs to have enough resource provided by the XenServer host. | ||
| 125 | When creating or editing a new App Layer after importing a new non-US-English OS Layer, you may receive a boot failure on the Packaging Machine with message "Windows failed to load because the NLS data is missing, or corrupt". | Follow the CTX article to edit the "bootfile.txt" file, adding entries to ".NLS" files that match the language you are using. | https://support.citrix.com/article/CTX238440 | |
| 126 | When adding versions to layers, the task may fail with error "Failed to execute the script. Unable to perform the operation. The Nutanix server has encountered a failure processing the request (500). Error: internal server error. Details: Error occurred while creating Disk image.". | You must configure the Connector to communicate directly to a Nutanix host, and not the Prism Central Server. If using Nutanix AHV 5.6 or 5.7, the Nutanix host must not be registered to Prism Central. For Nutanix AHV 5.8, hosts can remain registered to Prism Central. | https://support.citrix.com/article/CTX238626 | |
| 127 | After publishing an image via an MCS Connector and updating your MCS provisioned Machine Catalog with this new image, the Published Desktop encounters CPU spikes by "VMTOOLSD.exe". | Edit "tools.conf" from "%ProgramData%\VMware\VMware Tools" adding the two lines mentioned in the CTX article. | https://support.citrix.com/article/CTX238677 | |
| 128 | When editing a layer or publishing an image, the task may fail with error "The given key was not present in the dictionary". | Reboot the ELM. If that does not work, check for any existing running tasks, let them complete or cancel them if they have stalled. | https://support.citrix.com/article/CTX238655 | |
| 129 | Importing a certificate PEM file which contains more than one certificate results in denied access to the management console. | Use an SSH client to connect to ELM and resolve the issue as explained in the CTX article. | https://support.citrix.com/article/CTX238556 | |
| 130 | You receive error "The certificate provided is not a valid format for a certificate. Unable to parse the certificate file" when trying to install a certificate on ELM. | This normally means that the certificate contains attributes/additional data that the ELM cannot handle. A certificate normally contains a single "PRIVATE KEY" and one or more "CERTIFICATE" sections. Delete any additional data from this certificate. | https://support.citrix.com/article/CTX238555 | |
| 131 | When adding a new certificate via the App Layering management console, the console seems to crash, however a refresh indicates that the upload never occurred. | Then can happen if the certificate PEM file contains metadata that cannot be parsed by the ELM. Delete any bad data from the PEM file. Normally the PEM file should contain a single "PRIVATE KEY" and one or more "CERTIFICATE" sections. | https://support.citrix.com/article/CTX238554 | |
| 132 | With User Layers in use and trying to install Chrome extensions via GPO or manually, the extensions do not install and Chrome reports the install as being blocked by an administrator. | This turned out to be a firewall issue, blocking the automatic install via GPO, and when pushing out extensions via GPO, you cannot manually install them and get the error saying that the install has been blocked. | https://discussions.citrix.com/topic/398718-chrome-extensions-in-user-layer-not-deploying-via-gpo/ | |
| 133 | After upgrading to App Layering 4.14, Elastic Layers VHDs mount to desktops but nothing shows up in the file system. If enabling compatibility mode, all Elastic Layers work. | In this case the customer had configured the "Userinit" string to fix an old issue and "layerinfo.exe" was being stripped out of the string. This meant that the logon compositing step never ran. | https://discussions.citrix.com/topic/398674-app-layering-414-elastic-layering-not-working/ | |
| 134 | Applications that have been installed do not open when double-clicked in a published image. | This seems to have occured after Octrober 2018 Windows updates, but is not an App Layering specific issue. Recreating the local administrator account that was used to install applications has resolved the issue. | https://discussions.citrix.com/topic/399105-application-install-dissapears/ | |
| 135 | User Layer mounting takes over 4 minutes. | Symantec Endpoint Protection was causing this issue. | https://discussions.citrix.com/topic/399117-414-user-layer-4-minutes-to-mount/ | |
| 136 | After enabling User Layers, Windows Store or local sideloaded applications work after installing them, but do not work after a reboot. | This appears to happen when applications install "AppX" packages as prerequisites, which gets lost after reboot. You will need to run a logon script to repair these files each time. | https://support.citrix.com/article/CTX239157 | |
| 137 | App Layering upgrade fails with errors "One of the configured repositories failed (Unidesk appliance update), and yum doesn't have enough cached data to continue" and "Metadata file does not match checksum". | Extract the App Layering upgrade package again from the downloaded media and copy the VHD upgrade disk to the network file share, replacing the old upgrade disk. If that fails, move the upgrade disk to a different folder under the network share such as the "UpgradeDisks" folder and try an upgrade from that location. | ||
| 138 | App Layering upgrade fails and the "ApplianceUpgrader.log" file shows error "Error: Package: audit-libs-python". | Uninstall the "audit-libs-python" package by running command "yum erase audit-libs-python-2.7.6-3.e17.x86_64". If you see other package dependency check failures, don't remove those packages unless you have a snapshot you can revert back to. | https://support.citrix.com/article/CTX239267 |
|
| 139 | After installing September 2018 Windows updates for Windows Server 2016 in the OS Layer and then applying September 2018 Office updates to the Office Application Layer, two blank shortcuts and one folder appear on the desktop. | Recreating the Office 2016 layer completely resolved the issue. | https://discussions.citrix.com/topic/398401-office-2016-blank-icons/ | |
| 140 | Some applications delivered by Elastic Layers do not run and present a generic "Windows cannot find path" error. | This is resolved in App Layering 4.15. | https://discussions.citrix.com/topic/398859-windows-10-elastic-layer-shortcuts-not-working/ | |
| 141 | You receive error "Unexpected exception occurred. There is not enough space on the disk." when logging on to the App Layering management console. | This happens when the C:\ drive of the computer you are using to access the management console has run out of space. | https://support.citrix.com/article/CTX239542 | |
| 142 | Randomly, Elastic Layers do not load. For example, 25% of the user base are missing a single Elastic Layer after login. | This happened when a specific USB printer was connected to the affected user's thin client at time of login. Creating a new Application Layer and connecting directly to the Packaging Machine with USB printer attached allowed the printer to be fully installed in the layer. This resolved the issue. | https://discussions.citrix.com/topic/399757-elastic-layer-not-loading/ | |
| 143 | Desktops sometimes use the wrong User Layer share or ignore Elastic Layer assignments. | This can happen if you have two ELM appliances pointing to the same folder on your Elastic Layer/User Layer file share. One ELM appliance could write to a JSON file during Elastic Layer assignment for example, and the other ELM could also potentially overwrite it. Make sure each ELM points to a different file share folder. | https://support.citrix.com/article/CTX239743 | |
| 144 | When publishing layers you receive error "A failure occurred while publishing the Layered Image. Failed scanning a directory for files". | One single layer which was added to the Image Template caused this. Recreating the affected layer fixed the issue. | https://discussions.citrix.com/topic/399915-publish-layered-image-error-failed-scanning-a-directory-for-files/ | |
| 145 | If using "Nutanix AFS" in a multi-node cluster, you may get errors such as "STATUS_PATH_NOT_COVERED" when trying to mount the file share from the ELM. | Nutanix AFS appears to use DFS namespace redirection to point you to individual nodes in the AFS cluster, which is not currently supported by the ELM. The only workaround is to point ELM to a specific node in the AFS cluster. | Nutanix Acropolis File Services. | https://support.citrix.com/article/CTX239812 |
| 146 | The Layer Priority Tool fails to test the ELM password and returns error "ELM Password Test Failed". | This error only occurs if the attempt to download a count of layers from the ELM returns 0 or fails. Check "output.txt" on the ELM, and delete it before trying again. | https://support.citrix.com/article/CTX239810 | |
| 147 | After a Citrix Provisioning server failure and eventual rebuild, when creating a Connector in ELM, the PVS server shows twice. | You have to contact Citrix support so that they can remove the duplicate entry from the database. | https://discussions.citrix.com/topic/400306-how-to-delete-pvs-server-registered-within-elm-citrix-app-layering-appliance/ | |
| 148 | After deploying a machine to Azure and powering it on, you find out the NIC is disabled. | The Platform Layer was originally created on a network different to what provisioned machines use. Recreating the Platform Layer on the correct network resolved the issue. | https://support.citrix.com/article/CTX239986 | |
| 149 | One customer is seeing an increase in CPU usage on virtual desktops after an upgrade to App Layering 1812. | https://discussions.citrix.com/topic/400335-increased-cpu-usage-in-recent-versions/ | ||
| 150 | Installing the NVIDIA GRID driver in a Platform Layer does not work. Installing it in the OS Layer does not work either. The NVIDIA control panel does not open. | This appears to be an issue with the filter driver as after disabling Elastic Layering, everything works. Add "C:\Program Files\NVIDIA Corporation\" and "C:\Program Files (x86)\NVIDIA Corporation\" to the "AlwaysOnBoot" multi-string under "HKLM\System\CurrentControlSet\Services\unifltr". | Citrix App Layering 4.15. | https://support.citrix.com/article/CTX241448 |
| 151 | Publishing an image fails with error "A failure occurred while publishnig the Layered Image: Failed scanning a directory for files". This happens after an App Layer update. | From the ELM log files, a Java directory from a newly created App Layer was causing the problem. Deleting the directory solved the issue. | https://discussions.citrix.com/topic/400048-a-failure-occurred-while-publishing-the-layered-image-failed-scanning-a-directory-for-files/ | |
| 152 | When building a Platform Layer, the Packaging Machine cannot be power managed. For example, issuing a restart to the machine does not always work or there is a long delay in processing the request. | The "Enable Fast Logoff" option which was set withn Workspace Environment Management and applying to the Platform Layer caused this issue. | https://discussions.citrix.com/topic/400232-no-power-control-shutdownrestart-in-layers/ | |
| 153 | After applying Windows updates and updates to UWP applications such as "Sticky notes", the applications when launched show error "The data area passed to a system call is too small". The applications launch fine when editing layers. | Some Store applications simply do not work with User Layers and there is no fix at this time. | https://discussions.citrix.com/topic/399017-win10-1803-uwp-app-errors-the-data-area-passed-to-a-system-call-is-too-small/ | |
| 154 | After an upgrade to App Layering 4 1812, User Layers mount but an error is shown to indicate otherwise. The "ulayersvc.log" log file mentions "The specified share does not exist". | Granting Authenticated Users permission to the json files that reside on the User Layer share(s) solved the problem. | Citrix App Layering 4 1812. | https://discussions.citrix.com/topic/400755-after-1812-update-cant-connect-to-user-layer/ |
| 155 | With User Layers enabled, new users cannot search anything in the Windows Start Menu. Existing users appear to be fine. | Upgrading to App Layering 1901 and republishing the images solved the problem. | https://discussions.citrix.com/topic/400896-windows-search-service-runs-but-searching-start-menu-and-such-returns-no-results/ | |
| 156 | When logging on, User Layers do not mount and users receive error "The Layer disk is invalid because it contains an unrecognized volume (The system cannot find the path specified)". | The share that stores User Layer disks had a Hard Quota configured against it. The quota was increased. | https://discussions.citrix.com/topic/400856-unable-to-attach-user-layer-the-layer-disk-is-invalid-because-it-contains-an-unrecognized-volume-the-system-cannot-find-the-path-specified/ | |
| 157 | After installing "CrowdStrike Endpoint Protection" into an Application Layer, USB functionality is broken. | Installing CrowdStrike in the Platform Layer solved the problem. | https://discussions.citrix.com/topic/400922-crowdstrike-layer-and-usb-devices-not-working/ | |
| 158 | Windows 10 Plartform Layer cannot communicate with the KKMS server after running "slmgr.vbs /ato". | The wrong KMS host key was installed on the KMS server. | https://discussions.citrix.com/topic/400721-w10-platform-layer-cant-reach-kms-server/ | |
| 159 | After selecting to send a batch of print jobs to a secure printer, some of the jobs appear missing and as a result do not print as a user swipes their badge to print their jobs. | This is will be fixed in App Layering build 19.1.0.20, which releases after App Layering 1901. | https://discussions.citrix.com/topic/400748-network-printing-randomly-not-working-question/ | |
| 160 | After an upgrade to App Layering 1901 and upgrading the Machine Tools, KMS Office activation is not triggered at machine startup. | In your OS Layer, roll back "kmssetup.cmd" to an earlier version. This is fixed in the Machine Tools scripts in 1902. | Citrix App Layering 1901. | |
| 161 | Saving a Microsoft Word 2013 or 2016 document produces error "Word cannot complete the save due to a file permission error". | Upgrade to App Layering 1812 or above. | Citrix App Layering 4.14 and 4.15. | https://discussions.citrix.com/topic/398768-2013-word-cannot-complete-the-save-due-to-a-file-permission-error-full-user-layer-only-after-upgrading-to-414/ |
| 162 | Windows Search does not work after enabling and deploying User Layers. | Upgrade to App Layering 1812 or above. | https://discussions.citrix.com/topic/399127-search-catalog-corruption-when-full-user-layers-are-enabled/ | |
| 163 | With User Layers enabled, after logging on you may see error "This system was not shutdown properly. Please log off immediately and contact your system administrator". | Reboot the machine. Also never log on to the machine as a domain user when the machine is in private mode (PVS) or when editing the gold image. If you do and then deploy that image, the user layer service will think the disk has not been properly reverted. | https://support.citrix.com/article/CTX231631 | |
| 164 | The Sophos Enterprise Console shows duplicate computers. These computers use an App Layering published image. | Make sure you have layered Sophos correctly to avoid this. Use the search box of this blog to locate a guide. | https://support.citrix.com/article/CTX235187 | |
| 165 | After an upgrade to 1901, the ELM cannot connect to Clustered Shared Volumes on a Scale-Out File Server. | A recent Linux upgrade has broken Scale-Out File Server support. This is resolved in 1903. | Citrix App Layering 4 1901. | https://discussions.citrix.com/topic/401126-smb-mount-to-csv-share-not-possible-after-upgrade-to-elm-1901/ |
| 166 | After an upgrade to 1901, when creating an App Layer and selecting to include a domain-joined Packaging Layer for creating layers, the Packaging Machine is not joined to the domain. | Citrix App Layering 4 1901. | ||
| 167 | When logging on you receive message "We were unable to load the required configuration files. You may not be able to access some of your applications. And, any changes you make to application settings or data will not be saved. Be sure to save any work to a shared network location". | Granting "Authenticated Users" the appropriate NTFS permissions on the SMB network file share solved the issue. | https://discussions.citrix.com/topic/401333-unable-to-find-the-folder-specified/ | |
| 168 | After an upgrade to 1901, any published image that is booted encounters a BSOD with message "Your operating system couldn't be loaded because the kernel is missing or contains errors" and error "0xc000a004". | Recreating the Platform Layer has solved it. | https://discussions.citrix.com/topic/401339-app-layering-elm-191017-issues-all-new-images-are-failing/ | |
| 169 | Machines are 6 hours ahead of time when provisioned by App Layering. | Make sure your Platform Layer is joined to the domain, so it can retrieve the correct time, or else create a "RealTimeIsUniversal" DWORD with a value of "0x1" under "HKLM\System\CurrentControlSet\Control\TimeZoneInformation". | https://discussions.citrix.com/topic/401596-windows-10-time-off-by-6-hours-on-any-new-machine/ | |
| 170 | On subsequent logons the Calculator and other UWP applications disappear or corrupt. | Disabling the cache and recreating any of the corrupted layers has resolved this. Citrix will be required to come up with a fix without disabling caching. | https://discussions.citrix.com/topic/401380-universal-windows-platform-apps-using-upm-and-1709/ | |
| 171 | "OneDriveMapper" script does not work when run from a machine provisioned from App Layering. | On the App Layering image, the "Web Client Network" provider order was missing from the Network Providers list. A Group Policy Object was created to populate the "ProviderOrder" string under "HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order" with the value "PnSson,PICAClientNetwork,RDPNP,LanmanWorkstation,webclient". | https://discussions.citrix.com/topic/401829-onedrive-script-mapper-issue-on-non-persistent-vdi-machines/ | |
| 172 | Running "ngen /update" on a layer takes a long time to complete and consumes the majority if not all free disk space. | When disabling caching on the Connector, NGEN operations run quickly. It only appears to be an issue when the packaging Connector is configured for caching. | https://discussions.citrix.com/topic/400964-ngen-filling-up-app-layers/ | |
| 173 | With Symantec Endpoint Protection in use, User Layers take up to 4 minutes to mount. | Edit the "Virus and Spyware" policy that is applied to the OU where your VDAs reside. Make sure that settings "Enable Virtual Image Exception for Auto-Protect" and "Enable Vittual Image Exception for Administrator-Defined Scans" are checked. | Symantec Endpoint Protection. | https://discussions.citrix.com/topic/399117-app-layering-user-layer-4-minutes-to-mount-with-sep-142/ |
| 174 | When installing "Oracle Database Client 11g" the installation becomes stuck. | This is resolved in 1905. | Oracle Database Client 11g. | |
| 185 | The Start Menu encounters issues when Citrix Profile Management and Elastic Layers are used together. | This is resolved in App Layering 4 1905. | ||
| 175 | After upgrading from Windows 10 1703 to 1803, some applications such as "mstsc.exe" and "iexplore.exe" do not run. Copies of these executables reside in the User Layer which is the problem, and they need to be deleted. | During a major Windows upgrade, the User Layer is searched for particular files (such as mstsc.exe and iexplore.exe) in order for them to be removed. A database of strategic files is used for this operation. In this case, it didn't work. It appears only one User Layer was affected. | https://discussions.citrix.com/topic/402305-after-windows-10-upgrade-system-files-saved-on-userlayer-conflict-with-os-update/ | |
| 176 | After importing an OS layer, Windows Defender folders under "Program Files" and "ProgramData" are empty. | Publishing an image smaller than the OS layer caused this. This may be fixed in App Layering 4 1903. | https://discussions.citrix.com/topic/402316-windows-defender-folder-empty/ | |
| 177 | Multiple OST Outlook files are created in the User Layer, causing free disk space issues. | https://discussions.citrix.com/topic/402258-outlook-365-multiple-ost-files/ | ||
| 178 | You cannot start applications such as Photos, Calculator, Sticky Notes. | Edit "C:\Program Files\Unidesk\Uniservice\bootfile.txt" and add "C:\Windows\System32\drivers\wof.sys" to the end of the file. A future fix will apply to only new OS layers. | https://support.citrix.com/article/CTX250078 | |
| 179 | When looking at the name of a published image, there may be two to three digits appended to the filename before the date and timestamp. | Use "sudo" to manipulate the data as needed, as outlined in the CTX article. | https://support.citrix.com/article/CTX249923 | |
| 180 | After setting "Automatically manage paging file size for all drives" in a Platform layer, the setting is unchecked when booting from the published image. | Citrix are able to reproduce the issue. | Citrix App Layering 4 1901 & 1902. | https://discussions.citrix.com/topic/402304-turning-on-windows-paging-filevirtual-memory/ |
| 181 | Office 365 will not install on a Packaging Machine and you receive error "30016-4". | Upgrade to App Layering 4.3 or later. | Citrix App Layering 4.1 & 4.2. | https://support.citrix.com/article/CTX225860 |
| 182 | Office activation is not working after an update to Windows 10 1809. | "C:\Windows\Setup\Scripts\kmsdir\kmssetup.cmd" was missing after the upgrade, and other scripts were missing from the "kmsdir" folder. | https://discussions.citrix.com/topic/403122-office-layer-broke-after-re-doing-1809-update/ | |
| 183 | On a Windows 10 virtual machine, the "Shutdown to Finalize" shortcut is missing from the desktop and a number of files are missing from "C:\Program Files\Unidesk". | Recreating the OS layer worked. | https://discussions.citrix.com/topic/402995-missing-shutdown-to-finalize-on-desktop/ | |
| 184 | Citrix Profile Management profiles corrupt if Elastic Layers and Profile Streaming are both enabled. | Contact Citrix support for a hotfix. | Citrix App Layering 4 1903. | https://discussions.citrix.com/topic/402953-citrix-vda-1903-with-applayering-profile-streaming/ |
| 186 | Start Menu tiles appear missing. | This is resolved in App Layering 4 1905. | ||
| 187 | Clicking the Start Menu does nothing for a couple of minutes when AppSense is used with App Layering. | Disabling the "UWPBridgeHook" solved the problem. | https://discussions.citrix.com/topic/402109-appsense-published-image-windows-10-start-menu-issue/ | |
| 188 | On second logon, a black screen appears for around 4 minutes and the following Event Viewer logs show an error opening the "EDB.chk" TileDataLayer database file. Also, the Start Menu does not work. | Contact Citrix for a private fix. | Citrix App Layering 4 1903. | https://discussions.citrix.com/topic/403101-server-2016-start-menu-inaccessible/ |
| 189 | During the creation or updating or layers, virtual machines are created and deleted as normal from the host, but this results in failed objects in the SCVMM console. | App Layering has no understanding of SCVMM so there is no way to interface with it. | https://discussions.citrix.com/topic/403437-scvmm-fills-up-with-missing-objects/ | |
| 190 | Publishing an image to a Citrix Provisioning server fails and the logs show "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. (Exception from HRESULT: 0x80070422)". | The "BITS" service was disabled. | https://discussions.citrix.com/topic/403442-publishing-an-image-to-pvs-fails-hresult-0x80070422/ | |
| 191 | After an upgrade of the VDA to 7.15 LTSR CU4 and an upgrade of the ELM to 1905, KMS activation is not working. | Building a new OS layer and Platform layer got around this problem. | https://discussions.citrix.com/topic/403497-server-2016-xenapp-server-with-pvs-platform-layer-constantly-reboots/ | |
| 192 | Scale-Out File Server does not work on App Layering 4 1901 or 1902. | Upgrade to App Layering 4 1903. | Citrix App Layering 4 1901 & 1902. | https://support.citrix.com/article/CTX256124 |
| 193 | With full User layers in use, Windows Explorer consumes a lot of CPU and desktop performance is degraded when Windows Personalization policies are configured. | Upgrade to App Layering 4 1905. | Citrix App Layering 4 1901. | https://support.citrix.com/article/CTX256710 |
| 194 | Machines sporadically hang at "Getting devices ready" when booting when Symantec Endpoint Protection is part of the image. | The wrong Target Device software was installed in the image, which did not match the version of the PVS servers. | https://support.citrix.com/article/CTX256637 | |
| 195 | Opening and reading Event Viewer consumes a lot of CPU when creating an App or Platform layer. | https://discussions.citrix.com/topic/403585-app-layer-of-platform-layer-eventviewer-cause-cpu-spike/ | ||
| 196 | When using App Layering in Azure, you receive error "The client does not have authorization to perform action 'Microsoft.Storage/storageAccounts/read' over scope '/subscriptions/". | This was resolved by assigning "Contributor" permissions as per Citrix documentation. | https://discussions.citrix.com/topic/403750-machine-creation-for-azure-connector-does-not-have-authorization-to-perform-action-microsoftstoragestorageaccountsread-over-scope/ | |
| 197 | With Elastic Layers enabled and FSLogix in use, new profiles are not created or existing profiles are not receiving any new changes. | Set the "frxdrvvt" service altitude to "138010", under "HKLM\System\CurrentControlSet\Services\frxdrvvt\Instances\frxdrvvt\Altitude". | https://discussions.citrix.com/topic/394715-elastic-layers-and-profile-issues/ | |
| 198 | Office randomly crashes on one VDA per day with an error in Event Viewer such as "Faulting application name: WINWORD.EXE" and "Exception code: 0xe06d7363". | Rebuilding the Office layer using the latest OS layer version has resolved this issue. | https://discussions.citrix.com/topic/404012-office-applications-crashing-randomly-office-365/ | |
| 199 | When using User layers, when adding Chrome extensions error "Could not install package: 'COULD_NOT_GET_TEMP_DIRECTORY'" is received. This issue appears to have started with App Layering 4 1905. | Mulitple customers affected. | Citrix App Layering 4 1905, 1907. | https://discussions.citrix.com/topic/404118-chrome-extensions-could_not_get_temp_directory/ |
| 200 | Publishing a new image fails with error "The file copy was aborted after 5 transient errors". | Replacing the ELM certificate resolved the problem. | https://discussions.citrix.com/topic/404137-elm-195027-failing-on-copying-image-to-filestore/ | |
| 201 | Virtual Machines were configured with old statically assigned DNS IP addresses, even after removing them. This only happens to PVS provisioned machines with App Layering images. | It turns out that Citrix Provisioning was being used to deploy the machines and the Boot Device Manager ISO has static DNS entries configured, which was then applying to the machines. | https://discussions.citrix.com/topic/404273-app-layering-image-being-assigned-static-dns-ips/ | |
| 202 | When publishing an image from App Layering, the published virtual machine contains an LSI SCSI controller, even though the Template Machine specified in the Connector was set to use Paravirtual. | App Layering does not support Paravirtual SCSI controllers | https://discussions.citrix.com/topic/404368-scsi-controller-vmware-paravirtual-not-switching-to-lsi-logic-sas/ | |
| 203 | Adobe Reader, specifically the "RdrCEF.exe" process, is causing machines to blue screen. | The fix was to disable Elastic Layering, however a hotfix has been released to address this issue. | Citrix App Layering 4 1906. | https://discussions.citrix.com/topic/404031-rdrcefexe-crashing-vda-with-bsod-stop-0xa/ |
| 204 | When attempting to create your first Connector, you receive a "This page can't be displayed" error in Internet Explorer. | Reboot the ELM. Sometimes the Connector processes don't start correctly on the very first boot of ELM. | https://support.citrix.com/article/CTX223531 | |
| 205 | When logging in to a VDA with User Layers enabled you receive error "The system was not shutdown properly". In the ulayersvc log file you see error "Not mounting user layer because O/S disk was not reverted". | This can occur when the machine is non-persistent but not rebooting between sessions. |
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