Exchange Team news

System Center Operation Manager

samedi 30 avril 2011

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 :

mercredi 27 avril 2011

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



vendredi 22 avril 2011

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

Coexistance et Migration vers Exchange Server 2010

Author : http://unifiedit.wordpress.com/category/1-exchange-2010/coexistence-2010/

l’installation d’Exchange Server 2010 et la configuration lors de l’intégration dans une organisation Exchange Server 2003 ou 2007 et la procédure de migration en français.

jeudi 21 avril 2011

Windows Network Load Balancing Ports configuration

Windows Network Load Balancing array can load-balance HTTPS (TCP443), IMAP4 (TCP143 and TCP993), POP3 (TCP110 and TCP995), RPC Endpoint Mapper (TCP135), Address Book service (TCP7576), and RPC Client Access (TCP7575).

Exchange 2007 error; IIS directory entry couldn't be created


When upgrading to Exchange 2010, do you have E 2007 Servers in your organization.
If Yes then

The security group “Exchange Trusted Subsystem” as member of Local Administrators group on an ALL Exchange Server 2007 boxes.

Exchange 2010 Antivirus Recommendations

If you are deploying file-level scanners on Exchange 2010 servers, make sure that the appropriate exclusions, such as directory exclusions, process exclusions, and file name extension exclusions, are in place for both scheduled and real-time scanning. This section describes directory exclusions, process exclusions, and file name extension exclusions for each server or server role.

Directory Exclusions

You must exclude specific directories for each Exchange server or server role on which you run a file-level antivirus scanner. This section describes the directories that you should exclude from file-level scanning for each server or server role.

Mailbox server role

· Exchange databases, checkpoint files, and log files across all storage groups. By default, these are located in sub-folders under the %Program Files%\Microsoft\Exchange Server\v14\Mailbox folder. You can obtain the directory location by running the following commands in the Exchange Management Shell:

· To determine the location of a mailbox database and log folders, run the following command: Get-MailboxDatabase -server | fl *path*

· To determine the location of a public folder database, run the following command: Get-PublicFolderDatabase -server | fl *path*

· Database content indexes. By default, these are located in mailbox database sub-folders under the %Program Files%\Microsoft\Exchange Server\v14\Mailbox folder.

· General log files, such as message tracking log files. These files are located in subfolders under the %Program Files%\Microsoft\Exchange Server\v14\TransportRoles\Logs folder and %Program Files%\Microsoft\Exchange Server\v14\Logging folder. To determine the log paths being used, run the following command in the Exchange Management Shell: Get-MailboxServer | fl *path*

· The Offline Address Book files that are located in subfolders under the %Program Files%\Microsoft\Exchange Server\v14\ExchangeOAB folder

· IIS system files in the %SystemRoot%\System32\Inetsrv folder

· The temporary folder that is used with offline maintenance utilities, such as Eseutil.exe. By default, this folder is the location where the .exe file is run from. However, you can configure where you perform the operation from when you run the utility.

· The temporary folders that are used to perform conversions:

· Content conversions are performed in the server’s TMP folder.

· OLE conversions are performed in %Program Files%\Microsoft\Exchange Server\v14\Working\OleConvertor folder.

· The Mailbox database temporary folder: %Program Files%\Microsoft\Exchange Server\v14\Mailbox\MDBTEMP

· Any Exchange-aware antivirus program folders


DAG Member Mailbox server

All the items listed in the Mailbox server role list, and the following:

· The file share witness. This is located on another server in the environment, typically a Hub transport server.

Hub Transport server role

· General log files, for example, message tracking. These files are located in subfolders under the %Program Files%\Microsoft\Exchange Server\v14\TransportRoles\Logs folder. To determine the log paths being used, run the following command in the Exchange Management Shell: Get-TransportServer | fl *logpath*,*tracingpath*

· The message folders that are located under the %Program Files%\Microsoft\Exchange Server\v14\TransportRoles folder. To determine the paths being used, run the following command in the Exchange Management Shell: Get-TransportServer | fl *dir*path*

· The transport server role queue database, checkpoint, and log files that are located in the %Program Files%\Microsoft\Exchange Server\v14\TransportRoles\Data\Queue folder.

· The transport server role Sender Reputation database, checkpoint, and log files that are located in the %Program Files%\Microsoft\Exchange Server\v14\TransportRoles\Data\SenderReputation folder

· The transport server role IP filter database, checkpoint, and log files that are located in the %Program Files%\Microsoft\Exchange Server\v14\TransportRoles\Data\IpFilter folder

· The temporary folders that are used to perform conversions:

· Content conversions are performed in the server’s TMP folder.

· OLE conversions are performed in %Program Files%\Microsoft\Exchange Server\v14\Working\OleConvertor folder.

· Any Exchange-aware antivirus program folders


Edge Transport server role

· The Active Directory Application Mode (ADAM) database and log files that are located in the %Program Files%\Microsoft\Exchange Server\v14\TransportRoles\Data\Adam folder.

· General log files, for example message tracking. These files are located in subfolders under the %Program Files%\Microsoft\Exchange Server\v14\TransportRoles\Logs folder. To determine the log paths being used, run the following command in the Exchange Management Shell: Get-TransportServer | fl *logpath*,*tracingpath*

· The message folders that are located under the %Program Files%\Microsoft\Exchange Server\v14\TransportRoles folder. To determine the log paths being used, run the following command in the Exchange Management Shell: Get-TransportServer | fl *dir*path*

· The transport server role queue database, checkpoint, and log files that are located in the %Program Files%\Microsoft\Exchange Server\v14\TransportRoles\Data\Queue folder.

· The transport server role Sender Reputation database, checkpoint, and log files that are located in the %Program Files%\Microsoft\Exchange Server\v14\TransportRoles\Data\SenderReputation folder

· The transport server role IP filter database, checkpoint, and log files that are located in the %Program Files%\Microsoft\Exchange Server\v14\TransportRoles\Data\IpFilter folder

· The temporary folders that are used to perform conversions:

· Content conversions are performed in the server’s TMP folder.

· OLE conversions are performed in %Program Files%\Microsoft\Exchange Server\v14\Working\OleConvertor folder.

· Any Exchange-aware antivirus program folders

Client Access server role

· Exclude the IIS compression directory from the antivirus software's scan list
For more information, see the Microsoft Knowledge Base article
KB817422,

· IIS system files in the %SystemRoot%\System32\Inetsrv folder

· The Internet-related files that are stored in the sub-folders of the %Program Files%\Microsoft\Exchange Server\v14\ClientAccess folder

· The temporary folder that is used to perform content conversion. By default, this is the server’s TMP folder.

Unified Messaging server role

· The grammar files that are stored in the subfolders in the %Program Files%\Microsoft\Exchange Server\v14\UnifiedMessaging\grammars folder

· The voice prompts that are stored in the subfolders in the %Program Files%\Microsoft\Exchange Server\v14\UnifiedMessaging\Prompts folder

· The voicemail files that are stored in the %Program Files%\Microsoft\Exchange Server\v14\UnifiedMessaging\voicemail folder