Unified Communications News Tips and Tricks

What's New in Exchange Server 2010

David Figueiredo — Wed, 14 Oct 2009 14:42:11 GMT

http://technet.microsoft.com/en-us/library/dd298136(EXCHG.149).aspx

What's New in Exchange Server 2010

[This is pre-release documentation and subject to change in future releases. This topic's current status is: Writing.]

Applies to: Exchange Server 2010

Microsoft Exchange Server 2010 brings a new and rich set of technologies, features, and services to the Exchange Server product line. This topic includes a list of the new features and functionality that are included in Exchange 2010. The list isn't comprehensive, but it provides important information to use when you're planning, deploying, and administering your Exchange 2010 organization. This topic also includes information about some of the limitations of this release and features from Exchange Server 2007 that have been removed.

New Rights-Protected E-Mail Functionality with Active Directory RMS

The following is a list of new rights-protected e-mail functionality with Active Directory Rights Management Services (AD RMS) that has been included in Exchange 2010:

Transport rules to apply AD RMS protection to messages based on conditions.
Persistent protection of attachments in rights-protected messages.
Support for AD RMS templates.
An Internet confidential AD RMS template for protection over the Internet.
AD RMS protection for Unified Messaging voice mail messages

New Transport and Routing Functionality

The following is a list of new transport and routing functionality that has been included in Exchange 2010:

Cross-premises mail routing An organization can choose to outsource some of their mailboxes to a hosted solution while maintaining their on-premises deployment. For example, a university can choose to host the mailboxes for all faculty and staff in their on-premises deployment and use a hosted solution for student mailboxes. Exchange 2010 allows routing of messages between the on-premises and hosted mailboxes.
Enhanced disclaimers Exchange 2010 lets you add disclaimers that can include hyperlinks, images, and HTML-formatted text. You can also insert Active Directory attributes that are substituted for the sender's attributes when a disclaimer rule is triggered.
Transport rules integration with AD RMS Exchange 2010 gives you the ability to create rules that require AD RMS protection based on keywords or patterns.
Moderated Transport Exchange 2010 provides an approval workflow for sending messages to recipients. When you configure a recipient for moderation, all messages sent to that recipient must go through an approval process.
Shadow redundancy Messages that are submitted to an Exchange 2010 Hub Transport server are stored in the transport database until the next hop reports successful delivery of the message. If the next hop doesn't report successful delivery and it fails, the message is resubmitted for delivery.
Transport Dumpster truncation based on log copy status When messages that are in the dumpster are replicated to all mailbox databases, they're removed from the dumpster.
Latency SLA management Exchange 2010 Transport lets you measure service levels delivered relative to your service level agreement (SLA) goals. Exchange 2010 gives you the ability to measure latencies for each hop, as well as end-to-end latency.
Transport database improvements Performance improvements in the Transport database result in reduced database I/O per second (IOPS) per message, which increases message throughput.

New Permissions Functionality

In Exchange 2010, Role Based Access Control (RBAC) has replaced the permissions model that was used in Exchange 2007. RBAC lets you define extremely broad or extremely precise permissions models based on the roles of you administrators and users.

For administrators and specialist users, management role groups define what these users can manage in the organization. Role groups associate role group members to a set of management roles that define what the members can do. By adding or removing users as members of role groups, and adding or removing role assignments to or from a role group, you can control what aspects of the organization the members can manage.

For end users, management role assignment policies define what users can configure on their own mailbox. Assignment policies are applied to every mailbox either by default or manually, and enable you to control whether users can change their personal information, contact information, distribution group membership, and so on.

Both group groups and role assignment policies are assigned management roles. Management roles control access to the cmdlets and parameters required to perform a task. For example, if a cmdlet exists on a management role, and that role is assigned to a role group, the members of that role group can then use that cmdlet.

For more information about RBAC, see Overview of Permissions.

New High Availability Functionality

Exchange 2010 integrates high availability into the core architecture of Microsoft Exchange to enable customers of all sizes and in all segments to be able to economically deploy a messaging continuity service in their organization.

Exchange 2010 includes many changes to its core architecture. The following features in Exchange 2007 and Exchange 2007 Service Pack 1 (SP1) no longer exist in Exchange 2010:

Local continuous replication (LCR)
Single copy clusters (SCC)

In addition to these features, the concept of a clustered mailbox server no longer exists in Exchange 2010. Two other features, cluster continuous replication (CCR) and standby continuous replication (SCR), have been merged and renamed as a set of new features in Exchange 2010: incremental deployment, continuous mailbox availability, database mobility, database copies, and database availability groups.

For more information about Exchange 2010 high availability features, see New High Availability and Site Resilience Functionality.

New Messaging Policy and Compliance Features

Exchange 2010 compliance features make retention independent of users' mailbox management and filing habits, and ensure retention policies are applied continuously. The following is a list of new messaging and compliance features that have been included in Exchange 2010:

New interface for applying retention policies
Auto tagging for retention policies
Mailbox search features for cross-mailbox search with AQS support
New transport rules predicates and actions

For more information, see New Messaging Policy and Compliance Functionality.

New Outlook Web App Features

The following is a list of new features in Outlook Web App in Exchange 2010.

Favorites in the Navigation Pane
Search folders
Message filtering
The ability to set categories in the message list
Options in the Web management interface for Outlook Web App
A side-by-side view for calendars
Multi-client language support
The ability to attach messages to messages
Expanded right-click capabilities
Integration with Office Communicator, including presence, chat, and a contact list
Conversation view
The ability to send and receive text (SMS) messages from Outlook Web App
Outlook Web App mailbox policies

New Unified Messaging Features

The following is a list of new Unified Messaging features that have been included in Exchange 2010:

Call answering rules
Additional language support including in Outlook Voice Access
Enhancements to name lookup from caller ID
Voice mail preview
Messaging Waiting Indicator
Missed call and voice mail notifications using text messaging (SMS)
Protected voice mail
Incoming fax support
Addressing to Groups (Personal Distribution Lists) support
Built-in Unified Messaging administrative roles

For more information about the new Unified Messaging functionality and new voice mail features, see New Unified Messaging Functionality and Voice Mail Features.

Web Management Interface

The following is a list of the features available in the new Web management interface for Outlook Web App.

Text messaging (SMS) integration
Voice messaging integration
Mailbox Search
Additional proxy addresses for mailboxes
Moderation and approval for distribution list submission

New Exchange Store and Mailbox Database Functionality

The following is a list of core store functionality that is included or has been changed in Exchange 2010:

Storage groups are deprecated.
Mailbox databases are no longer connected to the server object.
Extensible Storage Engine (ESE) has many improvements for high availability, performance, and database mobility.
The Exchange Store schema has been flattened.
Enhanced reporting with Public Folders

For more information about these changes, see New Exchange Core Store Functionality.

New Mailbox and Recipient Functionality

The following is a list of the new mailbox and recipient functionality that is included or has been changed in Exchange 2010.

Users can share information such as calendar free/busy and contacts with users who reside in a different organization
Scheduling and configuring resource mailbox calendar processing has been improved
You can now move a mailbox while the end user is still accessing it
New parameters have been added to the distribution group cmdlets to allow users to create and manage their own distribution groups in Outlook Web App and Outlook 2010
You can manage folder-level permissions for all folders within a user's mailbox
Bulk recipient management has been expanded to allow you to bulk manage recipient properties
You can send mail to recipients from the EMC

New Administration Functionality in the Exchange Management Console

The following is a list of the new core Exchange Management Console (EMC) features that have been included in Exchange 2010. The core EMC refers to new functionality that affects how you use the Exchange Management Console, not how you use specific features:

Customer Experience Improvement Program (CEIP)
Organizational Health
Community and Resources
Command logging
Property dialog command exposure
UI is RBAC aware

For more information about these features, see New Administrative Functionality in the Exchange Management Console.

New Administration Functionality in the Exchange Management Shell

The following is a list of features available in the new Exchange Management Shell:

Remote administration With the new Shell, you can connect to remote Exchange 2010 servers across the network with only the Windows Management Framework installed, which includes Windows PowerShell. For more information, see Overview of Exchange Management Shell.
RBAC integration The Shell works with RBAC to give you and your users access only to the cmdlets and parameters they're allowed to use. If your permissions don't allow you to configure a certain feature, you aren't given access to the cmdlets, parameters, or both, that manage that feature. For more information, see Understanding Role Based Access Control.
Administrator audit logging Actions that result in the modification of Exchange organization configuration and other object properties in the Exchange Management Console, the Web management interface, and the Shell can now be logged for later review. For more information, see Overview of Administrator Audit Logging.
Improved multiple-valued property syntax Instead of running multiple commands to add and remove values from a single property, you can now add and remove values with a single command line. For more information, see Multi-Valued Properties.

Exchange 2010 has been RTM’d

David Figueiredo — Thu, 08 Oct 2009 23:39:50 GMT

http://msexchangeteam.com/archive/2009/10/08/452775.aspx

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.

Windows 7 and Windows 2008 R2 Released To Manufacturing

David Figueiredo — Thu, 23 Jul 2009 16:43:37 GMT

http://windowsteamblog.com/blogs/windows7/archive/2009/07/22/windows-7-has-been-released-to-manufacturing.aspx

Release dates

http://windowsteamblog.com/blogs/windows7/archive/2009/07/21/when-will-you-get-windows-7-rtm.aspx

OCS front end service fails to start after KB967831

David Figueiredo — Thu, 21 May 2009 12:51:00 GMT

KB967831 patch will try to update OCS and afterwards will try to start RtcQmsAgent (aka Monitoring Agent)

If you dont use or configure this service it will never start, causing the rollback of the patch and with it the failure of the frontend service.

So just install MS messaging queue services (ServerManagerCmd -i MSMQ-Services) and MS messaging queue server (ServerManagerCmd -i MSMQ-Server) and reapply the patch that will apply with success since now he is able to start Monitoring Agent Service.

How to update OCS external address book url

David Figueiredo — Wed, 20 May 2009 13:04:21 GMT

Here’s how to update the external address book url:

Lcscmd /web /action:updatepoolurls /externalwebfqdn:<WebfarmFQDN> /poolname:<poolname

more info:

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

Presenting Exchange Server 2010

David Figueiredo — Wed, 15 Apr 2009 20:06:06 GMT

Presenting the Exchange 2010……

http://msexchangeteam.com/archive/2009/04/14/451032.aspx

OCS R2 Global settings changes in AD

David Figueiredo — Thu, 02 Apr 2009 13:04:20 GMT

After a new deployment, a great question mark appeared in my head when the follow popup appeared:

So what's next?

In some multidomain scenarios where the configuration stays in the root domain there where some reports of performance issues so the OCS team decided to enable the ability to change the the settings from the system container to the configuration partition in AD.

I’ve found this info on the The Three UC Amigos blog to how to do this move:

“How do I move the OCS global settings from System container to Configuration container?

Here are the steps from the R2 deployment guide:

You can run any of the following steps in read-only test mode by appending the /Check parameter to the MigrateOcsGlobalSettings command. This parameter prints the status of target objects and properties without making updates.

If any of the following steps fails to complete successfully due to network, replication, or permission issues, you can rerun the step until it completes successfully.

Important:

Before you begin the migration process, use the Office Communications Server snap-in to stop all Office Communications Server services on all Office Communications Servers.

To migrate global settings to Configuration container

1. Copy the global settings tree structure to the Configuration container by opening a command prompt and then running the following command:

cscript MigrateOcsGlobalSettings.vbs /Action:MigrateGlobalSettingsTree

2. Copy the global settings attributes to the Configuration container as follows:

cscript MigrateOcsGlobalSettings.vbs /Action: MigrateGlobalSettingsProperties

3. For Office Communications Server 2007 and Live Communications Server 2005 with SP1, run forest preparation to set permissions as follows:

Important:

Do not use the Office Communications Server Prep Forest wizard for this step. The wizard will show that the forest is already prepared, although the ACEs are not in the new container yet.

LcsCmd /Forest /Action:ForestPrep /global:configuration

For Live Communications Server 2005 with SP1, also run domain preparation in every domain the runs Live Communications Server as follows:

LcsCmd /Domain /Action:DomainPrep

Wait for the global settings tree to replicate to most forest global catalogs before proceeding to the next step.

4. Update server distinguished name (DN) references to the new global settings tree as follows:

cscript MigrateOcsGlobalSettings.vbs /Action: MigrateServerDnReferences /SearchBaseDN:<server search base DN>

Where /SearchBaseDN specifies the migration scope for servers.

5. Update DN references for user, contact, and inetOrgPerson objects to point to new global settings tree as follows:

cscript MigrateOcsGlobalSettings.vbs /Action: MigrateUserDnReferences /SearchBaseDN:<user search base DN>

Where /SearchBaseDN specifies the migration scope for users.

Wait for this step to complete before proceeding to the next step (for example, with stable network connectivity, it takes about one hour to migrate 30,000 users).

Use the Office Communications Server snap-in to restart the Office Communications Server services.

6. Try to send instant messages and perform some conferencing tasks to verify that the migration was successful.

Remove the original global settings tree structure from the System container as follows:

Important:

Do not perform this step until steps 5 and 6 are complete.

cscript MigrateOcsGlobalSettings.vbs /Action: DeleteSystemGlobalSettingsTree”

from:http://blogs.technet.com/ucedsg/archive/2009/02/27/where-should-i-store-my-ocs-r2-global-settings.aspx

OCS R2

David Figueiredo — Thu, 05 Feb 2009 14:01:27 GMT

Hi all

OCS R2 is out there, just check the virtual launch

http://www.microsoft.com/communicationsserver/r2-virtual-launch/event/default.aspx

How to check Mailbox Backup status

David Figueiredo — Thu, 29 Jan 2009 18:10:43 GMT

Hi all just a simple line to check with PS the backup status of your MBX:

Get-MailboxDatabase "Database Name Here" -status | select *backup* | fl

Exchange self signed certificates

David Figueiredo — Thu, 04 Dec 2008 14:00:04 GMT

Exchange self signed certificates are used to secure communications between exchange servers inside and outside your org, for example the communication between a Edge and a Hub server, this certificates expire after 12 months and there’s no workaround for this except to screen your event log to a event id like “an internal transport certificate expired” or “is going to expire within x days or hours”. This certificates are created upon the server installation. The process of renewal is quite simple just have to follow this:

Just get the thumbprint of the cert that is going to expire:

Get-ExchangeCertificate -DomainName CAS_SERVER.wathever.com

then clone it

Get-ExchangeCertificate -Thumbprint c4248cd7065c87cb942d60f7293feb7d533a4afc | New-ExchangeCertificate

And that’s it ! Good as new for more 12m

More info on this subject:

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

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

Network Monitor 3.2 Has been released

David Figueiredo — Thu, 18 Sep 2008 18:46:44 GMT

Netmon 3.2 is RTM and here's some extra info:

Externally Network Monitor 3.2 is available on Microsoft.com. The link is: http://www.microsoft.com/downloads/details.aspx?FamilyID=f4db40af-1e08-4a21-a26b-ec2f4dc4190d&DisplayLang=en.

So What's New in Network Monitor 3.2?
Process Tracking: Now you can identify rogue applications sending network data! View all the processes on your machine generating network traffic (process name and PID). Use the conversation tree to view frames associated with each process.
§Capture engine re-architecture to improve capture rate in high-speed networks. Network Monitor 3.2 drops significantly fewer frames that Network Monitor 3.1.
§ Find conversations: You asked for this. Many of our users found conversation tracking to be difficult to use as the view grew hard to manage, and it was difficult to correlate the frames they were seeing with the conversation nodes in the tree. Now, you can quickly isolate frames in the same network conversation. Just right-click on a frame and select a conversation to track, and you will see all the frames in that conversation. View TCP streams, HTTP flows etc.
§ Extensive parser set: Parsers for over 300 protocols! As before, the parsers are fully customizable.
§ Better parser management: By default only a subset of parsers are loaded. You can load the full parser set by going to ToolsOptionsParser and choose Full vs. Stub implementations.
§ CodePlex Ready: In the upcoming months, we plan to place all our Windows parsers on the Microsoft open-source CodePlex site and allow the community to modify and contribute parsers. You can find out more information on this here. This version of Network Monitor seamlessly integrates new parser packages.
§ Network Monitor API: Create your own applications that capture, parse and analyze network traffic!
§ More extensive documentation of the API and NPL. Access the documentation from Help NPL and API Documentation.
§ IA64 builds.
§ PCAP capture file support*.
§ ContainsBin Plug-in: Search frames for arbitrary byte sequences or strings.
§ . and more. See our Release Notes in the Help directory of the installation folder for a complete list of new features and known issues.
*This feature includes software developed by the University of California, Berkeley and its contributors.
This feature includes software developed by the Kungliga Tekniska Hogskolan and its contributors.
This feature includes software developed by Yen Yen Lim and North Dakota State University.