Enhancements
The Jamf AD CS Connector now supports outbound connections for proxying communication with AD CS. In outbound communication mode, the connector initiates connections to Jamf Pro to retrieve certificate requests. This outbound configuration removes the need to disable firewall rules or locate servers in DMZ associated with inbound mode communications. Additionally, outbound communication mode is token-based rather than certificate-based.
If you have an existing AD CS integration and do not need outbound communication mode, Jamf recommends continuing to use Jamf AD CS Connector 1.1.0. You only need Jamf AD CS Connector 2.0.0 if you want to use outbound communication mode.
To move an existing AD CS integration from inbound to outbound communication mode, you must create a new PKI integration and deploy new or updated configuration profiles.