Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  • Windows 2003, Windows 2008, Windows 2012, Windows 2012 R2
  • .NET Framework 4.0 or later
  • approx. 20MB of free disk space
  • approx. 200MB of available RAM





Note MSIgithub Evolveum/ConnId (branch master)Experimental. Adds support for filtering results handler validation mode and paged searches in AD connector. MSIgithub Evolveum/ConnId (branch master)Seems to be quite stable. We recommend to use this one.

ZIP MSIgithub Evolveum/ConnId (branch openicf-1.1)Obsolete - to be used with pre-3.0 versions of midPoint.


Execute ServiceInstall-*.msi and follow the wizard. When it completes the Connector Server will be installed as a windows service.



You may need to change the identity of the Connector Server service. Local user account may not be sufficient for some operations. Open the Services console, edit properties of "ConnectorServerService". Specify a valid domain account in the "Log On" tab.


Configuring SSL

The Connector Server is a SSL server. Therefore is needs a keypair (private key + certificate). .NET Connector Serve is using Windows certificate stores to keep the certificates and keys.



If the Connector Server Service is configured to run as specific user (not LocalSystem) and it does not start automatically although it is configured to do so, and Event Viewer complains that "The account name is invalid or does not exist, or the password is invalid for the account name specified", please try if you can start the service manually to check if the user/password are ok. If you are perfectly able to start the service manually, but automatic start does not work, please set the startup for the service to "Automatic (Delayed)".


See Also