The previously reported issue with Cumulative Update 6 (CU6) for Microsoft Exchange Server 2013, that you cannot manage Exchange Online mailboxes by using Exchange Admin Center (EAC) from an on-premises server. This issue has been addressed by Microsoft in lightning response, the following script will help you to fix this issue.

Download: Exchange Online mailboxes cannot be managed in Exchange Server 2013 CU6

To know more about the issue, please see Exchange Online mailboxes cannot be managed by using EAC after you deploy Exchange Server 2013 CU6

-Praveen

Published in Solutions

In the past we all had nightmares about the recovery of a failed or crashed exchange server. But from the version 2010 (even in 2007) the recovery process became really painless and easy. The following steps will help you to recover a completely failed/crashed server from scratch.

Though all of us know, I would like to emphasize the fact that most of the exchange configuration information are stored in the AD database and we only need to recover the application by using the AD information and then complete the Database recovery and other customized exchange settings.


Note – This document is reference only for Exchange server which are not part of Database Availability Group. If you wish to get more details about DAG member recovery, please follow 
Recovery Installation of a DAG Member with Multi Roles – Exchange Server 2010.

Before we proceed, please ensure that a proper account with required permissions are used to complete the activity.

Other thumb rules,

  • Prepare a server with OS and patches similar to failed server
  • Use the same hostname as the failed server
  • Same drive letters and capacity of disks should be used
  • Similar hardware capacity should be used to avoid performance issues.

Recovery Procedure for Exchange Server 2013, SP1

1. Logon AD console and reset the failed server computer account

Reset

2. Join the prepared server with similar characteristics and same host name (as stated above) to domain. Recovery will fail if the pre-requisite did not match with the failed server.

3. Log back in to the server being recovered using an account which has required permissions assigned and open the command prompt. Navigate to the location where Exchange Installation files are extracted and execute the cmdlet, Setup /m:RecoverServer /IAcceptExchangeServerLicenseTerms

setup recover cmd

4. Now sit back and relax, the process will automatically read the information from AD and recover the server.

Progress1

5. After the successful recovery process, please proceed with the custom configurations and restorations such as,

Exchange Virtual directory settings,
Restoration of Databases

Note – It is recommended to restart the server before the start of DB restore and other custom settings.

Share your experience!

-Praveen

Published in Articles

Update: On Windows Server 2012, follow Installation Guide of Exchange 2013 on Windows 2012 Server

This documents describes how the exchange environment for Exchange 2013 is installed. This includes the steps by step process of installing exchange in a new environment with Exchange Server 2013 preview version installation. From my thought, the installation will become much more easier when the RTM version is available to download. Even at this point the installation goes smooth if you follow the instructions correctly.

LAB Details:

One Domain Controller in Windows 2008 R2 Std, and running in Windows 2008 native mode.

One member server joined into the domain exchange2013.local.

Coivering Exchange 2013 Prerequisites

Login to the server App-Exchange2013 with domain credentials (Ensure that the domain account you use to install Exchange 2013 have sufficient privileges.)

See MS write up on permission required, however I use the Administrator account to avoid any permission issues.

-- You must ensure the account you use is delegated membership in the Schema Admins group if you haven't previously prepared the Active Directory schema. If you're installing the first Exchange 2013 Preview server in the organization, the account you use must have membership in the Enterprise Admins group. If you've already prepared the schema and aren't installing the first Exchange 2013 Preview server in the organization, the account you use must be a member of the Exchange 2013 Preview Organization Management role group.

Administrators who are members of the Delegated Setup role group can deploy Exchange 2013 Preview servers that have been previously provisioned by a member of the Organization Management role group. --

Now, open Windows PowerShell (preferable to run as administrator) and type “Import-Module ServerManager” without quotes

Run the following command to add the all the features for the role combination.

Role Combination

Add-WindowsFeature command

Only Mailbox role

OR

Mailbox and Client Access Server

Add-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI

Client Access Role

Add-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI

 1.       Run the below command on Windows Power Shell to add “Remote Tools Administration Pack”

 Cmdlet:  Add-WindowsFeature RSAT-ADDS

RSAT

Important: Ensure that you take a restart of the server before step to the next stage of installations.

1.       Once you finish the roles and features for the operating system, do install the following software in given order. Note – If you fail to follow the order may end up in error during Exchange installation.

  1. Download and Install Microsoft .NET Framework 4.5 RC
  2. Download and Install Windows Management Framework 3.0 (Note – restart the server at this point, and process to next step.)
  3. Download and Install Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit
  4. Download and Install Microsoft Office 2010 Filter Pack 64 bit
  5. Download and Install Microsoft Office 2010 Filter Pack SP1 64 bit
  6. Download and Install Microsoft Knowledge Base article KB974405 (Windows Identity Foundation)
  7. Download and Install Knowledge Base article KB2619234 (Enable the Association Cookie/GUID that is used by RPC over HTTP to also be used at the RPC layer in Windows 7 and in Windows Server 2008 R2)
  8. Download and Install Knowledge Base article KB2533623 (Insecure library loading could allow remote code execution)

Restart the server once you complete all the above software installations.

Once you done with all above software, follow below steps. This is also part of pre-requisites, do complete them before you start the actual installation.

  1. Uninstall Microsoft Visual C++ 11 Beta Redistributable (x64) (Open Program and Feature from Control Panel and uninstall the specified program) Note - This task must be done after you've installed UCMA, but before you run Exchange 2013 Preview Setup.
  2. Unistall_c_11_beta-updated
  3. Register ASP.NET with .NET Framework 4.5 in Internet Information Services (IIS)
    1. Open windows command prompt
    2. Run “%SystemDrive%\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -ir –enable” without quotes
  4. Do an IISReset after registering the ASP.NET with .NET Framework 4.5

Before you proceed with the Exchange 2013 installation, please reboot the server. Otherwise the pre-installation check may fail.

The actual Install Exchange Server 2013:

  • Extract the Exchange 2013 to local drive of the server
  • Run the setup.exe with Run as Administrator
  • Select appropriate selection on Check for Updates, I selected do not check.
  • The setup will start copying the files, wait for it to complete and click on “next”
  • On Introduction Page, click “next”
  • Accept the License Agreement and say “next”
  • Error reporting, I selected “No” for time being, and click on “next”
  • Click next on Checking for required software section
  • Select the roles, (mailbox and Client access). By now you must have known that the hub transport role now in Mailbox server.

Server_Roles

  • Installation space and Location, I leave as default and click on “next”
  • Give an Organization name, and click on Next

Org_Name

  • Leave default on Malware Protection Settings, click next
  • Give the external URL on Configure Client Access Server page, and click next

CAS_Internet_Facing

  • Leave as default on CEP page, and give “next”
  • You will see successful readiness check if you have done all the steps mentioned in this article. Click on Install button to start the installation process.

You will see a completion page after the successful installation of Exchange Server 2013. You may now go to the ECP or Exchange Management Shell for further configuartion, as the EMC has very limited

administration option.

Share your feedback on the installation experience, hope this helped you in setting up your Exchaneg Server 2013 server.

References,

Install Exchange 2013 Using the Setup Wizard , Exchange 2013 Prerequisites, Verify an Exchange 2013 Installation

-Praveen

Published in Articles
theme by reviewshub