Martin Poirier
-
Posts
34 -
Joined
-
Last visited
Content Type
Forums
Articles
Labs
Videos
TechZone
Citrix Community Articles
Events
Profiles
Posts posted by Martin Poirier
-
-
Yes. When you create an App Layer, the Platform Layer section allows you to choose 'None' (default) or you can choose a platform layer.
-
I'm looking to expand some users user layer size. I intend to control this via a separate OS Layer version, so I can deploy it to one pool only. Based on this article : Deploy user layers | App Layering (citrix.com) I can create a new reg key called DefaultUserLayerSizeInGb here : HKLM\Software\Unidesk\Ulayer. I created that key and set it to 20 (in a snapshot) Deployed to a pool and the new size isn't showing. I even deleted the test user's user layer and that didn't recognize the increased size. Is there something else I'm missing to this?
am aware that I can use the User Layer Management Utility, and it works fine. Its changes though, don't persist if we have to delete a users user layer.
-
Solution was to use a vm template in my connector settings. I created a new VM (no disk), ensured the time was set correctly. I added that VM template to my VMware Connecter settings and now the time is all correct. Still not sure what changed to cause this issue as I've never had a template VM setup since switching to App Layering 4.
-
I'm trying to get a working platform layer so I can create a layer/layer version, add it to a manual View pool so I can connect to through an endpoint (Zero Client) The goal is to get the layer to 'see' a USB device and capture the correct driver. Pre-installing the drivers don't help, windows needs the device to be visible so we can assign the correct driver.
Usually when I've done this, I'll have a platform layer built with just VMware Tools, VMware Agent and domain joined, but everytime I use it, I get a configuration error in View. Which is odd, since its the same platform layer i've used before. I created a new version based of my latest OS layer and updated both Tools and Agent, but to no avail.
I've even taken my production Platform Layer (which I know works), created a version with the options for creating/updating layers and it has the same behaviour.
Is there something I'm missing from this process? This used to work just fine.
Windows 10 VM's, VMware View 7.13, App Layering 23.9.0.1004
-
Vmware View 7.13, Desktop OS WIndows 10 22H2, App Layering 23.9.0.1004.
I started seeing this error recently after re-composing a pool with an image created from App Layering:
After a little while, Composer will re-compose the desktop again and the error will go away and the desktop will compose fine. Any ideas why this error has started showing up in the first place?
Thanks.
-
Office 365 Local Apps layer not working, user unable to sign in. We have just started deploying Office 365 Local Apps. I followed the app-layering recipe (I don't think I missed anything) and created the layer and made a new gold image with it. I have a few users who are testing it, so I moved them to the new pool and several of them are working fine. One user had an a separate issue and we deleted her user layer. Now when she attempts to log into any Office 365 App, she enters in her e-mail address and then the login just closes with no error. We did discover that it appears she is missing the microsoft.aad.brokerplugin. Manually adding it back, solved the issue, however another user layer reset and that change will get reverted. The oddity, is that plug does exist on the gold image. I have ben able to duplicate the issue, so its not just with her account. Did I miss something with the layer recipe? Or is there another issue that might be causing this?
ELM 23.4.0.1007
Horizon View 7.13, linked clones
Win10 21H2
-
No AV in OS Layer (its in the platform layer). I did scrap the version and started over, same result. I also did use ngen eqi 3.
I don't know if this was coincidental or not, but I the datastore the ELM is on was down to 200GB free. I cleared up some old OS layer to get some space back, now the OS layer will finalize. Could that of been the issue ? I didn't see any errors from App Layering.
-
Windows 10, 21H2, May 2023 Updates. App Layering ELM 23.4.0.1007. VMware, vsphere 7.0.3.00500
I'm creating a new version of my OS layer which includes May 2023 updates and two print drivers added. I've completed several reboots, and all Ngen operations are done. When I choose 'shutdown for finalize' The VM restarts then I can watch the processing and at some point, it will just reboot again and bring me back to the logon screen.
Any ideas?
-
I've come across some users desktops that are showing up with activation failures. The odd part is that on the windows 10 activation screen, it says there is no key found. I checked the OS layer, and its activated properly with the KMS key. One a couple of the affected desktops, I added the key and windows activated fine. Any reason why this would happen? I checked some layers that were common to the affected desktops and they are all activated.
-
Does anyone know how Foxit's licensing work? If I buy 20 perpetual licenses (non-subscription) are they one key, or 20 keys? Right now I have 10 Adobe Pro layers with different keys and I'd like to get a PDF editor with just one key and manage the license totals with Elastic Layering.
-
Last month we updated all our desktops to the December 2021 Windows updates. Ever since then, our user's layers have maxed out to their full 10GB. After a while, Windows then reports their free space back to a reasonable 3-6 GB free (10GB user layer). We though it was some odd temp file issue, however, when I take a user layer VHD and scan it with windirstat, it doesn't register even close to the full 10GB. Nothing in that scan points to what is filling up the space.
Any ideas?
App Layering : 21.10.0.1008
Windows 10 20H2 KB5008212
VMware View 7.13
-
I've been working on getting updated from 1909 to 20H2 and in my testing, the start menu is broken for existing users, it won't open when clicked on. No errors, just no response.
Through my testing/troubleshooting I've found that if a user has no User Layer, they can log into a 20H2 desktop with no issues, user layer creates, they can work as normal. If a user with an existing user layer signs in, then the start menu is broken. I can re-produce this consistently.
The other thing that I noticed, if a user (with no user layer) signs into 20H2 first, then tries to sign into 1909, they get an App Layering error 'this user layer was created on a different version of windows'
My thought is that something in the 20H2 update needs to update user files, however, since they don't exist in the OS layer, its breaking something? I have updated App Layering to 21.4.0.1006 and re-did the update from 1909 to 20H2 and still no luck.
Any ideas? I have a case open already, however, I think I stumped them.
-
I have a registry key dealing with skipping KMS activation (some recompose issues in View and they key change is supposed to fix it) Its HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform\SkipRearm = 1.
I set that key in the PL. Once I published the image and deployed a desktop from it, they key went back to 0. Should this be in the OS layer instead? Although other KMS settings (the server) are set in the PL.
-
Just to clean-up and save some space, is there any reason why I can't delete older Upgrade Disks in the AppLayers\Unidesk\Upgrade Disks folder?
-
Thank you Penny ! That did it!
-
I did create a new IM. We didn't have to re-create the datastores, the issue was a host lock on one of the LUN's didn't get released.
They do look correct in the MA setup. Nothing seems out of sorts. I even did a synchronize infrastructure and there are no errors there.
-
Yes, I know 2.9 is out of support and we are moving off of it, we have users on Windows 10 on app layering, but not quite ready for everyone yet.
When I attempt to create a new layer, it fails with this error :
The CachePoint Appliance could not create the boot image. Error is: Failed to reattach disks to the desktop that were temporarily attached to the CachePoint Appliance; export the logs and notify Technical Support that this error occurred.
The vSphere error showing is:
FIle[]/vmfs/volumes/****/IM-1/IM-1vmdk was not found
Nothing in the logs seem to indicate any error as described here https://support.citrix.com/article/CTX233778 (unless i'm looking in the wrong place). I tried restarted all CP's and MA with no change. I also re-created the IM and still had the same issue. I do know that this issue started after a storage issue we had, however, that's been resolved and there are no other issues in Unidesk besides this.
I did notice that when we get the error, the IM's folder gets renamed for some reason. The IM is called IM1 and after the error shows up, the folder is renamed IM1_1 and its now missing the vmdk file.
So if I try again to edit a layer, I then get this error :
The virtual infrastructure failed to reconfigure a virtual machine. Error is: Internal client error: 'Couldn't find the current boot disk in the list of disk'
Which makes sense, since the folder has been renamed.
Any ideas that anyone can remember from the 2.x world ?
I'm on 2.9.3, vSphere 6.0, Win7 32-bit.
-
I figured it out. It wasn't an App Layering issue. The scanner drivers in Windows 10 for some reason don't work with APPDATA being re-directed, hence it was fine in the installation machine (which did have the view agent as a packaging platform layer so I could access usb from the endpoint) and failed when tested on a deployed VM. It was fine in Windows 7, but (surpising no one) something must of changed in Windows 10.
-
We aren't using a PC as an endpoint, we are using HP Zero Clients.
In Unidesk 2 (windows 7) I had created the layer and with my View Agent Layer (vsphere environment) joined the Installation Machine to a pool, connected to it with a zero client with the scanner physically plugged into it to have windows install the drivers and test the software (which works in both Unidesk and App Layering). After finalizing that, I then deployed to any desktops who need that driver without issue.
I did test installing the Alaris software into a Win10 VM and there are no issues. So it doesn't seem to be a VM or zero client issue.
-
I know the title is a little vague, but the issue is it seems that App Layering 4 (v19.10.0.29/ Win 10 v1903) isn't capturing something in a layer.
I am creating a layer for scanners from Kodak and Alaris (same company now, so essentially the same software). My steps when creating the layer are:
- I create the layer with a view agent platform layer (that way I connect to the VM through a zero client for USB driver captures)
- install the Alaris/Kodak software and drivers
- connect the scanner (detected properly and shows in device manager with correct driver)
- go through their built-in scanner tester and can successfully scan
- reboot and finalize the layer
- deploy to an image and publish (am NOT using elastic layering)
- published VM can see the scanner, device manager shows correct driver, but scanner software can't detect the scanner. If I install the scanner software as admin on a VM, then no issues, it works fine.
My assumption is something isn't getting captured and i'm not sure what.
This is the identical process I used in our Unidesk 2.9/Windows 7 world and there are no issues the this software in that environment.
-
I just finally got a chance to rebuild a pool with this fix. It worked great ! Thanks!
-
I have a layer (Velox Radiology Viewer) that has a service that gets created upon software install. The service doesn't show when the layer is elastically assigned. Any reason why this would get captured?
-
In Horizon 7 when I recompose a pool with a new image from App Layering, I noticed that most VM's will come up with an Error state about license activation. They will eventually clear, sometimes it will take a few hours. I'm guessing that after some time, they reach out to the KMS server and activate then continue on. Is this normal behavior?
-
Is there a way to specify certain VM settings when publishing an image ? For example, machine specs, dvd removal etc ?
Teams 2.0 Recipe
in App Layering 4.x
Posted
Similar issue that I'm having. (VMware View, App Layering 23.12, Win10 22H2) I installed teams per: Known issues | App Layering (citrix.com). I published the image as normal, Teams shows up in the image just fine. Once I composed the image to a pool and had a user log in (with classic teams removed, I had it as an elastic layer), Teams wouldn't show up in the start menu.
The solution I found was that any user who had classic teams, I would need to delete their personalization layer, then have them sign in and then New Teams would work correctly. Not the best solution, but it works.