Saturday, June 26, 2010

The blog has moved to wordpress

Hello Dears,
I have spent 4 years with blogger, during this period I have struggled to post the best to you all, but blogger no longer helping me so I moved to wordpress with more intuitive name :), the blog will be located on http://autodiscover.wordpress.com

although the name is for Exchange LOL (I love Exchange the best Product I can work with), we will keep posting on CS14, AD and virtualization as usual.

I will no longer post here, to follow us please visit the blog on: http://autodiscover.wordpress.com


Bye bye Blogger

Friday, June 25, 2010

Exchange 2007 SP3 expired password reset tool

we all suffered from that, users with expired password cannot login to OWA or change their passwords, this have neen changed in Exchange 2007 SP3, there is a new web module that enables users with expired password to change their passwords.
Now that this feature is disabled by default, to avail this Password Reset feature administrators need to enable this…..To enable the password reset feature
  1. Log on Client Access Server | Registry Editor
  2. Go to HLKM\SYSTEM\CurrentControlSet\Services\MSExchange OWA
  3. Create the following DWORD value if it does not already exist:
    Value name: 
    ChangeExpiredPasswordEnabledValue type: REG_DWORD
    Value data: 
    1

how to set spell checking language for users in OWA

here is a Nice Trick: to set the spell checking language for users you can use the following cmdlet:

Set-MailboxSpellingConfiguration with -DictionaryLanguage
More information:
Set-MailboxSpellingConfiguration
thanks to Frank Wang for the trick

Wednesday, June 23, 2010

how to prevent users from updating their info using RBAC and Exchange control panel

here is a nice quick tip, if you want to quickly prevent users from updating their info using the ECP in Exchange 2010, then you use cmdlet:


set-ManagementRoleAssignment -Identity "MyContactInformation-Default Role Assignment Policy" -Enabled $false


this stop users immediately from updating the info in the ECP, if you want to allow some users to still do this you will have to edit the default policies to include a custom management role.

Thursday, June 17, 2010

Exchange 2010 Issue: you may receive 554 5.6.0 STOREDR .Deliver; Corrupt message content

Consider the following scenario:
a user send a message to:
Multiple recipients within the organization including 1 or attachments and Rule or software applied disclaimer.
you will receive the following error:
#554 5.6.0 STOREDRV.Deliver; Corrupt message content ##





Original message headers:





Received: from mail.domain.com ([fe80::b5a3:e52f:14f6:1733]) by

mail.domain.com ([fe80::b5a3:e52f:14f6:1733%11]) with mapi; Mon, 26

Apr 2010 16:05:28 -0500

Content-Type: application/ms-tnef; name="winmail.dat"

Content-Transfer-Encoding: binary

This issue is a bug reported in Exchange 2010 RTM until RU3, this will be fixed in RU4 and SP1 RTM, there is no current fix for the issue.