Wrong link I sent for the current mac client
Correct one http://www.microsoft.com/en-us/download/details.aspx?id=36212 [signature] From: Thomas Gonzalez Sent: Tuesday, June 25, 2013 9:44 AM To: [email protected] Subject: RE: [mssms] RE: Mac client installation Last item: http://www.microsoft.com/en-us/download/confirmation.aspx?id=36212 contains the new Mac client that supports OSX 10.8 [signature] From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Thomas Gonzalez Sent: Tuesday, June 25, 2013 9:30 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] RE: Mac client installation Mike, here’s the link to the patch I used in the lab, http://support.microsoft.com/kb/938397?wa=wsignin1.0 we have CA Enterprise on windows 2003 in the production environment, we upgraded to Windows 2008 R2 to ensure that the Macs will accept the SHA2. Also, verify that the cert has installed correctly on the Mac, --> Utilities --> Keychain Access --> System and category select My certs, should be registered with the same name. Expand the cert and the private key SCCM should be linked, and on the Access control make sure “Always allow access by the apps” (CMEnroll and CCMClient) Now, the one item we are having issues with on the Mac side is when deploying plist changes to firewall, desktop and other items, the Macintosh is not processing and the SMS_DM is showing a forbidden error and the component classes are error’n. The HINV/SINV reports back as expected. We have a PSS involved with our Mac Engineer to see why the forbidden and component classes are error’n. The minor items we are testing is changing home page, firewall disabling, file vault info. Now the software deployment to a Mac has begun error’n and we are seeing a 0x87d00238 error in the SMS_DM and the client logs are not recording the error. As many folks have seen and voiced, they are either going to parallels since they are placing their own agent and does not require PKI setup, but communicates over 80 rather than 443. I hope this helps, and I apologize for the delay, been hectic since I’m in involved with NAC/BYOD/RSA and also creating a self-service portal for BYOD [signature] From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Monday, June 24, 2013 2:33 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] RE: Mac client installation bump From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Tuesday, June 18, 2013 5:20 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] RE: Mac client installation Thanks, I’d appreciate it! From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Thomas Gonzalez Sent: Tuesday, June 18, 2013 5:13 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] RE: Mac client installation Mike what sha version are you using? I found during the lab test I had to apply a patch to the 2k3 ca or upgrade to 2k8 to conform with the requirements. When I get back on Friday I'll send you what I did, if you haven't resolved it by then ________________________________ From: Murray, Mike<mailto:[email protected]> Sent: 6/18/2013 7:04 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Mac client installation Here’s some errors from the Mac client log file. <![LOG[OMA Session failed with error code 0x80004005 ]LOG]!><time="16:59:54.755+007" date="06-18-2013" component="Default" context="" type="3" thread="2956050432" file="OMADMService.mm:410"> <![LOG[Failed to connect to DMP]LOG]!><time="16:59:54.755+007" date="06-18-2013" component="Default" context="" type="3" thread="2956050432" file="OMADMService.mm:345"> <![LOG[OMA : Sending Notification to UI : <CCMClientNotification><Sender>Service</Sender><Name></Name><Id></Id><Type>CCM_OMA</Type><State>Error</State><Data>-2147467259</Data><Description></Description><RebootRequired></RebootRequired><Time></Time></CCMClientNotification>]LOG]!><time="16:59:54.755+007" date="06-18-2013" component="Default" context="" type="1" thread="2956050432" file="OMADMService.mm:271"> <![LOG[No Preferences found for Key - 'OMAFailureRetryDelayInSec', Domain - 'com.microsoft.ccmclient'.]LOG]!><time="16:59:54.755+007" date="06-18-2013" component="Default" context="" type="1" thread="2956050432" file="OSXUtilities.mm:456"> <![LOG[CCMClient - Broadcasting Msg to UI : <CCMClientNotification><Sender>Service</Sender><Name></Name><Id></Id><Type>CCM_OMA</Type><State>Error</State><Data>-2147467259</Data><Description></Description><RebootRequired></RebootRequired><Time></Time></CCMClientNotification>]LOG]!><time="16:59:54.755+007" date="06-18-2013" component="Default" context="" type="1" thread="2900179496" file="NotificationProcessor.mm:65"> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Tuesday, June 18, 2013 4:37 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Mac client installation Anyone successfully using the Mac client in CM2012? I set up the certificate on my SCCM server, copied it to the keychain on a Mac, then ran the install instructions detailed under “To install the client certificate independently from Configuration Manager and install the client” here: http://technet.microsoft.com/en-us/library/jj591553.aspx#BKMK_Step8 The client is installed and says it has the management point correct in the CM window under system preferences. However, when I click the connect button, it fails. Any ideas? [cid:[email protected]] Best Regards, Mike Murray Desktop Management Coordinator - IT Support Services California State University, Chico 530.898.4357 [email protected]<mailto:[email protected]> [The entire original message is not included.]
<<inline: image001.png>>
