3/19/2014 - Updated Clients for Mac computers have been released. For more information see our announcement post http://blogs.technet.com/b/configmgrteam/archive/2014/03/19/announcement-update-for-configuration-manager-clients-for-mac-computers.aspx.
Mac OS X 10.9 is supported on System Center 2012 R2 Configuration Manager with the following known exception:
USB devices on Mac computers cannot be inventoried. If you inventory USB devices for Mac computers, whether a USB device is attached or not, the System Center 2012 R2 Configuration Manager Mac client running on Mac OS X 10.9 will fail to connect to the management point to get policies
Workaround: Uncheck the USB Device class found in the Hardware Inventory tab of Client Settings. By default this checkbox is unchecked.
In the Administration workspace, click Client Settings and select the client settings you have created for Mac computers (or create new Client Device Settings).
Right-click the client settings and then select Properties.
Navigate to the Hardware Inventory tab and click Set Classes.
Search for “usb device”. Once you notice the list under USB Device class is populated, make sure that the USB Device Asset Intelligence (Win32_USBDevice) class is unchecked as shown below.
To support Mac OS X 10.9, ensure that all Mac OS X versions are selected for application and settings deployments. The steps to select all Mac OS X versions for application and settings deployments are listed below:
In the Software Library workspace, click Applications. Select your application, then click the Deployment Types tab located on the bottom of the console.
Select the file (typically with a .dmg extension) you want to target, right-click it, and then click Properties.
On the Requirements tab, click Add.
Click Select all as shown in the screenshot below.
In the Assets and Compliance workspace, expand Compliance Settings. Right-click Configuration Items, and then click Create Configuration Item.
On the General page of the Create Configuration Item Wizard, specify Mac OS X as the type of configuration item from the drop–down list. Give the configuration item a name and then click Next.
On the Supported Platforms page, check the Select all checkbox to ensure all Mac OS X checkboxes are checked, then click Next. Continue stepping through the wizard as you normally would.
This posting is provided "AS IS" with no warranties and confers no rights.
Do we need to re-isntall the Mac Clients on the endpoints after making this change? Thanks for this post!
How do you get 10.9 listed in the supported OS's
While it appears to work, installation still pops up a warning that it is not supported.
Is there a version of the stand-alone installer that omits that warning? It's really hard to get people to use security software that even hints that there might be a problem using it.
the mac client for 2012 doesn't have the -p for ccmsetup as it did in spy, how are people scripting this install?
the r2 client doesn't have the -p option for ccmsetup anymore, how are people deploying this package pragmatically now?
Clay Taylor - no you need not re-install the Mac Clients on the endpoints after making this change. Todd - we are making server side changes coming soon that will list 10.9 in the supported OS's the -p issue #!/usr/bin/expect spawn CMEnroll -s sb-ss.sudheerb.nttest.microsoft.com -u 'SUDHEERB\Administrator' expect "Please enter your password." send "Elvis1;\n" interact Q:"While it appears to work, installation still pops up a warning that it is not supported. Is there a version of the stand-alone installer that omits that warning?" A: Could you please specify what security software you're using? We could not reproduce the situation, and in our tests we did not notice any popups. Other issues are being investigated and we will get back to you soon. Thank you very much for your patience and enthusiasm.
Wiill you know if the System Center 2012 (not R2) will support Mac Client Mac OS X 10.9 feature?
Any plans to implement a deployment mechanism for Apple OS X MDM / iOS Configuration Profiles? This seems to be one of the key features for a mac client management solution.
"Server connection failed. HTTP Response code is 500 and reason is Internal Server Error”.Was having an issue enrolling Mac OSX clients initially and traced it back to the DMP weirdness in the log as described above.Registered asp.net 4 with IIS as described below and everything started working!!!http://heinrichandsccm.blogspot.co.uk/2013/05/sccm-2012-sp1-management-point-error.html
I am slightly confused by this post, is it saying the only way to deploy software to a running Mac OS X 10.9 is to select all the variable versions, and it will work even though Mac OS X 10.9 is not listed? Or is OS X 10.9 just not supported at all in
SCCM 2012 R2? I know CU1 is now out for R2, is that the only way to get support for OS X 10.9?
There appears to be issues on OSX 10.9.3 and newer:
@Chris.Bradford. Chris please see our post here:
http://blogs.technet.com/b/configmgrteam/archive/2014/07/07/mac-os-x-10-9-3-support-for-system-center-2012-configuration-manager-clients.aspx. That may be the issue you are experiencing. The post contains a workaround for not being able to contact the MP.
We are working on a fix for the issue described in that post.
@Yvette that's got it working for now, thank you! Any ETA on the fix itself?
@Yvette, whilst the OSX 10.9.4 client now communicates with the site server, software deployment seems to fail - despite working to OSX 10.9.1 clients.