Exchange 2010 - Test User Solutions

Exchange 2010 - Test User

I'm trying to run the cmdlet test-outlookconnectivity and other test cmdlets, but they fail. I tried running the new-testcasconnectivityuser.ps1 script to create the test user they complain about, but it errors with an invalid error. I have the OU = Users and my password met the complexity requirements.

[PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>.\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.
Enter password: *************
Create test user on: EXCHANGE.domain.local
Click CTRL+Break to quit or click Enter to continue.:
CreateTestUser : Mailbox could not be created. Verify that OU ( Users ) exists and that password meets complexity requi
rements.
At C:\Program Files\Microsoft\Exchange Server\V14\Scripts\new-TestCasConnectivityUser.ps1:267 char:31
+ $result = CreateTestUser <<<< $exchangeServer $mailboxServer $securePassword $OrganizationalUnit $UMDialPlan $
UMExtension $Prompt
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,CreateTestUser

View Solution Only

mmusurlian

Commented: 2011-11-01

Just a thought ...

I had a colleague with a similar issue - turned out to be a script error - he opened the script in notepad and found the line beginning “new-mailbox” – and deleted the parameter “–OrgainisationalUnit:$OrganistationalUnit”. This means the new user defaults to the default OU – Users!

Also, Looks like this can also occur if there's more than one OU called Users

Radweld

Commented: 2011-11-02

Yeah this nearly always occurs because the script is a little stupid and defaults to Ou=users, you can modify the script to create the account anywhere.

LrdKanien

Author

Commented: 2011-11-02

I removed that line you said, but there is a user logon error now. I saw the user in extest in the Users OU.

Here is the error:
[PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>Test-EcpConnectivity -ClientAccessServer fcs-exchange |fl

RunspaceId : 415956e3-084f-42c7-869a-9d42349ba41a
LocalSite : FosterCityOffice
SecureAccess : True
VirtualDirectoryName :
Url :
UrlType : Unknown
Port : 0
ConnectionType : Plaintext
ClientAccessServerShortName : FCS-EXCHANGE
LocalSiteShortName : FosterCityOffice
ClientAccessServer : FCS-EXCHANGE.NewSunNutrition.local
Scenario : Reset Credentials
ScenarioDescription : Reset automated credentials for the Client Access Probing Task user on Mailbox server EXC
HANGE.NewSunNutrition.local.
PerformanceCounterName : Logon Latency
Result : Failure
Error : [Microsoft.Exchange.Monitoring.CasHealthStorageErrorException]: An error occurred while t
rying to access mailbox EXCHANGE.NewSunNutrition.local, on behalf of user NewSunNutrition
.local\extest_2d576f973d874

Additional information:
[Microsoft.Exchange.Data.Storage.WrongServerException]: The user and the mailbox are in
different Active Directory sites..
UserName : extest_2d576f973d874
StartTime : 11/2/2011 1:15:42 AM
Latency : 00:00:00.0156211
EventType : Error
LatencyInMillisecondsString :
Identity :
IsValid : True

Radweld

Commented: 2011-11-02

If you have not already done so, upgrade your Exchange 2010 server to SP1 RU5 (I know RU 6 is out but you never trust a new RU on the week it's released)

Rajith EnchiparambilOffice 365 & Exchange Architect

Commented: 2011-11-02

DONT tweak the script the way mentioned above. The issue is that either the password is not complex or you have more than one OU with "Users" as the name.

Check http://www.howexchangeworks.com/2011/07/new-testcasconnectivityuserps1-script.html