Answered by:
Test-owaconnectivity command is not working

Question
-
Hello Experts,
Can you please help me figure out how to successfully run this command please?
When I run test-owaconnectivity on one of our CAS servers, here is what I get:
WARNING: Test user 'extest_0c7dd26927464' isn't accessible, so this cmdlet won't be able to test Client Access server
connectivity.
Could not find or sign in with user domain.com\extest_0c7dd26927464. If this task is being run without c
redentials, sign in as a Domain Administrator, and then run Scripts\new-TestCasConnectivityUser.ps1 to verify that the
user exists on Mailbox server server.domain.com
+ CategoryInfo : ObjectNotFound: (:) [Test-OwaConnectivity], CasHealthCouldN...edInfoException
+ FullyQualifiedErrorId : 1C57E73D,Microsoft.Exchange.Monitoring.TestOwaConnectivitySo after that I ran new-TestCasConnectivityUser.ps1 on the script folder:
..:\Program Files\Microsoft\Exchange Server\V14\Scripts>Get-MailboxServer server.domain.com |
.\new-TestCasConnectivityUser.ps1
Please enter a temporary secure password for creating test users. For security purposes, the password will be changed r
egularly and automatically by the system if SCOM is installed. The password must be changed manually if SCOM is not ins
talled.
Enter password: *********
Update test user permissions on: server.domain.com
Click CTRL+Break to quit or click Enter to continue.:
UserPrincipalName: extest_210dc47e41cd4@domain.com
WARNING: The command completed successfully but no settings of 'domain.com/Users/extest_210dc47e41cd4'
have been modified.
WARNING: Test user 'extest_0c7dd26927464' isn't accessible, so this cmdlet won't be able to test Client Access server
connectivity.We do have a test account called "extest_210dc47e41cd4" but I don't know if that affects the test because the command test-owaconnectivity is working smoothly on the other site we have.
Currently, we do not have some issues on OWA connections or other CAS related issues. I just want to make this working for monitoring purposes on all our Exchange servers.
Thanks in advance!
Reynald
None
Thursday, November 20, 2014 11:50 PM
Answers
-
Hi,
From your description, I recommend you use the following cmdlet to test OWA connectivity.
Test-OwaConnectivity -URL:https://mail.contoso.com/owa -MailboxCredential:(get-credential contoso\administrator)
I have some tests in my environment using Exchange 2010, it occurs the same error as yours when running Test-OwaConnectivity. But when I use the above cmdlet, it works well.
For more information, here is an article for your reference.
Test-OwaConnectivity
http://technet.microsoft.com/en-us/library/aa997682(v=exchg.141).aspx
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support- Marked as answer by reynald13 Monday, November 24, 2014 4:16 PM
Monday, November 24, 2014 7:01 AMModerator
All replies
-
Hi All,
I appreciate any advise on this. Thanks in advance!
None
Friday, November 21, 2014 4:05 PM -
Hi,
From your description, I recommend you use the following cmdlet to test OWA connectivity.
Test-OwaConnectivity -URL:https://mail.contoso.com/owa -MailboxCredential:(get-credential contoso\administrator)
I have some tests in my environment using Exchange 2010, it occurs the same error as yours when running Test-OwaConnectivity. But when I use the above cmdlet, it works well.
For more information, here is an article for your reference.
Test-OwaConnectivity
http://technet.microsoft.com/en-us/library/aa997682(v=exchg.141).aspx
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support- Marked as answer by reynald13 Monday, November 24, 2014 4:16 PM
Monday, November 24, 2014 7:01 AMModerator -
You can try creating a test account first
http://exchangeserverpro.com/activesync-policies-cause-test-activesyncconnectivity-to-fail/
Tuesday, June 16, 2015 5:17 PM