Trying to run the script new-TestCasConnectivityUser
I just want to run this script and create a test user. I am running it on a 2010 CAS server. I keep getting the error:
CreateTestUser : Mailbox could not be created. Verify that OU ( Users ) exists and that password requirements.
I found numerous articles using Google saying you need to modify the script and change the variable $OrganizationalUnit to something besides users. That doesn't work. I even created a brand new unique OU and put that in the script. It just keeps failing coming back with whatever OU I designate in the script in the error message. I don't know what I am doing wrong. Maybe its the syntax in the script. I don't know. Can someone please tell me how they got around this!! Below is what I am defining $OrganizationalUnit as:
$OrganizationUnit = "Sites/testusers"
No matter what OU I specify in the script, it just keeps coming back telling me the OU does not exist.
CreateTestUser : Mailbox could not be created. Verify that OU ( Users ) exists and that password requirements.
I found numerous articles using Google saying you need to modify the script and change the variable $OrganizationalUnit to something besides users. That doesn't work. I even created a brand new unique OU and put that in the script. It just keeps failing coming back with whatever OU I designate in the script in the error message. I don't know what I am doing wrong. Maybe its the syntax in the script. I don't know. Can someone please tell me how they got around this!! Below is what I am defining $OrganizationalUnit as:
$OrganizationUnit = "Sites/testusers"
No matter what OU I specify in the script, it just keeps coming back telling me the OU does not exist.
Who is Participating?
I figured out what it was. I don't have an Exchange 2010 mailbox server yet. Just a CAS. Apparently when you specify a mailbox server, it has to be Exchang3e 2010. I have a test environment with an Exchange 2010 mailbox server and the exact same command worked when I specified an Exchange 2010 server. It would be nice if it told you that instead of just saying the OU does not exist.
1) Make sure that there is a Users OU just off the root of your organization. That's usually the case.
2) Make sure that the password you specify is complex. You'll never need to type it again, so I usually do something really complex.
When I run this script, usually all I have to do is supply the password, since it defaults to the Users OU, which usually always exists.
2) Make sure that the password you specify is complex. You'll never need to type it again, so I usually do something really complex.
When I run this script, usually all I have to do is supply the password, since it defaults to the Users OU, which usually always exists.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
-
Course of the Month11 days, 1 hour left to enrollMonitoring and Operating a Private Cloud with System Center 2012 R2 273 lessons
