rightgaq.blogg.se

This does not apply to per-mailbox restrictions. When setting per-server restrictions it is very important to avoid restricting clients with version numbers 6.y.z as Exchange Server makes use of MAPI for server-side component connections and uses MAPI versions within the 6.y.z range (with the version number potentially varying by Exchange component and patch level). For example, the version number for Outlook 2003 RTM becomes 11.5604.0. When specifying MAPI versions to be blocked you must use the format x.y.z. The MAPI client version numbers listed in Table 1, and those in the results of the Get-LogonStatistics cmdlet, are in the format x.0.y.z. Table 1 – Emsmdb32.dll version by Office release Get-LogonStatistics accepts a mailbox, a mailbox database, or a server name as input and returns statistics including user name, logon time, last access time, client name, and client version.įor example, to list the client versions used to access a single mailbox, the command is: In Exchange 2007 client version information is retrieved using the Get-LogonStatistics cmdlet. With this information you can tell which clients need to be upgraded to a newer version before blocking is implemented, or simply which clients will no longer be able to connect after it is implemented. Determining Which Client Versions are in useīefore implementing client version blocking it’s a good idea to know versions are in use. In Exchange 2007 MAPI client blocking can be implemented on a per-server basis using a registry change, or on a per-mailbox basis using the Exchange Command Shell.Īdditionally, Microsoft recommends implementing Outlook client blocking as a best practice, and if you run the Exchange Best Practices Analyzer against a server which does not have client blocking enabled it will suggest that you configure it.

You may also have corporate policy which dictates that a particular version or versions of Outlook are used.įortunately Exchange has the ability to restrict which versions of Outlook can connect by blocking MAPI client versions, a feature which was introduced in Exchange 2000 Service Pack 1. It’s not always desirable to let any version of Outlook connect to Exchange Server as you may require your clients to utilize a specific feature set, such as Messaging Records Management, or to have certain security fixes. Outlook has been around for a long time, and there are many versions with different features and varying levels of security fixes. Restricting Outlook Client Versions in Exchange 2007 - Simple Talk Skip to content