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.

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.

ACL issue on user-published App-V 5.0 SP2 packages

There is a known issue when you publish an App-V 5.0 SP2 package user-based. The issue will be seen when it’s published to roughly ~250 users. This can be observed in the eventlog:

Part or all packages publish failed.
published: 3
failed: 1
Please check the error events of ‘Configure/Publish Package’ before this message for the details of the failure.
Event-ID: 19104

The issue happens because every user that got the app published has been added to the ACL of the published App-V package below c:\programdata\app-V reaches its limit (~250 entries) and therefore the whole publishing mechanism doesn’t work properly anymore. The reason is the PSAC feature (Package Store Access Control) that is depreciated and won’t exist anymore in App-V 5.0 SP3 that will be released soon. So SP3 will fix the issue. In the meantime, the following workarounds exist:

  • Publish the app globally and not user-based
  • Delete the cache
  • Run a scheduled script that will reset the permissions on the folder

Thanks to Sebastian Gernert who posted about the issue (it’s in German): not working

To troubleshoot Citrix issues, I often open cdf traces with CDFControl, a Citrix tool. Unfortunately I discovered that is currently not responding (time out). You need that to download the Citrix symbol files. According to, Citrix is aware of the issue and works on bringing the server back online. Be patient….

19.09.14: Solved, it’s back working!