Configmgr For Mac
Dec 9, 2018 - How to deploy clients to Macs. This article describes how to deploy and maintain the Configuration Manager client on Mac computers. To learn about what you have to configure before deploying clients to Mac computers, see Prepare to deploy client software to Macs. Aja kona 3g driver.
ConfigMgr offers limited support to manage an OSX-device, however you can extend the capabilities using third-party tooling such as Parallels Mac Management for SCCM. Parallels Mac Management for SCCM primarily offers something similar to Software Center – namely an interface called Parallels Application Portal that will allow available applications (not the classic package) to be installed or removed through a user interface. Unlike the Windows-applications and their respective deployment types for an application the ability to configure the deployment is rather peculiar.
Some basics You will need access to an instance of OSX where you can. As previously described on howto there is a small tool to generate a ConfigMgr compatible package from various different formats available for OSX to install applications. Once the package is generated it will contain the binary pieces of the application, aswell as a basic command-line to install the application and (optional, but enabled by default) a detection method to verify that the application is installed. Command-line Most likely the command-line will look something like this /usr/sbin/installer -pkg 'Parallels Desktop.pkg' -target '/' –verboseR As Parallels Mac Management for SCCM has the ability to also uninstall applications there is a need to specify the command-line for actually removing the application. Using the “:” you can provide the two commands on the same command-line. Command-line (more about rm on ) rm -rf '/Applications/Parallels Desktop.app' Combined command-line (notice the: at the start, the middle and the end of the command-line)::/usr/sbin/installer -pkg 'Parallels Desktop.pkg' -target '/' -verboseR:rm -rf '/Applications/Parallels Desktop.app': Detection Method Detection Method will be determined by default (you will need to specify the –c option to avoid having it generated within the ConfigMgr package) when a package is created. The Package ID can be reviewed within OSX using the.
Configmgr For Macbook Pro
Sample command-line to review if a package is installed or not within OSX $ pkgutil -pkg-info com.parallels.package Sample output $ pkgutil -pkg-info com.apple.pkg.BaseSystem package-id: com.apple.pkg.BaseSystem version: 10.6.0.1.1. Volume: / location: / install-time: groups: com.apple.snowleopard-repair-permissions.pkg-group com.apple.FindSystemFiles.pkg-group $ date -r Sun May 29 15:16:27 PDT 2011 As you can see we request information if a specific package is installed.
To list all packages on a volume you can use the following command $ pkgutil -packages –volume / Additional command-line During the uninstall command we technically only remove the application, however the information which we base the detection on is left behind. To remove the package information the following command-line can be used $ pkgutil -forget com.parallels.package Using we can combine our multiple commands for uninstall – both removing the Parallels Desktop.app and the package information.:/usr/sbin/installer -pkg 'Parallels Desktop.pkg' -target '/' -verboseR:rm -rf '/Applications/Parallels Desktop.app' && pkgutil -forget com.parallels.package: Summary Unlike the Windows-applications where the install / uninstall scenario are split into two separate command-lines there is a single-command line to handle for OSX. One needs to be familiar with OSX tools to manage applications and the terminal capabilities to successfully manage a successful installation and uninstall of an application.
How To Use Configurationmanager
If you are unfortunate enough to be in a position where you are required to use SCCM 2012 R2 to manage your fleet of Mac OS X devices. Then you may already be aware that the process to enroll these devices on mass is not easily automated. Unlike other management products like Casper suite, where we have a QuickAdd.pkg which we can install on the client at firstboot or through ARD or any other number of methods that require no user intervention, SCCM is a little bit different.
Download Configuration Manager
The installer package that is provided installs the client, but it doesn’t install any of the tools required to automate the enrollment via a script for example. Previously with SCCM 2012 SP1 it had been possible to automate the enrollment process by passing the username and password on the command line to the cmenroll binary (albeit in clear text) Now it seems that MS would rather rely on the user to enter in their AD credentials in the new ConfigMgr GUI window in order to enroll.
This is obviously a problem if you have a lab of Mac’s or wish to enroll a number of machines at imaging time using DeployStudio/Casper etc etc. So in this post I will show you how I was able to create a metapackage that contains all the required files and a postflight script which can automatically enroll the device using an AD service account.
From here I will assume that you already have the macclient.dmg which should look like this: First we need to create a package that contains our Client Tools. If you have created packages before this should be a relatively straight forward process. I used Composer and ended up with something looking like this: We now need to create an enrollment script, or two.