Issues with Exchange 2013 iApp on 11.4.1

Hi Alex-

Just to make sure--are you running the 1.3.0 version of the iApp?

For your SSL question: What do you mean by "nothing would become available"? Do you mean that there weren't any serverssl profiles to select from the drop-down (meaning that you're not choosing the option to "Create a new Server SSL profile), or that you can't pass traffic when you select a profile that doesn't have the 'No TLSv1.2' option enabled? Or something else? If you provide some more details, we should be able to help.

Based on the fact that your OWA monitor works and your other two don't, I believe you have incorrect authentication credentials. The OWA monitor, even in Advanced mode, doesn't perform an authenticated connection when OWA is configured with Forms-Based Authentication. Instead, it just checks for the availability of the login form. The other two services use authenticated monitors; since they're failing, I suspect the format of the credentials you entered might not be quite right.

The 4 credential questions, and required format, are:

• What email address do you want to use for the advanced monitors?

This is required to format a valid XML POST for Autodiscover. It should be in normal user@mycompany.com format.

• Which mailbox account should be used for monitors?

This is the Windows username. Mine, for instance, might be dmiller (exact format will be specific to your domain, of course). This has to be the username associated with the mailbox email address entered in the previous field.

• What is the password for that mailbox account?

Self-explanatory ;) I believe we accept all extended characters that are valid for Windows passwords; the only exception is that a password can not start with one or more leading blank spaces.

• What is the domain name of the user account for the monitors?

This is the question most often answered incorrectly. The domain is the short (NetBIOS) version of the Windows domain (example: MYDOMAIN) or the FQDN (example: mydomain.com). In neither case should you have a trailing backslash or any other character.

Please try adjusting the credentials; make sure you're using an account that hasn't been locked!