O-Xchange Notes from the Field!

Friday, April 27, 2012

locate old meetings and change meeting organizer

Locate Old meetings and Change meeting Organizer

Imap user not able to login to Exchange 2010

Issue: Imap user not able to login to Exchange 2010
synopsis: User has been able to login to Imap using any imap client. However imap suddenly stopped working and won't accept the credentials. User was able to login to OWA or Outlook with same credentials
Resolution: Move user's mailbox to another database and Clear the move requests

Thursday, April 26, 2012

Tuesday, April 24, 2012

troubleshooting Outlook logon prompt for users

Synopsis: group of outlook users homed on Exch2007 reported logon prompt issues. Users(who already logged in the domain) get prompted to login upon launching Outlook. In some cases, users login successfully, but receive logon prompts intermittently
Systems/Software Affected: Outlook 2007, Outlook 2010, Exchange 2007
Things to check on Exchange 2007 CAS servers when such issues happen:
1. Please note that Issue could be related to a reboot of Domain Controller. Confirm with AD team prior to troubleshooting
2. Issue is also likely related to Offline Address Book (OAB)
login to the Exch2007 cas servers and confirm the following:
1. launch IIS manager and under default website
2. right click OAB, properties, directory security
3. make sure integrated windows authentication and basic auth are checked
4. Go to Exchange installation folder, for eg E:\program files\exchange server\client access
5. Right click on OAB, properties, ensure that authenticated users is in the ACE and check to make sure the group at least read and execute right
6. If all the settings are correct, you are done with your checks. If not, make the changes and do iisreset /noforce from the command prompt
as part of the test, you can type this url to verify you can reach the OAB xml file;

Thursday, April 12, 2012

Resolving Quarantined Mailboxes in Exchange 2010

Exchange 2010 has a security measure when it comes across a 'poisoned' mailbox' in its Information Store database. If it deems the mailbox 'dirty' or 'poisoned', it will quarantine the mailbox. This keeps it safe from corruption and crashing.
Usually, quarantined mailboxes will be released after some hours (2-6hrs). In some cases, that may not be feasible, as user will have to stay without access to email.
You can follow these steps to resolve if critical: (you must be admin to do these)

1.Run Get-MailboxStatistics -identity 'username' | fl
2.Copy the mailbox GUID and keep it handy.
4.Delete the key.
5.Restart the Information Store
Important repair considerations:
Consider repairing the mailbox upon expiration of 6hrs(release of mailbox from quarantine)
A. This example detects and repairs the folder view for the mailboxob@domain.com
New-MailboxRepairRequest -Mailbox obtest@domain.com -CorruptionType FolderView
B.This example detects and repairs all corruption types for mailboxes that have CustomAttribute2 set to RepairCorruption.
Get-Mailbox -Filter {CustomAttribute2 -like "RepairCorruption"} | New-MailboxRepairRequest -CorruptionType SearchFolder,AggregateCounts,ProvisionedFolder,FolderView
During the repair operation, there will be no mailbox access for the user.

The output of New-MailboxRepairRequest will be a number of Event IDs with a source of “MSExchangeIS Mailbox Store” and you will need to watch for the following events related to a repair request “0044,10045,01146,10047,10048,10049,10050,10051,10059,10062”

Tuesday, April 10, 2012

Use Pshell commands to mass delete spam from your mailbox

use a combination of get-mailbox plus search-mailbox to mass-delete unwanted content(such as spam, etc) from your mailbox
get-mailbox -id username | Search-Mailbox -SearchQuery subject:"spam",from:spamcop@fakesite.edu -DeleteContent