MapiExceptionNoSupport : 0x80040102 | Une erreur irrécupérable MapiExceptionNoSupport s’est produite

Le déplacement des boites aux lettres d'Exchange 2003 vers Exchange 2010 produit l'erreur (MapiExceptionNoSupport : 0x80040102 | Une erreur irrécupérable MapiExceptionNoSupport s’est produite);
Solution : Utiliser PFDAVAdmin sur le serveur Exchange 2003, se connecter sur les boites aux lettres et Fixer les DACL.
Source: http://runebelune.blogspot.com/2010/11/mapiexceptionnosupport.html

Internet Explorer 9(IE9) and Forefront TMG 2010

After install IE9, Microsoft Forefront Thread Management Gateway management tools cannot work anymore, it gives error message like “member not found”, “refresh failed”.

* Open "C:\Program Files\Microsoft Forefront Threat Management Gateway\UI_HTMLs\TabsHandler\TabsHandler.htc"
* Search for the 3 lines which contain "paddingTop", and remark-out each of them by adding "//" in the begining.
Example: Change the line:
m_aPages [niPage].m_tdMain.style.paddingTop = ((m_nBoostUp < 0) ? -m_nBoostUp : 0) ;
into:
// m_aPages [niPage].m_tdMain.style.paddingTop = ((m_nBoostUp < 0) ? -m_nBoostUp : 0) ;
* Save the file, and re-open TMG management console.

Source : http://blogs.technet.com/b/asiasupp/archive/2011/04/29/internet-explorer-9-ie9-and-forefront-tmg-2010.aspx

Ouvrir une instance SQL à distance via un firewall

La connexion à l'instance ne s'effectue pas
1. L'instance est configuré pour une connexion sur un port dynamique; vérifier que l'instance n'utilise pas un port dynamique (#0)

Dans la console de SQL enterprise Manager spécifier :

Redirecting OWA URLs in Exchange 2010 / Redirection de OWA dans IIS7 et Exchange 2010

Souvent on souhaite se connecter sur le serveur web avec : http://myserver.mydomain.ext et on veut être rederiger vers : http://myserver.mydomain.ext/owa

Etape par étape / Step by Step:
Source : http://briandesmond.com/blog/redirecting-owa-urls-in-exchange-2010/
Ou/Or : http://blog.xiquest.com/2009/12/exchange-2010-simplify-owa-url/

N'oubliez pas de supprimer la redirection sur les repertoires virtuel suivant :

• Autodiscover
• ecp
• EWS
• Microsoft-Server-ActiveSync
• owa
• Rpc
• RpcWithCert

Configure Anonymous Relay to External Domains/ Autoriser le SMTP anonyme sous Exchange 2010

Exchange Relaying to external domains
Source : http://www.lazynetworkadmin.com/knowledgebase-mainmenu-6/2-windows/149-exchange-2010-configure-anonymous-relay-to-external-domains

Autoriser le SMTP anonyme sous Exchange 2010

Par défaut Exchange 2007 & 2010 ne permettent pas l’émission de mail via SMTP de façon anonyme. Et heureusement car ceci permettrait de disposer d’un relais ouvert !

step by step / étape par étape
Source : http://gmergit.blogspot.com/2010/02/autoriser-le-smtp-anonyme-sous-exchange.html

Partition alignment and NTFS Allocation unit size

Below is a table of recommendations for use with Exchange.

Best practice: 64 KB for both .edb and log file volumes.

Description	Recommended Value
Storage Track Boundary	64K or greater. (1MB recommended)
NTFS allocation unit/cluster size	64KB (DB and Log Drives)
RAID Stripe size	256KB or greater. Check with your storage vendor for best practices

Source : http://blogs.technet.com/b/mikelag/archive/2011/02/09/how-fragmentation-on-incorrectly-formatted-ntfs-volumes-affects-exchange.aspx

Plus : http://technet.microsoft.com/fr-fr/library/ee832792.aspx

Transitioning Client Access to Exchange Server 2010

Article complet sur la transition du CAS :
Source : http://blogs.technet.com/b/exchange/archive/2009/11/20/3408856.aspx

By now most of you have heard about the release of Exchange 2010. Those of you that are upgrading from Exchange 2003, Exchange 2007 or a mixture of the two, are probably curious about the client access upgrade strategy. To satisfy your curiosity, we are releasing a series of blog articles on the subject. The first in this series provides a summary of the steps that are required to introduce Exchange 2010 within your environment from a client access perspective. More detailed information about the upgrade process is discussed in TechNet and within the Deployment Assistant. The second and third parts in this series will discuss the end user experience for OWA and ActiveSync, respectively. Look for those in upcoming weeks.

Many of you have been asking how you can transition your existing Exchange environment to Exchange 2010 from a client access perspective. For most of you, this will also mean coexisting with legacy Exchange and Exchange 2010 for a period of time. This post will hopefully answer these questions by breaking down your transition into two scenarios:

1. Transitioning an Exchange 2003 environment to Exchange 2010.
2. Transitioning an Exchange 2007 (that may or may not contain Exchange 2003 mailbox servers) environment to Exchange 2010.

The underlying goal here is to move your primary namespace, mail.contoso.com and autodiscover.contoso.com, over to Exchange 2010 and introduce a new namespace for legacy access, legacy.contoso.com and associate it with your legacy Exchange client access infrastructure. Users will continue to use mail.contoso.com as their access point into the organization for messaging services. While Exchange 2003/2007 end users will see the legacy.contoso.com namespace in their browser address bar, ActiveSync settings, and Test Auto-Configuration output within Outlook, they only need to use the mail.contoso.com namespace as their primary entry point into the organization; in addition, IT should continue directing customers to utilize the mail.contoso.com namespace for all external connectivity mechanisms