Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win


Exchange 2010 install failing - Can't create Admin Group

Posted on 2011-03-09
Medium Priority
Last Modified: 2012-05-11
I'm having an issue trying to install Exchange 2010 into my Exchange 2003 environment. See below for the error message. Basically it can't create the Exchange Administrative Group (FYDIBOHF23SPDLT) during the hub transport installation portion.

Also, in the past I had manually delete an Exchange 2010 admin group because the server failed and couldn't be restored. Could this be causing the issue?
(this was previous issue - http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26470470.html)

[03/09/2011 17:04:00.0495] [2] Beginning processing new-exchangeserver -DomainController:'DC1.XX.XX.XXX' -Name:'MAIL'
[03/09/2011 17:04:00.0557] [2] Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[03/09/2011 17:04:00.0557] [2] Ending processing new-exchangeserver
[03/09/2011 17:04:00.0557] [1] The following 1 error(s) occurred during task execution:
[03/09/2011 17:04:00.0557] [1] 0.  ErrorRecord: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[03/09/2011 17:04:00.0557] [1] 0.  ErrorRecord: Microsoft.Exchange.Data.Directory.SystemConfiguration.DefaultAdministrativeGroupNotFoundException: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
   at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetAdministrativeGroup()
   at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetAdministrativeGroupId()
   at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeServer.PrepareDataObject()
   at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[03/09/2011 17:04:00.0573] [1] The following error was generated when "$error.Clear();
          if ($server -eq $null)
          new-exchangeserver -DomainController $RoleDomainController -Name $RoleNetBIOSName
        " was run: "Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.".
[03/09/2011 17:04:00.0573] [1] Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[03/09/2011 17:04:00.0573] [1] [ERROR-REFERENCE] Id=ProvisionServerComponent___84489810458648f5ac6e47811394a284 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[03/09/2011 17:04:00.0573] [1] Setup is stopping now because of one or more critical errors.
Question by:futureman0
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 3

Expert Comment

ID: 35088367
is you think that manual deletion is the issue, please go to ADIEDIT.msc and check whether ur able to see the AG there

Author Comment

ID: 35098665
Update, this is what is happening to me now (from another experts-exchange questions)


"Database is mandatory on UserMailbox error during install of Hub Transport"

Another suggestion was to try installing the other roles prior to the Hub Transport Role, so I also tried that. The Mailbox Role installed fine with no errors, as did the Client Access Role.

I then tried to install the Hub Transport Role again, and it worked! Rebooted server and then opened the Exchange Management Console, and voila, there it is, it appears we have Exchange 2010 again.

EXCEPT, now the mailbox role is failing with "Database is mandatory on UserMailbox. Property Name: Database".

I've tried deleting the FederatedEmail user account (per here http://support.microsoft.com/kb/978776), but when I go to recreate the account it fails.

This is another link regarding the issue - http://www.paulbrown.us/2009/12/adding-a-mailbox-server-role-to-exchange-2010-database-is-mandatory-on-usermailbox/

It states I need to manually add a exchange db to the homeMDB for CN=FederatedEmail.4c....

How I'm I suppose to manually add a db value to homeMDB when no Exchange 2010 db has been created??

Author Comment

ID: 35098981

setup.com /ps
setup.com /preparead
setup.com /pad

got me past the first error I posted about not being able to find the storage group.
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.


Expert Comment

ID: 35101051
have u tried deleting the water mark key and installing it again ??

teh above link has a pic which shows where the water mark key is present

Expert Comment

ID: 35101054
HKLM\Software\Microsoft\Exchange\v14.0\<name of role>.

Author Comment

ID: 35131911
I'm not seeing that value (see image)

Author Comment

ID: 35131929

Accepted Solution

futureman0 earned 0 total points
ID: 35158961
FIXED!! Using - http://www.paulbrown.us/2009/12/adding-a-mailbox-server-role-to-exchange-2010-database-is-mandatory-on-usermailbox/ 

Using ADSIEdit I put in the value of "CN=Mailbox Store (OLDMAILSERVER),CN=First Storage Group,CN=InformationStore,CN=OLDMAILSERVER,CN=Servers,CN=CCIC,CN=Administrative Groups,CN=XXXX,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=XXX,DC=XXXX,DC=XXX" for the homdMDB value for the federatedmail user/discovery.

This actually points two the old mail server that is still in operation (Exchange 2003). I put this value in for FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 and  DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852} for homeMDB value.

After the install was done the homeMDB for FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042
changed to  CN=Mailbox Database 0562700375,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=XXX,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=XXX,DC=XXXX,DC=XXX which points to the new server. For whatever reason the homeMDB value did NOT change for DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852}

The whole reason for all these problems is that my first Exchange 2010 server failed (VM) and had to be deleted. By not gracefully uninstalling Exchange 2010 on this system it really messed up things in AD.

Author Closing Comment

ID: 35187392
found my own solution!

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

There are times when we need to generate a report on the inbox rules, where users have set up forwarding externally in their mailbox. In this article, I will be sharing a script I wrote to generate the report in CSV format.
Are you an Exchange administrator employed with an organization? And, have you encountered a corrupt Exchange database due to which you are not able to open its EDB file. This article will explain all the steps to repair corrupt Exchange database.
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…
Suggested Courses

610 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question