Exchange 2007 list all mailboxes with there SMTP addresses

If you want an overview off all the mailboxes in your Exchange 2007 environment with there primairy SMTP address and there extra SMTP aliasses, you can run the following command.

For a overview off all the options after the pipe command, you can the following command.

Get-Mailbox -Identity <useralias> | fl

Get-Mailbox | fl UserPrincipalName, ServerName, PrimarySMTPaddress, Emailaddresses

e2k7

 

 

Move a Information Store to another Exchange 2007 Server

Mailbox data isn’t specific to any one server. Why should access to this data be?  This is the reason behind the Database Portability feature, enabling a mailbox database to be mounted on any server in the same forest. In earlier Exchange versions, such an object could only be mounted in an RSG (Recovery Storage Group). Only mailbox databases are portable. Public Folder  data should be moved by replication, not file copy.

Database Portability cuts disaster recovery restore time:

1) Run eseutil /r <Enn> to commit all logs and put database into clean shutdown state.
<Enn> specifies the log file prefix for the storage group that contains the database into which you intend to replay the log files. The log file prefix specified by <Enn> is a required parameter for Eseutil /r. You can run the following Exchange Management Shell command to determine the log file prefix of a storage group:
Get-StorageGroup <Server_Name>\<StorageGroup_Name> | fl LogFilePrefix

exc_prf_01

2) Select a storage group on the replacement server and create the required database.
(Note: make sure the Storage Group and the Database have the same name as previous configuration on the crashed server).
3) Enable: EMC > Server Configuration > Mailbox > Database Management > Properties > General > This database can be over written by restore. Or: Set-MailboxDatabase <Database Name> -AllowFileRestore:$true.
4) Move database files (edb & log files, Exchange Search catalog) to appropriate location on new server.
5) Mount database.
6) Run Move-Mailbox -ConfigurationOnly — so accounts in AD will point to mailboxes on the replacement machine.
Get-Mailbox -Database <SourceDatabase> |where {$_.ObjectClass -NotMatch ‘(SystemAttendantMailbox|ExOleDbSystemMailbox)’}| Move-Mailbox -ConfigurationOnly -TargetDatabase <TargetDatabase>

After replication completes, when Outlook clients try to connect to their mail, the Autodiscover service will automatically redirect them to its new location.

Performing maintenance on your Exchange 2007 database(s).

When you’ve an up and running Microsoft Exchange 2007 environment, you’ve to perform some maintenance on your databases after some time. You can use the tool ESEUTIL for this job. Let’s have a look on some commands.

1) Open the commandline
2) Type in eseutil /?
3) Choose the right switch

———————————————————————–
Checking your database integrity: (Note: make sure you’ve dismounted your database(s)!! )
eseutil /g “E:\Database\SG01\MD01.edb” /t “E:\TMP\TEMPINTEG.edb”

eseutil /g: tool with the check integrity option
“E:\Database\SG01\MD01.edb”: location of the database(s)
/t “E:\TMP\TEMPINTEG.edb”: location of the temperary database file

ese_g_01    ese_g_02    ese_g_03
———————————————————————–

Repairing a corrupted or damaged database:  (Note: make sure you’ve dismounted your database(s)!! )
eseutil /p “E:\Database\SG01\MD01.edb” /t “E:\TMP\TEMPREPAIR.edb”

eseutil /p: tool with the repair option
“E:\Database\SG01\MD01.edb”: location of the database(s)
/t “E:\TMP\TEMPREPAIR.edb”: location of the temperary database file

r_ese_01    r_ese_02    r_ese_03
———————————————————————–

Offline defragmentation of a database:  (Note: make sure you’ve dismounted your database(s)!! )
eseutil /d “E:\Database\SG01\MD01.edb” /t “E:\TMP\TEMPDEFRAG.edb”

eseutil /d: tool with the offline defragmentation option
“E:\Database\SG01\MD01.edb”: location of the database(s)
/t “E:\TMP\TEMPDEFRAG.edb”: location of the temperary database file

d_ese_01    d_ese_02    d_ese_03

d_ese_04    d_ese_05
———————————————————————–


How to: Migrate mailboxes from Exchange 2003 to Exchange 2007 using ExMerge and PowerShell

When you have a up and running Exchange 2003 environment, and you want to migrate to an completely new Exchange 2007 environment, also with a new Active Directory, you can use the following tools to migrate the user mailboxes.

First of all we are gonna export the user mailboxes with ExMerge, after the export, we are gonna import the mailboxes with PowerShell. You can follow this article to provide the migration step by step.

I’ve installed an Microsoft Exchange 2003 Enterprise SP2 environment with 10 user mailboxes. I’ve also installed a Microsoft Windows XP workstation with Microsoft Office 2007.

exc2003_01    exc2003_02    exc2003_03

The allias of the user is the same as the User Logon Name.

By default, the Administrators, Domain Admins and Enterprise Admins have deny permissions on the Information Store. Make sure you configure the right permissions, so you have access to the mailboxes for making the export with ExMerge.

1) right-click on your Exchange Server, choose Properties
2) go to the Security tab, hit Administrators (also do this for Domain Admins and Enterprise Admins)
3) Advanced, hit Allow inheritable….Copy
4) hit Administrators, allow Send As and Receive As (also do this for Domain Admins and Enterprise Admins)
5) Restart the Microsoft Exchange System Attendant service.

excper_01    excper_02    excper_03

excper_04    excper_05    excper_06

Configure an MAPI profile for a user and generate some e-mail traffic. (e-mail, calendar items, tasks etc..)

off_01    off_02    off_03

Now we’re gonna export the user mailboxes with ExMerge.

 em_01    em_02    em_03

em_04    em_05    em_06

em_07    em_08    em_09

em_10    em_11

In the next post, we’re gonna import the user mailboxes into the new Microsoft Exchange 2007 SP1 environment using PowerShell.

Exchange 2007 SP1 Rollup 7 is available

Update Roll-up 7 for Exchange Server 2007 SP1 has been released. You can download it here.

As noted in previous posts, Exchange 2007 updates are cumulative and release-specific. This roll-up is for Exchange 2007 SP1, and supersedes all previous update roll-ups for Exchange 2007 SP1.

Update Roll-up 7 for Exchange Server 2007 SP1 has 50 fixes, including important fixes for SCR and IMAP4 issues.

Fixes for the following issues are included (details in KB960384):
946449 A non-read report message is sent after you perform a “Mark All as Read” operation against unread e-mail messages in Exchange Server 2007

949113 Unexpected modified instances of a recurring meeting may appear when you use Entourage to access a calendar on a computer that is running Exchange Server 2007

949114 Duplicate calendar items may appear when you use Entourage to access a calendar on an Exchange 2007 server

949464 The customized properties are removed in the recipients’ calendars when you send a meeting request that includes customized properties

950115 When a CDO 1.2.1-based application generates a meeting request that includes some European characters in the message body, these characters appear as question marks in Exchange 2007

951341 Users cannot read calendar items when they connect Exchange Server 2007 by using certain IMAP4 or POP3 clients

952778 Event ID 9874 is frequently logged on Exchange Server 2007 with Service Pack 1

953094 The value in the “Messages queued for submission” performance counter on the mailbox role of Exchange Server 2007 increases after a meeting request is delivered

954213 All Test commands that are related to the Client Access Server fail when you run the commands on an Exchange 2007 server in a disjoint namespace

954741 The UseRUSServer parameter does not work if an administrator has specified an RUS server on a target mailbox server

954898 The LegacyExchangeDN attributes for mail-enabled objects are incorrectly set in an environment that contains Exchange 2003 and Exchange 2007

955027 The Edgetransport.exe process may crash on a hub transport server that is running Exchange Server 2007 Service Pack 1

955462 You notice high CPU usage when the IMAP service is running on an Exchange 2007 Service Pack 1 server that has the CAS role

955778 You receive a Non-Delivery Report (NDR) message when you send an e-mail message to a non-SMTP address in an Outlook client that is using Cached mode

956069 A Non-Delivery Report (NDR) is generated when an Exchange Server 2007 user tries to send a message to a recipient who has a one-off FAX address that includes any characters that are larger than 0xFF in Unicode

956205 Corrupted characters appear in the Subject field or in the Location field of a recurring calendar item after a user adds DBCS characters to a field in a meeting occurrence by using an Outlook 2002 client

956275 An Exchange 2007 sender’s address is split into two separate addresses when an external recipient replies to the message

956455 The display name appears in a received message even though the property of the user mailbox is set to “Hide from Exchange address lists” in Exchange Server 2007

956687 Messages stay in the submission queue after you enable per-mailbox database journaling in an Exchange Server 2003 and Exchange Server 2007 coexisting environment

957019 Images cannot be pasted in an Exchange Server 2007 Outlook Web Access message body

957071 The MSExchange Transport service may crash intermittently on the Exchange 2007 server

957124 You do not receive an NDR message even though your meeting request cannot be sent successfully to a recipient

957227 The Exchange Management Console crashes when one or more domain controllers of a top-level domain are not reachable

957485 The Test-OwaConnectivity command returns a warning message in Exchange Server 2007 when there is a disjoint namespace

957504 The IMAP4 service crashes intermittently, and Event ID 4999 is logged on Exchange Server 2007

957683 An IP Gateway can still be used to dial out for a “Play on Phone” request after the IP Gateway is disabled

957834 Network shares are deleted and created intermittently by the replication service on an Exchange SCC cluster when SCR is enabled on the Exchange server

957947 The Exchange Information Store service may crash when an Entourage client synchronizes with an Exchange 2007 server

958091 You cannot update the task complete percentage to any value other than 0 or 100 in Outlook Web Access

958093 Voice mail messages are not stamped with the disclaimer that is defined in the transport rule in an Exchange Server 2007 environment

958128 Replication messages stay in a queue in a retry state after a public folder database is dismounted

958331 The Restore-StorageGroupCopy command may fail in an Exchange Server 2007 SCR environment

958444 Event 522 is logged when replication is resumed on a suspended Storage Group on an Exchange Server 2007 CCR or SCR environment

958472 An unexpected text string appears at the top of the message body when an Exchange Server 2007 user sends an HTML message by using Outlook Web Access

958552 The ByteEncoderTypeFor7BitCharsets setting does not take effect for the US ASCII character set after you install the hotfix that is mentioned in Microsoft Knowledge Base article 946641

958638 Exchange 2007 Server cannot parse X-Priority headers from clients that submit X-Priority headers that contain additional comments

958803 The EdgeTransport.exe process may stop responding in Exchange Server 2007 when the priority queuing feature is enabled

958872 The Map This Address feature in the contact page for an OWA client does not work in Exchange Server 2007

959100 Exchange Server 2007 cannot route e-mail messages to mail enabled Non-MAPI public folders that are hosted on an Exchange Server 2003 server

959135 Event 9673 occurs when the Microsoft Exchange Information Store service crashes on a computer that is running Exchange 2007 with Service Pack 1

959397 An increase in database size is generated unexpectedly when IMAP4 users use a Copy command in Exchange 2007

959434 The last logon time is not updated to reflect the logon times that have occurred after users log on to their mailboxes by using the Entourage client in an Exchange 2007 environment

959545 A redirection message in Outlook Web Access 2007 is incorrect when the message is translated to Korean

959671 The Manage Mobile Devices option is not displayed in Exchange Management Console after a mobile device re-synchronizes with an Exchange 2007 server

959952 The Set-Mailbox command does not change the AutomateProcessing attribute for an Exchange Server 2007 user when a regular user mailbox is converted from a room mailbox

960291 Outlook Web Access or an Exchange Web Service application does not correctly display a monthly or yearly recurring appointment or meeting request

960292 The MSExchangeIMAP4 service may crash intermittently after you apply an update rollup for Exchange Server 2007 Service Pack 1

960349 The Exchange Information Store service may crash after you enable tracing for the logon actions

961281 An error is returned when you enable SCR from any source in a child domain after you install Exchange Server 2007 Service Pack 1 Rollup 5

961395 The Exchange 2007 Unified Messaging server does not update the caller information if an external user makes a call

Exchange 2007 and Message Tracking

A nice feature in Exchange 2007 SP1 is the Message Tracking. Message tracking records the Simple Mail Transfer Protocol (SMTP) transport activity of all messages that are transferred to and from an Exchange 2007 computer that has the Hub Transport, Mailbox, or Edge Transport server role installed. You can use message tracking logs for message forensics, mail flow analysis, reporting, and troubleshooting. In this article I’ll give you some nice tips to configure and fine-tune the message tracking feature.

Remember, by default, message tracking is enabled on all Exchange 2007 computers that have the Hub Transport, Mailbox, or Edge Transport server roles installed.

You can enable or disable the message tracking performing the following steps:

1) Open the Exchange Management Console
2) Open Server Configuration, Hub Transport, Properties on your servername
3) Click on the tab Log Settings       

 mt_01    mt_02    mt_03

You can also configure the message tracking with the Exchange Management Shell. You can use the following command:

Set-TransportServer <Identity> -MessageTrackingLogEnabled <$true | $false>
(For example: Set-TransportServer SRVEXC01 -MessageTrackingLogEnabled $true)
——————————————————————

By default, the place of your message tracking logfiles is the following location:
DriveLetter:\Exchsvr\TransportRoles\Logs\MessageTracking
(For example: E:\Exchsvr\TransportRoles\Logs\MessageTracking
)

You can change this path with the Exchange Management Console, just browse to the new folder, or you can change this path with the Exchange Management Shell with the following command:
Set-TransportServer <Identity> -MessageTrackingLogPath <LocalFilePath>
(For example: Set-TransportServer SRVEXC01 -MessageTrackingLogPath E:\MessageTracking\Logs
)

Note! when you change the message tracking logpath, make sure this folder has the following permissions:
– Administrator: Full Control
– System: Full Control
– Network Service: Read, Write, and Delete Subfolders and Files
——————————————————————

By default, the maximum size for each message tracking log file is 10 MB. When a message tracking log file reaches its maximum size, Exchange 2007 opens a new message tracking log file. This process continues until either of the following conditions is true:
– The message tracking log directory reaches its specified maximum size.
– A message tracking log file reaches its specified maximum age.

After the maximum size or age limit is reached, circular logging deletes the oldest message tracking log files.
By default, the maximum size for the whole message tracking log directory is 250 MB. Circular logging deletes the oldest message tracking log files when either of the following conditions is true:
– A message tracking log file reaches its specified maximum age.
– The message tracking log directory reaches its specified maximum size.
You can change this size with the following command:
Set-MailboxServer <Identity> -MessageTrackingLogMaxDirectorySize <DirectorySize>
(For example: Set-TransportServer SRVEXC01 -MessageTrackingLogMaxDirectorySize 600MB)
——————————————————————

By default, the maximum age for any message tracking log file is 30 days. Circular logging deletes the oldest message tracking log files if either of the following conditions is true:
– The message tracking log directory reaches its specified maximum size.
– A message tracking log file reaches its specified maximum age.
You can change this age with the following command:
Set-TransportServer <Identity> -MessageTrackingLogMaxAge <Age>
(For example: Set-TransportServer SRVEXC01 -MessageTrackingLogMaxAge 90.00:00:00)

 To specify an age value, enter it as a time span, as follows: dd.hh:mm:ss where d = days, h = hours, m = minutes, and s = seconds. The valid input range for this parameter is 00:00:00 to 24855.03:14:07. Setting the value of the MessageTrackingLogMaxAge parameter to 00:00:00 prevents the automatic removal of message tracking log of files because of their age.
——————————————————————

To see all the settings of your TransportServer, you can use the following command:
get-transportserver | fl

In the next post I’ll let you see how to use the Exchange Message Tracking for easy tracing some e-mailtraffic.

Exchange 2007 SP1 Rollup 6 is available

Yesterday Microsoft has released Rollup 6 for Exchange 2007 SP1.

Update Rollup 6 for Exchange Server 2007 SP1 fixes the issues that are described in the following Microsoft Knowledge Base articles:

950675  Downloaded .xls file attachments are empty when you open the files by using Outlook Web Access on Exchange Server 2007 Service Pack 1

955443  Some free/busy messages are not replicated from Exchange 2007 to Exchange 2003 servers after some mailboxes are migrated from Exchange Server 2003 to Exchange Server 2007

956536  The Microsoft Exchange File Distribution service uses lots of memory and processor time when Exchange Server 2007 processes many OABs

956624  The Microsoft Exchange Transport service crashes continuously after you enable journal rule or deploy an antivirus application on an Exchange Server 2007 server

957748  The custom message class of contact object is overwritten by the normal IPM.Contact class when an Exchange 2007 server replicates the contact object to any other public store

959239  MS09-003: Vulnerabilities in Microsoft Exchange could allow remote code execution

More information you can find here. You can download Rollup 6 for Exchange 2007 SP1 here.

Microsoft Exchange TCP/IP Ports List

Here’s a list of the must used TCP & UDP IP ports that you could possibly need to use (or open in your firewall(s)).

TCP port 25 – SMTP
TCP port 26 – SSL secured SMTP
TCP port 110 – Post Office Protocol (POP3)
TCP port 995 – SSL secured POP3
TCP port 143 – Internet Message Access Protocol v. 4 (IMAP4)
TCP port 993 – SSL secured IMAP4
TCP port 80 – HTTP for Outlook Web Access
TCP port 443 – SSL secured HTTP for Outlook Web Access (HTTPS)
TCP/UDP port 389 – Lightweight Directory Access Protocol (LDAP)
TCP port 3268 – LDAP communications with an Active Directory Global Catalog Server
TCP port 119 – Network News Transfer Protocol (NNTP)
TCP port 563 – SSL secured NNTP
TCP port 135 – Remote Procedure Protocol (RPC) however it will also use ports 1024 and up as needed.
TCP/UDP port 53 – Domain Name System (DNS)
TCP port 102 – Mail Transfer Agent (MTA) *Only used in X.400 connections.
TCP/UDP port 88 – Kerberos