Correct. There are multiple issue/bugs when HTTPS MP is part of the MPlist, starting with OSD which the crucial one.
Other issues are policy download and client MP assignments. With CU3 I belive you can do MP affinity. The preferance for a client is HTTPS first. I was you, I would do some additional reading on known issues so you can be prepared in advance. Cesar A On Mar 23, 2015 9:08 AM, "Daniel Ratliff" <[email protected]> wrote: > There is a bug in 2012 R2 with MP lists in OSD. If you have HTTPS servers > that are inaccessible to the clients they will not fall back to the > non-HTTPS MPs to get policy. > > Daniel Ratliff > > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of Chris Nackers > Sent: Monday, March 23, 2015 11:57 AM > To: [email protected] > Subject: Re: [mssms] HTTP and HTTPS configured site systems > > Shouldn’t, you can run HTTP and HTTPS side-by-side without any issues. I > believe if memory serves, clients will prefer HTTPS, but if they don’t’ > have the appropriate cert, then they will fall back to HTTP > > Chris Nackers > Microsoft MVP – Enterprise Client Management > > > > > > > > > > On 3/23/15, 12:35 PM, "Brian McDonald" <[email protected]> wrote: > > >Hey all, > > > >I have a need to deploy an additional sync system in my environment to > >support needs HTTPS support (MP/DP/SUP) for an untrusted remote forest. > > > >This site system will reside in my internal domain along with my > >primary site and other HTTP configured site systems. With this > >configuration cause any issues for Intranet clients? > > > >Thanks! > > > >Brian > > > >Sent from my iPhone > > > > > > > > > The information transmitted is intended only for the person or entity to > which it is addressed > and may contain CONFIDENTIAL material. If you receive this > material/information in error, > please contact the sender and delete or destroy the material/information. > >
