January 2009
Monthly Archive
written by admin on
Jan 30, 2009
I wanted to bring to light a specific issue that may occur during mailbox moves in complex environments with multiple Active Directory Sites and multiple Exchange servers. There are several other settings which must be in place in order for this issue to present itself.
First, here are the settings which need to be in place:
1. On both the Source and Target mailbox stores, set Deleted Mailbox Retention to 0 days.
2. Note what the Online Maintenance schedule is set to on both stores. The moves need to be scheduled to coincide with Online Maintenance on the Target mailbox store.
*Note - for the purposes of my testing, I set Online Maintenance to run Always for my databases.
3. There must be multiple Active Directory Sites so as to introduce AD replication latency (Inter-Site connectors can only replicate every 15 minutes), and there need to be Exchange servers in these different AD sites (or Exchange must be configured to statically point to the GC of the other site).
4. Enable Diagnostics Logging under MSExchangeIS\Mailbox, and set the category General to Maximum (only minimum is necessary though). This is necessary in order to log Online Maintenance events.
Some background here: one of the tasks performed by Online Maintenance is to identify mailboxes that are past the retention date and to delete them. As part of this task, it will also run the Cleanup Agent, which is the task that identifies orphaned/reconnected mailboxes. If you recall, in Exchange 2000 and 2003, if you delete a mailbox, it is not immediately deleted, nor is it marked as disconnected. If a mailbox is orphaned (no user connected to it), it gets marked as disconnected; if it is disconnected and past the retention date, it gets deleted.
For more information on the tasks run during Online maintenance, please see the following link:
http://technet.microsoft.com/en-us/library/aa996226(EXCHG.65).aspx
During a mailbox move, the destination mailbox will be created so that data can be copied to it. This destination mailbox is not yet associated with a user account though. This process of associating with the user account does not happen until the very end of the mailbox move and all content has been copied to the destination mailbox. During the final step of the move, the user attributes are updated to point to the new server (if applicable) and new database. This process of updating attributes is what associates the destination mailbox with the user account.
If you manually run the Cleanup Agent on the destination mailbox store during a move, you will find that the destination mailbox will show up as a disconnected mailbox. If you then run the Cleanup Agent again right after the move completes, you will find that in some cases the destination mailbox will also be purged. This can cause problems, because when a move is successful, the source mailbox is removed as well. If the Cleanup Agent is run from another Exchange server that is pointing at a different Active Directory Site, and the Exchange attributes (homeMDB, homeMTA, msExchHomeServerName) have not yet been updated, the Cleanup Agent will detect that this mailbox is not attached to a user account, and that it is past the retention date; and therefore, the mailbox will be deleted. You should see the following events indicating that this is occurring:
Event 9533
The user account for "user" does not exist in the directory or is not enabled for Exchange mail. This mailbox will be removed from the mailbox store "database" in 0 days.
Following that, you will see:
Event 9535
Cleanup of deleted mailboxes that are past the retention date is finished on database "database"
The first time I saw this event, the mailbox was not deleted. Then we have round 2, a few minutes later:
Event 9531
Starting cleanup of deleted mailboxes that are past the retention date on database "database"
Event 9535
Cleanup of deleted mailboxes that are past the retention date is finished on database "database"
1 deleted mailboxes have been removed
Event 9532
The user account "user" does not exist in the directory or is not enabled for Exchange mail. This mailbox has been removed from the mailbox store "database"
There are two ways to prevent this from happening:
- Make sure that Deleted Mailbox Retention is set to a non-zero value.
- Configure the Online Maintenance interval so that it does not overlap with your scheduled mailbox moves. Alternatively, set Online Maintenance to not run on days when you will be scheduling moves.
If you have encountered a situation similar to this, we want to hear from you! Please post a comment.
- Ben Winzenz
written by admin on
Jan 29, 2009
Category Importer for Outlook, exports your Master Category List (MCL) to a text file that you can easily import on another PC. Free
written by admin on
Jan 29, 2009
Delegate Message Mover automatically moves Sent-As messages to the Sent Items folder of the mailbox given as the sender. Free.
written by admin on
Jan 29, 2009
Use AutoBCC to automatically send a blind-copy of all your outgoing messages to another address, for monitoring team communications with customers or just to improve workflow. Free.
written by admin on
Jan 28, 2009
Here is a summary on the mailbox language settings following the various tests that I could do and articles that I have read. I hope that this can help you.
How it worked before Exchange 2007
In previous versions of Exchange Server, the language for a user mailbox was determined by the language setting of the MAPI agent (such as the Outlook client) and not by the Exchange server:
- At the first connection of a MAPI agent (like Outlook client) to a user mailbox, the language of the default folders (like inbox) and system messages (like quota messages and non-delivery reports) was set on the information store (PR_LOCALE_ID MAPI property) to the language used by the MAPI agent.
- Each new connection of an MAPI agent changed the PR_LOCALE_ID of the mailbox to match the one used by the agent. Only system messages were modified, the default folders remained in the language of the first agent connection.
And now with Exchange 2007
What's new?
In Microsoft Exchange Server 2007, you can specify the language preferences for a mailbox, in order of preference, with the Languages parameter by using the Exchange Management Shell and the Set-Mailbox cmdlet. Several Exchange components display information to the user using the preferred language, if that language is supported. These components include quota messages, non-delivery reports (NDRs), the Microsoft Outlook Web Access user interface, and Unified Messaging (UM) voice prompts.
Note:
- An acceptable value for the Languages parameter is a combination of an ISO 639 two-letter lowercase culture code associated with a language and an ISO 3166 two-letter uppercase subculture code associated with a country or region. (To learn more about culture codes and to view a complete list of acceptable values: http://msdn.microsoft.com/en-us/library/system.globalization.cultureinfo.aspx).
- The update of the Languages parameter (by administrator or user action) can requires some time (minutes to hour(s)) to be taken into account by the Exchange infrastructure.
- Microsoft Exchange Server 2007 has more language support for its components and features than in any earlier versions of Microsoft Exchange (http://technet.microsoft.com/en-us/library/bb123979.aspx).
Example: How to change the languages for a user mailbox (see http://technet.microsoft.com/en-us/library/bb310757.aspx):
|
Set-Mailbox -Identity "Carlo Dupont" -Languages "fr-FR" |
How it works
- At the first connection of a MAPI agent (like the Outlook client) to a user mailbox, the language of the default folders (like inbox) and system messages is set on the information store (using the PR_LOCALE_ID MAPI property) to the language used by the MAPI agent.
- Subsequent MAPI agent connections will never change neither the language of system messages nor default folders language even if the PR_LOCALE_ID does change.
- An administrator can set the language of a mailbox language (Set-Mailbox cmdlet with -Languages parameter) and this setting has no impact on the PR_LOCALE_ID MAPI property but affects the msExchUserCulture attribute for the user object in Active Directory.
- If this Language parameter (empty by default) is defined, following settings are affected:
- System messages
- OWA user interface
- Unified Messaging voice prompts
- The user will still be prompted to choose a language and time zone the first time he logs on to Outlook Web Access (OWA). But the default selected language will be the one defined by the administrator:
- If the user accepts these default settings: the language for default folders and system messages will be set to the language defined by the administrator.
- If the user chooses another language: this will modify only the language of system messages BUT default folders names will remain in the language defined by the administrator.
Figure 1: OWA - First connection Language Setting
Conclusion
Administratively set language will prevail for default folder language but not necessarily for user interface language.
What else?
An administrator can also define two language parameters for each OWA Virtual Directory (by using the Set-OwaVirtualDirectory cmdlet):
- DefaultClientLanguage: The default value for this setting is 0. This means the default client language is not defined and users will be prompted to choose a language and time zone the first time that they log on to OWA. If the value is defined (different from 0 ) (for example 1036 for French (France)), users will not be prompted to choose a language and the OWA time zone will use the time zone of the Client Access server. Thus the default folders and system messages of the user mailbox will be in the language defined by the administrator (the Languages parameter of the mailbox will remain empty). However users are still free to update their language in OWA and therefore change the system messages language.
- LogonAndErrorLanguage: The logon and error language is the language that will be used for errors and the forms-based authentication logon page. By default the value is not defined and set to 0 and OWA will default first to the language set on Internet Explorer on the client computer. If the language set on Internet Explorer on the client computer is not supported by OWA, the language of the Client Access server will be used.
Example: How to set OwaVirtualDirectory Language parameters (see http://technet.microsoft.com/en-us/library/aa997435.aspx):
|
Set-OwaVirtualDirectory -identity "Owa (Default Web Site)" -LogonAndErrorLanguage 1036 -DefaultClientLanguage 1036 |
What can the user do?
Whatever configuration is set by the administrator (except disabling OWA access), a user can change his language with the Outlook Web Access "Regional Settings" options.

Figure 2: Language modification in OWA
Note: When a user change the language with OWA, the Languages parameter of the mailbox is updated. For example: At the first connection, if the user has chosen "French (France)" so the -Languages parameter will be {fr-FR}. Then if the user chooses "Turkish" with OWA, the parameter will be {tr-TR, fr-FR}.
Focus on the default folders language
The first of the following actions will set the language of the default folders:
- Set the Languages parameter (with Set-Mailbox cmdlet) by an administrator [new];
- Connection to the mailbox with an MAPI agent (like Outlook client);
- Connection to the mailbox with OWA;
- Mail received by the mailbox before any connection or administrator action (use of the Mailbox server language).
And it is possible for the user to change his default folder names to another language with the following methods:
- By using his Outlook clients: Outlook 2002 and newer version can run a command line switch to rename the default folders to the language of the client. To do this, click Start, click Run, and then type Outlook.exe /resetfoldernames. Outlook will start normally and the default folder names will be in the language of the client.
- By using the Exchange 2007 Outlook Web Access: under "Regional Settings" options [new]
Figure 3: Default Folders Language modification in OWA
Using Exchange Management Shell or Console, the Administrator has no way of changing default folders language if the mailbox is already initialized.
Synthesis
Here is a quick summary of the various possibilities for set the language of mailboxes:
|
|
User |
Administrator |
|
System Messages language change |
Yes, with Outlook Web Access |
Yes, using cmdlets (Set-Mailbox, Set-OwaDefaultVirtualDirectory) |
|
Folder name changes |
Yes, with Outlook Web Access or Outlook client |
Yes, using cmdlets (Set-Mailbox, Set-OwaDefaultVirtualDirectory)
Only before mailbox initialization* |
|
System Message content change |
N/A |
Yes, for each supported language(New-SystemMessage) |
*Initialization occurs during the first connection from a client (MAPI or Outlook Web Access) or when receiving a message
For further reading and most up-to-date information:
--Murat Gunyar
written by admin on
Jan 27, 2009
Please be advised that Single Label Domain (SLD) support in the next version of Exchange is under review.
In February 2008 we announced that Exchange 2007 would be supported on an SLD. At the same time we announced that the next version of Exchange would not be supported on an SLD.
This policy is now under review and it may be that the next version of Exchange will be supported on an SLD. The Exchange product team's view continues to be that SLDs are not a recommended configuration, and that customers should fully evaluate how remaining on an SLD impacts their environment. Anyone who is currently planning on migrating their SLD to a Fully Qualified Domain Name (FQDN) only because of the February 2008 announcement should also take into consideration that the policy is being re-evaluated. We expect to make the decision public in the next few months.
- Ed Beck
written by admin on
Jan 27, 2009
Please be advised that Single Label Domain (SLD) support in the next version of Exchange is under review.
In February 2008 we announced that Exchange 2007 would be supported on an SLD. At the same time we announced that the next version of Exchange would not be supported on an SLD.
This policy is now under review and it may be that the next version of Exchange will be supported on an SLD. The Exchange product team's view continues to be that SLDs are not a recommended configuration, and that customers should fully evaluate how remaining on an SLD impacts their environment. Anyone who is currently planning on migrating their SLD to a Fully Qualified Domain Name (FQDN) only because of the February 2008 announcement should also take into consideration that the policy is being re-evaluated. We expect to make the decision public in the next few months.
- Ed Beck
written by admin on
Jan 27, 2009
Learn the basics of editing the Calendar Printing Assistant templates.
written by admin on
Jan 27, 2009
Genie Archive for Outlook (2003/2007) is an ideal solution for email archiving and management. You can automatically clean up that over cluttered inbox of thousands and thousands of old emails without the need of user interference. Simply set it up and let Genie Archive for Outlook handle the rest. Version 2.5 For Outlook 2003/2007.
written by admin on
Jan 27, 2009
Backup utility for Outlook 2000, 2002, 2003 handling folder data and key user options, including toolbar and Outlook bar settings, signatures, stationery, and Internet account information. Version 8.
Next Page »