Deploying Citrix Receiver 3.0 & Enterprise Client 13.0 From SCCM

Hi All,

I don't know about you, but I was planning to roll out the new Citrix on-line plugin. Recently, I was rolling out a new web interface and needed to change all of the citrix clients to point to the new location. The older clients can be changed via GPO's however, the receiver clients are a little harder. The only real way to change the receiver clients is by utilising the Citrix merchandising server.

Since I needed to implement the Citrix merchandising server I decided I was going to roll out the new Citrix receiver 3.0 & Enterprise client 13.0 from SCCM.

Below is the method I used.

Instructions for Merchandising Server

• I used these instructions to deploy the merchandising server. I created one default rule to deploy the  enterprise client. 
• I have included the plug-in for two reasons. 
• When I need to change the server URL I can just change it in this deployment and the changes ripple down to all clients. 
• If the client gets removed from the workstation it will automatically be re-installed.

• Generate a new token within your merchandising server under configuration => authentication:  This will allow you to deploy the receiver with pass-thru authentication.

• Download the Citrix Receiver 3.0 and On-line Plug-in (Enterprise)  from your merchandising server so it is ready for application deployment. If you have followed the above link to install the merchandising server then you will already know how to download the required clients. 

Instructions for Deploying from SCCM

• Package the applications in SCCM

• Use the following command line for the Citrix Receiver Enterprise 13.0 program, changing the server_location and token variables.
  CitrixReceiverEnterprise.exe /silent SERVER_LOCATION=https://ClientWebAddress AUTOUPDATE=true TOKEN=TokenYouCreated ENABLE_SSON=Yes

• Use the following command line for the Citrix Receiver Updater 3.0 program, changing the server_location and token variables.
  CitrixReceiverUpdater.msi /quiet SERVER_LOCATION=https://MerchandisingWebAddress AUTOUPDATE=true TOKEN=TokenYouCreated ENABLE_SSON=Yes

• Under the advanced tab for the package Citrix Receiver Updater 3.0 daisy chain the Citrix Receiver Enterprise 13.0 to always run before.

• Setup you collection to deploy:
• Membership: In my case I included all Windows XP and Windows 7 workstations that do not have the two clients already installed and computers that are not a member of a SG
  select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from  SMS_R_System where (SMS_R_System.OperatingSystemNameandVersion like "%Workstation 5.1%" or SMS_R_System.OperatingSystemNameandVersion like "%Workstation 6.1%") and SMS_R_System.Name like "LCHSPC%" and (not SMS_R_System.ResourceId in (select SMS_R_System.ResourceId from  SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = "Citrix Receiver (Enterprise)")) and (not SMS_R_System.ResourceId in (select SMS_R_System.ResourceId from  SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = "Citrix Receiver Updater ")) and not SMS_R_System.ResourceId in (SELECT SMS_R_SYSTEM.ResourceID  from SMS_R_System  WHERE SMS_R_System.SystemGroupName = "Domain\\SG")
• Maintenance Windows: Outside of business hours

• Name

• Advertise you package to your collection and you’re done.

I have chosen to force the deployment outside of business hours. The install process will remove the current on-line plug-in. I have also given the user the option to install it during business hours.

Now all my systems are all running the same client and I can change the server URL from one location. I can also any new Citrix client just by adding it to the merchandising server.

I do hope this helps. If you have any questions please leave a comment

CcmSetObjectSecurityInit Error when installing SCCM client on Server 2008

Hi All,

I recently had an issue with the SCCM client not installing on a 2008 server with IIS installed.

Within the client.msi.log I found the following error:

Error 25001. Setup failed due to unexpected circumstances
The error code is 80004005

Action ended 8:59:25: CcmSetObjectSecurityInit. Return value 3.

After days of searching I found this blog and changed the permissions on the Anonymous Authentication in IIS to the local administrator account. Installed the SCCM client and then changed it back.

I hope this saves you some time.

Blair