new-TestCasConnectivityUser.ps1 fails with Verify that OU ( Users ) exists

5Oct/105

new-TestCasConnectivityUser.ps1 fails with Verify that OU ( Users ) exists

When trying to run the new-TestCasConnectivityUser.ps1 script the latter might fail with the following error

CreateTestUser : Mailbox could not be created. Verify that OU ( Users ) exists and that password meets complexity requirements.

The first thing you need to do is making sure that the password does meets complexity requirements however if you did and still having the failure you most probably have multiple OUs with name "Users" and that is why the script is failing.

The solution for this is to specify the OU in the command by running the following

get-mailboxServer | .\new-TestCasConnectivityUser.ps1 -OU domain.com/users

Enjoyed the post, what is next?

Grab our FULL RSS feed! or Email Updates then share it

About Antoine Khater

I have been working in IT consultancy and solution integration since 1998 and I consider myself lucky to be, one in a few, making a living out of my passion. I am also member of the famous Experts Exchange (profile here) online community where I try my best to share what I have learned along the road.

Tagged as: exchange 2007, exchange 2010, Exchange Server, power shell, troubleshooting Leave a comment

Jay

Thank you. But that backslash in “domain.comusers” alsmost made me pull out my hair…
Better make that “domain.com/users“
http://whygoogle.me/ akhater

Thanks for the typo notification, i've arranged it
Ian Vassallo

I actually got around this issue by adding a line as per below…

$adSiteGuidLeft13 = $exchangeServer.Site.ObjectGuid.ToString().Replace(“-”,”").Substring(0, 13);
$UserName = “extest_” + $adSiteGuidLeft13;
$SamAccountName = “extest_” + $adSiteGuidLeft13;
$UserPrincipalName = $SamAccountName + “@” + $exchangeserver.Domain
> $OrganizationalUnit = $exchangeserver.Domain + “/” + $OrganizationalUnit
http://whygoogle.me/ akhater

Thank you Ian for sharing the solution!

I will give it a go
http://www.facebook.com/Jaffa374 James Collins

THANKYOU!!!!! I did every single fix I can find with the OU’s, adding bits to the script, nothing, but yours did it! Finally I can sort autodiscover out

« Autodiscover/Outlook anywhere fails when using a wildcard certificate Quick Tip: Restarting all Microsoft Exchange services »

Latest Tweets

Lync 2010 mobility service is released along with various Mobile Clients check the deployment details http://t.co/1UJuOEsrJanuary 4, 2012 8:34
Just published: Extending Exchange 2010 Shadow Redundancy Cross Forest http://t.co/YhVKu2I4December 6, 2011 10:32
http://t.co/t6MvXuZSeptember 10, 2011 8:40
Lync tools and apps tabbed conversations http://www.zerohoursleep.com/2011/07/lync-2010-tabbed-conversations/July 31, 2011 12:09
Hitting the bed for the first time in 40hours or so, really feels like ZeroHourSleep :) night everyoneJuly 22, 2011 10:08

Follow @ZeroHourSleep (115 followers)