Saturday, January 31, 2009

Exchange Server 07 -- Mailing Lists

A reader asks...
Does anyone know of any third party extention to Exchange 2007 for
mailing list features.
i.e reply to list, interchangable subject line.
_________________________________________________________________


Here are some I know about.

Build your own:

http://www.ftponline.com/wss/2002_04/magazine/columns/maximumexchange/

Exchange-based products:

http://www.ikakura.com/

http://www.gfi.com/mes/ (More than just a list server)

Non-Exchange-based but worthy of consideration:

http://www.lyris.com/products/listmanager/
__________________________________________________________________

Programming MS Exchange Server: Achieve Enterprise-Wide Document Management
____________________________________________________________________

Early in January Notre Dame was moved from Sendmail to Exchange
2007-about 13K accounts.
They used Transcend Migrator to do it. The app did an imap copy and
overall it worked well. Transcend Migrator provided them with some custom DLL's to do
auth-ext. They had about a %1 failure rate on the mailboxes.
Yale recently did the same thing but the staff there wrote their own
java based app to move the data and used Transcend to migrate desktop
mail files.
Miami University also recently moved all accounts from imap to
exchange and developed there own framework to do it.
I'm not too familiar with sunmail but if you use imap you have about 4
choices- MS provides a imap copy utility, Transcend's application, one
or two opensource packages, or roll your own.

Wednesday, January 28, 2009

Exchange Server 07

The SPF records for domain.com show up just fine from here as well:
domain.com text =

"v=spf1 mx ip4:69.63.211.0/25 ip4:64.85.73.0/25 ip4:70.103.251.0/24 ip4:
63.251.171.160/27 -all"

Make sure that if you're using split brained DNS thast your internal DNS servers have the spf record as well.

Tuesday, January 27, 2009

Exchange Server 07] Q&A

James asks:
We currently have 4 mailbox groups with 1 store in each. Is there any
performance hit in using more than 1 store in each group? We have 2
groups that are over 100gig each and I would like to break them down
further.
I was told that using multiple stores in each group is not supported
but I could not find anything that stated that.

Answer:

Probably not.


Adrian asks:
Not sure if anyone can help here. I seem to be getting a specific
error on what would seem to be spam messages that are to/from legit
addresses on our domain, but are coming from outside and we do have an
SPF record. Looking at other messages, SPF checking seems to be
flowing OK. The error is:

Received-SPF: TempError (mail.domain.com: error in processing during
lookup of example@domain.com: DNS timeout)

I just did an NSlookup against our DNS server and it returned the SPF
OK.

FYI, i only stamp the message even if it fails as far as SPF processing
goes. I am wondering if now is the time to reject messages, but I am
not sure if that will cure this problem.

Answer:

check back tomorrow....

Monday, January 26, 2009

Exchange Server 07 -- static routes

The discussion had evolved into exploring the stretched option. The static route is necessary IFF (if and only if) he decides that the two nodes of the cluster need to be on separate private subnets. I've seen customers doing this because they don't want to have to stretch either the public or the private subnets between two sites.

Example:

Site A
Public subnet: 10.0.0.0/24
Private subnet: 192.168.0.0/24

Site B
Public subnet: 10.0.1.0/24
Private subnet: 192.168.1.0/24

In that case, each node will need a static route to the router that connects 192.168.0.0/24 and 192.168.1.0/24, assuming that these networks cannot be reached by the normal default gateway. The public interfaces, however, SHOULD NOT have a default gateway.
_____________________________________________

AllThoseArticles.info

Saturday, January 24, 2009

private network heartbeat

Question:
Does anyone know how the private network heartbeat works specifically?
I've read articles and you must use a different IP/Subnet then the public network but without a gateway. I'm confused how the heartbeat will actually work if there is no requirement to use a VLAN/Gateway etc.




Answer:

The lack of a default gateway on the private network exists for a
couple of reasons.

1) Nodes of a cluster should have low-latency link between all
members of the cluster. In general, you need gateways between IP
subnets because you are either provisioning subnets for administrative
purposes (client subnet vs. server subnet vs. perimeter subnet, etc.)
or because you have more devices than can fit on a single subnet. Now,
on a well-managed network, adding a gateway only increases the latency
by a tiny bit, but it does represent a potential point of congestion.
For a cluster, that congestion could be killer.

2) IP networking stacks in general don't handle the case of multiple
default gateways very well. Think about how IP routing works for a
minute by taking a look at the output of route print. That routing
table there helps the IP stack figure out which next hop (and which
interface) a packet needs to use, and it does it by matching from most
specific to least specific, modified by the metric (weight; lower is
higher priority) of the route if there's a tie based on IP
address/subnet mask.

So, having two default gateways will confuse the computer -- two
"last match" destinations. What happens is that Windows typically will
assign one a higher metric, which means it won't get used. This rarely
leads to desirable conditions.

Example time: say I've got an internal network of 172.31.0.0/24 and
a cluster network of 192.168.0.0/24. My IP address are 172.31.0.16 and
192.168.0.16. Here's my routing table:

Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 172.31.0.1 172.31.0.16
20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
172.31.0.0 255.255.255.0 172.31.0.16 172.31.0.16
20
172.31.0.16 255.255.255.255 127.0.0.1 127.0.0.1
20
172.31.0.255 255.255.255.255 172.31.0.16 172.31.0.16
20
* 192.168.0.0 255.255.255.0 192.168.0.16 192.168.0.16
30
192.168.0.16 255.255.255.255 127.0.0.1 127.0.0.1
30
192.168.0.255 255.255.255.255 192.168.0.16 192.168.0.16
30
224.0.0.0 240.0.0.0 172.31.0.16 172.31.0.16
20
224.0.0.0 240.0.0.0 192.168.0.16 192.168.0.16
30
255.255.255.255 255.255.255.255 172.31.0.16 172.31.0.16
1
255.255.255.255 255.255.255.255 192.168.0.16 192.168.0.16
1
Default Gateway: 172.31.0.1

When this computer wants to send a packet using the private
(192.168.0.0/24) network, the cluster service knows that other node
has an IP address of 192.168.0.12, so that's the destination IP
address in the packet. When it gets to the IP stack, that destination
matches the line marked with an asterisk, so the IP stack routes it
out the appropriate interface. No second default gateway is needed;
the 172.31.0.1 gateway isn't part of the private network and doesn't
know how to route for it, and the second interface is part of the
appropriate network.

So that's the easy example -- a single stretched subnet between the
two. What happens if you're using a stretched subnet with a second
subnet for the other node (say, 192.168.1.0/24)? Simple -- you don't
add a default gateway, you add a persistent static route:

route -p add 192.168.1.0 mask 255.255.255.0 192.168.0.1

This adds the following line to the routing table:

192.168.1.0 255.255.255.0 192.168.0.1 192.168.0.16
1

Windows still has a specific route entry in the table to guide the
packets to the correct next hop, without having to resolve between two
default gateways.

Hope this helps.


AllThoseArticles.info

Thursday, January 22, 2009

Exchange 07 Toolbox Tips

Microsoft has linked the Exchange Tools Website into the Exchange System Managers Toolbox. On the Actions Pane click “Open Tools Website” and you will be linked to the Exchange Server 2003 Tools Website. There are some well-known tools like Exmerge, Microsoft Searchadmin and many more. At the time of writing this article there are no publicly available Exchange 2007 tools. For an overview of the Exchange 2003 Web Tools read my article here.



Figure 2: Exchange (2003) Tools Website

I think that Microsoft will update the Website or change the Link to the Exchange Tools in the Exchange 2007 toolbox after the first Exchange 2007 tools are available. Currently we can only use the tools for Exchange 200x. Some of the tools should also work with Exchange 2007 but I haven't tested every tool with Exchange 2007.
Exchange Best Practice Analyzer

The Microsoft Exchange Best Practice Analyzer is now tightly integrated within Exchange 2007, so it is no longer necessary to download and install the Exchange Server Best Practice Analyzer manually. The Update mechanisms will be the same. The Exchange Server Best Practice Analyzer can update itself at start up or at the time you specify in the ExBPA tool.

The Exchange Server Best Practice Analyzer in the Beta I release of Exchange 2007, is older than the Exchange Best Practice Analyzer on the Microsoft Exchange Website so it seems to me that this is not a special version for Exchange 2007.

The Version number of the Exchange Server Best Practice Analyzer on the Microsoft Website is 2.6.7812.0 at the time of writing this article.

The Microsoft Exchange Server Best Practice Analyzer Version that comes with Exchange 2007 Beta I is 2.5.462.19.




Figure 3: Exchange Server Best Practice Analyzer Version from Exchange 2007

But this is not a problem. Try to run the Exchange Server Best Practice Analyzer against Exchange 2007 and you will see some interesting points. There are some differences to Exchange 2007 that the ExBPA is not aware of, but most of ExBPA seems to be working. I’m sure that Microsoft will update the Exchange Server Best Practice Analyzer Tool for Exchange 2007 specific configuration as soon as possible.
Exchange Server Performance Monitor

The second tool in the Exchange Server 2007 System Manager Toolbox is the well-known Exchange Server Performance Monitor. Yes, we are talking about the Windows Performance Monitor. The Exchange Server Performance Monitor in Exchange 2007 comes with some predefined counters related to Exchange 2007.



Figure 4: Exchange 2007 Performance Monitor Counters

Explanation of some Exchange Performance counters

There are two counters that are related to the number of Messages Received and Sent per Second.

Four other counters are specific to the RPC traffic. As all of you might know, Exchange uses RPC for several components and the main E-Mail Client Outlook uses RPC to communicate with the Exchange Server.

On highly utilized Exchange Servers or Exchange Servers with moderate hardware, many of us have seen a high Rate of RPC traffic in Perfmon or the notice in Outlook that Messages are transferred to and from the Exchange Server and the connection is delayed. For this problem Microsoft has released the Exchange Server Best Practice Performance Troubleshooting Analyzer which you can download here. You can read here more about this helpful tool.

Exchange 2007 has been optimized to reduce the RPC workload but you should carefully monitor some of the RPC counters.
Exchange Queue Viewer

The Exchange 2007 Queue Viewer is not new but the component in the Toolbox that has the most changes and improvements.

The Exchange Queue Viewer opens in a separate Window and remains open when you close the Exchange System Manager.

The reason is that the Exchange 2007 Queue Viewer is now built into a Standalone MMC SnapIn.




Figure 5: Exchange 2007 Queue Viewer MMC SnapIn

Like in Exchange 2003 it is possible to show the Messages in the different Exchange message queues. It is possible to Freeze messages or to remove messages from the Queue with or without generating a NDR (Non Delivery Reports).




Figure 6: Overview of the Exchange 2007 Queue Viewer

You can filter messages by several variables and criteria. For example, with Exchange 2007 it is now possible to filter by extended criteria like SCL (Spam Confidence Level) from Microsoft Exchange IMF (Intelligent Message Filter). To create a Filter click Create Filter.




Figure 7: Exchange 2007 Filter selection

In the Actions pane on the right side it is possible to save the created filter as Default or to set the Limit of the number of items to display.
Conclusion

In this article I gave you an overview of the Exchange 2007 Toolbox and how to use each of the tools. All of you should be familiar with this tool. The Performance Monitor is not new to Exchange and Windows, and the Toolbox only links to the Windows Performance Monitor. Nothing new on the Exchange Server Best Practice Analyzer. The version that ships with Exchange 2007 Beta 1 is older than the Exchange Server Best Practice Analyzer on the web but I recommend using ExBPA to see what the tool reports about Exchange 2007. You should also spend some time on the Exchange 2007 Queue Viewer. This tool has some enhancements.
Related Links

Introducing Exchange 2007
http://www.microsoft.com/exchange/preview/default.mspx

Exchange 2007 Overview
http://go.microsoft.com/?linkid=4735035

Frequently Asked Questions about Exchange 2007
http://go.microsoft.com/?linkid=4735036



About Marc Grote

Marc Grote is an MCSA/MCSE Messaging & Security, an MCTS/MCITP and a Microsoft Certified Trainer and MCLC. He is a freelance IT Trainer and Consultant in the north of Germany near Hanover. He works with Invenate GmbH on special projects. You can find more information about Invenate at ttp://www.invenate.de. He specializes in ISA Server, Exchange, Security for Windows 2000/2003 and Windows Server 2008 designs, migrations and implementations, and Citrix Metaframe implementations. His efforts have earned him recognition as a Microsoft MVP for ISA Server since 2004. You can visit his homepage at http://www.it-training-grote.de.


AllThoseArticles.info