Software Deployment

The one thing you don't seem to have tried is reading about Windows Installer.

You cannot install 2 MSIs simultaneously. Either:

- create a script to execute the MSIs in sequence or use your authoring tool to build a set-up stub to do the same. Whichever method you choose, remember to build in proper error-trapping.
- given the environment (i.e. one which uses Citrix), there must be a deployment system in use (e.g. Group Policy, SMS/SCCM, Radia) so why not "chain" the MSIs to deploy that way?

Hi DJ,

I am trying to build a MSI package for citrix online plug in 12.X, i am unable to find any free tool that serve my purpose. Can
someone shed light on this please?


Thanks

Someone else having trouble reading....

The plug-in is installed by 6 MSIs The source provided for this application is an exe (CitrixOnlinePluginFull.exe) which is extracting and installing 6 MSIs. so why do you need to create another? Re-packaging an MSI into another MSIs is one of the fastest routes to insanity.

A free re-packaging tool? Ummmm...have you searched AppDeploy for one? If you did, I don't think you searched hard enough.

Guys, if you can't deploy this using your preferred tool (SMS / SCCM) via the .EXE command line:

e.g. CitrixOnlinePluginFull.exe /silent ADDLOCAL="ICA_Client,PN_Agent,SSON,USB,DesktopViewer,Flash" SERVER_LOCATION="http://mywebinterface/Citrix/PNAgent/config.xml"

Then I guess you are needing to use AD to deploy it? If so have a look here: http://support.citrix.com/proddocs/index.jsp?topic=/online-plugin-112-windows/ica-client-deploy-active-dir.html - yes it's a pain the the backside.

Otherwise you'll need to do what Ian says and extract the MSI's then chain them together in a script or whatever. This is kind of re-inventing the wheel since the vendor .EXE already effectively does this - along with a load of other logic, including removing previous versions...

Cheers,
Rob.

Hi Everyone,

I used a VB script along with GPO to push the the citrix client, I have tested with test users and its going good.But i am trying to write reg entries (in order to set file security permissions on citrix client) which seems not working as expected.

i am trying to write reg entries (in order to set file security permissions on citrix client)Eh? How does that work? If you need to protect the client files, you need to either use the LockPermissions table (which nobody really does) or use something like SetACL, SubInACL or the like.

If it's registry settings you need to write, these are controlled by the Registry table. If they're failing to be written, presumably they're protected already? One would then have to ask the question as to why an admin level or system account doesn't have such rights.

I too am trying to repackage this as an MSI (for deployment with the only platform I have available currently- Active Directory). I used WinInstall LE and here is what I am seeing (have seen this before w/some other apps). It wants to install "per user" but I am deploying to the computer itself. So after I did my discovery, install and discovery on my model computer I edited the MSI so it is destined to install for computer instead of "per user".

After the install is complete there still seems to be errors referencing a profile that I was logged on as on my model computer (that doesn't exist on my test target VM). Also every time I logon to a unique profile i get the message "Please wait while Windows configures Citrix...Gathering Required Information" with progress bar. Citrix "seems" to be working but would like to avoid this install every time a user logs in. Also when I tried to uninstall it I get a "feature trying to use a network resources that is unavailable" message and the path seems to be looking for that same profile that doesn't exist (only on the model computer)

Anyone do this with WinInstall LE and able to supress those install messages? I understand that it is basically 4 MSIs wrapped up already but Active Directory needs an MSI. I also tried just extracting the 4 MSIs and deploying them but none of them even install...

I too am trying to repackage this as an MSIThen stop. Use the MSIs you have already extracted.

I suspect that the failure may be to do with the order of installation. Re-try the installattion but specify a verbose log on the command line. The resulting log will detail any errors.

I have no idea how to specify verbose logging within the packaging application (WinInstall LE). Perhaps this is something I do when doing the before/after discovery on the model machine?

this is something I do when doing the before/after discovery on the model machine?No. I already said to stop trying to capture the install. As it's already MSI-based, you are opening up a world of pain which, given the level of your questions - no offence intended - you will be unable to rectify.

I meant that you should use the logging switch when executing the MSIs from the command line, using MSIEXEC:MSIExec /i [path_to_and-name_of_MSI] /l*v [path_to_and_name_of_log_file]