@AlanSmith Nope! With macOS's built-in API's/processes, if we are
leveraging LDAPS and enforcing LDAP signing, the Mac will know to switch
to 636 of its own accord. That is done via GPO and ensuring a valid
LDAPS TLS cert is in place on the DC in the...
Hello again everyone! Just a quick update for you. Thanks to user
@hlans question above, I double-checked my work and soon discovered what
you all had already reported: the default behavior at this time for the
PacRequestorEnforcement key is one (1)...
@jgarland I was able to get this to work! Take a look at my reply above
in this same thread. Let's give this another shot using LDAPS over port
636 and see if we can't confirm that this is working well before the
upcoming cutoff in July. I'll be test...
@AlanSmith Yes, that would be me! I successfully updated my DC with the
standalone update from Microsoft today and confirmed it was installed. I
then did a test bind without Jamf Pro in the mix using `dsconfigad` and
was able to successfully bind my ...
Hey everyone! :Ben from Jamf Support here. For those following this
thread, I'm curious if you are seeing the same error when binding Macs
using LDAPS. For anyone who is testing this, can you please let us know
if the behavior persists when using po...