"..Unnatural work produces too much stress.."

Attachments not showing in Microsoft Outlook

Interesting topic

ISSUE: When an user sends email with  attachment Microsoft Outlook clients don’t see paperclip nor attachment but the size of the mail shows there is more then just text. The attachment is visible in OWA. When forwarding the message from OWA the attachment shows up in outlook.

FINDINGS: I think the issue related to misformed MIME. The content type of the email is not correct; it is multipart/related, and should be multipart/mixed.

  • It may or may not be an issue on your end, incorrectly formatted mime messages sent by the sender can cause it not to render correctly in Outlook.
  • Things like the sender running third party apps such as disclaimers can mess up the mime formatting.
  • RFC 2387 describes the intended use of multipart/related:
    • “The Multipart/Related media type is intended for compound objects consisting of several inter-related body parts. For a Multipart/Related object, proper display cannot be achieved by individually displaying the constituent body parts.”
    • Exchange handles multipart/related specially – i.e. it considers all attachment parts inside multipart/related as “inline”. Such attachments are normally hidden from the attachment list and supposed to be accessible from the body itself, like inline images. Some clients, like OWA, can determine whether attachments are really “inline” by analyzing a message body – if they don’t find any reference to such attachment in a body they fix it by displaying it in attachment list. Other clients like Outlook will trust how attachments are marked by Exchange and hide them.
  • A “correct” way to structure message would look like this:
    • Multipart/mixed
    • Multipart/related
    • Text/html – message body
    • Any inline attachments referenced from the body
    • Any normal attachments, like application/msword

 SUGGESTION: Add a Transport Rule to simply “force” us to use multipart/mixed (Only when the mail is coming from the specific domain) and that will make the attachment visible in Outlook.

SOLUTION: Launch Exchange Management Console

  • Expand Organization Configuration
  • Select Hub Transport
  • On the right-hand Action Pane, select New Transport Rule …
  • Give the rule a name
  • Select when the From Address contains Specific Word click the highlighted “Specific words”, Type “”
  • click Add, click OK, and then click Next
  • Select “set header with value,” click the highlighted “header” text, type
  • Content-Type, click OK
  • Click the highlighted “value” text, type multipart/mixed, click OK, and then click
  • Next
  • On the “Exceptions” page, simply click next
  • At the final “Create Rule” page
  • Click New, and then click Finish

April 12, 2012 Posted by | Exchange Management Console, Exchange Server 2007, Exchange server 2010, Mails, Microsoft, Office, Outlook, Software | , , | Leave a comment

Exchange server 2010 SP1 – Step by Step installlation on the production server – Live

Earlier i’ve done the Exchange server migration – 2007 to 2010 – Live cast, Its been 10 months since Exchange team release the SP1 for Microsoft Exchange server 2010….today i’m doing Microsoft Exchange server 2010 SP1 upgradation…Live page is opened.

Click here to view this live page


June 24, 2011 Posted by | Active Sync, DAG, ECP, Edge Server, EWS, Exchange Management Console, Exchange Management Shell, Exchange Pre-Deployment Analyzer, Exchange server 2010, Exchange Server Profile Analyzer, Forefront, Forefront Endpoint protection 2010, Hyper-V, IP Block List, Log Parser, Mailbox Server Requirements Calculator, Microsoft, New Service Pack, Office 2010, Office for Mac, Power Shell, Software, Transport architecture, Windows Server 2008 R2 | , , , , , , , , , , , , , , | Leave a comment

Exchange server 2010 management tools do not start after the installation – Solution

Problem impacts Exchange management tools on servers running Exchange 2010 on

  • Windows Server 2008 SP2
  • Windows 2008 R2 RTM

Symptom: Event ID 1000 & 1023

  • Faulting application Powershell.exe, version 6.0.6002.18111, time stamp 0x4acfacc6, faulting module mscorwks.dll, version 2.0.50727.5653, time stamp 0x4d54a59c, exception code 0xc0000005, fault offset 0x00000000001d9e19, process id 0x%9, application start time 0x%10.
  • .NET Runtime version 2.0.50727.3053 – Fatal Execution Engine Error (000007FEF9216D36) (80131506)
  • Exchange Management Shell does not start
  • Exchange Management Console does not start
  • There might be a crash in Exchange Mailbox Replication Service (it is not clear yet if this is related)
  • Event Viewer might have trouble opening

Resolution : Please see the following KB article for the resolution of this problem. The solution already explained in the Microsoft Exchange team Blog.

June 21, 2011 Posted by | Exchange Management Console, Exchange Management Shell, Exchange server 2010, Microsoft, Software | , , , | Leave a comment

Microsoft Exchange 2010 – Administrator Audit logging

Another nice feature introduced in Exchange 2010 is Administrator Audit logging. Audit logging allows an organization to examine different policies. A second important benefit is the review of configuration changes made to the Exchange organization through the Exchange Management Console, Exchange Web Services, and Exchange Management Shell. Audit Logging is useful in tracking configuration changes made within an Exchange Organization, and help identifying any errors. In Exchange 2010 Microsoft introduced AdminAuditLogConfig.

Check out the following commands


To enable if its disabled: Set-AdminAuditLogConfig -AdminAuditLogEnabled $true :

Search in the AdminAuditLog: Search-AdminAuditLog –Cmdlets New-Mailbox, Remove-Mailbox | FT :

Microsoft article about AdminAuditLog, Click here

April 26, 2011 Posted by | Exchange Management Console, Exchange Management Shell, Exchange Online, Exchange server 2010, Microsoft, Software | , , , , , , | Leave a comment

Exchange 2010 – Attachment size – Global setting (for Send & Receive)

Attachment size setting inside Exchange server 2010 for global user settings.

  • Go to your mailbox server
  • open EMC
  • goto Organization configuration
  • goto Hub Transport
  • select global setting tab

Edit the Transport settings and change the parameters as below.

Once you done it, click Apply and ok

Remember one thing, the more you increase the size of the attachment, the load on the CAS & Edge server increase…plus the Virus scanning engine too.

Thats all folks!!!

March 28, 2011 Posted by | Computer TIPS, Edge Server, Exchange Management Console, Exchange server 2010, Forefront, Mailbox Server Requirements Calculator, Mails, Microsoft, Software, Transport architecture | , , | Leave a comment

Exchange server 2010 CAS array to MAPI load balance – Detailed

Most of you guys must have experience the scenario when “Outlook connection lost….” even if you have Exchange server 2010 (with Edge, 2 clustered H&C and 2 DAG configured MB) and Outlook 2010 in place. The reason is that, when you are doing a maintenance on one of the H&C, and if the client is connected to that H&C, communication to the MB is lost. The reason for this is that the cluster load balancing on the H&C cluster handler is not in place, even if the cluster name is published in the DNS server.

In Exchange 2007, 5 server roles that performed distinct functions within the Exchange organization. One role in particular – the Client Access server role – introduced a variety of new Web services, including the Availability service, the Auto discover service and Calendar Concierge services.

In Exchange 2010, same 5 server roles exists. However, there are some significant architectural changes and some shift in responsibilities. The most significant change in Exchange 2010, two new services on CAS called the RPC Client Access and Address Book services establish the RPC (Repote Procedure Call) endpoint for MAPI(Messaging Application Programming Interface), NSPI(Name Service Provider Interface) and RFR (Request for Response) client access. This new functionality replaces the RPC endpoints in the Information Store. The RPC endpoint in the Information Store has not been removed in Exchange 2010, but it has been modified to only accept requests from CAS servers. The RPC endpoint for public folder database access remains on the Mailbox server, however, Outlook clients now communicate directly with the RPC Client Access service on the Mailbox Server for public folder database access, and not with the Information Store.

When CAS starts communicating with the Mailbox server, it makes sense to view it as the Client Access server communicating with the Mailbox database via the Mailbox server that hosts the database. This is especially evident in a load-balanced array of Client Access servers and/or where your environment is configured to use Database Availability Groups that are associated with a Client Access server or Client Access server array.

  • In a non-load balanced environment, the mailbox database is associated with only a single Client Access server.
  • In a load-balanced environment, the Mailbox database is associated with the load balanced array of multiple Client Access servers.

By default, before a Client Access array is configured,

  • all databases are associated with a Client Access server in the environment
  • the Outlook clients communicate directly with the Client Access server until the association with the database is updated to be the Client Access array.

In order for the clients to utilize a CAS array

  1. Create a Client Access array with an FQDN (Fully Qualified Domain Name).
  2. Load balance your CAS servers in a CAS array by whatever method you choose – Both Hardware LB or Windows Network LB are supported load balancers
  3. Add the Client Access servers within the AD site to a load balanced array and in DNS associate the unique FQDN to the Virtual IP of the load-balanced array.
  4. Configure your load balancing array to load balance the MAPI RPC ports – TCP 135, UDP/TCP 6005-65535; or set static ports
  5. Configure the databases to utilize the CAS array… Use the new-clientaccessarray cmdlet to create the CAS array object. Eg: New-ClientAccessArray –Name “Tromso CAS Array” –Fqdn” –Site “SITEA”

How to Setup!!!..

Goto one of the CAS server where the NLB is ( to read more about New-ClientAccessArray cmdlet, click here )

[1] Check is there are any pre-created CAS Arrays. PS Command : Get-ClientAccessArray

[2] Create new Client Access Array. Run the Cmdlet in EMS New-ClientAccessArray -Fqdn -Site “Redmond” -Name “”

[3] Associate databases with this CAS Array –

Use this CMDLet to add mailbox database to CAS array. Add all mailbox databases at once – Get-MailboxDatabase | Set-MailboxDatabase -RPCClientAccessServer “”

Now the best part –

Configuring Outlook 2010 using Auto Discover

If you already configured Outlook client, Close the outlook, then goto Control Panel->Mail and change the Server name to the new CAS NLB name

If you are going to use a new outlook configuration, Auto discover will return the new CAS NLB name.

Thats all folks!!! Enjoy!!!

March 28, 2011 Posted by | Active Sync, DAG, ECP, Entourage, EWS, Exchange Management Console, Exchange Management Shell, Exchange server 2010, HTTPS, Hyper-V, IMAP, IP, Mailbox Server Requirements Calculator, Mails, Microsoft, OAB, Office, Office 2010, Office 2011, Office for Mac, Office Professional Plus, Outlook, Outlook Webapps, OWA, POP3, Protocols, Public Folder, Software, TCP, Transport architecture | , , , , , , , , , , , , , , | Leave a comment

Un-installing/De-commissioning Exchange server 2007 Mailbox from Passive cluster node for Exchange 2010

  1. Open the command prompt of the Passive mailbox server..make sure you logged in as domain administrator.
  2. Go to C:\Program Files\Microsoft\Exchange SErver\Bin
  3. Type the command setup /mode:uninstall

Now you have successfully uninstall the Exchange server mailbox role from the passive node, but the cluster environment server information still exists, and we need to remove that as well.

To do that we need to…

  • Open the Cluster Management Tool
  • Expand the cluster resource name
  • Expand the Nodes
  • Right click the passive node server
  • Click on More actions -> click on “Stop cluster service”


 Once you “Stop Cluster Service”, then click on More actions again and click Evict and click the Evict Node….

Once you done this, restart the server.

Once the server is up…do the following too

  1. Open the Server manager console
  2. Click on Features and then click on Remove Features
  3. Uncheck Failover Clustering
  4. Click on Yes to reconfirm and click on NEXT
  5. Click on Remove.
  6. After the Server is restarted
  7. Remove any remaining files and folders from the Exchange Server program files folder and subfolders.

Thats the end of Exchange Server 2007 Mailbox de-commissioning on a Passive node….Now go to the Active mailbox server of Exchange server 2007

This process is not as same like passive node. Here we can’t go with uninstall command only, because this server holds the culstered mailbox server information and it is online. In order to remove this,

Go to the command prompt..change the directory to C:\Program files\Microsoft\Exchange Server\Bin

Type command /removeCMS /CMSName:<Clustername>

This will take the mailbox now offline from the cluster…

Now type setup /mode:uninstall

Once you finish this uninstallation, Exchange server 2007 last mail box has been remove from your do the evict

Goto command prompt (If the command prompt is open, close it and open it and then type

Cluster <mailbox cluster name> node <nodename> /force


Now you are completely depended on Exchange server 2010.

March 15, 2011 Posted by | Edge Server, Exchange Management Console, Exchange Management Shell, Exchange Server 2007, Exchange server 2010, Mailbox Server Requirements Calculator, Microsoft, Remote Connectivity Analyzer, Software, Transport architecture | , , | Leave a comment

Active Directory operation failed on *DomainController*. This error is not retriable. Additional information: Insufficient access rights to perform the operation.

When you try to move a mailbox from Exchange 2007 to Exchange 2010,  following error occured:

Active Directory operation failed on *DomainController*. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150E8A, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0

The user has insufficient access rights.

Exchange Management Shell command attempted:
’*OUStructure*’ | New-MoveRequest -TargetDatabase ‘Mailbox Database 1985885663′ -BadItemLimit ‘-1′

To resolve this error… editing the Advanced Security Settings for that user,

  • Open Active Directory Users and Computers
  • Find the user of which the mailbox error occured
  • Open  the properties of the user and go to the security tab (if this is not available, choose view and then advanced features in the AD users and computers under  MMC)
  • Click on [Advanced]
  • Check the box at the bottom which says “Include inheritable permissions from this object’s parent” and then click [OK] twice.
Error fixing

Then try to move it and it will work…

March 15, 2011 Posted by | Exchange Management Console, Exchange Server 2007, Exchange server 2010, Mailbox Server Requirements Calculator, Microsoft, Software | , , , | Leave a comment

Exchange 2010 – Manage CAS role – Access is denied error – HResult = -2147024891

ERROR: An IIS directory entry couldn’t be created. The error message is Access is denied.
. HResult = -2147024891

After installing Exchange 2010 server in an Exchange 2007 server environment may get some funny error results. After the installation Exchange 2010 , open the Exchange management console, you nee to go to Microsoft Exchange On-Premises -> ServerConfiguration -> Client Access and here you will receive the following error message.

So let run the “Get-OwaVirtualDirectory” in powershell and you will get the following result

From the power Shell command prompt .. Run

[PS] C:\Windows\system32>Get-OwaVirtualDirectory

An IIS directory entry couldn’t be created. The error message is Access is denied.
. HResult = -2147024891
    + CategoryInfo          : NotInstalled: (<ExchangeServer2007>\Exchange (Default Web Site):ADObjectId) [Get-OwaVirtualDirectory]
   , IISGeneralCOMException
    + FullyQualifiedErrorId : 4B12EB5D,Microsoft.Exchange.Management.SystemConfigurationTasks.GetOwaVirtualDirectory

Above command reads the Active Directory objects to see all the registered OWA virtual directories. The virtual directories you retrieve are the virtual directories from Exchange 2010,  but also from Exchange 2007. Next it connects to these directories and needs admin rights. This is the problem. Exchange 2010 creates a few new groups and one of them is Exchange Trusted Subsystem. Exchange Trusted Subsystem is automatically added to the local administrators group of the Exchange 2010 server but not on the Exchange 2007 servers. 

RESOLUTION :  All you need to do is add the Exchange Trusted Subsystem to the local administrators group on the Exchange 2007 CAS servers and restart the server, including the new 2010 H&C Server.

Now  run the “Get-OwaVirtualDirectory” in powershell we see:

[PS] C:\Windows\system32>Get-OwaVirtualDirectory

Name                                    Server                                  OwaVersion
—-                                    ——                                  ———-
Exchange (Default Web Site)             <ExchangeServer2007>                                 Exchange2003or2000
Public (Default Web Site)               <ExchangeServer2007>                               Exchange2003or2000
Exadmin (Default Web Site)              <ExchangeServer2007>                                 Exchange2003or2000

owa (Default Web Site)                  <ExchangeServer2010>                                 Exchange2010


March 15, 2011 Posted by | Exchange Management Console, Exchange Management Shell, Exchange server 2010, Microsoft, Software | , , , | Leave a comment

Old public folder – How to remove from Exchange server

It is difficult to delete old public folder from EMC. How to do it, use the ADSIEDIT to clear the old ones.

Right click on the folder you want to delete from CN=Exchange Administrative Group, CN=Databases,  and click delete. The go to Active directory Sites and Services and initiate the replication across the domain.

Go to EMC and refresh.

Thats it.

February 12, 2011 Posted by | Active Directory, Exchange Management Console, Exchange Management Shell, Exchange server 2010, Exchange Server Profile Analyzer, Mailbox Server Requirements Calculator, Mails, Microsoft, Public Folder, Windows Server 2008 R2 | , , | Leave a comment

%d bloggers like this: