Forefront "Sterling" is on the lose...

For anyone wanting to test drive more details can be found at: http://blogs.technet.com/forefront/archive/2009/04/23/forefront-stirling-beta-2.aspx 

Last week, as part of introducing the Business Ready Security strategy, we publicly released beta 2 of Forefront codename "Stirling.". 

“Stirling” is an integrated security suite that delivers comprehensive protection across endpoint, application servers, and the edge.  It also integrates with existing infrastructure software, such as Active Directory, System Center, and Network Access Protection, for better protection and reduced complexity.

Go here to download and evaluate with trial software or pre-configured virtual machines.   Below is a video demo worth watching, too.  Stay tuned for more info on "Stirling," such as the Security Assessment Sharing capabilities that enable interoperability with partner solutions.

Thought i would write a quick note on this process as i just got myself a HP 2140 Netbook & i am installing Windows 7 on there right now. Just got the machine this morning so the process is not yet complete, but i also bought a new 120GB SSD SATA Drive to replace the drive that came with the 2140.

So, since the 2140 obviously does not come with a CD/DVD Drive we have to look for alternatives, mine is to use one of my 8GB USB Drives as i don't want to but a USB DVD Drive of course. First order of business (assuming you have a USB drive in hand that is capable of holding at least 2.5GB) is to make our USB Drive bootable.

(Note: This set of commands assumes that the USB flash drive is addressed as "disk 2".  you should double check that this is the case before proceeding with the cleaning as you could inadvertently wipe data in error. To check this change directory into the USB Drive at the command line & type in "list disk" this should return a result similar to:

Once you have verified that you are using the correct Disk # lets proceed with the formatting.

1. Start/Run type in CMD (opens the Command Line utility)
2. Change your working drive to that of the USB drive (e.g. C:\F: “This changes your current working drive from C:\ to F:\)
3. diskpart
4. select disk 2
5. clean
6. create partition primary
7. select partition 1
8. active
9. format fs=fat32
10. assign
11. exit

If you were a user of the Windows XP Power toys there was a tool in there that i used all the time called Image Resizer. Unfortunately it was not carried over to Vista but i just came across this cloned copy on Sourceforge.net

It is a 13MB package, here is the link if your interested in a copy:

http://sourceforge.net/projects/phototoysclone 

I have always found it a killer to load up your digital photos & see your space be just gobbled up by each image being 3MB + in size.

Anyway, hope this useful.

Shouldn't have downloaded that last movie… :)

http://news.cnet.com/8301-1023_3-10221666-93.html?tag=newsLeadStoriesArea.1

VMware, Inc. (NYSE: VMW), the global leader in virtualization solutions from the desktop to the datacenter, will host a webcast presentation to unveil the next generation virtualization platform from VMware. 

Join Paul Maritz, president and chief executive officer, VMware as he and other VMware leaders officially unveil how VMware is bringing cloud computing to businesses of all sizes.

Date: Tuesday, April 21, 2009

Time: 9:00am > 10:30 pm PT

To register please visit: http://www.vmware.com/landing_pages/nextgen.html

Want to learn more about the new features in Exchange 2010 in a more interactive way than via the Exchange 2010 TechNet documentation? Then I suggest you take this course over on the Microsoft Learning site.

Collection 6899: Exploring Features of Exchange Server 2010

Overview
This two-hour collection provides you with an overview of the new features in Exchange Server 2010. It also describes the enhancements made over Exchange Server 2007.

The clinics within this collection cover:

- New features in Exchange Server 2010
- Technology enhancements
- Management tools used in Exchange Server 2010
- Managing a Mailbox server
- Unified Messaging in Exchange Server 2010
- High availability features in Exchange Server 2010

Users completing this collection should have three or more years of experience working with previous versions of Exchange Server, including the implementation of Exchange Server 2007. They should be familiar with Active Directory, Exchange messaging, and SharePoint and fundamentals of Microsoft Office 2003, Microsoft Office 2007, Windows Server 2003, and Windows Server 2008. It is beneficial if they have experience with a Windows or command-line scripting.

The Tech·Ed Web site has some great reasons as to why you should attend this year, but I thought I would add a few more:

• Sessions, sessions, and more sessions.  In case you haven't looked at the Session List, there's 738 technical sessions available.
• Of the 738 sessions, 67 of them are Unified Communications sessions.
• If you review the 67 UC sessions, you'll see titles like:
  • UNC204 Introduction to Microsoft Exchange Server "14" 
  • UNC312 Archiving and Retention in Microsoft Exchange Server "14"
  • UNC313 High Availability in Microsoft Exchange Server "14" (this one is presented by yours truly)
  • UNC316 Microsoft Exchange Server "14" Architecture
  • etc., etc. (I think you know where this is going)
• You'll also find several Hands On Labs, interactive instructor led sessions, and more!
• If you need help convincing your boss that you should attend, we can help with that.
• If you need help convincing your friends and co-workers to attend, we can help with that, too.

The future is coming, and you can see it at Tech·Ed North America 2009!

Now that Exchange Server 2010 is available to download and try in Beta format, I wanted to provide a quick blog on how to install the Exchange Server 2010 Beta.

Installing Exchange Server 2010 begins with installing and preparing the operating system.  Exchange Server 2010 can be installed only on Windows Server 2008 Standard Edition or Enterprise Edition.  If you plan on trying out database availability groups and mailbox database copies, you will need to use the Enterprise Edition of Windows Server 2008. For more information about the requirements for Exchange Server 2010, see Exchange 2010 System Requirements.

Once the operating system has been installed, several pre-requisites must be installed.  These include:

• Operating system components, including RSAT-ADDS (needed on server that will perform schema updates), Web-Server, Web-Metabase, Web-Lgcy-Mgmt-Console, Web-ISAPI-Ext, NET-HTTP-Activation, Web-Basic-Auth, Web-Digest-Auth, Web-Windows-Auth, Web-Dyn-Compression, RPC-over-HTTP-proxy, Web-Net-Ext and Net-Framework.  You can install all of these components at one time (e.g., for the Mailbox, Client Access and/or Hub Transport Server roles) by running the following command:
  ServerManagerCmd -i RSAT-ADDS Web-Server Web-Metabase Web-Lgcy-Mgmt-Console Web-ISAPI-Ext NET-HTTP-Activation Web-Basic-Auth Web-Digest-Auth Web-Windows-Auth Web-Dyn-Compression RPC-over-HTTP-proxy Web-Net-Ext -Restart
  For more information about the prerequisites for Exchange 2010, including those for the Edge Transport server role, see Exchange 2010 Prerequisites.
  You might have noticed that Failover-Clustering is not listed as a pre-requisite. There is a feature in Exchange Server 2010 called a database availability group that does use Windows failover clustering technologies. However, thanks to another Exchange Server 2010 feature called incremental deployment, you no longer install failover clustering before installing Exchange.  If you decide to use a database availability group, you simply create one, and then add Mailbox servers to it. When you add a Mailbox server to a DAG, we install the Windows failover clustering feature and automatically create a cluster for you. So while you do need to have Exchange installed on an operating system that supports Windows failover clustering, you do not install the failover clustering feature manually, or ahead of time, and you don't manually create a cluster. It makes deploying highly available mailbox databases quick and easy.
  Exchange Server 2010 also supports installing the above pre-requisites by using an Answer File with ServerManagerCmd, and answer files are included in the \AMD64\Scripts folder.  To use them, you run ServerManagerCmd -ip <Name of File>.  For example:
  ServerManagerCmd -ip Exchange-CAS.XML
  I recommend that you don't use the XML Answer Files for Exchange-Typical or Exchange-MBX as is, because in the Beta build it mistakenly includs the Failover-Clustering feature, which does not need to be installed before Exchange is installed.  This is a remnant from the Answer Files we had in Exchange 2007 that we've since removed.
• Next, are the software pre-requisites, which include:
  • Microsoft .NET Framework 3.5
  • Windows Remote Management (WinRM) 2.0 CTP 3
  • Windows PowerShell 2.0 CTP 3
  • Update from KB 951725
  • Update from KB 950888
  • Update from KB 951116
  • Update from KB 952664
  • Update from KB 953290
  • Update from KB 958178

See Exchange 2010 Prerequisites for information about and links to other pre-requisites that might apply to your environment (e.g., for Edge Transport and Unified Messaging server roles, and for environments that use System Center Operations Manager). 

Once the above pre-requisites have been installed, check Microsoft Update for any additional updates that might be needed.  Make sure the system has been rebooted after installing any updates which require a reboot.

Now you're ready to install Exchange 2010.  You can perform the installation using the GUI or command-line version of Setup.  In this example, I'll use the GUI.

I'll start by launching Setup.exe from the AMD64 folder.  This launches the Exchange 2010 splash screen:

As you can see, the Exchange 2010 splash screen is very similar to the one we had in Exchange 2007.  Any needed pre-requisites which are detected, are greyed out, indicating they have been installed, and that you can proceed to the next step.  In this case, I can proceed directly to Step 4: Install Microsoft Exchange.

I click that link and it launches the GUI version of Exchange Setup, beginning with a file copy process, and the initialization of Setup.

Once Setup is initialized and the file copy process has completed, the Introduction page appears:

I click Next, and the Language Files Location page appears:

I don't have any additional language files, so I'll leave the default setting of Continue setup without language files and click Next.  The Language Pack Confirmation page appears:

I click Next, and the License Agreement page appears:

After reading the license agreement, I select I accept the terms in the license agreement and click Next.  The Error Reporting page appears:

Error reporting is very helpful to us, which in turn is helpful to our customers, as it enables us to gather a minimal amount of diagnostic data to troubleshoot and resolve errors and crashes more quickly. So I am going to choose Yes (Recommended) and click Next.  The Installation Type page appears:

Immediately, you might notice some differences from Exchange Server 2007.  First, the Custom Exchange Server Installation option no longer lists any clustered mailbox server roles.  That's because clustered mailbox servers don't exist in Exchange Server 2010.  Exchange 2010 includes a new feature called Incremental Deployment.  This feature enables to you configure high availability and site resilience for your mailbox database after Exchange has been installed.

Second, the default path for the Exchange Server installation is new and different. If I choose Custom Exchange Server Installation, the Server Role Selection page appears:

If I choose Typical Exchange Server Installation instead of Custom Exchange Server Installation and click Next, or once I've completed the Custom Exchange Server Installation choices and clicked Next, the Exchange Organization page appears:

I specify a name for my Exchange Organization, and then I click Next.  The Client Settings page appears:

If the Exchange organization uses Outlook 2003 or earlier, or Microsoft Entourage, then a public folder database is needed so that those clients can access system data, such as Free/Busy information. In that case, you would select Yes on this page.  Since my organization does not use Outlook 2003 or earlier, or Entourage, I can leave the default setting of No and click Next.

The Customer Experience Improvement Program (CEIP) page appears:

This program helps us improve our software by collecting data about how Exchange Server is used. I'll click Join the Exchange Customer Experience Improvement Program and specify an industry of Computer-Related Products/Services. 

I click Next. The Readiness Checks page appears, and Setup automatically performs readiness checks for any installed language packs, as well as the selected server roles to be installed.

As you can see, the readiness checks don't take much time at all.  Once all readiness checks have successfully passed, the Readiness Check page will look similar to this:

At this point, the system and server are ready for the installation to begin.  I click Install to start the installation of Exchange 2010 Mailbox, Client Access and Hub Transport server roles, as well as the Exchange Management tools (Exchange Management Console and Exchange Management Shell).

While Setup is progressing, a Progress page will be appeared:

Once Setup has completed successfully, the Completion page will appear:

As you can see, installing Exchange 2010 is quick and easy.  On my system, Setup took just under 10 minutes to complete.

I prefer to reboot the system before finalizing the installation. Uncheck the Finalize installation using the Exchange Management Console checkbox, and click Finish to complete the Setup process.  This returns Setup to the splash screen.  Click Close to close the splash screen, and when the Confirm Exit dialog appears:

Click Yes.

Then, reboot the server.  OK, technically, you don't need to reboot the server, but I do anyway.

The installation of Exchange Server 2010 is now complete.  Check out the Exchange 2010 TechCenter for documentation and other resources for Exchange 2010.

CREDIT TO: Scott Schnoll @ http://blogs.technet.com/scottschnoll/

This document describes steps necessary to configure Double-Take to provide high availability for Windows servers running Microsoft Exchange Server version 2000 or 2003. These procedures allow a secondary server to assume the identity and role of a failed Exchange server while maintaining the availability of Exchange services with minimal disruption or data loss.

That means that users will have access to the same mailboxes and public folders on a uniquely named target server that existed on the source server prior to a failure.

In addition to the Exchange Information Stores (mailboxes and public folders), there are many important aspects of an Exchange server configuration that are required for Exchange functionality following the loss of a production Exchange Server.

It is important to be aware of the overall production Exchange server configuration, and to configure the target server identically.

Requirements

1. Microsoft Windows 2003
2. Exchange Server 2003
3. Both the Source and target Servers must be in same AD Domain
4. Double take Software
5. Exchfailover utility version 1.24 from NSI Software

Preparing the Source Server

1. Install Windows 2003 Server OS and apply Service packs and patches as required
2. Join this Server to the Domain (Server should be a member Server)
3. Install Exchange 2003 Server on the Source with Service pack 2

NOTE:
Keep track of your installation selections and storage locations so that Exchange can be installed identically on the target server. You will need to know the exact names and locations for the following items:
a) Storage group names
b) Public and Private Store name
c) Log files and system paths
d) Log file prefix
e) Database names and paths
4. Install Double take Software and copy the ExchFailover.exe into the directory where double take is installed

Preparing the Target Server

1. Install Windows 2003 Server OS and apply Service packs and patches as required
2. Join this Server to the Domain (Server should be a member Server and join to the same domain as source)
3. Install Exchange 2003 Server on the Source with Service pack 2 and verify that the installation paths and storage group paths are same as source server
4. On the target server, use Exchange System Manager to configure the database so that it can be overwritten during a restoration.

a) In System Manager, right-click the server store name and select Properties.
b) On the Database tab, enable This Database can be overwritten by restore.
c) Repeat steps a and b for each information store that will be replicated from the source.

5. On the target, change the Exchange services that are automatic startup to manual startup. If an Exchange service is disabled because it is not necessary for your environment, leave the service disabled.
Microsoft Exchange System Attendant (MSExchangeSA)
Microsoft Exchange Information Store (MSExchangeIS)
Microsoft Exchange Event Service (MSExchangeES)
Microsoft Exchange MTA Stacks (MSExchangeMTA)
Microsoft Exchange Post Office Protocol (POP3Svc)
Microsoft Exchange Internet Message Access Protocol (IMAP4Svc)
Microsoft Exchange Management (MSExchangeMGMT)
Microsoft Exchange Routing Engine (RESvc)
Any other Exchange related services: Fax, Blackberry, Management software, and so on.

6. Install Double-Take on the target and reboot when the installation is complete. This will initialize Double-Take and stop the Exchange services because the services were set to manual.

7. Copy the ExchFailover.exe into the directory where double take is installed

Configuring Double-Take mirroring and replication

In this section, you will be creating your Double-Take replication set and establishing the Double-Take connection between your source and target servers.

1. On the source, open the Double-Take Management Console (Start, Programs, Double-Take, Management Console).
2. In the left pane of the Management Console, double-click on the target to login.
3. Again in the left pane, double-click on the source to login. Right-click on the source and select Properties. On the Source tab, enable Block Checksum All Files on a Difference Mirror and click OK.
4. Right-click the source and select New, Replication Set and enter the desired name for the replication set. Select your Exchange data to replicate to the target. You can use the GUI selection process or the Replication Set Properties dialog. Right-click the replication set name and select Save to save the replication set.
5. Drag and drop the replication set onto the target and the Connection Manager will open.
The Source Server, Target Server, Replication Set, and Route fields will automatically be populated. If you have multiple IP addresses on your target, verify the Route field is set to the correct network path. Select the One To One mapping so that the replication set data is transmitted to the same directory structure on the target.
6. Click Connect to start the mirror and replication processes.
7. Exchange continuously writes data to the disk causing the replication statistics in the Double-Take Management Console to constantly change, even when users are not logged in. Your data is protected after the mirror is complete and the Mirror Status has changed to Idle.

NOTE:
Be sure of the following caveats:
Select all of the Exchange directories, including the directories with the database and log files.
Exclude the \bin directory.
Exclude any application files (.dll and .exe) since Exchange is already installed on the target.
When creating a rule that excludes files based on a wildcard, you must include the full path to the wildcard. For example, to exclude all .dll files in the exchsrvr directory, the replication set rule should be c:\program files\exchsrvr\*.dll.
This completes about configuration

Note: In an Exchange 2007 environment BlackBerry Enterprise Server should NOT be installed on the mail server as the BES software is not 64BIT compatible. In the event BES is installed on the mail server is will change IIS from 64BIT to 32BIT mode, this will then cause sites like OWA to be disabled. Also before installing BES you MUST have public folders enabled and have an Offline Address book configured in Exchange 2007.

1. On the server you have selected to load BlackBerry Enterprise Server download and install “Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1” which is available from the Microsoft Download site (a.k.a ExchangeMapiCdo.EXE). This will install the CDO and MAPI DLLs which are no longer available in Exchange 2007. This replaces the previous requirement to have Exchange System Manager installed as in Exchange 2000 or 2003 environments. The current download link is as follows:
http://www.microsoft.com/downloads/details.aspx?FamilyID=e17e7f31-079a-43a9-bff2-0a110307611e&DisplayLang=en
2. Log onto your Exchange Server using an account which has permissions to create an account. Open the Exchange Management Console and create a service account called BESadmin.
3. From the Exchange 2007 server open the “Exchange Management Shell” which can be found in the Exchange program group. From EMS run the following two scripts to set the delegate control and required permissions:
get-mailboxserver <mail_server_name> | add-exchangeadministrator BESAdmin –role ViewOnlyAdmin
get-mailboxserver <mail_server_name> | add-adpermission -user BESadmin -accessrights GenericRead, GenericWrite -extendedrights Send-As, Receive-As, ms-Exch-Store-Admin
4. Open Active Directory and from the View menu select "Advanced Features". Then go to each user that will be added to the BES and open their properties, go to the security tab and add the user BESadmin and add the security permission "Send As". (This will overcome some MS patches that prevent BES sending emails). Methods are available to add BESadmin "Send As" rights to all users if required but this method ensures only the required users have permissions added.
5. Make BESadmin a local Administrator of the server where you will be installing the BES software. This is done by right mouse clicking my computer and selecting “Manage”. From Computer Management expand “Local Users & Groups” and select Groups. From Groups double click “Administrators” and add BESadmin.
6. On the BES server go to “Administrative Tools” and open "Local Security Policy" and then expand the "Local Policies" and "User Right Assignment". You need to add BESadmin to "Log on Locally" and log on as Service".
7. Log onto the server where you will be installing the BES using the BESadmin account. Extract the install files and run the install file. Normally you select "BlackBerry Enterprise Server" as the install option once prompted as most sites don't use the MDS services for custom applications (MDS is a much heavier install). Follow the prompts of the install and the server will be required to restart half way through the install. Restart the server and log back on as BESadmin and the install will continue. (Make sure the Connect Test works and the SRP ID etc is validated during the install)
8. After the install is finished open BlackBerry Manager, an error will appear about MAPI client which you can just hit OK. The MAPI setting windows will appear so just add the server name back in and select "Check Name", if it resolves just hit OK and the manager will start.
9. Within Blackberry Manager click on Blackberry Domain in the left column and then the users SERVERS tab in the centre section, select your server within this tab and view the properties below. Ensure that "SRP Status:" is Connected (This can take a few minutes the first time so refresh the screen a few times). Once your status is connected you can start adding users.
10. Within Blackberry Manager click on your server name (The blue server) in the left column and then the users TAB in the centre section, just add a user and the click on that user. You will see all the users’ properties and a drop down menu called "Service Access” and select “Set Activation Password” and set a password of “a” for example.
11. Turn on you BlackBerry device and ensure Wireless is enabled. Go into “Options/Settings” and “Time & Date” and set the correct zone and time etc. Then from the home screen go to enterprise activation and enter the users email address and enter the password that was set in step 10. Press the track wheel and select Activate. Within a minute you should get data returned which indicates the process is functioning correct.

Here is a PowerShell script to identify the top 10 users who have the biggest mailbox on your Exchange 2007 server and output the result to Internet Explorer.

$strComputer = (Read-Host "Enter The Server Name").Toupper()
$ie = new-object -comobject InternetExplorer.Application
$ie.visible = $True
$ie.navigate("About:Blank")
$ie.document.title = "Top 10 Mailbox Users On $strComputer"
$ie.toolbar = "1"
$ie.statusbar = ""
$BigMailUsers = Get-MailboxStatistics -server $strComputer |sort-object -Property totalitemsize -des |select-object Displayname, ItemCount,
@{name='TotalItemSize(MB)';expression={$_.totalitemsize/1MB}} -first 10 |Convertto-html
$ie.Document.Body.InnerHTML = $BigMailUsers
$ie.Document.body.Bgcolor = "MintCream"
$ie.Document.FgColor = "MidnightBlue"

If you use VMware in virtually any of its flavors, then you've probably become familiar with the list of files created in each folder you create for a virtual machine. Those files are used by the software to process the running of each virtual machine.

But what exactly is each file for? What does each do? Let's take a few minutes to look at the files, and specifically the file extensions, that you'll see within each virtual machine's folder to help you understand the role of each:

.VMDK -- These files are the actual hard disk of the virtual machine itself, and tend to be the largest file within the folder. You can consider the size of this file to be roughly equivalent to the size of either the disk itself (if you've chosen to use preallocated disks) or the size of the data currently stored on that disk (if you use growable disks).

.NVRAM -- Consider this file the BIOS of the virtual machine.

.VMX -- With typically one VMX file per folder, this file holds the configuration information for the virtual machine in a text format. Unlike almost all the other files you'll see, these files can be edited using any text editing program, a process that is actually required for some functionality that is not exposed in the GUI.

.VMXF -- This file, in XML format, includes additional information about the virtual machine if it has been added to a team. If a machine has been added to a team and then later removed, this file remains resident. This file can also be opened and read in a text editor.

.VMTM -- For virtual machines actively participating in a team, this file stores information about that team membership.

.VMEM -- These files, which contain a backup of the VMs paging file, are typically very small or non-existent when the virtual machine is powered off, but grow immediately to the size of configured RAM when the machine is powered on.

.VMSN and .VMSD -- When snapshots are created for a virtual machine, these files are created to host the state of the virtual machine. The VMSN file stores the running state of the machine, what you could consider the "delta" between the VMDK at the point of the snapshot and what has been processed up until the present time. The VMSD stores information and metadata about the snapshot itself.

.VMSS -- If you've suspected the state of your machine, this file contains the suspended state of that machine. These files typically only appear when virtual machines have been suspended.

Depending on the VMware product you use or the platform upon which it resides, these files may be slightly different. However, these files are mostly the same across all versions of VMware's products.

Credit: Greg Shields.

Neither Exchange 2007 nor Exchange 2007 SP1 is supported in production in a virtual environment. However, as stated previously, Microsoft Virtual Server is a good environment for training, labs, and demos. Exchange 2007 and Exchange 2007 SP1 are supported in production environments using only the 64-bit version of Exchange 2007, and currently neither Microsoft Virtual Server nor Microsoft Virtual PC supports 64-bit guest systems. Exchange 2007 and Exchange 2007 SP1 are also not supported in production in a virtual environment using virtualization software that is not Microsoft software. For details about the Microsoft support policy for third-party virtualization software, see Microsoft Knowledge Base article 897615, Support policy for Microsoft software running in non-Microsoft hardware virtualization software.

In addition to the missing Exchange Management Console interface for entering a product key as described in "Evaluations and Product Keys" later in this topic, two other features are not available in the 32-bit version of Exchange 2007:

• Automatic anti-spam updates from Microsoft Update. Only a licensed 64-bit version of Exchange 2007 can get automatic anti-spam updates from Microsoft Update.
• Large numbers of storage groups and databases. You can have a maximum of five databases per server in as many as five storage groups on the 32-bit version.

Microsoft supports Exchange Server 2003 running on hardware virtualization software (virtual machines) only when all the following conditions are true:

• The hardware virtualization operating system is Virtual Server 2005 R2 or a later version.

• The version of Exchange Server that is running on the virtual machine is Microsoft Exchange Server 2003 Service Pack 2 (SP2) or a later version.

• The Microsoft Virtual Server 2005 R2 Virtual Machine Additions are installed on the guest operating system.

• Exchange Server 2003 is configured as a stand-alone server, not as part of a Windows cluster.

• The SCSI driver that is installed on the guest operating system is the Microsoft Virtual Machine PCI SCSI Controller driver.

• The virtual hard disk Undo feature is not enabled.

Reasons to create an SMTP connector include:

• You are connecting to a Microsoft Exchange Server 5.5 computer in another routing group (site), and want to use SMTP.

• You want to configure either server-side or client-side ETRN/TURN.

• You want either to send or not to send ETRN/TURN.

• You want to request ETRN/TURN when sending messages.

• You want to request ETRN/TURN from different servers.

• You want to configure outbound security, and to do it one time and affect many outbound servers.

• You want to permit high, normal, or low message priorities for a domain.

• You want to permit system or non-system messages.

• You want to schedule the SMTP connector.

• You want to use different delivery times for oversize messages.

• You want to queue mail for remote triggered delivery.

• You want to send HELO instead of EHLO.

• You want to specify a specific address space.

• You want to set delivery restrictions.