Dario IT Solutions Blog

The process of mailbox-enabling a user for Exchange 2003-based mailbox was preformed using the Active Directory Users and Computers SnapIn. Using this SnapIn, you could choose to place the mailbox on a DB located on an Exchange 2007 server. That, of course, would be the wrong way to go. The appropriate way of creating a mailbox on Exchange 2007 is to use the Exchange Management Console or the Exchange Management Shell.

Creating an Exchange 2007 mailbox using the mentioned snapIn would leave you with a mailbox that is missing some attributes. These attributes are required for normal operation under Exchange 2007 environment. Your mailbox will appear as “Legacy Mailbox”, rather then “User Mailbox” in the EMC. Usually, “Legacy Mailbox” means that this is a mailbox located on an Exchange 2003 within the same Exchange Organization.

The fix is simple.

Open Exchange Management Shell and run this command on the problematic mailbox:

Set-Mailbox Alias -ApplyMandatoryProperties

Your mailbox’s attributes should have been updated,  and the result will be visible a few seconds later within the EMC.

Further details from Microsoft:

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

Hi guys,

It was very nice meeting you all yesterday at the re-birth of the Infrastructure & Management User Group.

Below is the presentation for the main subject we talked about – “Windows 2008 R2 Overview”.

We will continue next month, on December 17th with the subject “Active Directory improvements in Windows 2008 R2”.

In the meantime, share your thoughts and interesting finds at the group site – http://www.linkedin.com/groupRegistration?gid=2389097

Have a great weekend and take care!

I know its a bit late, but here is the presentation I gave on November 3rd at the Microsoft convention – Let’s Talk Business-Tech that was held at Tel Aviv.

During the presentation, my co-presenter Ronen Gabay and myself talked about the new features of Failover Clustering in Windows 2008 R2.

We talked about Geo-Clusters, PowerShell 2.0 extensive support, Cluster Shared Volumes and mainly about how simple it is to create and manage complex cluster (everyone can do it! believe me! ).

We finished the presentation with a nice demo of RDS 7.0 media enhancement when we showed a 1080P HD movie (Terminators 2 Trailer) over RDP 7.0 while doing a Live Migration of the RDS Session Host virtual server that we RDPed into.. very nice!

What do you think, will we start seeing more clusters from now on? or something is still missing?

I’ll love to get your input.

By default when a new mailbox access the OWA after the first logon the following screen appears, and we should choose the language and time zone settings:

How can we remove this screen? It’s easy just set up the DefaultClientLanguage parameter in the OWA virtual directory, using the following cmdlet: 

Set-OwaVirtualDirectory -identity “Owa (Default Web Site)” -DefaultClientLanguagage <language code>

Now, all the first logon will be using the language that we choose in the language code, here are some language codes:

• English (Canada) : 4105

• Portuguese (Brazil): 1046

• French(Canada): 3084

• Hebrew(Israel): 1037

Note: When you change the language code, this value is not filled out in the user attribute, when you return the value to 0, all the users that haven’t chosen yet the value will receive the option to choose. To rollback the settings to the normal behavior(user get to choose), just set up the language code with the 0 value.

More useful commands:

1. List the DefaultClientLanguage of determined server:
   Get-OwaVirtualDirectory | Sect Name,DefaultClientLanguage

2. Run the following command to set the logon and error language setting:
   Set-OwaVirtualDirectory -identity “Owa (Default Web Site)” -LogonAndErrorLanguage <language code>

3. Run the following command to set the client languages setting for an individual mailbox:
   Set-Mailbox -identity <mailbox identity> -languages <language code>

4. Validating the Language value in the mailboxes
   Get-Mailbox | Select Name,Languages

(Taken from: Anderson Patricio Blog-http://msmvps.com/blogs/andersonpatricio/archive/2007/06/06/changing-the-language-of-the-owa-logon-page.aspx

And from Technet- http://technet.microsoft.com/en-us/library/aa997435.aspx)