Category: Exchange 2007

event id parameters of message tracking logs defined

 In exchange 2007, the admin needs to understand the important parameters of Message Tracking logs. Whereas Exchange Server 2003/2000’s Message Tracking log was an easy-to-use application that shielded the user from this complexity, it also provided much less flexibility.
 
Message Tracking logs have a lot of details about a message as it originates from an internal user or external sender, and makes its way through the different stages of message routing and transfer, and finally gets delivered (or not). You can now track messages based on these events.
 
see below the event ids and descriptions. Proper understanding of these events will help for better troubleshooting and tracking of messages.
 
 
EventID Description

DEFER Message delivery delayed
DELIVER Message delivered to a mailbox
DSN A delivery status notification was generated.
Messages quarantined by the Content Filter are also delivered as DSNs. the recipients field has the SMTP address of the quarantine mailbox.
EXPAND Distribution Group expanded. The RelatedRecipientAddress field has the SMTP address of the Distribution Group.
FAIL Delivery failed. The RecipientStatus field has more information about the failure, including the SMTP response code. You should also look at the Source and Recipients fields when inspecting messages with this event.
POISONMESSAGE Message added to or removed from the poison queue
RECEIVE Message received. The Source field is STOREDRIVER for messages submitted by Store Driver (from a Mailbox server), or SMTP for messages
a) received from another Hub/Edge
b) received from an external (non-Exchange) host using SMTP
c) submitted by SMTP clients such as POP/IMAP users.
REDIRECT Message redirected to alternate recipient
RESOLVE Generally seen when a message is received on a proxy address and resolved to the default email address. The RelatedRecipientAddress field has the proxy address the message was sent to. The recipients field has the default address it was resolved (and delivered) to.
SEND Message sent by SMTP. The ServerIP and ServerHostName parameters have the IP address and hostname of the SMTP server.
SUBMIT The Microsoft Exchange Mail Submission service on a Mailbox server successfully notified a Hub Transport server that a message is awaiting submission (to the Hub). These are the events you’ll see on a Mailbox server.
The SourceContext property provides the MDB Guid, Mailbox Guid, Event sequence number, Message class, Creation timestamp, and Client type. Client type can be User (Outlook MAPI), RPCHTTP (Outlook Anwhere), OWA, EWS, EAS, Assistants, Transport.
TRANSFER Message forked because of content conversion, recipient limits, or transport agents

Working with message tracking logs

use this powershell command to get message tracking logs from a hub transport server, with start date of 1/13/2009 and end date of 2/13/09 at 11:20am respectively. this will also export to csv file on root of C:drive
get-messagetrackinglog -Server “servername”
 -Start “1/13/2009 11:20:00 AM” -End “2/13/2009 11:20:00 AM” -resultsize unlimited
| select timestamp, eventid, source, messagesubject, sender, internalmessageid, {_.recipients}, sourcecontext | export-csv c:msgtrak.csv
 
more examples:
Get-MessageTrackingLog -sender chuck@chuck.com
Get-MessageTrackingLog -sender “obi@obi.com” -eventID RECEIVE
Get-MessageTrackingLog -sender “barb@domain.com” -eventID DELIVER
Get-MessageTrackingLog -sender “erik@domain.com” -eventID DELIVER -Start “10/01/2009 9:00AM” -End “10/03/2009 5:00PM”
formatting the output
Get-MessageTrackingLog -sender obi@domain.com -eventID DELIVER -Start “10/01/2009 9:00AM” -End “10/03/2009 5:00PM” | Select timestamp,recipients,messagesubject
Get-MessageTrackingLog -sender “Mike@domain.com” -eventID DELIVER -Start “10/01/2009 9:00AM” -End “10/03/2009 5:00PM” -ResultSize 25

Configure Sync’em for Exchange 2007 Access

These are the info you need to configure Sync’em to connect to Exchange server 2007
WS Username: Username
WS password: password
Exchange server address: owa.domain.com
Windows domain: Domain
Exchange email address: type your exchange email address
Make sure you check use only secure communications
If you follow the instructions listed, sync’em will be able to connect to exchange server and start synchronizing your folders as configured.

How to rebuild Full-Text Index Catalog for Exchange server

issue: Customer complained of not being able to search mail through Outlook web access
 
resolution
 
Find out customer’s home server/db. Check the server to see the last date files were indexed. Confirm customer’s complaint with your finding. If indexing isn’t running properly
 
follow these steps to resolve
 
1. go to exchange powershell
2. type net stop MSExchangeSearch. this will stop the search service and indexer
3. go to the index directory and delete the index catalog folder. You can delete the catalogs for all storage groups as needed
4. go back to the shell and type net start MSExchangeSearch
 
You are done. Check to make sure service started and customer is able to search mails via OWA

customer reports not being able to open attachments via webmail

customer reports not being able to open attachments via webmail
 
customer must have chosen public at the initial logon in OWA. Public doesn’t allow opening of attachments, but private setting does
 
to resolve, follow these steps:
 
using adsiedit, set the value of MsExchMailboxFolderSet attribute to 2080374783
This will reset all cas-mailbox values to true except ability to change password over the web
 

how to turn on diagnostic logging of services in exchange 2007

Use these commands to turn on diagnostic logging for information store
 
get-eventloglevel (this lists all services that can be logged extensively)
use the powershell commands below to set logging level (lowest, low, medium, expert)
 
set-eventloglevel -id ‘MSExchangeIS9002 SystemGeneral’ -level ‘expert’
 
set-eventloglevel -id ‘MSExchangeIS9000 privateGeneral’ -level ‘expert’

steps to create shared mailbox for customers

steps to create shared mailbox for customers. Note that ad accounts for shared mailboxes are disabled.
 
Customers can use shared mailboxes for shared calendaring.
customers should use sharepoint as the preferred method for for shared and collaborative calendaring.
 
use these steps below to create shared mailbox and assign full access to the owner
 
step 1 create new user mailbox with console or powershell
 
step 2 use powershell and type this command to convert mailbox to shared.set-mailbox pep-employees -Type:Shared
step 3  Assign full access to the owner using this command.
get-mailbox -id “ep-events” | add-mailboxpermission -user “ond1” -accessrights ‘FullAccess’

fixing cas-mailboxes running in lite Mode for web experience

A funny Exchange Cmdlet, and how to fix it: Set-CASMailbox

In Exchange 2007 you can implement Outlook Web Access segmentation both server-side and client-side. The server-side segmentation can be done using both the power of the Exchange Management Shell, and the Exchange Management Console. To disable particular features, you will need the set-casmailbox to do so. Please read on
Issue: User can only run Outlook web access(owa) in lite version regardless of browser used
Solution: I have to use the EMS cmdlet Set-CASMailbox, as is stated in Technet “The Set-CASMailbox cmdlet sets client access-related attributes for Microsoft Exchange ActiveSync, Microsoft Office Outlook Web Access, Post Office Protocol version 3 (POP3), and Internet Message Access Protocol version 4rev1 (IMAP4) for a specified user.”
When running the cmdlet Get-CASMailbox ivancriekinge | fl, I can see that by default all features are enabled:

So, by running the following cmdlet I believe I’m disabling the ability to change my password using Outlook Web Access:Set-CasMailbox ivancriekinge -OWAChangePasswordEnabled:$False
But, it seems that running the specified line, it seems that all features are disabled…
And if you would on the other hand explicitely enable one feature, the result would be the same, all other features would be set to disabled 🙂

Solution = AdsiEdit…
When you check the properties of the mailbox using AdsiEdit, you can see that by running the cmdlet specified above, Exchange has changed the value of the attribute msExchMailboxFolderSet. By default this value is not set for a user, when all features are disabled, the value gets the value of 0.
If we change this value again, the default value would be reinstated.
In order to disable one feature, it’s very useful to first use AdsiEdit, or the Shell and set the value of MsExchMailboxFolderSet to 2147483647. And then, use the Set-CASMailbox cmdlet to disable the one feature wanted.
To use the shell, use the following commands:

To reset the value of the parameter to the default <not set>, just run the following line:
Set-QADUser ‘<domainname>/<OU>/username’ -objectattributes @{msExchMailboxFolderSet=$Null}
To set the value of all properties (starting with OWA) to $True, just run the following:
Set-QADUser ‘<domainname>/<OU>/username’ -objectattributes @{msExchMailboxFolderSet=2147483647}

Value of 2080374783 sets all to true except for ability to change password over the web

Reference:

Ilse, http://www.Proexchange.be, retrieved on November 13, 2008