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.

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.

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.

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.

Open the command prompt of the Passive mailbox server..make sure you logged in as domain administrator.

Go to C:\Program Files\Microsoft\Exchange SErver\Bin

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

Open the Server manager console

Click on Features and then click on Remove Features

Uncheck Failover Clustering

Click on Yes to reconfirm and click on NEXT

Click on Remove.

After the Server is restarted

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 setup.com /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 domain..now do the evict

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

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

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.

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.