Saturday, October 18, 2014

Prepopulating Citrix Receiver within ICA session.

We get the requirement quite   often that once users logged into virtual desktop application should launch via seamlessly. Here seamlessly have many meaning  and it varies from customer to customer. For example one customer would like the application to be present as a shortcut in the start menu and when users click the application it must do single sign on.  There are various way to achieve this. Once can import receiver ADM template using gpedit.msc

To prepopulate the receiver with the URL


To prepopulate url , one can do it via adm template or via Citrix HDX policy . To do it via adm template, import it into local policy and then perform following settings


Once storefront url is selected value must be entered in following format “

SalesStore;;On;Store for Sales staff” and even one doesn’t want to wish to have it. So once this is done it will prepopulate the URL.

Once url is prepopulated, SSO has to be done. To do the so , we must choose “local user name and password” and then choose Enable pass-through authentication.


This will allow single sign on and allow users to launch application seamlessly.

Tuesday, October 14, 2014

Failed to add a Failover Cluster Node because “SQL Server Agent” account name empty

I came across interesting issue on two occasion when I tried adding second node to the SQL 2012 cluster node. After it detecting the second server detail, account name for “SQL Server Agent”  is blank. After we typed password this still fail with error message “There are validation error on this page”


We tried rebooting boxes but that didn’t help. Finally to fix this we need to create

1. SQL Server agent 2. Add the same agent as fail over cluster resources.

You can do this steps on any of the fail over cluster node. Use following PS editor to run the command


$ClusterName = "YourClusterName"
$FciClusterGroupName = "SQL Server (MSSQLSERVER)" # may need to modify to reflect your environment

Add-ClusterResourceType -Name "SQL Server Agent" -Dll "sqagtres.dll" 

Output of command will be like this


Once this is done,select role –>Add Resource –> More Resources –>


More Resources –> SQL Server Agent


Select “New SQL Server Agent” and --->properties –>Dependencies select resource as “SQL Server”


Now select properties tab and type  InstanceName = <Name of the SQL server Instance name> VirtualServerName =<Name of the SQLCluster>


Now the “New SQL Server agent”  will start


Make sure the registry on primary server is set to 1


After above steps when setup is run again , it was able to see SQL Server Agent users name.


Yeah I am also a SQL expert Smile

Source here