To work properly, correct.

J

From: [email protected] [mailto:[email protected]] On 
Behalf Of Iacaruso, Mike
Sent: Friday, November 15, 2013 11:43 AM
To: [email protected]
Subject: [mssms] RE: Running SCCM 2012 R2 HTTP clients in a HTTPS environment

So Jason with one MP set to HTTPS for client connections every system needs a 
client cert?

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Jason Sandys
Sent: Friday, November 15, 2013 11:12 AM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: Running SCCM 2012 R2 HTTP clients in a HTTPS environment

*nix management does *not* require HTTPS client communication. OSX does though.

Each client centric site role - MP, DP, SUP - can only communicate using either 
HTTPS *or* HTTP. Thus, if you only set up a single set of systems hosting these 
roles using HTTPS to support the OSX systems, then yes, every managed client 
will require a unique client auth cert. You can however, as eluded to, set up a 
second set of these systems that listen on HTTP. Clients will then choose the 
proper site system to communicate with based upon the presence of a client auth 
cert.

J

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Iacaruso, Mike
Sent: Friday, November 15, 2013 10:05 AM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] Running SCCM 2012 R2 HTTP clients in a HTTPS environment

I am setting up our new SCCM 2012 R2 environment and have enabled HTTPS 
communications and configured certificates due to the Mac and Linux client 
requirement we have.  With this configured do all Windows systems need a 
certificate to communicate with the MP and DP?  I thought Windows systems can 
communicate with either HTTP or HTTPS.  Right now the only way to get Windows 
clients installed and communicating is by requesting and enrolling the Windows 
PKI cert.

Mike Iacaruso
Enterprise Desktop Engineer
Office of Technology Services
Towson University
410-704-3965
[email protected]<mailto:[email protected]>







Reply via email to