![]() Update: Thanks to Vigneshwaran for the feedback regarding the CMAppUtil Parameters.I have an application that I want to launch via a shell script that does some setup and then launches the app itself with some specific options. The next blog post will be on how to create an Application within ConfigMgr and deploy this Application to a Mac, which has the Parallels Mac Management Agent installed. Those Settings are automatically being used when importing the. It also contains some basic Installation Parameter as where to install the Application. The Detection.xml contains, as the name implies, the Detection Method which is mandatory for creating an Application in ConfigMgr. Metadata: Contains a file called Detection.xml In this example either “Google Chrome.app” or “Install Citrix Receiver.pkg” cmaac is an Archive File which can be opened an extract on any Windows or Mac Device.Ĭontents: Contains the original, unmodified Installation File. cmmac fileĪt last, let’s have a closer look to what CMAppUtil has exactly done with the wrapped Application. dmg file without getting the prompt below.Īfter a short while, the Wrapping should complete, leaving you with another. You can use the parameter “-a” to convert all packages inside the. CMAppUtil will pause the wrapping and ask, you as seen above, to choose the correct installer. However, here we have the situation, that the specified. pkg file is exactly the same as in the example above. If CMAppUtil should fail, you can use the Parameter “-s” to create the cmmac with an empty detection method. Your app should now be available in the specified Output Directory in the. If the dmg file is opened during the wrapping, ignore it. Adjust the Path if neededs./CMAppUtil -c "/Users/macbookpro/Desktop/googlechrome.dmg" -o "/Users/macbookpro/Desktop/Wrapped/"Īfter a short while, the Wrapping Process should complete with the above message. ![]() Use the following Command to start the Wrapping process. You can use ‘cd’ to change directories and ‘ls’ to list the content of the present directory. Open Terminal on the Mac and navigate into the Tools folder where CMAppUtil is located. Citrix Receiver however is an Installer (.pkg). Google Chrome is a native App (.app) which can just be put into the Applications Folder. Whichever App you are going to wrap, CMAppUtil supports the following formats:Īs you see the Installers for the two Applications that I choose look a bit different. In this Example, we will wrap Google Chrome and Citrix Receiver. The file is located at: C:\Program Files (x86)\Microsoft\System Center Configuration Manager for Mac client\macclient.dmgĬopy the Tools folder to a place on the Mac. Install the “System Center Configuration Manager for Mac client Setup” on a Test device.Ĭopy the installed dmg file to a Mac OS X Device. The Mac Client can be found on Microsoft Download as part of the Clients for Additional Operating Systems. Getting CMAppUtilĬMAppUtil, which we use for the Wrapping-Process, is part of the ConfigMgr Mac Client. The Wrapped App can later be deployed as an Application to managed Mac Devices.įor the Wrapping you need a Windows device to install the Mac Client Installer and a Mac Device to perform the actual Wrapping. In this blog post, I’d like to demonstrate how you can easily wrap an OS X App for Distribution via System Center Configuration Manager.
0 Comments
Leave a Reply. |