App Layering – App Layers, Image Templates, and Publishing

Last Modified: Nov 5, 2017 @ 8:27 am

Navigation

Create App Layer

Note: Citrix App Layering does not isolate applications. If you need isolation (e.g. multiple versions of Java), consider implementing Microsoft App-V. Citrix App Layering merges the layers without isolation.

  1. See Citrix CTX225952 4.x Layering Best Practices
  2. In the ELM Management Console, go to the Layers tab.
  3. Right-click in the grey, and click Create App Layer.
  4. In the Layer Details page, give the layer a name and version. Since the App Layer is tied to the OS Layer, it’s a good idea to include the OS Layer name in the App Layer name.
  5. Give the layer a Max Size. The layer disk created for the vSphere Packaging Machine is Thick Provisioned. Click the down arrow.
  6. In the OS Layer page, select an OS Layer. An App Layer created for one OS Layer cannot be used with another OS Layer. Click the down arrow.
  7. In the Prerequisite Layers page, you can select additional layers to include in your packaging machine. If there are no dependent layers, just click the down arrow.
  8. In the Connector page, select a vSphere connector, and click the down arrow.
  9. In the Platform Layer page, if you are creating the App Layer on a different hypervisor than originally used for the OS Layer, you can select the Platform Layer for the new hypervisor. If the hypervisor has not changed, just click the down arrow. The hypervisor can also be changed when publishing the Image Template later.
  10. In the Packaging Disk page, give the .vmdk file a name, and click the down arrow.
  11. In the Icon Assignment page, select an icon, or upload a new one, and click the down arrow.
  12. In the Confirm and Complete page, click Create Layer.
  13. At the bottom of the page, open the Tasks panel.
  14. Click the information icon next to the running task.
  15. Eventually the task will finish deploying the Packaging Machine.
  16. In vSphere Web Client, find the new Packaging Machine (in the PackagingVMs folder in the Layering VM folder), open its console, and install your app normally.
  17. See Layering Recipes for some application install instructions.
  18. Citrix CTX226984 App Layering/Unidesk: The list of Windows Updates is usually wrong in app/platform layers and published images/desktops.
  19. Antivirus can be installed on an App layer. See Deploy anti-virus software at Citrix Docs for instructions for the following:
    • Symantec
    • McAfee
    • Trend Micro
    • Sophos
    • AVG
    • Kaspersky
  20. User settings are not captured in an Application Layer.
  21. Domain Join – CTX224668 How to install applications that require joining the domain with Citrix App Layering – In summary, you can join a layer to the domain while packaging, but you must remove it from that domain before finalization.
  22. For Office, put all Office apps in one layer.
    1. Print to OneNote does not work in Elastic Layers.
  23. For Office 365 Click-to-run activation:
    1. After Office Click-to-run is installed, for all OSs other than Windows 7, run C:\Windows\Setup\scripts\Office2013Windows81_PREP.cmd as Administrator.
    2. In App Layering 4.6, Optimize.hta and Office Activate.cmd can handle Office 365 Click-to-run activation. For 4.5 and older, see Rob Zylowski at Office Activation Scripts for Office 365 at Citrix Discussions, to download these scripts . Also see O365 Office 2016 click to run online activation at Citrix Discussions.
    3. Run Optimize.hta from an elevated command prompt.
    4. Scroll down to J, check the box next to Process Office 365, and click Save Settings A-K.
    5. This creates a file called ProcessOffice365.txt.
    6. See Citrix CTX224566 Unidesk Recipe for Office 2016: Using Shared Computer Activation From Office 365 for more licensing guidance.
  24. For Office Volume License activation:
    1. From Citrix CTX224900 Windows / Office 2016 KMS not activating in App Layering images (MCS Image Prep OS Rearm Failed): Run Optimize64.hta from an elevated command prompt.
    2. Configure item H, and Save the settings.
    3. For all OSs other than Windows 7, run C:\Windows\Setup\scripts\Office2013Windows81_PREP.cmd as Administrator.
    4. Then rearm Office by running C:\Program Files\Microsoft Office\Office16\OSPPREAM.exe as administrator.
  25. When you are done installing your app, finalize the layer:
    1. George Spiers Citrix App Layering Preparation Script: runs a number of tasks to clean out temporary folders, clear out Event Log entries, remove ghost devices from Device Manager, etc.  💡
    2. Double-click the Shutdown for Finalize icon on the desktop. If it finds issues, it will tell you what to do (e.g. reboot needed). Otherwise, it will shut down the VM.
  26. After the machine is shutdown, in ELM Management Console, go to Layers > App Layers.
  27. Right-click the Layer that is currently being Edited, and click Finalize.
  28. In the Script Path page, if you embedded any scripts in the layer, specify the path. Otherwise, just click the down arrow.
  29. In the Confirm and Complete page, click Finalize.
  30. You can view the running tasks in the bottom window pane.
  31. It will eventually finish and say Deployable.

Windows Updates – From Gunther Anderson at Unable to update O/S version. (ELM reverts back to older version) at Unidesk Forums: “Generally, the list of updates is unreliable anywhere except the layer where the updates were installed. If your OS layer says the updates were installed, then they were. The actual list (the list is not the same as the actual updates) tends to get stepped on by your other app layers, since they remember the updates list from when they were originally created. With all of your app layers trying to set their own personal misunderstanding based on when they were initially created, what winds up in the published image is not a good reflection of any reality. However, the information from the OS layer is correct. Likewise, the list of Office updates shown in the Office layer is correct even when the list of Windows updates shown in the Office layer is not.”

Image/Template

  1. In the Management Console, go to the Images tab.
  2. Right-click in the grey, and click Create Template.
  3. In the Name and Description page, give the Template a Name that indicates the OS Layer, Platform Layer, and App Layers. Then click the down arrow.
  4. In the OS Layer page, select an OS Layer, and click the down arrow.
  5. In the Application Assignment page, select zero or more applications. Any App Layer you select here will be merged into the machine pre-boot. Elastic Layers are assigned later. Click the down arrow.

  6. In the Connector page, select a Connector for the platform you want to push this image to. If publishing to MCS, select a vSphere Connector, and click the down arrow.
  7. If you are publishing to PvS, and if you don’t have a PvS Connector, click New.

    1. From Connector Configuration & Optional Script (PVS) at Unidesk.com.
    2. In the Choose a Connector Type window, select Citrix PVS, and click New.
    3. For info on the other connectors, see Connectors for publishing (vSphere environment) at unidesk.com.
    4. A new tab opens.
    5. Give the Connector a name. This Connector points to one PvS server, and one vDisk store, so the name should reflect that.
    6. The Console field contains the list of registered App Layering Agents running on PvS Servers.
    7. Enter credentials of a service account that is an administrator in PvS. Click Check Credentials.
    8. Scroll down. Use the drop-downs to select the vDisk store and other vDisk settings. Click Test.
    9. On the bottom, click Save.
    10. On the left, click Script Configuration.
    11. If you installed a PvS Connector Script, you can specify it here.
      1. Citrix CTX226060 Citrix App Layering 4.x: PVS Connector Script to Convert VHD to VHDX – a script that can convert the published VHD file to VHDX, and add it as a Version.
      2. Citrix CTX226062 Citrix App Layering 4.x: PVS Connector (BootPrivate) – a script that provides a mechanism to modify the vDisk mode to Private, Boot the vDisk on a pre-defined target so that it can run pre-defined layer scripts, the scripts shut down the target, the script waits for that shutdown then switches the mode back to standard.
    12. Click Save when done.
    13. Then click Close.
    14. Back in the Connector page, select the PvS connector, and click the down arrow.
  8. In the Platform Layer page, select one Platform Layer, and click the down arrow. For PvS, make sure the Platform Layer includes both VDA and PvS Target Device Software.
  9. In the Layered Image Disk page, give the .vmdk file a name, specify a size, and decide if you want Sysprep to run or not. You typically don’t need to Sysprep the image if you’re using MCS, PvS, Composer, or Instant Clone.
  10. If you wish to enable Elastic Layering, select it here. Assignment of Elastic Layers to users is described later.
    1. Note: when you enable Elastic Layering, the published image only gets 20 GB of free space due to the addition of a writable partition. See Disk space of the published VM at Unidesk forums.
    2. From Rob Zylowski at XenApp Image Template Application Assignment vs Elastic Delay at Citrix Discussions: “There is a 5-8 second penalty just for turning on elastic layering. But its not a straight x seconds per app because the mounts run in parallel. However more apps do take longer. What can have more of an effect is if the app has a service. We have to mount the disk, read it and then start the service before we allow the logon to ensure that the service is available if your logon actually needs it. There is a log at c:\programdata\unidesk\logs that will tell you the time associated with mounting and starting elastic layers so you will know how much of the logon impact is due to elastic layering.”
    3. The path to Elastic Layers can be overridden by setting HKEY_LOCAL_MACHINE\SOFTWARE\Unidesk\ULayer:RepositoryPath on the published machine. See DFS path and Elastic Layers at Citrix Discussions, and CTX222107 You can change the Elastic Layer repository in the registry without reimaging (4.x).
  11. As of App Layering 4.2, User Layers for Windows 7 and Windows 10 (Windows Store disabled) is a Lab feature that can be optionally enabled at System > Settings and Configuration > Labs.
    1. User Layers have the same application compatibility limitation as Elastic Layers.
    2. Storage Locations for User Layers are configured at System > Storage Locations.
    3. The default size for User Layers is 10 GB. You can change this size by setting HKLM\Software\Unidesk\Ulayer\DefaultUserLayerSizeInGb on the managed machines. Source = Understanding Elastic Layering > Scaling (tab) > User Layer Size.
  12. As of App Layering 4.6, Office 365 Layers is a Lab feature that can be optionally enabled at System > Settings and Configuration > Labs. For details (including limitations), see David Wilkinson at Citrix Application Layering – Office 365 User layer.  💡
  13. Click the down arrow.
  14. In the Confirm and Complete page, click Create Template.
  15. The Image is then displayed as Publishable.

Publish Image

  1. Right-click a publishable image, and click Publish Layered Image.
  2. In the Confirm and Complete page, click Publish Layered Image.
  3. Open the Tasks pane, and click the information icon to view details of the running task.
  4. If publishing to MCS (vSphere):
    1. In the vSphere Web Client, you’ll find the Template VM under the TemplateVMs folder under the Virtual Machine folder you selected for the Connector.
    2. Citrix MCS creates VMs in the same Folder as the Master Image. You might want to move the Template VM to a different virtual machine folder.
    3. If you edit the VM’s hardware, you’ll see that the disk is Thick Provisioned.
    4. For MCS, in Citrix Studio, create a Machine Catalog using the Template VM as the Master Image.
    5. Notice that MCS creates VMs in the same Virtual Machine folder as the Master Image.
  5. If publishing to PvS:
    1. The image is uploaded to the vDisk Store as a .VHD file (not .VHDX).
    2. And it’s automatically added to the vDisk Store in the PvS Console. You can now assign it to your Target Devices.
    3. CTX226065 Citrix App Layering 4.x: PVS Image Management – choose an image, then list all the targets using that image optionally filtering on one ore more collections, then “promote” the image to all selected targets.

Elastic Layers

From Rob Zylowski at XenApp Image Template Application Assignment vs Elastic Delay at Citrix Discussions: “There is a 5-8 second penalty just for turning on elastic layering. But its not a straight x seconds per app because the mounts run in parallel. However more apps do take longer. What can have more of an effect is if the app has a service. We have to mount the disk, read it and then start the service before we allow the logon to ensure that the service is available if your logon actually needs it. There is a log at c:\programdata\unidesk\logs that will tell you the time associated with mounting and starting elastic layers so you will know how much of the logon impact is due to elastic layering.”

Citrix.com Understanding Elastic Layering – A technical overview of the Citrix App Layering 4.x Elastic Layering Architecture and Configuration details

Citrix CTX227454 App Layering: PVS Cache Disks May Need to Be Larger with Elastic Layering: you may need to add capacity to your Cache Disks and/or Cache Memory reservation on your Target Machines to support App Layering with Elastic Layers. App Layering caches entire modified files, not individual modified blocks.

To assign elastic layers to users:

  1. In the ELM Management Console, go to Layers > App Layers.
  2. Right-click a Deployable App Layer, and click Add Assignments.
  3. In the Select Version page, select an App Layer version, and click the down arrow.
  4. In the Image Template Assignment page, don’t select anything. This page lets you assign this App Layer to a Image Template for pre-boot merging. For Elastic merging/mounting, just click the down arrow.
  5. In the Elastic Assignment page, note any issues that Elastic Fit discovered that would prevent the app from merging elastically correctly. If you’re OK with the issues, click the Assign Elastically button.
  6. Search for a user group you want to assign this Layer to, and check the box next to the group. Click the down arrow when done.
  7. In the Confirm and Complete page, click Assign Layer.
  8. Open the Tasks pane to see the progress while it copies the App Layer to the remote SMB share.
  9. When it’s done, go to the SMB share to see the files it uploaded, including the .json files that contain Layer assignments.
  10. To enable Elastic Layers in machines created from a ELM Image Template, edit the Template (Images), and make sure Elastic Layers is enabled in the Layered Image Disk page.
  11. Note: when you enable Elastic Layering, the published image only gets 20 GB of free space due to the addition of a writable partition. See Disk space of the published VM at Unidesk forums.

  12. Note: if you find that App Layers are conflicting with each other, you can adjust the App Layer priority by using the Unidesk 4 Layer Priority Utility — Experimental tool.
  13. From Citrix Discussions Application from an Elastic Layer as “Published App”? You can publish an elastic app. Simply publish an app, but manually specify the path to where executable would be. The app is mounted before the user logs in, so it will be there when Citrix tries to launch the app.
  14. The path to Elastic Layers can be overridden by setting HKEY_LOCAL_MACHINE\SOFTWARE\Unidesk\ULayer:RepositoryPath on the published machine. See DFS path and Elastic Layers at Citrix Discussions, and CTX222107 You can change the Elastic Layer repository in the registry without reimaging (4.x).

Update Layers

  1. Right-click an App Layer, and click Add Version.
  2. In the Version Details page, enter a new version, and click the down arrow.
  3. In the OS Layer page, click the down arrow.
  4. In the Prerequisites Layers page, click the down arrow.
  5. In the Connector page, select a Connector, and click the down arrow.
  6. In the Platform Layer page, click the down arrow.
  7. In the Packaging Disk page, click the down arrow.
  8. In the Confirm and Complete page, click Add Version.
  9. The task details shows the current progress.
  10. When the Packaging Machine is deployed, you can connect to its console and perform any desired updates. When you are done performing updates, finalize the layer:
    1. George Spiers Citrix App Layering Preparation Script: runs a number of tasks to clean out temporary folders, clear out Event Log entries, remove ghost devices from Device Manager, etc.  💡
    2. Double-click the Shutdown for Finalize icon on the desktop. If it finds issues, it will tell you what to do (e.g. reboot needed). Otherwise, it will shut down the VM.
  11. When done updating the Packaging Machine, right-click the App Layer that is marked as Editing, and click Finalize.
  12. In the Script Path page, click the down arrow.
  13. In the Confirm and Complete page, click Finalize.
  14. View the task details to see the current progress.
  15. To confirm that you have a new version, right-click the App Layer, and click Delete Versions.
  16. You can only delete versions that are not assigned to any Image.
  17. There are two methods of assigning a new version: one image at a time, or multiple images.
  18. To edit one image:
    1. Go to the Images tab. Right-click an Image, and click Edit Template.
    2. Click the Application Assignment page.
    3. Click the plus arrow next to a Layer and select the new version. Then complete the wizard.
  19. To update multiple images:
    1. Right-click the updated layer, and click Update Assignments.
    2. In the Select Version page, select the version you want to assign, and click the down arrow.
    3. In the Image Template Assignment page, select the templates you want to update, and click the down arrow.
    4. In the Elastic Assignment page, if this App Layer is assigned to users, you can update them too. Click the down arrow.
    5. In the Confirm and Complete page, click Update Assignments.
  20. Once an image has a new version assigned, you must republish it.

Export Layers

App Layering 4.3 and newer let you export all layers and versions to the SMB File Share.

  1. Go to System > Settings and Configuration.
  2. In the Labs section, click Edit.
  3. Check the box next to Import and Export Layers, and click Save.
  4. Go to the Layers tab.
  5. Right-click on any layer, and click Export All.
  6. App Layering 4.4 and newer lets you specify a file share for the exported layers.
  7. ELM 4.5 and newer let you select the layers and versions that you want to export. Make your selections, and then click the down arrow.
  8. Review the list of layers/versions it will export, and click Export.
  9. If you look in your SMB share, in the \Unidesk\Exported Layers folder, you’ll see a folder for the OS Layer, and in there, you’ll see a folder for each Platform and Application Layer.
  10. After creating new layer versions, if you export layers again, it will only export the layers/versions that haven’t already been exported.
  11. If you right-click any layer, and click Import
  12. It only imports the layers/versions that are missing.

44 thoughts on “App Layering – App Layers, Image Templates, and Publishing”

  1. Hi Carl.
    Hoping you can help with a challenge around SCCM and Microsoft Endpoint.

    I found a recipe for SCCM (https://support.citrix.com/article/CTX226394?download) which seems fine so we can deploy that in an app layer. How do we ensure that Microsoft endpoint definition updates apply to PVS target thought? Is this not compatible as we cannot put endpoint in an application layer as it is integrated into Windows 2016 OS.

    Also, the OS layer guide recommends disabling Windows update which Endpoint client requires.

    I assume these endpoint definition updates need to apply to the OS disk which is read only so how do we ensure that PVS target can successfully update when Endpoint definition updates become available throughout the day.

    Thanks

    1. Layering recommends a GPO to disable Automatic Updates, but the service is not disabled. I assume a SCCM configuration can still deliver definition updates to the SCCM client.

  2. Hi Carl,

    would you please consider to go more into detail when it comes to publish images to PvS?
    I’m missing there statements about when and where to set up the cache disk configuration.
    For example:
    In order to get PvS caching working properly I need configure the cache disk settings properly within the Layers.
    I assume I need to create at some time an additional disk and at some point I need to configure the required settings for caching, WEM cache settings, Event Log redirection and so on.
    I think this all should be done while setting up the App Layer, correct?
    Also I assume that right after finalizing the App Lauer and shutting down the VM but before uploading it to the CLM appliance I have to remove the cache disk from the VM, correct?

    It’s quite important to get a good guidance to properly combine the different Citrix components, especially when it comes to get CLM, WEM and PVS or MCS properly working all together.
    Just for example some of the questions there that should be answered are:
    Where should I do the promotion of the published images: By using CLM or PvS console? What are the Best Practices there?
    Should I consider to convert the uploaded images from VHD to VHDX and in which cases this doesn’t make sense?

    1. https://support.citrix.com/article/CTX226095 shows how to add a drive to the Packaging Machine. Note, PvS will move the pagefile automatically so you don’t have to worry about that specific component. Other components (e.g. UPM Logs) can be moved by simply pushing down a group policy. The WEM Cache makes sense on D: drive, but WEM is installed in the Platform Layer.

      App Layering pushes the image/template to PvS and adds the vDisk to the Provisioning Services console. You then assign it to Target Devices.

      VHDX is beneficial (fast merges) for PvS versioning, which isn’t needed with App Layering, since each Publish is a new vDisk. Ideally, Citrix should add native VHDX to App Layering, but it isn’t there today.

  3. Hey Carl when using Citrix App Layering and publishing an image we are noticing the image is joined to the domain. We look in the logs of the Norskale agent and it showing trust issues with the domain. I am not sure if one of the layers was not removed from the domain before finalizing. Should the image be joined to the domain before publishing to MCS?

      1. Well yes the platform layer is joined to the domain but when we create that image from all the layers should that image still be joined to the domain?

        1. Maybe not correctly. It’s the domain join registry keys that are important. MCS and PvS should change the machine identity.

  4. Hello, we have used elastic layers but noticed that with only a few elastics mounted the login time become longer. The process of mounted VHD is very fast but it looks the service “User profile service” takes much more time to process when there is about 10 or more elastics layers. Consequently, the whole login process time can takes up to 2 minutes with EL enabled. If we do not use it or if there is only a few elastic assignments then login times takes between 10 and 40 seconds. This was tested with XenApp 7.14 and 7.15LTSR and Windows 2016 as VDA.

  5. Hi carl

    Do you know it is possible to use windows 10 build 1607 and applayering 4.3 also with pvs and pvd? I publish a win10 image over elm and use than pvs xendesktop wizard with static desktop. But that wont work. The pvd disk is empty. Is applayering with pvd disk Supported?

    Regards frank

  6. Hi,

    I have created an Image, which includes an OS-Layer with Windows Server 2016 and Citrix PVS as Connector. So when I start the VM, everything is ok, but when I select “Elastic layering only for application layers” at the image, the VM stucks at booting. I´ve attached an screenshot in here:

    https://discussions.citrix.com/topic/388391-vm-does-not-boot-from-image-when-elastic-layering-for-application-layers-was-selected/#entry1976122

    Can you figure out why it does not function?

  7. Citrix says that elestic layers on XenApp (terminal) servers are nw possible and even with retaining user data according to the lates “hot-adduser-assigned-app-layers-for-xenapp” post
    As far as I know, this has only been possible for Win7 guest OS, but not for Server 2016 based XenApp servers.
    Hast this really changed and does the current 4.2 really already support this or is this a little premature and only something they will provide in future?
    In case it really should be possible with 4.2, Carl, do you have some instructions on how to use this on Terminal Serversand most of all how retaining the user data is working and how it is merged into the user proifiledata?
    Thank you!

    1. User Layers for RDSH are on the roadmap, but I suspect it will be a while before it’s released. They need to get it working on Virtual Desktops first. 🙂

        1. Maybe you’re thinking of general application settings stored in a user profile? That definitely works. Just implement UPM like normal.

          1. No, not in the user profile, because, yes, then UPM would cover this, but I’m thinking about the settings within the program and maybe for example changes in an application’s proprietary database or similar things.
            To get this handled we would need not only a read only layer, but something which is taking care about saving all the intermittent data. Is this what will be working once the announcement in the above link will really be coming true?

  8. Hi Carl,

    i have a strange issue with the applayer in version 4.3.
    I build a applayer with Office 2013 SP1 KMS an published with the elastic methode to the users.
    If a user start a word or excle document from redirect Desktop Folder , he become a flicker issues after closed the documents.
    If the user move the documents into a folder on redirect Desktop an start again it is ok.

    I dont now it is a bug or is this normal ?

    BR,
    Thomas

  9. Hi Carl,

    I am trying to figure out what would be the use case in our environment for Citrix App Layering. We are using XenDesktop 7.14 to provide end users VDI’s and also applications (the XenApp way). The main thing we need to provide is browsers with different Java-versions. We are using vSphere and MCS to deploy both the VDI’s and the Servers providing just the applications.

    Right now we have a different golden images for every Java-version. So we have e.g. Windows Server 2012 R2 with Java 6 Update 60, another Windows Server 2012 R2 with Java 7 Update 80 etc. Same thing with the Desktop OS’s.

    From what I’ve understood, with App Layering (Elastic Layers) it is still not possible to provide different Java versions for the same VDI depending on the user who logs in. So this is not possible:

    User logs in to VDI and get’s Java 6 update 60. Another user logs on to the same VDI and gets Java 7 Update 80. Like you mentioned here, layering does not isolate the applications.

    We also publish browsers with different Java versions (the XenApp way).

    I am just trying to figure out here what benefit would the App Layering bring us comparing to the current model. Any chance you could enlighten me? 🙂

    1. It helps if you have identical applications in multiple images and only want to update the apps once.

      1. Thanks! From MCS perspective the idea is that you can more easily manage the golden images, am I right? So with App Layering you can deploy new golden image which, in turn the MCS will use to deploy x number of new VM’s? Does App Layering help when you need to install patches to the VM’s deployed from the golden image? Is it easier with App Layering, and could you give an example of how the OS Layer is updated?

        1. You can have multiple MCS Catalogs/images based on a single Unidesk OS image. When you update the Unidesk OS image, it updates all of the MCS Catalogs, even if they have different apps layered in.

          1. When you say “update the Unidesk OS image”, are you talking about updating the VM that was published from the ELM, or update the OS layer in the ELM, and then publish an updated layered image (VM) to vcenter.

            In the case of the later, I am not sure how the MCS catalog will use this updated layered image since the VM it creates has a unique name. The snapshot that the MCS Catalog uses is based off of a different VM.

            Can you help me reconcile this?

          2. I meant: create a new version of the OS Layer. Update the Image Templates to use the new OS version. Publish the Image to hypervisor. Then use MCS to update the Catalogs.

  10. Carl,

    Thanks for the instructions! I am getting the error below right after I logged in. Any ideas? I did skipped some of the optional configuration you mentioned.

    Citrix App Layering – Error

    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.

    Unable to find the folder specified.

    1. Do you see the Elastic Layers in the file share?

      Do users have permissions to read the files in the file share?

    1. I don’t think so. And I don’t it’s necessary either since it has no effect on the deployed machines. You should back it up, of course.

  11. Hi Carl,
    I have created 3 App layer .1 MS-Office 2. VLC Player 3. Adove reader
    And assign to domain users through Elastic assignment, User can see and access 1 MS-Office 2. VLC Player but unable to see & Access Adove Reader

  12. Carl,

    What version of VMware vSphere were you running when creating this guide?

    I was trying to use Server 2016 on vSphere 5.5 and keep getting the following error trying to make a platform layer.

    “A failure occurred while deploying the virtual machine. The error is ‘Cannot read property ‘$value” of undefined’ ”

    My initial thought is since im using an older version of vSphere, server 2016 is not an option when deploying a VM and i had to use Server 2012 where it asks about the Guest Operating System version in the initial VM deployment.

    Thanks
    Trent

  13. Hi Carl, how manage the PVS cache disk for target device when using Citrix App Layering? Should I have to add a disk during the platform layer creation?
    Regards

  14. Hey Carl, like everyone else, i think your website really is off the charts! It’s so unbelievably helpful!

    I’ve got a question though: Are elastic layers by default shown to everyone that logs on to the XenApp server?
    I’ve made a template of Win2K12 with PVS tools and made an elastic layer of 7zip.
    I gave the rights of the elastic layer to a test group and made one account member of it.

    But all the AD accounts that log in, see 7zip in Windows explorer.

    Did i miss something? Or is this normal behavior?

    1. Citrix tells me that the context menu handler should be isolated to the users that are assigned to the Elastic Layer. Either there’s a misconfiguration, or a bug. You might have to call Citrix Support.

      1. Thanks.

        Maybe i’ve overlooked something, but the only thing i see is the root folder (c:\program files\7zip), but not the files beneath it. So maybe that’s standard functionality.
        I will ask Jeff Pitsch from Unidesk this upcoming friday (at a seminar where he presents).

        Will give his response here afterwards.. 🙂

  15. Carl, how have you been defining the PVS device collection with overflow disks? Previously you would create a master target, attach a D drive for overflow/persistent folder structure, and then use a PVS device wizard to spin off X total PVS targets using a template based off of the master target. I think when you do publish image #2 operation from the Unidesk console, that new PVS vDisk file has no knowledge of a D drive and pointers to it for persistent folder locations like D:\EventLogs, etc.

    1. Preston, have you managed to figure this out? my write-cache is getting redirected to server instead of drive d and I think my unidesk created image is not aware of my drive d

      1. We pushed the PVS vdisk (cache to server) to 1 PVS target. We then added a D drive on that target using its VM settings and then disk management in the VM. We created necessary redirect folders on it (e.g. D:\spooler). Then we shut it down and created a VM template from it. PVS streamed wizard was then used to generate desktops from it. GPO was used to set the pointers to redirect locations on the D drive (e.g. spooler, event logs).

  16. Spot on as always. Thanks 🙂 When you have published an updated image, you have to go in to Citrix Studio and change machine in machine catalog manually there, correct?

Leave a Reply