PVS write cache filling up? handy filter in Procmon to give a clue as to what’s causing it

So of course with write cache filling up issues no simple way to tell what’s going on. Needless to say like most quirks that happen in Windows the sysinternals tools can come to you rescue.

Recently started work on a windows 10 PVS image and after about 10 minutes the write cache would fill up.

So using Procmon (https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx) was able to determine what was going on.

In order though to filter out the extraneous stuff found the following 2 filters gave me info on the offenders.

To do click Filter and filter out everything except write activity by making two filters as follows:

Operation begins with WriteFile Include
Operation begins with WriteConfig Include

and you’ll be on our way.


Citrix tip: getting WMI CPU spikes on certain VDA’s?

On a certain batch of VDA’s we had running in an environment here they were running 2 versions back (7.11) from current version on our delivery controllers (7.13) noticed tickets coming in relating to general sluggishness with performance. Ops teams did some digging and noticed it was related to WMIprvse.exe. Seen this in the past and wondered if a similar fix adopted to same issue we’d seen in XenApp 6.5 would work.

Sure enough did the trick.

Issue related to performance counters.


On a “happy” VDA (eg one chugging along nice and quiet from a CPU perspective)

export the performance counters

c:\ lodctr.exe /S:C:\counters.txt

On the “unhappy” VDA’s import the counters in

c:\ lodctr.exe /R:C:\counters.txt

Citrix tip: if having issues using HTML5 receiver post Storefront 3.5 upgrade check the following

A while posted this on the forums luckily Michael in citrix was able to assist with a “full” fix. As mentioned in the thread had a workaround but programmatically have checked the steps outlined and they do work too.



Citrix quick tip: how to use application categories to better lay out your published applications

Previously known as folders in the XenApp 6.x environments or earlier. When working in medium / large scale environments generally comes a biting point when applications are better grouped into folders (like files). The simplest way to do this in XenApp 7.x is by doing the following.

– Go into Citrix Studio

– Right click on an application in Studio and select properties

– Select Delivery on the pop-up window

– You will see the application category showing under the icon. Simply create your category there. Whether it be alphabetical eg “A-E Apps” or by type “Administrative apps” and click ok when done

Easy peasy


VSphere tip: removed VM from a datastore cluster but rules still applying to it

Found this issue last week and wanted to note it for future reference for myself (getting old and best way for me to remember as much as anyone:)).

So removed a VM from one of our datastore clusters. Now this machine had an affinity rule applied to it which i wasn’t aware of. Interestingly found i couldn’t remove the rule even  wanted to from the datastore cluster.

Turns out the solution was slightly inelegant but it worked.

i) Moved said VM back into the datastore cluster

ii) In the vSphere client (or web) browse to the datastore cluster.

iii) Click the Manage tab and select Settings

iv) Under Configuration, click Rules

v) Pick out your offending rule you want deleted and click Remove and click Ok

Enabling logging for troubleshooting app-v issues in your citrix environment

When troubleshooting App-v issues in your citrix environment one of the first usual port of calls will be to enabling logging.

To enable Studio and VDA logs used for App-V, you must have administrator privileges. You will also need a text editor such as Notepad.

To enable the Citrix Studio logs:

  1. Create the folder C:\AppvLogs.
  2. Navigate to C:\ProgramFiles\Citrix\StudioAppVIntegration\SnapIn\Citrix.Appv.Admin.V1. Open CtxAppvCommon.dll.config in a text editor and uncomment the line: <add key =”LogFileName” value=”C:\AppvLogs\log.txt”/>
  3. Restart the Broker service to start logging.

To enable VDA logs:

  1. Create the folder C:\AppvLogs.
  2. Go to C:\ProgramFiles\Citrix\ Virtual Desktop Agent. Open CtxAppvCommon.dll.config in a text editor and uncomment the following line: <add key =”LogFileName” value=”C:\AppvLogs\log.txt”/>
  3. Uncomment the line and set the value field to 1: <add key =”EnableLauncherLogs” value=”1″/>
  4. Restart the machine and logging should be working