I saw this error while attempting to install an update on Exchange 2010, but it can be seen on all flavours of Exchange. This is the ‘gist’ of the error;
[box]
Organization Preparation
Failed
Error:
The following error was generated when "$error.Clear();
install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\"+$RoleSchemaPrefix + "schema0.ldf")
" was run: "There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostExchange2003_schema0.ldf'. The error code is: 8224. More details can be found in the error file: 'C:\Users\{Username}\AppData\Local\Temp\ldif.err'".
There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostExchange2003_schema0.ldf'. The error code is: 8224. More details can be found in the error file: 'C:\Users\{Username}\AppData\Local\Temp\ldif.err'
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp
[/box]
Solution
This was an easy one to sort out, on one of your domain controllers open “Active Directory Sites and Services”, expand all the sites and look at the server names. In my case there was an old DC in the list (these are usually easy to spot as you cant ‘expand’ them), i.e.theres no NTDS settings below them.
Simply right click the offending server and delete it, then either force domain replication, or wait a while.
Related Articles, References, Credits, or External Links
I had a nightmare with this, (this morning). Client had an Exchange 2007 Server in a sub domain, and I am migrating them to Exchange 2016 (via Exchange 2013). While attempting to deploy the Exchange 2013 Server, the ‘Readiness Checks’ failed;
[box]
Error:
The Active Directory Schema isn’t up-to-date, and this user account isn’t a member of the ‘Schema Admins’ and/or ‘Enterprise Admins’ groups.
Error:
Global updates need to be made to Active Directory, and this user account isn’t a member of the ‘Enterprise Admins’ group.
Error:
The local domain needs to be updated. You must be a member of the ‘Domain Admins’ group and ‘Organization Management’ role group, or ‘Enterprise Admins’ group to continue.
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.
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.
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.
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.
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.
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.
Error:
Setup encountered a problem while validating the state of Active Directory: Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master. Run setup with the /prepareAD parameter on a computer in the domain {root-domain} and site (site-name}, and wait for replication to complete. See the Exchange setup log for more information on this error.
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.
Error:
Either Active Directory doesn’t exist, or it can’t be contacted.
[/box]
WOW! Thats some error list!
Solution
OK, I’m assuming from this point forward you ARE in the correct AD groups? Those being;
Schema Administrators
Enterprise Administrators
Exchange Organisational Management
Domain Admins
Note: If you’re in a sub-domain you can’t be in the Domain admins and Schema/Enterprise Admins groups, (see below).
At first I thought it was just a ‘bug’ that I’d seen before, you need to go to your user account in Active Directory and change your primary group from ‘Domain Users’ to ‘Enterprise Admins’, like so;
These Exchange servers were in a ‘Sub-domain’, so I had to go to the Root-domain, and go a bit ‘old-school’. Locate the Schema Master, (it will be in the root domain).
For some reason, every post says go to another DC in the same site as the Schema Master, and continue, well you can do that here? i.e. You can simply run the following commands on the same server!
The Windows component Server-Gui-Mgmt-Infra isn’t installed on this computer and needs to be installed before Exchange Setup can begin
Solution
This is a known problem when installing Exchange 2016 on Server 2016, and was fixed in Exchange 2016 (Cumulative Update number 4). You are probably installing Exchange 2016 from the RTM media, (downloaded from Microsoft.)
You need to download a newer version of the Exchange 2016, install media, CU4 or newer. Use the following link;
Seen today while installing Veeam 6.5 Backup and Recovery on Windows Server 2008 R2
The setup was unable to install new instance of Microsoft SQL server. Make sure this server meets minimum system requirements, or try installing it manually.
Solution
1. Press Windows Key+R > appwiz.cpl {enter} > Uninstall ALL references to SQL Server and Veeam (Warning: Obviously if the server is using SQL, SQL Express or MSDE for another reason then DON’T DO THIS).
2. Download and install SQL Express (SQLEXPR_x64_ENU.exe). Run the install and select default instance (accept the default name). I set the database for mixed mode authentication but you will probably be OK with Windows authentication.
3. This time it should complete without error.
4. Now run the Veeam setup again, and it will detect the already installed instance and run through without error.
Related Articles, References, Credits, or External Links
When trying to install SQL Server 2012 (Standard c/w SP2). This popped up;
Rule Check Result
Rule "Setup account privileges" failed.
The account that is running SQL Server Setup does not have one or all of the following rights: the right to back up files and directories, the right to manage auditing and the security log and the right to debug programs. To continue, use an account with both of these rights. For more information, see
http://msdn.microsoft.com/en-us/library/ms813696.aspx,
http://msdn.microsoft.com/en-us/library/ms813959.aspx and
http://msdn.microsoft.com/en-us/library/ms813847.aspx.
As I was logged in as the domain administrator, (yeah I know, but it’s my test network). I was confused.
Solution
1. Well, it turns out I don’t have those rights after all so lets grant them, Windows Key+R > Control admintools {Enter}.
2. Launch ‘Local Security Policy’.
3. Navigate to Security Settings >Local Policies > User Rights Assignment > Back up files and directories > Add in the user that’s being denied > Apply > OK.
4. In the same location locate ‘Manage auditing and security log’ > Add in the user that’s being denied > Apply > OK.
5. In the same location locate ‘Debug programs’ > Add in the user that’s being denied > Apply > OK.
6. Now try again, (remember if you added a group, you will need to log off and back on again.)
Related Articles, References, Credits, or External Links
When attempting to install the Microsoft Communications Managed API 4.0 on a Windows Server 2012 machine. You get the following error;
Setup has detected that this computer does not meet the requirements to install this software. The following blocking issue must be resolved before you can install Microsoft Unified Communications Managed API 4.0, Runtime software package.
Microsoft Unified Communications Managed API 4.0, Runtime required the following missing Windows Features.
-Media Foundation
1. Launch Server Manager (ServerManager.exe) > Manage > Add Roles and Features > Next > Next > Next > Scroll Down > Select Media Foundation > Next > Install.
Related Articles, References, Credits, or External Links
While trying to install Exchange 2010, the process fails with the following error.
[box]
Organization Preparation
FailedError:
The following error was generated when "$error.Clear();
install-ExchangeSchema -LdapFileName ($roleInstallPath + "SetupData"+$RoleSchemaPrefix
+ "schema0.ldf")
" was run: "There was an error while running 'ldifde.exe' to import the schema file 'C:WindowsTempExchangeSetupSetupDataPostWindows2003_schema0.ldf'. The error code is:
8224. More details can be found in the error file: 'C:Usersadministrator.{your-domain}
AppDataLocalTemp2ldif.err'".
There was an error while running 'ldifde.exe' to import the schema file 'C:WindowsTempExchangeSetupSetupDataPostWindows2003_schema0.ldf'. The error code is:
8224. More details can be found in the error file: 'C:Usersadministrator.{your-domain}
AppDataLocalTemp2ldif.err'
[/box]
Solution
1. The error is happening at the “Organization Preparation” stage, so let’s go ‘old school’ and do that manually.
2. Locate the server on your network that is the schema master (Locate FSMO Servers).
3. Put the Exchange 2010 DVD in the schema master (Or share it over the network and connect to it from the schema master server).
4. Drop to command line and change to the DVD Drive/Directory with the Exchange 2010 setup files in it.
5. ONLY do this if you have Exchange 2003 already! Run the following command, (If no Exchange 2003 present, skip to the next step).
While installing Exchange 2010 one of my client’s satellite sites, this is what I got.
Organizational Prerequisites Failed
Error: Setup needs to contact the Active Directory schema master but this computer
is not in the same Active Directory domain as the schema master {Site-Name}.
Error: Setup encountered a problem while validating the state of Active Directory: Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master. Run setup with the /prepareAD parameter on a computer in the domain root and site {Site-Name}, and wait for replication to complete.
Unfortunately I had migrated users and file and print onto this server, so putting it in the car and driving 50 miles north was not an option.
Solution
Luckily for me I had a domain controller at this site, so all I had to do was transfer the Schema Master Role to this site, Install Exchange, then move the role back to the correct server a the main site when I had finished.
