Posts RSS Comments RSS 287 Posts and 68 Comments till now

Archive for the 'Exchange' Category

Help, Outlook has blocked my attachments

Most of us that have worked with Outlook for some time have come across this feature.  You try to send a file to a colleague and Outlook blocks and displays a nice message for you:

Outlook blocked access to the following potentially unsafe attachments: []

Of course the kneejerk reaction is to just rename the extension and resend the email.  While this works the majority of the time, it requires extra steps, time and some forethought before sending the email (while increasing your mailbox size).  A more permanent solution (albeit more dangerous) is to modify the Outlook policy itself either through a registry edit or using a GPO.

Other and more preferred options include:

  1. Use a file share or FTP site to save and access the attachment.  This is a Messaging administrator’s dream as it takes the burden off the Exchange servers and places it solely onto the file server.  While message storage is usually at a premium, file share storage can be much cheaper.
  2. Use a file compression utility to change the file name extension.  This works great and often saves valuable mailbox space in the process.  Two birds with one stone.

Searching the Internet on this topic brings up many posts (this is not an new topic), and while most seem to be focused solely on how to modify the behavior at the client level, I’ve included some links that the administrator can utilize to adjust the attachment filtering behavior at the server level.
 

Background

For more information on Outlook’s attachment filtering behavior along with a table of all those extensions that Outlook (aka: Microsoft) deems unsafe following this link.

Outlook divides attachments into three groups based on their file name extension or file type.  Outlook handles each group in a specific way.

Level 1

The unsafe category represents any file name extension that may have script or code associated with it. You cannot open any attachment that has an unsafe file name extension.

Level 2

Level 2 files are not unsafe. However, they do require more security than other attachments. When you receive a Level 2 attachment, Outlook prompts you to save the attachment to a disk. You cannot open the attachment in the e-mail message.

Other

When you try to open an attachment that has a file name extension other than those in the Level 1 or the Level 2 list, Outlook prompts you to either open the file directly or save it to a disk.You can turn off future prompts for that file name extension if you clear the Always ask before opening this type of file check box.
 

Customizing Attachment Filtering

So now that you understand a bit more about why let’s focus on the how.  There are a couple of options for customizing attachment filtering behavior.  While this article’s language is specific to understanding and modifying the behavior of Outlook, I’ve also included some options for modifying the attachment filtering features at the server level.

Configure the behavior at the server level

Configure the behavior at the client level

Exchange 2010 Deployment Assistant

Originally released in November of 2009, this tool was created based on customer feedback and helps streamline the deployment experience for Exchange customers whishing to upgrade or deploy a new installation of Exchange 2010.

Review the MS Exchange Team’s for more information…

Overview

Microsoft Exchange Server 2010 introduces the Exchange Deployment Assistant or ExDeploy, a new Web-based tool that can help you with your Exchange deployment. ExDeploy asks you a few questions about your current environment and then generates a custom checklist and procedures that help simplify your deployment.

You can use ExDeploy for the following scenarios:

  • Upgrade from Exchange Server 2003
  • Upgrade from Exchange 2007
  • Upgrade from mixed Exchange 2003 and Exchange Server 2007
  • New installation of Exchange 2010

To access ExDeploy, see Exchange Server 2010 Deployment Assistant.

Cisco Unity support update for Exchange 2010

Special thanks to fellow colleague and Exchange MVP Dustin Smith for sharing…

As you know, Exchange 2010 became generally available last November.  Unfortunately, the GA version had several issues which prevented Unity Unified Messaging interoperability. Cisco and Microsoft together have identified these issues and as of mid-December Microsoft has delivered an updated version of MAPI addressing the primary issues. Cisco is now working aggressively to validate the new MAPI version as well as make the necessary changes in Unity to support Exchange 2010 as follows:

Unity 7.X – March 31, 2010

Unity 5.X – May 31, 2010

Unity 8.X – June 30, 2010

We urge Unity 4.X Unified Messaging customers who plan to upgrade to Exchange 2010 to first upgrade to Unity 7.X once the ES is available in preparation for their upgrade to Exchange 2010.

As for Meeting Place, unfortunately planned support for Office (Outlook) 2010 has been pushed back to MP 8.5, which is not even officially announced at this point.  It’s possible this could be supported in a later version of 8.0 once that has been released, but for 6.0 and 7.0 there is nothing planned.

Customers should ultimately be working with their Cisco representative if they are considering Exchange 2010 soon, but this will at least provide some ideas when Unity support is expected.

How to determine what version of Exchange you have installed

Step 1

Get the version, build and service pack level of Exchange.

Step 2

Review this link for a complete limiting of build numbers and release dates for Exchange.

 

To get detailed information on Exchange 2007 platforms, editions and versions including Rollup information follow this link…

OCS comes to the iPhone

Came across this hiding in the Apps on the iPhone this afternoon.  Not written by Microsoft or Apple but by a company called Modality.

Few tidbits…

  • The application uses Communicator Web Access (CWA) and not the Access Edge server.  So this means you’ll need to have CWA deployed externally to get this app to work outside your network.
  • It cost $9.99

Click here fore more information from Modality…

Connect your BlackBerry phone directly to Exchange

Came across an interesting application by AstraSync forwarded to me by a colleague.  At $49 a year per user this seems like a great bargain if it works as advertised.  Unfortunately I don’t have a BlackBerry to try out the software.

Highlights:
  • Bi-directional over the air synchronization of email, calendar and contacts
  • Works with MS Exchange, Fusion, CommuniGate Pro, Zimbra, FirstClass and Kerio
  • Download over the air
  • Runs silently in the background on the BlackBerry Smartphone
  • Users can select the data they wish to synchronize
  • ActiveSync protocol licensed from Microsoft
  • Synchronizes over Wi-Fi or the cellular network
  • Volume pricing available
  • No Blackberry Enterprise Server required
  • FREE 7 day trial!!

Read about it and try it for yourself…

Share your experience if you decide to try it out.

Exchange AD Schema Changes – June 2009

This download includes the Active Directory Schema Changes Reference, which provides information about the changes that Microsoft Exchange Server makes to the Active Directory schema when it is installed. The Active Directory Schema Changes Reference includes changes made to Microsoft Exchange Server 2010, Exchange Server 2007 SP1, Exchange Server 2007, and Exchange Server 2003.

Click here to download…

UPDATE: Exchange 2007 SP1 Rollup 8

This one addresses a long outstanding issue with running Exchange 2007 SP1 on Windows Server 2008.

 

Click here to get more information on installing Exchange 2007 SP1 on Windows 2008…

 

Excerpt from the MS Exchange Team:

  1. KB 969690 – We have fixed the bug introduced in Update Rollup 7 which caused the sender of the Delivery Status Notification (DSN) to be unresolved.
  2. Disable kernel mode authentication in Windows Server 2008 for CAS servers – As documented here, it was required to manually take the additional step to configure the CAS servers running Windows Server 2008 to disable kernel mode authentication. Starting this rollup, the installer will configure this for you.
  3. X-Header promotion to named properties- Change to the way X-headers are promoted to named properties. More on this in Jason Nelson’s blog post Named Properties, X-Headers, and You.
  4. KB 961606 – We have fixed a bug where Outlook Web Access (OWA) users may find that the font size of plain text messages is extremely small on third-party Web browsers.

 

Click here to download the rollup…

Click here to read the MS Exchange Team’s post…

MOC 2007 R2 Hotfix Rollup – May 2009, v3.5.6907.22

If you are testing OCS with Exchange 2010 you’ll want to get this update.

This cumulative update fixes the following issues:

  • 971078 (http://support.microsoft.com/kb/971078/ ) An Automatic Update download is not initiated on a computer that is running Office Communicator 2007 R2 build 3.5.6907.9
  • 970057 (http://support.microsoft.com/kb/970057/ ) Exchange Connection error when you use Office Communicator 2007 R2 with your mailbox in Exchange Server 2010: "Communicator could not retrieve calendar or Out of Office information from Exchange Web Services"

UPDATE: I’m not sure why, but the link to KB970057 is not working.  To get some more insight on the Exchange 2010 fix see Aaron’s post on the subject.

 

Click here to read the KB article (971083)…

Click here to download the rollup…

Exchange 2007 SP2 coming in Q3 of 2009

Right on par with the release of Exchange 2010 as this is a pre-requisite to interoperability between Exchange 2007 and Exchange 2010.

Click here to read all about it…

Next »