1.) First upgrade the CAS server(s)
2.) Then upgrade the HUB Transport server(s)
3.) Logon to the passive node
4.) Upgrade the passive node to Service Pack 3
 setup.com /mode:Upgrade
6.) Restart the server after the setup is completed succesfully
7.) Stop the CMS (Clustered Mailbox Server) on the active node (DOWNTIME!!)
 Stop-ClusteredMailboxServer MAILCLUSTER01 –StopReason “SP3 Upgrade”
8.) Move the CMS (Clustered Mailbox Server) to the passive node (DOWNTIME!!)
 Move-ClusteredMailboxServer MAILCLUSTER01 –TargetMachine CCR2 –MoveComment “SP3 Upgrade”
9.) On the passive node upgrade the CMS (Clustered Mailbox Server)
 setup.com /UpgradeCMS
10.) Bring the CCR cluster back online
 Start-ClusteredMailboxServer MAILCLUSTER01
11.) Upgrade the initial active node to Service Pack 3
 setup.com /mode:Upgrade
12.) Restart the server after the setup is completed succesfully
13.) Now you have an Exchange 2007 CCR cluster with Serivce Pack 3

Exchange 2007 SP3 brings this feature to the table. The option is disabled by default and can be turned on with a registry edit on the CAS server.

To enable the password reset feature,

1.) Log on to the CAS server with an admin account.
2.) In registry editor, navigate to HLKM\SYSTEM\CurrentControlSet\Services\MSExchange OWA
3.) Create the following DWORD value if it does not already exist. DWORD Name – ChangeExpiredPasswordEnabled, type – REG_DWORD and data set to 1.
4.) If the DWORD already exists, change the value from zero to one.
5.) Reset IIS from command prompt with the command iisreset /noforce

For the full release notes, you can browse to the following URL

Download Service Pack 3 for Microsoft Exchange 2007 here

Download details Update Rollup 1 for Exchange Server 2007 Service Pack 2 (KB972076)

This update rollup does not apply to Exchange Server 2007 Release To Manufacturing (RTM) or Exchange Server 2007 Service Pack 1 (SP1). For a list of update rollups applicable to Exchange Server 2007 RTM or Exchange Server 2007 SP1, refer to the Knowledge Base article KB937052.

Download details Update Rollup 1 for Exchange Server 2007 Service Pack 2 (KB971534)

——————————————-
We always talk about listening to customers and sometimes this is written off by many as ‘marketing speak’.  In fact, we do take feedback seriously and no input is more important to our engineering processes than your voice.

Earlier this year we made a decision in one direction, and due to the feedback we have received on this blog and elsewhere, we have reconsidered. In the coming calendar year we will issue an update for Exchange 2007 enabling full support of Windows Server 2008 R2. We heard from many customers that this was important for streamlining their operations and reducing administrative challenges, so we have changed course and will add R2 support.  We are still working through the specifics and will let you know once we have more to share on the timing of this update.

So, keep the feedback coming.  We are listening.

Kevin Allison
GM Exchange Customer Experience
——————————————-

So within a copple of months, there will be proberly full support for Exchange 2007 on Windows Server 2008 R2! This will be a great start of the new year 2010

• Exchange Server 2003 is not supported in Active Directory environments whose domain/forest functional levels have been raised beyond Windows Server 2003. However, Exchange Server 2003 SP2 can function against Windows Server 2008 Active Directory servers.
• Exchange Server 2007 is not supported on Windows Server 2008 R2. However, Exchange 2007 SP1 RU9 and SP2 are supported against Windows Server 2008 R2 Active Directory servers. In addition, Exchange 2007 SP1 RU9 and SP2 are supported in Active Directory environments whose domain/forest functional levels have been raised to Windows Server 2008 R2.
• Exchange 2007 SP2 is supported with PowerShell 2.0.

“Stand alone DC/GC can be Windows Server 2008 R2 and it is supported to have Exchange Server 2007 SP2 work against these DC/GCs.
There is NO support for any Exchange Server 2007 SP2 components (any roles, including admin tools) installed on Windows Server 2008 R2. Exchange Server 2007 SP2 will not even install on it – the pre-req check will fail during installation.”

So when you’re planning to upgrade to Microsoft Windows 2008 R2, keep in mind that you not upgrade your Exchange 2007 environment!

SCC (Single copy cluster)
was what I would call a traditional Exchange cluster which used shared storage to host the Exchange database.

CCR (cluster continuous replication)
was used to replicate Exchange database information between 2 Exchange server allowing for hardware and storage redundancy but was limited to 1 Active node and 1 Passive node.

SCR (standby continuous replication)
was introduced in Exchange 2007 SP1 to provide the ability to replicate Exchange databases to an disaster recovery location.

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

let’s update the Address Lists!

Set-AddressList “All Users” -IncludedRecipients MailboxUsers

Set-AddressList “All Groups” -IncludedRecipients MailGroups

Set-AddressList “All Contacts” -IncludedRecipients MailContacts

Set-AddressList “Public Folders” -RecipientFilter { RecipientType -eq ‘PublicFolder’ }

“Unable to edit the specified E-mail address policy. E-mail address policies created with legacy versions of Exchange must be upgraded using the ‘Set-EmailAddressPolicy’ task, with the Exchange 2007 Recipient Filter specified.”

Oké, let’s update the recipient policy! With the following command you can see the properties of this recipient policy.

Get-EmailAddressPolicy | fl Name,*RecipientFilter*,ExchangeVersion

Set-EmailAddressPolicy “Default Policy” -IncludedRecipients AllRecipients

After running this commands, you’re able to edit the “Default Policy” again.

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

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

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.

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

       
———————————————————————–

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

       
———————————————————————–

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

   
———————————————————————–

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.

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.

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

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

        

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

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

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       

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.

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.

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

First off all i’ve installed a Windows 2003 Server with HP Data Protector 6.0. (Note: if you’re using Exchange 2007, install patch DPWIN_307 or later)

After the installation we’re are going to deploy the HP Client to the Exchange 2007 server, for communicating with the Backup server.

The next step is configuring the device for the backup destination. In my situation it’s a backup to disk.

Now the device is created, we can go further with configuring the Exchange full Store backup.

In the next few days i’m going to configure the Exchange 2007 Single Mailbox backup.

- Locate the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange ADAccess key.
- Create the “CacheTTLUser” value
- Right-click MSExchange ADAccess, select New, and then select Key.
- Name the new key Instance0.
- Right-click Instance0, select New, and then select DWORD value.
- Name the new DWORD value “CacheTTLUser”.
- Right-click CacheTTLUser, and then click Modify.
- Enter a decimal value of 300 (5 minutes)

Alternately, copy this text file and paste it into a file called MailboxCache.reg, then import it into the registry of each of your Exchange 2007 Mailbox servers

———————————————————————-
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem]
“Reread Logon Quotas Interval”
=dword:000004b0
“Mailbox Cache Age Limit”
=dword:00000014
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange ADAccess\Instance0]
“CacheTTLUser”
=dword:0000012cc
———————————————————————-

- Installation
- Best practices
- Migration
- Storage solutions

Have a look on his blog, there are some great articles more, so check it out by yourself on Yellow-Bricks.com

Exchange Connectivity Analyzer

- Microsoft Exchange ActiveSync Test
This test will simulate the steps a mobile device uses to connect to an Exchange Server using Echange ActiveSync.

- Microsoft Exchange ActiveSync AutoDiscover Test
This test will walk through the steps a Windows Mobile 6.1 device (or another AirSync licensed device) uses to connect to the AutoDiscover Service

- Microsoft Office Outlook 2007 AutoDiscover Connectivity Test
This test will walk through the steps Microsoft Office Outlook 2007 uses to connect to AutoDiscover

- Microsoft Office Outlook 2003 RPC/HTTP Connectivity Test
This test will walk through the steps Microsoft Office Outlook 2003 uses to connect via RPC/HTTP

- Inbound SMTP Email Test
This test will walk through the steps an Internet e-mail server uses to send inbound SMTP email to your domain

This tool is especially useful for Exchange administrators and developers. By using this tool, you can gather real-time data about the users in an Exchange environment and learn more about the inner workings of MAPI, OWA, POP3, IMAP4, NNTP and other protocols.

ExInsight helps you to understand how individual users affect the performance of an Exchange Server, analyze application usage of Microsoft Exchange, and guide troubleshooting of applications that depend on Microsoft Exchange.

ExInsight consists of two tools: Activity Statistics and Transaction Monitor . These tools allow you to monitor users’ activity on multiple Exchange servers from any computer in the network.

Activity Statistics

This tool enables administrators to view statistics about individual users’ consumptions of Exchange Server resources and the users’ actual experiences. Shown on a user-by-user basis, this tool allows you to see the following information:

- Protocols used by the clients (MAPI, OWA, POP3, IMAP or NNTP)
- CPU usage (CPU time, CPU percentage)
- Number of messages sent, received or created
- IP addresses used by the clients (only for MAPI clients)
- Microsoft Office Outlook versions and mode, such as Cached Exchange Mode and the classic online mode

Transaction Monitor

This tool displays a continuous communication between any computer and Exchange Server, helping to guide troubleshooting of applications that depend on Exchange. You can view and log every Exchange Server transaction, applying filters and highlighting to pinpoint trouble areas.

Transaction Monitor shows accounts requesting the data, the names and locations of the objects queried in Exchange, timings and transaction results. This tool also provides simplified summaries and links with detailed diagnostic information for each transaction.

Download Version 1.1.152 – 7.38 MB (without .NET Framework 2.0, prerequisite)

Download Version 1.1.152 – 30.8 MB (with .NET Framework 2.0 included)

First i’ve installed an virtual Windows 2008 x64 server. The nex step is to install all the prerequisites. So as I posted a few weeks ago, this can be done with two simple batch file.

You can install Exchange 2007 SP1 with the following commands, it saves you a lot of time!

“C:\TMP\Microsoft Exchange Server 2007 incl. Service Pack 1 x64\setup.com” /mode:install /roles:HT,CA,MB,MT /organizationname:E2K7
/targetdir:E:\Exchsvr /EnableErrorReporting /EnableLegacyOutlook

Let’s see what all these commands are:

“C:\TMP\Microsoft Exchange Server 2007 incl. Service Pack 1 x64\setup.com”
This is the path to the installation files of Exchange 2007. Don’t forget the quotes(“”) when there’s a space in the path.

/mode:install
This will put the command in install mode.

/roles:HT,CA,MB,MT
This are the different roles that will be installed.
HT = Hub Transport
CA = Client Access
MB = Mailbox
MT = Management Tools

/organizationname:E2K7
This is the name of the Exchange 2007 Organization. Don’t forget the quotes(“”) when there’s a space in the name.

/targetdir:E:\Exchsvr
This is the location where you want to install Exchange 2007. It prefered a different partition then the Operating System (OS).

/EnableErrorReporting
This enables a higher logging level through the Exchange 2007 setup process, so it will be easier to trouble shoot.

/EnableLegacyOutlook
If you’ve Outlook 2000 of 2003 clients in your environment, then you need to enable the LegacyOutlook. When you’re only have Outlook 2007 clients, this option can be deleted from the command.

here you can see some of the major issues:

- CDCR: Need an option to apply ELC policy to only the root instead of applying it recursively to root and all subfolders
- CDCR: Add generatePublisherEvidence enabled=”false” to Exchange Services Config Files
- SCR does not copy logs in a disjoint namespace scenario
- SCR cannot be enabled when DNS suffixes differ on source/target in disjoint namespace scenarios
- Exchange 2007 CAS cannot copy the OAB from the OAB share on Windows Server 2008-based Exchange 2007 CCR clusters
- Messages get stuck in outbox on Windows Mobile 6.1 devices When using  CAS proxy
- CDCR: MSI patching doesn’t update logon.aspx if the file is modified by customer

You can download the Rollup 5 for Exchange 2007 SP1 below.

Download Exchange SP1 Rollup 5

Incoming Traffic:
SMTP – TCP 25 – from the Internet
SMTP – TCP 25 – from the Edge Server to the Hub Transport Server

Outgoing Traffic:
SMTP – TCP 25 – from the Edge Server to the Internet
SMTP – TCP 25 – from the Hub Transport Server to the Edge Server
Secure LDAP – TCP 50636 – from the Hub Transport Server to the Edge Server
DNS – UDP 53 – from the Edge Server to the Internet
RDP – TCP 3389 – from the Hub Transport Server to the Edge Server

First you need to install the following prerequisites:
- Powershell 1.0
- Microsoft Management Console 3.0 (MMC 3.0)
- .NET Framework 2.0
- .NET Framewerk 2.0 SP1
- Active Directory Application Mode (ADAM)

First off all you have to now that the Edge Server will be placed in the companys DMZ, therefore the name “Edge”. The server is NOT a member of the internal Domain and will be placed in a  workgroup, for example E2K7EDGE. The Hub Transport Server will push the Active Directory information to the ADAM on the Edge Server trough Secure LDAP, port 50636, so this is one-way traffic.

After the installation of the Edge Transport Role, we’re going to creat a new Edge Subscription file. This file will be imported later on on the Hub Transport Server.

new-EdgeSubscription -file “c:\Edgeexport.xml

Go to your Hub Transport Server, Organizational Configuration, Edge Subscriptions and select New Edge Subscription. Browse to your Edgeexport.xml file and select the right Active Directory Site. Click on New to import the Edge Subscription file.

Now we create a new Receive Connector, so we’re abble to receive e-mail from the outside world.

After this action, the Edge Subscription can be started, so the Active Directory will push some information to the ADAM.

Start-EdgeSubscription

As you can see, there are two Send Connectors available on the Edge Server. One for sending e-mail to the outside world, and one for sending e-mail from the Edge Server to the Hub Transport Server.

Now you can begin to fine-tuning your Anti-spam configuration on the Edge Server. So now your Edge Server is ready.

When you extract the Exchange 2007 SP1 setup, there’s also an folder called Updates. Here you can put the additional updates that are need to install after the Exchange 2007 SP1 setup. Easy as that, we put Exchange 2007 SP1 Rollup 3 in the update folder. The installation will be started automatically…..

All Contacts
All Groups
All Rooms
All Users
Default Global Address List
Public Folders

We can find everything in this lists within Outlook 2003/2007, exept one thing, the Equipment Recourse. You can find the equipment recourse in the All Users address list. So, let’s make a new custom address list for all our Recourse Mailboxes (included: Room and Equipment)

Open the EMC (Exchange Management Console), Organization Configuration, Mailbox, Address Lists.

Richt-click on New Address List. Lets call it All Recources.

Now we have created a new Address List. Let’s open the Outlook Web Access (or Outlook client) to check if it is available.

As you can see, there’s our new created custom Address List that includes all the Resource Mailboxes as shown in the preview. Make it easy for your users in the environment to search a resource.

Download the Exchange Server 2007 Component Architectur Poster

Script: Exchange2007_pre_2008.cmd

ServerManagerCmd -i PowerShell
ServerManagerCmd -i Web-Server
ServerManagerCmd -i Web-ISAPI-Ext
ServerManagerCmd -i Web-Metabase
ServerManagerCmd -i Web-Lgcy-Mgmt-Console
ServerManagerCmd -i Web-Basic-Auth
ServerManagerCmd -i Web-Digest-Auth
ServerManagerCmd -i Web-Windows-Auth
ServerManagerCmd -i Web-Dyn-Compression
ServerManagerCmd -i RSAT-ADDS
Shutdown -r  -t 5

The reboot is needed for the last command ServerManagerCmd -i RSAT-ADDS (Active Directory Domain Services Tools). The server is now ready for installing Exchange 2007.

Open the EMC (Exchange Management Console), Organization Configuration, Hub Transport, Transport Rules, New Transport Rule

So lets see if everything is working. We are sending an e-mail to Administrator@e2k7.nl

When we open the mailbox from Administrator, there’s one new e-mail…

And you will see, there’s our custom made disclaimer! You can make so much configurations whitin these transport rules, so check all these options, it’s a real great feature…

Now we are going to change the mailboxcalendarsettings for this Room Mailbox to AutoAccept.

Open the EMS (Exchange Management Shell)

Set-MailboxCalendarsettings -Identity MeetingRoom1 -automateprocessing:AutoAccept

Get-MailboxCalendarSettings -Identity meetingroom1 | fl

All the users must have Read permissions to view the calendar of Meetingroom01.

Add-MailboxPermission -identity meetingroom01 -user “Domain Users” -AccessRights readpermission

Lets reserve the MeetingRoom01 on Monday.

As you can see, the organisator received an automatic e-mail from MeetingRoom01 that the appointment is accepted.

What if another person also wants to reserve this MeetingRoom01 on the same time…..watch this.

Exactly…the meeting is not accepted by MeetingRoom01 because there is an timeconflict!
Pretty  easy in your environment to configure this on the different room mailboxes.

————————————————–
ehlo console
mail from: sender@domain.com
rcpt to: recipient@domain.com
data
To: recipient@domain.com
From: sender@domain.com
Subject: Test Message Mailflow

This is a message for testing the mailflow.
.
quit
————————————————–

After installing Exchange 2007 SP1 Standard Edtion, I received the following eventid (1216).

So, let’s change some register keys to prevent this eventid. Open regedit and go to the following registerhives.

HKEY_Local_Machine\System\CurruntControlSet\Services\MSExchangeIS\NTS31\Private-xxxxxxx

Here you can find your mailboxdatabases, this can be different in your situation.

Add a DWORD called Database Size Limit in GB. Lets change the decimal value to 180, this means 180 GB.

After dismounting and mounting the mailboxdatabase, you get the following eventid.

Let’s have a look on that…

First off all, open your Exchange Management Console, Server Configuration, Hub Transport, Receive Connectors. Here we going to add a new custom Receive Connector, calling Relay Connector.

In this example the following servers are authenticated to relay of the Exchange 2007 Server.

(172.16.1.19, 172.16.1.20 and the range 172.16.1.200 – 172.16.1.210)

Default all of the users have access to all the (new)features.

From the EMC (Exchange Management Console) go to Server Configuration, Client Access, Outlook Web Acces and open the Properties. After this go to the Segmentation tab.

Here you can enable or disable some features. Let’s customize our OWA website, and find the differents

You can download the files here.

Download Update Rollup 4 for Exchange 2007 SP1

“D:\ExchSvr\Bin\eseutil.exe” /d “E:\SG1MD1\SG1MD1.edb” /t “D:\TEMP\temp_defrag.edb”
pause

The path to the de maildatabase can be different in some environments, so you have to change that path manualy.

E:\temp\temp_defrag.edb is the path and filename for the tempdatabase. This can also changed manualy.

Make sure you dismount the specific mailstore.

First you will get some information about the current certificates.

Remember that you have to distribute this new certificate to all mobile devices.

• Microsoft .NET Framework 2.0 x64
• Microsoft .NET Framework 2.0 x64 update KB926776
• Microsoft Management Console 3.0 for Windows 2003 x64 KB907265
• Microsoft PowerShell 1.0 for Windows 2003 x64
• Domein Functional Level of 2000 Native of higher
• Internet Information Services (IIS)

The installation of Exchange 2007 Service Pack 1 is finished. Remember, this is only the basic installation without any rollup packs.