This error occurs because GSX Monitor is not configured properly as the account used to validate user connectivity and scan the CAS is not available in your Exchange organization. This article explains how to configure the CAS test account in the server scanning configuration to avoid this issue.
- The Exchange CAS led may be displayed in red, also affecting the CAS Array associated to this server.
- The information tooltip is displaying an error for selected protocols (either Active Sync, POP3, IMAP, OWA or Outlook) in the server scanning configuration:
- [Protocol name] Failed to find the mailbox.
In this article "username@domain" references the actual account configured in GSX Monitor to scan a CAS in your Domain, "extest_yourActiveDirectoryGUID" is the dedicated Microsoft Exchange diagnostic account where yourActiveDirectoryGUID is the Active Directory site GUID.
How to Solve the Issue
GSX Monitor relies on PowerShell tests run at the server level to validate user connectivity via a specific protocol. By default, the dedicated diagnostic account "extest_yourActiveDirectoryGUID" is used to validate protocol availability. For the CAS Role tests to work as designed, you have to manually create the required diagnostic account, as it is usually not enabled by default in Exchange environments:
- Connect remotely to an Exchange Server hosting the Mailbox role (the user account must be member of the "Organization Management" group).
- Open Exchange Management Shell.
- Locate and enter into the Exchange scripts folder (ie: cd C:\Program Files\Microsoft\Exchange Server\V15\Scripts)
- Execute New-TestCasConnectivityUser.ps1 (ie: .\New-TestCasConnectivityUser.ps1)
Each Active Directory site hosting Exchange servers may require a specific diagnostic account. If you are monitoring a multi-site configuration, the New-TestCasConnectivityUser.ps1 script has to be executed from one mailbox server of each Active Directory site.
NB: Active Directory sites are associated to network subnets (for example AD Site A is including 192.168.1.0/24 and AD Site B is including 192.168.2.0/24).
If for any reason you cannot use the"extest_yourActiveDirectoryGUID" default diagnostic account, from version 10.3, GSX Monitor also allows to use a regular user mailbox to perform CAS Protocols related checks. In the CAS Role configuration, simply select the "Use specific mailbox" option:
We highly recommend to use a dedicated account for GSX Monitor scanning.
To avoid conflicts with other tools running PowerShell tests, use the "extest_yourActiveDirectoryGUID" diagnostic account or create a standard user mailbox, without any special admin rights, dedicated to this purpose.
Microsoft Related Technote
Please find more information on how to Create Test Mailboxes for Synthetic Transaction Tests directly from Microsoft.