Exchange 2013 SP1 mailbox role on 2012 R2 and 2012

Hi,
We have a client who were running the following setup:
2 x Exchange 2013 CU2 CAS servers / Win Srv 2012
2 x Exchange 2013 CU2 MBX servers / Win Srv 2012
Active Directory etc, basically everything else, runs on Win Server 2012.
Due to upgrading etc, one of the mailbox servers has been removed. It is to be installed with Ex2013 SP1 with 2012 R2 from scratch, and eventually also upgrade the remaining CAS and MBX srvers with SP1 and 2012 R2.
So my question is..will this present a problem? Is it possible to have one MBX running 2013 CU2 on Server 2012 and one MBX running 2013 SP1 on Server 2012 R2?
I've read that failover clustering service is not possible between 2012 and 2012 R2, but i'm not sure how this effects Exchange.
Thanks for your time.

Hi,
Each member of the DAG should be running the same operating system. It is not supported to run a DAG member on Windows Server 2012 R2 and run another member on Windows Server 2012.
What's more, upgrading the OS is not supported on Exchange server.
Here are some helpful threads for your reference.
Planning for High Availability and Site Resilience
http://technet.microsoft.com/en-us/library/dd638104(v=exchg.150).aspx
Exchange 2013 CU2 and Upgrading from Server 2012 to Server 2012 R2 issues
http://social.technet.microsoft.com/Forums/exchange/en-US/afba40de-efb6-4916-ae42-b09cff35e5d7/exchange-2013-cu2-and-upgrading-from-server-2012-to-server-2012-r2-issues
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Similar Messages

Exchange 2013 SP1 EDGE role content filtering ?

Hello,
Have Exchange 2013 SP1 with CU5 with antispam enabled on mailbox role server. And i wonder if i deploy 2013 Edge role, will i get more granular content filter control, like there is in Office 365? For example: i want to treat empty messages as not
spam.
I have read that control of Edge server is done ONLY by powershell. So if edge role is deployed, still there is no content filter control in ECP (like in office365) ??

Hi,
The Content Filter agent assigns a spam confidence level (SCL) rating to each message. The SCL rating is a number between 0 and 9. A higher SCL rating indicates that a message is more likely to be spam.
Based on my knowledge, I'm afraid we can't filter the empty messages and treat them as not spam.
Here is an article about content filtering in Exchange 2013 for your reference.
Content Filtering
http://technet.microsoft.com/en-us/library/bb124739(v=exchg.150).aspx
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Issue Installing Exchange 2013 CU1: Mailbox role:Mailbox service

I receive this error when Installing Cumulative Update 1.
Error:
The following error was generated when "$error.Clear();
            if ($RoleIsDatacenter -ne $true)
            if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
            $sysMbx = $null;
            $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
            $dispName = "Microsoft Exchange";
            Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
            $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
            if ($mbxs.Length -eq 0)
            Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
            $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
            if ($dbs.Length -ne 0)
            Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
            $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
            if ($arbUsers.Length -ne 0)
            Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
            $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
            else
            if ($mbxs[0].DisplayName -ne $dispName )
            Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
            Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
            $sysMbx = $mbxs[0];
            # Set the Organization Capabilities needed for this mailbox
            if ($sysMbx -ne $null)
            # We need 1 GB for uploading large OAB files to the organization mailbox
            Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
                set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MessageTracking:$true -MaxSendSize
1GB -Force;
            else
            Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
            else
            Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
        " was run: "Database is mandatory on UserMailbox.".
Error:
The following error was generated when "$error.Clear();
            if ($RoleIsDatacenter -ne $true)
            if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
            $sysMbx = $null;
            $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
            $dispName = "Microsoft Exchange";
            Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
            $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
            if ($mbxs.Length -eq 0)
            Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
            $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
            if ($dbs.Length -ne 0)
            Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
            $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
            if ($arbUsers.Length -ne 0)
            Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
            $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
            else
            if ($mbxs[0].DisplayName -ne $dispName )
            Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
            Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
            $sysMbx = $mbxs[0];
            # Set the Organization Capabilities needed for this mailbox
            if ($sysMbx -ne $null)
            # We need 1 GB for uploading large OAB files to the organization mailbox
            Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
                set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MessageTracking:$true -MaxSendSize
1GB -Force;
            else
            Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
            else
            Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
        " was run: "Database is mandatory on UserMailbox. Property Name: Database".
Can Anyone help me figure out how I can resolve this error?

Hello,
Please make sure you have these permission " Schema Admins", "Domain Admins" and "Enterprise Admins".
Here is the article for your reference.
Prepare Active Directory and Domains
http://technet.microsoft.com/en-us/library/bb125224(v=exchg.150).aspx
Cara Chen
TechNet Community Support

Error in moving exchange 2010 mailboxes to Exchange 2013 SP1 during migration

Dear All,
We were running Exchange 2010 SP3 with MBX/HT/CAS role in single server. Now we are migrating our exchange 2010 to Exchange 2013 SP1. After configuring co-existence and during the mailbox move from Exchange 2010 to Exchange 2013 SP1, we are facing below
error. Please help to troubleshot. As per our search on net, people were suggesting that it can be due to not able to resolve NetBIOS name. We checked same and we are able to ping both servers by NetBIOS and FQDN names.
[PS] C:\Windows\system32>New-MoveRequest -Identity
'[email protected]' -TargetDatabase "CI-DB01"
MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)
Diagnostic context:
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1722
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 323
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
    Lid: 62184
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1237
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 313
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
    Lid: 62184
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 10060
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 311
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 3
    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[0]: Long val: 22964
    Lid: 15000   dwParam: 0x0 Msg: EEInfo: prm[1]: Pointer val: 0x0
    Lid: 15000   dwParam: 0x0 Msg: EEInfo: prm[2]: Pointer val: 0xFE01A8C000000000
    Lid: 62184
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 10060
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 318
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
    Lid: 53361   StoreEc: 0x977
    Lid: 51859
    Lid: 33649   StoreEc: 0x977
    Lid: 43315
    Lid: 58225   StoreEc: 0x977
    Lid: 39912   StoreEc: 0x977
    Lid: 54129   StoreEc: 0x977
    Lid: 50519
    Lid: 59735   StoreEc: 0x977
    Lid: 59199
    Lid: 27356   StoreEc: 0x977
    Lid: 65279
    Lid: 52465   StoreEc: 0x977
    Lid: 60065
    Lid: 33777   StoreEc: 0x977
    Lid: 59805
    Lid: 52487   StoreEc: 0x977
    Lid: 19778
    Lid: 27970   StoreEc: 0x977
    Lid: 17730
    Lid: 25922   StoreEc: 0x977
    + CategoryInfo          : NotSpecified: (:) [New-MoveRequest], RemoteTransientException
    + FullyQualifiedErrorId : [Server=Exch01,RequestId=f6886977-92f1-4148-991b-aa76b449aff5,TimeStamp=8/21/2014 9:1
   0:43 AM] [FailureCategory=Cmdlet-RemoteTransientException] 7FCC37,Microsoft.Exchange.Management.RecipientTasks.New
MoveRequest
+ PSComputerName        : Exch01.domain.local
Please help as we are stuck here!!
Thanks in advance!!

Can yo ping server by name not by FQDN? e.g. ping server1.
Make sure firewall/antivirus not blocking communication. Disable antivirus and try
Thanks,
MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Exchange 2013-SP1/Outlook 2013 connectivity issue.

We couldn't make Outlook 2013 (latest updates) to connect to our Exchange 2013-SP1 through the Internet.
Any PC inside the LAN (on the domain or outside the domain) can connect normally.
Any PC outside the LAN (WAN) cannot connect, it keep showing this error:
"The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
OWA is working fine from the WAN, smartphones (Android & Apple) are also working fine from the WAN.
Port 443 is open on the firewall.
So what we are missing!

Hi,
Firstly, I'd like to say, in Exchange 2013 SP1, Outlook 2013 SP1 clients may use MAPI over HTTP to connect to the server.
Before going further, let's confirm if they use MAPI over HTTP: Get-OrganizationConfig | FL MapiHttpEnabled
If the value of the above property is true, I recommend the following troubleshooting:
1. Check if your Exchange 2013 SP1 server is running on Windows Server 2012 R2.
2. Check MAPI virtual directory settings: get-MapiVirtualDirectory |fl
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Exchange 2013 SP1 and SCOM 2012 R2

Hi there,
Hopefully someone can assist me with this issue, if it is one...
I am halfway through an Exchange migration, from Exchange 2010 SP3 on Server 2008 R2 to Exchange 2013 SP1 on Server 2012 R2.
76 users in total, roughly 80GB of Public Folders.
I have configured the 2013 environment with a cross datacenter DAG, also increased all of the timeouts of the cluster to take this into consideration, and everything appears to function as expected.
Added both 2013 machines to SCOM 2012 R2 for at least a week with no active users on it, and all monitoring reported ok, no issues.
Exchange 2010 is configured to use webmail.company.com for RPC over HTTP, which is what I have configured 2013 to use as well.
Implemented Microsoft ARR for client access to Exchange 2013, as opposed to ISA we've used for Exchange 2010.
A week ago, changed the DNS records for webmail.company.com from ISA to ARR, and all clients connected perfect.
Thought, ok, now we can start the migration. So far everything "seems" to be going perfect with the mailbox moves, however, SCOM is really noisy.
Attempted to reran the probe for EWS and got the error below:
Is there perhaps anyone that can assist me with these errors?
Cheers

FYI... IIS ARR is not supported for Exchange Server.
Check in event log if you are getting anything related to the issue.
About Outlook POP UP to end users. Check the event log on 2010/2013 for MRS events.
Are those mailboxes still moving or in move request?
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.

Migrate to Windows 2012 R2 and Exchange 2013 SP1 using database portability

Hi, I'm planning to migrate from Exchange 2013 SP1 running on Windows 2012 to Exchange 2013 SP1 on Windows 2012 R2.
Is it possible to use database portability to move the databases from the exchange installation on win 2012 to the new installation on Win 2012 R2? This would save a great deal of time not doing the mailbox moves.
I've searched similar cases but couldn't find any, all speak about disaster recovery and database portability but I've found no articles that uses the migration scenario.
Would it be possible to do and if so, what would the steps be? Do I need to delete the database from the source server, move the database files to the new server and mount them and relocate the mailboxes? Or should I dismount the database on the source server,
move them to the new server and mount them and relocate the mailboxes?
Frank.

Hi,
According to your description, I recommend you consider using DAG to achieve your requirement.
The following steps for your reference:
1.Prepare a new server which installed windows 2012 R2 for Exchange 2013 mailbox server.
2.After you deploy Exchange 2013 Mailbox servers, you can create a DAG, add Mailbox servers to the DAG, and then replicate mailbox databases between the DAG members.
3.After replication, you can mount all the databases on the new server.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support
This no way a resolution. This won't work at all as Both OS will be different and you can't form the Cluster.
Please Unmark it!
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 2013 SP1 - Edge Tranport Role

Hi.
When Exchange 2013 was released only CAS & Mailbox roles where available. Hub & Edge Transport server roles were discontinued.
Now with Exchange 2013 SP1, the edge transport role has came back.
Question:
1. Can I deploy a new Exchange 2013 Infrastructure without the Edge Transport Role. This will be a fresh deployment.
I plan to have a UTM with spam blocking at the perimeter instead of the Edge Server?
2. will there any be problems without an Edge Transport ?
Thanks,
Paul

Hi ,
Please find the below mentioned points .
1. Can I deploy a new Exchange 2013 Infrastructure without the Edge Transport Role. This will be a fresh deployment.
I plan to have a UTM with spam blocking at the perimeter instead of the Edge Server?
Answer :
Just ensure that the product is having all the features as you need on your side .There is not necessary to have a an edge server in all the exchange environment's. Moreover Gateway and anti spam products will differ as per the company requirements.
2. will there any be problems without an Edge Transport ?
Answer :
If you are having any one the anti spamming solution to have all the emails scanned before it reaches the exchange server then it will be good .
Just ensure that the anti spamming product what you are going to use is mainly doing the reverse dns lookup
and spf look up .With the help of that we can able to avoid large no of forged emails.
Regards
S.Nithyanandham

Upgrade of Integation Services (Windows 2012 R2) on Windows 2008 R2 with Exchange 2013 SP1 DAG fails

Here is the scenario:
Legacy Host: Windows 2008 R2
Guest VM: Windows 2008 R2 with Exchange 2013 SP1 DAG cluster.
After importing the VM (2008 R2 and Exchange 2013 DAG) into a 2012 R2 host (Cluster). (copy VM files to new 2012 R2host) Everything works fine.
Then upgrading "Installation Services" (for Windows 2012 R2 host) on the imported VM runs fine with no errors to the "Restart" prompt. VM than shows: "Configuring Windows updates 32% complete. Do not turn
of your computer." Hangs there for about 20 minutes until is says "shutting down". Hangs there for 20 minutes until power off. Restart to normal start; "Preparing to configure Windows. Do not turnoff your computer." proceeds slowly
to "Configuring Windows updates 32% complete. Do not turn of your computer." hangs there again indefinite. Sometime hangs at shutdown cycle and "Configuring Windows updates 32% complete. Do not turn of your computer." indefinitely.
I moved 20 other machines from a 2008 R2 host to new Windows 2012 R2 hosts all of these machines install the 2012 R2 Integration services just fine on the 2008 R2 VM. Just the 2008 R2 VMs clustered (DAG) and Exchange 2013 SP1 do not take the Integration
Services upgrade.
Any advise from Microsoft? I know I could decommission the DAG and Exchange machines and install Integration services on the native box before Exchange and DAG and that would sure work, but I'd rather avoid that amount of work for a simple integration layer
upgrade.
Thanks
Gerhard Waterkamp ACSLA Inc.

Hi,
Could you try use the following method to fix this issue first?
1. Run the System Update Readiness Tool, then check if there is any error in the Checksur.log and checksur.persist.log.
1. Please run the System Update Readiness Tool on this affected server. Please download this tool from the following Microsoft article:
Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, and for Windows 7
http://support.microsoft.com/kb/947821/en-us
2. The System Update Readiness Tool creates the log files that captures any issues that the tool found or fixed. The log files are located at the following location:
%SYSTEMROOT%\Logs\CBS\
3. Please paste the checksur.log here for analysis.
If there is no error found, please try the following step.
==================================
2. Use Fix it tool to reset the Windows Update components.
1. Open the following link.
http://support.microsoft.com/kb/971058/en-nz
2. Select Windows 8.1, Windows 8 and Windows 7 in the product selection box.
3. Click “Run Now” to reset the Windows Update components.
Note: We can reset the Windows Updates manually by following the steps in the KB above.
3. Use the System File Checker tool to repair missing or corrupted system files
1. Open the command promote with Administrators.
2. At the command prompt, type the following command, and then press ENTER:
sfc /scannow
Any errors are found in the steps above, please let me know.
Hope this helpful.
Best Regards,
Jason Zeng
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Migrating a mailbox cross forest from exchange 2013 Sp1 to exchange 2010 SP2 Update rollup 8

I can migrate a mailbox fine from exchange 2010 sp2 update rollup 8 to exchange 2013 sp1 or Cu2.
I was testing today migrating cross forest from 2010 sp2 udpate rollup 8 back to exchange 2010 sp2 but I get the below error. Is this even possible? I cannot find any documentation on this scenario yet.
VERBOSE: [21:52:47.622 GMT] New-MoveRequest : The remote server doesn't support client 'casservername.domain.com'
version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
VERBOSE: [21:52:47.637 GMT] New-MoveRequest : Admin Audit Log: Entered Handler:OnComplete.
The remote server doesn't support client 'casservername.domain.com' version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
+ CategoryInfo : NotSpecified: (0:Int32) [New-MoveRequest], RemotePermanentException
+ FullyQualifiedErrorId : 782D22F0,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest

Hi Steve,
I'm a little confused what you are saying. Here is my understanding:
When you migrate mailboxes from Exchange 2013 back to Exchange 2007, the above error occurs.
If I have misunderstood your concern, please let me know.
For migrating mailboxes back to Exchange 2007, there is a simple and straightforward method. Please use the New-MailboxExportRequest cmdlet to convert all mailboxes into pst files. And then use the Import-Mailbox cmdlet to import all pst files into Exchange
2007.
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

DPM 2012 sp1 Exchange 2013 sp1

Hello
Is DPM 2012 sp1 supported to backup Exchange 2013 sp1?
Bulls on Parade

Hello,
At present, there are no official articles or Exchange Team Blogs to verify whether DPM 2012 sp1 supported to backup Exchange 2013 sp1.
Before you use DPM 2012 sp1 to back up exchange 2013 sp1, please test it in lab environment. If there is any error, please free let me know.
Cara Chen
TechNet Community Support

Exchange 2013 SP1 Installation Errors I Cannot Resolve

Good Afternoon All -
Note: I updated this post an hour after posting. Still no solution, but please see updated info at end of this post)
I'm trying to introduce Exchange into an existing, small environment. The server I'm trying to install it onto is an SBS 2011 server (single server.) Even though SBS comes with Exchange, I found out that it's installation was corrupted and someone
had attempted to uninstall it before. Yes, it's being installed onto a server with a DC. I considered creating a Hyper-V VM on the server for Exchange, but thought it may be better to try to install directly onto server instead.
Before I started, I made sure all Exchange data had been removed. I checked for and deleted (if present) all Exchange-related objects in ADSI, ADU&C, files, and registry entries.
When I try to install Exchange 2013 SP1, I get the below errors. I know that some are easily resolved by installing pre-requisites - however - others aren't - especially the pending reboot one. I've restarted the server many times when making
changes or applying various updates and still get flagged to restart during installation. I've tried the SBS 2011 repair disc as well, but had many issues with it. In all honesty, the whole server needs to be wiped and re-installed, but
cannot do at this point.
Besides the errors below, I've zipped up the ExchangeSetupLogs folder and placed them in the link below. Also below are system specs. The only edit I made in them is a find/replace for server and domain name.
ExchangeSetupLogs Folder
System Specs
Xeon E31270 3.4Ghz
16gb RAM
Windows Server 2011 SBS x64 (Domain Controller Role Installed & Used)
C:\ - RAID 1 = 500gb
D:\ - SATA HDD = 320gb
E:\ - SATA HDD = 320GB
Should I perhaps try to install to a VM on the server or think that would use too many unnecessary resources?
Any help would be appreciated - Thanks!
Error:
This computer requires the update described in Microsoft Knowledge Base article KB2619234 (http://go.microsoft.com/fwlink/?LinkId=262359).
Without this update, the Outlook Anywhere feature may not work reliably.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.Win7RpcHttpAssocCookieGuidUpdateNotInstalled.aspx
Error:
There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer and then
run Setup again.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.PendingRebootWindowsComponents.aspx
Error:
The Windows component RSAT-Clustering isn't installed on this computer and needs to be installed before Exchange Setup can begin.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.RsatClusteringInstalled.aspx
Error:
This computer requires the Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit. Please install the software from
http://go.microsoft.com/fwlink/?LinkId=260990.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UcmaRedistMsi.aspx
Error:
An unsupported operating system was detected. Exchange Server 2013 Client Access, Mailbox, and Edge Transport server roles support
Windows Server 2008 R2 SP1 or later and Windows Server 2012.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersion.aspx
Warning:
Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected
in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected
in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
Ben K.
UPDATE
I just tried fixing a few things and tried again. Still no luck. Below is what I changed as well as the errors received. Only option was Retry. Can I just not install it onto this environment?
What I Changed
Installed Unified Comm Managed API 4.0 (Required Uninstalling Speech Analysis app before it would install)
Installed KB2619234 for Outlook Anywhere
Installed 12 updates - Server fully patched
Exchange Setup Errors
Error:
An unsupported operating system was detected. Exchange Server 2013 Client Access, Mailbox, and Edge Transport server roles support
Windows Server 2008 R2 SP1 or later and Windows Server 2012.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersion.aspx
Warning:
Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected
in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected
in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
Thanks Guys -

Hi,
Agree. Windows Server 2011 SBS x64 can be the problem.
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

Exchange 2013 SP1 | Another HTTP 500.0.0 Error

Help!
We are in the middle of migrating from Exchange 2010 SP3 to Exchange 2013 SP1 and we are being plagued with HTTP 500 errors on every Exchange 2013 server now.
I have two Client Access servers installed (EXCHFE01 & EXCHFE02) and one backend mailbox server (EXCHMB03) with the Client Access role also installed (for troubleshooting purposes). Once I get everything working I'll install two backend 2013 servers
with the mailbox role only for production (load-balanced, clustered, etc). I still have two Exchange 2010 mailbox servers left since one has a single large mailbox left on it and the other hosts public folders. I'll get to migrating those later. All Exchange
2013 servers are running Windows Server 2012. All are on the same LAN and no firewalls are between them.
On all three 2013 servers (EXCHFE01, EXCHFE02, EXCHMB03) I'm getting the dreaded HTTP 500 error whether I try to get to OWA or ECP. This did work at one point where I could at least login to the mailbox server (EXCHMB03) and migrate all my mailboxes over
to it. Sometime this morning after the two Client Access servers were installed the mailbox server stopped working (HTTP 500 errors). This is very frustrating because I can't even login to a console to manage Exchange from any server at this point.
Both Client Access servers aren't really showing anything of value in the event logs or the IIS logs. The mailbox server (EXCHMB03) does show the following event 3002:
Protocol /Microsoft-Server-ActiveSync failed to process request from identity NT AUTHORITY\SYSTEM. Exception: Microsoft.Exchange.Security.Authentication.BackendRehydrationException: Rehydration failed. Reason: Source server 'NT AUTHORITY\SYSTEM' does not have token serialization permission.
at Microsoft.Exchange.Security.Authentication.BackendRehydrationModule.ProcessRequest(HttpContext httpContext)
at Microsoft.Exchange.Security.Authentication.BackendRehydrationModule.OnAuthenticateRequest(Object source, EventArgs args).
...and I get the following when I run the Exchange Management Shell tool on the same mailbox server (along with lots of other red HTML text):
More Information:
This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.
The Client Access servers show the following errors:
Performance counter updating error. Counter name is Location cache update time, category name is MSExchange Active Manager Client. Optional code: 3. Exception: The exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
at System.Diagnostics.PerformanceCounter.InitializeImpl()
at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
Last worker process info : System.ArgumentException: Process with an Id of 4040 is not running.
at System.Diagnostics.Process.GetProcessById(Int32 processId)
at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
Processes running while Performance counter failed to update:
888 svchost
264 smss
532 conhost
2576 Microsoft.Exchange.UM.CallRouter
1596 WMSvc
3932 dllhost
4020 svchost
2308 dwm
5060 taskhostex
844 svchost
1972 Microsoft.Exchange.Directory.TopologyService
1228 inetinfo
1316 vmtoolsd
3896 svchost
780 svchost
1580 rundll32
1668 mqsvc
816 dwm
3840 slui
3532 rdpclip
3980 WmiPrvSE
4200 SppExtComObj
4288 winlogon
2140 SMSvcHost
676 svchost
1564 svchost
1296 Microsoft.Exchange.Diagnostics.Service
1472 Microsoft.Exchange.ServiceHost
1204 svchost
1292 ServerManagerLauncher
488 winlogon
664 svchost
572 lsass
3236 dllhost
2972 WmiPrvSE
4484 w3wp
388 csrss
1600 rundll32
564 services
1260 msdtc
5032 sppsvc
1448 MSExchangeHMHost
824 LogonUI
4204 VSSVC
2524 userinit
2700 MSExchangeFrontendTransport
1708 SMSvcHost
728 svchost
460 wininit
904 svchost
992 svchost
4996 TSTheme
4240 slui
4904 taskhost
452 csrss
4340 csrss
4 System
1164 spoolsv
1988 slClient
2760 MSExchangeHMWorker
0 Idle
Performance Counters Layout information: FileMappingNotFoundException for category MSExchange Active Manager Client : Microsoft.Exchange.Diagnostics.FileMappingNotFoundException: Cound not open File mapping for name Global\netfxcustomperfcounters.1.0msexchange active manager client. Error Details: 2
at Microsoft.Exchange.Diagnostics.FileMapping.OpenFileMapping(String name, Boolean writable)
at Microsoft.Exchange.Diagnostics.PerformanceCounterMemoryMappedFile.Initialize(String fileMappingName, Boolean writable)
at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetAllInstancesLayout(String categoryName)
... and...
A transient failure has occurred. The problem may resolve itself. Diagnostic information:
Microsoft.Exchange.Data.DataSourceOperationException: The request failed. The remote server returned an error: (503) Server Unavailable. ---> Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed. The remote server returned an error: (503) Server Unavailable. ---> System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.Exchange.WebServices.Data.EwsHttpWebRequest.Microsoft.Exchange.WebServices.Data.IEwsHttpWebRequest.GetResponse()
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
--- End of inner exception stack trace ---
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(IEwsHttpWebRequest& request)
at Microsoft.Exchange.WebServices.Data.ExchangeService.InternalFindFolders(IEnumerable`1 parentFolderIds, SearchFilter searchFilter, FolderView view, ServiceErrorHandling errorHandlingMode)
at Microsoft.Exchange.WebServices.Data.ExchangeService.FindFolders(FolderId parentFolderId, SearchFilter searchFilter, FolderView view)
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback)
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.GetOrCreateFolderCore(String folderName, FolderId parentFolder, Func`1 creator)
at Microsoft.Exchange.Data.Storage.Management.AsyncOperationNotificationDataProvider.GetDefaultFolder()
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.<>c__DisplayClass1b`1.<InternalFindPaged>b__13()
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback)
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.<InternalFindPaged>d__21`1.MoveNext()
at Microsoft.Exchange.Data.Storage.Management.AsyncOperationNotificationDataProvider.<GetNotificationDetails>d__4.MoveNext()
at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
at Microsoft.Exchange.Servicelets.CertificateNotificationServicelet.RemoveAllNotification()
at Microsoft.Exchange.Servicelets.CertificateNotificationServicelet.UpdateDataInMbx(List`1 certificates)
at Microsoft.Exchange.Servicelets.CertificateNotificationServicelet.Work()
I've tried all sorts of recommended fixes but none have worked so far:
ADSIEdit and remove msExchCanaryData0 data
Reinstall Exchange multiple times
Rebooted multiple times
This article: http://social.technet.microsoft.com/Forums/exchange/en-US/08d3777c-dc03-4411-8c87-7db37d2f406a/exchange-2013-owa-login-error-http-500?forum=exchangesvrclients
Rebooted DCs multiple times (no exchange servers are DCs)
I'm sure I've left out a few troubleshooting steps since I've been working at this for two days. Can anybody offer any advice? I'm at my wits end here...

Hi,
Please check whether the mail.mydomain.com is pointed to your Exchange 2010 or Exchange 2013. Please run the following command to check your OWA virtual directores and ECP virtual directories:
Get-OwaVirtualDirectory -ShowMailboxVirtualDirectories | Select Identity,name,Internalurl,ExternalUrl,*auth*
Get-EcpVirtualDirectory -ShowMailboxVirtualDirectories | Select Identity,name,Internalurl,ExternalUrl,*auth*
In IIS manager > Default Web Site, please make sure Anonymous Authentication is Enabled in Authentication. Confirm that "Require SSL" is checked on the SSL Settings of the default web site.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 SP1 cu8 - mssing cmdlet - Get-SendConnector command missing, cannot change smart host port

Hi Everybody,
For some reason my Exchange 2013 SP1 cu8 are missing a bunch of cmdlets.
When i run the exchange powershell and get all the cmdlet command - i noticed all the send and receive connectors are missing.
This all started when i needed to change the smart host port for a client because their internet provider was blocking port 25.
So i did the traditional cmdlet
Get-SendConnector
Set-SendConnector -Indentity "connector name" -Port 551
Both commands i get "The term Get-SendConnector is not recognized as the name of a cmdlet, function, etc"
When i type Get-ExCommand
Any reference to SendConnector and ReceiveConnector are not on the list.
Am I missing somethings? This is a classic example why GUI and cmdlet functions should both be available and not just on cmdlets.
I went on other Exchange 2013 SP1 cu7 servers to see, and they all have the Send and Receive connectors in the cmdlets.
The only difference with this particular setup, is that this is the first Exchange 2013 on-premise installation with Windows 2012 r2 Small Business Essentials. However, i very much doubt the on-premise installation add-on to SBS would cause any issues
to missing cmdlets.
I searched all over the internet and found nothing.
Now my biggest fear is to re-install Exchange and import the mailboxes manually.
Any help is greatly appreciated.
MattLok

Hello
check role asigment for your user:
Get-ManagementRoleAssignment -GetEffectiveUsers | Where { $_.EffectiveUserName -Eq "administrator" }
sorry my english

What happend New-MailboxExportRequest cmdlet in exchange 2013 SP1 is missing?

Cmdlet New-MailboxExportRequest is not recognize cmdlet in Exchange 2013 SP1
How can i do export mailbox to pst file in exchange 2013 SP1?

You might be facing this issue because of not having the rights to execute the New-MailboxExportRequest CMDLET.
Follow the steps given below in order to export the mailboxes into PST file
1. Open the Exchange Console and run:
New-ManagementRoleAssignment -Name "Import Export PST" -SecurityGroup "Organization Management" -Role “Mailbox Import Export"
This will generate a new role group called Import Export PST to the Oranization Management group with the role Mailbox Import Export.
You should Close and Restart the Exchange Management System again so that the changes made will get reflected in the settings, otherwise you will still get the same erroriIf not
restarted. Now move to the next steps.
2. Assign “Mailbox Import Export” role to it.
3. Add Desired Users to Role Group
4. Create Network Share ( Exchange Trusted Subsystem group has read/write permission to NTFS Permissions)
5. Run PS New-MailboxExportRequest
6. Monitor New-MailboxExportRequest
Verify PST File has been created on the network Share and you are done.
If you get the same error again, then there will be some hardware or software issues due to which you are not able to export mailboxes into PST files. In that case, you can make
use of any third party tool like Stellar Phoenix EDB To PST converter, which will help you to export your exchange database files to PST files easily and quickly. You can try this software by downloading its demo directly from their site http://www.stellarinfo.com/email-repair/edb-pst-converter.php

Exchange 2013 SP1 mailbox role on 2012 R2 and 2012

Similar Messages

Maybe you are looking for