SQL Server Magazine

Exchange Tip: Understanding Exchange 2003 Transaction-Log Purges
From the Exchange tips section at MSD2D.com

If a backup is proceeding successfully, Exchange Server 2003 will flush all logs that have been committed to the database. So, typically, all committed transaction logs will be flushed if

• all databases in the storage group (SG) are backed up.
• all databases in the SG are mounted during the backup.

The Information Store (IS) determines which logs will be deleted by looking at the first log that hasn't yet been committed and deleting all previous log files. You can view the first uncommitted transaction log by running the following Eseutil command against the checkpoint (.chk) file:

eseutil /mk 

After the backup finishes, ESE Event ID 224 will be logged, specifying the series of transaction logs that will be deleted. For example, if the command

eseutil /mk E01.chk 

outputs E010000G, E0000001 through E010000F will be deleted. The purging process is sequential and purges all log files in the series with one exception: The purge process will stop if it tries to delete a nonexistent log file. So, in the previous example, if log file E010000A is missing, only logs E0100005 through E0100009 will be deleted. In this scenario, after the next backup, Exchange will again try to purge all log files that have been committed. This time, the previous Eseutil command outputs E01000016 as the uncommitted log file; thus, E010000B through E0100015 will be purged.

If your transaction logs aren't being purged, sooner or later you'll run out of disk space. If you have to create space in a hurry, don't move the log files; compress them instead. (In my lab, I've seen 3GB worth of log files compress to 1.5GB.) For recovery scenarios and for the purge process to finish successfully, you shouldn't move the transaction logs.

For more information about Exchange 2003 transaction logging, see the Microsoft articles "Exchange Transaction Logging in Exchange Server 2003" (http://www.microsoft.com/technet/prodtechnol/exchange/guides/UseE2k3RecStorGrps/d42ef86 0-170b-44fe-94c3-ec68e3b0e0ff.mspx), "XADM: Using Eseutil to Determine Which Logs Have Been Committed" (http://support.microsoft.com/?kbid=182961), and "How to remove Exchange Server transaction log files" (http://support.microsoft.com/?kbid=240145).
- Teo DeLasHeras

Exchange FAQs
Performing a GAL Lookup from a Windows Mobile 5.0 Phone

How can I perform a Global Address List (GAL) lookup from a Windows Mobile 5.0 phone?

Unlike earlier versions of mobile devices, which could display only local contact information, Windows Mobile 5.0 devices that have the new Messaging & Security Feature Pack installed can query the Exchange Server 2003 GAL in a variety of ways. To use a Windows Mobile 5.0 device to find GAL-based contact information, perform these steps:

1. From the Start menu, select the Contacts mobile applet.
2. Select Find Online.
3. Enter the name to search for, as Figure 1 shows, and click Find.
4. From the displayed list of matches, select the desired contact.

To use the GAL when you send email messages in which either the To: or Cc: box is selected, from the menu, click Add Recipient. On the Select a Contact screen, select Find Online, then enter the user's name. From the resulting list of matches, you can select the appropriate name.
- John Savill

Configuring Password Policies for Mobile Devices in Exchange 2003 SP2

How can I configure password requirements for mobile devices by using Exchange Server 2003 Service Pack 2 (SP2)?

The new Messaging & Security Feature Pack for Windows Mobile 5.0 lets you configure password policies from the Exchange server. To do so, follow these steps:

1. Start Exchange System Manager (ESM) by clicking Start, Programs, Microsoft Exchange, System Manager.
2. Expand Global Settings.
3. Right-click Mobile Services and select Properties.
4. Click Device Security.
5. Select the Enforce password on device check box and configure the required options, such as minimum password length, character combinations, and the duration of inactivity that will lock the device. You can also choose how many failed attempts will result in wiping the device, how often to refresh, and whether to allow access to devices that don't support the password settings. Also, you can use the Exceptions button to set exceptions to the policy. Click OK.
6. Click OK on the main Mobile Services dialog box.

The next time a device attempts to sync with the Exchange server, the mobile device will display a message, as Figure 2 shows, and the user will need to accept the new password policy before gaining further synchronization permission. After the user accepts the new password policy, he or she must enter a new password to satisfy the new password policy, as Figure 3 shows.
- John Savill

   Prev. page   [1] 2     next page