Mail Enabled User has legacy value in ExchangeVerion attribute
(Exchange 2007) I have a number of mail enabled users with the ExchangeVersion attribute set with this value: 0.0 (6.5.6500.0)
Can I update this via powershell? Will it be problem moving to Exchange 2010?
Thanks!
July 1st, 2011 7:03pm
I wouldn't tinker with it the objects probably didn't get "upgraded" sometimes they don't get upgraded unless they are "touched" again. In either case I doubt it will cause any issue for you. Try doing set-mailbox user -applymandatoryproperties and see
if it updates the object.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
July 1st, 2011 7:16pm
I did not test it, But I belive you can change it thru ADSI Edit. But if you are going to move it to 2010 server then what is need to do it. It should get change once it will migrate to exchange 2010.Anil MCC 2011,ITIL V3,MCSA 2003,MCTS 2010, My Blog : http://messagingschool.wordpress.com
July 1st, 2011 7:22pm
Hi,
Creating an Exchange 2007 mailbox through the Exchange 2003 extensions to the Active Directory Users and Computers console is not
supported. If an Exchange 2007 mailbox is created with this tool, it will be identified as a legacy mailbox, even though it resides on an Exchange 2007 server. Use the
ApplyMandatoryProperties parameter to modify the mandatory properties of a mailbox in this state to correct the problem and remove the legacyMailbox tag from the mailbox.
More information:
Set-Mailbox
user
was unable to access his OWA
Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
July 5th, 2011 8:45am
Thanks for the advice. These are mail enabled, not mailbox enabled and the -applymandatoryproperties is not an option for this type of mail user.
July 5th, 2011 2:45pm
Which type of the mail enabled object? Is it a mail enabled public folder?Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
July 6th, 2011 5:00am
These are mail enabled users
July 6th, 2011 2:14pm
Mail enabled user? This type of object should be able to apply this command.
set-Mailbox User_Name –ApplyMandatoryProperties
As my test, mail enable public folder can’t apply the command.
Did you read the link I post above?
Free Windows Admin Tool Kit Click here and download it now
July 7th, 2011 4:24am
Thanks for the links. This Exchange object type does not accept the set-mailbox cmdlet. These are not public folders.
July 7th, 2011 2:28pm
Could you please post a screen shoot?
I think there must be some misunderstanding between you and me.
As my test, Exchange 2007 supports the above command.
Free Windows Admin Tool Kit Click here and download it now
July 8th, 2011 4:25am
Hi AD EX,
Do you have any update?
July 13th, 2011 5:05am
here is a copy of the powershell output. I've replaced my test user with "<user>". Note the recipienttype and the error. We are dealing with a MailUser object not a UserMailbox.
[PS] C:>get-mailuser <user> | select name,recipienttype,exchangeversion | ft -autosize
Name RecipientType ExchangeVersion
---- ------------- ---------------
<user> MailUser 0.0 (6.5.6500.0)
[PS] C:>set-mailbox <user> -ApplyMandatoryProperties
Set-Mailbox : <user> is not a mailbox user.
At line:1 char:12
+ set-mailbox <<<< <user> -ApplyMandatoryProperties
+ CategoryInfo : NotSpecified: (0:Int32) [Set-Mailbox], ManagementObjectNotFoundException
+ FullyQualifiedErrorId : 8B3E6183,Microsoft.Exchange.Management.RecipientTasks.SetMailbox
Free Windows Admin Tool Kit Click here and download it now
July 13th, 2011 4:52pm
Can you try with this once
Get-User -Filter "ExchangeVersion -Eq "6.5.6500.0"
Check whether all the users are pulled out, if yes run
Get-User -Filter "ExchangeVersion -Eq "6.5.6500.0" -ApplyMandatoryProperties
Else
Get-User "Name of the user" -ApplyMandatoryPropertie
July 13th, 2011 9:41pm
Similar problem with this approach. The -ApplyMandatoryProperties does not work with the set-user cmdlet.
Free Windows Admin Tool Kit Click here and download it now
July 13th, 2011 9:52pm
Ok, I reproduce a similar issue.
I created a use via ADUC, but I didn’t mail enable the use.
I run this command:
Get-user test |select name, recipienttype, exchangeversion
Result:
Name
RecipientType
ExchangeVersion
Test
User
0.0 (6.5.6500.0)
Get-user administrator |select name, recipienttype, exchangeversion
Result:
Name
RecipientType
ExchangeVersion
Test
UserMailbox
0.1 (8.0.535.0)
Set-Mailbox test –applyMandatoryProperties
Result:
Set-Mailbox: test is not a mailbox user.
After I mail enabled test, the Exchange version update to 0.1 (8.0.535.0)
It seems you didn’t mail enable the user.
As
KB 931747 said,
This issue may occur if the following conditions are true:
1. The mailbox was created in the Active Directory Users and Computers snap-in on a server that was running Microsoft Exchange Server 2003.
2. The mailbox was moved to an Exchange Server 2007 server or an Exchange Server 2010 server .
Could you please try to create a new mailbox via EMC, and check the Exchange version of the user?
For the users in question, could you please try to remove mailbox and enable a new mailbox via EMC.
Before you do that, remember backing up their files.
July 14th, 2011 4:58am
Thanks for doing those tests. You are confusing the the terminology between mail enabled and mailbox enable. These are mail enabled users that have external addresses. At this point I think the only thing I can do is to remove the
exchange attributes and then mail enable them (not mailbox enable) to correct the attribute.
I was hoping that I could do this on a mail enabled user the same way it can be done on a mailbox enabled user.
Free Windows Admin Tool Kit Click here and download it now
July 14th, 2011 2:22pm
Hi AD EX,
Sorry for the misunderstand.
So you means mail user
Mail user: A mail-enabled Active Directory user that represents a user outside the Exchange organization. Each mail user has
an external e-mail address to which all messages sent to the mail user are routed. A mail user is similar to a mail contact, except that a mail user has Active Directory logon credentials and can access resources.
Understanding
Recipients
Here is an explanation of this attribute.
Exchange Server 2007 and Exchange Server 2010 both use the
msExchVersion attribute to determine the version of Exchange Server that user objects are associated with.
Error
message when an Exchange Server 2007 user or an Exchange Server 2010 user tries to log on to OWA
>>Can I update this via powershell? Will it be problem moving to Exchange 2010?
Each mailbox consists of an Active Directory user and the mailbox data stored in the Exchange mailbox database. All
configuration data for a mailbox is stored in the Exchange attributes of the Active Directory user object. The mailbox database contains the mail data that's in the mailbox associated with the user account.
Understanding
Disconnected Mailboxes
So,
I think you
can’t update Exchange version for this mail user. Because it not really associated with an Exchange mailbox. It associated with an external SMTP address. It is same in Exchange 2010.
July 14th, 2011 10:50pm