LrdKanien
asked on
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-testcasconnectivityuse r.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-T estCasConn ectivityUs er.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-Tes tCasConnec tivityUser .ps1:267 char:31
+ $result = CreateTestUser <<<< $exchangeServer $mailboxServer $securePassword $OrganizationalUnit $UMDialPlan $
UMExtension $Prompt
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Comma nds.WriteE rrorExcept ion,Create TestUser
[PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>.\new-T
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-Tes
+ $result = CreateTestUser <<<< $exchangeServer $mailboxServer $securePassword $OrganizationalUnit $UMDialPlan $
UMExtension $Prompt
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Comma
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.
ASKER
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-Ec pConnectiv ity -ClientAccessServer fcs-exchange |fl
RunspaceId : 415956e3-084f-42c7-869a-9d 42349ba41a
LocalSite : FosterCityOffice
SecureAccess : True
VirtualDirectoryName :
Url :
UrlType : Unknown
Port : 0
ConnectionType : Plaintext
ClientAccessServerShortNam e : FCS-EXCHANGE
LocalSiteShortName : FosterCityOffice
ClientAccessServer : FCS-EXCHANGE.NewSunNutriti on.local
Scenario : Reset Credentials
ScenarioDescription : Reset automated credentials for the Client Access Probing Task user on Mailbox server EXC
HANGE.NewSunNutrition.loca l.
PerformanceCounterName : Logon Latency
Result : Failure
Error : [Microsoft.Exchange.Monito ring.CasHe althStorag eErrorExce ption]: An error occurred while t
rying to access mailbox EXCHANGE.NewSunNutrition.l ocal, on behalf of user NewSunNutrition
.local\extest_2d576f973d87 4
Additional information:
[Microsoft.Exchange.Data.S torage.Wro ngServerEx ception]: 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
LatencyInMillisecondsStrin g :
Identity :
IsValid : True
Here is the error:
[PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>Test-Ec
RunspaceId : 415956e3-084f-42c7-869a-9d
LocalSite : FosterCityOffice
SecureAccess : True
VirtualDirectoryName :
Url :
UrlType : Unknown
Port : 0
ConnectionType : Plaintext
ClientAccessServerShortNam
LocalSiteShortName : FosterCityOffice
ClientAccessServer : FCS-EXCHANGE.NewSunNutriti
Scenario : Reset Credentials
ScenarioDescription : Reset automated credentials for the Client Access Probing Task user on Mailbox server EXC
HANGE.NewSunNutrition.loca
PerformanceCounterName : Logon Latency
Result : Failure
Error : [Microsoft.Exchange.Monito
rying to access mailbox EXCHANGE.NewSunNutrition.l
.local\extest_2d576f973d87
Additional information:
[Microsoft.Exchange.Data.S
different Active Directory sites..
UserName : extest_2d576f973d874
StartTime : 11/2/2011 1:15:42 AM
Latency : 00:00:00.0156211
EventType : Error
LatencyInMillisecondsStrin
Identity :
IsValid : True
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)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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:$Org
Also, Looks like this can also occur if there's more than one OU called Users