PREMNAIR'S Blog

"..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 “contoso.com”
  • 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
Advertisements

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

Microsoft Exchange on Twitter: A new hash tag for Exchange

Microsoft Exchange on Twitter has moved to a new hash tag – #MSExchange.  If you tweet about Microsoft Exchange or related topic, please use #MSExchange to tag your tweet… to follow use @MSFTExchange for the latest on Microsoft Exchange, including post updates from EHLO.

Thank you team

April 8, 2012 Posted by | Exchange Server 2007, Exchange server 2010, Microsoft, Twitter | , | Leave a comment

Update Rollup 6 for Exchange 2007 Service Pack 3

Update Rollup 6 for Exchange Server 2007 Service Pack 3 (SP3) resolves issues that were found in Exchange Server 2007 SP3 since the software was released. This update rollup is highly recommended for all Exchange Server 2007 SP3 customers. For a list of changes that are included in this update rollup, see KB2608656.
This update rollup does not apply to Exchange Server 2007 Release To Manufacturing (RTM), Exchange Server 2007 Service Pack 1 (SP1) or Exchange Server 2007 Service Pack 2 (SP2).

To Download, Click here

January 31, 2012 Posted by | Exchange Server 2007, Microsoft, New Service Pack, Software | , , | Leave a comment

Update Rollup 3-v2 for Exchange Server 2007 Service Pack 3 (KB2530488)

Update Rollup 3-v2 for Exchange Server 2007 Service Pack 3 (SP3) resolves issues that were found in Exchange Server 2007 SP3 since the software was released. This update rollup is highly recommended for all Exchange Server 2007 SP3 customers. This update rollup does not apply to Exchange Server 2007 Release To Manufacturing (RTM), Exchange Server 2007 Service Pack 1 (SP1) or Exchange Server 2007 Service Pack 2 (SP2). For a list of update rollups applicable to Exchange Server 2007 RTM , Exchange Server 2007 Service Pack 1 (SP1) or Exchange Server 2007 Service Pack 2 (SP2), refer to the Knowledge Base article KB937052. To know more/ download this, Click here

April 4, 2011 Posted by | Exchange Server 2007, Microsoft, New Service Pack, Software | , | Leave a comment

Restricting email to the Internet on a per user AND per domain basis

This blog post is meant to show how easy it now is to accomplish this oft heard request in Exchange 2010. Transport rules, introduced with Exchange 2007, provided a lot of new options for administration of mail resulting in even more requests for additional functionality. The rules now have new predicates and actions extending the possibilities of what can be done. For our example, the rule will restrictActive Directory Mail enabled users” who have their ‘Department‘ defined as ‘Temp Employees‘ from sending mail to the internet, except they must be allowed to send to 2 external domains called: ‘partnerdomain.com‘ and ‘fourthcoffee.com‘. Additionally, to reduce Helpdesk calls, you want to send an NDR when they violate the rule. For demonstration purposes I will use 2 Conditions, one Action and one Exception.

Microsoft Exchange Team Blog will explain you how to do it in Exchange 2010…beautiful blog post..click here

March 15, 2011 Posted by | Exchange Online, Exchange Server 2007, Exchange server 2010, Mails, MailTips, Microsoft, Office, Office 2010, Office 2011, Outlook, Outlook Webapps, Software, Transport architecture | , , | Leave a comment

An error occurred during discovery of the database availability group topology. Error: An error occurred while attempting a cluster operation. Error: Cluster API “AddClusterNode() (MaxPercentage=12) failed with 0×80070005. Error: Access is denied.”

If the witness server you specify isn’t an Exchange 2010 server, you must add the Exchange Trusted Subsystem universal security group to the local Administrators group on the witness server. These security permissions are necessary to ensure that Exchange can create a directory and share on the witness server as needed. If the proper permissions aren’t configured, the following error is returned:
Error: An error occurred during discovery of the database availability group topology. Error: An error occurred while attempting a cluster operation. Error: Cluster API “AddClusterNode() (MaxPercentage=12) failed with 0×80070005. Error: Access is denied.”

If you specify a witness server, you must use either a host name or a fully-qualified domain name (FQDN). Using an IP address or a wildcard name isn’t supported. In addition, the witness server cannot be a member of the DAG.

To know more read Exchange server migration – 2007 to 2010 – Live cast

March 15, 2011 Posted by | Exchange Server 2007, Exchange server 2010, Exchange Server Profile Analyzer, Mailbox Server Requirements Calculator, Microsoft, Software | | 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 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

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

That’s the end of the “EXCHANGE SERVER 2007 DE-COMMISSIONING PROCESS”

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:

Error:
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…..by 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

View user mailbox size from Outlook

December 22, 2010 Posted by | Computer TIPS, Exchange Server 2007, Exchange server 2010, MailTips, Microsoft, Office, Office 2010, Office 365, Office for Mac, Office Professional Plus, Outlook, Software | , | Leave a comment

Changing your domain password in OWA

In the previous edition of OWA and Exchange server 2007, there was a problem for users to change their password…because the loss of the IISADMPWD virtual directory as a supported feature in Windows Server 2008/IIS 7.0. This prevented OWA users with expired passwords from being able to change their password and log on. This was a problem for many OWA users ; especially remote/mobile users with non-domain-joined computers..From Exchange Server 2010 Service Pack 1 and Exchange Server 2007 Service Pack 3 (running on Windows Server 2008 or Windows Server 2008 R2) onwards, they have a new feature that will allow users with expired passwords to change their password. This also works for users who have their accounts configured to change password on next logon.

Use this procedure to enable it on Exchange 2007 SP3 and Exchange 2010 SP1 Client Access servers. If you are using a CAS Array, you must perform these steps on each CAS in the array.

  1. On the Client Access Server (CAS), click Start > Run and type regedit.exe and click OK.
  2. Navigate to HKLM\SYSTEM\CurrentControlSet\Services\MSExchange OWA.
  3. Right click the MSExchange OWA key and click New > DWord (32-bit).
  4. The DWORD value name is ChangeExpiredPasswordEnabled and set the value to 1.
    Note: The values accepted are 1 (or any non-zero value) for “Enabled” or 0 or blank / not present for “Disabled”
  5. After you configure this DWORD value, you must reset IIS. The recommended method to reset IIS is to use IISReset /noforce from a command prompt.

NOTE : User can’t use a User Principal Name (UPN) (eg: myname@domain.com) in the Domain\user name field in the Change Password window like below. It should be domain\myname

Once you done with it, click submit…make sure that your new password should match with the domain password policy.

December 14, 2010 Posted by | Active Directory, Exchange Server 2007, Exchange server 2010, Microsoft, Office, Office 2010, Outlook, OWA, Software | , | Leave a comment

%d bloggers like this: