• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2088
  • Last Modified:

Exchange 2010 install failing - Can't create Admin Group

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.
0
futureman0
Asked:
futureman0
  • 6
  • 3
1 Solution
 
praveenkumare_spCommented:
is you think that manual deletion is the issue, please go to ADIEDIT.msc and check whether ur able to see the AG there
0
 
futureman0Author Commented:
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??
0
 
futureman0Author Commented:
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.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
praveenkumare_spCommented:
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
0
 
praveenkumare_spCommented:
HKLM\Software\Microsoft\Exchange\v14.0\<name of role>.
0
 
futureman0Author Commented:
I'm not seeing that value (see image)
0
 
futureman0Author Commented:
0
 
futureman0Author Commented:
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.
0
 
futureman0Author Commented:
found my own solution!
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 6
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now