Monday, June 28, 2010

Unable to access mailbox after migration from Exchange 2003 to Exchange 2010

I migrated 400 users this weekend to Exchange 2010. The migration seems like the migration went well, since all the move requests came out 100% completed and no one reported any errors. But something didn’t go successfully as reported…..


Right now I have completed troubleshooting an issue where a migrated user was not able to access his mailbox. The users who by the move request report went successful, but not all of the AD attributes were updated.

This is an excerpt of the migration log:
Status : Completed
StatusDetail : Completed
SourceVersion : Version 0.0 (Build 7638.0)
SourceDatabase : exchange2003server\Storage Group\DBname
TargetVersion : Version 14.0 (Build 639.0)
TargetDatabase : 2010-databasename
MoveServerName : fqdn.servername
TotalMailboxSize : 2.951 GB (3,168,187,842 bytes)
TotalMailboxItemCount : 21074
BytesTransferred : 2.717 GB (2,917,612,755 bytes)
ItemsTransferred : 20958
PercentComplete : 100

I then did a get-mailbox username and this gave me the following result:



And this is strange, the log says it completed successfully, but AD says it’s on the Ex2003 server.

I then did | fl to get some more info, and the recipient type and recipient type details returned usermailbox, the Exchange version on the user was 0.10(14.0.100.0). And all these values were correct compared to the migration log.
The only attributes that was wrong on the user object was serverlegacyDN and Servername where it pointed to the Ex2003 server and Ex2003 administrative group.

This pointed me to something going wrong in Active Directory, at the current moment.
I went in to Active Directory with ADSI edit and changed the following attributes
HomeMDB and mdexchhomeservername to the new Exchange 2010 paths.

After changing this to the correct values, the mailbox worked as normal, and the get-mailbox username returned the correct value on servername and serverlegacyDN

Friday, June 25, 2010

Save all attachments does not work after moving to Exchange 2010

Today I troubleshot an issue with Outlook 2007 and the save all attachment function

When we tried to save all attachment from the file->Save as-> save all attachment, nothing happened. We were able to save attachment from the mail (right click save as…).

I tested to find out what causing this problem, and I was able to reproduce it. It seems like if the attachment has been sent from outside the Exchange organization this happens, but if I send the attachment within my Exchange organization the save all attachments works.

After verifying this, I thought this must be an bug.
I did some googling and found this link: http://social.technet.microsoft.com/Forums/en/exchange2010/thread/69f951f4-5ef3-46a3-8391-3e1e4c669c20

They say it’s a known bug in Exchange 2010, and that they are working on a KB article, which has not yet been published (KB980940).

Thursday, June 24, 2010

iPhone OS4.0 - ActiveSync

After iPhone OS 4 has been released, many of our users complain that the ActiveSync does not longer work against Exchange 2010.
This seems to be a bug in the ActiveSync somehow, but we are working on this issue to see if we can find a solution, or if we have to wait for Apple to fix it.

SCOM And Exchange 2010, the Extest_ account gets locked out

For the past 1 month we've been troubleshooting an issue with our SCOM and Exchange 2010 monitoring.
The monitonring with the SCOM Management Pack works fine for a long time, but suddenly the extest_ account get locked out. This is right after the automatic password change routine on the Exteset_ account.

After talking to MS premier support, they have now found a bug in how the SCOM does it authentication, and that the authentication is multiple ways.

I've got an workaround, and that was to disable the following SCOM monitors, this did not work for us, but you might try it to remove the annoying SCOM alerts. This is the response we got from Microsoft:

"In the authoring section of the OpsMgr console, “Outlook Server Availability” to your scope and disable the 6 monitors that start with “KHI: HTTP Connectivity Against Local Server”. This should disable the instance of test-outlookconnectivity that causes this problem. We’ll be addressing issue, but this should serve as a workaround for now"

Users unable to access Exchange Control Panel(ECP, OWA)

Today I troubleshooted an issue on Exchange 2010.
When the users clicked the Options button to access the Exchange Control Panel, the OWA page just reloaded and nothing happend.
Also when I tried to access the url for the ECP https://url/ECP I came to the OWA page.

One configuration change we did to remove the timezone and language prompt for our OWA users, was to set the defaultclientlanguage on the OWAVirtualdirectory.

When the OWAvirtualdirectory -defaultclientlanguage is set to something else than 0, this issue will occure.

I have now send a bug report to Microsoft, to find out if this is by design, or if its a bug.

Wednesday, June 16, 2010

An IIS directory entry couldn't be created. The error message is Access is denied.. HResult = -2147024891

Today I did a Exchange 2007 to Exchange 2010 migration. we had to keep one of the Exchange 2007 CAS serveres for the Microsoft Transporter Suite (Lotus Notes integration).
When doing an get-owavirtualdirectory and other cmdlets involving all servers in the organisation, I got the following error message:



The solution for this error messsage is to add the Exchange trusted subsystem to the local admin group on Exchange 2007 servers.

Tuesday, June 15, 2010

How to change placement of queues and log files in Exchange 2010 HUB and CAS

As a general best practise its recommended to change the default paths for logfiles, to avoid them filling up your System disk.

Exchange 2010 uses the default installation path for all logs and mail queues for HUB and CAS.
To change these you can modify the following files in the Exchange 2010 install folder \bin.
The paths I normally change is the ones specified below:

Edgetransport.exe.config
  • add key="QueueDatabasePath" value = "D:\Exchange\Transport Roles\Data\Queue"
  • add key="QueueDatabaseLoggingPath" value = "D:\Exchange\Transport Roles\Data\Queue"
  • add key="IPFilterDatabasePath" value = "D:\Exchange\Transport Roles\Data\IPFilter"
  • add key="IPFilterDatabaseLoggingPath" value = "D:\Exchange\Transport Roles\Data\IPFilter"
  • add key="TemporaryStoragePath" value = "D:\Exchange\Transport Roles\Data\Temp"
microsoft.exchange.addressbook.service.exe
  • add key="LogFilePath" value="Drive\Folder"

microsoft.exchange.rpcclientaccess.service.exe

  •  add key="LogPath" value="D:\Exchange\RPC Client Access\"

POP3 IMAP config files are located in \v14\ClientAccess\PopImap

Change the following files to set the new log folder for the services:

  
Microsoft.Exchange.Imap4.exe.config
  • add key="TemporaryStoragePath" value = "D:\Exchange\ClientAccess\PopImap\Temp"
  • add key="LogPath" value="D:\Exchange\ClientAccess\Imap4" 
Microsoft.Exchange.Pop3.exe.config

  •  add key="TemporaryStoragePath" value = "D:\Exchange\ClientAccess\PopImap\Temp"
  •  add key="LogPath" value="D:\Exchange\ClientAccess\Pop3"

Always backup your files before you edit them, and to make the change active. You have to restart the services related to the config file.
Regarding NTFS permissions, be sure to grant the correct user on the folder. Some services acts as network service.