Ok, now this is very cool. Courtesy of Bharat Suneja of the MS Exchange team this article walks you through the steps of adding photos to your GAL.
The process is broken down into three steps:
- A minor schema change
- Loading the picture into Active Directory
- Updating the Offline Address Book
Instructions: Click here to read the original article…
Other Useful Links…
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:
- 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.
- 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.
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…
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.
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.