Under Devices the Mac OS X system should appear, active and Approved.Ive noticed that this blog post still gets a reasonable amount of traffic and comments.While thats really gratifying, the content is horribly out-of-date, and a number of the comments relate to the fact that the functionality which was available when I wrote this post has changed quite a bit, and doesnt really match up to what youre going to see in an up-to-date build or ConfigMgr.
Sccm Console Client Mac OS X System ShouldIfwhen I get my hands on another Mac I can look at updating the content (although Im really working with Azure and Chef these days), so I strongly recommend that you take a look at the work my colleague Peter Daalmans has been doing with ConfigMgr and Mac management. He blogs over at ConfigMgrBlog.com and hes keeping up with all the latest developments in Mac management using Configuration Manager. Build 7782 does work on Windows Server 2012, but its slightly buggy and I lost a huge amount of time in troubleshooting. Stick with W2K8R2 for the moment and save yourself a headache. The reason for this is that Mac OS X clients are treated as internet clients at all times. This means that they are manageable regardless of where they are (assuming your site server is externally-accessible) but also that they dont need to be joined to the domain. Check out this post for PKI certificate requirements in CM12. For the purpose of lab testing, this can be the internal FQDN of the site server it doesnt HAVE to be accessible externally. Ensure that Hardware Inventory, Software Inventory and Compliance Settings policies are enabled. Then, go to the Mobile Devices policy and change the option Allow users to enrol mobile devices to Yes, then click on Set Profile to create a new enrolment profile. Give the new profile a name like Mac Enrollment, select an internet-enabled management site code, add the relevant CA and select the certificate template created earlier for Mac enrolment. ![]() If you need to edit the hosts file to fudge it, from Terminal run sudo nano etchosts and add an entry. Open Safari and navigate to fqdn.siteserver and ensure that you get the IIS welcome page. You should have the following files: ccmsetup and CMClient.pkg, and a Tools folder containing CMAppUtil, CMDiagnostics, CMEnroll and CMUninstall. Watch the EnrollmentService.log file in the SMSCCMEnrollmentPointLogs folder on the site server to see the request being received and processed. Under Keychains select System, and the under Category select My Certificates. In the main panel should be a certificate registered with the same name as the Mac system. Expand the certificate and it should be linked to a Private Key named SCCM. Double-click on the private key and then select Access Control. Under Always allow access by these applications should be CCMClient and CMEnroll. The CCMClient and CCMAgent applications can be found under LibraryApplication SupportMicrosoftCCM, along with the Logs folder.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |