joeware - never stop exploring... :)

Information about joeware mixed with wild and crazy opinions...

Now this is stupid… Go Exchange Dev Team…

by @ 11:18 pm on 11/9/2007. Filed under tech

http://support.microsoft.com/?kbid=944332

 

User Creation via PowerShell Did Not Succeed When Using LoadGen on Exchange Server 2007

Cause

This error may occur if the user account running LoadGen is not a member of the Enterprise Administrators group. This is one of the requirements.
If you do not log on as the Enterprise Administrator (for example if you log on as the local administrator), Exchange Load Generator cannot create users in Active Directory. Exchange Load Generator must have sufficient rights to create users, organizational units, distribution groups, and query-based distribution groups. Exchange Load Generator must be running under an account that is a member of the Enterprise Administrators group.

 

Resolution

Use Active Directory Users and Computers (ADUC) to add the user to Enterprise Administrator Group.
To view the group membership of a user, double-click the user account name in the Active Directory Users and Computers snap-in, and then click Member Of. If you are logged on as a user who has the correct permissions, you can add a user to a security group. To add a user to a security group, double-click the group in the Active Directory Users and Computers snap-in, click Members, and then click Add.

I guess the person working on this tool hadn’t taken his Active Directory nor “Get a Security clue” classes yet.

I am amazed someone could publish that article without being completely embarrassed.

Rating 3.00 out of 5

3 Responses to “Now this is stupid… Go Exchange Dev Team…”

  1. Deji says:

    Your displeasure is directed at the wrong person – the KB author.

    The author is just regurgitating a known fact. The LoadGen documentation contains this requirement, so it is not something that the KB author invented. It is also a known fact that LoadGen requires a lot of baby-sitting to get it to work successfully, IF you don’t give it EA access.

  2. joe says:

    My displeasure is aimed at the Exchange Team.

  3. Rich Milburn says:

    I’m amazed they manage to get Exchange working with AD at all with that kind of blunder. At least you don’t also have to be a member of Schema Admins and enable it using ADSIEdit…

[joeware – never stop exploring… :) is proudly powered by WordPress.]