From what I see- loadgen 2013 can only run on anything less than w2012R2 OS and 2013.

Is this true?

When will the utility be updated to support the current builds? W2012R2 is nothing new. EX2013 isn't either.

This creates a huge burden for test environments.

I thought I found the root cause.

I had to add the local SYSTEM to the local exchange host User group Administrators.

I also added Local Service, but I believe the System on the local host added to the local admins group is the key.This is on W2012, NO R2, so I am going to install EX13CU8 on a R2 host, test the failure, add the SYSTEM to the local admin, test the success. I recall I had to do this years ago (the last time I used loadgen on 2013 on 2012 OS).

This is nowhere in the doc. If you think this result is from some other CFG issue- please let me know. This is the second time over years with different builds involved.

The FIX:

1) login to each exchange node as the exchange admin

2) open computer management

3) open users and groups

4) Select groups, and open the administrators group

5) Click Add group membership

6) select the source for the LOCAL HOSTNAME, NOT THE DOMAIN.

7) search for SYSTEM.

8) add it. Click OK.

I did not need to logoff for this to take effect, but usually it is best practice to logoff and refresh your group membership results.

This worked in original ex13 releases.

I applied it to CU8 and the mailboxes are created with an @ in the general details and nothing else.

Loadgen reports no errors in the UI- but the logs have exceptions.

I am going to fall back to EX13 CU4 SP1 and HOPE this works.

If anyone has a clue- please share it. This is taking enormous amounts of time.

Cheers!