We did have LDAP working with a Linux infrastructure manager server, but it stopped working. We suspect the server may have been deleted from AD, but because no one here is a Linux expert we couldn't do any real troubleshooting - we couldn't even login to it. We decided to just build a new Infrastructure manager server but this time do it on a Windows server. We gave it the exact same hostname and IP as the previous one that we decommissioned so the firewall rules would all still point to the same location. At first we thought the new server could just slide in and pick up the role and restore LDAP but I found that when this new server enrolled, it created a new instance. I figured that's ok. I'll just give it a difference display name so I'll know where to point the new LDAP config. I cloned the existing LDAP config but changed the display name and pointed it to the new infrastructure manager instance.
The new infrastructure manager (on Windows server) is listed as a viable Jamf Infrastructure manager server and it is reporting as successfully checking in every 30 seconds. When I setup the LDAP connection and hit save, I got the following alert across the top of the page:
THE AUTOMATIC VERIFICATION IS IN PROGRESS FOR THIS CONNECTION. DO NOT EDIT THE SETTINGS UNTIL THE PROCESS COMPLETES.
I've waited over an hour and it is still stuck verifying. How long should this take?
I verified that all the ports are identical to the old config. The only thing that should be different is the specific JIM instance we're using. Do I keep waiting or is there something I'm missing?
The only thing I can find in the server log is a bunch of entries like this that started at the same time I clicked Save on the new LDAP config: