Creating the first Store within Citrix StoreFront with Powershell


You can easily automate the installation of Citrix StoreFront but what about the initial configuration. Perhaps you have multiple StoreFront server groups that you need to deploy and dont want to go through the hassle of running through the initial installation wizard when you open Citrix StoreFront for the first time.

Using a minimal amount of Powershell you can automate the initial Store creation process without having to open the StoreFront UI at all.

You need to have the set-executionpolicy set to unrestricted or similar to run non Microsoft based cmdlets in powershell.

Once you have the powershell pre-req’s covered you need to import the relevant powershell snapin’s by running the following command:

./”C:\Programs\Citrix\Receiver StoreFront\Scripts\ImportModules.ps1″

You can make the above part of a script if you like to make the powershell deployment even more fantastical.
Now all you need to do is customise and run the following powershell command.

set-dsinitialconfiguration -hostbaseurl https://loadbalancedurl.domain.local -farmname auto -port 80 -transporttype HTTP -sslrelayport 443 -servers @(“test.local“; “test2.local“) -loadbalance $false -farmtype “XenDesktop-storevirtualpath /Citrix/TEST -webreceivervirtualpath /Citrix/TESTWeb

The items in bold are variables and map directly to the initial store creation wizard you would normally have to step through within the GUI. In addition to the variables -storevirtualpath or -webreceivervirtualpath are included here as without them the initial store is given the default name of STORE which is ok but not exactly very personal.

In addition to the above you can also add XenDesktop sites to the stores by customising the following powershell command.

set-dsxdfarm -farmname XenDesktopSite -servers @(“test3.local”; “test4.local”) -port 80 -transporttype HTTP

However the only problem with the above command is that there is no way to set the farm type to anything but XenDesktop. So if you have a XenApp or VIAB environment you have to go into each delivery controller group after running the command and change the type.



Author: Dale Scriven

Leave a Reply