It may let you login but that’s because active directory integration is working and now exchange. CloudPanel uses the /powershell virtual directory on…

It has to be one of those things I mentioned. Please send screenshots of your IIS application pools, and the basic settings showing the CloudPanel app…

The error you are getting is actually from Exchange. So either the application pool isn’t set to the right user, the application isn’t associated with…

That usually is caused by the application pool in IIS that the CloudPanel virtual directory is running under isn’t set to an exchange organization adm…

Allowed Authenticated Users can expose data (read only) which is why we remove it and add the AllUsers@ group to the organization unit. My guess is yo…

That is great to hear! Let us know if you need anything else.

No the autodiscover redirect method is recommended because Outlook checks that before the SRV (SRV is last). What I was saying is its not recommended …

Use the same account you used in CloudPanel and on the application pool for the service username/password. It will need the same rights

That is because you do not seem to be running the CloudPanel Scheduler. There is two downloads with every CloudPanel released, one for CloudPanel and …

CloudPanel is going to do a DNS lookup. So if you are adding multiple IP addresses to your Exchange server for the autodiscover redirect method (not r…

Those fields should be populating, for sure. What version of CloudPanel are you using?

If you are getting that message then it cannot be set on basic. You need to use Exchange ECP to make sure it is set on Basic. Do not adjust this with …

When you patch Exchange it resets the Basic Authentication flag on the /powershell virtual directory. Use ECP and enable it again. No idea why it rese…

CloudPanel doesn’t validate the SSL when it connects. I would first make sure both the CloudPanel server and the Exchange server are patched. Do you s…

Are you pointed to a load balancer? Also you may want to check the eventviewer on both servers because that error is being returned by the powershell …