All about Exchange Server, HyperV, System Center

My last reading an amazing book : Active Directory with PowerShell

2015-05-16T13:33:00.001+01:00

Configure and manage Active Directory using PowerShell in an efficient and smart way
A nice book and nice scripts and tips,
Chap1: AD modules, Quest
Chap2: Managing Users and computer objects
Chap3: AD groups and memberships
Chap4: Group policies
Chap5: Domains, OU, sites and Subnets
Chap6: Advanced AD operations
Chap7: DFS-N and DF-R
Chap8: AD DNS
Chap9: Scripts and ressources

Go ahead get it at : http://bit.ly/1F7ooqX

2013-09-05T11:09:00.002+01:00

PowerShell 3.0 Advanced Administration | by Sherif Talaat, Haijun Fu

http://www.packtpub.com/powershell-3-0-advanced-administration-handbook/book

Good book for enterprise IT administrators, IT professionals, and all kinds of PowerShell users. It gives you a comprehensive view on the v3.0 of Windows PowerShell, which is more powerful in functionalities and more user-friendly than v2 in both console and ISE.

Step-by-step guide rich with real-world script examples, screenshots, and best practice
Understand the concept of Windows PowerShell 3.0
Learn the advanced techniques for a professional PowerShell scripting.
Explore the secret of building custom PowerShell snap-ins and modules.
Take advantage of PowerShell capabilities with other technologies for better administration skills.

The book includes sample scripts and files that go along with the book.

Chapter 1: Getting Started with PowerShell
Chapter 2: Developing Snap-ins for PowerShell
Chapter 3: Using PowerShell Remoting
Chapter 4: Extending Windows PowerShell
Chapter 5: Managing Core Infrastructure with PowerShell
Chapter 6: Managing Active Directory with PowerShell
Chapter 7: Managing the Server with PowerShell
Chapter 8: Managing Unified Communication Environments
Chapter 9: Managing Collaboration and Data Platforms
with PowerShell
Chapter 10: Managing Microsoft Desktop Virtualization
with PowerShell
Chapter 11: Managing Microsoft Cloud Platform with PowerShell
Chapter 12: Integrating Windows PowerShell and System
Center Orchestrator

Gestion des boites aux lettres deconectées via PowerShell / Managing Disconnected Exchange Mailboxes with PowerShell

2011-06-13T14:27:00.001+01:00

Source :

Gestion des boites aux lettres deconectées via PowerShell

Managing Disconnected Exchange Mailboxes with PowerShell

by Mike Pfeiffer on June 16, 2010

Source : http://www.mikepfeiffer.net/2010/06/managing-disconnected-exchange-mailboxes-with-powershell/

Having worked with Exchange 2007/2010 and PowerShell for some time now, I've developed a number of functions that I use to simplify particular "hard to type" commands. This has made for some good scripting exercises, but more importantly, it has served as a great time saver when performing certain routine tasks. In this post, I am going to share some code that I use to manage disconnected Exchange mailboxes.

Finding Disconnected Mailboxes

The first function is called Get-DisconnectedMailbox and the name is pretty much self explanitory. This function will give you a list of all disconnected mailboxes on each of your mailbox servers. Take a look at the following code:

function Get-DisconnectedMailbox {     [CmdletBinding()]     param(         [Parameter(Position=0, Mandatory=$false)]         [System.String]         $Name = '*'     )      $mailboxes = Get-MailboxServer     $mailboxes | %{         $disconn = Get-Mailboxstatistics -Server $_.name | ?{ $_.DisconnectDate -ne $null }         $disconn | ?{$_.displayname -like $Name} |             Select DisplayName,             @{n="StoreMailboxIdentity";e={$_.MailboxGuid}},             Database     } }

Note: If you've recently deleted a mailbox, but it's not showing up when running Get-DisconnectedMailbox, you may need to force Exchange to recognize this by running the Clean-MailboxDatabase cmdlet.

Running the function without specifying a user name will return all disconnected mailboxes:

To find a particular disconnected mailbox, just type the function name, followed by the users display name. For example, to determine the disconnected mailbox information for a user named Blanca Jacobs you could would run this command:

Get-DisconnectedMailbox "Blanca Jacobs"

The name parameter will accept wildcards. For example: Get-DisconnectedMailbox M* would give you all disconnected mailboxes starting with the letter "M".

Purging Disconnected Mailboxes

You purge mailboxes using the Remove-Mailbox cmdlet, specifying the StoreMailboxIdentity and Database for the disconnected mailbox in question. For a good example of this, check out Nitin Gupta's post on removing disconnected mailboxes.

In an effort to simplify the purging of disconnected mailboxes, I wrote the Remove-DisconnectedMailbox function that is designed to work with Get-DisconnectedMailbox. Here is the code:

function Remove-DisconnectedMailbox {     [CmdletBinding(SupportsShouldProcess=$true)]     param(         [Parameter(Position=0, ValueFromPipelineByPropertyName=$true, Mandatory=$true)]         [System.String]         $StoreMailboxIdentity,         [Parameter(Position=1, ValueFromPipelineByPropertyName=$true, Mandatory=$true)]         [System.String]         $Database         )      process {         Remove-Mailbox @PSBoundParameters     } }

This allows you to easily purge all disconnected mailboxes returned from Get-DisconnectedMailbox by piping the output to Remove-DisconnectedMailbox. You can also purge one disconnected mailbox at time, as shown here:

Get-DisconnectedMailbox "Bill Jones" | Remove-DisconnectedMailbox -Confirm:$false

Notice the use of -Confirm:$false in the above command. Since this is an advanced function, we can take advantage of ShouldProcess, which allows functions to use common cmdlet parameters such as -Confirm and -WhatIf.

If you look at the code closely, you'll notice that this function is essentially a specialized wrapper for the Remove-Mailbox cmdlet. I use splatting with the $PSBoundParameters variable to automatically bind all of the function parameter values to Remove-Mailbox.

Connecting Disconnected Mailboxes

Of course, you can also use the Get-DisconnectedMailbox cmdlet in conjunction with the built-in Connect-Mailbox cmdlet to reconnect a mailbox to a user account.

For example, here's how you would connect a disconnected mailbox for a user named Bradford Boyer:

Get-DisconnectedMailbox "Bradford Boyer" | %{Connect-Mailbox -Identity $_.StoreMailboxIdentity -Database 'DB1' -User 'contoso\bboyer' -Alias 'bboyer'}

As you can see in the above example, you provide the StoreMailboxIdentity, Database, User and Alias to the Connect-Mailbox cmdlet. If you'd like to do this manually, you can determine the StoreMailboxIdentity of the disconnected mailbox using the Get-MailboxStatistics cmdlet.

Understanding Memory Configurations and Exchange Performance

2011-06-08T10:39:00.000+01:00

Understanding Memory Configurations and Exchange Performance
Source : http://technet.microsoft.com/en-us/library/dd346700.aspx

Memory configurations for Exchange 2010 servers based on installed server roles

Exchange 2010 server role	Minimum supported	Recommended maximum
Edge Transport	4 GB	1 GB per core (4 GB minimum)
Hub Transport	4 GB	1 GB per core (4 GB minimum)
Client Access	4 GB	2 GB per core (8 GB minimum)
Unified Messaging	4 GB	2 GB per core (4 GB minimum)
Mailbox	4 GB	4 GB plus 3-30 MB additional memory per mailbox: The total required memory is based on the user profile and database cache size. For more information about how to determine the total required memory, see Understanding the Mailbox Database Cache.
Client Access/Hub Transport combined role (Client Access and Hub Transport server roles running on the same physical server)	4 GB	2 GB per core (8 GB minimum)
Multiple roles (combinations of Hub Transport, Client Access, and Mailbox server roles)	8 GB	4 GB plus 3-30 MB additional memory per mailbox: The total required memory is based on the user profile and database cache size. For more information about how to determine the total required memory, see Understanding the Mailbox Database Cache.

Edge Transport and Hub Transport Server Roles

The Edge Transport and Hub Transport server roles don't require substantial quantities of memory to perform well in optimal conditions. Generally, 1 GB of RAM per processor core (4 GB minimum total) is sufficient to handle all but the most demanding loads. Most deployments will be optimally configured with the recommended memory configuration of 1 GB per processor core (4 GB minimum total).

Client Access Server Role

In general, memory utilization on Client Access servers has a linear relationship with the number of client connections and the transaction rate. Based on the current recommendations of 2 GB per core processor and memory configurations, a Client Access server will be balanced in terms of memory and processor utilization, and it will become processor-bound at approximately the same time it becomes memory- bound.

These recommendations are based on the Exchange 2010 feature, RPC Client Access. This feature requires a larger memory and processor configuration to manage the increased loads placed on the Client Access server role.

Exchange Server 2010 Design and Architecture at Microsoft

2011-06-08T10:38:00.000+01:00

Exchange Server 2010 Design and Architecture at Microsoft : http://technet.microsoft.com/en-us/library/ff829232.aspx

Les mauvaises conceptions de la Haute Disponibilité sur Exchange 2010/Exchange 2010 High Availability Misconceptions Addressed

2011-06-08T10:28:00.003+01:00

Source : http://blogs.technet.com/b/exchange/archive/2011/05/31/exchange-2010-high-availability-misconceptions-addressed.aspx

The recommended maximum number of processor cores we state that you should have for a Client Access or Hub Transport server. It’s 12. Memory guidance for Client Access servers is 2 GB per core and for Hub Transport it is 1 GB per core. Thus, if you have a 12-core Client Access server, you’d install 24 GB of memory, and if you had a 12-core Hub Transport server, you would install 12 GB of memory.

Exchange 2010 High Availability and Site Resilience Terminology

But first let’s start with some terminology to make sure everyone understands the components, settings and concepts I’ll be discussing.

Term	Description	How Configured
Activation	The process of making a passive database copy into an active database copy.	Move-ActiveMailboxDatabase cmdlet
Activation Suspended or Blocked	The process of suspending or blocking a single database or an entire server from automatic activation.	Suspend-MailboxDatabaseCopy or Set-MailboxServer cmdlets
Active Manager	An internal Exchange component which runs inside the Microsoft Exchange Replication service that is responsible for failure monitoring and corrective action within a DAG.	N/A
Alternate Witness Directory	An optional property of a DAG that specifies the name of the directory that is shared on the Alternate Witness Server for quorum purposes.	Set-DatabaseAvailabilityGroup cmdlet or Exchange Management Console (EMC)
Alternate Witness Server	An optional property of a DAG that specifies the witness server that will be used by DAG after you have performed a datacenter switchover.	Set-DatabaseAvailabilityGroup cmdlet or EMC
Attempt Copy Last Logs (ACLL)	A process performed during Best Copy Selection in which the system attempts to copy from the original active database copy any log files missing by the passive copy selected for activation.	N/A
AutoDatabaseMountDial	Property setting of a Mailbox server that determines whether a passive database copy will automatically mount as the new active copy, based on the number of log files missing by the copy being mounted.	Set-MailboxServer cmdlet
Best Copy Selection (BCS)	A process performed by Active Manager to determine the best passive mailbox database copy to activate either in response to a failure affecting the active mailbox database copy, or as a result of an administrator performing a targetless switchover.	N/A
Continuous Replication Block Mode	A form of continuous replication that replicates blocks of ESE transaction data between the ESE log buffers on the active mailbox database copy to replication log buffers on one or more passive mailbox databases copies.	N/A – not configurable The system automatically switches between file mode and block mode based on the passive copy’s ability to keep up with continuous replication.
Continuous Replication File Mode	A form of continuous replication that replicates closed transaction log files from the active mailbox database copy to one or more passive mailbox database copies.	N/A – not configurable
Datacenter	In Exchange, typically this refers to an Active Directory site; however, it can also refer to a physical site. In the context of this blog post, datacenter equals Active Directory site.	N/A
Datacenter Activation Coordination (DAC) Mode	A property of the DAG setting that, when enabled, forces starting DAG members to acquire permission in order to mount databases.	Set-DatabaseAvailabilityGroup cmdlet
Datacenter Activation Coordination Protocol (DACP)	A bit in memory (0 or 1) that is used by DAG members in DAC mode. A value of 0 indicates the DAG member cannot mount databases; a value of 1 indicates the DAG member can mount active databases that it currently hosts.	N/A – Automatically used when the DAG is configured for DAC mode.
Datacenter Switchover	The manual process performed to activate the Exchange components of a standby datacenter and restore Exchange service and data after failure of a primary datacenter.	Process documented in Datacenter Switchovers.
Failover	The automatic process performed by the system in response to a failure affecting one or more active mailbox database copies.	N/A – Happens automatically by the system; although you can activation-block or suspend individual mailbox database copies or an entire DAG member.
File Share Witness	A cluster-managed resource that is created and use when the cluster uses the node and file share majority quorum model.	N/A – Automatically created and destroyed by Exchange, as needed, based on the number of DAG members.
Incremental Resync	A built-in process that corrects certain forms of divergence that occur between mailbox database copies in a DAG (typically between a new active copy and the previous active copy).	N/A – Happens automatically by the system
Lossy Failover	A database failover condition in which the passive copy being activated is mounted with one or more log files missing.	Partially controlled via AutoDatabaseMountDial
Primary Active Manager (PAM)	An Active Manager role held by a single DAG member at any given time that is responsible for responding to failures an initiating corrective action in the form of a database or server failover.	N/A – The PAM role is automatically held by the DAG member that owns the cluster’s core resource group.
Quorum	Has a dual meaning: Refers to the consensus model used by members of a cluster to ensure consistency within the cluster. Exchange uses two of the four cluster quorum models: Node Majority (for DAGs with an odd number of members) Node and File Share Majority (for DAGs with even number of members) Refers to the data (e.g., “quorum data”) shared by the cluster members that is used to maintain quorum	N/A – Automatically configured by Exchange, as needed, based on the number of DAG members.
RPCClientAccessServer	A property of a Mailbox database that specifies the Client Access server or Client Access server array through which MAPI/RPC clients (Outlook 2003, Outlook 2007, Outlook 2010) access their mailboxes on that database.	Set-MailboxDatabase cmdlet
Site	Active Directory Site, which is defined as one or more fast, reliable and well-connected (< 10 ms latency) subnets.	N/A – Configured outside of Exchange by using Active Directory Sites and Services
Split Brain	A condition in which multiple cluster members believe they are authoritative for one or more common resources.	N/A
Standby Active Manager (SAM)	An Active Manager role held by all DAG members that do not hold the PAM role that is responsible for monitoring for local failures and responding to queries from CAS and Hub as to the location of the user’s mailbox database.	N/A – The SAM role is automatically held by the DAG members that do not own the cluster’s core resource group.
StartedMailboxServers	A list of DAG members that are currently operational and functional.	Automatically added to list during normal operations Manually added to list as part of re-activation of primary datacenter using Start-DatabaseAvailabilityGroup cmdlet
StoppedMailboxServers	A list of DAG members that have been marked as non-operational or non-functional.	Automatically added to list during normal operations Manually added to list as part of activation of second datacenter using Stop-DatabaseAvailabilityGroup cmdlet
Switchover	In the context of a single database, it is the manual process used to move the active mailbox database copy to another server. In the context of an entire server, it is the manual process used to move all active mailbox database copies from one server to one or more other servers.	Move-ActiveMailboxDatabase cmdlet
Targetless Switchover	A switchover process in which the administrator does not specify which passive mailbox database copy should become active, but instead allows Active Manager’s BCS process to choose the best copy to activate.	Move-ActiveMailboxDatabase cmdlet (specifically without using the TargetServer parameter)
Transport Dumpster	A feature of the Hub Transport role that retains copies of messages sent to users on replicated mailbox databases in a DAG so that messages can be recovered by the system in the event of a lossy failover of the user’s database.	Set-TransportConfig cmdlet or EMC
Witness Directory	A required property of every DAG that specifies the name of the directory that is shared on the Witness Server for quorum purposes.	Set-DatabaseAvailabilityGroup cmdlet or EMC
Witness Server	A required property of every DAG that specifies the server external to the DAG that should be used as a participant in quorum for the DAG’s underlying cluster when the DAG contains even number of members.	Set-DatabaseAvailabilityGroup cmdlet or EMC

Exchange 2010 Service Pack 2

2011-05-18T08:15:00.000+01:00

source : http://blogs.technet.com/b/exchange/archive/2011/05/17/announcing-exchange-2010-service-pack-2.aspx

SP2, the following new features and capabilities will be included:

Outlook Web App (OWA) Mini: A browse-only version of OWA designed for low bandwidth and resolution devices. Based on the existing Exchange 2010 SP1 OWA infrastructure, this feature provides a simple text based interface to navigate the user’s mailbox and access to the global address list from a plurality of mobile devices.
Cross-Site Silent Redirection for Outlook Web App: With Service Pack 2, you will have the ability to enable silent redirection when CAS must redirect an OWA request to CAS infrastructure located in another Active Directory site. Silent redirection can also provide a single sign-on experience when Forms-Based Authentication is used.
Hybrid Configuration Wizard: Organizations can choose to deploy a hybrid scenario where some mailboxes are on-premises and some are in Exchange Online with Microsoft Office 365. Hybrid deployments may be needed for migrations taking place over weeks, months or indefinite timeframes. This wizard helps simplify the configuration of Exchange sharing features, like: calendar and free/busy sharing, secure mailflow, mailbox moves, as well as online archive.
Address Book Policies: Allows organizations to segment their address books into smaller scoped subsets of users providing a more refined user experience than the previous manual configuration approach. We also blogged about this new feature recently in GAL Segmentation, Exchange Server 2010 and Address Book Policies.
Customer Requested Fixes: All fixes contained within update rollups released prior to Service Pack 2 will also be contained within SP2. Details of our regular Exchange 2010 release rhythm can be found in Exchange 2010 Servicing.

In order to support these newly added features, there will be a requirement for customers to update their Active Directory schema. We’ve heard the feedback loud and clear from our customers on multiple occasions regarding delays that can be caused to deployment as a result of needing to update your schema and as such with the release of Exchange 2010 SP2 are communicating the required changes ahead of release in order to assist our customers with planning their upgrade path ahead of time.

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

2011-05-05T16:03:00.002+01:00

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

2011-05-02T15:29:00.000+01:00

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

2011-04-30T09:56:00.004+01:00

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

2011-04-27T11:24:00.003+01:00

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

2011-04-27T11:21:00.001+01:00

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

2011-04-27T08:12:00.001+01:00

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

2011-04-22T10:05:00.001+01:00

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:

Transitioning an Exchange 2003 environment to Exchange 2010.
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

2011-04-22T10:02:00.000+01:00

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.

Windows Network Load Balancing Ports configuration

2011-04-21T21:32:00.000+01:00

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

2011-04-21T21:25:00.001+01:00

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

2011-04-21T21:23:00.000+01:00

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

autodiscover, Create, mono-site and site affinity

2011-04-21T20:59:00.000+01:00

Create a new autodiscover virtual directory

1. From the Start menu, point to All Programs, point to Microsoft Exchange Server 2007 and launch Exchange Management Shell.

2. Run the following command: New-AutodiscoverVirtualDirectory -Websitename -BasicAuthentication:$true -WindowsAuthentication:$true

Note: Before you perform this procedure, confirm that the Autodiscover service virtual directory is not present under the Default Web Site node in the IIS console tree.

Configure autodicover in a mono-site

3. From the Start menu, point to All Programs, point to Microsoft Exchange Server 2007 and launch Exchange Management Shell.

4. Run the following command: Set-WebServicesVirtualDirectory -identity "CAS01\EWS (Default Web Site)" -externalurl https:///EWS/Exchange.asmx -BasicAuthentication:$True

Configure autodiscover to use site affinity

5. From the Start menu, point to All Programs, point to Microsoft Exchange Server 2007 and launch Exchange Management Shell.

Run the following command: Set-ClientAccessServer -Identity "" -AutodiscoverServiceInternalURI "https:///autodiscover/autodiscover.xml" AutodiscoverSiteScope ""

There is a bug in Exchange 2007 when you decide to designate a new server responsible for generating the offline address book (OAB).

2011-04-21T20:42:00.002+01:00

Move-OfflineAddressBook will give an error and fail if the target server doesn't already have the ExchangeOAB folder. This only occurs on Exchange 2007 to Exchange 2007 moves. To get around this, the Administrator needs to create a dummy OAB and build it, then move the desired OAB, delete the dummy OAB, and delete the dummy OAB files from the ExchangeOAB directory.

1 Procedure

1.1 Prepare Folder

Pre requisite	§ Use account with membership in the local Administrators group for the target server
Description	This procedure is used to create folder, configure share and sharing permission and set security permission folder to the new location
Procedure	Create folder step: 1. Open an Windows Explorer 2. Go to C:\Program Files\Microsoft\Exchange Server and create a new folder named ExchangeOAB Share folder and sharing permission step: 3. Right click on new folder ExchangeOAB and click Properties 4. Select Sharing tab 5. Check Share this folder option and verify share’s name. It must equal to ExchangeOAB. 6. Click on Permission button and set permission to : § COMPUTER\Administrators group as Full Control permission § DOMAIN\Exchange Servers group as Read permission § SYSTEM built-in group as Full Control permission 7. Click OK on Permissions for ExchangeOAB window when permissions are completed like figure as above 8. Click Apply on ExchangeOAB Properties window to validate sharing permission change Set security permission folder step: 9. Click on Security tab and click Advance button 10. Click Add button and type Exchange Servers and click on Check Name button. 11. Click OK and Permission Entry for ExchangeOAB window appears 12. Check the following options: § Verify that “This folder, subfolder and files” parameter is selected in Apply onto option § Check Allow for List Folder / Read Data option § Check Allow for Read Attributes option § Check Allow for Read Extended Attributes option § Check Allow for Read Permissions option 13. Click OK when all permissions are correctly sets. Advanced Security Settings for ExchangeOAB window appears, like figure as below. 14. Click Add button and type Exchange Servers and click on Check Name button. 15. Click OK and Permission Entry for ExchangeOAB window appears 16. In Apply onto option, select ““This folder and subfolders” parameter, like figure as below 17. Check Allow for the following permissions options § Check Allow for Traverse Folder / Execute File option § Check Allow for List Folder / Read Data option § Check Allow for Read Attributes option § Check Allow for Read Extended Attributes option § Check Allow for Read Permissions option 18. Click OK when all permissions are correctly sets. Advanced Security Settings for ExchangeOAB window appears, like figure as below. 19. Click OK and OK again to close all security windows
Check or Remark

1.2 Move OABGen

Pre requisite	§ Use account with Exchange Organization Administrator role § Folder to the new location must be completed (Share, Sharing permission and Security permissions)
Description	This procedure is used to designate a new server responsible for generating the offline address book (OAB).
Exchange Management Console	1. Open an Exchange Management Console and expand Organization Configuration and click on Mailbox 2. On Result pane click Offline Address Book tab and select the OAB who want to move. 3. In Action pane click Move action 4. Move Offline Address Book wizard appears. Click on Browse button to select designate mailbox server. 5. When new offline address book generation server is configured click on move button. 6. When move is done a warning appears at the end Move Offline Address Book wizard. Go to Remove old OABG procedure to complete all process
Exchange Management Shell	§ To Move Offline Address Book generation server run the following command: Move-OfflineAddressBook –Identity ‘AddressBookName’ –Server ‘TargetServerName’
Check or Remark	To complete move OABGen you must execute “3.3 Remove old OABGen” procedure

1.3 Remove old OABGen

Pre requisite	§ Use account with membership in the local Administrators group for the target server
Description	This procedure is used to remove share and data of old OAB Generation server.
Command Prompt and Windows Explorer	1. Log on to old OAB server generation and open a command prompt 2. Type net share ExchangeOAB /delete and type Enter. 3. Open a Windows Explorer and go to C:\Program Files\Microsoft\Exchange Server\ExchangeOAB 4. Delete ExchangeOAB’s subfolder. Folder Example :da34a04f-2c52-4f7b-ad40-6c7d5d897c0c.
Check or Remark

logs de diagnostique sur les services MBX, CAS, Hub

2011-04-21T20:35:00.001+01:00

1 CAS D’USAGE

Cette rubrique décrit la procédure de modification du niveau d'enregistrement de diagnostic des processus Exchange Server pour régler les problèmes de dépannage pouvant survenir dans un environnement Microsoft Exchange Server 2007.

Les niveaux d'enregistrement possibles que vous pouvez définir sont : 0 (Minimal), 1 (Bas), 3 (Moyen), 5 (Haut) et 7 (Expert). Le niveau d’enregistrement par défaut est 0 (Minimal). Vous devez toujours remettre le niveau d’enregistrement au paramètre par défaut une fois le dépannage effectué.

2 PREALABLE A L'OPERATION

Se connecter sur un serveur Exchange 2007 en utilisant un compte auquel ont été délégués :

· Le rôle Administrateur de serveur Exchange.

· Le groupe Administrateurs local.

Connaitre le/les éléments à diagnostiquer (ci-dessous une liste des différents éléments).

Identity	EventLevel
MSExchange ActiveSync\Requests	Lowest
MSExchange ActiveSync\Configuration	Lowest
MSExchange Assistants\Assistants	Lowest
MSExchange Autodiscover\Core	Lowest
MSExchange Autodiscover\Web	Lowest
MSExchange Autodiscover\Provider	Lowest
MSExchange Availability\Availability Service	Lowest
MSExchange Availability\Availability Service General	Lowest
MSExchange Availability\Availability Service Authentication	Lowest
MSExchange Availability\Availability Service Authorization	Lowest
MSExchange Cluster\Move	Lowest
MSExchange Cluster\Upgrade	Lowest
MSExchange Cluster\Action	Lowest
MSExchange Common\General	Lowest
MSExchange Common\Configuration	Lowest
MSExchange Common\Logging	Lowest
MSExchange Extensibility\Transport Address Book	Lowest
MSExchange Extensibility\MExRuntime	Lowest
MSExchange EdgeSync\Synchronization	Lowest
MSExchange EdgeSync\Topology	Lowest
MSExchange EdgeSync\SyncNow	Lowest
MSExchange Web Services\Core	Lowest
MSExchange IMAP4\General	Lowest
MSExchange Management Application\Shell	Lowest
MSExchange Management Application\Console	Lowest
MSExchange OWA\FormsRegistry	Lowest
MSExchange OWA\Core	Lowest
MSExchange OWA\Configuration	Lowest
MSExchange OWA\Themes	Lowest
MSExchange OWA\SmallIcons	Lowest
MSExchange OWA\Proxy	Lowest
MSExchange OWA\Transcoding	Lowest
MSExchange OWA\ADNotifications	Lowest
MSExchange POP3\General	Lowest
MSExchange Process Manager\ProcessManager	Lowest
MSExchange Repl\Service	Lowest
MSExchange Repl\Exchange VSS Writer	Lowest
MSExchange Search Indexer\General	Lowest
MSExchange Search Indexer\Configuration	Lowest
MSExchange System Attendant Mailbox\General	Lowest
MSExchange Topology\Topology Discovery	Lowest
MSExchange ADAccess\General	Lowest
MSExchange ADAccess\Cache	Lowest
MSExchange ADAccess\Topology	Low
MSExchange ADAccess\Configuration	Lowest
MSExchange ADAccess\LDAP	Lowest
MSExchange ADAccess\Validation	Low
MSExchange ADAccess\Recipient Update Service	Lowest
MSExchange ADAccess\Site Update	Lowest
MSExchangeAL\Ldap Operations	Lowest
MSExchangeAL\Service Control	Lowest
MSExchangeAL\Attribute Mapping	Lowest
MSExchangeAL\Account Management	Lowest
MSExchangeAL\Address List Synchronization	Lowest
MSExchangeIS\9000 Private\Transport General	Lowest
MSExchangeIS\9000 Private\General	Lowest
MSExchangeIS\9000 Private\Transport Sending	Lowest
MSExchangeIS\9000 Private\Transport Delivering	Lowest
MSExchangeIS\9000 Private\Transfer Into Gateway	Lowest
MSExchangeIS\9000 Private\Transfer Out Of Gateway	Lowest
MSExchangeIS\9000 Private\MTA Connections	Lowest
MSExchangeIS\9000 Private\Logons	Lowest
MSExchangeIS\9000 Private\Access Control	Lowest
MSExchangeIS\9000 Private\Send On Behalf Of	Lowest
MSExchangeIS\9000 Private\Send As	Lowest
MSExchangeIS\9000 Private\Rules	Lowest
MSExchangeIS\9000 Private\Storage Limits	Lowest
MSExchangeIS\9000 Private\Background Cleanup	Lowest
MSExchangeIS\9000 Private\DS Synchronization	Lowest
MSExchangeIS\9000 Private\Views	Lowest
MSExchangeIS\9000 Private\Download	Lowest
MSExchangeIS\9000 Private\Local Replication	Lowest
MSExchangeIS\9001 Public\Transport General	Lowest
MSExchangeIS\9001 Public\General	Lowest
MSExchangeIS\9001 Public\Replication DS Updates	Lowest
MSExchangeIS\9001 Public\Replication Incoming Messages	Lowest
MSExchangeIS\9001 Public\Replication Outgoing Messages	Lowest
MSExchangeIS\9001 Public\Replication NDRs	Lowest
MSExchangeIS\9001 Public\Transport Sending	Lowest
MSExchangeIS\9001 Public\Transport Delivering	Lowest
MSExchangeIS\9001 Public\MTA Connections	Lowest
MSExchangeIS\9001 Public\Logons	Lowest
MSExchangeIS\9001 Public\Access Control	Lowest
MSExchangeIS\9001 Public\Send On Behalf Of	Lowest
MSExchangeIS\9001 Public\Send As	Lowest
MSExchangeIS\9001 Public\Rules	Lowest
MSExchangeIS\9001 Public\Storage Limits	Lowest
MSExchangeIS\9001 Public\Replication Site Folders	Lowest
MSExchangeIS\9001 Public\Replication Expiry	Lowest
MSExchangeIS\9001 Public\Replication Conflicts	Lowest
MSExchangeIS\9001 Public\Replication Backfill	Lowest
MSExchangeIS\9001 Public\Background Cleanup	Lowest
MSExchangeIS\9001 Public\Replication Errors	Lowest
MSExchangeIS\9001 Public\DS Synchronization	Lowest
MSExchangeIS\9001 Public\Views	Lowest
MSExchangeIS\9001 Public\Replication General	Lowest
MSExchangeIS\9001 Public\Download	Lowest
MSExchangeIS\9001 Public\Local Replication	Lowest
MSExchangeIS\9002 System\Recovery	Lowest
MSExchangeIS\9002 System\General	Lowest
MSExchangeIS\9002 System\Connections	Lowest
MSExchangeIS\9002 System\Table Cache	Lowest
MSExchangeIS\9002 System\Content Engine	Lowest
MSExchangeIS\9002 System\Performance Monitor	Lowest
MSExchangeIS\9002 System\Move Mailbox	Lowest
MSExchangeIS\9002 System\Download	Lowest
MSExchangeIS\9002 System\Virus Scanning	Lowest
MSExchangeIS\9002 System\Exchange Writer	Lowest
MSExchangeIS\9002 System\Backup Restore	Lowest
MSExchangeIS\9002 System\Client Monitoring	Lowest
MSExchangeIS\9002 System\Event History	Lowest
MSExchangeIS\9002 System\Database Storage Engine	Lowest
MSExchangeMailboxAssistants\Service	Lowest
MSExchangeMailboxAssistants\OOF Assistant	Lowest
MSExchangeMailboxAssistants\OOF Library	Lowest
MSExchangeMailboxAssistants\Resource Booking Attendant	Lowest
MSExchangeMailboxAssistants\Email_Lifecycle_Assistant	Lowest
MSExchangeMailSubmission\General	Lowest
MSExchangeMU\General	Lowest
MSExchangeSA\Clean Mailbox	Lowest
MSExchangeSA\NSPI Proxy	Lowest
MSExchangeSA\RFR Interface	Lowest
MSExchangeSA\OAL Generator	Lowest
MSExchangeSA\Proxy Generation	Lowest
MSExchangeSA\RPC Calls	Lowest
MSExchangeSA\RPC-HTTP Management	Lowest
MSExchangeFDS\General	Lowest
MSExchangeFDS\FileReplication	Lowest

3 DETAIL DU TRAITEMENT

1. Démarrez l'environnement de ligne de commande Exchange Management Shell.

2. Identifiez le niveau d'enregistrement actuel en tapant la commande suivante :

Get-EventLogLevel

Remplacez <process> par le nom du service ou processus.

3. Modifiez le niveau d'enregistrement en tapant la commande suivante :

Set-EventLogLevel  -Level

4. Vérifiez que le niveau d'enregistrement a été modifié en tapant la commande suivante :

Get-EventLogLevel

Remplacez <level> par le mot Lowest | Low | Medium | High | Expert ou numéro du niveau. Par exemple :

Set-EventLogLevel MSExchangeMU\General -Level 5

Remarque :

Les noms de processus contenant des espaces, tels que MSExchangeIS\9002 System\Virus Scanning, doivent être placés entre guillemets. Par exemple : "MSExchangeIS\9002 System\Virus Scanning"

Remarque :

Vous pouvez obtenir des informations supplémentaires sur un processus en ajoutant la variable « |fl », sans guillemets, à la commande get. Par exemple :
Get-EventLogLevel <process> |fl

Remarque :

Remettez toujours le niveau d’enregistrement au niveau par défaut une fois le dépannage effectué.

Réactivation d'une BAL Exchange 2007 après suppression Procédure de récupération d'une boîte aux lettres supprimée

2011-04-21T20:32:00.000+01:00

1 CAS D’USAGE

Cette rubrique décrit l'utilisation d'Exchange Management Shell pour récupérer une boîte aux lettres supprimée. La rétention de boîtes aux lettres supprimées permet de récupérer des boîtes aux lettres après qu'elles ont été supprimées. Vous devez configurer le serveur Exchange pour la rétention de boîtes aux lettres supprimées et la récupération des boîtes aux lettres doit avoir lieu pendant la période de rétention. Dans Microsoft Exchange Server 2007, la période de rétention par défaut est de 30 jours.

2 PREALABLE A L'OPERATION

Se connecter sur un serveur Exchange 2007 en utilisant un compte auquel ont été délégués :

Le rôle Administrateur de serveur Exchange.

Le groupe Administrateurs du domaine.

3 DETAIL DU TRAITEMENT

Récupération d’une boîte aux lettres supprimée à l’aide d'Exchange Management Shell :

1. Pour trouver les boîtes aux lettres déconnectées, exécutez la commande d’Exchange Management Shell suivante :

Get-MailboxStatistics -Server  | where { $_.DisconnectDate -ne $null } | select DisplayName,DisconnectDate

NB :

est le nom du serveur qui hébergeait la BAL.

2. Pour reconnecter une boîte aux lettres déconnectée lorsque l’objet utilisateur est toujours dans le service d’annuaire Active Directory, exécutez la commande d’Exchange Management Shell suivante :

Connect-Mailbox -Database  -Identity

NB :

est le nom de la banque d’informations hébergeait la BAL. est le nom de la BAL supprimé récupéré dans l’étape 1).

DELEGATION D’APPROBATION MANUEL SUR UN COMPTE UTILISATEUR

2011-04-21T20:26:00.001+01:00

1 CAS D’USAGE

Cette rubrique détaille comment déléguer l’utilisation d’une boite aux lettres d’un utilisateur à un autre.

2 PREALABLE A L'OPERATION

Se connecter sur un serveur Exchange 2007 en utilisant un compte auquel ont été délégués :

Le rôle Administrateur de serveur Exchange.

Le groupe Administrateurs du domaine.

Avoir les noms des utilisateurs concernés par la délégation à savoir :

- Le nom du compte de l’utilisateur dans Exchange

- Le nom du compte à qui on donne l’approbation : login + Domaine

3 DETAIL DU TRAITEMENT

Utilisation de l'environnement de ligne de commande Exchange Management Shell pour octroyer une autorisation d'accès complet à une boîte aux lettres

Permission pour ajouter l'autorisation d'accès complet directement à la boîte aux lettres :

Add-MailboxPermission "Mailbox" -User "Trusted User" -AccessRights FullAccess

Permission Recevoir en tant que (Receive AS):

Add-ADPermission -Identity "Mailbox Store" -User "Trusted User" -ExtendedRights Receive-As

Permission Envoyé en tant que (Send AS):

Add-ADPermission "Mailbox" -User "Domain\User" -Extendedrights "Send As"

NB : “Mailbox” est la BAL de l’utilisateur a délégué.

4 CONTRÔLE DU BON DEROULEMENT DE L'OPERATION

L’utilisateur "Trusted User" devra modifier son profil Outlook afin que la fenêtre d’authentification n’apparaisse plus.

(Pour l’utilisateur) Dans la configuration du profil de messagerie, sélectionner l’onglet Options avancées et pour la Sécurité de connexion au réseau il faut choisir « Authentification du mot de passe NT » (au lieu de Aucun pour un compte sans approbation).

CONTROLE DE L’INTEGRITE D’UNE BANQUE D’INFORMATION DANS EXCHANGE

2011-04-21T20:25:00.000+01:00

Se connecter sur un serveur Exchange 2007 en utilisant un compte auquel ont été délégués :

· Le rôle Administrateur de serveur Exchange.

· Le groupe Administrateurs du domaine.

Avoir le nom de la banque de boites aux lettres à vérifier.

Ce type d’opération s’effectue base Exchange démontée, ce qui signifie que les utilisateurs ne peuvent pas avoir accès à cette base.

Dans un souci de haute disponibilité, et dans la mesure du faisable, ce contrôle d’intégrité s’effectuera donc sur une base Exchange restaurée sur le serveur de backup.

Pour réaliser ce contrôle d’intégrité, il faut utiliser un compte administrateur intégral Exchange.

Informations à connaître : emplacement physique et nom des bases (.edb), emplacement et préfixe des fichiers de transactions associés (E0n*.log), nom et emplacement du fichier système (E0n.chk).

1 DETAIL DU TRAITEMENT

Démonter la base à contrôler

La commande Dismount-Database permet de démonter la base de données nommée « MyDatabase ».

Dismount-Database -Identity ExchangeServer1.Contoso.com\MyDatabase

Vérification de la consistance des bases

Dans le dossier mdbdata où se trouve la base {MyDatabase.edb} à contrôler, taper les commandes DOS :

C:\ C:\Program Files\Microsoft\Exchange Server\Bin>Eseutil /mh MyDatabase.edb | find /i « DB Signature »

Les réponses doivent être exactement identiques.

C:\Program Files\Microsoft\Exchange Server\Bin>Eseutil /mh MyDatabase.edb | find /i « consistent »

Les réponses doivent indiquer :

« State : Consistent »

« Last Consistent: (%a,%b,%c) » sont identiques

Vérification de l’intégrité des bases

Taper la commande C:\Program Files\Microsoft\Exchange Server\Bin>Eseutil /g /i

Le contrôle d’intégrité de la base s’effectue, ça peut durer plusieurs dizaines de minutes (10 Go/H environ)

En cas d’erreur, le contrôle est interrompu

A la fin du contrôle, un message apparaît :

« Integrity check successful »

Remonter les bases

La commande Mount-Database permet de monter la base de données nommée « MyDatabase ».

Mount-Database –Identity ExchangeServer1.Contoso.com\MyDatabase

Update Rollup 3 for Exchange 2010 SP1 and Exchange 2007 SP3

2011-03-27T08:21:00.000+01:00

Update Rollup 3 for Exchange 2010 SP1 and Exchange 2007 SP3

Source : http://blogs.technet.com/b/exchange/archive/2011/03/08/3412103.aspx