Also I worked wiht engineering on this and gave it to them but they have not had time to fully test yest whcih is why they are not public

These started wiht the public ones abd i added tow things hybernate and the ability to auto config the boot diagnostics

Worth noting that Citrix's documentation on creating a Template Spec (I know you can use a VM) is now outdated, with MS removing the 'Add to Library' button/functionality: https://docs.citrix.com/en-us/citrix-daas/install-configure/machine-catalogs-create/create-machine-catalog-citrix-azure.html#create-an-[…]plate-spec. I wound up writing my own PS script to accomplish this task based on the master VM I build. This isn't App Layering related, but I figured since you guys were talking about templates...

🤦‍♂️, I'm reviewing the other engineers stuff, and I'm 90% sure that he couldn't get hibernation working because he used the default Citrix Optimizer template with it disabled.

Finding we are getting "Activate Windows" prompts now on the latest build we've done for our 2016 based images but the Activation script appears to have worked successfully. We are on ELM Version 24.3.2.1021. I've updated the ELM scripts and that seems to be when this started. Going to open the OS Layer as we are also seeing issues with our performance counters as well 😞 . If I run a "slmgr /ato" it immediately activates the VM successfully (in my MCS deployed VDAs). Any ideas? I also saw this in the edocs "Publishing images into environments where both KMS and Active Directory-based activation (ADBA) are being used at the same time causes problems with activation." Is there anything special I should do if ADBA is in place? Select "Do not use KMS" on the image? I'm not sure why this has changed though as I think we have had both for some time. We also have 2019 and 2022 based images that do not seem to have this issue despite the "use KMS" being set.

I don't know the answer to that one. Normally if the log shows activated our good. You could try renaming the c:\widnows\setup\scripts\runato.cmd and the runipkato.cmd files and that will stop our script from activating windows then the ADBA should just work on its own and see what happens.

Can the ELM generate images for Native AVD? The OS layer was created in Azure and should have the AVD bits, I think. I try creating an image template with just an os layer, no platform, but it fails (Encountered an error while trying to delete a file from the file system.) I am setting sysprep to "Generalized Offline" at the template level.

Anyone got Teams 2 working in an App Layer? Getting reports that the permissions get broken when used in this manner....(on a published desktop only)

App Layering 2409 released - major updates, including an ELM OS switch from CentOS to Oracle Linux 8: https://docs.citrix.com/en-us/citrix-app-layering/4/whats-new

All Please note the following from the fixes section of the 2409 what's new because its very important: • "You can only update Microsoft Edge through Windows OS updates now. If you previously used an application layer to deploy Edge, that layer can’t be used in the image anymore, as Edge updates will be ignored. Make sure to keep Edge up to date when updating Windows versions. [UNI-90502] " This means we will no longer save changes that edge makes in an app layer. This is in response to many issue customers have had wiht edge so now you keep it in your OS layer and we ensure it wont bleed into other layers. This also applies to EdWebView2

We're experiencing an issue wherein one of our image assigned app layers is somehow dropping a file when we publish the image template, assign the .vhd to a server in PVS, and restart said server(s). We use the same app layer in a different ELM, from which we export the layer and import into the faulty ELM, and the file is always present in the resulting PVS target. We've mounted the faulty .vhd on the PVS server and the file that has gone missing on the targets is present in the .vhd.

Has anyone deployed Microsoft ATP / MDE on layers by chance? I think I asked that before but dont recall specifics.

@Paul Brown / @Brandon Mitchell: Rehashing a CrowdStrike thread from a while back (https://www.linen.dev/s/worldofeuc/t/16925258/is-anyone-using-crowdstrike-with-app-layering-if-so-any-tric), are you guys still installing CS in an app layer that is domain joined? We have been using the Platform layer, and I'd like to go the app layer route, but if it means joining the layer to the domain, not sure it's worth the effort. Still bonkers to me that this is even a requirement.

Got an issue where the ELM is stuck deleting a layer but it will not finish. I've tried rebooting the ELM and it's still stuck. I'm nervous as if this OS layer breaks all my apps will be useless if i need to rebuild. How can i clear this pending deletion? We also are trying to do the migration upgrade but that fails and I'm wondering if its related.

Citrix App Layering on Nutanix. While this doesn’t cover everything for App Layering, it covers specifics for integration with Nutanix AHV and Nutanix Files. https://portal.nutanix.com/page/documents/solutions/details?targetId=TN-2205-Citrix-App-Layering-on-Nutanix:TN-2205-Citrix-App-Layering-on-Nutanix Slack Conversation

hey guys, this was posted here before (maybe @Rob Zylowski?) but I cant remember exact solution. How do you trigger appv refresh so its available via published apps and not just desktop? I think this was triggered via scheduled task. The packages are on a share, no infra

Anyone seen it where edge when updating in the OS layer doesn't seem to reflect in the final image? We've been doing edge this way for a while (and was working fine) and just now it seems that the update isn't persisting into the final image. For example, my OS layer says 132.x.x.x. and my final image is still saying 120.x.x.x. Any ideas? Very basic image with only 3 apps and a platform layer (no changes in any of them). I haven't tried recreating the platform layer but i assume it shouldn't be necessary.

@Rob Zylowski This CTX article about teams is helpful, but there is an error on the page. The error is the Reg entry under "For UPL deployments" it should say: "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer" not "hklm\Software\Microsoft\CurrentVersionExplorer" I'd normally report it on the page, but the buttons seem to have been removed.

All is anyone using Sentinel One wiht App Layering? If so are you installing it in an app layer?

Do i see correctly that teams in an app layer is not working with windows server 2022? https://support.citrix.com/s/article/CTX692020-new-teams-deployment-guidance-for-app-layering-or-user-personalization-layerupl?language=en_US

Tested to migrate our test ELM to new 24.9.0.1, migration worked fine but I'm experiencing issues with the Network File Share for Elastic Layering. Running a test will take 10 min+, uploading a new layer doesn't work at all. I can see files being updated on the share, and I can also write new files from the mount points on the ELM itself. Have anyone else experienced the same issue?

Does the userlayer repair utility still work with the newer ELM?

<Cross-posted to Automation channel> Has anyone noticed any problems using Chocolatey with App Layered images? When I uninstall or upgrade any Chocolatey packages, the original folder simply stays put on the C: drive. So if I upgrade Paint dotNet from 5.1.4 to 5.1.6, whether through removal/reinstall or simple upgrade, it stays on version 5.1.4. Is this simply because Chocolatey and App Layering can't work together? The original install goes fine - it is the subsequent change or removal that fails.

Applayer Version 24.9.0.1 Hypervisor host XenServer 8.4 Having an issue i can't get beyond after updating the OS layer to 24H2. Have been able to make additional OS layer updates, have been able to create a new platform layer based off this OS layer, but cannot build new app layers. Each time we try the VM boots to this:

Are RSAT only supported in the OS layer with the newer Elm? Asking since not able to build a layer, always get "Something didn't go as planned" on restart of the layer after installing, but adding RSAT to the OS layer works without a problem.

Citrix App Layering 2503 released yesterday: https://www.citrix.com/downloads/citrix-app-layering/product-software/citrix-app-layering-2503.html https://docs.citrix.com/en-us/citrix-app-layering/4/whats-new.html

Elastic layers. Contemplating using them for the first time, but now that teams needs to be in the OS layer it makes Elastic Fit tests for app layers throw errors. What's the guidance here now?

Anyone found a way to deploy Microsoft Teams backgrounds without Premium Addon WITH New Teams on VDI in Citrix with Slimcore? This solution doesnt seem to work on VDI with Slimcore : https://office365.thorpick.de/the-new-microsoft-teams-client-2-1-and-background-images-in-video-calls

Greetings. We recently migrated our ELM to a new server/versions (2409) in Azure. We experienced a few challenges, the latest being firewall port related. In attempting to build a new Windows 11 image, we experienced the following error. We are thinking this also may be port related. I have seen one reference that indicated modifying the TLS 1.2 setting might resolve. Curious if anyone has experienced this. Thanks for the help.

Hi All, We have a customer currently running VMware together with Citrix App Layering (ELM version 24.9.0.1). We are about to start a XenServer POC, where we plan to build a dedicated XenServer pool for Windows 11 VDI workloads. We already have an OS Layer and a number of App Layers built on top of it. VMware Tools are installed in the OS Layer. As a product, App Layering is supposed to be hypervisor-agnostic and able to support multiple platforms using a single OS Layer. My question is: Will this setup work without rebuilding the OS Layer or uninstalling VMware Tools from the OS Layer? Can we simply build a new Platform Layer for XenServer, using the existing OS Layer (which has VMware Tools installed)? Does anyone have real-world experience with a similar situation?