Exchange 2010 ships with a number of test cmdlets to test the CAS functionality, like testing Outlook, OWA, ActiveSync, POP, IMAP etc. But whenever you try and run a test cmdlet like Test-OutlookConnectivity, it will complain that it can’t find a test mailbox.
Exchange 2010 ships with a script to create a test mailbox to run these test cmdlets. It’s named “New-TestCASConnectivityUser.ps1” and is stored in the Scripts directory. I ran this script in my lab only to be greeted with an error!
CreateTestUser : Mailbox could not be created. Verify that OU (Users) exists and that password meets complexity requirements.
I am sure that the password I entered was a complex one. That left me with the second half of the error message. I do have a “Users” OU and hence I took a look at the script only to find that the OU name is coded as “Users”. As I have (and many other companies have) more than one OU named “Users”, the script throws the error message.
There are number of solutions for this issue.
- Edit your OU structure so that there is only one OU named “Users”.
- Edit the script with the distinguished name of the OU named “Users”.
- If you have a specific OU for test/service accounts, specify the DN of that OU in the script.
Once I made the changes, I was able to create the test account successfully using the script.
Fritz January 11, 2012 at 5:02 pm
Thank you!
Rajith Enchiparambil January 13, 2012 at 10:31 am
No problem Fritz.
Jos Hollink March 12, 2012 at 2:22 pm
The problem here is that the script uses OU=Users. The default users object is not an OU but a Container. Therefore it returns the error. Modify the script to use another OU of your choice
Rajith Enchiparambil March 20, 2012 at 12:42 pm
Thanks Jos.
RobertK March 8, 2012 at 7:29 pm
Thanks for the info. Would you know why after running the script you get the yellow warning? and why would you be getting it?
thank you
Rajith Enchiparambil March 9, 2012 at 2:39 pm
Hi Robert,
That is normal. It is just saying that the settings for the mailbox has not been modified. Safe to ignore.
Peter Jonkers June 6, 2012 at 1:34 pm
Nothing helped in the above solutions.
my solution was to delete the recovery database that was still running.
Cheers
Peter
Rajith Enchiparambil June 26, 2012 at 2:03 pm
Thanks for the tip Peter.
Voffka July 24, 2012 at 11:56 am
Really helps a lot !!! tnx !
Rajith Enchiparambil July 26, 2012 at 9:07 am
Glad to help Vofka
RUbenB November 16, 2012 at 12:25 pm
When reading the script, I found that the $arg after $arg = “OU” replaces the default OU value;
Therefore, you could use the New-TestCasConnectivityUser.ps1 -OU “domain.local/Users” command in stead.
Rajith Enchiparambil November 28, 2012 at 9:39 am
True RubenB. Thanks for sharing.