If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.
COURSE of the MONTH
13 days, 11 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Exchange 2010 install failing - Can't create Admin Group
Posted on 2011-03-09
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.
[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.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Managem
at Microsoft.Exchange.Configu
at Microsoft.Exchange.Configu
[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=ProvisionServerComponen
[03/09/2011 17:04:00.0573] [1] Setup is stopping now because of one or more critical errors.
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.
[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.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Managem
at Microsoft.Exchange.Configu
at Microsoft.Exchange.Configu
[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=ProvisionServerComponen
[03/09/2011 17:04:00.0573] [1] Setup is stopping now because of one or more critical errors.
[X]
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
9 Comments
is you think that manual deletion is the issue, please go to ADIEDIT.msc and check whether ur able to see the AG there
Update, this is what is happening to me now (from another experts-exchange questions)
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26296094.html
"Database is mandatory on UserMailbox error during install of Hub Transport"
http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/214ded66-f987-4023-9158-9a80e6477e2b
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??
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26296094.html
"Database is mandatory on UserMailbox error during install of Hub Transport"
http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/214ded66-f987-4023-9158-9a80e6477e2b
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??
also
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.
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.
have u tried deleting the water mark key and installing it again ??
http://msexchangeteam.com/archive/2007/05/21/439529.aspx
teh above link has a pic which shows where the water mark key is present
http://msexchangeteam.com/archive/2007/05/21/439529.aspx
teh above link has a pic which shows where the water mark key is present
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,
This actually points two the old mail server that is still in operation (Exchange 2003). I put this value in for FederatedEmail.4c1f4d8b-81
After the install was done the homeMDB for FederatedEmail.4c1f4d8b-81
changed to CN=Mailbox Database 0562700375,CN=Databases,CN
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.
Using ADSIEdit I put in the value of "CN=Mailbox Store (OLDMAILSERVER),CN=First Storage Group,CN=InformationStore,
This actually points two the old mail server that is still in operation (Exchange 2003). I put this value in for FederatedEmail.4c1f4d8b-81
After the install was done the homeMDB for FederatedEmail.4c1f4d8b-81
changed to CN=Mailbox Database 0562700375,CN=Databases,CN
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.
Featured Post
Managing Active Directory does not always have to be complicated. If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
In this video we show how to create a mailbox database 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 Servers >> Data…
To show how to generate a certificate request 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 Servers >> Certificates…
Suggested Courses
Course of the Month13 days, 11 hours left to enroll
801 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.