![](http://content.invisioncic.com/m329563/set_resources_3/84c1e40ea0e759e3f1505eb1788ddf3c_pattern.png)
Jeff Gardiner1709159995
-
Posts
17 -
Joined
-
Last visited
-
Days Won
1
Content Type
Forums
Articles
Labs
Videos
TechZone
Citrix Community Articles
Events
Profiles
Posts posted by Jeff Gardiner1709159995
-
-
Try setting the Read & Write Cache on the VDA:
Set-ItemProperty -Path 'HKLM:System\CurrentControlSet\Services\PicAdm\Parameters' -Name EnableCcReadCache -Value 1
Set-ItemProperty -Path 'HKLM:System\CurrentControlSet\Services\PicAdm\Parameters' -Name EnableCcWriteCache -Value 1
You can also change the Packet Integrity Checks per CTX231205 but we didn't need to mess with that to fix our slow transfers.
-
Forget this reply. I read it too fast and thought it said "client" version rather than "OS" version.
I'm sorry.
-------------------------------
You can try this:
Nev
asnp citrix*
$Sessions = Get-BrokerSession -AdminAddress XADDCASP01 -MaxRecordCount 5000
Foreach ($Session in $Sessions) {Write-Host $Session.Username `t`t $Session.ClientVersion} -
If you log onto the defective server via RDP and telnet to itself on TCP 1494 do you get a response?
If that responds, use Quick Launch from another server on the same network to bypass StoreFront and the Gateway. That will help determine which component may be at fault. If Quick Launch fails, it's probably a server problem. If it succeeds, you may have a gateway, StoreFront, ticket server, etc. problem.
The event logs on the XenApp server and StoreFront (if it's on Windows) are usually a great help.
-
It may be worth trying the Receiver Cleanup Utility (https://support.citrix.com/article/CTX137494)
- Run the Cleanup Utiliy
- Reboot
- Install Workspace App again
-
There are a couple possibilities but try this first;
-
Right-click on the Citrix Workspace icon in the system tray:
- Select "Advanced Preferences"
-
Click "High DPI"
- Change the setting to "Yes" or "Use Native Resolution"
If one of those doesn't work, there's another change to try.
Ignore the images below. I tried to delete them but they keep coming back.
-
Right-click on the Citrix Workspace icon in the system tray:
-
It's probably a different exe that's causing the trouble. Try killing some other processes one at a time (not wfshell.exe) until the session terminates.
There are some exe's that are automatically included now so they don't need to be specified in LogOffCheckSysModules (shown below). One that's already included is wfshell.exe. But, CtxMtHost.exe isn't listed so that change was needed if it's one of the troublemakers.
- atok1*.exe
- clipsrv.exe
- conime.exe
- csrss.exe
- ctfmon.exe
- ddhelp.exe
- eventlog.exe
- iatokik*.exe
- iatokqb*.exe
- iatqb1*.exe
- ibdbsch.exe
- imejp98m.exe
- imejpmgr.exe
- imepadsv.exe
- jsvschvw.exe
- lmsvcs.exe
- lsass.exe
- msgsvc.exe
- nddeagent.exe
- nddeagnt.exe
- netdde.exe
- netstrs.exe
- os2srv.exe
- proquota.exe
- screg.exe
- smss.exe
- spoolss.exe
- ssonsvr.exe
- wfshell.exe
- win.com
- winlogon.exe
- wpabaln.exe
- wuauclt.exe
-
2
-
When I've had this, I'd terminate the running processes one at a time until the session ended. Add the last process you terminated just before the session closed itself to LogOffCheckSysModules.
Most of the processes in your screen shot are pretty normal so start with the odder ones (like fontdrvhost.exe).
-
2
-
-
I haven't experienced the problem with Chrome but I do have some apps that need a short delay. In those cases we publish a batch file that has a brief pause before starting the app.
However, based on your description, the built-in DOS commands may not be capable of inserting the delay where needed (between Chrome starting up and inserting the URL). But, you could do this with AutoIT. I have a couple apps that need this.
-
Is this a case where CtxWebBrowser.exe shuold be added to LogOffCheckSysModules?
https://support.citrix.com/article/CTX891671
-
1
-
-
It may be worth disabling Session Sharing so each app gets an independent session:
Set-BrokerApplicationGroup "App Group Name" -SessionSharingEnabled $false -SingleAppPerSession $true
-
We get very similar issues with newer laptops. The instructions below almost always fix it (I'm sorry for the elementary instructions, it's what we send to users who often need more detail than you will). It may not work for your situation but it's easy to test and quick to revert back if necessary.
- Start Windows Explorer (file manager)
- Open the directory C:\Program Files (x86)\Citrix\ICA Client
- Right-click on wfica32.exe & wfcrun32.exe
- Click “Properties”
- Make these changes to both files (if you don't see an immediate impact, reboot your laptop):
-
Is there any chance the user(s) are trying to access the local drive on the client/receiver/workspace when it freezes?
How long does the freeze last?
-
On the XenApp servers (VDA's) try changing these two keys from 0 to 1. They made a huge difference for us:
HKLM:System\CurrentControlSet\Services\PicAdm\Parameters EnableCcReadCache = 1HKLM:System\CurrentControlSet\Services\PicAdm\Parameters EnableCcWriteCache = 1
-
1
-
-
It sounds a little like a problem we used to have. We got it to work by using the AlternateShellStartup policy. https://support.citrix.com/article/CTX127874
-
Users with multiple monitors are experiencing 30 - 40 seconds of flickering when a published app is first launched. The app is unusable while it's flickering (you can't type into it) but once it settles down, it's fine for the rest of the session.
- XA 7.15 CU3
- W2K12
- Receiver 19.05 on Windows 10
- The monitors are the same resolution (1080p)
- There's no flickering with the same workstation config. on XA 6.5 / W2K8
- All apps (including calc.exe) experience the problem so it doesn't appear to be a coding problem
-
Things that didn't help:
- Setting the Scale & Layout to 100%
- Receiver set to "Let the operating system scale the resolution"
- wfica32.exe set to Hi DPI compatibility
- Increased video memory (although the calculations didn't seem to warrant it)
- Enabled the Legacy Graphics policy
- Disable RemoteFX
I was wondering if there are any other suggestions?
Thanks, Jeff
-
XA 7.15 LTSR CU2
W2K12
We had one server yesterday where apps would launch from StoreFront but not be visible to the user.
- The apps appeared in Citrix Studio as though everything was normal but they didn't seem to "attach" to the user's Receiver
- It happened with all apps on the server (including notepad.exe)
- We tried a variety of Receivers
- Other server were working fine (it was just one machine out of a few hundred)
- Rebooting resolved it
- I should have tried Shadowing the session to see if it was, in fact, starting normally but didn't think about it until it was too late
I don't have anything to troubleshoot on now because the reboot fixed it.
Most of our servers are CU3 or CU4 so I'll updated this machine.
I was just wondering if anyone else has seen this or has any troubleshooting suggestions if it occurs again?
Thanks, Jeff
Windows .vbs logon scripts are not being executed when launching Published Applications, but do when launching a virtual desktop
in XenApp 7.x
Posted
This may not be your problem but I run into a similar situation this occasionally and it's easy to fix.
Sessions started via a published application don’t run all the background jobs that published desktops do. To force all the jobs to run, add the following to the local group policy:
Script Name: C:\Windows\SysWOW64\runonce.exe
Script Parameters: /AlternateShellStartup