-
Posts
776 -
Joined
-
Last visited
-
Days Won
39
Content Type
Forums
Articles
Labs
Videos
TechZone
Citrix Community Articles
Events
Profiles
Posts posted by Jeff Riechers
-
-
What are the variables assigned to the Desktop Group? You will have to check via powershell.
Get-BrokerDesktopGroup | Citrix Virtual Apps and Desktops SDK
-
What clients are users using?
If you check in Director does it show the clientname there?
-
What do the log files show? It could be they aren't empty enough for a compaction.
-
Can confirm, seeing this on ios 17. LTSR 2203 CU3 backend.
Could be that Director doesn't have information on that new version of OS.
I will finish setup on my lab 2308 environment and see if that shows the same.Can confirm this happens with 2308 as well.
-
5 hours ago, Björn Schläfli said:
I think you don't understand me correctly.
I have upm exclusions in use to exclude everything not needed (a user profile is approx. 150 mb in size). Also profiles will be deleted at logoff of course.
example:
user logs in, uses edge browser and has to download some vlc files needed for their work. These files have a size of up to 12 gb. If they choose %temp% as download path (although we set the path to user home drive as recommended setting) these files are downloaded to their local profile copy on the server and of course the write cache is then filled. When the user logs out the local profile is deleted and user's %temp% will not be written to profile share because it's excluded.
The problem here occurs while the user is actively working on the server and writing files to his profile. I cannot remove write access to his profile ? and I cannot set the download path as a must because some of theme need to be able to choose where they want to save downloads.
Is this more understandable?
We got you. So if users are breaking out of locations you have selected for things, you may just have to boost the size of the writecache drive. I had to do that recently for a customer that worked with monstrous data sets. No amount of redirection worked. Bumping up the writecache drive and thin provisioned in the hypervisor was the only fix.
-
Use the Exclusion list options to exclude those temp files out of the profile.
Setup UPM to delete any local cached profiles at logoff.
Also with the larger delta changes with non-persistent images, I have taken to making the writecache drive match the c:\ drive 100%
-
What is the horsepower on the endpoint? Blurring will add a lot of processing from the endpoint, and if they are on a thin client it might experience more load.
-
In the local WEM agent logs do you see it applying the setting? And if you try launching the exe does it attempt to elevate?
Also make sure you use a published desktop as this feature does not apply to Citrix virtual apps.
-
Do they need to run Citrix Workspace in your PVS image? If not just remove it.
The Cicero error is from the MS Office Speech and Handwriting Recognition function.
-
Rebuilding my home lab with terraform and 14.1. I see that the 14.1 most recent build does not include any location databases in the binary.
I have not checked the previous 14.1 builds.
-
Whats the share permission for the share? If set to Change, try taking it to Full Control and see if that fixes it. It something with how upm creates a lock for the container.
If that does fix it, then open a support ticket so they can do a similar hotfix to what fixes the newer versions.
-
But that's the thing, you can't just do a pass through for Citrix. It requires the full deployment. Either cloud, or on-premise connectors and storefront. And Gateway is only if you don't have a VPN for remote access. If everyone is local or vpn, then you don't need gateway.
It's not like how you can direct RDP to a machine without an RDP broker.
-
Check the share permissions on the profile share. With 2305 I found a bug that if users don't have full control to the profile share containers didn't work, since most shares were change level rights containers were broken. They fixed it with a private hotfix for 2305, and included that fix in 2308.
CU8 might have had the same issue.
-
If your environment isn't 24x7 and your images are non-persistent, you can schedule out of hours reboots to flush the system.
-
Those ports should be locked down on the firewall to only allow communication between the NetScalers, this will mitigate any security questions.
-
Citrix does not recommend or support expanding the hard drives. Instead mount a secondary drive and it will get /var/crash mounted there.
-
1
-
-
This is part of the Citrix Virtual Geolocation Device. It looks like some metro application has reset file association on this device service and it is popping this message.
Dig through the registry and see if you can see that referenced somewhere.
-
Is this a non-persistent image? If so, make sure to run an agentcacheutility.utility -refreshcache before you shut it down for deployment. That does wonders for my WEM deployments as if there aren't a lot of changes to the WEM settings the agent will have a fully populated cache to work from.
-
That the Citrix Provisioning versions. Not the VDA.
You would have to clone the PVS disk and upgrade just the VDA software on the image. Then create a new catalog for it. Unless you are using versioning with a test layer.
-
You're asking for something that usually gets scoped out as a 20-40 hour to start with as a project with most vendors.
You need to setup Delivery Controllers, Storefront connections, VDA configuration on Terminal Server, NetScaler Gateway if you want internet based connectivity. This is for an on-premise deployment.
If you want to go Citrix Cloud, they will handle the Controller database, Storefront and gateway, but you must configure cloud connectors, VDA configurations, and cloud configurations.
You are basically replacing the whole brokering and access to your environment to a new vendor.
-
That's the storefront version, but you should update the VDA on the 2019 image to the latest version, and check out this article for specific grey issues.
Troubleshoot Gray or Black Screen (citrix.com)https://support.citrix.com/article/CTX463357/troubleshooting-gray-or-black-screen
-
I've had 1912 wem talking to 230x versions. Not sure about that 2 versions back limitation.
-
1
-
-
What all are you doing on the WEM system? If you are doing UPM performance logging, that needs to have the DB to write too.
If you are just configuring actions, those should be cached, but only if you have it setup to work from the cache. And the cache has been updated on the base machine with the latest info.
-
Has the HTML5 client been updated on storefront to the latest versions? Client drive mapping is a relatively new function.
Environment variable clietname for published apps not found
in XenApp 7.x
Posted
This was removed from the environment variables in 2019 and 2022. So, your best bet is to grab it from a registry query.
It looks like clientname was only available on 2016 for local users, not domain users at some point from software updates.
If you are scripting with powershell, this might work for you.
$sessionID = (Get-Process -PID $pid).SessionID
$sessionCLIENTNAME = (Get-ItemProperty -path ("HKCU:\Volatile Environment\" + $sessionID) -name "CLIENTNAME").CLIENTNAME