In the earlier articles I wrote down how to install unattended the XenDesktop components. The article was based on the versions of XenDesktop 7.6 till XenDesktop 7.11 (dependent of the article). Currently Citrix is releasing every quarter a new version, so it’s time to update the articles with the new installation information of later release(s) based on XenDesktop/XenApp 7.12 and XenDesktop/XenApp 7.13.

XenDesktop 7.12 / 7.13 Delivery Controller

Just like the earlier version XenDesktop 7.12 requires .Net Framework 4.5.2. However .Net Framework 4.6 and 4.6.1 are also supported for version 7.12. XenDesktop 7.13 also supports .Net Framework 4.6.2.

I will refer to part 4 for the installation parameters of .Net. Remember that a restart is required.

I added in part 4 a check which version is actually installed, so the script could be used for upgrades as well. The same key is available for both version 7.12 and 7.13, so the script part is similar as the previous version. The version that should be checked is for XenDesktop 7.12 Delivery Controller, while XenDesktop 7.13 has labeled with version number

For the script this will be the variables defined for XenDesktop 7.12

#Define Variables
$DCUninstall="HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Citrix Desktop Delivery Controller”

For XenDesktop 7.13 this will be the Define variable part.

#Define Variables
$DCUninstall="HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Citrix Desktop Delivery Controller”

The rest of the code don’t need to changed. As this one is introduced in part 4 for the first time I will show the code once more in this article, both for the pre-check as the post-check.

#Pre-Checking Delivery Controller software is already installed

If ((Test-Path -path "$DCUninstall") -ne $True)
                    { Write-Host "The checked uninstall key $DCUninstall does not exit. Delivery Controller software is not yet installed, software will be installed."}
                    {Write-Host "Uninstall Delivery Controller Key defined as $DirectorUninstall found. Check if the version is already installed or the software should be upgrade."
                    $var=Get-Itemproperty "$DCUninstall"
                    if ($var.Displayversion -ne "$XDVersion")
                    {write-host "Another Delivery Controller version is installed. Software will try to update this version" }
                    {write-host "Version $XDVersion is already installed. Installation will be cancelled" -ForegroundColor Yellow

#Checking Delivery Controller software installation is successful

Write-Host "Checking Delivery Controller software installation is succesful"

$var=Get-Itemproperty "$DCUninstall"
                    if ($var.Displayversion -ne "$XDVersion")
                    {write-host "$XDVersion not found. Installation failed." -ForegroundColor Red}
                    {write-host "Version $XDVersion found. Installation succesful." -ForegroundColor Green}


XenDesktop VDA 7.12 and 7.13

For the VDA it’s pretty simple again. Just as with the earlier releases a new GUID is added to the uninstall key. For de XenDesktop/XenApp 7.12 VDA the key is {17B99D50-E136-484B-B969-B5D175184334}


Using the just released (February 2017) XenDesktop/XenApp 7.13 VDA the key is {81111155-7ECB-48C7-9B88-69D1171A9BF3}. Also you need to be update with Windows Updates before the 7.13 VDA can be installed. At least you need to have KB KB2919355 installed. This KB requires that updates KB2939087 and KB2975061 are present. See for more details CTX220340


PVS Target Device 7.12 and 7.13

Together with XenDesktop 7.12, also PVS 7.12 is released (with a few days delay). Just as the VDA for the PVS Target Device you only need to change the GUID in which the PVS Target Device 7.12 software uninstall key is added. For PVS 7.12 is the GUID {EC9A6AEE-6DDE-4C89-9556-B8C1F5D5539C}. I also understood that the installed is fixed, so you don’t need to copy the driver files to the machine first anymore. I did not test it myself as I just read this after I updated my demo environment. So it’s worth giving it a try.


For the Target Device of Citrix Provisioning Services 7.13 released together with XenDesktop/XenApp 7.13. No changes to the installation procedures with this release, so again we only need to add the correct GUID to the installation script. For 7.13 VDA the GUID is {B7487F2D-97CE-4B22-8C04-17DCF5662857}.



Citrix StoreFront 3.8

With the release of XenDesktop 7.11 Citrix also released Citrix StoreFront 3.8. For the unattended installation of StoreFront we only need to change the GUID at Define Variables. The story is still a bit boring especially when you have read the previous articles, isn’t it?


Citrix StoreFront 3.9

Citrix StoreFront 3.9 is released together with XenDesktop 7.13. Just as for earlier version we only need to change the GUID defined at the variables part of the script. It’s getting even really boring right now, don’t you think.


Citrix Director 7.12

From Director 7.9 and higher are now 64bit. So we also only need to change the GUID for the Director 7.12 script. The correct GUID is {84D42AD4-3219-4D49-B2E9-FBD81646E7D3}.



Citrix Director 7.13

Pretty strange, but the uninstall information of Citrix Director 7.13 is now again stored in the Wow6432Node registry part. It is not clear why it is moved over again to this location, officially this means that the software is 32bit again. In the 64bit I cannot find any referral to Citrix Director in the uinstall key. So you need to change the variable $DirectorUninstall as shown below.



In this article I updated the installation scripts with the latest version of XenDesktop, StoreFront and PVS (version 7.12 and 7.13). For the full scripts, check the earlier articles in this series.