Problems deploying Citrix Receiver 3.3 through Desktop Central.

Problems deploying Citrix Receiver 3.3 through Desktop Central.

I am hoping someone out there has had similar issues to what I am going through, but has solved the problem with deploying Citrix Receiver 3.3 to their clients through Desktop Central.

Downloaded from here: http://www.citrix.com/downloads/citrix-receiver/receivers-by-platform/receiver-for-windows-33.html

The installer seems fairly simplistic, although it has a few custom switches.
Information on command line install is here:
http://support.citrix.com/proddocs/topic/receiver-30-windows/ica-configure-command-line.html

and more specifically to my needs: http://support.citrix.com/article/CTX135438

The only switches I need to make use of specifically are /silent and /ALLOWADDSTORE=N

installing the program locally on my system with those switches (as shown in the following example) works locally on my system - it installs silently, and only installs the web component meaning that it does not ask for the server address or the users email address.

CitrixReceiver.exe /silent /ALLOWADDSTORE=N

When deployed via DesktopCentral - it installs silently, but the switch /ALLOWADDSTORE=N does not appear to get passed along and the popup box asking for server address comes up - we can't have this.

I created a batch file to perform the installation - thinking if I have all the commands listed in the batch, it will pass through and run like it does locally on my test system.

For testing purposes I have echo turned on.

  1. echo on
    start /wait CitrixReceiver.exe /silent /ALLOWADDSTORE=N
    EXIT


Again - this batch file works locally on my test machine - but the moment I try to deploy it through Desktop Central, it only acknowledges the /silent switch and not the other - which really baffles me because its encapsulated within the batch so should in theory be acting as it is installing locally.

I can't seem to get this to deploy through Desktop Central properly with the appropriate switch enabled, yet it works absolutely fine when done locally.

Suggestions?

We have to many off site users that deploying via GPO isn't ideal, that is why using Desktop Central for this becomes rather imperative for us.

Carlo Piva
















Systems Administrator
Bird Construction Inc
http://www.bird.ca
http://ca.linkedin.com/pub/carlo-piva/31/267/a5b



















                  New to ADSelfService Plus?