Outlook says .. Microsoft Exchange is not available

This was is a good one and has been doing my head in!

I had a user mailbox that could log in to OWA but not Outlook.

With outlook you would get an error saying:

"Cannot open your default e-mail folders. Microsoft Exchange is not available. Ether there are network problems or the exchange Computer is down for maintenance"

If you run:

Get-LogonStatistics -Identity <email address>

Then have a look at the FullMailboxDirectoryName

This should match the users legacyexchangedn.  In my case, another user has the same address as a proxy address.

Just removed it and everything worked fine!

#Powershell and Get-ExchangeServer

#IAMMEC

Now that is cool.  Been playing with the cmdlet Get-ExchangeServer.  I wanted to get a group of different server names in one go, without having the run the cmdlet multiple times.

So I thought I would try and chuck an array at Get-ExchangeServer and see what it does?  It only bloody works ;-)

$s=@()
$s +="MyServers*"
$s += "Exch*"
$s | Get-ExchangeServer

Neat trick, and you can also pass arrays in as a script parameter too.  Found this: http://santoshbenjamin.wordpress.com/2008/09/30/powershell-and-arrays-as-named-parameters/

The key for a script or function parameter is [String[]]$Server=”*”

I Like it ALOT!

Forefront for Exchange Kaspersky Engine

#Exchange2010 #Exchange

Been getting lot of errors over the past couple of week with the Kaspersky engine not updating:

Log Name:      Application
Source:        GetEngineFiles
Event ID:      6012
Task Category: Engine Error
Level:         Error
Description:
Microsoft Forefront Protection encountered an error while performing a scan engine update.
   Scan Engine: Kaspersky
   Error Code: 0x80004005
   Error Detail: Description: An error occurred while loading the scan engine.

Found this:http://social.technet.microsoft.com/Forums/en/FSENext/thread/a198da95-b500-4627-820f-dd796ebe7fc5

The resolution works a dream:

Under C:ProgramData there is a folder called "KasperSky SDK" (you will have to enable viewing of hidden files to see if)

Rename the folder to say it for example  to "KasperSky SDK,old”

Update "Kaspersky" through the Forefront Console

Shweet!

Virtualized Exchange Storage: VMDK or RDM or…?

#Exchange #Exchange2010 #vmware

Matt sent me this .. an Interesting read

http://blogs.vmware.com/apps/2011/11/virtualized-exchange-storage-vmdk-or-rdm-or.html

One of the hottest topics I get into when talking to customers about virtualizing Exchange is storage. Not surprising considering the number of options available when we virtualize Exchange on vSphere. If you are not familiar with the common methods for provisioning storage in vSphere a brief description of each follows:

  • VMFS based virtual disk (VMDK) – VMFS is a high performance, clustered file system that allows concurrent access by multiple hosts to files on a shared volume. VMFS offers high I/O capabilities for virtual machines and is optimized for large VMDK files. VMFS volumes can be Fibre Channel or iSCSI attached.
  • Raw-device mappings (RDM) – RDM is a mapping file in a VMFS volume that acts as a proxy for a raw physical device, sometimes called a pass-thru disk. The RDM file contains metadata used to manage and redirect disk access to the physical device. RDMs can be Fibre Channel or iSCSI attached.

In early versions of ESX the virtualization overhead associated with deploying virtual disks (VMDK files) was much higher than it is today and why it was considered a best practice to place Exchange data files on physical mode raw-device mappings (RDM). As ESX and vSphere have evolved the performance difference between RDMs and virtual disks has become almost nonexistent. This leaves some questioning why we might choose to deploy RDMs for Exchange storage.

… “

New-MoveRequest Fails at 95%

#Exchange2010 #Exchange

I had a single mailbox, that I could not move from Exchange 2003 to Exchange 2010.  It moved from 2003 to another 2003 database no problem, but 2003 to 2010 no chance.

From the MoveRequest Log you could see this at the end:

12/10/2011 1:04:36 AM [CAS] Fatal error UpdateMovedMailboxPermanentException has occurred.
Error details: An error occurred while updating a user object after the move operation. –> Active Directory operation failed on MyDC. One or more attribute entries of the object ‘BadUser’ already exists. –> The attribute exists or the value has been assigned.
   at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.Microsoft.Exchange.MailboxReplicationService.IMailbox.UpdateMovedMailbox(UpdateMovedMailboxOperation op, ADUser remoteRecipientData, String domainController, ReportEntry[]& entries, Guid newDatabaseGuid, Guid newArchiveDatabaseGuid, String archiveDomain, ArchiveStatusFlags archiveStatus)
   at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.<>c__DisplayClass3c.<Microsoft.Exchange.MailboxReplicationService.IMailbox.UpdateMovedMailbox>b__3b()
   at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
   at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.Microsoft.Exchange.MailboxReplicationService.IMailbox.UpdateMovedMailbox(UpdateMovedMailboxOperation op, ADUser remoteRecipientData, String domainController, ReportEntry[]& entries, Guid newDatabaseGuid, Guid newArchiveDatabaseGuid, String archiveDomain, ArchiveStatusFlags archiveStatus)
   at Microsoft.Exchange.MailboxReplicationService.LocalMoveJob.UpdateMovedMailbox()
   at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.UpdateAD(Object[] wiParams)
   at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
Error context: ——–
Operation: IMailbox.UpdateMovedMailbox
OperationSide: Target
Primary (62d90226-d9a1-4941-baa5-28104b5fab78)
12/10/2011 1:04:36 AM [CAS] Relinquishing job.

It turns out that in when looking in the AD at the user proxy addresses a couple of them had an Š instead of an S.

When you looked with Exchange, it showed the S and not Š

So it’s an extended ASCII character (_http://en.wikipedia.org/wiki/%C5%A0 (_http://en.wikipedia.org/wiki/%C5%A0)). 

When I have changed it to a “normal” S using ADSIEdit, the move then worked!

How funky! .. Interesting in the Get-Mailbox still tagged the mailbox as valid!

Virus of the week (2012-01-09)

#Exchange #Exchange2010 #Virus

So this is a summary of what Microsoft Forefront Protection for Exchange Server detected as a virus.

Trojan-Spy.HTML.Fraud.gen

  • Subject line:  "Botanical Gardens Boot Camp NOW STARTING"
  • Subject line:  "Just for Cardholders: Save an extra 10% on select TVs at Amazon.com"
  • Subject line:  "Bank of America Customer Service – Tell us what you think"
  • Subject line:  "PayPal – Your account has been limited!"

Win32/Pdfjsc.RF

MSWord/Dropper.B!Camelot   

  • File name:  "winmail.dat->Insurance.zip->1036775_4909136e-c76f-466a-a8fe-a935fb735dbd_TATAAIGFIRSTPLAN.doc"

    Forefront Protection for Exchange

    #Exchange #Exchange2010

    So it’s been annoying me, when Forefront sends you an email, the from address it is a bit pants, and I want to change it.  By default it’s ForefrontServerProtection@servername.server.

    I looked around the PowerShell add in for Forefront and drew a blank so after a bit of googling I found this: http://technet.microsoft.com/en-us/library/dd639362.aspx

    Essentially …

    Changing the From address for notifications

    FPE utilizes SMTP messaging for notification purposes, placing the message in the SMTP service Pickup folder and resolving the Exchange name with the Active Directory directory service. By default, the server profile used for identifying notifications is: ForefrontServerProtection@servername.server. However, you can change this server profile by modifying the FromAddress registry value.

    To modify the FromAddress registry value

    Open the Registry Editor and navigate to the following registry key:

    HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftForefront Server SecurityNotifications

    Modify the default value of FromAddress to the sender name you would like. Alphanumeric characters are acceptable. You may also use the at sign (@) or a period (.), but these characters cannot be the first or last character. Any illegal characters will be replaced with an underscore (_).

    You must restart the relevant Microsoft Exchange and Microsoft Forefront Server Protection services in order for this change to take effect.