Error:
Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalUpdateRequired.aspx

Error:
You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx

Error:
Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx

Error:
The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2013, the forest functional level must be at least Windows Server 2003 native.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ForestLevelNotWin2003Native.aspx

Error:
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx

Warning:
Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx

Warning:
Setup can't contact the primary DNS server (192.168.1.1) using TCP port 53. Check that the IP address of the DNS server is correct and that the DNS server is reachable.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.PrimaryDNSTestFailed.aspx

Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx

Hi

Is the Exchange server on a separate server from the DC?  What happens if you ping the FQDN of the domain (e.g. yourdomain.local) from the Exchange server?  If you are using separate servers then try to remove the Exchange server from the domain and join it again.

Cheers, Steve

Hi Steve,

Thank you for your quick response to my question.

I try to install Echange 2013 on my DC as I only have one server.
Pinging to domain.local results in a reply from DC.

Tried to test DNS by using dcdiag /test:dns and passed just fine.

DNS is set to server IP. (itself)
Using loopback address will do the same, right?

Something went wrong installing Exchange this afternoon, probably because I renamed a site on IIS.
I eventually ended up reinstalling it later on. It didn't showed this error the first time, instead it began installing right away.

Could this indicate that there are some leftovers of my previous partially installed exchange that I need to take car

I first uninstalled Microsoft Exchange from my server, removed the existing site (which was renamed) and Exchange backbone on IIS, then added a new site to my server.

After that I did a rebooted, this is all I basically did.

Maybe I should plan to renstall it, since no backups were made yet (waiting for an extra sas drive)
I just don't know where to look further.

• Edited by Shadow_of_Light Thursday, February 28, 2013 10:33 PM

did you uninstall via add/remove programs? was it a clean uninstall?

what do you removed the existing site?

Is this a live enf, AD e?

No it's not online yet, otherwise I wouldn't dare taking this gamble ;)

I've renstalled Windows Server 2012, I will be installing Exchange 2013 this afternoon.
If anything goes wrong, I will let you know.

Thank you for your help, I appreciate it.

I think I might need some help installing Microsoft Exchange, since this is quite an unusual case.
Basically what I want to do is install it on a domain controller, which is not recommended by Microsoft.

I've only got one server that should be more than powerful enough to handle both roles given the number of people that will be using it.

I've read that in order to do so, not only do I have to perform the prerequisites, but also leave IPv6 protocol enabled and such in which I'm not very confident that it will succeed.

I thought about upgrading memory and running a virtual console, but it's license won't come cheap...
On top of that, running a virtual console will reduce overall performance.

Could you or anyone else give me some advise concerning preparations besides the basic prerequisites?

Thank you.

http://technet.microsoft.com/en-us/library/ms.exch.setupreadiness.warninginstallexchangerolesondomaincontroller(v=exchg.150).aspx

Too many possible issue, there may be even more which are not documented. Reinforce this to senoir management & purchase more license & hardware.

I've purchased another license of Windows Server 2012 standard.
I will stick to my plan and use Hyper-V for Microsoft Exchange 2013.

So far, so go

I got all the same (re-install of Exchange 2013 on Windows Server 2012, same errors).

Solved it as follows:

1) Go to directory 'C:\Program Files\Microsoft\Exchange Server' and then delete the 'Exchange Server' Folder

2) Delete the Exchange folders from Active Directory ('Microsoft Exchange Security Groups' and 'Microsoft Exchange System Objects') see http://technet.microsoft.com/en-us/library/aa998138(v=exchg.80).aspx for how.

Cheers

Varus Septimus

• Proposed as answer by Varus Septimus Monday, July 15, 2013 8:38 PM

I am not if this will help any one but I spent 10 hours trying every fix on the net and it ended up being stupid simple, I went under active directory users and computers and under the computer name i was installing exchange i right clicked went to properties, then added enterprise admins under member of tab. hope this helps someone