Error: “Cannot Complete Your Request” When Using Custom Portal Theme on AAA or Gateway VServer

In case you see this error, that shows up right when you open the aaa or gateway vserver (before logging in), this is the solution:

When the “Integrated caching” feature isn’t licensed, you will just need to execute the following command:

set aaa parameter -enableStaticPageCaching NO

I tested it on Netscaler ADC 12.1 51.19 and it worked perfectly.

Storefront 3.9 – default Website not working

Recently I upgraded to Storefront 3.9. Setting the default Website no longer works in that verion:

Disable the setting and enable it again won’t make any difference. That setting configures the web.config file in the root folder of IIS (c:\intetpub\wwwroot\web.config). As a workaround you can configure it in the web.config by yourself. Just add the following config:

<?xml version=”1.0″ encoding=”UTF-8″?>
<httpRedirect enabled=”true” destination=”https://FQDN/Citrix/StoreWeb” childOnly=”true” />

Replace the destination value with your Website of the store and you’re done.

Adobe solved the z@ tmp files issue

Back in 2014 I posted about these z@ tmp files that are sometimes created by Adobe Acrobat (or Reader) in the temp Folder and cannot be deleted anymore afterwards because they are still in use (see post here).

Adobe finally solved the issue in Adobe Reader 11.0.14, released in January 2016. See the release notes here:

How to bring back the customized Delivery Group icons with Storefront 3.0

When you migrate to Storefront 3.0, you probably will see that the customized delivery Group Icons are gone. There’s an Powershell command that brings those icons back, just run it on the Storefront Server:

& ‘C:\Program Files\Citrix\Receiver StoreFront\Scripts\ImportModules.ps1’

Disable-DSStoreSubstituteDesktopImage -SiteId 1 -VirtualPath /Citrix/Store


Note that you might have to Change the paths according to your Installation.

Reserve your free upgrade to Windows 10…

…yes, that’s the message I got after clicking on the Windows symbol that appeared in my system tray:


That confirms the statement of a free upgrade, although it’s time limited (I believe 1 year). Today I read that Win 10 would be delayed and will be released for public end of August. Let’s see….

Update 8.6.15: Windows 10 will be available end of July….

App-V 5.0 SP3 Sequencer issue

There is a bug with the App-V 5.0 SP3 Sequencer that has just been release some days ago. When you try to install the MSI of a created App-V package created by the SP3 Sequencer, the installation only works when you run the MSI installation in an elevated cmd (start cmd.exe with “Run as Administrator”). If you deploy your apps with SCCM, you’re usually not affected when you run the installation by the system account.

The following error messages are shown when you install the msi without elevated cmd:

error1 error2

I created an mst that fixes the issue. Do the following steps to apply the fix :

  1. Download the mst that fixes the issue:
  2. Extract the mst file and copy it into the same folder as your msi file
  3. Run the following command:
    msiexec /i YourAppvPackage.msi TRANSFORMS=AppV5_SP3Fix.mst

If you want to run it unattended, add /qb as parameter. Make sure your current directory is the one that contains the msi/mst or just add the full path to your msi and mst. Don’t rename your msi, use the original name that has been created by the sequencer.

You can also permanently apply the transform (mst) to the msi with Orca.

The root cause of the issue is a changed setting in the MSI. The custom actions responsible to publish and remove the App-V package won’t run under the local system account with full privileges (no impersonation)


The mst I created changes that configuration back so that these custom actions run under the local system account with full privileges (no impersonation) as it was prior to SP3. This change is done by changing the above marked type values from 1025 to 3073.


GoPro Importer causes high CPU usage

I bought the new GoPro Hero 4 Black edition camera in order to make some recordings during my Australia trip that will take place the whole January 2015. After installing GoPro Studio, I observed a constant high CPU usage (20-50%) caused by WMI Provide Host. That high CPU usage was caused by GoPro Importer. It’s a startup executable that constantly checks if the GoPro cam has been plugged into the computer. After having removed it from the startup list, the issue disappeared.