Showing posts from 2011

Exchange 2010 MMC Fails to Load - Fixes

Common Errors While Opening Exchange Management Console - "How to Fix Them"
Connecting to the remote server failed with the following error message: The WinRM client cannot process the request.  It cannot determine the content type of the HTTP response from the destination computer.  The content type is absent or invalid.  For more information, see the about_Remote_Troubleshooting Help topic.  It was running the command 'Discover-ExchangeServer -IseWIA $true -SuppressError $true'.
The WinRM client received an HTTP server error status (500), but the Remote service did not include any other information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic. It was running the command 'Discover-ExchangeServer -UseWIA $true -SuppressError $true'.

Cause :- Missing parameter in Applicationhost.config file / IIS was reinstalled / Configuration Mismatch
Fix 1 -
Make Sure IISAdmin Service is up and running (Automatic and …

How To Work On Cross Site Failure in Exchange 2010 Environment (Failover and Failback)

Lets consider we have 2 Site "SITE ALPHA and SITE BETA" , SITE ALPHA is running 2 Exchange 2010 Server and SITE BETA is running 1 Exchange 2010 Server. SITE ALPHA is configured as Active Cluster Node and SITE BETA as Passive Cluster Node. In this documentation we will try and get the Passive Cluster Node up and running if the Active Cluster goes down and even do a failback. The entire infrastructure is designed keeping the High Availability options of Exchange 2010.
This is how my Exchange Inftrastructure looks like:-
EXCAHNGE SERVER SITE DAG FSW CAS ARRAY DATABASE COPY Alpha (Prod Site) DAG 1 FSW 1 Mapi1 D1 ,D2 ,D3 Alpha (Prod Site) DAG 1 FSW 1 Mapi1 D1 ,D2 ,D3 Beta (DR Site) DAG 1 FSW 2 Mapi2 D1 ,D2 ,D3
Prod Site  - Production Site DR Site     - Disaster Recovery Site
Before moving further one should understand some important concepts or phrases that we will use in this documentation.
Database Availability Group (DAG)

A database availability gr…

Microsoft Exchange Server 2010 Downloads

Microsoft Exchange Server 2010 Service Pack 1 (SP1)

Fine Name: Exchange2010-SP1-x64.exe
Size: 522.2MB
Version: 14.01.0218.015

Update Rollup 1 for Exchange Server 2010 Service Pack 1 (KB2407028)

File Name: Exchange2010-KB2407028-x64-en.msp
Size: 15.8MB

Update Rollup 2 for Exchange Server 2010 Service Pack 1 (KB2425179)

File Name: Exchange2010-KB2425179-x64-en.msp
Size: 28.1MB
Version: 14.01.0270.001

Forefront Protection 2010 for Exchange Server

Forefront Protection Server Management Console

File Name: fpsmc_setup.…

Unable To Reply/Forward Email From OWA - Exchange 2010

Exchange 2010 SP1. Unable to Reply / Forward email from Outlook Web Access. Even we have seen similar issue with ActiveSync. While hitting reply / performing a sync throws an error similar to :-


Exception type: System.ArgumentException
Exception message: imceaDomain must be a valid domain name.

Call stack

Microsoft.Exchange.Data.Storage.InboundConversionOptions.CheckImceaDomain(String imceaDomain)
Microsoft.Exchange.Data.Storage.InboundConversionOptions..ctor(String imceaDomain)
Microsoft.Exchange.Clients.Owa.Core.Utilities.CreateInboundConversionOptions(UserContext userContext)
Microsoft.Exchange.Clients.Owa.Core.ReplyForwardUtilities.CreateReplyOrReplyAllItem(BodyFormat bodyFormat, Item item, ReplyForwardFlags flags, Boolean replyAll, UserContext userContext, StoreObjectId parentFolderId)
Microsoft.Exchange.Clients.Owa.Core.ReplyForwardUtilities.CreateReplyItem(BodyFormat bodyFormat, Item item, ReplyForwardFlags flags, UserContext userContext, StoreObjectId parentFold…

Activate Exchange 2010 Manually

In this Blog i will try to put some tested methods to activate your Microsoft Exchange 2010.

-The Build version of Exchange is 14.00.0702.000.
-The RTM version of Exchange 2010 is 14.00.0639.021.
-The SP1 version of Exchange is 14.01.0218.015.

Always makes sure you are running SP1 version of Exchange 2010 not RTM. If its RTM upgrade it to SP1:-

-Open Exchange Shell in Elevated Mode and run the following command --

Set-ExchangeServer ServerName -ProductKey #####-#####-#####-#####-#####

-Restart Microsoft Exchange Information Store Service

Note:- Mention the ServerName without mistake

Some Key type Description :-

CUS This custom key requires special actions to activate or install.
MAK This volume license key (MAK) allows multiple activations.
RTL This retail key allows multiple activations.
STA This setup key bypasses a…

Message Routing in Exchange 2007

Exchange 2007 simplifies the management of the physical layout of Exchange by eliminating the need for routing groups and relying on the Active Directory site architecture instead. Servers with the Hub Transport role accept messages from Mailbox servers, determine the location of the destination mailbox database, and deliver the message to a Hub Transport server in the remote Active Directory site.
I am sure you might have read about Exchange 2007 roles. Let me try and brief it again:- The best way to think of Exchange 2007 server roles is to think of a server that has the necessary software and configuration to perform only a specific set of functions. This makes installing servers with dedicated functions much easier. Dedicated server roles are also more secure because only the necessary software is installed, thus reducing the attack surface. With Exchange 2007, the server roles are assigned with the setup.
There are five basic server roles: -Mailbox Server Role -Client Access Role -Hu…

Exchange 2007 Services and Function Part 2 (A Little More)

In My Previous Blog i tried putting up Exchange Functions with the related executables. In this blog you will see more description on Exchange 2007 Services which are responsible for Client Access Server, Hub Transport Server, Mailbox Server, Edge Server and Unified Messaging. This article is purely published on the basis of event triggered from my virtual lab. Event ID's whatever you see in your production environment may vary compare to this however the function of each service will remain the same.
1) Microsoft Exchange Active Directory Topology: This service is responsible to provide the information of Active Directory Information to Exchange Server Components. This service need to be started on the client Access Server, Hub Transport Server, Mailbox Server and Unified Messaging Server. It doesn’t depend on dependencies in order to start. However there are some other Exchange Services which are dependent on this service. 
List of Services which are dependent on this service: -


Exchange 2007 Services and Function

Service Name Executable Name Function Microsoft Exchange Active Directory Topology/MSExchangeADTopology MSExchangeADTopologyService.exe Provides Exchange Server 2007 with Active Directory site, domain controller, and global catalog server information. This component is found on all Exchange 2007 server roles except the Edge Transport Microsoft Exchange ADAM/ADAM_MSExchange Dsamain.exe This is the ADAM instance that holds the Edge Transport server role's configuration, recipient information, safe sender lists, and blocked sender lists. This service is only found on the Edge Transport role. Microsoft Exchange Anti-spam Update/MSExchange AntispamUpdate Microsoft.Exchange.AntispamUpdateSvc.exe This service provides updates for the content filter service. This service is found on the Edge Transport and Hub Transport server roles. Microsoft Exchange Credential Service/EdgeCredentialSvc EdgeCredentialSvc.exe This service monitors credential changes for the ADAM database and updates the Edge Transport …