Exchange Server 2007 mailbox stamped as legacy mailbox

User's mailbopx has been moved to Exchange 2007 server. User complains he or she cannot access the mailbox via OWA. However, Outlook works fine. Find the mailbox via EMC, it stamped as a legacy mailbox instead of user mailbox.

 

Solution:

 

    To remove the legacy tag from mailboxes, use the following Exchange Shell command:

 

Set-Mailbox jsmith -ApplyMandatoryProperties

 

MS KB Link:

 

http://support.microsoft.com/kb/931747

 

 

Please also note that: If you use the Exchange Server 2003/2000 extensions to Active Directory Users & Computers (ADUC) console to create mailboxes residing on Exchange Server 2007 servers, these mailboxes get stamped as legacy mailboxes.

 

Get-ExchangeServer | Where {$_.IsExchange2007OrLater} | Get-Mailbox | where {$_.RecipientTypeDetails -eq "legacymailbox"} >C:\ex07_LegacyMailbox.txt

 

To Apply mandatory properties to all Exchange Server 2007 mailboxes stamped as legacy mailbox, please us e the following shell cmdlet:

 

Get-ExchangeServer | Where {$_.IsExchange2007OrLater} | Get-Mailbox | where {$_.RecipientTypeDetails -eq "legacymailbox"} | Set-Mailbox -ApplyMandatoryProperties

 

 

"Unspecified error" when replying or forwading mail in outlook 2003

Issue: Outlook's Users experienced the issue ("Unspecified error" when replying or forwading mail in outlook 2003) when users use Microsoft Word as Outlook's default editor and the message contains html embedded format.

 

Workaround:   Once changed the HTML format to Rich Text format (next to option) while forwarding or replying to this email, and it goes perfect.

Fix “username” is not valid for UserPrincipalName issue

After an upgrade to Exchange 2007, you may get some errors related to your account and User Principal Name (UPN). This particularly occurs when you have users where no domain name is filled in at User Logon Name at the Account tab in Active Directory.

The following error indicates that you have not set a domain name at the User Logon Name:

Warning:
Object domain/organizational unit/username has been corrupted and it is in an inconsistent state. The following validation errors have occurred:

Warning:
"username" is not valid for UserPrincipalName. Valid values are: Strings that includes '@', where '@' cannot be the last character..

To solve the problem, you should fill in a domain name for every user who hasn't got one. If you have only a few users without domain name, you could do it manually. If there are more than 10, I would suggest using ADModify. ADmodidy is a tool with a GUI, which offers you many functionality in a very easy way to modify attributes in Active Directory.

You can download ADModify

Practical note: When setting attributes with ADmodify, don't forget to test first with a small group of users!