![]() If you go to the project folder you will see the MSI that has been created. The added executableĬlick Next after leaving the Package options as default.Ĭlick Finish to create the MSI file. Supply silent switchesĬlick OK and click Next after adding the executable. I used the /silent /includeSSON switches. Next you need to add the executable and you need to configure the “package” and add the silent switches, Citrix has a support article how to deploy the Citrix Receiver with SCCM. Specify where the Project needs to be saved in and where the MSI file needs to be saved and click Next. Next supply the name of the “product” and the name of the product manufacturer, in this case “Citrix Receiver” and “EMSKings”. Choose right option in Advanced Installer So when using Advanced Installer you need to go to New, Convert and select MSI from EXE(s). And yes, so it is! With Advanced Installer it is pretty easy to do so, even for someone who created application packages with Zenworks 6.5 and so on, light years ago! ). So what if we could wrap the executable in some kind of MSI? So, I reached out to my CTGLobal colleague Thomas Marcussen to verify if this would be possible. But like said it can take a long -random- time before the Citrix Receiver is available. ![]() After a long time with many reties of installing the MSI’s, the Citrix Receiver will be installed correctly with all components (MSI’s) in place. If an MSI fails due to that another one is required. If you add all ten MSI’s to Microsoft Intune and deploy them to the Windows 10 devices and they will be installed in a random order. With Microsoft Intune we currently do not have the option to create some kind of sequence of apps that need to be installed or something like application dependencies.
0 Comments
Leave a Reply. |