Hi,

long story but I had exchange server working on a server 2012 DC and it broke.
after weeks of trying to remove and reinstall I gave up and have purchased another server.
I installed server 2012 on this new server and then installed Exchange 2013 within Server 2012 on new server so it's no longer on a DC.
Installed ok and I can log into OWA and ECP but only using the administrator account which I guess is normal.
My problem is logging into ECP, it's missing 90% of the options, I can't add new users or anything within ECP.

If I create a new AD user and give them access to the various exchange security groups it still refuses to grant access to this new user.
It seems to be ignoring the settings in the AD
I'm pulling my hair out, if someone could please help I would really appreciate it.

Regards

Jamie

Jamie,

Check, if the 'Administrator' account is a member of 'Organization Management'. If this is not giving any help, create a new administrative user and add as a member of 'Organization Management'. Login with the new user and see how ECP works

Hi Administrator is already a member of Organization Management.

I created a new user and also added it to Organization Management but ECP won't even allow it to log in

403 Sorry Access Denied :(

EMS won't allow me to run cmds either

Get-RoleGroup
says its not recognized :(

Anyone able to help?

Hi Jamie,

Have you prepared AD for your exchange 2013?

I recommend you upgrade the exchange 2013 to CU9 with preparing AD & Schema, and check the result.

Prepare AD and Prepare Schema for Exchange 2013 CU9

Prepare Active Directory and domains

How do you know this worked:

After Exchange extends your Active Directory schema and prepares Active Directory for Exchange, several properties are updated to show that preparation is complete. Use the information in the following list to make sure these properties have the right values. Each property needs to match the value in the table below for the release of Exchange 2013 that you're installing.

• In the Schema naming context, verify that the rangeUpper property on ms-Exch-Schema-Verision-Pt is set to the value shown for your version of Exchange 2013 in the Exchange 2013 Active Directory versions table.

• In the Configuration naming context, verify that the objectVersion property in the CN=<your organization>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<domain> container is set to the value shown for your version of Exchange 2013 in the Exchange 2013 Active Directory versions table.

• In the Default naming context, verify that the objectVersion property in the Microsoft Exchange System Objects container under DC=<root domain is set to the value shown for your version of Exchange 2013 in the Exchange 2013 Active Directory versions table.

Best regards,

Hi Niko,

Thanks for your reply, I had already tried that and unfortunately it mad no difference.

I ended up formatting the box and building a completely separate network  for my exchange.

I keep my existing DC server and then built another server box with DC & Exchange in VM's

After weeks of trying to reinstall on old server and then trying to still use old DC for exchange I just couldn't get it to function.

New server seems to be working ok and on the plus side I'm no longer using a .local domain

Cheers

Jamie