SBS 2003 to 2011 Migration - Exchange Server 2010 cannot be installed

Hello,
We have a Small Business Server 2003 server that we are trying to migrate to SBS 2011 using the out of the box migration process. After the install, the SBS console showed a couple installation issues - the big one turned out to be "Exchange Server
2010 cannot be installed".
Here is the end of 'ExchangeSetup.log' showing various error messages:
[11/29/2014 23:00:07.0489] [2] Active Directory session settings for 'Get-ExchangeServer' are: View Entire Forest: 'True', Configuration Domain Controller: 'MB-MAINSERVER04.Contoso.local', Preferred Global Catalog: 'MB-MAINSERVER04.Contoso.local', Preferred Domain Controllers: '{ MB-MAINSERVER04.Contoso.local }'
[11/29/2014 23:00:07.0490] [2] Beginning processing get-exchangeserver -Identity:'MB-MAINSERVER04' -DomainController:'MB-MAINSERVER04.Contoso.local' -ErrorAction:'SilentlyContinue'
[11/29/2014 23:00:07.0506] [2] Searching objects "MB-MAINSERVER04" of type "Server" under the root "$null".
[11/29/2014 23:00:07.0518] [2] Previous operation run on domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0518] [2] Previous operation run on domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0518] [2] Preparing to output objects. The maximum size of the result set is "unlimited".
[11/29/2014 23:00:07.0522] [2] Unexpected Error
[11/29/2014 23:00:07.0522] [2] The operation couldn't be performed because object 'MB-MAINSERVER04' couldn't be found on 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0523] [2] Ending processing get-exchangeserver
[11/29/2014 23:00:07.0523] [1] Executing:
if ($server -eq $null)
new-exchangeserver -DomainController $RoleDomainController -Name $RoleNetBIOSName
[11/29/2014 23:00:07.0545] [2] Active Directory session settings for 'New-ExchangeServer' are: View Entire Forest: 'True', Configuration Domain Controller: 'MB-MAINSERVER04.Contoso.local', Preferred Global Catalog: 'MB-MAINSERVER04.Contoso.local', Preferred Domain Controllers: '{ MB-MAINSERVER04.Contoso.local }'
[11/29/2014 23:00:07.0545] [2] Beginning processing new-exchangeserver -DomainController:'MB-MAINSERVER04.Contoso.local' -Name:'MB-MAINSERVER04'
[11/29/2014 23:00:07.0599] [2] [ERROR] Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0600] [2] Ending processing new-exchangeserver
[11/29/2014 23:00:07.0607] [1] The following 1 error(s) occurred during task execution:
[11/29/2014 23:00:07.0607] [1] 0. ErrorRecord: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0607] [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()
[11/29/2014 23:00:07.0609] [1] [ERROR] 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)'.".
[11/29/2014 23:00:07.0609] [1] [ERROR] Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0609] [1] [ERROR-REFERENCE] Id=ProvisionServerComponent___84489810458648f5ac6e47811394a284 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[11/29/2014 23:00:07.0610] [1] Setup is stopping now because of one or more critical errors.
[11/29/2014 23:00:07.0610] [1] Finished executing component tasks.
[11/29/2014 23:00:07.0618] [1] Ending processing Install-BridgeheadRole
[11/29/2014 23:00:07.0626] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[11/29/2014 23:00:07.0633] [0] End of Setup
[11/29/2014 23:00:07.0633] [0] **********************************************
[11/29/2014 23:39:03.0429] [0] **********************************************
[11/29/2014 23:39:03.0435] [0] Starting Microsoft Exchange Server 2010 Setup
[11/29/2014 23:39:03.0435] [0] **********************************************
[11/29/2014 23:39:03.0456] [0] Local Time Zone: (UTC-08:00) Pacific Time (US & Canada).
[11/29/2014 23:39:03.0457] [0] Operating System version: Microsoft Windows NT 6.1.7600.0.
[11/29/2014 23:39:03.0469] [0] Setup version: 14.1.438.0.
[11/29/2014 23:39:03.0473] [0] Logged on user: Contoso2K3\Administrator.
[11/29/2014 23:39:06.0763] [0] Command Line Parameter Name='mode', Value='Install'.
[11/29/2014 23:39:06.0776] [0] ExSetupUI was started with the following command: '-mode:install'.
[11/29/2014 23:39:07.0413] [0] Setup is choosing the domain controller to use
[11/29/2014 23:39:07.0730] [0] Setup is choosing a local domain controller...
[11/29/2014 23:39:08.0459] [0] Setup has chosen the local domain controller MB-MAINSERVER04.Contoso.local for initial queries
[11/29/2014 23:39:08.0747] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use MB-MAINSERVER04.Contoso.local
[11/29/2014 23:39:08.0748] [0] Setup is choosing a global catalog...
[11/29/2014 23:39:08.0758] [0] Setup has chosen the global catalog server MB-MAINSERVER04.Contoso.local.
[11/29/2014 23:39:08.0819] [0] Setup will use the domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:39:08.0820] [0] Setup will use the global catalog 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:39:08.0823] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Contoso,DC=local'.
[11/29/2014 23:39:08.0830] [0] Exchange organization container for the organization is 'CN=Contoso2K3,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Contoso,DC=local'.
[11/29/2014 23:39:08.0867] [0] Setup will search for an Exchange Server object for the local machine with name 'MB-MAINSERVER04'.
[11/29/2014 23:39:08.0914] [0] No Exchange Server with identity 'MB-MAINSERVER04' was found.
[11/29/2014 23:39:09.0061] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole AdminToolsRole
[11/29/2014 23:39:09.0062] [0] The following datacenter roles are unpacked:
[11/29/2014 23:39:09.0064] [0] The following roles are installed: AdminToolsRole
[11/29/2014 23:39:09.0066] [0] The local server has some Exchange files installed.
[11/29/2014 23:39:09.0320] [0] Setup will use the path 'C:\Program Files\Windows Small Business Server\Bin\CMPNENTS\EXCHANGE14_SP1' for installing Exchange.
[11/29/2014 23:39:09.0332] [0] The installation mode is set to: 'Install'.
[11/29/2014 23:39:13.0558] [0] An Exchange organization with name 'Contoso2K3' was found in this forest.
[11/29/2014 23:39:13.0560] [0] Active Directory Initialization status : 'True'.
[11/29/2014 23:39:13.0561] [0] Schema Update Required Status : 'False'.
[11/29/2014 23:39:13.0562] [0] Organization Configuration Update Required Status : 'False'.
[11/29/2014 23:39:13.0563] [0] Domain Configuration Update Required Status : 'False'.
[11/29/2014 23:39:13.0564] [0] The locally installed version is 14.1.218.15.
[11/29/2014 23:39:13.0565] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V14'.
[11/29/2014 23:39:13.0920] [0] Applying default role selection state
[11/29/2014 23:39:13.0961] [0] Setup is determining what organization-level operations to perform.
[11/29/2014 23:39:13.0962] [0] Because the value was specified, setup is setting the argument OrganizationName to the value Contoso2K3.
[11/29/2014 23:39:13.0963] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V14\'.
[11/29/2014 23:39:13.0972] [0] InstallModeDataHandler has 0 DataHandlers
[11/29/2014 23:39:13.0972] [0] RootDataHandler has 1 DataHandlers
[11/29/2014 23:39:15.0491] [0] Setup encountered an exception when trying to access the setup state file: Could not find file 'C:\ExchangeSetupLogs\exchangeInstallState.xml'.
[11/29/2014 23:39:26.0117] [0] End of Setup
[11/29/2014 23:39:26.0117] [0] **********************************************
I should add that the source server's AD configuration might not be perfect due to this being the second attempt at a SBS 2011 migration install.
I'd be grateful for any help I can get on this as SBS migration has been plauged with multiple setbacks already. I really need to get this done! ;)
Thanks,
Voon

Thank you Larry and Al for your replies.
I used the 'official' migration
guide plus this page (http://www.techieshelp.com/step-by-step-guide-to-migrating-to-sbs-2011/)
as my migration references. The SBS migration prep tool gave no errors on the source server when I ran it.
I have a full system drive image plus a a system state backup from before migration. Though I am very loathed to rollback the migration and attempt a new one - again. I will do some searching to see if I can resolve the Exchange server problem and continue
the migration/installation. If not, then its a system state restore for me. One of Al's links had a resource for doing a thorough check of AD - which something I'd run if I have to another migration attempt.
I am also really tempted to open up a paid MS support ticket for them to help me fix this problem. :)

Similar Messages

KB953804 for delegatesentitemsstyle in Outlook 2003 in combination with Exchange Server 2010 SP1 not working.

KB953804 Full title "Hotfix for An e-mail message does not appear in a user's mailbox if the e-mail message was sent on behalf of the user by a delegate in Outlook 2003."
We have this working for ok Outlook 2003 SP3 in combination with Exchange Server 2003 SP2. Now for mailboxes that are moved to our new Exchange 2010 environment the hotfix stopped working. The sent items get stuck in the outbox of the delegate instead
of moving to the user in whose name the mail was sent. It does not matter if the user mailbox is on 2003 or 2010 as long as the delegated user is on Exchange 2010 SP1 it fails. We use Outlook 2003 SP3 in online mode. Does anyone know how to fix this
or maybe someone knows an alternative way to move the mails to the sent items with Exchange2010 SP1.

Hi,
I'd like to know how did you set "send on behalf",from outlook give delegation permission or from Exchange Server give "send as" right?
Please try to use get-adpermission to verify if the user has "send as" right.
Manage Send As Permissions for a Mailbox
http://technet.microsoft.com/en-us/library/bb676368.aspx
Note: After you grant send as right, please try to restart Microsoft Information Store.
By the way, do you receive any NDR or error information when you send on behalf of others?
Xiu

Migrate Exchange Server 2010 Public Folder shared calendars to Exchange Server 2013

Dear All,
I have an question about calendars under public folder migrating to new exchange server 2013. When completed the PF migration progress, will it also migrate calendars under sub-folder under PF to new PF mailbox?
For example: in exchange 2010 PF:
In exchange 2013
\Public Folder\sales\A1_calendar
--->
\ Public Folder\sales\A2_calendar
---> ?
\Public Folder\sales\A3_calendar
---> ?
\Public Folder\sales\A4_calendar
---> ?
Thanks in advance.
Regards,
Willis Wong

Hi Willis,
This forum is for general questions and feedback related to Outlook. Since your question is more related to Exchange server, I'd recommend you post a new question in the Exchange forum for further assistance:
https://social.technet.microsoft.com/Forums/office/en-US/home?category=exchangeserver
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Steve Fan
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Migrate from Exchange Server 2010 sp3 to 2013 sp1

I have one Exchange Server 2010 SP3 server (300 mailboxes) installed on Windows Server 2008 R2 SP1 with three major roles on it (CAS, MB and HT) - typical installation. Edge Transport server is not installed thus for controlling of mail flow
Symantec Messaging Gateway Virtual Appliance is used as Smart Host. UM server is not installed either. I set up test domain environment where I installed one domain controller (Windows Server 2008 R2 SP1) and one Exchange Server 2010 SP3 (Windows
Server 2008 R2 SP1) at first place and yesterday I did everything necessary to install Exchange Server 2013 SP1 on new test virtual server running Windows Server 2012 R2 which I successfully did.
Now in test domain I have two Exchange Servers (2010 SP3 and 2013 SP1). Is there any 100% reliable documentation with all actions that had to be taken in order to successfully migrate Exchange Server 2010 SP3 to 2013 SP1? I would want to know what
needs to be done not only for my scenario but also for other scenarios (DAG, CAS array, Edge, UM, multiple HT servers . . .) since I am interested in digging deep into Exchange Server 2013.

Hi BoxiKG,
In addition to the above mentioned, and this for your reference:
Upgrade from Exchange 2010 to Exchange 2013
http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
Best regards,
Eric

Migration from Exchange server 2010 to Exchange server 2013

Hi All,
We have migrate Exchange Server 2010 to Exchange Server 2013. When I turned off my Exchange Server 2010, Outlook is not able to connect through Exchange 2013. It's prompting for user name and password again and again and nothing would happen
after provide user name and password. So, we are not able to uninstall exchange 2010 from old server.

Run these commands and post the update.
Get-WebservicesVirtualDirectory -Server E2K13SERVER |Fl internalURL,ExternalURL
Get-OWAVirtualDirectory -Server E2K13SERVER | Fl internalUrl,ExternalURL
Get-ClientAccessServer E2K13SERVER | Fl AutodiscoverServiceInternalUri
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange Server 2010 - Receive Connector for Client Computers

I have one customer with a SBS 2011 with Exchange Server 2010 - a pretty standard setup except for some customisation with Receive Connectors in order to cater for an application which is installed on a number of computers that requires to use an SMTP Server
to send notifications. In order to accomplish this (allow to be sent using Exchange Server) we added the IP Address of client computer (which we also set as a DHCP reservation) to a pre-configured Receive Connector (Anonymous setup for Printer/Scanner).
This worked fine, but we now find that there are other applications that require the same function to use SMTP to send.
How should/could this be better configured so an application can send if they authenticate?

Hi
For this you need to create a seperate receive connector to be used for Relay in your organizations.
Follow the below steps
1) Create a dedicated Relay Receive Connector
2) Add only the Ip addresses of the applications which needs to relay on Exchange servers
3) You can use either anonymous or authenticated relay according to your relay config
You can follow the below link as well
http://exchangequery.com/2013/12/02/steps-to-configure-anonymous-and-authenticated-relay-in-exchange-2013/
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

When sending e-mail messages to a mail-enabled public folder that have been replicated from old Exchange Server 2000/2003/2007, Exchange Server 2010 environment mails are rejected with NDR.

Hi, I would like to share with you issue that I’ve solved regarding mail-enabled PF that migrated from Exchange 2000/2003/2007 to 2010, I’ve searched & contacted my MVP leader – there’s no official KB regarding this issue right
now, so I’m posting here in order to share this among others.
Note: There’s article(s) that talked about PF replication from Exch2000/2003/2007 to 2010 – this is the same issue as well.
Symptoms
E-mail messages that been sent to mail-enabled public folder in Exchange Server 2010 environment rejected with the following NDR:
“#< #5.2.0 smtp;554 5.2.0 STOREDRV.Deliver.Exception:ObjectNotFoundException; Failed to process message due to a permanent exception with message The Active Directory user wasn’t found. ObjectNotFoundException: The Active Directory
user wasn’t found.> #SMTP#”
Sometimes Exchange Server 2010 is documented as well Event ID 1020 on the Event Viewer with this information:
“Log Name: Application
Source: MSExchange Store Driver
Event ID: 1020
Level: Error
Description:
The store driver couldn’t deliver the public folder replication message "Hierarchy ([email protected])" because the following error occurred: The Active Directory user wasn't found.”
Cause
In an environment where Microsoft Exchange Server 2000 or Microsoft Exchange Server 2003 previously existed, and all those servers have been removed, there is a chance that an Administrative Group (First Administrative Group or another custom Administrative
Group) remains with a Servers container, but no servers inside it.
During replication, when the Exchange 2010 Store Driver sees the empty Servers container in Active Directory, it's expecting a System Attendant object inside the container and when it is not found the error occurs.
Resolution
To work around the issue, delete the empty Servers container. This can't be done through Exchange System Manager. Use the ADSI Edit tool to remove it using the following steps:
Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows
2003 Server, Microsoft Windows Server 2008, Microsoft Exchange 2010 Server or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes
at your own risk.
1.
Start the ADSI Edit MMC Snap-in. Click Start, then
Run, and type adsiedit.msc, and then click OK.
2.
Connect & Expand the Configuration Container [YourServer.DNSDomainName.com], and then expand
CN=Configuration,DC=DNSDomainName,DC=com.
3.
Expand CN=Services, and then CN=Microsoft Exchange, and then expand
CN=YourOrganizationName.
4.
You will see an empty Administrative Group. Expand the
CN=YourAdministrativeGroupName.
5.
Expand CN=Servers.
6.
Verify there are no server objects listed under the
CN=Servers container.
7.
Right click on the empty CN=Servers container and choose
Delete.
8.
Verify the modification, and try to send again the E-mail to the mail-enabled public folder.
Applies to
Exchange Server 2010, Standard Edition
Exchange Server 2010, Enterprise Edition
Netanel Ben-Shushan, MCSA/E, MCTS, MCITP, Windows Expert-IT Pro MVP. IT Consultant & Trainer | Website (Hebrew): http://www.ben-shushan.net | IT Services: http://www.ben-shushan.net/services | Weblog (Hebrew): http://blogs.microsoft.co.il/blogs/netanelb
| E-mail: [email protected]

Sounds like you are looking in the wrong Administrative Group container which is why you are seeing your Exchange 2010 servers in there.
When you install Exchange 2003 only you will see a container named by default as "CN=First Administrative Group" container. But this could be named anything if you changed the Organization Name on the installation when you installed the first
Exchange 2003 server into the domain/forest.
You will notice that when you install Exchange 2010 part of the AD setup is to create a new configuration container and is named by default "CN=First Administrative Group (FYDIBOHF23SPDLT)".
So it sounds like you are not looking in the right location within ADSIEdit.
You may find the following article also helpful for this issue which is the same resolution:
http://blogs.technet.com/b/sbs/archive/2012/05/17/empty-cn-servers-container-causing-issues-with-public-folders-on-small-business-server-2011.aspx
I recommend though that you ensure your Exchange 2003 servers are fully uninstalled or no longer present in your environment before you go deleting the Servers container though.. The following Microsoft article will help with this:
http://technet.microsoft.com/en-gb/library/gg576862(v=exchg.141).aspx

Cannot install exchange server 2010 without small business server 2011

we purchased Windows Small Business server 2011 for one of our servers and installed the software and setup exchange server for the office. We had some 3rd party software that would not work with small business server so we had to install windows
2008 r2 server. we still need exchange server 2010. Is there anyway to install without small business server? When I entered the key in exchange server for the small business server it is saying that it is an invalid key. We have a
genuine version of windows small business server. is it all or nothing for the software. Thanks

SBS is indeed all or nothing. Breaking apart the individual components is not allowed. That includes exchange. If you want exchange without SBS, you'll need to buy exchange separately and exchange CALs. If you only have SBS CALs and aren't going to run
SBS, you'll need Windows CALs as well.

Migrate Ubuntu Zentyal to Exchange Server 2010

Hi guys!! Good evening!!
I'm having the next scenario.
My client has an Ubuntu Server, managed by Zentyal, Is it possible to migrate to Exchange Server 2010 from that enviroment?
Thanks for your answers.

Hi,
I suggest we contact the Zentyal support to confirm whether the migration is possible.
Thanks,
Simon Wu
TechNet Community Support

Exchange Server 2010 after Office365 Cutover Migration

We transitioned to Office 365 4 months ago. Per this reference, we have left an Exchange Server 2010 on premise per this guidance.
http://blogs.technet.com/b/exchange/archive/2012/12/05/decommissioning-your-exchange-2010-servers-in-a-hybrid-deployment.aspx
I want to move Exchange 2010 to an older less capable server to repurpose the current server. I have installed it with client access and mailbox server roles.
When I try to uninstall the old Exchange 2010 installation, I can't do it citing the existence of mailboxes. When I attempt to remove an mailbox, the entire user is deleted from our Active Directory? Premise mailboxes are now irrelevant consider
they exist on Office365.
How do I decommission this old Exchange 2010 server without deleting all our users?

Hi,
The proper way to remove a hybrid deployment is to disable it manually. The following actions should be performed to remove the objects created and configured by the Hybrid Configuration
Wizard:
1. Re-point your organization’s MX record to the Office 365 service if it is pointing to the on-premises organization. If you are removing Exchange and don’t point the MX record
to Office 365, inbound Internet mail flow won’t function.
2. Using the Shell in the on-premises organization, run the following commands:
Remove-OrganizationRelationship –Identity “On Premises to Exchange Online Organization Relationship”
Remove-FederationTrust –Identity “Microsoft Federation Gateway”
Remove-SendConnector
“Outbound to Office 365″
3. Using EMC, you can also remove the <your organization domain>.mail.onmicrosoft.com domain that was added as part of the email address policy for your organization.
4. OPTIONAL – Remove the remote domains created by the Hybrid Configuration wizard in the Exchange Online organization. From the EMC, select the Hub Transport in the Exchange Online
forest node and remove all remote domains starting with “Hybrid Domain”
5. Remove the organization relationship from the Exchange Online organization with the following command. You must use Remote PowerShell to connect to Exchange Online connected to
Exchange Online.
Remove-OrganizationRelationship –Identity “Exchange Online to On Premises Organization Relationship”
6. OPTIONAL – Disable the Inbound and Outbound Forefront Online Protection for Exchange (FOPE) connectors created by the Hybrid Configuration Wizard.
Referred from:
http://www.paradyne.com.au/office-365-decommissioning-on-premises-exchange/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety,
or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Problems installing Mailbox role on Exchange Server 2010 SP3

I am in the process of installing Exchange Server 2010 SP3 on a Windows Server 2012 server in order to migrate our existing Exchange 2003 server. Everything went well with the installation process until I went to add the Mailbox server role, which is giving
me the following error (from the log file):
[05/03/2013 21:58:09.0090] [1] Executing:
$wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
$manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
[05/03/2013 21:58:09.0105] [2] Active Directory session settings for 'Start-SetupProcess' are: View Entire Forest: 'True', Configuration Domain Controller: 'TAM-FS2.tacomaartmuseum.org', Preferred Global Catalog: 'TAM-FS2.tacomaartmuseum.org', Preferred Domain
Controllers: '{ TAM-FS2.tacomaartmuseum.org }'
[05/03/2013 21:58:09.0105] [2] Beginning processing Start-SetupProcess -Name:'C:\Windows\system32\wevtutil.exe' -Args:'im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man" '
[05/03/2013 21:58:09.0276] [2] Starting: C:\Windows\system32\wevtutil.exe with arguments: im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man"
[05/03/2013 21:58:09.0344] [2] Process standard output:
[05/03/2013 21:58:09.0344] [2] Process standard error: The value for channel property Type contains an invalid value. The parameter is incorrect.
[05/03/2013 21:58:09.0347] [2] [ERROR] Unexpected Error
[05/03/2013 21:58:09.0347] [2] [ERROR] Process execution failed with exit code 87.
[05/03/2013 21:58:09.0350] [2] Ending processing Start-SetupProcess
[05/03/2013 21:58:09.0350] [1] The following 1 error(s) occurred during task execution:
[05/03/2013 21:58:09.0350] [1] 0. ErrorRecord: Process execution failed with exit code 87.
[05/03/2013 21:58:09.0350] [1] 0. ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code 87.
[05/03/2013 21:58:09.0351] [1] [ERROR] The following error was generated when "$error.Clear();
$wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
$manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
" was run: "Process execution failed with exit code 87.".
[05/03/2013 21:58:09.0351] [1] [ERROR] Process execution failed with exit code 87.
[05/03/2013 21:58:09.0351] [1] [ERROR-REFERENCE] Id=MailboxComponent___13A8A6B7DE0A4fe3BEB5CB1D86105DA3 Component=EXCHANGE14:\Current\Release\PIM Storage\Content Indexing
[05/03/2013 21:58:09.0351] [1] Setup is stopping now because of one or more critical errors.
[05/03/2013 21:58:09.0351] [1] Finished executing component tasks.
[05/03/2013 21:58:09.0393] [1] Ending processing Install-MailboxRole
I've searched all over but can't seem to find any reference to "exit code 87" - does anyone have any ideas?
Thanks,
Matt

Error 87 -with these details below - and a fix. The situation that got me here by the way was an incomplete install that was uninstalled, then installed again.
[02/24/2014 06:49:06.0967] [2] Active Directory session settings for 'Start-SetupProcess' are: View Entire Forest: 'True', Configuration Domain Controller: 'xxxxxxxxxxxxxxx', Preferred Global Catalog: 'xxxxxxxxxxxxxxxxxxxxxxxx', Preferred Domain Controllers:
'{ xxxxxxxxxxxxxxxxxxxxxxx }'
[02/24/2014 06:49:06.0967] [2] Beginning processing Start-SetupProcess -Name:'C:\Windows\system32\wevtutil.exe' -Args:'im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man" '
[02/24/2014 06:49:06.0967] [2] Starting: C:\Windows\system32\wevtutil.exe with arguments: im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man"
[02/24/2014 06:49:07.0592] [2] Process standard output:
[02/24/2014 06:49:07.0592] [2] Process standard error: The value for channel property Type contains an invalid value. The parameter is incorrect.
[02/24/2014 06:49:07.0592] [2] [ERROR] Unexpected Error
[02/24/2014 06:49:07.0592] [2] [ERROR] Process execution failed with exit code 87.
[02/24/2014 06:49:07.0592] [2] Ending processing Start-SetupProcess
[02/24/2014 06:49:07.0592] [1] The following 1 error(s) occurred during task execution:
[02/24/2014 06:49:07.0592] [1] 0. ErrorRecord: Process execution failed with exit code 87.
[02/24/2014 06:49:07.0592] [1] 0. ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code 87.
[02/24/2014 06:49:07.0608] [1] [ERROR] The following error was generated when "$error.Clear();
          $wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
          $manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
          Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
        " was run: "Process execution failed with exit code 87.".
[02/24/2014 06:49:07.0608] [1] [ERROR] Process execution failed with exit code 87.
I found I could fix this by removing the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\eventlog\Microsoft-Exchange-Troubleshooters/Operational
and everything underneath it.
My guess is that wevtutil didn't like adding an event log where it already existed but was slightly different in setup (no idea how, exactly).
After 24 hours I'll try post again - giving things time to make sure they are actually working.

Exchange Server 2010 SP3 Databases are not mounting after the recovery process

Hi,
We are using Exchange server 2010 SP3 in our office. Databases are stored in an ISCSI drive mapped with the exchange. We are taking daily full backup of my Exchange server using Symantec Backup exe 2012. As a testing purpose I created a test environment
same like my existing live environment to check the disaster recovery and backup. Thankfully disaster recovery worked well and I am able to open the exchange management console and powershell. But I am not able to mount the recovered databases ending
with an error saying "Couldn't mount the database that you specified. Specified database: officialrecover; Error code:
An Active Manager operation failed.........." and even I am not able to use the utility eseutil.exe to the database with an error "access to source database failed with jet error 1811". I am able to create a new database and mount
it.
I am using Windows Server Ent 2008 R2 64 Bit with Exchange Server 2010 SP3 in the Live environment with 3 partitions called C (279 GB), E (4.46 TB, ISCSI), F (976 GB) in my Live environment.
For test it is Windows Server Ent 2008 R2 64 Bit with Exchange Server 2010 SP3 with 3 partitions C (240 GB), E (1.4 TB), & F (240 GB).
Please help me with your valid comments to solve and mount the database and close the issue for ever.
With Regards
Jay

Jared is correct that in essence the message is saying the DB cannot be found.
When you restored to your recovery server are all the paths the same, i.e. if the DB existed on E:\XYZ on the production server it must be the same on the recovery server
When you restored into the recovery site do you have AD restored into that site as well?
For the recovery server are you using iSCSI storage for it as well? If so am I correct to assume that you have copies of the databases just for use on this server and are not trying to reference the same instance of the DB from the production
and test/recovery server?
I have also seen an issue where DB's getting written to disk from Symantec mess up the header of the DB. If you want to validate that the DB is actually intact and accessible you might want to check out our DigiScope product
http://www.lucid8.com/product/digiscope.asp using a free DEMO license. If it works i.e. you are able to mount in DigiScope from same location where its failing on the recovery server we know the
DB your pointing at is good and accessible from the current path but something else is amiss in your configuration
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Exchange Server 2010: Convert Mailbox to MailUser

Dear All,
I plan to cutover migration exchange on-premises to exchange online with single-sign-on.
http://community.office365.com/en-us/w/exchange/835.cutover-exchange-migration-and-single-sign-on.aspx
In Step 2: It need to Convert on-premises mailboxes to mail-enabled users. it has only instruction guide for exchange server 2003 and 2007. it didn't have for exchange server 2010 or 2013.
Could you guide what is the best solution to convert mailbox in exchange server 2010?
BR,
Khemarin
[email protected]

Hi Khemarin,
You can use the following cmdlet to convert a mailbox to a MailUser:
$DomainController = (Get-ADServerSettings).DefaultConfigurationDomainController.domain
$MailboxList= Get-Mailbox
foreach ($Mailbox in $MailboxList) {
    Disable-Mailbox -Id $mailbox.Identity -Confirm:$False -DomainController $DomainController
    Enable-MailUser -Id $mailbox.Identity -ExternalEmailAddress ($mailbox.alias +"@domain.com") -DomainController $DomainController
    Set-MailUser -Id $mailbox.Identity `
     -DomainController $DomainController `
     -CustomAttribute1 $Mailbox.CustomAttribute1
For more information, here is an article for your reference.
Converting a Mailbox to a MailUser
http://mikecrowley.wordpress.com/2010/12/09/converting-a-mailbox-to-a-mailuser-and-not-loosing-attributes/
Note: Microsoft is providing this information as a convenience to you. The site is not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any information found there. Please make sure that
you completely understand the risk before retrieving any suggestions from the above link.
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Recover mailbox from Exchange server 2010 information store to exchange server 2013

I have a big issue. I have a correct exchange server 2010 where the active directory is corrupt but the information store is good.
I would like to recover a couple of mailboxes to an exchange server 2013.
Can anyone give me a detailed walk through of how I can accomplish this?
Thank in advance

Well if your AD is messed up that leaves you in a jam for sure because;
1. Database portability ONLY works within the same organization, so you cannot just install a new 2010 server in a completely different forest and then move the DB in hopes that DB portability will work.
2. As Ed said you should build a new Exchange 2010 server and use portability but it has to be in the same organization.
3. Here is a good article on how to accomplish
http://exchangeserverpro.com/exchange-2010-database-portability-disaster-recovery/
4. Now if you by chance have an AD backup before it went south you could build a separate network with same names etc just keep it isolated from the production server and then restore AD to that environment and you could then use DB portability.
That said if you don't have any other machines to work with then you are in a bit of a pickle and will have to use a 3rd party product to get to that data within the 2010 DB. We make a product that can do this (DigiScope), however if you don't
have any budget to handle its a non-issue.
The only other thing you could consider is to restore your AD from a previous point in time, however BE VERY CAREFUL if you consider this since it could cause more issues then you have now.
BTW if you AD is messed up, where are you putting this new 2013 server?
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Processor requirments for Exchange Server 2010 roles

I am looking at migrating from Exchange Server 2003 to Exchange Server 2010. My exchange environment has 350 mailboxes. Can anyone tell me how much processing power will be required for each exchange role to run on VMware? I know Microsoft's recommendation is 1GB per core.

Hi Amyraghunath,
It's hard to give general guidance on sizing Exchange 2010 since it is heavily dependent on your specific configuration. The key number to use for sizing the Mailbox server role is to know the number of messages sent/received per day. That number will help you size CPU and memory for your Mailbox server which will ultimately drive the sizing for the other roles.
A good place to start is the following article: http://technet.microsoft.com/en-us/library/ee712771(v=exchg.141).aspx
That article describes the impact of messages sent/received per day has on sizing the Mailbox server and shows the math that is involved as well. Once you know how to size the Mailbox server, you can size the other roles as well.
You can also use the Exchange Mailbox sizing calculator here ( Exchange 2010 Server Role Requirements Calculator - Exchange Team Blog - Site Home - TechNet Blogs), though be careful with this because if you aren't sure what you're entering in here you could end up with incorrect results.
Finally, here are some other great links that should be helpful to you in sizing your Exchange 2010 environment on vSphere:
http://technet.microsoft.com/en-us/library/dd346700.aspx
http://technet.microsoft.com/en-us/library/dd346699.aspx
VMware: Run Microsoft Exchange Server Software on a Virtualization Platform - United States
Hope these links help! If not feel free to post back here.
Matt
http://www.thelowercasew.com

SBS 2003 to 2011 Migration - Exchange Server 2010 cannot be installed

Similar Messages

Maybe you are looking for