Powershell

Test user ‘extest_b648a1a700f64’ isn’t accessible when running test-owaconnectivity

I was recently playing about in Exchange 2010 in preparation for my exam in a few days time and I noticed i was getting an error when i ran the test-owaconnectivity commandlet. I error message i was recieving was:

WARNING: Test user ‘extest_b648a1a700f64’ isn’t accessible, so this cmdlet won’t be able to test Client Access server
connectivity.
Could not find or sign in with user testlab.local\extest_b648a1a700f64. If this task is being run without credentials,
sign in as a Domain Administrator, and then run Scripts\new-TestCasConnectivityUser.ps1 to verify that the user exists
on Mailbox server EXCH2010A.testlab.local
+ CategoryInfo          : ObjectNotFound: (:) [Test-OwaConnectivity], CasHealthCouldN…edInfoException
+ FullyQualifiedErrorId : E56E7F0C,Microsoft.Exchange.Monitoring.TestOwaConnectivity

WARNING: No Client Access servers were tested.

Hmmmmmm OK. So i dug out the Exchange 2010 DVD and had a look in the scripts folder for the new-testcasconnectivityuser.ps1 and ran the script which gave the following output:

Please enter a temporary secure password for creating test users.  For security, the password will be changed regularly
and automatically by the system.
Enter password: **************
Create test user on:  EXCH2010A.testlab.local
Control-Break to quit or Enter to continue:
UserPrincipalName:  extest_b648a1a700f64@testlab.local
WARNING: The command completed successfully but no settings of ‘testlab.local/Users/extest_b648a1a700f64’ have been
modified.

You can um-enable the test user by running this command with the following optional parameters : [-UMDialPlan <dialplann
ame> -UMExtension <numDigitsInDialplan>] .Either None or Both must be present.

So now that he user was created I ran the test-owaconnectivity cmdlet again and got yet another error:

[PS] C:\Windows\system32>test-owaconnectivity
WARNING: [11:14:18.643] : The server returned the language selection page. This is the first logon for the test user.
WARNING: [11:14:23.503] : The test couldn’t sign in to Outlook Web App due to an authentication failure.
WARNING: [11:14:23.518] : Test failed for URL ‘https://exch2010a.testlab.local/owa/’.

ClientAccessServer MailboxServer URL                     Scenario Result  Latency Error
(ms)
—————— ————- —                     ——– ——  ——- —–
EXCH2010A.testl… EXCH2010A…. https://exch2010a.te… Logon    Skipped         The te…

So i ran the cmdlet again and finally – success 🙂

[PS] C:\Windows\system32>test-owaconnectivity | format-list

RunspaceId                  : c75fb48d-763e-4c36-ac63-54aace2925f2
AuthenticationMethod        : WindowsIntegrated
MailboxServer               : EXCH2010A.testlab.local
LocalSite                   : Default-First-Site-Name
SecureAccess                : True
VirtualDirectoryName        : owa (Default Web Site)
Url                         : https://exch2010a.testlab.local/owa/
UrlType                     : Internal
Port                        : 0
ConnectionType              : Plaintext
ClientAccessServerShortName : EXCH2010A
LocalSiteShortName          : Default-First-Site-Name
ClientAccessServer          : EXCH2010A.testlab.local
Scenario                    : Logon
ScenarioDescription         : Sign in to Outlook Web App and verify the response page.
PerformanceCounterName      : Logon Latency
Result                      : Success
Error                       :
UserName                    : extest_b648a1a700f64
StartTime                   : 31/10/2010 11:16:04
Latency                     : 00:00:00.1250016
EventType                   : Success
LatencyInMillisecondsString : 125.00
Identity                    :
IsValid                     : True

Be Sociable, Share!

5 Comments on “Test user ‘extest_b648a1a700f64’ isn’t accessible when running test-owaconnectivity

  1. Thanks for the post!

    You can also access the ‘new-TestCasConnectivityUse’r script from your Exchange 2010 installation folder…by default its under ‘C:\Program Files\Microsoft\Exchange Server\V14\Scripts’

  2. hello there and thank you for your info – I’ve certainly picked up something new
    from right here. I did however expertise a few
    technical points using this site, as I experienced to reload the site a lot of
    times previous to I could get it to load properly.

    I had been wondering if your web hosting is OK? Not that I am complaining, but sluggish loading instances times will
    very frequently affect your placement in google and can damage your high quality score if ads and
    marketing with Adwords. Anyway I am adding this RSS to
    my email and can look out for much more of your respective exciting content.

    Ensure that you update this again very soon.

Comments are closed.