Exchange

Exchange 2007 SP1 Out, RTFM FIRST

Exchange 2007 SP1 has shipped today, there is a TON of stuff you need to be aware of before you roll out. This is a significant upgrade that should not just be clicked through without reading the manual. So while congratulations are in order and feature set gold enough to make you go for it right now, hold on, wait a minute..

The set of release notes linked in with the download link points to the RTM (ie, the original release of Exchange 2007, not SP1). The actual Exchange 2007 SP1 Release Notes are here.

I'll break down the SP1 over the next couple of days so stay tuned. If you need to rush and install it today, please read the documentation first.

HOWTO: Troubleshooting Mail Delivery

One of the most frustrating things I do for living is troubleshooting mail delivery. Not because it’s incredibly frustrating and almost never my fault, but because I tend to get pwned by the most ridiculous “gotchas” of the SMTP.

Of the items that I probably deserve a Darwin Honorable Mention award for is troubleshooting delivery for an expired domain name, for a mail server that had the SMTP service stopped, that had the IP address changed, that had the letter 0 or O in the domain name and they just blurred together.

So today I set myself up for another “documentation writing” day and I have to say that I enjoy it. Writing about the products I’ve designed makes me realize how braindead some of our process is, nothing sounds quite so stupid than when you read it back to yourself. It also gives me ideas on how to improve the service, add in some gizmos that could help cut out a lot of time from troubleshooting.

Today, I proudly bring you the OWN Guide for Troubleshooting ExchangeDefender Delivery. Even if you are not an ExchangeDefender customer (come on!) the guide is general and verbose enough to give you an idea how to troubleshoot mail flow, diagnose issues with SMTP servers, create sample email messages from the command prompt.. I really hope you like it.

At the very worst you’ll learn how to install the telnet client for Microsoft Vista / 2008 Server from the command prompt.

Windows PowerShell 2.0 CTP Released

One of my fellow Exchange MVP buddies, Bharat (sounds like "Bart") Suneja is talking about the release of Windows PowerShell 2.0 CTP! Now, before you get overly excited, that CTP acronym stands for Community Technology Preview which is just a fancy name for Beta which is just a pretty name for Broken. So while you should definitely not go buck wild and install this on a production system, kudos to PowerShell team for getting the stuff out into developers hands especially given that the new release supports:

Remoting!!! Jim Harrison and I were talking about this very feature at this years TechEd, and the limitation that seemed almost crippling. Remoting gives you the ability to manage remote systems, execute cmdlets on remote servers which is important because..

You can now write your own cmdlets in PowerShell instead of having to compile .NET code. That in turn is important because:

PowerShell 2.0 comes with a GUI (of sorts) so you can do cool stuff like multiple shells, highlight and run only select pieces of the code..

Now, you do need .NET 3.0 but the boldfaced stuff up threre ought to give you more than enough reason to go get it. If you are new to PowerShell try get-help, if you're experienced you've GOT to check out remoting: get-help About_Remoting

lg-go-away-tshirt Sorry for the inane fanboyism about this but this level of flexibility and automation is what the PowerShell is all about and it allows organizations that rely on these servers to save a ton of time. It's really a two-fold benefit. We spend a lot of time automating the documenting our processes in PowerShell since we have gone to Exchange 2007 and now Server 2008 because it enables us to give higher level administrative functions to the jr admins and not worry about them breaking anything. This shrinks our training requirements, makes sure everything is done according to our process (after all, humans make a lot more mistakes than computers).

So go, check it out. If you're a sysadmin and you're not yet knees deep in PowerShell I hope you're working for the government cause you're becoming obsolete more rapidly than the computer you're reading this blog on. Go, get your dev on!

Two more Windows Mobile phones you shouldn't buy

This has been on my mind for a little while now and sometimes the fanboy eyeglaze needs to wear off before you evaluate things for what they are.

I will never buy another Windows Mobile phone until Microsoft stands behind its platform and here is why you shouldn’t either: It’s not Microsoft.

Microsoft has made its significant wealth by producing business tools that grew, scaled and upgraded. I have never owned a computer that I couldn’t upgrade to the next version of Windows. Our servers have scaled from Windows Server standard, to SBS, to Enterprise with clustering. We (and I) could afford to keep up with the technology and with Microsoft and realize the business and productivity benefits because we did not face a significant hardware charge every time we wanted to implement something new. The idea of Software Assurance further delivers on this promise.

But take that same strategy to Windows Mobile platform. Can you do the same? For a very large population of devices the answer is yes – albeit, illegally.

Want a legal way to upgrade your phone? $499 please. Wait, $499 is $400 more than you advertise a brand new phone for, how can an upgrade cost four times more? Oh! You’re not really upgrading my phone, which is perfectly capable of running the said software, you’re just replacing it with the brand new phone. Oh, and you want at least a two year contract on it too?

This is where the Microsoft – OEM – Telco menage a  trois infuriates the customer and makes them abandon Windows Mobile and crumbles the Exchange, Unified Communications, Windows Platform and the “connected” dream evaporates: They look elsewhere.

I cannot and will not recommend a Windows Mobile phone anymore until Microsoft starts offering upgrades for them, directly from Microsoft’s site. Please do not buy into the lie that only the OEM can write the drivers and only the carrier can publish it because thats a total copout. For literally everyone in my audience that has seen a Windows Mobile demo or a new release preview, just what do you think that demo ran on? Boiling pot of water? Of course not. Microsoft develops and tests this software on the Windows Mobile devices you own and use. Every developer that compiles of a piece of Windows Mobile code already has the architecture cabs as a part of their Visual Studio SDK for mobility so if we can roll out the new OS, if we can compile software for it – what are we waiting for the OEM and the carrier to do? Compile their garbage IM software and design a new theme?

Welcome_hero_20070927OEMs and carriers have the least incentive to implement any software upgrades because it means more support and more documentation work for them. They usually never relase them and you’re stuck buying a new phone. And in business, being forced to buy something new and abandon something functional is equivalent to theft.

Blackjack is my last Windows Mobile phone, even if I get a free one I will give it away.

If you are a business, avoid Windows Mobile until Microsoft chooses to stand behind its platform a little more than just releasing Haloween backgrounds and ringtones.

For those of you that don’t understand what I mean without using crude street language (all complaints should be sent to my PR firms: Tim Barrett & Co in USA and Susanne Dansey, LTD worldwide):

If I wanted to be fucked by a telco carrier and mislead into a product purchase of a toy that will be obsolete the moment I opened the box I would have bought an iPhone.

Big UC News: Yahoo! Acquires Zimbra

Yahoo! acquired Zimbra earlier tonight for cool $350 mil in cash. Zimbra, for the uninformed crowd basically means: Exchange features on Linux. Though its a lot more than that (collaboration, AJAX interfaces) the bottom line is that this is (or was) the main competition to Microsoft Exchange – Lotus and friends included. I must admit, Yahoo! is a surprise, what does Yahoo! gain (or what does Zimbra lose). Smelling the synergy? Here is how they are selling it: 

At the heart of this merger is the conviction that email is a core application and Yahoo! can continue to expand its leadership to new markets using Zimbra. For Zimbra, it was the opportunity to grow our footprint at an accelerated pace and the opportunity to provide innovative and new ways to use Yahoo!'s vast SDKs, trusted brand, vast network of users, great communication applications, core email technology like anti-spam and search as well as its ad network to bring in innovative combined solutions to markets that are still left untapped. At every step of the way, we will ensure that Customers have the freedom of choice in what they deploy.

Zimbra is clearly the big winner here. $350 mil in cash, free advertising, bigger footprint and customer base to pitch to.

What does Yahoo! gain? This takes away from their “everything ought to be hosted on our Yahoo! everything systems” and provides people with a downloadable on-premise, or more key – away from Yahoo!-privacy-concernville. Yahoo! now owns a piece of infrastructure incompatible with their message so was this huge deal just a takeaway to keep a key component away from someone else that has recently been talking about “offlining” their data?

Time will tell, congrats to the boys at Zimbra, Ferrari in every color is the only way to go….

Exchange 2007 "Bookmark-Me" SP1

Over at You Had Me At EHLO, Cathy has published the updated documentation links for Exchange 2007 Service Pack 1. There is a lot of new stuff coming, and the new features address pretty much all the issues that clients have raised and will let us roll out Exchange 2007 where we previously faced resistance or felt we ought to hold off on an upgrade.

Exchange 2007 Service Pack 1 Documentation

I got to spend a lot of time at TechEd with Cathy and with a few folks from the documentation team, they have really outdone themselves when it comes to documenting this product.

 

Need help with Exchange!

Ever find yourself saying that? I’ve gotten quite a few questions now that I’ve resumed my tech writing and apparently there are a lot of you that realize you might have been sitting on some pretty poorly configured and managed systems. But how do you get help?

Let me first make it clear that I do not do non-enterprise Exchange consulting, so unless you’re on the Fortune 500 list, I can’t help you. Articles and posts you read here are absolutely as-is and I’m sharing them with you in hope that you learn something and get more of a handle on your IT. You’re not required to buy ExchangeDefender, though that would be very nice, but I will always link it when I talk about perimeter security because thats something I know in-depth and can speak about with a high degree of authority.

So how do you get help? Say it with me:

M i c r o s o f t T e c h N e t

URL is a little difficult to remember but if you Google for “exchange newsgroups” it will always be the first result.

So if you ever have a question about any of my current/past/future posts about Unified Communications (Mobility, Messaging, VoIP, Presence) this is the place to go.

Exchange 2003 Mailbombs slowing you down?

The other day I wrote an article on why you should consider limiting the session concurrency to RFC established standards if you don’t have decent perimeter security. Your really should get something, but there is quite a bit you can do yourself to help deal with mailbombs.

Mailbombs, you say? Yes, mailbombs. Kind of like how you spec’ed that server for 10 employees and never considered it would have to one day deal with 10,000 messages an hour? Well, it’s happening. The more systems get owned, the more computers get compromised, the larger the broadcast storms become. And yes, you get to hear it first because I run one of the largest mail networks in the world, but don’t think for a minute that these threats aren’t coming down to you. Over the past week I have been hearing from one partner after another that has his or hers appliance on its knees. Why? The volume is explosive.

And even without perimeter security, there is something you can do with Exchange 2003 alone. Let’s look at some Default bafoonery:

Exchange2003vsp

Yes, those are Exchange 2003 default settings. The two of particular interest are the limits for the number of messages per connection and number of recipients per message. You can just look at those limits for a second and note their absurdity – 64000 recipients per message?

Exchange2003vsp1

Another area of interest is the checkbox next to “Perform reverse DNS lookup on incoming messages” – some folks had a bright idea to use this as an antispam measure. Please do not. If you’re being mailbombed the last thing you want to do is reduce your mail flow to a crawl while you run a DNS query for each incoming connection.

Finally, the least likely option to appeal to you: disable IMF. IMF bayesian (SmartScreen) technology is very expensive when it comes to resources and can easilly exhaust your systems resources during the high load averages – so turn it off and let the workstations deal with the issue. Unless you are rejecting fairly low scores, having IMF around during mailbombs will not help you. Don’t think IMF is killing your box? Get some stats:

Imfv2

You can get performance counters. Two of particularly interesting ones are “MSExchange Intelligent Message Filter \ Total Messages Scanned for UCE” and “MSExchangeMTA Connections \ Inbound Messages Total” which given a little bit of time and resources will show you when you are experiencing spikes and whether you’re truely experiencing a problem to begin with.

Obviously, it is fairly difficult to tell if you have an anomaly if you don’t know what your baseline (“known standard metric” or “business as usual”) numbers are so its important to actually manage your servers. Those tasks, and the above settings and defaults explained in detail is of course a subject for a lengthy article…. but if you’re getting swamped right now this ought to help you out just a little bit while you weather the storm.

Throttling Session Concurrency with SBS / Exchange 2003

I have really slacked off when it comes to my Technical Articles but I have to say that last two weeks of direct involvement with ExchangeDefender and fighting spammers has really reinvigorated my passion for helping people deal with this scum. So, what’s the problem?

Having any email troubles as of late? Email messages delayed? Coming in out of sequence or with a large delay? How about peers asking you why you haven’t responded to an email they sent you (and you explaining that you’ve just never seen it?)

If that sounds familiar, you have been a victim of a latest botnet, which whether intentionally or inconsequently, launched a large scale DDoS attack against many mail servers on the Internet.

This post shows you how to throttle down session concurrency with SBS / Exchange 2003.

I would like to thank my good friend Karl Palachuk for being a true leader and writing a series of blog posts on managed services that really encouraged me to start sharing my technical expertise with my audience. I hope you guys enjoy it.

Note: I wrote the post completely and totally drunk. I hope that is enough to excuse any typographic errors.