ESM archives - Exchange Me!

Exchange Me!:

ESM

Jan 12 2008   12:11PM GMT

Recipient Policies What Are They?



Posted by: John Bostock
ESM, Exchange, Information Store, Exchange databases, Mailboxes, RUS, Exchange Tracking Center, X.400, Recipient Policies

Recipient Policies What Are They?

Recipient policies are organisation wide objects held in the “Recipient Policies” container – a sub container of Recipients. When you install Exchange the program creates a default policy and you can then create as many policies as you want to after. Although you must keep the default policy and you cannot delete it.

What do they do?

Set a default value for the domain used by Exchange to reference files via IFS. (IFS provides access to the Exchange information store by using Win32 file system APIs)Generates email proxy address. RUS generates and sets email addresses on new mail enabled objects but you define the format for the addresses and the type of proxy address that RUS generates through policy.Controls how the mailbox manager processes mailboxes.

Enables SMTP virtual servers to accept incoming mail. When you make an installation of Exchange the virtual servers will accept email from the domain defined in the default policy, but you add policies to cover additional domains if you require.

The Recipient Update Service (RUS) is responsible for creating and maintaining E-Mail Addresses in your Exchange Organization. The Recipient Update Service creates an Entry (Recipient Update Service (Enterprise Configuration)) for the entire Exchange Organization for modifying objects in the Configuration Container Partition in Active Directory and one RUS for every Exchange enabled Domain in this Forest.

Exchange Install.After install there is one default policy created called “Default Policy” This policy contains Proxy address for the default SMTP domain and one for X.400 – You can add additional Proxy addresses to the default policy or have different Recipient Policies for different users.Note:If you want to remove old or unwanted E-Mail addresses, you must either remove the addresses manually in Active Directory Users and Computers or use an automated process. Or you can use LDIFDE.

Dec 20 2007   9:40AM GMT

Build numbers and release dates for Exchange Server



Posted by: John Bostock
ESM, Information Store, Exchange databases, Bridgehead Server, Exchange Tracking Center

How to tell what Exchange version you are using? Many of us know of course but Microsoft have build numbers to indentify exact builds.

To find your build: The easiest way is to open ESM>Administrative Groups>Domain Name>click on the servers folder and to the right you will see all your servers and under Server Version is the version type. Make sure you are running the latest service pack for the version you are using.

Version                                             Build number              Release date
———————————————————————————————-
Microsoft Exchange Server  4.0                      4.0.837                   April 1996
Microsoft Exchange Server  4.0 (a)                4.0.993                   August 1996
Microsoft Exchange Server  4.0 SP1               4.0.838                   May 1996
Microsoft Exchange Server  4.0 SP2               4.0.993                   August 1996
Microsoft Exchange Server  4.0 SP3               4.0.994                   November 1996
Microsoft Exchange Server  4.0 SP4               4.0.995                   April 1997
Microsoft Exchange Server  4.0 SP5               4.0.996                   May 1998

Microsoft Exchange Server  5.0                       5.0.1457                  March 1997
Microsoft Exchange Server  5.0 SP1                5.0.1458                  June 1997
Microsoft Exchange Server  5.0 SP2                5.0.1460                  February 1998

Microsoft Exchange Server  5.5                        5.5.1960                  November 1997
Microsoft Exchange Server  5.5 SP1                 5.5.2232                  July 1998
Microsoft Exchange Server  5.5 SP2                 5.5.2448                  December 1998
Microsoft Exchange Server  5.5 SP3                 5.5.2650                  September 1999
Microsoft Exchange Server  5.5 SP4                 5.5.2653                  November 2000

Microsoft Exchange 2000 Server                      6.0.4417                  October 2000
Microsoft Exchange 2000 Server (a)                 6.0.4417                  January 2001
Microsoft Exchange 2000 Server SP1                6.0.4712                  July 2001
Microsoft Exchange 2000 Server SP2                6.0.5762                  December 2001
Microsoft Exchange 2000 Server SP3                6.0.6249                  August 2002
Microsoft Exchange 2000 Server post-SP3       6.0.6487                  September 2003
Microsoft Exchange 2000 Server post-SP3       6.0.6556                  April 2004
Microsoft Exchange 2000 Server post-SP3       6.0.6603                  August 2004

Microsoft Exchange Server  2003                        6.5.6944                  October 2003
Microsoft Exchange Server  2003 SP1                6.5.7226                  May 2004
Microsoft Exchange Server  2003 SP2                6.5.7638                  October 2005

Microsoft Exchange Server  2007                        8.0.685.24 or 8.0.685.25  December 2006
Microsoft Exchange Server  2007 SP1                8.1.0240.006              November 2007


Dec 14 2007   7:24AM GMT

Exchange Message Tracking - A Great Tool!!



Posted by: John Bostock
Microsoft Windows, Mobile, ESM, Exchange, Message tracing, Message logging, Exchange Tracking Center

Exchange has a great feature called message tracking that enables you to track messages. It works for both directions inbound/outbound – it also does internal messages. This function has a low overhead so I leave it enabled so I can get my hands on the info when I want,  although I do have a large amount of emails that pass through my organization on a daily basis so I set log removal to be low.

—————————————————————————————————————————————————————–

Here is the scenario. Your Boss calls at the wrong moment as per usual raving about a SUPER important email message that never got delivered. So what do you do? This is when you need to know how to use Message Tracking so let’s have a look at how.

How to Enable

1.       Open ESM go to servers
2.       Right click on the server and choose properties
3.       Select these options “enable subject logging and display” “enable message tracking”
4.       “Remove log files” This option set to 30 days which is long enough. If you have massive traffic consider lower times say 7-10 days.
5.       Also check out the location of the log files. Keep them away from the main store on a separate drive if possible.

Now mine looks slightly different because I do mine through a server policy as I have multiple Exchange servers. Although greyed out you can see the ticks and where I store them.

Now let’s look at Tracking Messages.

Once tracking has been running for a while you will have collected some information, then we can track messages. Let’s look at how

1.       Open ESM and then go to tools
2.       Scroll down to Message Tracking Center
3.       Choose the server you want to track the message from. This of course will be the server that the user has his or her mailbox on, depending on whether you want to track inbound or outbound messages.

At this point we can search even though nothing else is configured. But this will result in heaps of results up to a max of 1000 every message since midnight will be processed. Best case - use the other fields to narrow the search results. Once the system finds the message you can double click it which will show what exchange did with the message.

Tracking log files will be stored (by default) in a folder located at x:\Program Files\Exchsrvr\servername.log, where x is the volume you have installed Exchange Server onto. Inside this folder you will find a text file for each day that logs are being retained for. You can open these files and work from them if you want, but I would recommend doing it in Excel as the files are tab-delimited and very hard to sort through otherwise.  

Ok so we have a great way of searching and finding out what has happened with an email. Now that’s it but we can advance things a bit by utilizing third party tools and REALLY bringing Message Tracking ALIVE.

Check out these links for advanced use of Message Tracking. If you search the web you will find various software, some users have created scripts to work with these logs - Just make sure you test them and not in your live enviroment :-)

Exchange Log Analyzer    Promodag Now This is great software