Unified Communications News Tips and Tricks : Exchange 2007

Exchange 2007 SP2 has been released

David Figueiredo — Tue, 25 Aug 2009 14:05:09 GMT

Hi all for all of those that were anxious for SP2 here’s the download link:

The download site is located here:

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=4c4bd2a3-5e50-42b0-8bbb-2cc9afe3216a

Some new features:

Enhanced Auditing – New Exchange auditing events and audit log repository enable Exchange administrators to more easily audit the activities occurring on their Exchange servers. It allows the right balance of granularity, performance, and easy access to audited events via a dedicated audit log repository. This simplifies the auditing process and makes review of audited events easier by segregating audited events in a dedicated location
Exchange Volume Snapshot Backup Functionality – A new backup plug-in has been added to the product that will enable customers to create Exchange backups when a backup is invoked through the Windows Server 2008 Backup tool. Exchange Server 2007 didn’t have this capability on Windows Server 2008 and additional solutions were required to perform this task.
Dynamic Active Directory Schema Update and Validation – The dynamic AD schema update and validation feature allows for future schema updates to be dynamic deployed as well as proactively preventing conflicts whenever a new property is added to the AD schema. Once this capability is deployed it will enable easier management of future schema updates and will prevent support issues when adding properties that don’t exist in the AD schema.

Public Folder Quota Management – SP2 enables a consistent way to manage quotas by improving the current PowerShell cmdlets to perform quota management tasks.

Centralized Organizational Settings – SP2 introduces new PowerShell option that enable centralized management of many of the Exchange organization settings.

Named Properties cmdlets – SP2 enables Exchange administrators to monitor their named property usage per database.

New User Interface for Managing Diagnostic Logging– SP2 enables Exchange administrators to easily configure and manage diagnostic logging from within the Exchange Management Console.

Standard NDR codes table and troubleshooting

David Figueiredo — Tue, 14 Oct 2008 19:07:45 GMT

NDR status codes and corresponding error conditions

NDR status code

Event log message ID

Event log message severity

Event log message text

Possible cause

Troubleshooting

4.3.1

3001

Error

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

An out-of-memory error occurred. A resource problem, such as a full disk, can cause this problem.

Another possible cause of this error is that your Transport queue is on a FAT partition and the service has reached a Windows-imposed limit on the number of concurrent file handles opened by IIS.

Instead of getting a disk full error, you might be getting an out-of- memory error.

Ensure that your Exchange server has enough disk storage. If possible, move your mail queues to an NTFS disk partition.

4.3.2

3002

Informational

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

Available in Exchange 2000 Service Pack (SP) 1 and later. This NDR is generated when a queue has been frozen.

Unfreeze the queue.

4.4.1

3003

Warning

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

The destination server is not responding. Transient network conditions can cause this error. The Exchange server automatically tries to connect to the server again and deliver the mail. If delivery fails after multiple attempts, an NDR with a permanent failure code is generated.

Monitor the situation. This may be a transient problem that may correct itself.

4.4.2

3304

Warning

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

A connection dropped between the servers. Transient network conditions or a server that is experiencing problems can cause this error. The sending server will retry delivery of the message for a specific time period, and then generate further status reports.

Monitor the situation as the server retries delivery. This may be a transient problem that may correct itself.

4.4.6

3005

Error

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

The maximum hop count was exceeded for the message.

This non-delivery report can also be caused if a looping condition exists between sending and receiving servers that are not in the same Exchange organization. In this situation, the message bounces back and forth until the maximum hop count is exceeded.

A configuration error in the e-mail system can also cause the message to bounce between two servers or to be forwarded between two recipients.

The maximum hop count is a property set on each virtual server and you can manually override it.

The default maximum hop count is 15.

You should also check for situations that might cause looping between servers.

4.4.7

3006

Warning

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

The message in the queue has expired. The sending server tried to relay or deliver the message, but the action was not completed before the message expiration time occurred. This message can also indicate that a message header limit has been reached on a remote server, or some other protocol time-out occurred while communicating with the remote server.

This message usually indicates an issue on the receiving server. Check the validity of the recipient address and determine if the receiving server is configured correctly to receive messages.

You may have to reduce the number of recipients in the message header for the host about which you are receiving this error. If you resend the message, it is placed in the queue again. If the receiving server is available, the message is delivered.

4.4.9

3007

Error

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

This indicates a temporary routing error or bad routing configuration. Possible causes are:

· First scenario: Someone configured an SMTP connector to use DNS (rather than a smart host) and added a non-SMTP address space, such as an X.400 address, to this connector.

· Second scenario: Someone created a routing group, and a recipient in this routing group was supposed to receive mail. A routing group connector using DNS was used to bridge the routing group, and then this administrative or routing group was removed. Therefore, any mail sent to this routing group was sent in the MSGWIA.X500 format (the address encapsulation used for non-SMTP addresses); DNS does not recognize this format.Prior to Exchange Server 2003, messages sent to routing groups that no longer exist are stuck on a link.

Routing detects these situations, and Exchange returns DSNs.

· To remedy the first scenario, configure the SMTP connector to use a smart host, instead of DNS, to resolve the non-SMTP address space.

· To remedy the second scenario, ensure that you moved all users in the removed administrative group or routing group to a valid group.

5.0.0

3008

Error

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

Note Prior to Exchange 2000 SP1, the following codes appeared under the 5.0.0. code:

· 4.3.2

· 5.4.0

· 5.4.4

· 5.5.0

The categorizer failed; this is a permanent failure. Possible causes include:

· There is no route for the given address space; for example, an SMTP connector is configured, but this address does not match.

· DNS returned an authoritative host that was not found for the domain.

· The routing group does not have a connector defined; mail from one server in one routing group does not have a route to another routing group.

· An SMTP error occurred.

On one or more SMTP connectors, add an asterisk (*) value as the SMTP address space; verify that DNS is working; ensure that routing groups have connectors connecting them.

5.1.0

3009

Error

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

This NDR is caused by a general categorizer-based failure (bad address failure). An e-mail address or another attribute could not be found in Active Directory. Contact entries without the targetAddress attribute set can cause this problem. Another possible cause could be that the categorizer is unable to determine the homeMDB attribute of a user. The homeMDB attribute corresponds to the Exchange server on which the user's mailbox resides.

Another common cause of this NDR is if you used Outlook to save your e-mail message as a file, and then someone opened the message offline and replied to the message. The message property only preserves the legacyExchangeDN attribute when Outlook delivers the message, and therefore the lookup could fail.

Either the recipient address is incorrectly formatted, or the categorizer was not able to resolve the recipient properly. The first step in resolving this error is to check the recipient address and resend the message.

5.1.1

3028

Informational

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

The e-mail account does not exist in the organization where the message was sent. This can occur when users move to new locations within a site. For instance, if a former Administrative_Group_1 user moves to Administrative_Group_2 and then replies to an old message or does not re-create an Outlook profile, an old Administrative Group style LegacyDN address will be used, and this NDR is issued. Likewise, sending mail to obsolete personal address book entries results in this error.

Also, if you configured your SMTP contact with invalid SMTP characters (as per RFC 821), the categorizer rejects the delivery with this diagnostic code.

Either the recipient address is formatted incorrectly, or the categorizer was not able to resolve the recipient properly. The first step in resolving this error is to check the recipient address, and resend the message.

5.1.2

3031

Error

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

The recipient has a non-SMTP address that can't be matched to a destination. The address does not appear to be local, and there are no connectors configured with address spaces that contain the recipient's address.

Verify that the recipient's address was entered correctly. If the recipient's address is in a non-SMTP e-mail system that you specifically want to provide mail delivery to, you will need to add the appropriate type of connector to your topology and configure it to provide service to the recipient's e-mail system.

5.1.3

3010

Error

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

This message indicates a problem with the address syntax; this means that the recipient address appears incorrectly on the message. Possible causes are

1) You configured a contact with a targetAddress attribute with no address type.

2) Exchange 5.5 allows an SMTP recipient policy which violates RFC821 (SMTP standards) For example, an Exchange 5.5 site and organization contain an invalid RFC821 domain name.

Having a mixed mode environment (Exchange 5.5 and Exchange 2000 servers) can cause invalid target addresses.

Also, examine the SMTP recipient policy and ensure that each mail domain for which you want to accept mail appears correctly.

5.1.4

3029

Error

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

Two objects have the same (proxy) address, and mail is sent to that address. This issue can also occur if the recipient does not exist on the remote server.

Check the recipient address to ensure that two objects do not share the address. Attempt to resend the message.

5.1.6

3011

Error

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

One possible cause of this NDR is that the user directory attributes such as homeMDB (the user's home mailbox store) or msExchHomeServerName (the server on which the user's mailbox resides) are missing or corrupted.

Check the user directory attribute's integrity, and rerun the Recipient Update Service to ensure the validity of the attributes that are required for transport have been updated in Active Directory (and the metabase).

5.1.7

3012

Error

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

The sender has a malformed or missing SMTP address, the mail attribute in the directory service. The categorizer cannot deliver the mail item without a valid mail attribute.

Check the sender directory structure, and determine if the mail attribute exists.

5.2.1

3013

Warning

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

Local mail is refused because the message is too large or the recipient’s mailbox is not mail-enabled. A missing Master Account Security ID (SID) number on the recipient can also cause this error.

Check access permissions as well as the message size. Check if the recipient has a SID in Active Directory. Check to ensure that the recipient mailbox is mail-enabled.

5.2.2

3000

Informational

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

This NDR is generated when the recipient's mailbox exceeds its storage limit.

In Windows 2000 or Windows 2003, the DSN is generated when the storage size of drop directory exceeds the SMTP virtual server disk quota.

The quota size is 11 times the maximum messages size or 22 MB if there is no max message size.

If the available storage size of the drop directory is within one maximum size message of the quota, or 2MB if no maximum message size is defined, the system assumes that this message causes the storage size to exceed the quota, so this DSN is generated.

Check the mailbox storage or the queue storage quota limit.

5.2.3

3014

Warning

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

The message is too large, and the local quota is exceeded. For example, a remote Exchange user might have a restriction on the maximum size of an incoming message.

Resend the message without attachments, or set the server or the client-side limit to allow a larger message size limit.

5.2.4

3032

Error

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

The recipient is a misconfigured dynamic distribution list. Either the filter string or the base DN of the dynamic distribution list is invalid.

Set the categorizer event logging level to at least the minimum level, and send another message to the dynamic distribution list. Check the application event log for a 6025 event or a 6026 event detailing which attribute is misconfigured on the dynamic distribution list object.

5.3.0

3015

Error

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

Exchange mistakenly attempted mail delivery to an incorrect MTA route.

Exchange 2003 can operate without the message transfer agent (MTA). If mail was mistakenly sent to the MTA, Exchange returns this DSN to the sender. This condition is enforced only if you have disabled the MTA service and used specific registry settings to disable the MTA/StoreDriver. A default configuration strands the misrouted mail on the MTA queues.

Check your routing topology. Use the WinRoute tool to ensure that the routes are properly replicated between servers and routing groups.

5.3.3

3016

Warning

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

When the Exchange remote server reaches capacity of its disk storage to hold mail, it could respond with this NDR. This error usually occurs when the sending server is sending mail with an ESMTP BDAT command. This error also indicates a possible SMTP protocol error.

Ensure that the remote server has enough storage capacity to hold mail. Check the SMTP log.

5.3.5

3017

Error

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

A mail-looping situation was detected. This means that the server is configured to loop mail back to itself. If you have multiple SMTP virtual servers configured on your Exchange server, ensure that they are serving unique incoming ports. Also, to avoid looping between local SMTP virtual servers, ensure that the outgoing SMTP port configuration is valid.

Check the configuration of the virtual server's connectors for loops and ensure that each virtual server is defined by a unique incoming port. If there are multiple virtual servers, ensure that none are set to "All Unassigned."

5.4.0

3018

Error

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

Possible causes include:

· Authoritative host not found in DNS.

· Smart host entry is incorrect.

· Fully qualified domain name (FQDN) in HOSTS file (fixed in Windows 2000 SP3).

· DNS failure occurred, or you configured an invalid IP address as your smart host.

· SMTP virtual server does not have a valid FQDN or lookup of your SMTP virtual server.

· A contact's SMTP domain does not resolve to any SMTP address spaces.

Use the DNS Resolver tool (Dnsdiag.exe) or Nslookup to check the DNS configuration. Verify that the IP address is in IPv4 literal format. Verify the valid DNS entry for the server/computer name in question. If you rely on an FQDN in a HOSTS file, update the entry in Exchange System Manager with a valid IP address or correct name.

5.4.4

3019

Error

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

Available in Exchange 2000 SP1 and later versions.

This NDR occurs if no route exists for message delivery, or if the categorizer could not determine the next-hop destination.

You set up a routing group topology, but no routing group connector exists between the routing groups.

Add or configure your routing group connector between routing groups.

5.4.6

3020

Error

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

A categorizer forward loop was detected. The targetAddress attribute is set on a mailbox-enabled user.

This common hosting configuration problem occurs when someone creates a contact in one organizational unit, and then uses the provisioning tool to create a user in another organizational unit with the same e-mail address.

This happens when contact A has an alternate recipient that points to contact B, which then has an alternate recipient that points back to contact A. Check the contact's alternate recipient. Check and remove the targetAddress attribute from mailbox-enabled users. For hosting, that is, sending mail from one user in one company in an organizational unit to a user in another company in a separate organizational unit, you should configure the following two related objects: User: SMTP proxy: user@contoso.com Contact: targetAddress: user@contoso.com; SMTP proxy: contact@fourthcoffee.com, where fourthcoffee.com is the name of the second company.

5.4.8

3021

Error

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

Available in Exchange 2000 SP1 and later versions.

This message warns of a looping condition, which may occur because one of the recipient policies includes a local domain that matches the FQDN of an Exchange server in the organization. When the categorizer is processing mail that is destined for a domain matching an Exchange server's FQDN, it returns this NDR.

Check your recipient policies. If a recipient policy contains an Exchange server's FQDN, you must remove that entry. Your recipient policy should not contain the FQDN of your server; instead, it should contain the mail domain only—for example, instead of server1.contoso.com, you enter contoso.com.

5.5.0

3022

Warning

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

A generic protocol error or an SMTP error causes this NDR. The remote SMTP server responds to a sending server's identifying EHLO with a 500-level error. The sending system will then terminate the connection and deliver an NDR indicating that the remote SMTP server cannot handle the protocol. For example, if a Microsoft Hotmail® e-mail account is no longer active, a 550 SMTP error will occur.

View the SMTP Log or a Netmon trace to see why the remote SMTP server rejects the protocol request.

5.5.2

3023

Error

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

A generic SMTP error occurs when SMTP commands are sent out of sequence. For example, a server attempts to send an AUTH (authorization) command before identifying itself with an EHLO command.

It is possible that this error can also occur when the system disk is full.

View the SMTP Log or a Netmon trace, and ensure there is enough disk storage and virtual memory for SMTP to operate.

5.5.3

3024

Informational

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

Too many recipients on a message can cause this NDR.

The recipient limit is a configurable setting. To resolve this issue, either increase the recipient limit or revise the message into multiple messages to fit the server limit.

Note:

The default recipient limit on an SMTP message is 5,000. To change this limit, start Exchange System Manager, expand Global Settings, right-click Message Delivery, click Properties, and then use the Defaults tab. This can also be a per-user setting in Active Directory.

5.5.4

3025

Error

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

The message contains either an invalid sender or an incorrect recipient address format.

One possible cause is that the recipient address format might contain characters that are not conforming to Internet standards.

Check the recipient address for nonstandard characters.

5.5.6

3026

Error

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

This message indicates a possible protocol error.

Check the X-LINK2STATE protocol and Event Log for possible failures.

5.7.1

3027

Informational

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

Possible causes include:

· General access denied, and sender access denied—the sender of the message does not have the required permissions necessary to complete delivery.

· You are trying to relay your mail through another SMTP server, and the server does not permit you to relay.

· The recipient may have mailbox delivery restrictions enabled. For example, if a recipient's mailbox delivery restriction is set to receive mail from a distribution list only, non-member's mail will be rejected and produce this error.

· New in Exchange 2003: An anonymous user attempted to send mail to recipients or distribution lists that accept mail only from an authenticated SMTP session.

Check system privileges and attributes for the contact, and try sending the message again. Also, to resolve other potential issues, ensure that you are running Exchange 2000 SP1 or later.

5.7.3

3033

Error

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3).

The sender prohibited

Update Rollup 4 for Exchange Server 2007 SP1 has been released

David Figueiredo — Thu, 09 Oct 2008 17:46:50 GMT

Hi all UR 4 for Exchange 2007 SP1 is out there here’s some useful info:

Download Link:

http://www.microsoft.com/downloads/details.aspx?FamilyId=8B492ED2-EA92-412F-A852-3AA1C58D9499&displaylang=en

Kb article with list of fixes:

http://support.microsoft.com/?kbid=952580

Be aware of the Exchange managed code services, the symptoms are Exchange services that don’t start after the update and the workaround is here:

944752 Exchange Server 2007 managed code services do not start after you install an update rollup for Exchange Server 2007

New version of Exchange 2007 Mailbox Server Role Storage Requirements Calculator v 16.0

David Figueiredo — Thu, 25 Sep 2008 13:00:05 GMT

There's a new version of Mailbox Server role storage requirements calc, you can get this new version here:

http://msexchangeteam.com/archive/2007/01/15/432207.aspx

Microsoft Virtualization support for Exchange and new Licensing Announcements

David Figueiredo — Wed, 20 Aug 2008 12:03:15 GMT

Hi all

There's been a major announcement about Microsoft Exchange support in virtualized environments and respective licensing.

About Exchange support here's the two major changes:

Microsoft now supports Exchange Server 2007 SP1 running Hyper-V or hypervisors validated under the Microsoft Server Virtualization Validation Program (SVVP).

Microsoft is waiving its 90-day license reassignment policy to enable customers who virtualize Exchange to move their licenses between servers within a data farm as often as necessary.

Support policies were also updated, and theres a new article called Microsoft Support Policies and Recommendations for Exchange Servers in Hardware Virtualization Environments. This article includes Microsoft's support policy and recommendations for running Exchange Server 2003 in a Microsoft Virtual Server 2005 R2 environment. It replaces Microsoft Knowledge Base article 320220, which previously detailed the policy and recommendations for this environment. In addition, this article includes Microsoft's support policy and Microsoft's recommendations for running Exchange Server 2007 SP1 in a hardware virtualization environment.

For all the ones that are planing a Exchange migration to a virtual environment:

Microsoft Support Policies and Recommendations for Exchange Servers in Hardware Virtualization Environments

The follow links provide more info about the licensing and support changes:

Microsoft press release - http://www.microsoft.com/Presspass/press/2008/aug08/08-19EasyPathPR.mspx
Volume Licensing Brief from WWLP - http://www.microsoft.com/licensing/resources/volbrief.mspx
Support policy for Microsoft software running in non-Microsoft hardware virtualization software - http://go.microsoft.com/fwlink/?linkid=3052&kbid=897615
Support partners for non-Microsoft hardware virtualization software - http://go.microsoft.com/fwlink/?linkid=3052&kbid=944987
Microsoft server software and supported virtualization environments - http://go.microsoft.com/fwlink/?linkid=3052&kbid=957006

How to Configure Exchange Services for the Autodiscover Service

David Figueiredo — Thu, 24 Jul 2008 19:57:00 GMT

Heres a nice article explaining how to configure Some Exchange servcices for Autodiscover.

http://technet.microsoft.com/en-us/library/bb201695.aspx

Exchange and Iphone.....Dude give me my WM back!!!

David Figueiredo — Thu, 24 Jul 2008 19:23:00 GMT

Hi all

Hi only knew Nokia implementation of Active Sync, and personally they have a limited implementation, like the lack of options to sync more than the Inbox, I’ve got at least 10 or 12 folders below Inbox and other ones in side of it but after this article I can see that Nokia isn’t the only one, there a lot of missing pieces in apple implementation of Apple IPhone, you can say “…so what I really don’t use my iPhone with my company email system” ok but if Apple wants to move ahead a make a presence in the Enterprise market this lack of features sure cool down the hype of this launches.

http://mobilitytoday.com/news/008688/apple_exchange_bug_iphone

Performance counters and thresholds for Exchange 2007

David Figueiredo — Thu, 10 Jul 2008 12:57:00 GMT

Common counters for all server roles

http://technet.microsoft.com/en-us/exchange/cc671175(EXCHG.80).aspx

Client Access Server

http://technet.microsoft.com/en-us/exchange/bb201674(EXCHG.80).aspx

Unified messaging

http://technet.microsoft.com/en-us/exchange/bb201671(EXCHG.80).aspx

Hub Transport Server

http://technet.microsoft.com/en-us/exchange/bb201704(EXCHG.80).aspx

Mailbox server

http://technet.microsoft.com/en-us/exchange/bb201689(EXCHG.80).aspx

Other useful white papers:

Continuous Replication Deep Dive

http://technet.microsoft.com/en-us/library/cc535020(EXCHG.80).aspx

Planning for Large Mailboxes with Exchange 2007

http://technet.microsoft.com/en-us/exchange/cc671168.aspx

Microsoft Exchange Server 2007 Management Pack for System Center Operations Manager 2007

David Figueiredo — Thu, 26 Jun 2008 14:11:41 GMT

Overview

The Microsoft Exchange Server 2007 management pack is designed to be used for monitoring Exchange 2007 events, collecting Exchange component-specific performance counters in one central location, and for raising alerts for operator intervention as necessary. By detecting, sending alerts, and automatically responding to critical events, this management pack helps indicate, correct, and prevent possible service outages or configuration problems, allowing you to proactively manage Exchange servers and identify issues before they become critical. The management pack monitors and provides alerts for automatic notification of events indicating service outages, performance degradation, health monitoring, and centralized management.
This Management Pack requires Operations Manager 2007 Service Pack 1.
This Management Pack requires the Operations Manager 2007 updates specified in Knowledge Base articles 950853, 951979 and 951380 (see the Management Pack Guide for details).
Release History:

10/9/2007 - Initial Release, version 6.0.5000.0
6/22/2008 - Updated Release, version 6.0.6278.12

Download link:

http://www.microsoft.com/downloads/details.aspx?familyid=1a83e112-8677-4e03-83c3-f1b7ebfc3a4b&displaylang=en&tm

Microsoft Exchange Server 2007 Management Tools (32-Bit) released

David Figueiredo — Thu, 08 May 2008 19:03:14 GMT

Exchange Server 2007 is a native 64-bit application that includes 64-bit management tools. You can use the management tools to administer your Exchange Server environment remotely. If the remote computer is running a 32-bit operating system, you will need to download the 32-bit management tools.

Download Link:

https://www.microsoft.com/downloads/details.aspx?FamilyID=6be38633-7248-4532-929b-76e9c677e802&DisplayLang=en

Create custom addresslist in Exchange 2007

David Figueiredo — Mon, 21 Apr 2008 13:32:00 GMT

In a first glance to the Address List creation Wizard it seem's that a old fashion query is missing from it, as usual we use Powershell to solve the issue.

The new way to create a custom address list has been simplified in Powershell, instead of the old headache that the LDAP queries in Exchange 2003 were we have now a simple syntax were we can choose all attributes that will filter our Custom address list.

In the following syntax we are creating a new address list that includes all users enabled mailbox that their offices is in Lisbon:

New-AddressList -Name Teste -RecipientFilter {((RecipientType -eq 'UserMailbox') -and ((office -eq 'Lisbon')))}

The full command description can be found here:

http://uat.technet.microsoft.com/en-us/library/aa996912.aspx

And the full list of Filterable properties can be found here:

http://uat.technet.microsoft.com/en-us/library/bb430771(EXCHG.80).aspx

How to Install Exchange 2007 SP1 Prerequisites on Windows Server 2008 or Windows Vista

David Figueiredo — Wed, 19 Mar 2008 14:04:11 GMT

Here's a good article that explains how to install the necessary prerequisites for all Microsoft Exchange Server 2007 Service Pack 1 (SP1) server roles on Windows Server 2008 or Windows Vista.

http://technet.microsoft.com/en-us/library/bb691354.aspx

Using Exchange Database Portability in Exchange 2007

David Figueiredo — Thu, 18 Oct 2007 11:39:36 GMT

This is a great feature of Exchange 2007, that was a real headache in Exchange 2003 if you all remember in "those days" if you want to mount a DB in another server a series of requisites were needed to do so (The worst of all was that the target server needed to have the exact same name has the old one, fact that in production environments were a major problem, and the alternative was mount it in a lab environment). So now with Exchange 2007 just have to put the DB in any server with any name mount it and change the users info trough PS. This sound very simple, doesn't it? but it is.. here's how:

The first step is to guarantee that the DB is in a clean state for that just run eseutil /mh NAME-OF-DATABASE.EDB against it

This should be the result

So the next step should be the creation of a new mbx in the destination server, this mbx shouldn't be mounted in the end, and we must allow it to be overwritten. Another point to consider is that the name of this database should be the same of the original.

New MBX

New-MailboxDatabase -StorageGroup <Server_Name>\<StorageGroup_Name> -Name <Database Name>

Allow it to be overwritten

Set-MailboxDatabase <Database Name> -AllowFileRestore:$true

(This can also be performed trough the Exchange Management Console)

Ok, so after this we just have to copy the original Database to the path defined for it, if you don't know were is it just check the database properties in the Exchange Management console.

Now we're ready to mount it

Mount-Database <Database Name>

And finally change the user account setting to point to the new server and Database to do so:

Get-Mailbox -Database NAME-OF-SERVER1\DATABASE-NAME |where {$_.ObjectClass -NotMatch '(SystemAttendantMailbox|ExOleDbSystemMailbox)'}| Move-Mailbox -ConfigurationOnly -TargetDatabase NAME-OF-SERVER2\DATABASE-NAME

After Active Directory replication your users will be able to access their Mailboxes, one last thing be aware that Outlook 2007 clients should be redirected automatically because of the auto discovery service, in Outlook 2003 you should manually change the users server.

Bulk creation of Exchange 2007 Mailboxes

David Figueiredo — Thu, 04 Oct 2007 12:00:00 GMT

So this week I had the need of some test's of integration with Exchange 2007, and the first show stopper was at the point of creating 1000 users for testing purposes. Ok the creation of the users in AD is easy just grab the old vbs scripts, now the Select All -> Enable Mailbox where is it??? ooops just forgot that this is Exchange 2007 users, well let's take a look at the Powershell notes:

And the result was this piece of cmdlet

get-user | where-object{$_.RecipientType –eq "User"} | Enable-Mailbox –Database "SERVER NAME\MBX NAME"}

Get all users -----> then enable mailboxes for each one in this Server and Mailbox

You can filter a little more by choosing the OU or other users attribute like department or Office

get-user –organizationalUnit CONTOSO OFFICE | where-object{$_.RecipientType –eq "User" -and $_.department –eq "Marketing"} | Enable-Mailbox –Database "SERVER NAME\MBX NAME"}

Set recipient limits in Exchange 2007

David Figueiredo — Thu, 02 Aug 2007 12:13:00 GMT

Ok continuing the quick tips for Exchange 2007 operations, here goes another useful task. By default I recommend to all my customers to define recipient limits to all users, just to avoid some "mistakes" like someone that selects all users in the GAL, to send some email that shouldn't be sent to Everyone, as well as some spam that sends emails with bulk recipients.

So there are several ways to establish limits in E2K7, Globally, by server, by receive connector, by transport.... my tip is to establish a limit in the internet receive connector:

Set-ReceiveConnector "Name of Connector" –MaxRecipientsPerMessage “Number of messages allowed per mail” *

* To check all connectors name just enter a "Get-ReceiveConnector" in the Edge Server

This will establish the recipient limit for mails received externally

Next step establish a limit to all users:

get-user | Set-Mailbox -RecipientLimits "Number of Messages allowed per mail"

Of course that you have to put some exceptions (Corporate emails etc.), for that just increase the mailbox limits:

Set-Mailbox "MAILBOX Name" -RecipientLimits "Number of Messages allowed per mail"

More info about mailbox limits:

http://technet.microsoft.com/en-us/library/bb124345.aspx