Let me finish up my meeting and I’ll send you the patch and process we did
[signature] From: [email protected] [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Monday, June 24, 2013 2:33 PM To: [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>>
