Storefront Verbose Logging

To enable Verbose Logging in Storefront 2+ you have to run these commands in Powershell in the Storefront server:

Add-PSSnapin Citrix.DeliveryServices.Framework.Commands
Set-DSTraceLevel –All –TraceLevel Verbose

Then you need to restart these services, or reboot the server:

  • Citrix Configuration Replication
  • Citrix Credential Wallet
  • Citrix Default Domain Services
  • Citrix Peer Resolution Service
  • Citrix Subscriptions Store

After a while you’ll see the logs starting to fill up in:

C:\Program Files\Citrix\Receiver Storefront\Admin\Trace

And to disable the Verbose Logging run the following commands in Powershell:

Add-PSSnapin Citrix.DeliveryServices.Framework.Commands
Set-DSTraceLevel –All –TraceLevel Off

Storefront 2.6 – Additional URLs

A common setup is to use the same internal as external URL. The best way to accomplish this is to setup a load balancer and content switch vserver in Netscaler where you point the internal URL to. This way you can handle the redirection from the root (https://remote.domain.com/) to the Store address (https://remote.domain.com/Citrix/MyStoreWeb) for web access properly.

This works good as long as you’re accessing resources from a web browser. However, when the native receiver is used you get an error message saying “Select an account to continue”. This is because the storefront does not recognize the url you are accessing from as allowed.

To fix this you need to open this file with notepad:

C:\inetpub\wwwroot\Citrix\Roaming\web.config

Search for the tag “<allowedAudiences>”.
Here you find that the BaseURL of the storefront is already present, i.e:

<add name=”https-internalsf.domain.com” audience=”https://internalsf.domain.com/” />

Copy this row and insert in right after, and alter the address so it corresponds with the desired URL. The end result should like something like this:

<allowedAudiences>
<add name=”https-internalsf.domain.com” audience=”https://internalsf.domain.com/” />
<add name=”https-remote.domain.com” audience=”https://remote.domain.com/” />
</allowedAudiences>

Now you should be able to connect the native receiver to the Storefront via a Load Balance or Content Switch vServer.