Search results matching tag 'Exchange 2003'

Exchange 2007: Understanding the Routing Group Connector between an Exchange 2003 and Exchange 2007 Messaging Environment

lynn lunik — Mon, 19 Jan 2009 18:31:00 GMT

In a previous Blog entry I outlined the steps necessary to install the first Exchange 2007 Server into an existing Exchange 2003 Messaging Environment. This process, which Microsoft terms a 'Transition Strategy' is well defined and well documented. As part of a deeper look into the Routing Group Connector I thought I would offer some details using both the Exchange Management Shell (Powershell) and the Exchange Management Console to detail settings. Additionally, I show how to use the Message Tracking Application from the Exchange 2007 Manager Console.

Here are the reference URLs to prior Blog entries of interest on this topic:

Installation Steps - Installing the first Exchange 2007 Server into an Existing Exchange 2003 Organization

Moving from Exchange 2003 to Exchange 2007 using a Transition Strategy

Transition Steps - Moving a Mailbox from an Exchange 2003 Organization to an Exchange 2007 Organization using the Move Mailbox Wizard

In this Blog entry I will analyze mailflow across the Routing Group Connector to provide a clearer picture of what occurs while Organizations are Transitioning from Exchange 2003 to Exchange 2007.

1. Let's begin by examining the 2 Servers that comprise the Exchange 2003 Site titled 'First Administrative Group', and, the 2 Servers in the Exchange 2007 Site titled 'Exchange Administrative Group'. We see 4 Servers total:

Exchange 2003

S01-EX00
S01-EX00-1

Exchange 2007

S01-EX01
S01-Ex02

2. The Exchange 2007 Servers have been introduced into the Exchange 2003 Organization named 'ITPS Lab Exchange Organization'. When this occurred, a Bi-Directional Routing Group Connector was generated as part of the installation process. We see here the Routing Group Connector titled 'ITPS Lab Interop RGC' (actually, this is a hand-generated Routing Group Connector I created 'after the fact'). In this example, the Exchange 2007 Installation Process generated the RGC, then I generated an additional RGC and finally, deleted the RGC created automatically by the Exchange 2007 Installation Process. In a typical environment, we would generate (with the Exchange 2007 Installation Process) and maintain a single Routing Group Connector (RGC). Unless of course multiple Exchange 2007 Hub Transport Role Servers are required.

3. Let's examine the Properties of the Exchange 2003 Routing Group Connector.

4. Here we see the Exchange 2003 Server (titled S01-EX00) is the Default Server used for Routing Messages over the Routing Group Connector to the Exchange 2007 Remote Bridghead Servers.

5. The Exchange 2007 Server that is the Remote Bridgehead Server for this Exchange 2003 Routing Group Connector is titled 'S01-EX01'. It is an Exchange 2007 Hub Transport Role Server running Exchange 2007.

6. Now, let's examine the Routing Group Connector Properties for the Exchange 2007 Routing Group. Remember, Exchange 2007 only uses Routing Group Connectors for interoperability 'backwards' to Exchange 2003 Organizations.

7. Again, we see reciprocity! The Exchange 2007 Hub Transport Role Server (titled 'S01-EX001') 'connects' over this Routing Group Connector to the Exchange 2003 Server (titled in the next caption as 'S01-EX00').

8. The Remote Bridgehead Server for the Exchange 2003 Routing Group is identified as 'S01-EX00'.

9. Next I move to the Exchange 2007 Hub Transport Role Server titled 'S01-EX01'. As you can see, through the Exchange Management Console there is no Graphical Interface for Administering a Routing Group Connector (RGC). We will instead use the Exchange Management Shell to invoke the 'Get-RoutingGroupConnector' Commandlet.

10. Initially, when I offer the Exchange Management Shell Commandlet 'Get-RoutingGroupConnector' we see data listed in a Table from the default feedback. Here's the Exchange Management Shell Commandlet:

get-routinggroupconnector

11. Next, to see the full detail for this EMS Commandlet I issue the following Commandlet using the 'Pipeline Parameter' (|) followed by 'Format List' (fl):

get-routinggroupconnector | fl

12. The second half of the EMS window appears here. Notice we have rich granularity in the Attributes available.

13. So, what do we have here? This is another variation of the EMS Commandlet denoting additionall Attributes be displayed. Here we can see both 'Source Transport Server' and 'Target Transport Server' by using the followng EMS Commandlet variation:

get-routinggroupconnector |fl targetroutinggroup,targettransportservers,sourcetransportservers

14. Next I add the 'Cost' Attribute to display in this EMS Commandlet. Here's the Commandlet syntax:

get-routinggroupconnector |fl targetroutinggroup,targettransportservers,sourcetransportservers,cost

15. Finally, I personally favor the following EMS Commandlet Syntax for this Commandlet. It allows me to keep track of versional changes.

get-routinggroupconnector |fl targetroutinggroup,targettransportservers,sourcetransportservers,cost,whencreated,whenchanged

16. Okay, so where are we? We just spent time using the Exchange Management Shell (EMS) to analyze the output of the Routing Group Connector that links the Legacy Exchange 2003 Organization to the initial Exchange 2007 Hub Transport Role Server in our Messaging Environment. We are reviewing these configuration details to understand how and where SMTP Messages 'Route' in a Transitional Strategy that involves Exchange 2003 and Exchange 2007.

17. Next, I would like to review the 'Routing Log Viewer' available from within the Exchange Management Console in Exchange 2007. You will find it on the 'Tools' leaf of the Exchange 2007 Management Console.

18. The 'Routing Log Viewer' in the Exchange 2007 Management Console (EMC) provide XML Files that 'record' the Routing Configuratin across all Routing Group Connectors, Send Connectors and Receive Connectors. Foreign Connectors are not included in the Routing Log Viewer as Foreign Connectors simply 'pickup' SMTP Messages from the 'Pickup' Directory.

19. I select the most recent XML File to examine the contents.

20. Most Exchange System Engineer's have never seen, nor used the Routing Log Viewer. Here we can see the Active Directory Site whereby the Exchange 2007 Servers are visible. And, the Exchange 2003 Routing Group where the Exchange 2003 Servers are visible.

21. Upon moving to the 'Servers' Tab in the Routing Log Viewer we see a more detailed breakdown of both Exchange 2003 and Exchange 2007 Servers. Note the Exchange 2007 Servers use the Active Diretory Sites as their respective 'Routing Boundaries' (lower portion of capture) while the Exchange 2003 Servers use the Routing Group as their respective 'Routing Boundaries'.

22. Next we observe the 'Send Connectors' Tab of the Routing Log Viewer. Some of the details of the Routing Group Connector are present in this Graphical Interface.

23. As part of the endeavor to understand SMTP Message Routing across a Routing Group Connector I would like to 'follow' a message from an Exchange 2007 User Mailbox, across the Routing Group Connector to an Exchange 2003 User Mailbox. We can use Message Tracking available in the Exchange 2003 System Manager (ESM) and in the Exchange 2007 Management Console (EMC). Here I begin logging in as an Exchange 2007 Mailbox User fictitiously named 'Steve Railson' to send e-mail to an Exchange 2003 Mailbox User named 'Field1'.

24. Logging in to prepare e-mail for an Exchange 2003 Target (from an Exchange 2007 Mailbox User).

25. E-mail prepared and sent. This message should 'travel across' the Exchange 2007 Hub Transport Role Server to the Routing Group Connector (RGC), ultimately to the Exchange 2003 Routing Group Server and finally to the destination Exchange 2003 User Mailbox Server. Let's follow it's path!

26. Confirmation of the 'CC' of this message from/to himself.

27. I move to the Exchange 2003 Mailbox Server Role titled 'S01-EX00-1' to confirm an Exchange 2003 Mailbox User named 'Field1'. Confirmation complete! Our Mailbox is on this server!

28. When I open the 'Messaging Tracking Center' in Exchange 2003 and input query parameters (like Exchange 2007 Mailbox User Name, Mailbox Server Name, etc.) the response is identification of the exact message sent. Next, let's look a the Message Tracking in the Exchange 2007 Messaging Tracking to determine how this SMTP Message 'travelled' using which Connector (it should be our Routing Group Connector!).

29. I move to the EMC on an Exchange 2007 Hub Transport Role Server. Next, I open the Message Tracking Application.

30. When I input a narrow time range (the exact 5 minute interval I know the message was sent) I receive a response with the exact message tracking detail. Now, here is our point of confirmation - will the SMTP Message from the Exchange 2007 Mailbox User (srailson User ID) transmit over the Routing Group Connector as we expect? Let's see.

31. Yes! Success! A closer examination of the 'ConnectorID' Attribute and we see 'Intra-Organization SMTP Send Connector' indicated as the Connector used to transmit this SMTP Message from the Exchange 2007 Hub Transport Role to the Exchange 2003 Routing Group Server. Thus providing 'mailflow' between a Legacy Exchange 2003 Organization and new Exchange 2007 Hub Transport Role Servers in the same Exchange Organization.

In this Blog entry I review many of the configuration parameters of an Exchange 2007 Routing Group Connector. I use the many of the Exchange 2007 Applications for analysi, including the Exchange Management Shell Commandlet 'get-routinggroupconnector', the Exchange Management Console, the Routing Log Viewer and Message Tracking. While, when working on the Exchange 2003 Server Role I use the Exchange System Manager and the Message Tracking Center. All of these Tools prove useful when determining the SMTP Message Routing in a joint Exchange 2003 and Exchange 2007 Messaging Infrastructure!

If you'd like to 'Learn Advanced IT' - Check out the Free Video Lessons on Windows 2008 SP2 Failover Cluster Nodes for Highly Available File Services and other Microsoft product topics as well - http://www.exchangesummit.net.

Lynn Lunik
Independent Security Consultant
Windows(R) Platform
IT Pro Secure Corporation
and
exchangesummit.net
http://itprosecure.com and http://www.exchangesummit.net
blog <at> itprosecure.com

Exchange Server 2007 Design and Architecture at Microsoft

lynn lunik — Mon, 22 Sep 2008 12:17:00 GMT

A consistent theme with Large Clients entails discussions of 'How did Microsoft do their Exchange 2007 Transition?' or, 'How does Microsoft configure Spam Filtering', and even, 'How much capacity do I need for 'XYZ' Exchange 2007 Service?'. With these questions I utilize some of the quality reference materials as the resources to find the answers. Microsoft (and the Microsoft Exchange Technical Writing Team along with the Microsoft Operations Technology Group) have done a good job in offering technical, business and operational data on 'how best' to transition, configure and operate Exchange 2007 over time. The Microsoft TechNet Web Page on 'Exchange Server 2007 Design and Architecture at Microsoft' is another resource worth noting in this regard.

Exchange Server 2007 Design and Architecture at Microsoft

In this document you receive a detailed answer to most initial questions regarding planning a transition to Exchange 2007. Enclosed are screen captures of the images (most of them) included in this document. Take a quick review, then spend some time reading this document as a reference guide. I have posted a number of other links of benefit for this journey as well. Here is a short list from my Blog site:

Useful Transition and Migration Tools - Exchange Best Practice Analyzer and Active Directory Topology Diagrammer

System Center Capacity Planner 2007

Exchange Server 2007 Component Poster

Exchange Server 2007 Deployment Checklists

Installation Steps - Forefront Security for Exchange on the Exchange 2007 Mailbox Server Role

Configuration Steps - Creating an Edge Subscription between an Edge Transport Server Role and a Hub Transport Server Role in Exchange 2007

Installation Steps - Installing the Edge Transport Server Role on a Server with 2 Network Interface Cards

Transition Steps - Moving a Mailbox from an Exchange 2003 Organization to an Exchange 2007 Organization using the Move Mailbox Wizard

Technorati Tags: Exchange 2007

LiveJournal Tags: Exchange 2007

del.icio.us Tags: Exchange 2007

BuzzNet Tags: Exchange 2007

Lynn Lunik
Independent Security Consultant
Windows(R) Platform
IT Pro Secure Corporation
and
exchangesummit.net
http://itprosecure.com and http://www.exchangesummit.net
blog <at> itprosecure.com

Transition Steps - Moving a Mailbox from an Exchange 2003 Organization to an Exchange 2007 Organization using the Move Mailbox Wizard

lynn lunik — Wed, 05 Sep 2007 19:18:00 GMT

Over the past months I have worked with a number of Clients to 'Transition' from Exchange 2003 to Exchange 2007. If you research you can find information about the difference between a 'transition' and a 'migration' in this Blog Entry. For this entry I use the previously configured Exchange 2007 Server located in the existing Exchange 2003 Organization. The Installation Steps for the First Exchange 2007 Server in an Exchange 2003 Organization are located in this Blog Entry. Once we have the first Exchange 2007 Server installed in the existing Exchange 2003 Organization we can begin to 'transition' (or Move) Mailboxes into the Exchange 2007 Storage Groups and Information Stores.

Our 'Source' Server for this Mailbox Move is an Exchange 2003 Server running Ex2k3 SP2. I previously integrated the first Exchange 2007 Server into the existing Exchange 2003 Organization.

Here is the IP Configuration detail of the existing Exchange 2003 Server.

The Exchange 2003 System Manager shows both the 'First Administrative Group' where the Exchange 2003 Server resides and the newly created 'Exchange Administrative Group (with Cipher Text spelling something cool!) where the Exchange 2007 Server resides.

If we observe closely the Exchange 2003 Routing Group Connector we find this is the mechanism through which 'Ex2k3 knows about Ex2k7' and vice versa.

If we select 'Properties' on this Routing Group Connector a 'normal' error message appears indicating we need something from the Exchange 2007 MMC (or Management Shell) to open to modify settings.

We observer the 'Default Settings' on this Ex2k3/Ex2k7 Routing Group Connector.

Upon further investigation into both Administrative Groups we see a Routing Group Connector for both Exchange 2003 and Exchange 2007.

When we move over to the Exchange 2007 Server and invoke the 'Get-ExchangeServer' Commandlet we see the 2 existing Exchange Servers in their respective Version (V6.5 is Ex2k3 and V8.0 is Ex2k7).

In the Exchange 2007 Management Console I have selected a Mailbox for 'Ralph McGee' our target Mailbox for Moving from Exchange 2003 to Exchange 2007. Notice the 'Recipient Type Details' column indicating 'Legacy Mailbox'.

The 'Action Pane' from the Exchange 2007 Management Console offers access to the 'Move Mailbox' Wizard. I select the appropriate Exchange 2007 Server, Storage Group and Mailbox Database.

The 'Move Options' provide the benefit of scheduling the Mailbox Move 'after working hours'. Or when more convenient for End Users.

I trigger the 'Move Schedule' to be 'Immediately'.

This is the final confirmation before the Exchange Management Shell Commandlet is invoked (behind the Graphical Interface).

The 'Move Mailbox' process kicked off and indicates we completed succesfully. Ralph McGee now resides on an Exchange 2007 Server.

Notice the 'Recipient Type' has changes from 'Legacy Mailbox' to 'User Mailbox' indicating the Mailbox is on Exchange 2007.

I now move to a Windows XP SP2 Workstation with Office 2007 and Outlook 2007. I login as 'Ralph McGee' - a Domain User.

I invoke Outlook 2007 to see how Ralph's e-mail faired during the 'Move Mailbox' process.

Success! (as far as I know!) I observe Mail Messages previously included in the Exchange 2003 Mailbox Store.

Now I begin testing Mail Flow by sending an e-mail message from 'Ralph McGee' to 'Ralph McGee' and copy a Query-Based Distribution Group as well!

Instant feedback! Mail is flowing.

I now begin testing Mail Flow from Exchange 2007 to Exchange 2003 by targeting an e-mail to Joe Smith. Joe Smith has a Mailbox on the Legacy Exchange 2003 Server.

Logging in as 'Joe Smith' I immediately receive the e-mail from Ralph McGee. This indicates proper Mail Flow between Exchange 2007 and Exchange 2003.

My next steps would be to plan the migration of the remaining Users, Contacts, Distribution Lists and Public Folders. Everything is working well and I am off to the next Task!

If you'd like to 'Learn Advanced IT' - Check out the Free Video Lessons on Windows 2008 SP2 Failover Cluster Nodes for Highly Available File Services and other Microsoft topics as well - http://www.exchangesummit.net.

Lynn Lunik
Independent Security Consultant
Windows(R) Platform
IT Pro Secure Corporation
blog <at> itprosecure.com

Required Exchange 2007 Reference Materials - Books for the Exchange System Engineer's Library

lynn lunik — Wed, 29 Aug 2007 10:53:00 GMT

In my studies (and travels) I have compiled a list of Exchange 2007 Books worthwhile of both investing and understanding the contents offered in written format. Here's my 'short list' of titles that should be in every Exchange System Engineer's Library:

Microsoft Exchange Server 2007 Administrator's Pocket Consultant - William Stanek

How to Cheat at Configuring Exchange Server 2007: Including Outlook Web, Mobile and Voice Access - Henrik Walther

Microsoft Exchange Server 2007: A Beginner's Guide (Network Professional's Library) - Nick Cavalancia

Microsoft Exchange Server 2007 Unleashed - Rand Morimoto, Michael Noel, Andrew Abbate, Chris Amaris and Mark Weinhardt

Lynn Lunik
Independent Security Consultant
Windows(R) Platform
IT Pro Secure Corporation
and
exchangesummit.net
http://itprosecure.com and http://www.exchangesummit.net
blog <at> itprosecure.com

Installation Steps - Installing the first Exchange 2007 Server into an Existing Exchange 2003 Organization

lynn lunik — Fri, 24 Aug 2007 01:54:00 GMT

When considering a 'Transition Strategy' from Ex2k3 to Ex2k7 it is imperative to read through the many Technical Documents provided by Microsoft (and others) and establish testing criteria prior to any Production changes. I have posted a number of prior Blog Entries that are required reading (or viewing) with some of them summarized as:

Moving from Exchange 2003 to Exchange 2007 using a Transition Strategy

Technical Architecture of Exchange Server 2007

Exchange 2007 High Availability Strategies

After spending a good amount of time reading, working with Virtualization Software and comparing notes with Colleagues it is time to introduce the first Ex2k7 Server into your existing Ex2k3 Messaging Environment. The following Screen Captures offer a step-by-step approach to installing this initial Ex2k7 Server.

I login to the Schema FSMO Role Holder in the Forest Root the '....\setup.com /preparead' parameter is initiated in the User Context of a Schema Administrator. This parameter provides the required Schema Updates along with Domain Global Security Group additions and ACL modifications on the appropriate Active Directory Configuration Naming Contexts and Organizational Units.

A series of 'checks' occur at both the Domain and Forest Level to validate receipt of the Schema Changes and Domain Level changes. If all is well the modifications occur on the Forest Root Schema Role Holder. Replication to other Domain Controllers occur at the defined Replication Interval per the Active Directory Sites and Services configuration.

Upon successful completion of the Schema and Domain Upgrade process we can see new Domain Global Security Groups are generated. Invoking Active Directory Users and Computers and connecting to a Domain Controller shows the new Organizational Unit for Exchange 2007 Security Groups.

Another validation method that Exchange 2007 Schema updates were applied is to use ADSI Edit and look for specific Exchange 2007 Attributes. Here, I isolate the 'ms-exch-Auto-Discover-VirtualDirectory' attribute which is new for Exchange 2007.

The 'repadmin /syncall' parameter forces a synchronization between Domain Controllers. The goal is to ensure the Exchange 2007 Schema updates are synchronized between Domain Controllers prior to performing the Installation of Exchange 2007 on the first Exchange 2007 Server in an Exchange 2003 Organization. I force a replication as no one should have to wait in a Lab Environment!

On the second Domain Controller the Exchange 2007 Schema Attributes are present. The next step is to proceed with the Installation of Exchange 2007.

A 'Custom Installation' is necessary so we might select the Server Roles to be installed.

Three Server Roles are selected for this first Exchange 2007 Server in an Exchange 2003 Organization. The Client Access Server Role (formerly OWA Server), the Hub Transport Server Role and the Mailbox Server Role.

The moment of truth (not really, the moment of 'transition'!) whereby if we have configured all parameters correctly and are prepared - are offered the option to select an Exchange 2003 Server that the Routing Group Connector between Exchange 2007 and Exchange 2003 functions.

Upon completion of a successful installation the Exchange Best Practice Analyzer is run to identify areas of focus for configuration changes and parameters to be set for optimization.

Next the Exchange 2007 Update Rollup 4 is installed.

Perform a reboot of the Exchange 2007 Server after receiving the Exchange 2007 Update Rollup 4.

When the Exchange 2007 Server is available I start by using the 'Test-ServiceHealth' commandlet to validate critical Service availability. Additionally, I do a bevvy (whatever that means) of Commandlets to ensure proper installation and function of an Exchange 2007 Server.

Note that the 'Get-ExchangeServer' Commandlet shows both the Exchange 2003 Server (denoted as V6.5) and the Exchange 2007 Server (denoted as V8.0) in my Lab Environment. We are moving closer to being able to 'transition' Users and Public Folders to Exchange 2007.

Finally, we see our list of Exchange 2003 Mailbox Recipients denoted as 'Legacy Mailboxes'. These are our candidates for 'transitioning' to Exchange 2007. I will provide a separate Blog entry that provides step-by-step instructions in how to complete a 'Move Mailbox' using both the Exchange Console and using the Exchange Management Shell (PowerShell Commandlet).

We have a series of additional configuration parameters to complete. More about these steps in another Blog entry. We now have a healthy Exchange 2007 Server in our Exchange 2003 Organization.

If you'd like to 'Learn Advanced IT' - Check out the Free Video Lessons on Windows 2008 SP2 Failover Cluster Nodes for Highly Available File Services and other topics as well - http://www.exchangesummit.net.

Lynn Lunik
Independent Security Consultant
Windows(R) Platform
IT Pro Secure Corporation
and
exchangesummit.net
http://itprosecure.com and http://www.exchangesummit.net
blog <at> itprosecure.com

Top Three Exchange Server 2007 Deployment Scenarios: Essential Reading

lynn lunik — Fri, 03 Aug 2007 12:59:00 GMT

Jill Frank, Senior Technical Writer for the Microsoft Exchange Team has compiled a useful synopsis of the Top 3 Exchange 2007 Deployment Scenarios. In retrospect, I realized I have previously used every one of these URLs in current or previous Exchange 2007 Transitions and Migrations. Very useful information - especially for all the Scenarios where Transitioning from Exchange 2003 to Exchange 2007 is underway or being planned!

Top Three Exchange Server 2007 Deployment Scenarios: Essential Reading

Lynn Lunik
Independent Security Consultant
Windows(R) Platform
IT Pro Secure Corporation
and
exchangesummit.net
http://itprosecure.com and http://www.exchangesummit.net
blog <at> itprosecure.com

Exchange 2007 Webcasts

lynn lunik — Fri, 03 Aug 2007 12:49:00 GMT

I realized there is a large body of information made available from Microsoft (and others) when deploying Exchange 2007. Take a look at the following if you are considering using Forefront Security for Exchange - or - if you want to really configure your Client Access Server Role well!

Exchange 2007 Webcasts

Lynn Lunik
Independent Security Consultant
Windows(R) Platform
IT Pro Secure Corporation
and
exchangesummit.net
http://itprosecure.com and http://www.exchangesummit.net
blog <at> itprosecure.com

Moving from Exchange 2003 to Exchange 2007 using a Transition Strategy

lynn lunik — Tue, 17 Jul 2007 17:38:00 GMT

As you interact with Exchange 2007 during the process of moving from one version to the next version (Ex2k3 to Ex2k7 for example) several terms are quickly made apparent:

Transition - the Scenario in which you upgrade an existing Exchange Organization to Microsoft Exchange 2007.

Migration - the Scenario in which you upgrade to Exchange 2007 by migrating data from a non-Exchange Messaging System to Exchange 2007.

I have posted additional online resources for migrating from Lotus Domino 6.5 to Exchange 2007 Server at the following links:

Resources for Migrating from Lotus Domino 6.5 to Microsoft Exchange 2007 Server

There are numerous resource becoming available to address how to follow a Transition Strategy. A good starting point if you maintain an Exchange 2003 Messaging Infrastructure is the following Microsoft TechNet document:

Upgrading to Exchange 2007

Excellent reference material for co-existing with Exchange 2003 and Exchange 2000 Servers are found in these documents:

Co-existing with Exchange Server 2003 and Exchange 2000 Server

Planning for Co-existence

Best Practices for Transitioning an Exchange Organization

Additionally, there are a number of good reference articles that address use of the Exchange Command Shell (Powershell 1.0). I have referenced a few of these Powershell Commands in prior Blog entries:

PowerShell Commandlets for Mailbox Administration (Recipient Management)

How to Change Logging Levels for Exchange Processes in Exchange 2007

PowerShell Commandlets for Connector Configuration in Exchange 2007

PowerShell Blog Entries on IT Pro Secure Corporation Blogs

Lynn Lunik
Independent Security Consultant
Windows(R) Platform
IT Pro Secure Corporation
and
exchangesummit.net
http://itprosecure.com and http://www.exchangesummit.net
blog <at> itprosecure.com

SC Operations Manager 2007 - Resolving the 'Cluster Node Discovery' Issue Effecting Exchange 2003 Cluster Nodes using Exchange 2003 Management Pack

lynn lunik — Fri, 22 Jun 2007 12:00:00 GMT

In several recent SC Operations Manager 2007 Deployments I am working I encountered a challenge that took some assistance from Microsoft Premier Engineers and a Colleague of mine from Microsoft who formerly worked as a Professional Consultant (and who now works as a Product TS for System Center). Special thanks to Chris Urban for his willingness to engage and offer input to solve this issue!

Here was the Challenge:

         In a healthy SC Operations Manager configuration including the Exchange 2003 Management Pack and the Windows Server Base OS Management Pack the Exchange 2003 Cluster Nodes cannot be discovered (and thus, the Exchange 2003 Management Pack was not functioning for the Exchange 2003 Rules, Alerts, Performance Data, Health Explorer, etc.).

Here's the Scenario:

1. Windows 2003 Domain and Forest (Single Domain) in Windows 2003 Native Mode.

2. Single SC Operations Manager 2007 Installation
       a. Root Management Server Role
       b. No Gateway Server Role
       c. No ACS Server Role
       d. Single Management Server
       e. No Agentless Management Server Function
       f. 50 Servers Agent Managed

3. Management Packs Installed
      a. Windows Server Base OS Management Pack
      b. Active Directory Management Pack
      c. Information Worker Management Pack
      d. Operations Manager 2007 Management Pack
      e. SQL 2005 Management Pack
      f.   IIS Management Pack
      g. Exchange 2003 Management Pack

Here's one possible Solution:

I found following this sequence (for these particular configurations) remedied this issue and allowed the Exchange 2003 Cluster Nodes to be Discovered (once discovered the Exchange 2003 Management Pack components began collecting Alerts, Performance Data, Health Monitor values, etc.).

1. Uninstall the Exchange 2003 Management Pack (not absolutely necessary as it will work if you do not).
2. Move to the Administration Space.
3. Move to the 'Agent Managed' Node.
4. Select the first Exchange 2003 Cluster Node.
5. Select 'Properties' on the first Exchange 2003 Cluster Node.
6. Select the 'Security' Tab.
7. Enable the 'Allow this agent to act as a proxy and discover managed objects on other computers' under the 'Agent Proxy' section of the dialogue.
8. Complete Steps 1-7 on the second (and any additional) Exchange Cluster Nodes.
9. Wait approximately 30 minutes.
10. Open the SC OM2k7 Management Console.
11. Move to the 'Discovered Inventory' View.
12. Observe (if this process was successful) the Exchange 2003 Virtual Server Cluster Node(s).
13. Move to the Administration Space in the SC OM2k7 Management Console.
14. Re-Import the Exchange 2003 Management Pack (if you Uninstalled it in Step 1).
15. Move to the Monitoring Space in the SC OM2k7 Management Console.
16. Move to the Exchange 2003 Management Pack.
17. Move to the 'All Server State' View in the Exchange 2003 Management Pack.
18. Observe the Exchange 2003 Virtual Server Cluster Node by Name.
19. Observe and configure Performance Views for the Exchange 2003 Virtual server Cluster Node.

I understand a modified Exchange 2003 Management Pack will be release by Microsoft for the SC OM2k7 Management Pack Catalog in the near future that will mitigate having to follow Steps 1-19 above - in the meantime I hope this helps!

Lynn Lunik
Independent Security Consultant
Windows(R) Platform
IT Pro Secure Corporation
and
exchangesummit.net
http://itprosecure.com and http://www.exchangesummit.net
blog <at> itprosecure.com

Exchange 2007 Mailbox Server Role Storage Requirements Calculator

lynn lunik — Thu, 15 Mar 2007 09:38:00 GMT

Please Note: The Ex2k7 MB Server Role Storage Requirements Calculator Worksheet was revised in December 2007. This link is to the latest info!

Ross Smith of Microsoft has offered a Blog Entry that includes a new Ex2k7 Mailbox Server Role Storage Calculator.

If you have ever attempted LUN Design or IO Calculations you will find this of value.

Summary of Exchange 2007 Blog Entries

Lynn Lunik
Independent Security Consultant
Windows(R) Platform
IT Pro Secure Corporation
blog <at> itprosecure.com