Mailbox

Exchange 2010 and the Exchange Trusted Subsystem In this case, the problem was initially manifesting itself as the following error when trying to create a new mailbox in the first database created with installation of the server: Active Directory operation failed on adserver.domain.com. This error is not retriable. Additional information: Insufficient access rights to perform the operation. Active directory response: 00002098: SecErr: DSID-03150E8A, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0 The user has insufficient... [Lire la suite]

All Exchange admins are so used to seeing the name of the server / fqdn of the VIP in the server entry of the outlook profile. That is a thing of the past in Exchange 2013!   The server entry or the connection endpoint for Outlook 2007+ clients which connects to an Exchange 2013 mailbox is the “mailbox guid @ the primary smtp address of the user”. Let me explain the new concept with an example. My mailbox has a primary smtp address of Rajith@Exchangemaster.me and the server entryin my outlook profile is as shown below. This... [Lire la suite]

Qui a travaillé sur des projets Office 365 a surement rencontré cette problématique avec les boîtes partagées : Elles sont gratuites mais apparaissent dans les boîtes nécessitant une licence La procédure suivante vous permettra de configurer les boîtes partagées de façon à ce qu’elles n’aient pas besoin de licence Création de la boîte partagée via la création d’une RemoteMailbox, lancer ensuite un DirSync New-remoteMailbox : http://technet.microsoft.com/en-us/library/ff607480.aspx   --> La suite de... [Lire la suite]

The mailbox move process has been fine tuned in Exchange 2013 with the concept of “Batch Move”.   Similar to Exchange 2010, a single or multiple mailboxes can be moved using EAC. Mailbox move can be initiated from the move mailbox option next to a mailbox or by using the “Migration” tab in the “Recipients” node.  --> Please see the rest on the blog : http://www.howexchangeworks.com/2012/09/mailbox-move-in-exchange-2013.html

Site mailboxes allow users to work together naturally – while compliance is applied behind the scenes. A site mailbox brings Exchange emails and SharePoint documents together. For users, a site mailbox serves as a central filing cabinet, providing a place to file project emails and documents that can be only accessed and edited by site members. When one project member files mail or documents using the site mailbox, any project member can then access the content. Site mailboxes are surfaced in Outlook 2013 and give users easy access... [Lire la suite]

Bonjour à tous, S’il y a bien un changement dans Exchange 2013 qui a son importance, outre toutes les nouveautés présentées, c’est bien l’abandon de MAPI (Messaging Application Program Interface) comme protocole de communication ! MAPI représente le protocole utilisé par défaut par tous les clients de messagerie internes à l’organisation ou se trouve une infrastructure Exchange (2003/2007/2010) pour communiquer avec. Un changement important avec l’arrivé d’Exchange 2010 avait été fait en remontant le point de connexion du... [Lire la suite]

Mailbox Role Failed Error: The following error was generated when "$error.Clear(); $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName; $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName; $mbxs = @( get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 ); if ( $mbxs.length -eq 0) { $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController); if($dbs.Length -ne 0) { $mbxUser =... [Lire la suite]

Si vous rencontrez cette erreur ExchangeStoreDB (event 123) avec le détail suivant : At <timestamp> the Microsoft Exchange Information Store Database <identity> copy on this server experienced a corrupted search catalog. Consult the event log on the server for other « ExchangeStoreDb » and « MSExchange Search Indexer » events for more specific information about the failure. Reseeding the catalog is recommended via the ‘Update-MailboxDatabaseCopy’ task. Faite un reseed de l’index via la commande... [Lire la suite]

 was running mailbox moves from Exchange 2003 SP2 to Exchange 2010 SP1 servers and noticed that the process was taking much longer than previous migrations. I have migrated from legacy Exchange to 2010 RTM and the time taken was much lesser. Looking more into it, I found that only 2 mailboxes are moved simultaneously to a 2010 SP1 database, though there were hundreds of mailbox move requests queued. This happens because of a change that has been made in 2010 SP1 to the Mailbox Replication Service (MRS) configuration file in the... [Lire la suite]

The History Historically, when an administrator moved an Exchange 2010 mailbox from one database to another, the user's Outlook client would present them with a message stating: The Exchange administrator has made a change that requires you quit and restart Outlook. Only after restarting Outlook would the user have access to their mailbox. To understand this behavior, it's helpful to understand what generates the dialog in Outlook and why Exchange 2010 triggers the message. Outlook caches three items about each Exchange... [Lire la suite]