CyberTrails Technical Blog
By Peter Bliss, System Administrator at CyberTrails
Peter Bliss has been with CyberTrails since 2010 and is one of our System Administrators. Peter brings over 10 years of experience with Enterprise Networks, Cluster SQL servers, VMWare, Microsoft Exchange, and much more. Peter started with us in our NOC and was immediately promoted to our Admin team where he has been a key player and works on advance Microsoft configurations and implementations from full system migrations to complex break fix issues.
“Exchange 2010 could not find default Administrative Group”
A co-worker asked me to install Exchange 2010 in one of our client environments today. He stated that their old managed services team attempted to migrate this client to Exchange 2010, but failed. They had already installed Exchange 2010 but it was not working properly. He had used ADSIedit to remove all existence of any Exchange 2010.
Trusting this, I dove head first into the project of installing Exchange 2010 into their environment. I deployed two new VM servers that will host the CAS and HUB role. I installed all the prerequisites for Exchange 2010. Everything cleared the system check and I had all green check marks. I assumed all would be a snap to install. I was sadly mistaken! =(
I received this error below:
The following error was generated when “$error.Clear();
If ($server –eq $null)
New-exchangeserver –DomainController $RoleDomainController –
“was run: “Could not find the default Administrative Group ‘Exchange Administrative Group (FYDIBOHF23SPDLT)’.”.
Could not find the default Administrative Group ‘Exchange Administrative
So I “clicked here for help” and I got a page from Microsoft that stated “Help Resources for Errors!” but there was no help here. The site stated “don’t fret you can post on our forums and someone can help you.” Now what kind of answer is this from Microsoft REALLY! Someone has to have an answer to my problem. So I hit my best friend in the world, Google, because, well, that’s where all the answers are found. (I have tried Bing! and I find I get better results from Google).
Low and behold, there is some prep work that needs to be done! So what is happening is that the old Exchange environment is still showing up in the schema and forest setting. What needs to happen is a prep step to clear out and reset those settings. Since this installation is attempting to connect to ‘Exchange Administrative Group (FYDIBOHF23SPDLT)’. Which does not exist as it was removed with ADSIEdit.
So you need to run the following commands to prepare your domain for a new Administrative Group (FYDIBOHF23SPDLT).
From the root of the exchange installation CD run
‘SETUP.COM /ps’ – Prepares the Active Directory Schema for the Exchange Installation
‘SETUP.COM /p’ – Prepares the Active Directory forest for the Exchange installation
‘SETUP.COM /pd’ – Prepares the local domain for the exchange installation
Once these commands have been run at a command prompt you can continue on with your Exchange 2010 installation. Everything should function and install correctly without any errors.