b l o g

To access the citrix desktop delivery controler sdk shell (assuming its installed) do the following.

• Start > Programs > Citrix > Desktop Delivery Controler SDK
• Click on Citrix Desktop Delivery Controler SDK Shell
• Alternatively, you can run > Add-PSSnapin ‘XdCommands’
  • If you recieve the following error, the XDCommands Snap-in has already been loaded in your existing shell.
  • Add-PSSnapin : Cannot add Windows PowerShell snap-in xdcommands because it is already added. Verify the name of the snap-in and try again.
    At line:1 char:13
    + add-PSSnapin  <<<< ‘xdcommands’

Known Error: There were errors in loading the format data file: XdCommands, C:\Program Files (x86)\Citrix\Desktop Delivery Controller\Powershell\XdCommands.Format.ps1xml:File skipped because of validation exception: “File C:\Program Files (x86)\Citrix\Desktop Delivery Controller\Powershell\XdCommands.Format.ps1xml cannot be loaded because the execution of scripts is disabled on this system.  Please see “get-help about_signing” for more details.”.
File C:\Program Files (x86)\Citrix\Desktop Delivery Controller\Powershell\XdAliases.ps1 cannot be loaded because the execution of scripts is disabled on this system. Please see “get-help about_signing” for more details.At line:1 char:2+ .  <<<< ‘C:\Program Files (x86)\Citrix\Desktop Delivery Controller\Powershell\XdAliases.ps1′

If you get the above error, run the following from your shell > “get-executionpoliy” (without the quotes) then hit enter. If you get a responce indicating “Restricted” . Here is how to address so you can run the delivery controler sdk shell properly. Depending on your confort level and security concerns run one of the following.

• Set-ExecutionPolicy Restricted - to allow for Restricted, meaning – no powershell scripts can be used outside of interactive mode
• Set-ExecutionPolicy AllSigned – to only allow for scripts signed by a trusted publisher
• Set-ExecutionPolicy RemoteSigned – to only allow for downloaded scripts which are sighen by a trusted publisher
• Set-ExecutionPolicy Unrestricted – to allow all powershell scripts to be run, and with no restrictions.

 The above error has been corrected: