Recently in General Stuff Category

In part 1, I started talking about how I got into the writing business. Part 1 ended with me having written a couple of non-Windows-related books (including this) and contributing to several Windows-oriented books (like this). I began to wonder if it made sense for me to get an agent, so I started talking to David Rogelberg, the owner of StudioB. He offered me the tempting possibility of being able to write for O'Reilly, something I had always wanted to do. I signed on as a StudioB client and, true to his word, David got me in touch with O'Reilly about writing a book on programming for the Palm Pilot.

Of course, I didn't know anything about programming for the Pilot, but I wasn't about to let a minor technicality stop me.

What did stop me was a communications mixup between Robert Denn, my editor at O'Reilly, and another ORA editor who shall remain nameless. This other editor had signed Rhodes and McKeehan-- the experts who had written a book on Newton development too-- to write a Palm programming book. That left them in the position of having two PalmOS books under contract, only one of which would be written by, y'know, people who knew what they were doing.

Robert offered to let me write a book on another topic. In fact, he even gave me my pick of topics. I wish I could say that I jumped at the chance to write about Exchange, but I didn't. I had to be more-or-less bullied into it my my agent, who realized the long-term potential of working in the Exchange market. I didn't know anything about Exchange either, but I was quickly determined to learn, given that I had just signed a contract to write about it. I started joining every Exchange-related mailing list in sight, printed out all the product documentation, and set up Exchange using Virtual PC on my Powerbook. (Yes, that's right; my O'Reilly Exchange book was written on a Mac-- a trend which continues to this day).

I learned sooooo much from the folks on the swynk Exchange list. Not only were there rock stars like Andy Webb, Missy Koslosky, and Ed Crowley there; there were also a ton of Exchange developers. Just to cite one example, one of the primary perpetrators of the Exchange 5.5 MTA was on the list, as was Laurion Burchall, one of the key ESE developers. Everyone on the list was super generous with their time and knowledge, and it didn't take me long to get up to speed. (My first "live" exposure to the community, though, was attending the 1998 MEC. I was there when Tony Redmond made his famous "I'll pass on the clap" remark, and I heard Pierre Bijaoui explain that the average human has one breast and one testicle!)

Coincidentally, at about the same time I got a call from O'Reilly: Windows NT Pro magazine was looking for someone to write a regular Exchange column. Was I interested? You bet I was! I started writing it in September of 1998 and it's been in print ever since, although it's morphed into a few different forms.

All this time I was still holding down a real job at LJL Enterprises, writing crypto code on the Mac. Eventually my agent brought me an offer that was too good to refuse: Ford Motor Company wanted someone to write a book about their CAD system. I gave my two weeks' notice, set up my home office, and got ready to hang out my own shingle as a full-time author. That's when the real adventures started...

End-of-the-year randomness

| 1 Comment

Wow, how did it get to be the end of the year already? I've fallen down on my blogging bigtime, but I have ambitious plans for 2010-- mostly consisting of posting a batch of articles at once and letting MovableType publish them on a schedule. That way when I'm in the blogging mood I can write up a bunch of stuff and post it.

A few end-of-the-year notes:

  • Christmas was wonderful, even though (or perhaps because) we were here by ourselves. We gave Mom and our boys a Disney cruise, which means I'll miss the MVP summit this year. I think it's a reasonable tradeoff, though.
  • Julie and Paul gave me Cruise Ship Confidential, which was a real hoot. The author struck me as someone I'd love to sit down with over lunch. If you like true-confessions-style books, this one's excellent.
  • Lego Rock Band is a ton of fun, especially with the boys. We also gave them Lips: #1 Hits, which is way more fun than I expected it would be. No surprise that the Lips wireless mic works with the Rock Band family, and having a wireless mic makes those games more fun (and easier for us to stage).
  • I bought a USMC license plate frame from the Stars and Stripes Shop. It was cheaper than any place else I found, I got it in two days, and they sent me a 10% off code to share: sssfrienddec09. Share and enjoy!
  • This year's Aviation Week & Space Technology photo contest winners are even more awesome than usual. The little tiny online versions don't really do the pictures justice; if you can find the print magazine, you'll see what I mean.
  • One of my coworkers is an Iowa fan-- the first one I've ever met in the flesh. Too bad his team is going down when they play the mighty Yellow Jackets.
  • Speaking of work, I'm really excited about some of the stuff we're going to be doing. I can't share any details yet but there are some exciting things coming up.

I probably won't be posting again this year, so until next time, have a wonderful New Year's Eve and get ready for a great 2010!

Jeri Wendt, a friend of mine from Perrysburg Rotary, sent me this note, and I wanted to share it. If you have a loved one with Alzheimer's in metro Toledo, please look into Paul's Peers and support them in any way you can.

When you come across something that you care about and think others may benefit from you just HAVE to pass on the good word… so, please take a minute and read about something that makes my life so much better.

For those who don't know, my mom has Alzheimer's. My older brother and I share in her care and luckily for us, about three years ago, we discovered Paul's Peers Respite Care in Maumee where we take her four days a week. (See attached article featuring me and Mom!). Paul's Peers is a senior day-care center whose main purpose is caring for elderly people who need assistance. This includes people with Alzheimer's. It is a place to drop off your loved one knowing they will be cared for by the kindest people you would ever hope to meet. For $35 a day you have up to eight hours of free time for yourself and in our case, Mom gets a day away from us. (A win-win situation!)

I am sending this to you in case you know of someone who would be interested in this program. Due to the economy, many people aren't working now and are staying at home with their loved ones eliminating the need for elder care during the day. Much to our dismay, Paul's Peers has had to temporarily stop care on Tuesdays due to lack of enrollment. So… if you have a spouse, parent, grandparent or know of someone who could use this service please let them know. It is a program offered as much for the care giver as it is the recipient.

We would not be able to have my Mom stay at home were it not for this “gem”. We drop her off at 9:00 in the morning and her day begins with a continental breakfast, (donated by Panera Bread), and David, the assistant director, reading the newspaper and discussing current events. The rest of the day the incredible staff keeps things interesting by mild exercises, playing games and cards, watching old movies and listening to music with weekly entertainment such as an accordion player or a story teller. Other events are bi-weekly manicures, trips to the movie theater, crafts, tea parties, church every Wednesday and visits from the children's day-care. The staff patiently learns the likes and dislikes of each participant and gently works with them accordingly. It didn't take them long to find out my mom is an avid gin-rummy player who is tough to beat!

There you have it... now you know. If you don't have the need right now maybe sometime in the future you will have a friend who is at wits end and needs a break. You can offer them a solution.

Paul's Peers Respite Care

St. Paul's Episcopal Church

310 Elizabeth Street

Maumee

(419) 893-3381

Last month I wrote about my experience with American Standard's warranty process. I praised them a little too soon.

Friday, I installed the new "Champion 4 Accelerator" flush unit. Rather than the old-style flush tower, the Accelerator is a short, wide cylinder with a domed lid an an L-shaped overflow tube. When you push the handle, the lid lifts, and the accumulated water dumps into the trapway. Installation was easy, and the kit American Standard sent me included all the hardware I needed, including new tank bolts. Unfortunately, the new valve's performance was actually worse than the flush tower.

It turns out that the design of the Accelerator leaves about 4" of water in the tank. In other words, it doesn't deliver enough water through the trapway to empty the bowl. Ooops. Its height isn't adjustable, either. I set the water level to about 1/4" below the overflow tube, and that didn't do it. Thus it was with great irritation that I put the old, broken flush tower back into the hall bathroom yesterday. To compound the problem, American Standard doesn't take phone calls on Saturday, so I'll have to call them and find out what the suggested fix is.

Now I see why there's a class-action lawsuit against them over these toilets.

Last month I wrote about my experience with American Standard's warranty process. I praised them a little too soon.

Friday, I installed the new "Champion 4 Accelerator" flush unit. Rather than the old-style flush tower, the Accelerator is a short, wide cylinder with a domed lid an an L-shaped overflow tube. When you push the handle, the lid lifts, and the accumulated water dumps into the trapway. Installation was easy, and the kit American Standard sent me included all the hardware I needed, including new tank bolts. Unfortunately, the new valve's performance was actually worse than the flush tower.

It turns out that the design of the Accelerator leaves about 4" of water in the tank. In other words, it doesn't deliver enough water through the trapway to empty the bowl. Ooops. Its height isn't adjustable, either. I set the water level to about 1/4" below the overflow tube, and that didn't do it. Thus it was with great irritation that I put the old, broken flush tower back into the hall bathroom yesterday. To compound the problem, American Standard doesn't take phone calls on Saturday, so I'll have to call them and find out what the suggested fix is.

Now I see why there's a class-action lawsuit against them over these toilets.

I finally found the comment problem: an obsolete version of the Javascript site template. Somehow I missed it during one of the (multiple) MT upgrades. Comments appear to be working properly now, which will no doubt thrill the two or three people who regularly visit here (hi, Mom!)

I finally found the comment problem: an obsolete version of the Javascript site template. Somehow I missed it during one of the (multiple) MT upgrades. Comments appear to be working properly now, which will no doubt thrill the two or three people who regularly visit here (hi, Mom!)

Well, not really. They did, however, overturn their longstanding style rule that says that "Marines" shouldn't be capitalized. The Marine Corps Times has the whole story, drawn from the Times' Philip Corbett's blog entry here. Semper fi, Old Gray Lady!

UT is doing a series of "Saturday Morning Science" presentations on topics ranging from wind farming to inflammation to aluminum. I'll definitely be hitting these with the boys. Here's the link (hat tip: Mark Chandler)

UT is doing a series of "Saturday Morning Science" presentations on topics ranging from wind farming to inflammation to aluminum. I'll definitely be hitting these with the boys. Here's the link (hat tip: Mark Chandler)

From a friend in the Seattle area who wanted to stay anonymous:

  • Most of my disasters preparations; food, water, generator, water filters, supplies, etc... are for the days after things go bad. Getting through the first 24 hours in the best possible condition is much more important. How you get through and what you do in the first 24 hours will set the tone for everything that follows.
  • Do you know where your community rally point is? Where emergency services will be available? Where to get sandbags? Closest chopper pad?
  • Disasters are a come as you are event. I spent the first three hours of the flood in slip on moccasins and sweat pants. No gun, no multi-tool, just my Spyderco knife and a Sharpie. If it isn't on-hand in three minutes or if you don't remember that you have it or exactly where it is, it might as well be on the moon.
  • Don't overfill sandbags. 90% full is about optimum. That way, there's room in the bag for the sand to shift, conform to the space to fill in the gaps.
  • A wheelbarrow. Its not just for farmers. You can move twice as much material for less effort in a wheelbarrow than by carrying it. I recommend the dual-wheeled models as they're more stable and less likely to get stuck in the mud.
  • Energy drinks. Legalized "speed" that will carry you through with extra energy when you need it.
  • An American flag, pole and holder. Hanging the flag outside your residence is a good way to signal to aid/rescue that your house is occupied.
  • Pre-packed disaster equipment. Hoses with your pumps, extension cords with your generator. Saves time and effort as everything is in the box ready to go so you don't have to gather it up or remember where it is under pressure.
  • Physical skills. Do you know how to build a sandbag wall quickly and efficiently? (I never thought about it before now.) Do you know how to drive your SUV through deep water? How deep can you safely go?
  • You might be prepared and know what you're doing, but there's lots of idiots out there. Law enforcement and officials are going to assume you're the latter until they see otherwise.
  • Hand sanitizer.
  • Your most useful tool is the one between your ears.

There's some very thought-provoking advice in the above, especially knowing your community and convincing the local law that you're not an idiot. I know I'll be applying this list to our family's disaster planning.

Christmas Fish update

| No Comments

So the boys and I took care of the Christmas Fish on Christmas Eve. First we called Bassett's Market. Nope, they don't process fish, but they suggested calling Churchill's. Nope, they share a sink between the seafood and deli department and didn't have time to sanitize it-- but they told me to call Rohr's. I did, and they handled the fish with no muss and no fuss. (Turns out it was a snapper from Costa Rica, not a rock cod). As a bonus, the boys and I had lunch at the Chinese buffet across the street from Rohr's.

As a second bonus, the smoked salmon arrived Tuesday as planned. Good eatin'!

How I joined the Marine Corps

| No Comments

@ihenpecked on Twitter just said he wasn't sure if the Marines would have been right for him. I didn't think they were right for me, either.

Flashback: it's 1986. The Cold War is happening, big time. I wanted nothing more than to fly jets, pretty much for whoever would have me, but I certainly didn't work hard for it. I made a desultory effort to be nominated to the Air Force Academy or Annapolis, but my heart wasn't in it (and neither were my grades, sadly). More or less as a lark, I took the ASVAB and did pretty well on it. That resulted in a flood of calls from recruiters. All the Air Force guys could talk about was missile maintenance, and the Navy recruiters kept talking about subs and nuclear power, neither one of which I wanted any part of; I was firm on going to college and couldn't see putting that aside for active-duty service.

I had no interest in the Army or Marines, and told their recruiters that. The Army guy took me at my word, but the Marine recruiter, bless his heart, was made of sterner stuff. He kept calling me every few weeks, and it seemed like he always knew when we were sitting down to dinner. I finally agreed to go to his office to talk to him, and that was my downfall: he totally sold me. He convinced me of the benefits of serving in the Marine Corps Reserve, and that it was better to "test-drive" military service before making the commitment to get a commission and the obligations that come with it. (Advice that I took, having heard it from my grandfather, a WW II vet and retired USAF pilot.)

I left for boot camp about four months later, two days after graduating from high school. Then the real fun started :)

Helicopter ground resonance

| No Comments

This one's for you, Jim. Air & Space has a great article on ground resonance in helicopters. Basically, if you get the blade system to vibrate at just the right frequency, the helicopter tears itself apart. A couple of related videos: here's one of a US Army Chinook from the rear, and another from the side.

Amazon just e-mailed me an announcement: if you buy a minimum of $25 worth of stuff from their Music CD, Audio/Video, Camera, Photo & Video, Office Products, PC or Wireless stores in a single order, you get an instant $5 credit at AmazonMP3. This is particularly cool because AmazonMP3 has a long list of albums priced at $5 and under.
Amazon just e-mailed me an announcement: if you buy a minimum of $25 worth of stuff from their Music CD, Audio/Video, Camera, Photo & Video, Office Products, PC or Wireless stores in a single order, you get an instant $5 credit at AmazonMP3. This is particularly cool because AmazonMP3 has a long list of albums priced at $5 and under.

Free Christmas music from Oprah

| No Comments

I'm normally not a huge Oprah fan, but she's giving away 8 MP3-format Christmas songs by different artists, including Faith Hill and Aretha Franklin. Visit http://www.oprah.com/article/oprahshow/20081118_tows_holiday/2 to download them.

Every year, I write an Exchange UPDATE column with gift suggestions for your Exchange administrator (here are the 2007 and 2006 editions). This year I decided to try something different; I hit up HelpAReporterOut to put my query in front of about 35,000 people. The responses started to arrive almost immediately.

First responder: the folks at PCWeenies sent me a blurb about custom-drawn comics featuring your favorite admin. Neat idea, and very timely response. This is definitely a contender: it's unique, and it would make a nice keepsake.

Best comment: "The best gift you can give a SysAdmin is a Faraday Cage that blocks cell phones, pagers, and WiFi: it cuts off all connection to the outside world. It's _very_ popular with their wives, too!" I bet it would be popular! Sadly this respondent didn't give me a source to actually buy them. Time to break out the power tools!

Least likely to actually be given as a gift by anyone I'll ever work for: plasma TVs from a very large consumer electronics company who shall remain nameless. Great idea, but probably violates whatever office-Christmas-gift price policy your company has. If your company thinks it's OK to give its Exchange admins such expensive gifts, please contact me for a resume.

Least likely to actually be given, runner-up: a one-question "stocking stuffer" e-mail exchange with a Hollywood psychic.

Coolest suggestion I never would have expected: handmade stamped-metal keychains. Check them out.

Claim most in need of testing: "[IgnaFire chocolate] morsels are SO strong in flavor and texture, that a very small amount satisfies. No one can eat this chocolate by the handful." We'll just see about that; I ordered some for Arlene, whose expertise in the world of chocolate is known throughout the world.

Apart from these, I've gotten some very cool leads for potential gift ideas, and I'll be going through them for the remainder of the week to come up with the best list for next week's column.

Every year, I write an Exchange UPDATE column with gift suggestions for your Exchange administrator (here are the 2007 and 2006 editions). This year I decided to try something different; I hit up HelpAReporterOut to put my query in front of about 35,000 people. The responses started to arrive almost immediately.

First responder: the folks at PCWeenies sent me a blurb about custom-drawn comics featuring your favorite admin. Neat idea, and very timely response. This is definitely a contender: it's unique, and it would make a nice keepsake.

Best comment: "The best gift you can give a SysAdmin is a Faraday Cage that blocks cell phones, pagers, and WiFi: it cuts off all connection to the outside world. It's _very_ popular with their wives, too!" I bet it would be popular! Sadly this respondent didn't give me a source to actually buy them. Time to break out the power tools!

Least likely to actually be given as a gift by anyone I'll ever work for: plasma TVs from a very large consumer electronics company who shall remain nameless. Great idea, but probably violates whatever office-Christmas-gift price policy your company has. If your company thinks it's OK to give its Exchange admins such expensive gifts, please contact me for a resume.

Least likely to actually be given, runner-up: a one-question "stocking stuffer" e-mail exchange with a Hollywood psychic.

Coolest suggestion I never would have expected: handmade stamped-metal keychains. Check them out.

Claim most in need of testing: "[IgnaFire chocolate] morsels are SO strong in flavor and texture, that a very small amount satisfies. No one can eat this chocolate by the handful." We'll just see about that; I ordered some for Arlene, whose expertise in the world of chocolate is known throughout the world.

Apart from these, I've gotten some very cool leads for potential gift ideas, and I'll be going through them for the remainder of the week to come up with the best list for next week's column.

This year's edition of the annual Ohio State-Michigan game has been cancelled. The Wolverines were on their team bus headed down to Columbus, but unfortunately they couldn't get past Toledo. (But hey, neither could the Marines, so don't feel bad, UM fans!) All kidding aside, the boys and I will be watching tomorrow, probably with a plate of boudin in front of us. Go Bucs! (oh yeah, then LSU plays, and then the Saints are on Monday night!)

A birthday rickroll

| No Comments

I got rickrolled for my birthday today.

I'm in Redmond for meetings with customers and our team. Our company tradition is that we bring in cake of some kind when people celebrate their birthdays; my birthday is tomorrow, and Jason Weiss (one of our QA team members) has his birthday today.

About 1:30p, everyone gathered in our break room, and Paul Flynn brought in a big ol' chocolate cake. It was strangely rectangular, but the frosting made it look good. I was a bit skeptical when Paul said he'd baked it himself, but I took the proferred knife and tried to cut it. It was oddly crunchy when I cut it. Paul let me saw away at it for a few seconds, then removed the cardboard box that was covering the real cake... adorned with a picture of RIck Astley himself. At the same time, Tim started playing the original rickroll clip from YouTube.

1007149.jpg

This all came about because back in the spring I managed to rickroll nearly the entire company via a well-crafted e-mail. Apparently they collectively decided to get their revenge on me via cake, so I am happy to say that the cake was, in fact, not a lie.

Happy 233rd birthday, USMC!

| No Comments

Tomorrow marks the 233rd birthday of the world's finest fighting force: the United States Marine Corps. Semper Fidelis to all my brethren who have served or are serving our nation as Marines and corpsmen. On this day, I hope you will join me in celebrating the Marines' traditions of honor, service, and duty. Here's the Commandant's annual birthday message to help get you in the mood.

Remembering Samuel Nicholas

| No Comments

Every Marine knows the name of Samuel Nicholas, the Quaker businessman and farmer who was commissioned as the first officer of the Continental Marines back in 1775. For the rest of you, here's an interesting article on the quiet and little-known ceremony that marks the founding of the Corps each November 10th. Semper fi, Major Nicholas.

Still here, just quiet

| No Comments

It's hard to believe it's been two weeks since my last posting here (and, at that, it was a short rumination on vegetables.) Since my last post, a lot has happened:

  • I decided to forgo my spot in the first Microsoft Certified Master: Exchange class. This was a very difficult decision, but it turned out to be a good one because…
  • Mom sold her house in Perrysburg. It closes in late October, which means we essentially have a month to help her get packed up, moved out, and down to Louisiana. We've been busy with various house-related tasks, like turning the lights on for showings and so forth.
  • I got some kind of stomach flu of doom that made me sicker than I've been in 20 years. I'm talking full-blown, flat-out, can't-hardly-get-out-of-bed sick. Fortunately, it only lasted a couple of days, but it was rough during that time. The kids and I have all intermittently had snuffles, too
  • We got our hardwood-- all 1900+ square feet of it-- refinished. This sounds easier than it is; it involved compressing several rooms worth of furniture into the living room, master bedroom, and kitchen, then living in it for two weeks. The results are beautiful but we're all eager to get everything put back where it belongs.

Of course, it wasn't all drudgery; I watched the LSU-Auburn game with Mom, Arlene, and the boys, played a bit of Rock Band 2, and so on. I hope to get back on a more regular posting schedule. There are certainly a lot of developments in the unified communications world to talk about!

Still here, just quiet

| No Comments

It's hard to believe it's been two weeks since my last posting here (and, at that, it was a short rumination on vegetables.) Since my last post, a lot has happened:

  • I decided to forgo my spot in the first Microsoft Certified Master: Exchange class. This was a very difficult decision, but it turned out to be a good one because…
  • Mom sold her house in Perrysburg. It closes in late October, which means we essentially have a month to help her get packed up, moved out, and down to Louisiana. We've been busy with various house-related tasks, like turning the lights on for showings and so forth.
  • I got some kind of stomach flu of doom that made me sicker than I've been in 20 years. I'm talking full-blown, flat-out, can't-hardly-get-out-of-bed sick. Fortunately, it only lasted a couple of days, but it was rough during that time. The kids and I have all intermittently had snuffles, too
  • We got our hardwood-- all 1900+ square feet of it-- refinished. This sounds easier than it is; it involved compressing several rooms worth of furniture into the living room, master bedroom, and kitchen, then living in it for two weeks. The results are beautiful but we're all eager to get everything put back where it belongs.

Of course, it wasn't all drudgery; I watched the LSU-Auburn game with Mom, Arlene, and the boys, played a bit of Rock Band 2, and so on. I hope to get back on a more regular posting schedule. There are certainly a lot of developments in the unified communications world to talk about!

Vegetables shrink your brain

| 2 Comments

From the "I knew it" department: eating vegetables makes your brain shrink.

Vegetables shrink your brain

| 2 Comments

From the "I knew it" department: eating vegetables makes your brain shrink.

Wow! This puts Arlene's complaints about my snoring in a whole new light. Apparently, heavy snoring is a risk factor for carotid atherosclerosis, as measured by an Austrian research team. Better keep an eye on that (or an ear!)

It's always fun to joust with my friend Bob Thompson, who is perhaps the most libertarian libertarian I know. Sadly, I think he's flat-out wrong about food allergy warnings. I admit to being biased; my wife is gluten-intolerant and I have other relatives (and friends) who suffer from various kinds of nut allergy.

The problem with the current labeling standard is this: there is no standard. Quick: what's the difference between "may contain", "made in the same factory with", and "produced on the same equipment with"? If I have three products with those labels, how can I tell which one(s) (if any) are OK to bring home? The existing US law, FALCPA, requires manufacturers to label products that contain certain allergens. Manufacturers have voluntarily been adding "may contain"-style warnings to reduce their liability-- but there's no standard for doing so, and this is resulting in a lot of needless hassle for the producers and consumers.

On the gluten-free front, there is an existing EU standard for deciding which products may be labeled as "gluten-free", based solely on measured gluten content in the final product. The FDA is in the process of adopting it, which I think is great: it gives people a tangible indicator of whether something is safe to eat, or not, irrespective of where and how it was produced. Until then, I don't see how standardizing on a labeling phrase could possibly be a bad thing. In fact, if I'm going to have the government spending money on regulations, better they should do it for food safety than on firearms or political contributions.

Get a Kindle for $259

| No Comments

This is a pretty sweet deal: Amazon will sell you a Kindle for $259 if you apply for (and qualify for, it must be said) their Amazon-branded credit card from Chase. See details here. (Bonus link: James Fallows on how to avoid becoming a Kindle nerd-bore).

Experimenting with Twitter

| No Comments

I've decided to give Twitter a try. So far, I'm following Chris, Ed Brill, Erica, and Al Tompkins. Follow me here.

Droppin' science for real

| No Comments

Droppin' science for real

| No Comments

Brooke Adams of the Salt Lake Tribune handles the polygamy beat for the paper. Yes, that's right; the Trib has a dedicated reporter who researches and writes stories about polygamists. Because of her topical knowledge, she's written some very interesting stories about the Texas polygamy case. Alone among her peers, Adams challenged the legality of Texas' raid on the FLDS compound, pretty much from the start. This Poynter article has a great Q&A with Adams-- well worth reading. How I wish we had more investigative reporters like her, and fewer like the kind we see on FoCNMSNBC.

Brooke Adams of the Salt Lake Tribune handles the polygamy beat for the paper. Yes, that's right; the Trib has a dedicated reporter who researches and writes stories about polygamists. Because of her topical knowledge, she's written some very interesting stories about the Texas polygamy case. Alone among her peers, Adams challenged the legality of Texas' raid on the FLDS compound, pretty much from the start. This Poynter article has a great Q&A with Adams-- well worth reading. How I wish we had more investigative reporters like her, and fewer like the kind we see on FoCNMSNBC.

One of the record companies' major beefs with Apple is that Apple won't let them charge variable prices. One of the chief reasons that Amazon was able to get permission to sell non-DRM MP3 files is because they do in fact use variable pricing. That means, of course, that Amazon can offer things on sale from time to time. Today I picked up Weezer's Pinkerton for $2 and Led Zeppelin's Mothership for $5-- significantly cheaper than buying the album, or the individual tracks, from iTunes. The only way I know of to get notified of these sales is to sign up for Amazon's MP3 newsletter (or check slickdeals.net daily, which is what I do).

Random quote meme

| No Comments

So, Devin tagged me with the latest random meme circulating through the intertubes. Without further comment, here are my five quotes:

Bear Bryant's devotional
Time is the one thing we can't get any more of. How we choose to use our time says a lot about our self and our values.
"I teach them correct principles, and they govern themselves".
Joseph Smith, Junior, founder of the Church of Jesus Christ of Latter-day Saints, said this when asked how he managed the rapid early growth of the church. This is exactly the strategy Arlene and I are trying to follow with the boys, but some days I think it works better than others.
"It doesn't matter how long you've been in the Corps; you'll always be a boot to someone."
My senior drill instructor, Staff Sergeant Taylor, told our platoon this one night at Parris Island. His point has stuck with me ever since: no matter how smart or skilled you are, there's someone out there smarter and more skilled, so don't get cocky.
"Don't get stuck on stupid".
Lt. Gen. Rusell Honoré said this during a press conference after Hurricane Katrina. Would that the national media had taken his advice. I try to take it daily. When you think you're not stuck on stupid, that's precisely when you need to double-check.
"What you do speaks so loud I cannot hear what you say."
Ralph Waldo Emerson is the claimed originator of this quote. I have never been a big Emerson fan (even less so after reading Kim Stanley Robinson's climate-change trilogy), but this quote neatly sums up the importance of trying to live in harmony with one's beliefs.

In retaliation, I tag Arlene, Julie, Tim, and Ed.

More England

| 1 Comment

I'm on the plane, headed home after a quite successful UC Metro event. A good time was had by all :)

While I was in Reading, I stayed at the Hilton St. Anne's Manor, Bracknell (which is actually in Wokingham, go figure). It's an old manor house that has been converted to a hotel, and quite nicely at that. The hotel sits on about 25 acres of land, including both wooded and open spaces. On arrival, the desk clerk upgraded me to a room in the "Buckhurst Club" area of the hotel; apparently that's where they put HHonors members. My room was quite nice, with a small patio that looked out onto the (grass) tennis courts. When I arrived, there were three fat rabbits outside my patio, munching happily on the lawn. However, the air conditioner didn't work. Normally this would not have been a problem, except that the kind souls who prepared my room had turned on two halogen lamps, apparently early that morning. Between that and the fact that the room faced south, the room temperature was about 85°. I slept on top of the covers with the door open; after an undistinguished hotel breakfast the next morning, I headed out, asking the clerk to fix the air conditioner during the day. I got back to the hotel about 11pm after visiting the local mall cinema to watch Iron Man (summary: it's made of win!), but the air conditioner wasn't fixed. The surly night clerk sent one of the housekeeping staff to look at it, and she concluded that--sure enough-- it was broken. As a result, I moved to another room, just as nicely outfitted as the first but with working air (and, thankfully, no halogen lamps). The staff quality varied pretty widely, from ignorant and surly to helpful and pleasant, but the weather and grounds made up for that. In the photo below, if you look closely you can see my laptop on the table under the umbrella... sure a lot nicer than working in some drab office somewhere.


Hilton St Anne's Bracknell patio view

Tuesday was uneventful: I got up, went to work, taught, and went back to the hotel.

Wednesday I repeated the pattern, at least until the class was over. I had intended to stay at the London Temple accomodation center, but they close the doors at 7pm. By the time my class was over, I had to catch the 5:35 train to Gatwick, which put me there right about 7pm. Instead, I booked a room at the Hilton Gatwick: the last-minute rate was cheap, and I hoped that I'd be able to easily get to the terminal in the morning. It turns out to be quite a hike from the terminal to the hotel, but then the same is true of the Sofitel, so no big deal.

The Hilton itself was quite nice-- just a basic airport hotel (albeit with terrible, fuzzy TV reception). They upgraded me to the "executive floor" (ha!), with a small lounge with a nice variety of drinks and snacks. I wanted a real dinner, though, so I roamed the airport shopping area, looking for food, and found a place to have a panini while watching the UEFA Cup final. I then discovered that Marks & Spencer had a small "Simply Food" convenience store, where I bought some snacks for the boys and... drum roll... a two-pack of scotch eggs.

Let me describe the joy of scotch eggs. First, you boil an egg. Then you wrap it in minced sausage (spicy is better, of course), bread it, and deep-fry it. Delicious! Unfortunately, the custom is to eat them cold; Simply Food keeps them in the cooler, and I didn't have any way to heat them up. However, they were still delightful. I'm glad I finally got to try them. (I also had fish and chips while in Reading, but I understand they don't really taste right unless you eat them out of wax paper at the seashore.)

At lunch on Wednesday, I told the class attendees that this was my first visit to the UK. This sparked a lively conversation about how my expectations matched up to the reality, and what surprised me. So, in no particular order, a few thoughts:

  • Everywhere I went, I saw electricity-saving devices like speed-sensitive escalators and individual light fixtures with motion sensors. However, nowhere did I see any water-saving devices like automatic faucets. (And speaking of faucets: for some odd reason, many of the restrooms I saw lacked dividers between urinals, but had floor-to-ceiling walls on the toilet stalls... a little TMI to brighten your day!)
  • At the hotels, airports, and shops, I was surprised to see how many jobs were taken by immigrants from Eastern Europe.
  • I loved the ubiquity and ease of public transport, although it seemed rather expensive. The office park where I was teaching had a free bus that ran between the offices and the town center (where the train station is), and the train system was easy to figure out and use.
  • Shops and businesses close much earlier than I had expected. For example, there's a large mall near Gatwick (well, it's in Croydon), but it closes at 5pm. Hard to get much shopping done on that kind of schedule.
  • In the mall, on the train, and on the street, women tend to dress better than they do in the US. Not so much for the men, however.
  • Over and over I heard how unusual the nice weather was. That's a bit scary.
  • I was very surprised to find out that this is not only legal but widely available in England.

China earthquake

| No Comments

On the China earthquake, from a friend who manages the Chinese manufacturing and development teams at a large company:

It’s much, much worse than what you hear through western channels. Think of 80% of downtown Seattle destroyed at 3PM on a weekday. Give if you can.

China earthquake

| No Comments

On the China earthquake, from a friend who manages the Chinese manufacturing and development teams at a large company:

It’s much, much worse than what you hear through western channels. Think of 80% of downtown Seattle destroyed at 3PM on a weekday. Give if you can.

Missing Connections

| 1 Comment

I thought I'd posted on this Tuesday night, but apparently I didn't. Anyway...

I've been speaking on Exchange and other topics professionally for about ten years. During that time, I've probably spoken at more than a hundred events, ranging from the small to the gargantuan, and I've only cancelled one. Tuesday afternoon, I made the really difficult decision to cancel another, my appearance at Connections. My wife has been ill for the last week or so, and I just wasn't comfortable leaving her alone. She's feeling somewhat better now, and three of my four sessions were covered by people who are even smarter than I am (thanks to Jim, Jüergen, and John!) so I feel better about my decision. I still hated to miss Connections, though, and I'm really looking forward to the Vegas version! My apologies to anyone who was disappointed by my absence. I hope it never happens again :)

TastesLikeRealFood.com

| 2 Comments

Arlene just found an ad for a new gluten-free product supplier: TastesLikeRealFood.com. They sell several kinds of imported flours and mixes from Norway. With a name like that, no doubt their stuff is good, so we ordered the sampler to try it out.

David managed to break his Nintendo DS Lite; he snapped off part of the headphone plug fairly deep inside the jack. I didn't want to tackle taking it apart, and I'd heard rumors on the intertubes that Nintendo offered drop-off service. Because Nintendo customer service center. It's conveniently located a few blocks away from Microsoft's campus, so I took the broken DS with me and drove over there yesterday afternoon. It took less than 10 minutes for me to walk in, show the busticated DS to the friendly guy behind the counter, and get a refurb unit with a fresh 1-year warranty. David is now back in business. This is the best customer service experience I've ever had at a store-- I wish Microsoft would take some lessons from this and apply them to the Xbox 360 service process.

I didn't post this yesterday because no one would have believed it (and I was skeptical myself). Here's a video of a Finnish rock group, the Leningrad Cowboys, singing "Sweet Home Alabama"-- accompanied by the Red Army Choir. Yes, that Red Army Choir. No word on whether the audience demanded an encore of "Free Bird".

Bernie Marcus, the co-founder of Home Depot, is opening his own checkbook to help cover the cost of treatment for veterans at Atlanta's Shepherd Spinal Center:

Marcus got involved in January after he heard of a soldier who was treated at the Shepherd Center and was improving, but faced the loss of funding. "It angered me," said Marcus, a co-founder of Home Depot and now a billionaire philanthropist. "It is disgraceful and it is not something that we should have to tolerate in this country."

I don't know about you, but I plan to go spend some money at Home Depot tomorrow.

Bernie Marcus, the co-founder of Home Depot, is opening his own checkbook to help cover the cost of treatment for veterans at Atlanta's Shepherd Spinal Center:

Marcus got involved in January after he heard of a soldier who was treated at the Shepherd Center and was improving, but faced the loss of funding. "It angered me," said Marcus, a co-founder of Home Depot and now a billionaire philanthropist. "It is disgraceful and it is not something that we should have to tolerate in this country."

I don't know about you, but I plan to go spend some money at Home Depot tomorrow.

Today's cheerful song: "Rise Up"

| No Comments

I've been hearing Yves Larock's "Rise Up" on XM, and I finally found it on iTunes. It's a very cheerful, reggae-infused song with a great bass line. The video, which features some awesome jumprope stunts (how often do you get to type that>) is on both YouTube and iTunes. DJ Paul says "check it out!"

Hysterical BIll Gates video

| No Comments

Here's what Bill Gates' last day at Microsoft will be like.

This is a great song; I found it more or less by accident.

You might have been wondering how Marines can re-integrate to civilian life. A friend just sent me this handy guide (which I have edited somewhat to make it more family-friendly).

  1. ADMIT you have a problem. Say "I am a Marine, I have a problem."
  2. SPEECH
    • Time should never begin with a zero or end in a hundred. It is not 0530 or 1400; it is 5:30 in the morning (AKA awful early)
    • Words like deck, rack, and "PT" will get you weird looks; floor, bed, work out will work better-- get used to it
    • "F---" cannot be used to replace whatever word you can't think of right now. Try "um" instead.
    • Grunting is not talking
    • It's a phone, not a radio. Conversations on a phone do not end in "out"
    • People will not know what you are talking about if you tell them you are coming from Camp Lejeune with the MWSS platoon or that you spent a deployment in the OCAC
  3. STYLE
    • Do not put creases in your jeans
    • Do not put creases on the front of your dress shirts
    • A hat indoors does not make you a bad person, it makes you like the rest of the world
    • You do not have to wear a belt all the time
  4. WOMEN
    • Being divorced twice by the time you are 23 is not normal, neither are 6 month marriages, even if it is your first
    • Marrying a girl so that you can move out of the barracks does not make "financial sense", it makes you 'SPECIAL"
  5. PERSONAL ACCOMPLISHMENTS
    • In the real world, being able to do pushups will not make you good at your job
    • How much pain you can take is not a personal accomplishment.
  6. ALCOHOL
    • In the real world, being drunk before 5pm will get you an intervention, not a "good for you"
    • That time you drank a 5th of Jaeger and accidentally relieved yourself in your closet is not a conversation starter
    • That time you went to the combat medic school and practiced giving vodka IV's will also not be a good conversation starter
  7. SPENDING HABITS
    • One day, you will have to pay bills
    • Buying a $30,000 car on a $16,000 a year salary is a really bad idea
    • Spending money on video games instead of on diapers makes you a fool
    • One day you will need health insurance
  8. INTERACTING WITH CIVILIANS (AKA YOU):
    • Making fun of your neighbor to his face for being fat will not be normal
  9. REAL JOBS
    • They really can fire you
    • On the flip side you really can quit
    • Screaming at the people that work for you will not be normal. Remember, they really can quit too
    • Taking naps at work will not be acceptable
    • Remember 9-5, not 0530 to 1800
  10. THE LAW
    • Non-judicial punishment does not exist and will not save you from prison
    • Your workplace, unlike your command, can't save you and probably won't. In fact, most likely you will be fired about 5 minutes after they find out you've been arrested.
    • Even McDonalds does background checks
    • Fighting is not a normal thing and will get you really arrested, not yelled at Monday morning before they ask you if you won

  11. GENERAL KNOWLEDGE


    • You can in fact really say what you think about the President in public

    • Pain is not weakness leaving the body, it's just pain

    • They won't wear anything shiny that tells you they are more important then
      you are, so be polite

    • Read the contracts before you sign them. Remember what happened the first time


I was delighted to get a Zibra OpenIt for Christmas, all the more so because I'd never heard of it before. The OpenIt is basically a pair of shears where the blades are perpendicular to the handle. It works a treat for opening those stupid blister packs, plus it has a built-in utility knife for cutting other kinds of packaging. I used it heavily for our family Christmas presents, and as a result we suffered no incidences of wrap rage. Highly recommended. I've already ordered one for our office.

The history of Tabasco

| No Comments

Wow, this is neat-- NewsGator just alerted me to a book review of a book called McIlhenny's Gold: How a Louisiana Family Built the Tabasco Empire. This sounds like my cup of tea. Or something.

Courtesy of my Marine mailing list, here's a video of this year's Marine Corps birthday message from Gen James Conway, Commandant of the Marine Corps.

Courtesy of my Marine mailing list, here's a video of this year's Marine Corps birthday message from Gen James Conway, Commandant of the Marine Corps.

Lots of short updates

| No Comments

I have a long list of stuff to blog about, but I'm far behind. Expect a stream of short (and possibly pithy) posts over the next few days as I get ready for my trips to Vegas and Barcelona. I've got book reviews, trip reports, and more!

David's watching TV to help him recover from his appendectomy, and I was passing the TV I noticed that he was watching an "Ant and Aardvark" cartoon on Boomerang. Our whole family loves these, so I did a quick search when I got back upstairs and was delighted to find that Warner has issued a DVD of all 17 original Ant and Aardvark shorts: volume 5 of the Pink Panther collection. Yowza! I know what somebody's getting for Christmas!

OttawaFlood.com

| No Comments

Steve Teffenhardt has started a comprehensive new site, www.ottawaflood.com, centering on flood relief efforts for the people affected by this summer's flooding in Hancock and Putnam Counties. Check it out.

Troop 270 flood relief

| No Comments

This was great to see: John Cargill sent me a note about his Scout troop's trip down to Ottawa for flood cleanup.

Thank you for your assistance in locating a relief agency that my Scouts and I could work with.

We traveled with 13 scouts and 7 adult volunteers. Scout Camp Berry hosted us at no cost for tent camping - and with thanks for our purpose in traveling to Ohio.

The agency you directed us to was very efficient and registered us quickly. They listened (some don't) to our level of preparation and tried their best to assign us to matching tasks. We responded to one home where the owner had approximately 3 feet of ware in her basement and questioned whether there was mold behind the paneled walls. We carefully removed one sheet - found no mold, but some moisture, and recommended that the base molding be removed for better drying.

She agreed as she really didn't want to strip off all of the walls unless there was a clear need. Her family had already spray bleached the external paneling so we
proceeded to Murphy oil soap the whole basement. Some furniture washing and yard work finished us up on that site.

We returned for additional assignment and responded to the need for re-insulating a shop garage and yard raking and cleanup of wet plaster scraps. While this particular home looked okay from the outside, we were aware that they had had to pull up all of the floors and part of the wet plaster walls - so despite our not being involved in demolition or internal reconstruction we were able to help with some work that they did not have time to get done.

All-in-all a good trip. Several scouts and parents said that they really enjoyed the recovery work and would be interested in future trips of the same kind.

Walk to Cure Diabetes

| No Comments

The Juvenile Diabetes Research Foundation is dedicated to finding the cause of, and cures for, type-1 diabetes-- the insulin-dependent kind. Using insulin doesn't cure diabetes, it just postpones the inevitable slow degeneration of major organs that eventually leads to death. That's no good.

Our martial arts school is sponsoring a team, the Black Belt Brigade. As part of that team, our family has signed up to raise $500. That's a lot, on one hand, but on the other, it's a very small fraction of the $90 million that JDRF hopes to raise this year.

If you're reading this, please consider donating online. $2, $5, $10, or more will definitely help. You can donate, or just check our family's status, here. (and if not, that's OK too... but Dad's ghost may come haunt you. No, wait, that was just a joke.... maybe!)

Flood of Hope

| No Comments

Last night, 13 ABC here in Toledo did a short piece on "Flood of Hope", my effort to "surge" volunteers down to Ottawa to help with flood relief. I haven't had time to set up a formal website, so here are the details-- hopefully people searching for "flood of hope" will find this article.

The Ottawa / Blanchard River Valley area has been badly afflicted by the recent flooding. More than 500 homes are uninhabitable, and the Red Cross estimates it will take several months of cleanup work to get the area back in shape. If you haven’t been there, you might not appreciate the scope of the destruction— it’s worse than you might imagine,.

I am coordinating “Flood of Hope”, an effort to surge volunteers from the metro Toledo area down to Ottawa on September 6th. The goal is to get teams from Toledo-area employers to go down and help with restoration and cleanup work.

Here’s how you can help:

  1. If you’re a business owner or manager, please consider giving your employees a paid day off or vacation day to participate. (A big shout out to Ritter and Associates, the first company to volunteer to do this!) The cost may even be deductible as a charitable contribution (but maybe not; only your accountant knows for sure.)
  2. If you’re not a business owner, consider taking a vacation day to come help anyway, even if it’s not on September 6th. The cleanup efforts will continue for some time to come, and they need help every day, including weekends.
  3. Spread the word. Tell your friends, neighbors, church members, and co-workers. We need all the help we can get.

The recovery efforts can use special skills if you have them—they need construction expertise, data entry and office skills, and good old-fashioned demolition and cleanup too. Whatever you can do will be appreciated.

If you want to join the Flood of Hope, please email me or call me at 419 873 8308 and I’ll get you signed up. It’s important that you call ASAP so I can keep the volunteer staffing coordinators apprised of how many people to expect. If you can’t reach me, call the volunteer center at 419 523 3288 and tell them you want to work on September 6th.

Flood cleanup, part 1

| No Comments

Yesterday I headed down to Findlay to help with cleanup. I didn't realize the extent of the flooding until I got down there, mostly because I haven't been watching the local news.

Matt and I first went to the LDS chapel in Findlay. The church has been designated the lead for all the church-based service groups participating in the cleanup; we drew cleaning supplies and a map to Ottawa, about 25mi W of Findlay. As we got about 10mi from Ottawa, the flood damage in the fields became readily apparent-- miles of dead corn stalks, ruined tomatoes, and high-water marks on trees and greenery. When we got into town, it was even worse: the streets are lined with piles of debris. Many businesses are still closed, and many of the people whose homes were damaged have few local alternatives for housing-- as a small town, Ottawa doesn't have any hotels and little spare rental housing.

At the Ottawa center, we signed in and quickly got a work assignment. Matt and I teamed up with four missionaries (the Ohio Cleveland Mission has assigned 50 missionaries to the cleanup efforts) and headed out. We spent the day tearing out the interior of a two-story house. Wallboard, lath, and insulation all had to go; the homeowner had already taken out the carpet, but the trim and tack strips had to be removed too. It was hot (94° outside), messy work, but we could definitely measure our progress. It was rewarding work.

I'm going back down on Thursday with a few other folks, and I'm trying to coordinate a broader business-based effort for sometime next week. Drop me an e-mail if you're interested in taking part.

The value of LinkedIn

| No Comments

David Pogue asks a good question:

…could somebody tell me the point of LinkedIn? … What I don’t understand is: If somebody knows me well enough to e-mail me with an invitation to join, why doesn’t he just e-mail me directly with whatever his problem or offer is?

Easy. LinkedIn has very little value for someone like you, David, because you're already super-connected. For virtually any problem you have, you can easily find a resolution because you're David Pogue. You have access to a huge audience, hundreds (if not thousands) of contacts from all walks of life, and the accumulated knowledge of the entire NYT staff (or, at least, those you get along with well enough to ask for favors).

For those of us not similarly blessed, LinkedIn is valuable because it provides a tool for finding contacts or expertise in areas where we're not necessarily connected. For example, say I want to know about a particular market segment in depth, or I want to ask an alumnus what he thought of a given MBA program, or I want to find someone who works for Company X. LinkedIn makes it easy. I've used it to find contacts at famously opaque companies like Apple, as well as contacts at companies I didn't even know existed. I occasionally get linkage requests from people I don't know, and I don't feel obligated to accept them, but usually I do. Why? For the same reason I accept business cards when I meet people at face-to-face events: a) it's polite and b) that person may turn out to be a very useful contact.

So, David, feel free to send me a link request now that you have your answer. Heck, you can even write a recommendation if you like.

Yes, it's true: up to 60% of shopping carts have coliform bacteria. Yikes! I think I'll be bagging my fresh fruits from now on, thankyouverymuch. And wearing a biohazard suit, too.

Happy Monday!

| No Comments

Want to get your week off to a great start? Try an 0830 appointment with your doctor, then top it off with a 1000 visit to the dentist. After that, the rest of the week is guaranteed to be a breeze!

The headline says it all. Semper Fi.

Finally. The FDA is getting more aggressive about regulating companies that harvest useful tissue from cadavers. I still recommend reading Body Brokers if you want to know more about the industry (provided you have a strong stomach!)

Wow, this is a fascinating video clip of a guy whose job it is to fix high-tension power lines. Not for the faint of heart! (It's from Straight Up: Helicopters in Action, which I may now have to order!)

This video shows home prices, adjusted for inflation, since 1890-- as a roller-coaster ride.

This just in from my pal Kevin Engman:

The Unified Communication Marketing team will be conducting six focus groups at Tech Ed, Orlando in June 2007 focusing on Unified Messaging and the IP telephony space. We are conducting focus groups to gain clarity concerning the roles and responsibilities in an IP telephony environment, given Exchange Server 2007 Unified Messaging and the public release of Beta 3 Office Communications Server (OCS) 2007. We would like to talk to IT administrators and IT managers currently working in an enterprise environment, which is defined as an organization with 100+ servers and 500+ PCs. They may work as full time employees or as contracted vendors. We are looking for a group of IT administrators and IT managers who have experience with Microsoft products such as Exchange Unified Messaging, Office Communications Server 2007, Office Live meeting, Live Communications Server, etc. We are also interested in IT administrators and IT managers who have experience in an IP telephony environment and not strictly a TDM/legacy telephony environment, with expertise in IP telephony equipment from vendors such as Cisco, Avaya, and Nortel.

The sessions will be held at the Peabody Hotel in Bayhill II. The session times are as follows:

• Session 1: June 4th, 1:00pm-3:00pm – For IT administrators and IT managers who manage Microsoft LCS or Microsoft OCS pilots.
• Session 2: June 4th, 3:00pm-5:00pm – For IT administrators and IT managers who manage Microsoft LCS or Microsoft OCS pilots
• Session 3: June 5th, 3:00pm-5:00pm – For IT administrators and IT managers who manage Exchange Unified Messaging or Cisco Unified Messaging solutions
• Session 4: June 6th, 12:00pm-2:00pm – For IT administrators and IT managers who manage Exchange Unified Messaging or Cisco Unified Messaging solutions
• Session 5: June 7th, 1:30pm-3:30pm – For IT administrators and IT managers who manage Cisco, Avaya, Nortel or any other VOIP solution.
• Session 6: June 7th, 3:30pm-5:30pm – For IT administrators and IT managers who manage Cisco, Avaya, Nortel or any other VOIP solution.

If you're interested, drop ucgfg@microsoft.com a line and let them know.

Technorati Tags: ,

I'm at the MVP Summit this week, and Computerworld's Eric Lai has written a background piece on the MVP program that's pretty interesting (and no, I'm not saying that just because he quoted me!) For example, I didn't know that the original set of MVPs were mostly FoxPro developers. Check it out here.

Happy New Year!

| No Comments

Back to the grind after a wonderful holiday break. OK, I admit it; it wasn't a break from work, except for the few days I took off around Christmas. However, it was a big change in our routine since David didn't have to get up at zero-dark-thirty to catch the junior high bus, and that made a big difference.

Santa (or, more properly, the section 179 fairy) brought me a couple of new gadgets that I'll be writing about. Stay tuned.

A Soldier's Christmas

| No Comments

Original poem by Michael Marks:


The embers glowed softly, and in their dim light,
I gazed round the room and I cherished the sight.
My wife was asleep, her head on my chest,
my daughter beside me, angelic in rest.

Outside the snow fell, a blanket of white,
Transforming the yard to a winter delight.
The sparkling lights in the tree, I believe,
Completed the magic that was Christmas Eve.

My eyelids were heavy, my breathing was deep,
Secure and surrounded by love I would sleep
in perfect contentment, or so it would seem.
So I slumbered, perhaps I started to dream.

The sound wasn't loud, and it wasn't too near,
But I opened my eye when it tickled my ear.
Perhaps just a cough, I didn't quite know,
Then the sure sound of footsteps outside in the snow.

My soul gave a tremble, I struggled to hear,
and I crept to the door just to see who was near.
Standing out in the cold and the dark of the night,
A lone figure stood, his face weary and tight.

A soldier, I puzzled, some twenty years old
Perhaps a Marine, huddled here in the cold.
Alone in the dark, he looked up and smiled,
Standing watch over me, and my wife and my child.

"What are you doing?" I asked without fear
"Come in this moment, it's freezing out here!
Put down your pack, brush the snow from your sleeve,
You should be at home on a cold Christmas Eve!"

For barely a moment I saw his eyes shift,
away from the cold and the snow blown in drifts,
to the window that danced with a warm fire's light
then he sighed and he said "It's really all right,
I'm out here by choice. I'm here every night"

"Its my duty to stand at the front of the line,
that separates you from the darkest of times.
No one had to ask or beg or implore me,
I'm proud to stand here like my fathers before me.

My Gramps died at 'Pearl on a day in December,"
then he sighed, "That's a Christmas 'Gram always remembers."
My dad stood his watch in the jungles of 'Nam
And now it is my turn and so, here I am.

I've not seen my own son in more than a while,
But my wife sends me pictures, he's sure got her smile.
Then he bent and he carefully pulled from his bag,
The red white and blue... an American flag.

"I can live through the cold and the being alone,
Away from my family, my house and my home,
I can stand at my post through the rain and the sleet,
I can sleep in a foxhole with little to eat,
I can carry the weight of killing another
or lay down my life with my sisters and brothers
who stand at the front against any and all,
to insure for all time that this flag will not fall."

"So go back inside," he said, "harbor no fright
Your family is waiting and I'll be all right."
"But isn't there something I can do, at the least,
"Give you money," I asked, "or prepare you a feast?
It seems all too little for all that you've done,
For being away from your wife and your son."

Then his eye welled a tear that held no regret,
"Just tell us you love us, and never forget
To fight for our rights back at home while we're gone.
To stand your own watch, no matter how long.

For when we come home, either standing or dead,
to know you remember we fought and we bled
is payment enough, and with that we will trust.
That we mattered to you as you mattered to us."


Way behind on blogging

| No Comments

When I get super busy, the first thing to go is the Xbox 360; the second is this blog. That explains my relative silence. I'm trying to finish up a large project at work before the end of the year; last week I was in Seattle and Toronto, plus we had a major power outage in Redmond that slowed my progress down considerably.

Plus, let's not forget, it's the Christmas season! That means lots of evening time spent wrapping, shopping, going to chorus concerts, and so on. I have a couple of book reviews to post, but I probably won't get to them for a few days. In the meantime, Merry Christmas to all!

Time to pay up!

| No Comments

Last year, I made a bet with some folks over at Ed's blog:

@5: I'll take that bet, Bill. I've got $20 that says MS will only ship 64-bit production versions of E12 (although they will probably ship test / demo versions that run on 32-bit hardware). If I'm right, you pay Habitat for Humanity in New Orleans $20; if you're right, I'll pay the $20 to a charity of your choice. In fact, I'll take up to 5 identical bets. Ante up!

Today Microsoft released Exchange 2007 to manufacturing, which I'd say counts as "shipping" it. As I predicted last year, they're only shipping 64-bit versions; there will be a limited-use 32-bit version that is not licensed for use in production, but MS hasn't announced how or when they'll make it available. By my lights, that means that Ed, Mike Lazar, and Bill Buchan each owe the New Orleans chapter of Habitat for Humanity $20.

The folks over at ITSecurity.com just published a wonderful article, "Hacking EMail: 99 Email Security and Productivity Tips". None of these tips will be surprising to power users (don't forward chain mails; respond promptly; remember, e-mail's not private). However, it's refreshing to see them collected in one place, and I hope the list makes the rounds of corporate America, where hopefully it will start to sink in. (Hat tip: Rich).

Wow, so much to write about and so little time to do it in! I'll be blogging less than usual for the next week or so. This is mostly due to the fact that I have a large project due by month's end that I don't want to slip, combined with the happy news that my new upstairs office is ready for me to move in. First, though, my existing office needs a good Thompson Deep Clean, which will take time in itself. Not to mention that my birthday gifts included both Viva Piñata and Gears of War, both of which could suck up a huge amount of free time. Then there are the basement ceiling panels I have to put up once I move out... and the Ohio State-Michigan game on Saturday... and so on. Thus, don't look for a huge volume of posts here for the next little while.

A little housekeeping

| No Comments

I've made some long-overdue changes to the blog layout and categorization. You may or may not have noticed, but:

  • the categories are now streamlined to better reflect what's actually in them
  • the Google ads from the right sidebar are now gone, since they were basically just an annoyance
  • the RSS syndication info in the "about" block of the right sidebar now works
  • the monthly archives are gone, replaced by a list of category archives

I still have a number of other things to tweak, but this is a good start.

Hardware failures galore

| No Comments

It's been a tough two or three weeks here, at least for computer hardware.

First, I flattened my trusty ThinkPad. Ryan Femling, my coworker, says you can easily go two or more years without performance problems on a stable Windows install. He's right; I got just over three years out of the install, but for some reason, the machine had decided that it would permanently disable both its wireless card and its onboard Ethernet port. That made it, if not useless, much less useful. There wasn't anything wrong with the hardware; some combination of Windows patches and software installs/removals apparently whacked the driver. A clean install using IBM's recovery partition certainly fixed things up.

The next weekend, I came back from Michigan to find my only x64 machine (an Athlon 3800+ in an ASUS A8N) was beeping every two or three seconds. All the fans spin up normally, but the machine just sits there and won't POST. I haven't started diagnosing it yet.

Two nights ago, our electrician was here doing some work. He had to take down house power, so I cleanly shut down all my servers. When the power came back on, my primary file server wouldn't boot. After a little troubleshooting, I found that the video card was at fault; after I removed, cleaned, and reseated it, I was back in business. Coincidentally, Windows maven Ed Bott had the same problem two weeks ago, and his post is what reminded me to check the video card first, so I'm passing the tip on.

And another thing, which I originally forgot: I lost a 16-port network switch early Wednesday morning. It was making a cool frying-bacon sound when I came downstairs; this is annoying since it's the link to the ground floor of the house. Until I replace it, no Internet in Arlene's workroom.

Walter Glenn has a blog

| No Comments

Thanks to Technorati, I just found that Walter Glenn has a blog; with characteristic modesty, he hasn't been plugging it anywhere, so I found it through searching for links to my own blog! Walter and I first worked together on an MCSE guide for Exchange 5.5 back in 1998 or so. He's a great guy and knows a ton about Windows and Exchange. His blog is focused on simple tips for making Windows easier to use-- check it out.

Oh, bother.

I got a testy e-mail from Shane Keats of McAfee asking us to remove SiteAdvisor from the study, based on his claim that SiteAdvisor isn't an anti-phishing toolbar. I wrote a detailed response, in private e-mail, and was prepared to leave it at that.

However, Mr. Keats cried "foul" to InfoWorld and on the IE blog, saying that including SiteAdvisor is "silly and wrong. We don't claim, anywhere, to offer phishing protection. In fact, we're pretty explicit that we don't."

I'll admit to sometimes being silly, and I've certainly been wrong before, but I think in this case it's fair to include SiteAdvisor. Here's why:

  • The SiteAdvisor.com home page contains this text: “McAfee SiteAdvisor also complements and enhances your existing security software by detecting threats which traditional security products often miss, including spyware attacks, online scams, and sites that spam you”. I think a reasonable person would likely interpret the reference to “online scams” as including phish.
  • Question 2 of the SiteAdvisor FAQ page says “SiteAdvisor is a consumer software company dedicated to protecting Internet users from all kinds of Web-based security threats and annoyances including spyware, adware, unwanted software, spam, phishing, pop-ups, online fraud, and identity theft.” This definitely seems to represent SiteAdvisor as an anti-phishing tool.
  • Mr. Keats included a partial quote from this support article: "SiteAdvisor's software does not currently provide automated or real-time phishing detection". However, the full text of this article explicitly says that user reports of phish sites are reported by SiteAdvisor. In our report, we didn’t distinguish between tools that use automated reporting and those, like SiteAdvisor, that can incorporate user-generated reports.
  • On August 3rd, I spoke via phone with both Craig Kenwec of McAfee and Scott Van Sickle of Global Fluency, a PR agency that handles client-security PR for McAfee. Both of them told me that SiteAdvisor incorporates anti-phishing functionality.

Technorati Tags: ,

Arlene and I got our free iPod nano units from KeyBank's promotion today. I was expecting a 1GB unit because that's what the ad promised. Instead, though, they shipped me one of the brand new (as in, introduced two weeks ago) aluminum 2GB models. I'm delighted! That's way nicer than I expected. Now, if I can just get Key to send me that debit card I asked for...

Fantastic Xbox 360 news

| No Comments

At the Tokyo Game Show, Microsoft made a couple of huge announcements about the Xbox 360. First, they announced some new games for the Japanese market, where the Xbox family has traditionally been pretty weak. They announced some excellent new Xbox Live Arcade titles, too, including Gyruss, Rally-X, and Track & Field. Konami and NAMCO BANDAI have really jumped on the potential of XBLA; Konami alone had three or four titles released just within the last couple of months.

On Friday, I posted that I was starting to experiment with Naturally Speaking. The results are in: here's my first post written using NS.

I just bought Dragon Naturally Speaking and was eager to try it, then I had second thoughts: what if it doesn't work well with Office 2007? I installed it anyway. Unfortunately, despite what Marc says, in my initial tests performance was quite poor. This may be because I was running it in Parallels on my MacBook Pro. However, other people seem to be pleased with its performance in Parallels. I'm going to try it on the Thinkpad tonight and see if it's any better. If not, back to Amazon it goes.

Setting up for Direct Push

| No Comments

Reader mail from Mike in Canada:


I’ve read your articles for years and they’ve always provided me with invaluable timely information. I have a quick question about the “Messaging and Security Feature Pack for Windows Mobile 5”. This seems to be a hard feature pack to find good information about. Microsoft doesn’t seem to have a download for it so I assume it must come with a Windows Mobile 5 Device that has a version after 148xx.2.x.x. My organization is about to get the latest Motorola Q’s from Bell Mobility in Canada. Apparently the Q’s that Bell have support the messaging and security feature pack for Windows Mobile 5 but I don’t really have any good information on it. This article is supposed to step me through the process of getting Windows Mobile devices working with Exchange SP2. Step 7 in this article tells me to install the Exchange ActiveSync Mobile Administration Web tool but I’ve never seen that tool (I’m guessing it comes with the feature pack).

I have an ISA 2004 server and I already have active sync working for older Windows Mobile devices but I’m very interested in the new live sync “direct push” technology so I’m trying to get as educated as I can before my new devices arrive from my provider. I don’t even know if the new “direct push” requires me to change my publishing policy in ISA Server as I can’t find information on that topic either (I used the wizard in ISA server to publish Exchange active sync over SSL for my older devices). Can you direct me to some more information and let me know if the feature pack is downloadable?

TiVo alert: "Wench Swap"

| 2 Comments

Arrr! Avast, ye scurvy dogs! Make ready the TiVo! In honor of National Talk Like a Pirate Day (19 September!), I'm happy to report that ABC's "Wife Swap" is doing a special pirate-themed episode the day before. Normally I avoid reality TV like the black spot, but I'll make an exception in this case.

Varitalk demo

| 2 Comments

I was very tempted to make this my voicemail announcement. I'm guessing they're not going after the Republican market.

Man, this is a pretty good deal: open a new Key Bank checking account and get a free 1GB iPod Nano. You have to open a checking account, fund it with at least $50, and either sign up for direct deposit or get a Key credit card. Arlene and I have already signed up; it's too good a deal not to.

Dilana Robichaux is apparently a contestant on some kind of reality TV knockoff of American Idol. Good luck, cuz!

How cool is this? A fellow Marine, also named Robichaux, "borrowed" the picnic table where he and his girlfriend shared their first kiss. Why? To propose marriage, of course. The proposal was successful; no word on whether the po-lice will drop the hammer on him (he e-mailed the City of Irvine to let them know that he'd taken it and that he would be returning it).

Those Cajun Marines... you just can't keep 'em down!

Yay! Julie found a site that has some of ABC's old Saturday-morning videos featuring Timer, the little yellow guy who sang unforgettable songs like "I Hanker for a Hunk o' Cheese". I can't wait to show these to the kids!

Too busy to blog

| 1 Comment

I've got a ton of work to do, and that's been keeping me too busy to blog (even to say "hey, I'm too busy to blog!") I'm making travel plans to go to Lisbon, Oslo, and Johannesburg over the next few weeks for a new roadshow that Windows IT Pro is putting on in those cities, and I'm trying to wrap up several ongoing projects that all close out at the end of this month. I also have some great info on the Exchange 2007 Unified Messaging server role, and I'll be posting that as time allows over the next couple of months. (Plus, I had to write a cover story on Monad, er, PowerShell, and that took some time to boot!)

How to go broke in a hurry

SAP is announcing that it will expand its efforts to sell low-cost support for Oracle products. I wonder what they think their margins will be on this?

Verifying backups? I vote yes

Got a good question from one of the folks who attended Exchange Connections Europe in Nice. He wrote:

I am running a nightly full backup to disk of my exchange mailbox servers. This is then backed up further, to tape. I use NTBackup on Windows 2003. Do you know off-hand whether it is necessary to set verify on for these scheduled jobs? The current verification adds an additional 70 minutes, which id be happy to remove if it is overhead. Or does keeping the verification allow me greater comfort that the bkf files are good for recovery.

MDA vs Treo 650, round 2

In my earlier post, I compared some aspects of the new-to-me T-Mobile MDA with my familiar Verizon Treo 650.

First, about the customizations. I installed the AKU2 ROM (which includes the MSFP DirectPush bits), and I stil love it. Having wireless sync for all my calendar and contact data was extremely valuable when I was in France (although I'm not looking forward to getting the bill for data charges, which are something like $0.015/KB). I also installed a ton of software, including SPB PocketPlus, SPB Weather, and PocketInformant. I'm really impressed with SPB's products, and I like PocketInformant too although it's taken some getting used to. I've also installed a free app called Smartkeys that makes the right softkey double as an "OK" button-- highly recommended.

Second, the hardware. Battery life, even with WiFi and Bluetooth off, has generally been poor. I started yesterday with a fully charged battery; after a total of about 15 min of phone calls and a day worth of DirectPush, I was down to 20% (the first warning threshold) by about 6pm. I've gotten in the habit of turning on flight mode overnight, and that helps some, but not enough. The camera is decent, and I like having the three additional side buttons (I have one mapped to PocketInformant so I get one-button calendar access), plus the two softkeys, plus the red/green buttons, plus the dedicated mail and IE buttons.

The screen is excellent, and I like the ability to switch between portrait and landscape mode. Overall, though, the phone feels a bit slow. It's not entirely clear how much performance is affected by the homebrew AKU2 ROM I'm using; consensus seems to be that it's actually faster than the factory ROM, but I don't have any basis for comparison.

Windows Mobile 5.0 has been quite stable. Occasionally when I press the "mail" button, Pocket Outlook launches and updates the softkeys but doesn't display the message list. This is a little bothersome, but closing Outlook and IE generally fixes it. (Speaking of Outlook: I complained that there was no way to move between messages, but that was just me not knowing to use the 5-way navigator by moving left/right).

There are still some things I miss from Palm OS. For one thing, Palm OS has the concept of numeric fields, so when you go to enter something like a phone number, the keypad automatically goes into numeric mode. Applications can leverage this, so entering things like flight numbers or birthdays is easy. As far as I can tell, there's no equivalent concept in WM. The Palm text entry engine does a better job of correcting some kinds of shorthand entries (e.g. "dont" turns automatically into "don't"); although WM will suggest words, I haven't figured out how to edit the list of suggestions or turn the feature off.

How is the MDA as a phone? Decent. T-Mobile's network coverage isn't as good as Verizon's in the areas I've tested (around Toledo and at CVG and JFK). The phone worked fairly well on the Orange and Bouygtel networks in France, although incoming calls didn't always make the phone ring on my end. Sound quality isn't as good on the Treo 650, and the speaker volume for ringtones and alerts isn't loud enough. (Part of the problem is that Voice Command adds an audio announcement, which it mixes over the ringtone audio, reducing its volume further). When the phone's in its holster on my belt, it's very difficult to hear it ring if there's any kind of environmental noise.

EDGE data speeds are acceptable; by comparison, all I have here in Toledo is Verizon's 1xRTT, which feels about the same.

Overall, I like the form factor of the device quite a bit, but I'm not satisfied enough with T-Mobile's network to switch.

Next up: evaluating the Verizon Treo 700w that I got in yesterday. So far, after a little fiddling with it, I like it a lot.

Update: PhoneScoop just posted their review of the MDA. Their conclusion: it's great if you're using Exchange, but only mediocre otherwise.

Treo 700w: my first week

Today marks the end of my first week carrying the Verizon Treo 700w as my primary phone. I haven't traveled with it much, which means it hasn't been subjected to the true acid tests that I usually use to judge a smartphone's worth. However, the Treo has been remarkably stable, and it remains considerably faster than the MDA I last tested.

Audio and call quality have been excellent. The Treo line has always had a very good speed-dial implementation, and that's also true of the 700w; it's simple to peck in a few letters of the name you want to call (well, as long as it's not a company name!) and dial it. Palm has obviously spent a good bit of effort on small touches, too; for example, if you turn on the device PIN lock, you can enter your PIN using the number keys on the keyboard without having to first touch the Option key. Palm also includes a Today plug-in for Google searches, which is handy.

When I was in Detroit this weekend, I got to use the 700w on an EvDO network. Subjective performance was excellent. I didn't do any speed tests, but I did tell Outlook to pull down several large attachments that people had sent me and was pleased with the sync performance. Overall, I think it's fair to expect EvDO speeds to beat EDGE speeds consistently, by a factor of 4-5x in some cases.

I used the camera to shoot some pictures and video over the weekend. Not bad, but not super-impressive. I shot two short 30-sec clips at a concert this weekend; at the end of each clip, the phone gave me the spinning Windows busy cursor for a very long time, and now I can't find the videos. I haven't taken the time to re-test in a better-lit, less distracting environment.

Of course, the 700w isn't without its flaws. It refuses to recognize the same 2GB mini-SD card that the MDA happily used. I suspect it's because of the card's size, not because it's a mini-SD card in an SD adapter. The card doesn't work in my Treo 650 either. The MDA has a few advantages, too. I really like the Communications Manager software that HTC includes; because it's mapped to a button, it's easy to quickly turn Bluetooth, wi-fi, EAS, and/or the phone on or off. The MDA has two additional buttons on the right side that can be mapped to different applications; the Treo simulates this by letting you bind app launches to the four primary buttons, plus a different set of bindings when the Option key is held down. This is a little awkward; I think I'd rather have the extra buttons along the device edge. The built-in wi-fi is useful, too, although I'm not sure the tradeoff in battery life is worth it for my typical usage patterns.

Overall, though, I'm very pleased with the 700w; it's a strong contender for the not-exactly-coveted title of "most likely to be hanging on Paul's right hip".

Update: I just saw that Verizon said they're going to allow EvDO phone owners to tether their phones as modems. This is a pretty good deal, since it would let me drop my existing aircard subscription and move over to using a tethered phone.

Wow, looks like RIM is starting to feel the love from Exchange ActiveSync. They're now offering a "free" Express version of BES; it supports up to 15 users, and the first user license doesn't cost anything. In total, BES Express supports up to 15 users, with users 2-15 costing you US$99 each. So, a fully loaded 15-user server costs you $1405, compared with $1099 for the "Small Business Edition" of BES (which then requires CALs @ $99). This is not quite "free", especially since you're still paying the RIM device tax. Having said that, it's an interesting move by RIM to capture a market segment that has historically balked at paying the Big Bucks for the full-blown version of BES.

Treo 700w first look

Yesterday was my first full day toting around a Verizion Treo 700w as my primary phone. A few quick thoughts:

  • The screen is only 240 x 240. I don't know why Palm did this, given that the Treo 650 is 320 x 320. I really miss the extra 80 pixels from the MDA (240 x 320), particularly with PocketInformant.
  • Verizon's network quality is waaaay better than T-Mobile's, at least in my area.
  • The device I got from Verizon didn't include the MSFP update. However, after I downloaded it, Palm's packaged installer made it very easy to update the phone. Oddly, I was expecting to see the Starfield intermediate CA certificate after the installation, but I had to manually install it before DirectPush would work.
  • Battery life seems to be slightly better than the MDA; from a full charge, overnight the device ran down to about 50%.
  • I much prefer the 700w's full-length stylus to the little bitty collapsible pen that comes with the MDA.

Expect a more detailed review next week, once I get some more time logged with the 700w.

Breathless press release (titled "Spammers Use Bullying and Extortion to Intimidate Members of the Blue Community to Give up Fight Against Spam") from Blue Security, complaining that "spam terrorists" are attacking their users by-- you guessed it-- sending spam. The difference is that the spammers are threatening to send even more spam to BlueFrog users unless they opt out. I don't know that I agree that it's bullying or extortion, but I am certain that it's not surprising.

The US Senate committe on homeland security and governmental affairs released its report on its investigation of the US government response to Hurricane Katrina. This should be required reading for anyone involved in messaging or collaboration systems planning. It's not very pleasant, but it does set out, quite clearly, where they think the problems lay.

Called out for special positive mention: the US Coast Guard. As a Marine, I am honor bound to make fun of the other armed services whenever possible. However, I'll suspend that rule in the case of the Coast Guard.

What a great show! The sessions went well, the attendees enjoyed the sessions, and Nice is a fantastic place to visit. The big news was that PowerShell is now upon us, and that Exchange 12 is now officially named "Exchange Server 2007" (big surprise there; can't believe that was actually under NDA).

Monad script repository

There don't seem to be any general repositories of Monad scripts for Exchange yet, so I've added a new "Monad" category to the Exchange Cookbook web site and will be posting Exchange-ish Monad stuff there. If you're interested in Monad, you might want to grab the Cookbook RSS feed.

Educause and the National Cyber Security Alliance just posted the winning videos in its Computer Security Awareness Video Contest. Some of them are pretty funny (here's my current favorite), and all of them are generally appropriate for most non-technical audiences.

Conventional presence (is Paul online? is Missy on the phone?) is useful. Extended presence (when is Peter free to talk? what does Devin's OOF message say?) is even better. Microsoft has done a great job of delivering both of these capabilities in Outlook, Communicator, and the SharePoint twins. However, I want to kick it up a notch: I want to see Plazes-like

geo-presence information. Imagine being able to see a web part in your SharePoint team site that shows the (self-reported, opt-out) location of each of your team members. For my team, it's small enough so that this would be more a curiosity than anything else, but for larger teams it would be terrific.

I already do something like this, updating my IM status message to say things like "DTW enroute SEA" or "Exch Conn - Orlando" so that people will know not only what I'm doing but where I am. It would be great to make this more automatic, though. You could probably do this easily enough by making Plazes queries for your team then plotting them on Virtual Earth or Google Maps.

Newsgator outage explained

I posted about NewsGator's outage on my personal blog, and got a comment pointing me toward the official explanation. If you're interested in messaging and collaboration HA, it's worth a read. The money quote:


Frankly, this was a pretty frustrating experience. We have a lot of redundant systems - pretty much any piece of hardware in our data center could fail, and we can absorb it without a significant outage. For example, if an entire SQL box would have lost power, fallen on the floor, and broken into pieces, no problem, we'd have an approximately 10 second outage. But this case, where the database gets into an inconsistent state, wasn't helped by the redundant systems.

MDA vs Treo

Some differences I've noticed in my first day of toting the MDA. I'll update this as I get more time under my belt with it.

  • With SnapperMail on the Treo, I can hit the "mail" button twice and get mail-- once to turn on the device if it's off, and once more to tell SnapperMail to pick up the mail. There's no equivalent on the MDA.
  • Speaking of mail: why, oh why, does Pocket Outlook not allow you to easily navigate from a message you're reading to the next or previous message in the message list? This drives me crazy. It's a simple feature that every other mobile mail client I've ever used has.
  • It drives me crazy that most apps don't recognize the center button in the 5-way nav pad as "OK". This makes one-handed navigation about 100x harder than it needs to be.
  • DirectPush is awesome. 5 minutes of setup and I was wirelessly getting my mail-- first via 802.11g here at the house, then via GPRS at the library. I called the chiropractor, made an appointment, put it into my calendar, and was delighted to see it in Outlook when I got home.
  • I created some test IMAP accounts and needed to get rid of them, then I couldn't figure out how to delete an email account. I found the answer, but it wasn't intuitive-- guess I'd better get used to tap-holding things to see what actions are available.
  • The built-in apps have some limitations, e.g. not being able to create a task from the Calendar app, that bug me after my long years with DateBk+ on the Palm.It looks like PocketInformant might be worth a try (as will FlexMail, the same company's Pocket Outlook replacement).
  • Microsoft Voice Command is super cool. I love being able to have it read me my calendar. I don't quite have it working with my Bluetooth headset yet, though.

What a cool idea! This guy wrote an Exchange event sink to take incoming attachments from Vonage's voice mail service and transcode them using a codec natively supported by Windows Media Player on both the desktop and on mobile devices. I wish I'd thought of that.

T-Mobile MDA on the way

| 2 Comments

I'm waiting for my new T-Mobile MDA to get here. In the meantime, I've gathered a few useful links:

Before the device gets here, I need a new cert for my Exchange FE (some WM5 devices don't like self-signed certs), and I have a few dozen things to download to prep the install :) In particular, my first step will probably be to put an MSFP ROM on the device so I can use DirectPush. That will be invaluable when I travel.

Update: just ordered a 2GB miniSD card for the MDA, which got here about 30 minutes ago. I'm backing up the ROMs right now preparatory to installing the MSFP AKU2 image.

Well, mine are, anyway. (For once, I got this done before Jim McBee... yay me!) The sessions:

  • EXC04, Cookbook Reloaded: Cool Exchange Scripting with Monad: a 200-level introduction to the new Monad shell and how you can use it with both Exchange 2003 and Exchange 12.
  • EXC10, Improving Your Message Security: an overview of what CIA really means and how to get better confidentiality and integrity for your Exchange environment. One slide on E12 security features.
  • EXC17, Using Continuous Backup: coverage of storage- and host-based continuous backup solutions for Exchange, including a discussion of local continuous replication (LCR) and clustered continuous replication (CCR) in Exchange 12.

Wow, busy day yesterday! I got up early, hit the hotel gym (man, I love those elliptical machines!), had a huge breakfast with Devin and Missy, and hit my room. I say "my room" because I was in it for three sessions back-to-back: one on continuous backup, one on Exchange security, and one on scripting with Monad. All three were well attended, and I got a ton of questions in each session. Some of the questions were pretty thought-provoking, too, which is always fun.

Atypically, I didn't spend much time on the exhibit floor; I went to Devin's Sender ID session (which I'll be delivering in Nice), and we had a short book signing at the show bookstore. (Thanks to those of you who came by!) I missed the MVP get-together because I had planned what I thought would be a short trip via water taxi to Epcot for a souvenir run. Turns out that the water taxi takes you to the Epcot entrance on the opposite side of the lagoon from the front gate, and there's no gift shop there. By the time I made it back from the hotel, I was too tired to do anything but order room service (which was excellent) and start working on the list of session submissions for the fall Exchange Connections show. If you've submitted proposals, I hope to let you hear something back by week's end.

A couple of observations: first, I was surprised that no one in any of my 3 sessions (close to 400 people in total) was running 5.5. That's a very good sign. There was a lot of interest in Monad, with tons of questions about what specific tools the Exchange team would be shipping in beta 2. Cemaphore and Mimosa have gained a lot of name recognition since the fall San Diego show. Finally, I didn't win the Harley Sportster that the show organizers gave away. Maybe next time...

Sweet! The conference organizers for Connection Europe just sent me email solving an issue I've been asking about-- they're offering a special discount to my readers. Come to Nice, learn from your favorite speakers (like me, for instance-- OK, OK, just kidding) live and in person, and hear directly from Microsoft experts about the next generation of Microsoft technologies, particularly Exchange 12. Although I'm most excited about the Exchange part of Connections, there are actually 4 conferences located together for one price: ASP.NET, Visual Studio, SQL Server and Exchange plus bonus sessions on SharePoint and Windows!

So, what's the deal? Register with code "PAULEX" and you get a buy-one, get-one-free deal: € 675 per person. This is a great deal, and I encourage you to take advantage if you're considering going but are balking at the price. If you've complained in the past about having to travel to North America for premier events, now is your chance to show concrete support for bringing the good stuff to your own backyard!

Spam Cube

Here's an interesting idea: a small, silent spam-filtering appliance for the home. The folks at SpamCube may be on to something here-- if, that is, their filtering works well. For $150 MSRP, it's probably worth a good look, especially if their filtering works. (Their site does some unfortunate handwaving about "AI", which always makes me suspicious!)

Discovery nightmares continue

Morgan Stanley is in the news again because one of its former employees (who coincidentally was central in the Perelman affair) is suing for wrongful termination. Messaging Pipeline says it best:

A saga of inappropriate, incompetent, and potentially illegal conduct continues to unfold at Morgan Stanley, with the company's own E-mail trail at the center of it all.

Man, I hate it when that happens. The plaintiff, Arthur Riel, claims that he was terminated after pointing out inappropriate emails, including requests by the CTO to fix things so no one except the CEO's direct reports could email him. The company claims that Riel misused his access as head of the company's archiving project to spy on others. I don't know who's right, but it's clear that a) this case will get uglier before it's resolved; b) there are probably other similar Lurking Horrors waiting in other companies' archiving and retention efforts; and c) if I were a corporate counsel I'd be boning up on messaging case law.

Migration bounty update

| 2 Comments

An update on yesterday's migration bounty story: IBM's press release clarifies some details: the bounty is $20/seat, with a max of $20K. It applies only to customers who move to Domino hosted on Linux, Domino Web Access on Linux desktops, or the Notes plugin for the Workplace Managed Client. Like I said yesterday, that's a tough sell, especially when you consider the management environment of Linux desktops vs Windows desktops.

IBM offers migration bounty

| 3 Comments

This is a hoot: after complaining bitterly that Microsoft was offering bounties to business partners to encourage them to get customers moved from Notes/Domino to the MS collaboration stack, IBM is now doing the same thing. This Washington Post article quotes Peter O'Kelly at length, pointing out that it's unusual for IBM to offer a bounty like this. I don't want to say or imply that it's a desperation move by IBM, but it's certainly unexpected, and it seems to be funded (at least in part) by IBM's Linux division. Selling Notes on Linux is harder than selling it on Windows, since partners will have to convince non-Linux shops to make the leap to an unfamiliar OS and to throw away much of their investment in Windows infrastructure-- an irony, given IBM's claim that Notes/Domino provides better investment protection than does MS' stack.

A modest proposal: in six months, both IBM and MS should publicly tell the world how much bounty money they've paid out. That's a good way to gauge the effectiveness of their respective programs.

Last week, I went to a press briefing to find out what had become of FrontBridge. The answer: a lot!

This press release sums it up nicely; the former FrontBridge services are now known as "Exchange Hosted Services" (EHS). Not a great name, since one of the first orders of business in the briefing was to clear up the difference between hosted Exchange services and EHS. That was easy enough, but imagine having to have that conversation over, and over, and over, and ... well, you get the idea.

There are four EHS components: archiving, filtering, continuity, and encryption. The EHS filtering service combines all of the previously unbundled FrontBridge offerings into a single whole. The other services are, to me, more interesting because they provide pay-as-you-go options for services that formerly would have been required to be self-hosted. For example, the encryption service provides a simple way to send encrypted mail to outside recipients who may not have the capability to receive encrypted mail: you send a mail, the service captures it and sends the recipient an SSL-protected link, and the recipient clicks the link to go to the mail. This is a simple and effective approach that, in the past, would have required a hefty investment in Tumbleweed's products. The continuity component is interesting, too, although I'd have to give the nod to MessageOne's EMS product because it supports calendar and contact data, has better synchronization options, and offers BlackBerry support.

My Exchange UPDATE column this week has more details (I'll link to it once it goes live); the bottom line, though, is that the FrontBridge acquisition is complete, the new EHS products are commercially available and competitively priced, and they offer some interesting capabilities. In fact, you could even use EHS to provide filtering and policy enforcement for non-Exchange systems like Domino and OCS (both of which lack any serious built-in capabilities).

The Anti-Phishing Working Group has posted their phishing trends report for January 2006. The group reports 9,715 unique phishing sites in the month of January, up almost 35% from December 2005. That's pretty scary. It's interesting to see what major collaboration and messaging vendors are doing to address the problem, too: IBM and Oracle are ignoring the problem, while Microsoft's already added anti-phishing features to Outlook 2003 SP2 and has shown both server- and client-based solutions for Office 2007 and Exchange 12.

Hz: email-based agents

From Chris Scharff, a pointer to Hz, a new service that works with mobile devices. You send mail to a special email address (like, say, hzFlightInfo@hz.com), and you get back a set of requested information. This is akin to the IM bots that let you do web searches or get product information, but it doesn't require a special client, and it doesn't require you to have data service on your device-- if you can get email, you can get Hz service. There are agents for geolocation services (where's the nearest ATM?), travel (is my flight delayed? when's the next flight from point A to point B?) and others. I'll be playing with this to see how well it works in practice.

New secure messaging e-book

My main homie Jim McBee has been working on a new e-book for RealTime Publishers: the Tips and Tricks Guide to Secure Messaging. It's available as a free download (registration required) from Microsoft.

Jim also has a new book coming out May 1 -- Microsoft Exchange Server 2003 Advanced Administration (see?) It's basically the second edition of Exchange Server 2003 24Seven, so it's probably going to be worth picking up.

Apple security czar

Arik Hesserdahl at BusinessWeek says that Apple needs a security czar. So does Microsoft's Stephen Toulouse. So, I sent Steve Jobs a letter touting my qualifications for the job. We'll see what happens.

Re-categorizing

I used to have separate categories for posts about Workplace and Oracle Collaboration Suite, but now that I'm starting to work with Zimbra and Scalix, I figured I'd lump all the non-Exchange material into a single category so that people who aren't interested will only have one category to skip. Thus, the new "Non-Exchange" category.

Devin, Missy, and I will be doing a book signing for the Exchange Server Cookbook at the Orlando Exchange Connections show next month. The signing's at 3:30p on 10 April; see O'Reilly's page for details. C'mon by and say hello!

This is super cool: Microsoft's started a series of Exchange podcasts (in both WMA and MP3, naturally!). This is a very smart move on the Exchange team's part, since it will unlock their webcast content and deliver it to a much broader audience. I was hoping to find the Exchange 12 preview webcasts from last week in podcast form; no word on whether that content will be added later.

BlueHat Briefings blog

Sweet! Microsoft has an annual security conference called BlueHat (see MikeHow's comments on the 2005 version), and this year they've started a blog to cover it. Sadly, the blog is a retrospective, since the conference was actually last week. Still, this should make for intersting reading.

Cool script from the Windows Mobile team blog; it creates a CertificateStore CAB file, containing the root certificate of your choice, directly from the command line.

Sage advice from Jesper: don't worry about clearing the page file (I love his list of things to be worried about). The setting to clear the page file at shutdown has always seemed like security theater to me, so I'm glad to see him point it out.

3sharp is hiring

We're hiring! First, I need a good Exchange administrator with strong writing skills. The position's in Seattle. Contact me directly if you're interested.

Second, we need some Office solution developers. Dave Gerhardt's got the full scoop at his blog. (Note that in your cover letter, we want details of a product demo you've actually worked on or built!)

Coming very soon: a week's worth of webcasts on Exchange 12. Harold Wong's blog has the details.

On March 1, Microsoft announced that it was making Exchange 12 beta 1 available to TechNet and MSDN subscribers as a community technology preview (CTP). When beta 1 first began, late last year, it was a private beta restricted to about 1400 Microsoft customers, all of whom had to be nominated by Microsoft employees. MVPs and a few third-party developers were also nominated, but—even including participants in the Technology Adoption Program (TAP)—only a relative handful of the tens of thousands of Exchange-using sites were in on the beta. That's about to change dramatically, since there are more than 200,000 TechNet and MSDN subscribers, all of whom will have access to beta 1.

This isn't the first time Microsoft's offered a CTP; you may remember that Exchange 2003 SP2 was released as a CTP in August 2005. As with the SP2 CTP, the Exchange 12 CTP is being released so customers can get familiar with it in their own environments. It's not supported for production use (obviously), and Microsoft has already told beta 1 customers that they won't be able to upgrade from beta 1 directly to the released version.

As part of the CTP announcement, the product team also announced that beta 2, coming later this year, will be a public beta, so we'll all be able to discuss it to our hearts' content. Until then, both reviewers (which technically means me) and CTP participants are bound by the relevant NDAs and EULAs.

One thing that's no longer under NDA: Microsoft's finally starting to talk publicly about the new continuous replication features in Exchange 12. There are two flavors of continuous replication: local continuous replication (LCR) copies transaction log data to a second local volume, essentially giving you a protected local copy of your data. Clustered continuous replication (CCR) is cooler; with CCR, cluster nodes don't have to share disk resources, meaning that geographically dispersed clusters get much, much easier to design and deploy. Look for more on LCR and CCR in future columns.

Interestingly, the CTP builds will be made available in both 32- and 64-bit versions. This is a smart move on Microsoft's part, because customers that haven't decided on their forward path from Exchange 2000 (or even Exchange 5.5) will be able to evaluate Exchange 12 features (if only in an early state) on the hardware they already have. I don't expect any changes in their previous commitment to release the production version of Exchange 12 as a 64-bit-only product, though.

MSDN subscribers can download the Exchange 12 CTP starting today, while TechNet subscribers will get the bits as part of their March delivery. If you're not already a subscriber to one of these two programs, you can subscribe through Microsoft's web site.

Microsoft today released the new version of their Application Analyzer tool for Lotus Domino applications. It features a new UI, better reporting, and a customizable XML-based system for customizing the analysis it does and the ensuing recommendations. This version of the tool uses the four-phase process that MS has defined and refined since the last App Analyzer release. There's also an accompanying best practices guide. I'm looking forward to seeing customer feedback on these tools; the previous versions of the app analyzer had some shortcomings that I hope the new version fully addresses. In particular, I'm interested in seeing Paul Mooney's take on it.

Two big MS announcements today

Microsoft is making two pretty interesting announcements today. Stay tuned for more details.

Update: now you know what the first one is.

Windows IT Pro is now accepting session proposals for the Fall 2006 Exchange Connections conference. We're heading to Las Vegas for the premier Exchange technical conference, and we'd like to hear from you! We expect the fall event to have a healthy dose of Exchange 12 content, plus our continued emphasis on real-world solutions for Exchange 5.5 and Exchange 2000/2003 administrators. This year, I'm co-chairing the show along with Kieran McCorry and Kevin Laahs, both of HP.

If you're interested in speaking at the show, send your abstracts to me by March 21. We want proposals for regular 75-minute sessions as well as 1/2 day and full day pre-conference and post-conference sessions. Note that we have a limited number of speaking slots, and all participants must be able to present a minimum of three 75-minute sessions.

  • Send a minimum of 3 session proposals (4 or 5 is ideal for discussion purposes)
  • Include a short bio with your session proposals; if you have prior speaking experience, please include it
  • Include any additional pre- or post-con session proposals, if applicable

Please adhere to the March 21 deadline as we need to make speaker and session selections right away.

Monad shell profiles

The Lazy Admin has a great piece on the use of MSH profiles with Monad. If you're exploring Monad, you should check it out, since profiles are the primary customization method for your interactive shell sessions.

SecurID support for Direct Push

Sweet! I just noticed this article on the Exchange team blog-- RSA's SecurID product can now be made to support Direct Push. This is a big win, because many organizations that want to deploy Direct Push also want strong 2-factor authentication.

Actually, I blogged about this on Monday morning, but my local copy of Ecto ate the post and just spit it back out this morning.

The lowdown on E12 public folders

Terry Myerson drops science on public folders in Exchange 12 over at the Exchange team blog. High points: public folders will be supported until at least 2016, new apps should use the .NET framework and Windows SharePoint Services v3, and with Outlook 2007 + Exchange 12, you don't need PFs for free/busy. (Interestingly, I don't think that last tidbit has been publicly disclosed before Terry's post).

I love Monad

| 2 Comments

Wow, I love Monad. That's all I have to say about that.

Office Communicator Mobile

Somehow I missed this, but MS last week announced the impending availability of a Windows Mobile version of Office Communicator. This may be the app that gets me to carry a Windows Mobile 5.0 device full-time, because having in-pocket access to presence, VoIP, and extended presence data for my contacts would be incredibly valuable. I'll post more once I get the bits.

Getting serious about Monad

I'm working on my Exchange Connections presentation on Monad. There's already a good bit of information out there (including the official Monad team blog), but I'm interested in knowing what you want to know about Monad and Exchange. Leave feedback in the comments, and whenever possible I'll work the answers into my presentation.

Disconnecting for a week

I've been married for nearly 15 years. During that time, I have never taken a vacation wherein I didn't do some kind of work. Sad but true! Actually, "sad" isn't quite the right word; the freedom to work from the road has let me spend a lot more time traveling with my family than if I had a job that required physical presence in a defined location. However, I'm breaking the mold: for the next seven days, I'll be cruising the Caribbean with no laptop, and thus no email. I will have my trusty Treo, but it only works in 3 of the places we're going to, and I'm mostly taking it so we can call the kids to see how they're doing. I've already turned in my columns for next week, along with some other stuff that needed doing, so I'm free as a bird until 2/13. See you then!

IBM promises better Mac support

This is interesting: Computerworld's running a story saying that IBM has promised to make good its years of benign neglect by shipping a Mac Notes client that has feature parity with Windows. As someone who had to suffer through writing applications for the Mac Notes clients back in the day, I say "it's about time". Now, Microsoft: how about improving SharePoint support for Mac OS X?

Tony Redmond in Forbes

Forbes Magazine has an interesting, if short, interview with Exchange sensei Tony Redmond. For those of you just stepping out of the spaceship, Tony is an ex-DEC, ex-Compaq messaging specialist with an incredibly deep background on messaging in general and Exchange in particular; he's also a VP and CTO of the services division at HP.

LUA white paper

Ever want to know how to effectively use limited user accounts (LUA) to run on Windows XP? Me too. Fortunately, MS just released a white paper that details what LUA is (and isn't) and how to implement it on XP desktops. This is very valuable guidance-- try it yourself and you'll see what I mean.

The iPod goes to court

| 2 Comments

It's not often that I can praise Toledo (which I live near) as a technology leader. However, in yesterday's Blade, a story by Mark Reiter gives me something legit to praise: the local federal district court is using iPods to pass out evidence to defendants for review. I've got a call in to Jeff Helmick, who's quoted in the story, to ask some follow-up questions; check back here for an update.

Free books to good home

| 6 Comments

I’m cleaning out my office (that faint sound you hear is applause from my wife). I have 12 copies each of Secure Messaging with Exchange 2000 and Secure Messaging with Exchange Server 2003 to give away. If you want one, reply via email with your postal address (be sure to tell me which one you want) and I’ll ship it to you. First come, first served.

Update: all of the Exchange 2003 books are spoken for, but I still have a few Exchange 2000 books available.

Old-school book review

While searching the Interweb for something else, I found this review of Secure Messaging with Exchange Server 2003 by fellow MVP David Sengupta. Somehow I completely missed it when it was originally published. Duh. It was fun to look back (and, of course, if you haven't bought the book yet, you should read the review and then Make the Right Choice!)

Good performance question

A reader wrote to quiz me about my recent columns on 64-bit Exchange and the performance benefits it should offer. He asked:

In your last e-letter you mentioned the added performance boost putting Exchange on a 64-bit box. For those of us that connect our Exchange servers to an iSCSI SAN, would we not run into bottlenecks at the NIC (1Gb backbone, assuming we were not using a TOE card or maybe even if we do), before a 32-bit setup cut into performance?

I'll trot out my all-purpose answer: "it depends."

First, let's assume that you have a Gigabit Ethernet connection to the iSCSI SAN, with an HBA that has a native x64 driver-- no thunking required. That's just a clarification, but in the end it doesn't really matter. Why? Assuming that you have "enough" RAM (where the precise value of "enough" varies according to the user workload on your server), JET 12 is going to be able to cache a significantly larger portion of the EDB data than it can now, meaning that the amount of bandwidth between your server and the iSCSI cabinet becomes much less relevant from a perf standpoint. We already see a similar effect now; when SAN vendors are hunting for business, they often put lipstick on the bulldog by adding a very large cache to the controller. Of course, this only works until the disks hit 70% or so of capacity, then the cache detunes and performance drops like a rock. That's a problem only because the SAN controller has no idea what the application is doing; it's not a problem for Exchange in this case because ESE is in charge of the cache. Given "enough" RAM, the amount of bandwidth you use for a given set of user behaviors should decrease because you'll be making fewer requests to the actual disk.

What about page size? My gut feel is that the page size change will be a wash; caching will reduce the total number of IOPS that have to go over the wire, but those pages that do go will be 8KB vice 4KB. I'm looking forward to seeing hard data to confirm or disprove this, though.

Why did I say "it depends", then, if the performance news is so rosy? Because one of the key reasons people will be deploying Exchange 12 is to consolidate servers. Obviously if you take four or five Exchange 2003 servers and stuff their mailboxes onto an Exchange 12 server, the new server is going to require a significant amount of SAN bandwidth, and I suspect it'll easily be possible to build configurations that would saturate a GigE HBA. So, don't do that and you should be good to go!

If it's MacWorld week, it must be time for more Mac news here. Today's dose: Research In Motion has licensed IAA's PocketMac product. It'll be made avaialble as a free download on RIM's web site starting in February. This is obviously a good move for IAA, makers of PocketMac, and clearly it's an effort by RIM to remain competitive with Palm for hearts-and-mindshare among Mac users.

It's Patch Tuesday, so you know what that means. This month, there's actually an Exchange patch, although it only applies to Exchange 2000, Exchange 5.5, and Exchange 5.0 on the server side (Outlook 2000, Outlook XP, and Outlook 2003 are all affected too, though). The vuln reported in MS06-003 is a problem in the TNEF decoding engine that can allow remote code execution. Interestingly, MS released security patches for Exchange 5.5 even though it just went end-of-life 10 days ago... and what's up with that crazy Exchange 5.0 patch? That's been out of support for quite a while, and I'd bet the percentage of sites using it is very, very small.

Time for a new laptop?

| 2 Comments

Lenovo and Apple are fighting over my wallet. I'm thinking about buying a new laptop, and the two contenders now are the Thinkpad T60 and the brand-new MacBook Pro. The big variable is whether the MacBook can run Windows, either using VirtualPC (Microsoft isn't saying) or natively. If yes, that's my choice; if no, I'd probably lean towards the Thinkpad. Fortunately, neither one is actually shipping, so I don't have to make a decision quite yet.

Jim McBee says something that I've been evangelizing for a while: turn off outbound SMTP on your network. The only machines that should be able to send it are your messaging servers. Maybe, if you're feeling generous, you might allow VPN users to send SMTP so they can send mail while on the road. That's it, though. There's no good reason why Joe Cubedweller should be able to send SMTP direct from his machine. Worms like Sober use it, as do a number of rootkits/botnet droppers.

TechEd '06 session proposals in

I just sent off three session proposals for TechEd 2006. I didn't bother to submit anything last year, and-- big surprise-- didn't speak. It was nice to take a break and attend without having to speak, but I missed it, so this year I'm back to my normal MO. I'll also be speaking at Exchange Connections 2006 and the newly added Exchange Connections Europe-- more info on those coming soon!

Threats and Countermeasures version 2.0

I'm delighted to announce that Microsoft has released updated versions of two of its key security guides: the Threats and Countermeasures Guide 2.0 and the Windows Server 2003 Security Guide 2.0. Devin and I put in a lot of hours updating these two guides to reflect updated settings in XP SP2 and Windows Server 2003 SP1, and there's some very useful new information therein.

Don starts blogging

Normally I wouldn't mention this here, but it has security relevance. Don recently started blogging. Why do you care? Because he's an attorney who works for a really large software company in western Washington. In that capacity, he's written some amazing stuff that I hope shows up in his blog over time.

Cliff Reeves blogs

I had the opportunity to work with Microsoft's Cliff Reeves earlier this year, and thoroughly enjoyed it-- Cliff is scary smart, quite personable, and really "gets" the collaboration space. I urged him to start a blog, and whaddya know? he did! Check it out at http://cliffreeves.typepad.com/dyermaker/.

I just attended a Live Meeting hosted by Microsoft's Nicole Allen and Mike Lee. Nicole is well known in the Exchange community as being an expert on Exchange performance analysis, and her presentation covered some of the guts of the Exchange Performance Troubleshooting Analyzer (ExPTA). If you haven't used ExPTA, you're missing out; it's a terrific tool for analyzing the performance of your Exchange server and identifying problems, including problems experienced (or caused) by individual users. Mike Lee also did a similar presentation on the Exchange Disaster Recovery Analyzer (ExDRA). (For a good tutorial on what ExDRA does, see Marc Grote's article here.)

The interesting thing to me is the degree of investment that Microsoft is putting into these free add-on tools for Exchange. They fill a void that no third party vendor has effectively exploited, and customers love them because they greatly simplify the process of finding current or latent problems with an Exchange configuration. Between ExBPA, ExDRA, and ExPTA, Microsoft is assembling quite a formidable set of analysis and troubleshooting tools.

I meant to blog this, but with all the other things that've been going on, I forgot. Exchange Server 2003 has passed the evaluation process for receiving the Common Criteria security evaluation at Evaluation Assurance Level (EAL) 4. There's a good article at the Exchange team blog that covers the certification process and what CC certification means. Interestingly, I haven't found any evidence that any version of Domino is CC-certified, but I probably just wasn't using the right search terms (I note that IBM's talked a lot about the EAL-3 version of SUSE Linux Enterprise Server 9).

Microsoft releases Exchange 12 beta 1

It's a closed private beta, but there's some good information at their beta 1 preview site: http://www.microsoft.com/exchange/preview. Expect more information after the first of the year...

The OCS 10g documentation says you create SMTP domains by logging in to the web mail client and using the Administration tab. It also says that you won't see that tab unless the account you use has either domain or system admin privileges. However, it doesn't say that "domain administrator" accounts can't actually create or remove domain objects; you have to have "system administrator" for that.

Google Ads as comedy

Need a good laugh? Go to this article and check out the targeted ads. Obviously Google is channeling the feelings of people who've worked with OCS.

SearchExchange serializes my DR ebook

The folks at SearchExchange have been kind enough to turn chapter 2 of my current ebook, The Definitive Guide to Exchange Disaster Recovery and Availability, into a short "10 tips in 10 minutes" article. Check it out here, or get the entire book (well, the first 6 chapters; I just turned in the final chapter yesterday) here.

Jasjar update

| 3 Comments

My Jasjar wasn't really dead, it was just playing dead. I let the battery run down completely, then plugged it in to my Thinkpad and tried the firmware update again. This time, it worked like it's supposed to. John and I had fun playing around with it at the office; it flawlessly plays video that was encoded for his iPaq hw6315. I have several TiVo-to-Go shows on my laptop that I want to transcode to watch on the device, but WMP10 obstinately refuses to recognize the Jasjar, and since I'm on an airplane I can't check the Internets to see what the likely problem is.

I'm also having problems with ActiveSync 4.0, but that's nothing new. Every version of ActiveSync I've ever used has been troublesome. Come to think of it, so has every version of the Palm OS sync software (man, the stories I could tell about their Mac products…) Maybe that helps explain why Nokia just dropped US$430 million on IntelliSync.

Jim McBee's slides

Jim McBee has posted the slides for his (excellent) presentations at Exchange Connections. Get them here. Now, maybe I should do the same...

Exchange 12 to be 64-bit only

| 1 Comment

Breaking news: Exchange 12 will be 64-bit only. I have a lot more detail to post on this, but they're about to close the forward boarding door-- more when I land in Cincinnati in an hour or so. Here's a link to the umbrella press release from IT Forum.

Why the change? x64 technology is already widely deployed, and using it with Exchange reduces the I/O count dramatically-- by up to a factor of 4. This is huge, since IOPS are much more expensive than RAM or CPU. (If you don't believe me, try pricing 16GB of DRAM and a dual Opteron server compared to an EMC SAN and get back to me).

One objection I anticipate hearing is that this will strand customers who aren't on x64 hardware. I'm resistant to this argument, though, because even low-end servers now often include x64-capable CPUs, and this trend is only going to accelerate between now and the time Exchange 12 ships next year. Organizations that are planning to move to Exchange 12 after it ships can easily buy x64 hardware any time between now and the time they upgrade, usually without any increase in cost. Of course, I expect to hear criticism of this move because some customers won't be prepared to move to x64, but the fact is that there will always be customers-- for any product-- who don't want to, or cannot, upgrade when the manufacturer wants them to. Sure, there will be Exchange customers who will cling to their existing versions, but that has always been (and will always be) true for Exchange, Notes, Workplace, OCS, SAP, and any other software in this class.

The big news here, to me, is that Exchange is once again breaking ground in delivering a new technology-- and in this case, it's one that has the potential to radically alter the scalability and cost factors we're used to working with. I can't wait to get my hands on some E12 bits and start testing!

NewsGator Enterprise Server

| 1 Comment

This week's UPDATE column, posted here because I don't have time to write a separate entry on this right now

One of my favorite things about IT conferences like Exchange Connections is going to the exhibit floor to talk to vendors and see their products. Sometimes large vendors like HP and Symantec have interesting things to say (like Symantec's announcement of a new version and pricing strategy of their Exchange security products), but for my money the real goodies are usually found in the booths of smaller vendors. They tend to be more enthusiastic about their products, and more engaging when discussing them. I'll do a broader review of some of the cool things I saw here next week, but with my deadline looming I had to pick one thing to write about, and it's… RSS.

Now, you may wonder what RSS has to do with Exchange. Over the last year I've mentioned RSS a few times, but it's always been as a client-side technology that enables individual users to find the information sources they want and display them in a web browser or a rich client like Outlook. However, there are some problems with client-side RSS use:

  • you have to install an RSS client on each desktop; this is a non-starter for organizations that are trying to reduce the number of desktop touches. It also encourages end users to install and manage their own software, another hot-button issue that many firms are trying to clamp down on.
  • users make duplicate requests; if you have 500 users, and 200 of them are making hourly requests for the latest content for a particular RSS feed, you're using excess bandwidth to pull the same data over and over. (Of course, the owners of the servers providing the RSS feed might take issue with getting a large number of requests from your organization, which is why heavily-trafficed sites often include a throttling feature that will block requests from IP addresses that are making requests too often.)
  • users are left on their own to find the information sources they need. This is an advantage insofar as it allows users to make their own choices, but it makes it difficult to effectively share and consolidate useful information.

NewsGator Technologies has been making client-side aggregators for several years; their NewsGator for Outlook plug-in is my primary aggregator. I run it in a VM to let it collect RSS data that is then published to a tree of folders in my Exchange mailbox; that way, I can access it through OWA, Outlook, Entourage, or even an IMAP client. This addresses the first two of the problems I mention above, but it doesn't do anything about the third, and it doesn't scale well.

Enter a new product that NewsGator is showing on the expo floor: NewsGator Enterprise Server. It's a slick piece of work that effectively addresses all three of these problems by collecting and consolidating feed data in a centralized SQL Server database, then publishing it to users' mailboxes via WebDAV. This eliminates the need to license or install individual client plugins, and it makes the collected RSS data available to any client that can access an Exchange mailbox through IMAP, WebDAV, or MAPI.

This functionality in itself is very useful, but NewsGator architect Lane Mohler surprised me by showing me two other features. First, NewsGator Enterprise Server lets you specify default feed sets for individual mailboxes, or for sets of mailboxes as defined by Active Directory groups or OUs. For example, you can define a default set of feeds for users in your sales organization, and those feeds automatically appear in those users' mailboxes. Add a new employee, and she automatically gets access to whatever content you've identified as most valuable for people in that position. This neatly eliminates the problem of helping new users find the right set of resources when starting a new task or position.

The other cool new feature is called clippings. It addresses the problem of sharing relevant information by allowing any user to select an individual article and add it to their clipping set—to which other users can subscribe. I think of this like a librarian-in-a-box. Say you have someone in your company whose job it is to find articles about the company or its competitors and share them with appropriate groups. They probably do this by mailing URLs or articles to people, but the same task is more easily accomplished by using clippings; as the librarian finds relevant articles, he can add them as a clippings that are then automatically published to the appropriate users and groups.

What really gets me excited about the potential of NewsGator Enterprise Server is that it works with any kind of RSS feed, not just blogs. You can produce RSS feeds from SharePoint data or other back-end systems, making it easy to slip notification or status data automatically into users' mailboxes—a very cool potential that I expect other vendors to exploit.

Exchange 2003 SP2 on SBS 2003

I got a reader question asking whether you can install Exchange 2003 SP2 on Small Business Server 2003. On first reflection, I couldn't see why not; a quick query to Susan Bradley (SBS MVP and mistress of all SBS knowledge) netted a link to this article by Vlad Mazek, which explains the installation procedure in great detail.

It's live! Exchange 2003 Service Pack 2 is now available for download. This is great news, because SP2 adds some very welcome message hygiene, mobility, and management features. I'm working on an article on the mobility features now, and as soon as that's done I've got plans for a lengthy post exploring Sender ID support.

Update: here's a list of the bugs that are fixed.

Exchange 2003 Service Pack 2 available

It's live! Exchange 2003 Service Pack 2 is now available for download. This is great news, because SP2 adds some very welcome message hygiene, mobility, and management features. I'm working on an article on the mobility features now, and as soon as that's done I've got plans for a lengthy post exploring Sender ID support.

Exchange Connections is only a couple of weeks away, so I thought I'd post my final speaking schedule. Because Donald Livengood from HP has had to cancel, I've picked up his three sessions, leaving me a total of five:


  • Tuesday @ 2:15p: Deploying Rights Management Server with Lessons Learned

  • Wednesday @ 10a: Exchange Security: Tips and Tricks

  • Wednesday @ 2:15p: Multi-Forest Deployments

  • Wednesday @ 4p: Layered Anti-Spam with Exchange

  • Thursday @ 11:45a: Fun With Global Settings, Message Limits, Recipient Policies, and Connectors

Thursday at 2pm, I'll be busy collapsing from exhaustion.

(A shout out to Jim McBee, who graciously agreed to take my place on the Exchange 5.5 migration panel with Kieran McCorry and Missy Koslosky; it's scheduled at the same time as Don's RMS session.)

Microsoft Antigen

It's official-- from a Microsoft press release:

Today Microsoft also announced plans to release Microsoft Antigen anti-virus and anti-spam security software for messaging and collaboration servers based on the technology from recently acquired Sybari Software Inc. Adding to the defense-in-depth strategy inherent in Microsoft Antigen, Microsoft will add its own anti-virus scan engine. When it is available, customers of the Microsoft Sybari product line will benefit from the addition of the Microsoft anti-virus scan engine at no additional charge throughout the length of their contracts. In addition, Microsoft Antigen for Exchange recently completed Microsoft’s Security Development Lifecycle review process, which has been shown to achieve measurably improved levels of security for numerous Microsoft software solutions. Microsoft Antigen for Exchange is scheduled to be available in beta to customers in the first half of 2006.

Exchange VSS best practices paper

Wow, this is great-- a new Microsoft white paper on the recommended best practices for using the Volume Shadow Copy Service (VSS) with Exchange 2003. This is long overdue. VSS is a terrific backup mechanism when properly implemented. If you're at all interested in VSS, check it out. (Hat tip: Ross Smith)

SMT5600 for $0

For some reason, my review of the Audiovox SMT5600 is one of the most popular items on this blog (according both to page views and my referer log). In that vein, Buy.com's running a sale on the SMT5600: pay $224.99, then get $225 of mail-in rebates; when you activate it, you can also get a Jabra Bluetooth headset for free.

Monad, baby!

| 2 Comments

I'm at the Microsoft MVP summit in Redmond this week; today and tomorow are the "heavy" days that focus on specific technologies. Yesterday we had some executive keynotes in the morning, followed by some platform technology sessions. I got to see Jensen Harris' very cool presentation of the new Office "12" user experience (which I think wasidentical to what he showed at the PDC). I also got my first detailed look at the new Monad shell. Jeffrey Snover did the demo; there's a video of a similar demo here. I was blown away by Monad's elegance and simplicity; although Jeff didn't show any Exchange functionality, it's easy to see how features like the "-whatif" switch (which runs your script and shows that the output would be, but without committing any writes) could be useful. More interesting (at least to me) is how composable Monad is; you really can combine a wide range of cmdlets to take complex actions. I'm looking forward to learning more details about this today.

I'm not making this up. From this morning's email, an announcement from SANS of an upcoming Exchange security webcast. Here's an excerpt from the announcement:

A Microsoft Exchange Server is often found as one of the most important collaborative assets to current organizations of all sizes. With so much dependency on a reliable e-mail and collaboration system, many organizations are faced with the problem of how to secure those communications. This webcast will introduce listeners to Exchange messaging protocols and discuss strategies to secure those communications. This webcast will focus on Microsoft Exchange Server 2003. Miles Stevenson has spent the last five years working as a Linux network administrator. He worked in both commercial and government sectors specializing in low-cost Linux solutions. He currently works as a full time network administrator for the SANS Institute and directs the SANS Assessment program.

Now, I don't mean any personal disrespect to Mr. Stevenson. However, I don't understand what in his background as a Linux admin qualifies him to talk about securing Exchange. Securing any enterprise messaging system requires a fair bit of specialized knowledge, including a good understanding of the underlying OS. I wouldn't expect an Exchange administrator to be able to talk knowledgeably about Linux security, for example. I'm curious about what exactly will be covered in the webcast, but I'll be on a flight when it's being presented-- if you monitor it, leave a comment here and let me know what you thought about it.

Exchange hotfixes for Entourage 2004 SP2

See, I told you the Entourage blog was about to spring back to life. Today's entry: the details on the Exchange hotfixes suggested (but not required) for using Entourage 2004 SP2 with Exchange 2000 and Exchange Server 2003.

Today Microsoft announced that it was releasing Service Pack 2 (SP2) for the Macintosh version of Microsoft Office. Apart from the usual bug fixes to all of the Office apps, the big news here is that SP2 makes some major-- and welcome-- changes to Entourage's Exchange support.

There's a long list of tasty new Exchange goodness in the SP2 release, including:

  • A new model for calendaring and address books. Previous versions couldn't support calendar or contact public folders; this release does. In order to enable that support, the dev team changed the way calendar data is stored and managed. Now you'll have a calendar on your local machine, plus a calendar for each Exchange account, plus any calendar public folders you have. For most Exchange users, this will be a huge improvement. For the small number of users who'd defined multiple Exchange accounts in the same Entourage identity, you'll notice that now Entourage doesn't automatically sync events from every calendar to every other calendar.
  • Much, much better sync performance with Exchange accounts. (They also fixed that annoying bug where the Progress window would pop up even when you'd previously closed it.) Public folder browse performance is greatly improved too.
  • Support for setting permissions on Exchange items. That's right-- you can now grant permissions on any folders in your mailbox, just like you can in Outlook. You can also open other users' shared folders, provided you have permission to do so.
  • You can create private calendar and contact items.
  • There's much better support for delegation, including the ability to assign other users as delegates.

There are also some less obvious, but perhaps more welcome, changes. For example, Entourage now honors the Thread-Index and Thread-Topic headers that Outlook uses. That means that conversations with Outlook users will be properly threaded. Entourage also includes a new Conversation view type that properly threads mail messages-- a feature that's long overdue (though you could simulate it by creating your own custom view). You can also do a "get info" on any folder to see how much space it's taking up on the Exchange server-- something I use all the time, given the mailbox limits applied to some of my accounts.

SP2 is available for download from Microsoft's Mac website; as far as I know, it will update either the RTM or SP1 versions of the Office suite, and you'll need to install it separately on each machine unless you're using a software distribution system. Microsoft has also promised to make it available through their automatic update mechanism for Mac Office, but it doesn't seem to have shown up there yet.

Update: Gerod reminded me that you need an Exchange hotfix to enable sharing and delegation to work; I'd forgotten all about that. (Also updated the links to point to live content)

Update: John Welch has tons of screen shots in his article on SP2.

Entourage team blogs

Did you know that there's a blog maintained by the Entourage team at Microsoft's Mac business unit? Me neither. But they do, and a little bird tells me that they're going to start updating it much more regularly. Drop by and add it to your aggregator if you use or support Entourage.

Exchange 12 developer roadmap posted

Cool stuff from the PDC: the developer roadmap for E12 was unveiled at PDC today. Terry Myerson has a post on it at the Exchange team blog, or you can just go straight to the PowerPoint deck from the session. I've got a lot of catching up to do, since the Cookbook depends on WMI and CDOEXM.

Setting default reviewer permissions

Let's say you wanted to set every calendar in your organization to grant all users "reviewer" rights. This makes it easy to see detailed calendar data instead of just pure free/busy information. There's no direct way to do this through CDOEXM or WMI, but Glen Scales has come up with a solution that uses the Exchange 5.5 acl.dll. Check it out here.

Microsoft rolls out workflow

I actually had real work to do this week, so I couldn't attend the PDC. That's too bad, because there's a lot of interesting stuff happening there. For example, MS today took the wraps off Windows Workflow Services, their platform for workflow integration. There are some interesting touches that I think will help distinguish their offering from their competitors, including integration with Visual Studio and a marketplace for workflow actions (which MS is calling "activities".) When I get some time, I'll have to dig into this and see what's what.

In related news, MS also started talking about changes to InfoPath (hint: no more requirement for a client-side application) and their new Office server platforms. It's very interesting that they're focusing on BI and content management as first-class tasks in the new release; we'll have to wait and see what capabilities they're able to get in for the 1.0 release.

Byzantine failures

There's a fascinating article in the most recent issue of RISKS Digest about anomalies and Byzantine failures in flight control systems. I can't explain it nearly as well as Peter Ladkin, who wrote it, so I won't try. Although Exchange and Windows aren't generally vulnerable to Byzantine faults, it's a fascinating area of study in security-critical systems: how do you design systems that keep working when their inputs are lying?

I’ve been heads-down on some deadline-critical work, so I hadn't followed the Notes/Dominio 7 release as closely as I evidently should have. I woke this morning to find out that— oops— IBM isn't shipping DB2 support in Notes 7. See Ed Brill’s page for his take on it, including the news that you can apply for access to the DB2 functionality. I have to wonder whether there are secret criteria for the application process; I guess I'll find out when I apply. It's too bad that this feature didn't make the cut, although IBM had a tough decision: slip to keep the feature or ship without it. Given the customer uncertainty over the impact of moving to DB2 as part of Workplace, I'm sure they would have liked to ship this feature on schedule.

Interestingly, the reason Ed cites for not shipping the feature is that not enough customers were testing it. Microsoft has worked long and hard to build a real-world customer testing program, the Technology Adoption Program (or TAP). TAP customers run pre-release builds of Exchange in production, with full support from PSS. Of course, MS also dogfoods new releases in their own environment; between the TAP and internal MS users, my recollection is that there were about 150,000 mailboxes running live on Exchange 2003 during the latter part of its dev cycle. I expect to see the same thing-- probably with bigger numbers-- for Exchange 12. Perhaps IBM should consider a similar approach.

Recovery firms get busy after Katrina

Pace this ZDNet story, which describes how MessageOne has seen a spike in workload with the unwanted arrival of Katrina in the New Orleans-Biloxi-Gulfport-Pensacola strip. The article makes an excellent point: the time to get a recovery or continuance solution in place is before the bad weather starts. Just like flood insurance, if you wait too long you won't be able to get protection in time.

Upgraded to MoveableType 3.2

All I can say is "wow!" There are a ton of new features and enhancements-- very impressive for a point release. Please let me know if you find anything that doesn't work properly.

Steve Friedl just posted the first public draft of "An Illustrated Guide to IPsec". It's very well done, with lots of illustrations that help explain how IPsec works. It will help if you already know the basics of IPsec, but there's a good bit of intro-level information for those who aren't already IPsec gurus.

Jesper's blogging

Wonderful news: Microsoft's Jesper Johansson is blogging. (You may remember him as the guy who said it's OK to write down passwords). Check it.

Microsoft is making a "community technology preview" (CTP) of Exchange Server 2003 service pack 2. This is pretty cool. Get it from this link (which should be live shortly). I'm particularly interested to see how people put the Sender ID tools to use.

Update: the Exchange team blog has a list of FAQs about the CTP. Note well that the CTP build isn't supported by PSS and shouldn't be run on production servers.

Great news: CIS has finally released their benchmark for Exchange 2003. It's a fairly comprehensive assessment and hardening guide for Exchange Server 2003 (see these FAQs for more details). It was developed by CIS with input from NSA, MITRE, Microsoft, and various parts of the Exchange community. I think it will be of great benefit to most organizations now running Exchange (of course, I should have asked them to include the book in the bibliography :) )

Devin's new DCAR book

Devin Ganger, my cow-orker at 3sharp and coauthor of the Exchange Server Cookbook, is on the scoreboard again-- this time with an ebook on discovery, compliance, archival, and retention. The first chapter's now available, so go check it out.

I've been asked several times about ways to disable the use of removable storage devices to protect against pod slurping and related attacks. XP SP2 has a way to prevent writing to USB devices, but there's another solution that's described in this MVP-contributed KB article.

HA vs BC

| No TrackBacks

From an article I'm working on, the difference between high availability and business continuance succinctly expressed:

Availability measures how much use we get out of a system before it fails, or between failures. Business continuance (BC) is different; it means being able to continue business operations (possibly with some degraded capacity) while a recovery operation is in progress. A simple example might help: if your building has an automatic emergency generator, that's HA. If you have to bring in your own generator from home, that's BC.

Last year, I wrote about US v. Councilman, a court case in which the initial ruling seemed to indicate that it was OK to intercept others' email under certain conditions. Yesterday the First Circuit Court of Appeals issued a new ruling, essentially reversing the old one. Councilman was indicted in 2001 for violating the US federal law covering wiretapping because he was using procmail to copy inbound messages to hosted users on his server. The case was originally dismissed based on Councilman's claim that the messages he copied were in "electronic storage" (which has a narrow meaning under the 1968 wiretap law), and that what he did wasn't technically "interception" as defined in the law. The government appealed, and now the Court of Appeals is siding with them. Read their ruling for yourself; after I have time to dig into it a bit more, I'll have more to say (bearing in mind, of course, that I'm not a lawyer and don't give legal advice.)

Finally! Microsoft's released Microsoft Messenger:mac 5.0, which can use both the MSN Messenger service and Live Communications Server 2005. It fully supports TLS and Kerberos (although you'll need to read this reskit paper to turn Kerberos on). It also supports PIC for LCS if you're using it. In my tests over the last few months, I've found it very stable. It just works. If you're using a Mac, give it a try. (now, if we could only get a new version of the suck-a-delic Windows Media Player for Mac...)



See above: how much would you pay for a solution that actively prevents people from using "reply-all" to mass-distribution mails? (RMS does lots of other neat stuff, too, that I'll be writing about in the future.)

Here's an interesting tidbit: Scalix announced today that they're going to ship a wireless solution for their messaging product, based on Notify's product. Pricing and availability weren't announced; from a functionality standpoint, Notify has a pretty nice solution in terms of the range of devices and OTA methods they support. However, this may add significantly to Scalix' "flyaway" cost, making them potentially less attractive compared to Exchange 2003. No word yet either on whether Scalix will require device or mobile CALs in addition to mailbox CALs. Developing...

Bruce Schneier is a smart guy, but he also has a strong anti-Microsoft bias. That's why it's no surprise to see this article, in which he lambasts Microsoft for "building in security bypasses". What's he talking about? A quote from Microsoft's Martin Taylor:

For example, this new feature tool we have would allow me to tunnel directly using HTTP into my corporate Exchange server without having to go through the whole VPN (virtual private network) process, bypassing the need to use a smart card. It's such a huge time-saver, for me at least, compared to how long it takes me now.

Of course, that's our friend RPC-over-HTTPS. I think Schneier missed the point because he misunderstands the intent of the feature, which is to allow mail-only access from remote systems. It's true that VPNs allow for secure remote access to many different types of resource, often using multi-factor authentication. It's also true that many VPN systems (particularly the clients) are unstable and difficult to use, particularly from locations like hotels and airports where the network provider may not be clueful. The RPC tunneling feature allows secure access to email only without a VPN. This is actually a security benefit.

Why? Think of what happens when you connect a remote computer via VPN: you're allowing it unrestricted access to your entire corporate network. That means that when Joe Executive's home machine connects via VPN it has free roam of the network. That places a mighty high premium on ensuring that the remote machine is uncompromised, hence the interest in network access protection (but that's a solution for another day). As an admin, if I have users who only need email, I'm perfectly happy for them to use RPC-over-HTTPS instead of VPN because then I know that their machines are very unlikely to be able to cause damage to other machines on my intranet, no matter how crap-infested they may be. Couple RPC tunneling with an application-layer RPC scanner (like the one in ISA Server 2004) and you're better off than you would be with a pure VPN solution.

Some of the comments on Schneier's post make good points about the tradeoff between usability and security, including one guy who asks why VPNs are so hard to use. That's for another post, unfortunately.

Escape from Yesterworld

| No TrackBacks

The MS SQL Server 2005 and Visual Studio 2005 teams have a hysterical site called "Escape from Yesterworld" that casts IT development as something out of Flash Gordon. The overall site design is brilliant, and there are some extremely amusing video clips there, including:

Well worth a look-- I give it two thumbs up.

Yesterday I wrote about Simon Butler's quest to prevent individual users from sending messages via MAPI. In related news, the Exchange team blog has a great post today explaining how Exchange 2003 SP2 gives us the ability to block individual users from using MAPI. The good news: because the MAPI blocking is added to the existing ProtocolSettings mechanism for blocking other protocols, you can use the same script to block or allow multiple protocols at once. The bad news: as with Simon's original question, this method doesn't stop existing connections; it only blocks new ones. Still, this is a valuable new capability to have.

Wow, this article made my head hurt. David Berlind of ZDNet documented all the stuff he had to do to get his XV6600 to work via Bluetooth as a modem for his laptop. I admit that I never bothered to try this while I had a loaner XV6600, fearing that it would be too hard to be worthwhile. Here's Berlind's conclusion:

OK, now that we're done, and some of you now have the best step by step you'll ever find for getting a DUN connection working with Bluetooth, what does it tell you that takes nearly 40 distinctly separate screen shots or photos to document something that should be a lot simpler?
It tells me that I'm sticking with my aircard, thankyouverymuch.

Exchange MVP Simon Butler posed what seems like a simple question: how do you stop a user from sending mail? The answer is deceptively complex; we've been debating this on an MVP list for a few days now.

Say you have a MAPI user. You disable the associated Active Directory account, either by disabling the account or by changing the password. In either case, the user can still submit mail to the information store! In the case of a password change, the user will be asked to authenticate again, but if she cancels the password dialog, she can still send-- she just can't receive new mail! That might be a problem in case of an employee who's leaving (voluntarily or not), although a measure of physical access control will help.

You can kill the MAPI session, but that doesn't do anything to stop the user from reconnecting from the client side, at which point you're back to square 1: the user can still send mail. (This doesn't seem to be true if the user quits and relaunches the client after you kill their session, though).

For other protocols, it's easy to prevent users from connecting and sending mail. For example, for IMAP, POP, or HTTP connections, you can just remove the user's ability to use those protocols by using the Exchange Features tab in AD Users and Computers.

If you want to block all users, you can do that too; KB 288894 describes how to limit MAPI connections to a particular version of Outlook (so just set the regkey to deny from the current version (which I think is 11.0.6352.0) backwards. For HTTP, you can either set an IP address restriction on the Exchange vdir (thanks, KC!) or stop the w3svc, although this will have other effects. For that matter, if you want to prevent all client access, stopping store.exe will do the trick nicely at the cost of a service interruption.

Perhaps MS will fix this in Exchange 12.

I leveraged McDonald's wireless service when I was in rural Louisiana, but it looks like I'll have a tougher time getting connected while I'm at Sturgis. The nearest McD locations to Hill City, where we're staying, are in Rapid City, and none have Wi-Fi. Verizon's coverage map shows no coverage for Hill City, although the surrounding areas have digital service-- hopefully I'll be able to use my aircard. There's a local ISP, RapidNet, that may be able to help, too.

Interesting press release this morning from Blue Security, touting their new "Do Not Intrude Registry". The basic concept is simple: you sign up for their service and install an agent on your local computer. Blue creates honeypot mailboxes, which it then monitors. If spammers spam those mailboxes with messages that don't comply with the CAN-SPAM law, Blue asks the spammers to stop. If they don't, the Blue agent (which they call a Blue Frog, after the blue poison arrow frog) starts spamming the spammers by posting junk data to their order form. This is no big deal if only one agent does it-- but the agents are cooperative, so if the spammer sends out 10,000 messages, they get 10,000 junk order submissions.

The PR calls this "ethical and effective". I disagree on both counts; it's nothing more than a botnet in disguise. If it's wrong for J. Random Attacker to mount a DDoS against a website they don't like, it's wrong for Blue to mount DDoSes against spammers. Despite the fancy language deployed by Blue's CEO in this InformationWeek article, it's pretty clear that this is a clear-cut DDoS approach-- Blue is trying to hit the spammers where it hurts by degrading their operational capacity to take orders.

I don't condone spammers, but descending to their level isn't an ethical approach. In a remarkable coincidence, most of the sentiment on /. seems to agree that this is a bad idea.

Update: but don't take my word for it; legendary guru John Levine has weighed in with his thoughts (including the interesting fact that Blue tried to get sponsorship from a number of anti-spam orgs, all of whom rejected the idea).

I missed this in all the hubbub here at el rancho, but Alexander Nikolayev posted a terrific treatment of the Exchange 2003 SP2 anti-spam process at the Exchange team blog. He covers how the new SPF/Sender ID filtering process works in conjunction with the existing filtering features. Exchange 2003 SP2 is the only spam filter that Microsoft's using for their 90,000+ worldwide mailboxes; I think that's a pretty strong endorsement of its capabilities.

Just got the press release: Microsoft is buying FrontBridge, a hosted message hygiene service provider. This is primarily interesting because of FrontBridge's strength in compliance solutions; they have a broad range of services built around compliance for email and IM. Their hosted anti-spam services got good props from eWeek, but I think the combination of their data centers (which promise a 99.999% uptime SLA) and their compliance services opens the door for MS to diversify beyond Windows OneCare into a broader scope of direct service provision. I can't wait to see what part they play in the promised Exchange 12 updates for better compliance and message hygiene.

IIS 6 metabase auditing

| No TrackBacks

Unless you read the "Book of SP1" very closely, you might have missed out on the fact that Windows 2003 SP1 enables auditing of metabase object access. The IIS documentation for the feature is of little help, since it's missing some steps. This can be very handy for Exchange administrators, given how much heavy lifting the IIS core components do. IIS MVP Ken Schaefer has written a simple explanation of how to configure metabase auditing here.

Here's an interesting development: IBM made a Notes-related acquisition, buying PureEdge. PureEdge makes a set of XML-based forms tools-- not too dissimilar from another familiar XML tool, InfoPath. Could it be that IBM is feeling the pain of having a relatively poor XML story in Notes and Domino? Are they trying to play catch-up? Maybe.

Microsoft is widely reported to be preparing a server-based version of InfoPath, which would give them a pretty complete story for form management on the client, the server, and the back-end (via WSS, SPS, and BizTalk). Looks like form-based application development will become another front in the IBM-MS platform battle. I'll be interested to see how (or if) IBM integrates the new solutions into its products; clearly it's too late for Domino 7.x, so I'd expect these to be part of a future Workplace technology release in some form.

RAID-10 vs RAID-0+1

| No TrackBacks

Ever get tired of trying to explain (or, worse, remember) the difference? Check these handy diagrams: RAID-10 and RAID-0+1.

Update: edited to fix a bad link for the first diagram (thanks, Devin!)

Got an email today from Symantec touting their new "Symantec Disaster Recovery Strategies" conference. It's in Cancun, in October. The email says:

Learn from the experts who best know VERITAS technology, while enjoying beautiful Cancun! It's the perfect combination of work and play.

Training sessions run from 8:00 to noon; the rest of the day is free to "meet in small discussion groups, meet one on one with the instructor, or absorb what you have learned while relaxing by the pool." Now this is the kind of conference I could get into! I mean, TechEd and Exchange Connections are draining because there's so much, y'know, work stuff going on. It's hard! Thank goodness Symantec is going to help out by dialing back the pace a bit.

I thought of making fun of their list of covered topics by adding "Hangover Recovery Planning", "High Golf Availability Design", and "Maximizing Your Return on Bikini Watching", but that would just be unfair-- people might think I'm bitter at not being asked to speak :)

[ personal to Devin: no, you can't go. ]

Now I've heard everything: this article describes (with a straight face, I'm sure) how to set up a Linux box running VMware to use Postfix as the SMTP front-end and Exchange 5.5 as the mailbox store. Why you'd want to do this is beyond me. For an encore, I hear the author's going to write an article on how to run Lotus Notes 4.0 on a PlayStation Portable.

David Ross of Microsoft has posted a long, and extremely interesting, paper on analyzing browser-based malware. I recommend reading it even if you only have a passing interest in the subject; there's a lot of good stuff therein.

Brilliant essay on ID "theft"

John Denker has written a superb essay on why ID "theft" shouldn't be a problem, and how we already have all the tools to prevent it from being one. Excerpt:


it shouldn’t matter if somebody knows who I am. Suppose somebody can describe me -- so what? Suppose somebody knows my date of birth, social security number, and great-great-grandmother’s maiden name -- so what?

It’s only a problem if somebody uses that identifying information to spoof the authorization for some transaction.

And that is precisely where the problem lies. Any system that lets identifying information serve as authorization is so nonsensical that it is hardly worth discussing. I don’t know whether to laugh or cry.

He goes on to draw the distinction between entity authenticaiton and transaction authentication, and goes on to propose a couple of schemes for breaking these into two separate mechanisms instead of the conflated mess we now have. Well worth a read for anyone interested in security.

I'm lovin' it

Ironically, my last two UPDATE columns have been on mobility topics-- and now I'm somewhere with no mobile access!

So here I am in Farmerville, Louisiana. What's there? Not much (rimshot). Seriously, I'm here with my family visiting the beautiful Lake D'Arbonne State Park for our annual family reunion-style get-together. Whoever the State of Louisiana hired to build this place did a terrific job; the scenery is beautiful, the cabins are clean, spacious, and comfortable, and the wildlife is abundant. One thing's missing, though: connectivity. Ideally, I wouldn't have to work this week, but I do, so I've been arranging my schedule to work when everyone else is asleep. The problem is getting information to and from the people I work with.

Last year, we stayed in the same place, and I noticed that my Verizon cellphone worked fine. I figured that my aircard would give me data service. Problem #1: Alltel is actually the local network provider, as I found when I noticed the "Extended Roaming" indicator on my Treo. No aircard, and no data service on the Treo. The local public library has a few Internet terminals, but they're a) unstable b) locked down and c) on a network that won't allow me to plug in my laptop. Last year, I was able to cadge a few minutes from the nice lady who owns the local Radio Shack franchise, but that clearly wasn't a scalable solution. I didn't think she'd welcome seeing me twice a day every day, no matter how many batteries I bought.

The solution came from an unexpected quarter. I asked the lifeguards at the park pool, the folks at the public library, and the staff at the Radio Shack whether there were any public Internet points or cafes nearby. No one had a clue. While racking my brain to think of local businesses from which I could beg bandwidth, I remembered the McDonald's at the corner of La-2 and Bernice Highway-- a mere five miles from the park. A quick call to Devin netted me the information I sought: the local McD's did in fact have Wayport WiFi. Last night I rolled in, opened the laptop, and downloaded the 400+ messages that accumulated since I got here on Saturday. Today I made a grocery store run and stopped off for a Quarter Pounder and some email; I'll be heading back later tonight for another delivery.

I guess that means that I have to officially retract all the crap I gave McDonald's about their food. It's still not my favorite, but I'm willing to put up with a lot for the ability to keep my customers happy by delivering my work on time. It says a lot about their franchise consistency that even a small town like Farmerville rates WiFi in the store.

MBSA 2.0 released

| No TrackBacks

Microsoft today released version 2.0 of the Microsoft Baseline Security Analyzer. Among its many other new features, it can scan for Office security updates (among other products), it works with WSUS, and it presents more data on potential vulnerabilities. Go get it now.

From this morning's Wall Street Journal: Microsoft settles their antitrust dispute with IBM by paying them $775 million; in addition, MS is giving IBM "credit" of $75 million towards deployment of MS software at IBM. This essentially resolves all of IBM's claims of harm to OS/2 and the SmartSuite products, but it still leaves open potential claims by IBM for harm to their server software. It does set the clock for claiming damages forward, though, to June 30, 2002. Interesting...

I've decided to take the plunge into podcasting with a new series of podcasts for Windows IT Pro. The idea was hatched more or less out of the blue while I was sitting at TechEd with Karen Forster and Amy Eisenberg, so I offered to do a trial run of podcasts to see what kind of reader, er, listener reaction we got. I'm trying to do one 'cast a week on average from now until September, at which point we'll see what kind of listener numbers I can post. (In a transparent attempt to raise those numbers, I registered my podcast feed at Apple's new podcast directory; maybe that'll help).

Buy.com is selling the Verizon version of the Treo 650 for $175 to new customers; it's really $399, then you get $225 back via mail-in rebates. Still, that's a good deal for the Treo. Notably, palmOne hasn't released a firmware update for the VZW model, although there are updates for both the Sprint and unlocked-GSM versions that they sell.

ExBPA 2.1 released

| 1 Comment

The Exchange team just released version 2.1 of the Exchange Best Practices Analyzer (ExBPA). There's a lengthy list of improvements over at the Exchange team blog. My favorite new feature: the rule that warns you if only a single GC is present.

Cookbook shipping from Amazon

Amazon is now shipping the Exchange Server Cookbook. The book is now ranked at 8,930 (not bad for a debut title), and it's holding steady at #17 on the "computer early adopters" sub-list. Thanks to all of you who pre-ordered! If you haven't ordered your copy yet, now's a good time :)

Broadcast flag reappears

Even though the the DC circuit Court of Appeals struck down the original broadcast flag rules, the entertainment industry is still trying to clamp down on the devices we all use. I got an "action alert" email from EFF asking people to call Senators on the Senate Appropriations subcommittee that owns technical issues. Apparently the forces of darkness are trying to sneak a broadcast flag amendment into an appropriations vote. If you value your ability to use devices like iPods and TiVos, call or email your Senator right now. It only takes a minute to do, and the subcommittee markup is at 1400 EDT today, with a full committee vote on Thursday-- not a lot of time.

IBM to resell VERITAS products

Now here's an interesting development: VERITAS announced yesterday that IBM has agreed to resell VERITAS' Cluster Server and Storage Foundation products for Linux and for Windows. It'll be interesting to see what impact this has on the adoption of Storage Foundation in the Windows market; it's a very capable product that has been hampered by VERITAS' difficulty in effectively selling non-backup WIndows products.

Wow, this is unexpected. Verity, which makes both the UltraSeek and K2 Enterprise search tools, announced today that they're making one-year licenses for UltraSeek free for collections of less than 25,000 documents. If you have more than 25,000 documents, you can buy a four-year license for US$75,000; while this sounds expensive as all get-out, it's considerably cheaper than their original pricing. UltraSeek's strength is that it's designed to be an install-and-forget search product that delivers a user experience not dissimilar from Google's Internet search; Verity is throwing in access to their classification engine and their extension API, both of which used to be extra-cost options. This is an interesting move, and one which I think will help solidify their presence in this space by getting them into some doors they otherwise wouldn't have been able to cross. The missing piece is still desktop search, where Google and Microsoft have significant leads that Verity will be hard-pressed to match-- we'll have to wait and see what happens.

Clusters are like nuclear weapons: they're expensive; they're dangerous if misdeployed; people who don't have them frequently envy those who do, and they offer some key advantages that aren't easily matched by other technologies. (Also, they can cause significant amounts of fallout.)

Giving Thurrott his props

David Berlind asks "Who broke the Apple news?" He points out that the Wall Street Journal wasn't the first to break the story, as Steve Jobs claimed during his WWDC keynote. However, Berlind credits C|Net's June 3 story. However, more than a month beforehand, Paul Thurrott broke the story in this April 26 column, although he didn't cite sources until May 23rd-- the same day the WSJ printed their story. I'm disappointed to see the widespread lack of recognition for Thurrott, because he was the original person to break the story. And no, saying that David Coursey predicted this in August 2002 doesn't count as prior art, since that was a prediction and not a report of the actual transition.

{ed: updated to add a trackback to Berlind's original article}

Pod slurping?

| 4 Comments

From the "sounds dirty, but isn't" department, the newest security threat to corporate America: pod slurping. Abe Usher wrote a small executable that can be run from an iPod connected to a PC. When run, slurp will find and copy all of the document files it sees in subdirectories of c:\documents and settings. I hate it when that happens.

Live from TechEd: the X41

Scoble's raving about how sexy the new Lenovo Thinkpad X41 is. He's right, but here's the weird thing: where's Lenovo? In Ballmer's keynote yesterday, the X41 was on stage for a total of about 90 seconds. Instead of showing it, it got a brief mention and then Ballmer took it off-stage. The script surrounding its appearance sounded like a bad TV commercial. This would have been a perfect opportunity to showcase what makes the X41 special, or at least to include it in a demo of some kind. We've had a great deal of success including the Tablet in our line-of-business demos; for example, BJ Holtgrewe could have showed his stuff on a Tablet and then disconnected it to roam around the stage, just to highlight his claims about what Maestro and the Outlook managed-code support in Visual Studio could do. I know that IBM's former Thinkpad marketing folks now work for Lenovo, but suddenly they seem to have gone tone-deaf. What's up with that?

Update: I spent a few minutes playing with an X41 Tablet at IBM's booth. Terrific form factor, and it has the same solid feel as my T41 (and its predecessor T30, and the T20 I had before that, and the 600E I had before that). I think IBM's going to sell a lot of these.

Opening riff: Samantha Bee interviewing people in the audience. Medium-funny. We all want to give information workers a wedgie!

Paul Flessner onstage, "interviewed" by Bee. "This morning, he's the Techie Show's special senior connected systems correspondent."

Flessner: IT's a tough job. Budget's always cut. Clinton imitation: "I feel your pain." Bee: "Can you honestly echo his quote that he didn't inhale?" Big laughs. Funny story about accidentally powering down a rack of 3380s.

Now Flessner's presentation starts. "You might be asking yourself, what's a connected system?" Interesting slide showing progression of connectivity from first telegraph msg to first transoceanic cables to radio and TV to ICs and the Internet to the 2000 release of .NET.

Talking about the change in business application architecture from mainframe (monolithic, multi-function) to mini (monolithic, multi-function, with separate client). Wrong factoring for large-scale async applications. Refactor multiple functions of monolithic apps into cloud of web services, each offering well-defined independent services that are atomic and don't share context or state. Clouds of composite applications that federate data ("Federated data-- I'm not advocating it, but it's sort of a fact of life") and identity. "I'm not saying that you have to throw out your existing systems and rewrite... but it is something to think about. Think hard about breaking down into atomic services."

Three pillars: highest developer productivity, mission critical abilities, better business decisions. Have to enable both data and process.

Update: SQL Server 2005: integrated with VS and .NET to deliver integrated debugging / development. "No one in the world who wants to ship SQL Server 2005 more than me." Develop and debug code on client, midtier, and back-end from directly within VS. CLR now deeply embedded in SQL Server. Service broker (async queuing and messaging), cache sync, native XML database support. [ed: nothing new here that I can see, and I don't know much about SQL Server 2005]

Update: BizTalk Server 2006. Integrated with SQL and VS 2005, one-click deployment. Big win: simplified setup [ed: that's one of the biggest pains with BizTalk 2003-- it's extremely difficult to set up and get going] "You're going to get a lot of stuff for free in terms of ?? or SQL Server".

Announcing: RFID infrastructure from Microsoft.
[ed: I got it wrong yesterday-- I thought the demo was supposed to be yesterday-- no demo yet, though] Partnership between Symbol, Printronix, and MS. No timeframe; "you should sort of expect it in the 2006 timeframe."

Update: Visual Studio and VS Team System. [ed: this is super cool and is MS' attempt to kick Rational in the butt] Load testing, profiling, test coverage, other QA tools integrated into a "more sophisticated and more scalable" source code control service. "We're super excited about it... A lot of partners already plugging in and extending this".

50-75% code reduction for most scenarios of web dev and smart client dev. Better perf and offline experience for web apps; ClickOnce for smart client apps. CacheSync provides local caching of back-end data under developer control. "It will be difficult to buy a non-64-bit machine in, say, 24 months."

Demo: Brian Keller, PM for Visual Studio. His mom's in the audience! Demoing app showing counts of attendees in various locations via RFID. Now showing graph of number of attendees vs number of proctors in hands-on labs. [ed: cool, but scary; this isn't really anonymous even though they keep saying it is] VS 2005 supports smart tags [ed: great feature!] Large library of "code snippets" "that you don't have to develop or test". Demoing RFID monitoring of a piece of equipment as it moves around.

[ed: I see something that looks like a BattleBot on stage] Sure enough, that's Flessner's missing hardware. It runs on the .NET Compact Framework. The 'bot is delivering a Portable Media Center. "First RFID raffle ever". [ed: I didn't win]

Announcing: $50K Connected Systems Developer Competition. No real details.

Video featuring Xerox application developers. [ed: Borrring.]

Update: Samantha Bee again demoing the SQL Server 2005 Technical Benefits Translator. First benefit (availability): "Downtime is for suckers" [ed: my new email signature!] Second benefit (security): "Hey, hackers, bite me!" Third (scalability): "SQL Server 2005 is like spandex pants." "No matter how big you get, they still fit!"

Update: Flessner's back. Safe synchronous database mirroring or async replication. Online indexing, fine-grained online undo/repairs.

Talking about security now. "I apologize for [Slammer] again today." Showing critical security bulletin count of SQL vs Oracle. 2002: 11 for MS vs 20 for Oracle; 2003: 2 vs 13; 2004: 1 vs 74; 2005: 0 vs 2. [ed: source for this is vendor sites, osvdb, and Secunia]

Key security measures: surface area reduction, enhanced security (native encryption, cert mgmt, password policy enforcement, auditing & authZ). SQL Best Practices Analyzer ([ed: great! the Exchange BPA is a terrific tool].)

Rockin' TPC numbers: $5.38 TPC-C and $54 TPC-H (1 TB), compared to $6.49 and $119 for SQL 2000. Same hardware for SQL 2000, SQL 2005, and Oracle: Oracle is $8.33 TPC-C and $68 TPC-H. [ed: lots of fine print on this slide detailing the exact HW config and results]

Update: Francois Ajenstat, GPM for SQL Server, coming onstage to demo. Cool moving-bars perfmon application showing SQL 2000 vs SQL 2005 on identical HW. 64-bit version of SQL 2005 on Win 2003 x64. [ed: No surprise: much better perf due to much larger cache.] Here comes the BattleBot; it's attacking the network switch that connects the SQL Server 2005 32-bit demo machine. [ed: it's all pyro, no actual metal was bent] Failover worked well, though.

Update: Samantha Bee again with the head of "None of Your Business". "We follow the IBM/Oracle model... You pay to put information into a database, and if you really need it back, you pay to see it again."

Update: Back to Flessner. "Business activity monitoring is to business what BI is to data." Integrates SQL reporting services and "Office Scorecard Accelerator". Integrate, then analyze, then report. Announcement: SQL Server Reporting Services will be available in all SQL 2005 editions.

Demo: Donald Farmer, GPM for SQL Server. Stopwatch demo: Farmer has 8 minutes to do some reporting. Data mining over the output of a conditional split. [ed: Lots of clicking, so I can't follow step by step.] Prediction value of data seems low-- 0.26 or thereabouts. Showing wizard for creating report based on analysis. Flessner: "Kind of ugly, isn't it?" Farmer: "It does look like a report done in 5 minutes, doesn't it? Typical real-world scenario: he asked me to clean his dirty data, I did it in half the estimated time, and he's still not happy." Lots of applause and laughter.

Now showing visual report builder to prettify the report appearance.

Announcing: SQL Server 2005 launches week of November 7. BizTalk 2006 CTP starts now; SQL Server 2005 CTP starts June. Free Standard Edition of SQL Server Standard Edition for all TechEd attendees.

Gartner revenue market share numbers 2004: IBM 34.1%, Oracle 33.7%, Microsoft 20%. "sort of an option to port to Linux; haven't discussed that with Bill lately". IDC's unit share numbers: IBM has 7%, Oracle has 25%, Microsoft has 41%. "We took share" from IBM and Oracle. "How does IBM have the #1 revenue share and the lowest unit share? Let's take a look." Enterprise unit share: 9% IBM, 29% Oracle, 34% Microsoft.

Pricing: base product, 1 CPU, base price for enterprise edition of base product. Oracle $40K, IBM $25K, Microsoft $25K. Upcharges for manageability, availablity, clustering, BI, and multi-core. Final price for dual-core with all options: $232K for Oracle, $330K for IBM on AIX (they don't charge for multi-core on x86/x64).

Announcing: SQL Server Migration Assistant. Automates Oracle-to-SQL Server migration. Claimes to reduce manual effort by over 80%. Contest: most exciting Oracle conversion wins a custom chopper.

Live from TechEd: Exchange 12

I spent most of the day yesterday in a fairly small room that was filled to bursting... with information on Exchange 12. This release is going to rock. I'm immensely enthusiastic about some of the improvements, particularly around unified messaging, message hygeine, and scalability-- all areas where Exchange already has a strong competitive advantage. Of course, it's too early to talk about most of the changes, but Dave Thompson's presentation yesterday covered some of the biggest highlights.

This week I had to choose between going to TechEd and attending Apple's WWDC. The big WWDC news: Apple will start shipping x86 Macintoshes in 2007 next year. Wow.

Update: Edited to change the shipping date; Apple is shipping x86 machines starting next year. Also, I've seen several questions in various places asking whether Apple will allow running Mac OS X on other vendors' hardware. Phil Schiller says "heck no" in this interview.

If you're at TechEd, go by the O'Reilly Media booth and get a free sample of Exchange Cookbook content-- it's a nicely finished booklet that contains a dozen or so recipes that give you a flavor (pardon the expression) of what's in the completed book.

Live from TechEd: FabriKam

I couldn't get in to the "Exchange Today and Tomorrow" session-- by the time I got out of the keynote, which ran 30 minutes long, it was full. I went to John's session on FabriKam instead, and have been posting cookbook scripts in the background.

Thanks to the magic of Verizon Wireless, I'm posting live from Hall A at TechEd, where Steve Ballmer is about to take the stage for his keynote.

Update: Samatha Bee from The Daily Show is the emcee for the opener. She's doing some funny bits skewering Apple, IBM, eBay, and Google.

Update: Ballmer takes the stage and says "we got through the bubble" and we're "in a period of long-term, sustained, and positive growth". [ed: everything here on out is paraphrased unless it's in quotes] More pep and excitement in the industry. "I don't think there's ever been a better, more exciting time to be in the IT industry than right now." Impact of IT in the next 10 years will be bigger than the IT's impact in the preceding 10 years.

10-yr anniversary of Win95 launch, which had the most palpable excitement and energy of any product introduction. The next 10 years will be even more exciting and create even more opportunity for everyone in the room. Theme for my speech today: enabling people to drive business success.

"Each and every one of these scenarios is unfulfilled today": improving cust interaction, personal productivity, unified comms, supply chain optimization, team collab, finding information, spotting trends, engaging in business processes.

Update: Samantha Bee again (disclaimer: I don't know who she is and she's not all that funny). Employees are now repositioned as "free-range information workers". She's slagging users pretty bad. Top 5 most requested requests from information workers: one identity and password, online presence, network access, synchronization ("can't my BlackBerry do this now?"), self-service, rights management (labeled as "5 1/2").

Update: Ballmer takes the stage and introduces Avanade video. Ricardo Arroyo: can easily measure the benefits of self-service infrastructure. Closing line: "It's a great time to be an IT guy".

Ballmer again: Avanade wants to connect people and information. Need the tools to facilitate them delivering that connection. IWs inside Avenade are all IT professionals themselves. "Flywheel of activity": design & build with .NET, deploy and operate with Dynamic Systems Initiative (DSI), act and interact with "New World of Work" stuff. "We think we've come a long way" with .NET. Thanks to the .NET RDs.

Next piece: make sure those apps can be deployed and operated. Want to connect closely to design / build of new applications. Big DSI milestone: shipment of Visual Studio 2005, which will "actually connect the flywheel" where "you build the management instrumentation into every application you build".

New world of work builds on 3 principles: access without compromise, self-service infrastructure, "policy gives IT mgt control". built on presence, identity & rights mgmt, network access-- all implemented as shared infrastructure services. "More and more of what you provide, instead of being point solutions, can be infrastructure that IWs can provision themselves."

Rich comprehensive roadmap based on AD: 86% of large enterprises that use directories use AD, 41% use NT4 domains, 15% use NDS, 9% use eDirectory. "When we first brought AD to market, you were slow to adopt it... Good concept, but go back to work".

Windows R2 ships within the next 12 months with better branch office support, ADFS, and storage virtualization and support. New "Compute Cluster Edition" for grid computing. "We want to be the best" at a long lis of areas, including messaging, directory, and "all applications that are about connecting information workers to information. I think that is incontrovertible." "Investing in new scenarios where, if you will, we still have improvements to make and market share to gain."

"You can know without hesitation, no matter what you're trying to do, around Windows Server, it's the right tool for almost every job.

Update: Exchange 2003 SP2 and Messaging and Security feature Pack for Windows Mobile 5.0. "Some people say Microsoft's a good marketing company, but I have a hard time saying all that." "Direct Push" delivers always-up-to-date connectivity over a persistent IP connection. "The kind that we have not delivered, and RIM has historically. But we have also delivered that with no additional management cost". Policy based control for remote device wipe and PIN management. All included with Exchange. No additional licensing cost.

Exchange 2003 SP2 also ups the 16GB limit for Standard Edition and Small Business Server to 75GB. Install SP2; no other changes necessary.

Mike Hall joins Ballmer on stage. He's toting an X41 ThinkPad Tabler. [ed: I'm going to buy one as fast as I can] 6hr battery life, fingerprint reader. Ballmer took it offstage; now there's a video with a buy wo looks like Ed Brill sitting in the back of the cab calling his kids, his office, checking his email, etc. Guy drops his device as he gets out of the cab. Punk kid finds it. "Last year in Chicago, 85000 cell phones were lost-- that's 4 for every cab in Chicago". Guy's admin gets a call from his house telling her that "Dad lost the phone". She calls IT who says they can remotely wipe the device. Punk kid gives it back to the taxi driver.

Now Hall is demonstrating VoIP with Office Communicator and Exchange 2003 SP2 security features, along with MSN Desktop Search. Longhorn demo: "it's not so much about search, as about how you visualize information". Demoing filtering based on metadata (e.g. author, keywords). [ed note: Better UI than Apple's Spotlight.] Controls for minimum PIN length, inactivity lock time, local and remote wipe. Can define exceptions to wipe settings.

New Symbol MC50 device-- nice-looking device with QWERTY keyboard. Greatly simplified device-side setup user interface. Virtual Earth preview. [ed: this is wicked cool!]

Update: Samantha Bee again with interview on "IT pro-developer mediation techniques". Puppet show. Pretty funny.

Update: Ballmer again. .NET momentum is building; 43% "of all developers" use .NET as primary tool vs 35% using Java (Win32 non-.NET is #3). 90% of MS global accounts are using .NET in some way. Three important products: SQL Server 2005 with embedded .NET runtime; Visual Studio 2005 with .NET 2.0, and BizTalk Server 2006. Ideal for connected systems (instead of J2EE), lifecycle dev (instead of Rational), most demanding DB apps (instead of Oracle or DB2), and "lightweight web app development" (instead of LAMP).

.NET 2.0 is 25%-40% better than .NET 1.1 on Sun's WSTest 1.1, and up to 200% faster than WebSphere.

Update: BJ Holtgrewe showing VS 2005 features. New Outlook add-in support. Demoing integrated CRM and Maestro (new tool for BI, reporting, and scorecards). Links Outlook to SQL 2005 Reporting Services. Access to SharePoint, database, syndicated wbe search, and Outlook data. All synced using SQL Server Express for offline/mobility sync. Customer video: Bank of America and Korn/Ferry. "Everything revolves around your inbox, so why not plug everything into Outlook?" "Now it's all about funneling all of our information into Outlook." "We see Office as a platform."

Update: Ballmer again. Talking about Office 12 XML format. VS2005 delivers System Definition Model (SDM) info; SDM will be consumable by MOM and SMS in "System Center wave 2" coming in future. Bill Anderson from mgmt team doing demo showing remote reimaging and managing Solaris servers. Ballmer pulls two fans from the Sun server and MOM generates an alert. MOM-driven failover to backup Solaris box.

Update: Ballmer again. Security is job #1. Showing vulns YTD for Windows 2003 vs SuSE 9 vs RedHat 3. 1 high/29 other for Windows vs 28/136 and 14/174 for the other two. Similar counts for web server role (33 high/19 other for Win2003, 48/84 for RedHat minimum config, 77/97 for RedHat default config). Patching costs 13-14% less for Windows than Linux. "None of this is designed to tell you that our job is done. None of this is designed to tell you that we think our security job is done".

Announcing Microsoft Update: consolidated update service for consumer, small biz, medium biz, and enterprise. Automatic updates for low end, MBSA 2.0 for medium, Windows Server Update Services and SMS for medium-to-large.

Wrapup: "flywheel" graphic again. "We are committed absolutely to making sure that you have the leading-edge innovations that you need to be successful connecting people and information." Closed by thanking audience and giving out his email address.

[Ed: they handed out RFID tags at check-in, with a promised demo-- but then they didn't do the demo. I bet there's an interesting story there!]

I'd previously written about MS' support position on VERITAS Storage Foundation for Exchange. Sometime between then and now, MS released a KB article (895847) that sets out their support policy for hardware and software replication solutions. It outlines support boundaries for three important categories: asynchronous software replication, synchronous hardware replication in a geographically dispersed cluster, and sync hardware replication not in a dispersed cluster. Well worth a read if you're interested in this category of products.

I'm delighted to announce that the Exchange Server Cookbook (which I cowrote with Missy Koslosky, Devin Ganger, and Tom Meunier) is now available from Amazon! It should ship sometime next month... and yes, that is a baboon on the cover.

"Does Entourage use RPC-over-HTTP?" I've run across this question several times in the public newsgroups, on mailing lists, and in direct conversation. Now Mike Wendland's asking, so I figured I'd write a long answer and just refer to it in the future.

In the beginning, there was MAPI, the Mail Application Programming Interface. Microsoft Mail (remember that?) used MAPI, as did the long-forgotten Windows Messaging and Exchange Client applications. When the Outlook team began working on Outlook, it used MAPI also. MAPI communication between client and server are actually implemented using remote procedure calls (RPCs) that travel over the Windows RPC subsystem, which uses TCP ports 135 and 443 and UDP ports 137 and 139. Because early versions of Windows had a number of RPC-related security vulnerabilities, admins quickly learned to block these ports from the Internet, meaning that you had to dial in or establish a VPN session to get your mail with Outlook from outside the corporate network.

In the meantime, lots of other applications started tunneling their data over the standard HTTP port, TCP port 80. This has the advantage (for users) of letting these applications run without special permissions or changes to the firewall. With Outlook 2003, Microsoft implemented RPC-over-HTTP tunneling so that you can establish a native Outlook MAPI session from outside the firewall without using the default RPC ports. This is good from a security and convenience standpoint. Why security? Think about it: if you establish a VPN session, you're trusting the remote machine to be clean, and you're trusting the remote user not to do anything malicious on your network. With RPC-over-HTTP, all the remote user can do is get mail, so you don't have to worry that they're going to screw up anything else.

Entourage for Mac OS X doesn't use RPC-over-HTTP. Instead, it uses WebDAV, an XML-based technology that travels over HTTP connections. It has nothing to do with MAPI or with RPCs, and it works with Exchange 2000 and Exchange Server 2003-- RPC-over-HTTP requires Exchange Server 2003 running on Windows Server 2003.

Both technologies have the same effect: an outside user can establish a connection to the Exchange server using HTTP (which had better be protected with SSL) to talk to the server.

Now, on to Mike's specific question: Apple Mail 2 supports Exchange accounts using WebDAV, so if your employer supports WebDAV and is running Exchange 2000 or later, you should be good to go. You'll probably need to enter the same server name that you use for Outlook Web Access to get Mail to find the right server. Good luck!

Michael Murphy, a TechNet presenter for Microsoft, has been reading Secure Messaging with Microsoft Exchange Server 2003. So far, I like his approach to reviewing the book; he's posted an article that describes his reaction to the first two chapters, including an explanation of what's in them. One of the best parts of writing a security-focused book was that I had the luxury of including background material to help Exchange admins get the right vocabulary and mindset to talk security with real security folks. This makes my book very different from other Exchange books, since they normally have to cover so many topics that they can't provide much depth in any one area. In fact, the first five chapters are broad enough to be of interest to admins running any messaging or collaboration software on Windows-- so all you Notes folks who secretly read my blog, go get a copy :)

Congratulations to the Microsoft Office Communicator team! They just RTM'd their product. If you haven't already tried it, grab the evaluation version and give it a spin.

I was floored to hear about this, but maybe that just shows I need to get out more. Turns out that you can flip a metabase flag to get some additional control over SMTP relaying. By default, if you require authentication and list one or more allowed IP addresses, both of those restrictions apply. However, you can set the SMTPIPRestrictionFlag value to use the logical-OR of those two factors, so that you can relay if you authenticate or if you're coming from an allowed IP address. Mad props to Konstantin Ryvkin for admitting to this and to Devin for blogging it.

Brilliant move by Singlefin

Singlefin announced today that they're giving away their hosted spam filtering service, free, to organizations with 10 or fewer mailboxes. The press release (which isn't on their site yet) quotes their CEO as saying "Of course, we know that small companies can become large companies and if we extend this generous offer now while they are still growing, we are confident it will translate into brand loyalty and solid customer referrals down the road". Here's the most interesting part:

Any organization anywhere in the world is eligible to take advantage of this protection without the need for cumbersome software or expensive hardware. Singlefin solutions are 100% managed or “hosted” meaning protection for customer networks is all enabled through network redirects. One simple change to a customer’s DNS enables 100% protection from spam, viruses and other malware via Singlefin’s Enterprise Email Filter. The Web and Instant Message Filters are enabled through similar network changes.

This is a terrific move on Singlefin's part; the incremental cost for them to host these small organizations is low, but the brand-building value is very high. There are so many anti-spam solutions on the market that it's hard for vendors to differentiate themselves, but this should definitely help build awareness of Singlefin.

Fabrikam goes live

My partners at 3sharp have been involved in a huge project over the last few months: building credible enterprise-level sample applications using Office as a development platform. Behold: Fabrikam, a Microsoft Office System Solutions Learning Platform! Hats off to Peter, John, Anup, Kevin, David, Chris, Greg, and Phil.

Now this is pretty slick: the Visio 2003 Connector for MBSA turns an MBSA scan into a color-coded Visio network diagram. (Actually, you have to create the network diagram first, but that's trivial with Visio 2003 Professional). What a great add-on to MBSA's built-in scanning functionality. Get it here.

Greg Hughes has a great dissection of his recent search for a replacement for his BlackBerry. In the end, he went back to the old familiar BlackBerry, but not until after he tried the Audiovox 5600, the SX66/XV6600, the Treo 650, and the BlackBerry 7100 series. He started with a BlackBerry device and tried the others to see how they compared as mobile email devices and as phones. Perhaps unsurprisingly, he ended up with his same preferred device. It's fascinating to see how big a role inertia plays in PDA/smartphone selection, compared to the larger mobile phone market. Of course, device cost (and the cost of installed software) make a huge difference. I considered the BlackBerry 7100s, but since I can't run any of my stable of useful Palm apps, that wasn't going to happen. (I still have to post a longer review of the XV6600, besides my initial thoughts).

Huge news from the Real-Time Communications product team at Microsoft. First, we'll be getting a Live Communications Server client for Windows Mobile devices sometime in the second half of this year. I've been happy using the MSN Messenger client that comes with the Windows Mobile-powered Audiovox XV6600, but being able to communicate with other corporate LCS users will be a huge win-- right now, if I want to IM with someone inside Microsoft's perimeter, I have to dig out the ol' laptop. MS hasn't yet announced pricing or functionality; I think it's safe to assume that the Windows Mobile client will have a subset of Office Communicator's functionality, in the same way that Pocket Outlook is a subset of desktop Outlook.

The other news astonished me: Research In Motion, producers of the BlackBerry line, have signed an agreement with MS to produce a Live Communications Server client for the BlackBerry platform. This is terrific news for the LCS team, and great news for BlackBerry users who want to combine their existing mobile e-mail service with IM and presence. Of course, it raises the bar for the Windows Mobile team, who now have to contend with the loss of what would otherwise have been a significant capability advantage. With Magneto around the corner, though, I bet they have some other tricks up their sleeve.

Update: looks like RIM's been busy; yesterday they also announced an agreement with IBM Lotus to provide a native Sametime client for BlackBerry. The plot thickens...

Statistically improbable? Sez you

Amazon has a new feature with which they do various kinds of analysis on (many of) the books in their catalog. One of these analyses is the "statistically improbably phrase" test; this shows phrases for a given book that appear much more often in one book than in the whole corpus of books in their Search Inside program. For my book, here are the SIPs Amazon found:

relaying configuration, antivirus product vendors, relaying settings, archive sink, htr files, perimeter scanner, constrained delegation, check pox, default response rule, mailbox database, key archival, attachment access, perimeter network, message tracking, mailbox administrators, messaging security, retention categories, smart card enrollment station, machine certificates, delegate access, dialog hox, segmentation value, privilege escalation, inbound mail, event sink

Note "check pox" and "dialog hox"; those are probably my favorites. I can't wait to see what the list for the Cookbook looks like!

Ongoing discussion on MS vs IBM

There's a fascinating thread of comments over at Ed Brill's blog on this post. Ed and Alan Lepofsky, along with various other luminaries in the Notes communities, have been having a generally professional discussion with Cliff Reeves of Microsoft. David Madison of Microsoft may have gotten the last word, though, as Ed has promised to turn off comments on the post. It's his blog, and so of course it's his right to do so, but I'm sorry to see it, since I think the exchange has been very illuminating-- particularly since Ed has (quite fairly) criticized Microsoft in the past for not taking part in strategy debates at various public conferences.

If Cliff, David, or any of the other participants in the thread who don't have their own blogs want to carry this on, I'll be happy to guest-post their comments here.

Another week, another event! This time, I was in DC, where I had a great group of attendees. The highlight was probably during my demo of Microsoft Office Communicator, when I accidentally called Devin. I'd forgotten that the SIP-to-PSTN gateway was active, and I right-clicked his name and used the "Call" context menu to show that his contact information was there, prefilled from my personal Contacts folder. I was quite surprised when Devin's phone started ringing in my computer speakers (and so was he), but we had a short call and the crowd loved it. It's always great to surprise people like that-- I think I may work it into my demo script as a permanent item. Live Communications Server 2005's voice and telephony integration is pretty compelling, and I'm glad that came out in the demo.

Cool new Exchange tool: exmon

Microsoft has established a good pattern: they've been taking tools that they use internally, polishing them up, and releasing them as free tools through their web release (WR) program. This flow most recently brought us ExBPA 2.0, and now a new tool joins the family: the Exchange User Monitor, or ExMon. The cool thing (as Chris points out on the Exchange team blog) is that ExMon can both aggregate data and show you user-specific performance data. If you have a user or two who consistently complain about performance, ExMon gives you a quantitative tool to ID and fix the underlying problem. Check it out.

Forbes pimp-slaps Lotus

| 1 TrackBack

Wow, that's gotta hurt. This article, by Daniel Lyons, effectively claims that the air is going out of the Notes balloon, citing market share and revenue data from Gartner, IDC, Ferris, Meta, Radicati, and ITRG. It'll be interesting to see how IBM/Lotus respond to the article; with their 2004 numbers not yet released, the public data to refute some of Lyons' arguments may not be available yet.

So, yesterday I was in Manhattan, again. This time it was to attend IBM's "Microsoft Exchange Alternatives" seminar, held at IBM's building on Madison Avenue. I had to get up at 0400 to drive to Detroit and catch the first flight in to LGA; despite that, the flight was delayed. (That gave me time to finish a paper I've been working on, which I emailed from the back of the taxi on the way to IBM. Good news: I can send email from taxicabs. Bad news: sometimes I have to.) As Ed said, the seminar was well-attended, with about 20 folks in the room from a variety of customers.

There were four presenters: Ed did his overview of IBM's collab strategy; Jennifer Meade from ThroughBox IT did a somewhat lackluster review of three customer case studies, Henry Bestritsky from Binary Tree talked about their Common Migration Tool (CMT) and how it can be used to move from Exchange to Notes, and Brendan Crotty wrapped the morning up with a solid demo of the Domino Access for Microsoft Outlook (DAMO) tool.

Overall, I thought it was a good first effort. As I pointed out to Ed when I met him afterwards, there wasn't any convincing discussion about quantified business value. Interestingly, IBM had several Linux sales folks in the audience, and a common theme underlying Ed and Brendan's presentations was that IBM is promoting server OS choice. I'll save my analysis of that meme for another day :) I don't think the seminar content accurately reflected Microsoft's current collab strategy and why IBM thinks theirs is better. In fairness, that's not what this event was intended to cover. IBM did a good job of positively conveying their message, though, and I think mixing in the partners was a good touch.

How does this compare to our "Optimizing Collaboration and Communications" event? We have more demos, including an extended "day in the life" demo that lets me show how I actually use Microsoft's tools to get my daily work done. We also have a lot more quantitative information about the business benefits of extending Notes/Domino infrastructures with MS' tools. We'll see what Ed thinks when he attends our Chicago event.

Unlike Ed, I made it out of LGA before the weather turned bad :)

Getting on the bus well after it's left the station, Symbian announced today that they're licensing the Exchange ActiveSync protocol. With more than 25 million Symbian OS devices worldwide, this is a big announcement for both sides, although no firm timeline was disclosed. Symbian's already got a good mobile connectivity story; this makes it better while simultaneously highlighting Exchange 2003's advantages as a wireless messaging platform.

After seeing Ed Brill mention IBM's "Microsoft Alternatives" session in Manhattan next week, I decided to sign up for it.. or at least to attempt to. There's no online registration, so I sent mail to the listed address asking to register. No response. So, I tried again just now, and added a voicemail for good measure. Hopefully that will do the trick; it sounds like an interesting seminar.

Update: got the call yesterday; I'm confirmed, and looking forward to it. I don't know much about BinaryTree and their migration tools, so this should be a good learning opportunity.

This week I'm on the road in Boston and New York City, presenting the second and third iterations of the Microsoft "Optimizing Collaborations and Communications" roadshow that I wrote about last week. Yesterday's event was well attended, and the attendees asked some tough questions about Microsoft's C&C strategy. However, the session evaluation results indicate that they liked the answers they were hearing. MS' message-- that you can augment Notes/Domino installations by adding technologies that drive better business value-- seems to be resonating with these folks. Today, I go to Manhattan via the Acela (which I'll blog about later, or maybe during), then tomorrow it's St Paddy's Day in the Big Apple. I didn't bring anything green, so I need to do some shopping lest I face the wrath of the Irish.

MS buys Groove, gets new CTO

The AP is reporting that Microsoft is buying Groove, which I think is great news. Groove adds some critical capacity to Office System and SharePoint. Lots of other folks will be analyzing this in more detail. The most interesting detail to me is that the AP's report says that Ray Ozzie is going to be the new Microsoft chief technology officer. That certainly raises some very interesting possibilities.

Communications and presence cost

I'm supposed to be working on something else, but I couldn't resist the urge to answer Ed's post on the Microsoft Office Communicator launch, which in turn is in response to this Microsoft Monitor piece (which, by the way, contains a couple of errors).

First, let's consider public IM connectivity. Right now, if you want to interoperate with (say) AOL, you have to install AIM or an AIM-compatible client on your desktops... at which point you lose the security and compliance capabilities that Live Communications Server and Sametime/Workplace both offer. On the other hand, if you have a genuine business need for public IM connectivity, you can use the PIC feature of Live Communications Server to interoperate (selectively) with MSN Messenger, AIM, and Yahoo! Messenger users and still maintain both security and compliance. It's true that PIC is currently priced as a subscription. Ask yourself this: why did AOL suddenly decide to allow a competitor to interoperate? Normally their MO is to break interoperating clients as soon as they can get away with it. Are they getting a cut of the revenue? I don't know, but it certainly wouldn't surprise me.

Next, let's take Ed's point that the Microsoft collaboration platform has more than one piece (he actually uses the phrase "jigsaw puzzle"). Back in the day, Microsoft's claim was simple: Exchange does it all. They have since repented of that, instead delivering a broad suite of collaboration and communication tools that you can mix and match. You can deploy them together or separately. If you don't need, e.g., SharePoint Portal Server, fine-- don't buy it. There's significant stand-alone value in each of the components. In fact, I'm seeing a groundswell of interest in Live Meeting and Live Communication Server deployment among customers that aren't currently using Exchange. Why? Neither of those products require Exchange, and both add measurable business value.

Now, it's also true that the more pieces of the MS platform you deploy, the more capability you get. This is no different from Workplace, except that many of Microsoft's platform components are more mature than their Workplace equivalents. It's a little disingenuous of Microsoft Monitor to claim that you have to buy all of the features; that's like saying that I have to buy the Hemi when I buy a Dodge Magnum (well, OK, I would have to buy the Hemi, but that's another blog post).

About those Microsoft Monitor article mistakes: I count two simple typos ("Instanbul" and the confusion between SharePoint Portal and Windows SharePoint Services) and a misunderstanding of the Outlook/LCS connection. You can deploy Outlook 2003 without Exchange 2003 (in fact, you can even use Outlook 2003 against Notes/Domino servers, using either MS' or IBM's connectors). Every Exchange 2003 CAL includes an Outlook license, but Outlook is also licensable separately.

So, you might have seen Gary or Ed mention this, but now that it's underway I have time to talk about it too. 3sharp is presenting a 10-city roadshow called "Optimizing Communication and Collaboration with Microsoft Technologies". The thrust behind the roadshow is simple: you can get a lot of mileage from Microsoft's investment in communications and collaboration technologies by deploying them in parallel with-- not necessarily as a replacement for-- whatever you're currently using. The structure of the events is simple: if you're a developer, you go to John's excellent class on how to extend Notes apps by having them produce, or consume, data from .NET web services; if you're a technical decision maker, you come hear the Burton Group's forecast on market dynamics in the C&C space, then I get to explain the pieces of MS' collaboration strategy, with copious use of demos.

Our first event in Dallas this week went really well. My content was well-received; it was obvious to the attendees that we're not suggesting they rip-and-replace their existing infrastructures (well, maybe if you're using OCS). Instead, we're making a solid case for extending their business systems with Microsoft's collaboration and communications platform. Next stop: Waltham! (Personal to Ed Brill: the Chicago show got moved to 4/21, so please adjust your calendar!)

In this month's Windows IT Pro, I wrote a buyer's guide article on Exchange recovery tools. This just in from an admin who works for the city government of a large city in Virginia:

Thanks for putting this article together. I just wanted to let you know we are just about to implement a NetApp solution for Exchange 2003 and without NetApp's Single Mailbox Recovery product, not mentioned as needed in this article, it is impossible to Backup and Recover Individual Mailboxes, Recover Individual Items or Search and Query for Items to be Recovered. I wanted to let you know because their software is expensive and this product is an extra cost.

Yikes! My apologies for that. When I do a buyers' guide, I write the article itself that accompanies the guide, and I work with the magazine's editors to come up with a list of criteria, plus a list of products that meet those criteria. In this case, the selection criteria included the ability to do brick-level backups, the ability to search and query, and the ability to recover individual items. We don't usually ask vendors to list out all the products, submodules, agents, or other components that have to be installed to meet the criteria. For example, for backup solutions we don't ask whether there's a separate Exchange agent or not. Mail like this makes me think that maybe we should, though, because it's frustrating to buy what you think is a complete solution, only to find out that you have to lay out even more money to get the whole package.

Adzilla: worse than Autolink?

| 1 Comment

Lots of discussion about Autolink, which is good. So far, though, I haven't seen very much discussion around Adzilla. Their white paper for service providers describes their services for stripping banner ads (and other ad-related content) and letting the ISP insert its own ads. Yikes. I can't imagine that content providers are going to be too happy about that. Imagine going to CNN.com and seeing locally-inserted ads from your cable modem provider.

Back in November, I wrote about a problem with Entourage and Exchange transaction logs-- sending a message that was larger than the Exchange global message size limit would cause Entourage to resubmit the message each time it tried to send mail, and this would lead to a flood of transaction log files. There's now a server-side hotfix for this problem: MS KB 889525 (An e-mail message stays in the Outbox and the Exchange Server 2003 transaction log files grow when an Entourage user tries to send a message that exceeds the size limit in Global Settings).

Dang, I never thought I'd see this happen: the Microsoft Security Response Center (MSRC) has a blog. Pretty cool, and definitely good news for MS' ongoing attempts to broaden the degree of security communications.

Adomo's DEMO appearance

The Weblogs Inc folks covered Adomo's unveiling here (including a picture that's just begging for a caption). I suggested that the Adomo folks contact Robert Scoble before the show; their product is a natural for discussion on his blog, since it's a) MS-centric b) built with .NET and c) very, very cool. I don't know if they did, and now he's offline. However, he gave them (and everyone else) the same advice.

Now this is a surprise, and a pleasant one. Nokia announced that they're licensing Exchange ActiveSync for their Series 60 and Series 80-based phones. This is excellent news for the Exchange team; clearly their effort to get EAS more widely deployed is bearing fruit. (Nokia also licensed Flash.. just what I want on my phone, not.) Interestingly, the WIndows Mobile team has been busy at 3GSM World too; they announced that Flextronics, a large original device manufacturer (ODM), will be building "Peabody", a new, lower-cost, reference platform for Windows Mobile devices. It should be interesting to see how this plays out.

Update: it turns out that Nokia is also licensing a bunch of Windows Media technologies, including Windows Media DRM and the Media Transfer Protocol. Take that, Apple and your not-yet-shipping Motorola iTunes phone!

Today a startup named Adomo is launching their new product, Adomo Voice Messaging. They briefed me on it a month or so ago, and I've been eagerly waiting for today (the start of the DEMO 2005 conference) for the embargo to lift so I could talk about it. What they're essentially trying to do is build a comprehensive unified messaging (UM) solution that uses Exchange not just as a message store (like Cisco's Unity) but as the communications backbone. I think they're on the right track, taking what I privately label the CommVault approach: they're leveraging Exchange as much as possible, instead of building a product and trying to make it work, not very well, with multiple back ends.

The Adomo system has three parts: an appliance (running their own *NIX variant, I forget which-- maybe FreeBSD?) that handles up to 36 ports from the PBX, a connector that ties the appliance to the Exchange message store, and a really slick speech-based auto-attendant. You can chain appliances to use more than 36 ports, and Adomo's literature shows smaller 12- and 24-port appliances being used in remote offices. Adomo claims that a single 36-port appliance is enough to serve between 1800 and 3600 users, depending on usage; they're purposefully targeting organizations with more than 500 users. The appliance compresses incoming messages using the GSM codec (which means that you can listen to messages on pretty much any Windows, Mac OS X, or Linux machine-- the codec is ubiquitous, unlike Cisco's ACELP implementation) and sends them to the Exchange connector.

The Exchange connector is where the action happens: incoming messages are directed to the user's mailbox, where they appear as regular email messages. This is particularly important because it allows you to deploy their solution without any desktop changes: there are no required plugins or Outlook bits to add, and VM attachments are available on any device that can handle email attachments (including handhelds, OWA, and so on). Messages are delivered using an Exchange form that includes buttons that let you play your VM on your phone, call the sender, and take other appropriate actions; Adomo has promised tighter integration with Outlook for future versions, but the existing integration is pretty darn good.

One of Adomo's big selling points is that you don't have to touch the Exchange server or Active Directory to implement their product. You only need one connector per Exchange organization. The connector doesn't have to be on an Exchange server, and there are no AD schema changes required. You provision user accounts for voicemail by specifying the associated phone numbers, so there's no need for a separate user management tool. Adomo hasn't said which AD attributes they use, but their literature does claim that you can do all the provisioning through AD Users and Computers or through scripts.

Messages appear with Caller ID data, and the connector is smart enough to match that data against the user's Contacts folder so that messages appear with the correct sender information. That makes it easy to prioritize and handle VMs (either manually or with rules) in the same way you would any other email. In addition to the ubiquitous "message waiting" light, the connector can send SMS messages to a mobile phone or alerts (including the Caller ID number in the subject line) to BlackBerry or other non-audio-capable devices.

It's hard to do the auto-attendant justice in this form, but I'll try. When you call in, the attendant answers and plays its recorded greeting. You can speak a name at any time, and their speech recognizer will attempt to find the name in the GAL (with conflict resolution, so it can ask the user which John Smith ("John Smith in Sales, or John Smith in Engineering?") to connect to based on OU, domain, or group membership. This in itself is very cool; the cooler part is that the attendant has access to a wealth of user-specific data, including your schedule and presence data from LCS. Imagine being able to set a rule that says "if my wife calls on her cell phone, IM me to tell me; otherwise, dump all incoming calls to voicemail". From a user perspective, imagine calling a contact and having the attendant tell you "Jane's in a meeting until 3pm Central; do you want me to notify her that you're calling?" (based, of course, on Jane's decision to trust you with that information as a contact in her Contacts folder). There are almost limitless possibilities for future expansion here, particularly given that the Adomo solution can be used with SIP products (conveniently including LCS 2005).

Of course, given Adomo's target market focus, their solution won't work for everyone. First, it requires Exchange 2003. Second, they haven't released pricing data (at least to me) but since their focus is on 500-plus seat organizations, it likely won't be cheap. (One interesting note: Adomo's pitch talks about the benefits of their product for organizations that sell hosted Exchange services-- this could potentially be a nice revenue sweetener for hosting companies). However, in terms of functionality, their nearest competitor is the Wildfire service, which (last I checked) was $70-150/month/user-- so they've definitely got some pricing maneuvering room. I think their product will be successful, but I'm sure it will be interesting to see how Microsoft's announced UM support in Exchange 12 plays against Adomo's solution, which now has a year or two to get traction before E12 ships.

Surprise! MS buying Sybari

Interesting news: Microsoft is buying Sybari, makers of the outstanding Antigen line of anti-virus products (and some pretty good anti-spam tools, too). Interestingly, there are Antigen versions for Exchange, Live Communications Server, SharePoint, and even Domino; I expect that the breadth of their product line made them a more appealing target than some of their peers. It'll be interesting to see how this acquisition works in conjunction with MS' buy of GeCAD's RAV technology. However, it will be even more interesting to see what effect this announcement has on the second-tier AV vendors-- companies like Command and Panda have got to be sweating now. (Not to mention that many organizations who have stuck with products they don't really like will now use this as an excuse to move!)

I could snark about this filter update taking so long, but at least Microsoft's making the IMF freely available-- some messaging systems have no integrated spam filtering. Anyway, there's now a filter update for the IMF available here.

Ordinarily I wouldn't post this announcement here, but I'm going to break tradition and do so because I'm one of the conference co-chairs. As such, I have to help find speakers, so I want this call for papers to go out far and wide.

Windows IT Pro is now accepting session proposals for the Oct-Nov. 2005 Windows Connections conference. We're heading to San Diego October 30 to November 2, 2005, for the premier Windows technical conference, and we'd like to hear from you!

If you're interested in speaking on Exchange-related topics at the show, send your abstracts to
paul@robichaux.net by February 18. We want proposals for regular 75-minute sessions, as well as 1/2 day and full day pre-conference and post-conference sessions.

Note that we have a limited number of speaking slots, and all participants must be able to present a minimum of three 75-minute sessions. There are three basic requirements:

  • Send a minimum of 3 session proposals (4 or 5 is ideal for discussion purposes)
  • Include a biographical statement with your session proposals
  • Include any additional pre- or post-con session proposals, if applicable

Please adhere to the February 18 deadline as we need to make speaker and session selections right away. (We plan to have a conference brochure ready to distribute at TechEd in June.)

Here's a very cool trick: Glen Scales wrote a script that finds all of your mailbox and public folder stores, then queries their servers' event logs to find event ID 1221s indicating how much white space is available. This is a slick solution to the vexing problem of monitoring how much white space is lurking in your databases.

Rui J.M. Silva posted a cool script on his blog for migrating distribution list objects between Exchange organizations. The script is meant to be run against an Exchange 5.5 directory, from which it extracts the DLs with ldifde. It then extracts the 5.5 directory with csvde, matches the display and account names, and outputs a file that can imported using ldifde. The last step actually imports the DLs as universal distribution groups. If you want the DLs to be populated, you must already be using the ADC so that user accounts are synchronized, but the script is still a nice bit of work.

MS releases beta anti-spyware app

As has been widely reported elsewhere, MS has released the public beta of their new anti-spyware tool. Go get it and try it out; I've been running a test build for a while now and have been very impressed with it.

Why I run the MSN toolbar

| 3 Comments

I've been using the Google toolbar for a long time, but no more. Now I'm using the MSN toolbar instead. Why? Six simple reasons, five of which are security-related:

  1. The MSN toolbar doesn't index the browser cache or history file. That means that it won't find cached information like credit card or online banking statements.
  2. Every user on a multi-user machine has a separate set of index processes and files.
  3. The MSN toolbar never sends any data back to Microsoft. Google's toolbar, of course, sends tons of data back to Google, although they're up-front about it.
  4. Index files are obfuscated, raising the bar for casual snoopers (of course, snooping requires admin privileges in the first place :)
  5. MSN never automatically downloads updates. You can ask it to do so, but you don't have to.
  6. It searches Outlook.

50% off Trend ScanMail

This is a pretty good deal: 50% off new licenses of Trend's ScanMail suite if you're migrating from Exchange 5.5 to Exchange 2003. You have to have more than 1,000 seats, and you have to have proof of migration (evidenced by a current SA license or Exchange 2003 CALs purchased after 6/15/04), and the offer is only good until 12/31/04.

When "it's the pits" is actually GOOD

Microsoft today released a hotfix for the Windows 2003 SMTP stack that provides tarpitting for SMTP. (If you don't already know what tarpitting is, check this explanation). The idea is that you install software that intentionally slows down SMTP throughput for bogus requests. This helps make it uneconomical for spammers to ply their trade. The hotfix requires you to install a package and set a registry key, then you're done. Highly recommended.

Word of the day

| 1 Comment

What do you call a hotfix that doesn't actually fix the problem it's supposed to cure?

I vote for notfix, but I welcome your suggestions. The best suggestion posted as a comment here by December 15th wins... uh... something cool. Yeah, that's it-- your choice of a signed copy of one of my books or a $25 donation to the charity of your choice. Get those creative juices flowing.

Getting started with Workplace

| 1 Comment

So, here's a question for Ed and any other Lotus-Knowledgeable readers out there. What's the best way to start learning about Workplace Messaging? So far I've learned some peripheral facts, like that it has outrageous system requirements (quad 2GHz procs + 2 GB of RAM), that it's licensed per-processor (so you need 4 server licenses for that 4-proc machine), and that every initial license includes 12 months of maintenance. However, I haven't found a clear, comprehensive source of getting-started information, apart from this tutorial. That's probably just because I don't know where on IBM's gargantuan web site to look, hence this post. If you do know, please share.

Update: I just spoke to a friendly IBM sales rep who made it very clear that Workplace products are not licensed per-server or per-CPU, but per-user. My earlier post was based on something I saw at vowe.net. Caveat lector.

Motorola embraces EAS

Now this is interesting: Motorola has announced that they've licensed Exchange ActiveSync and will start supporting it when they release the A780 phone next year. That means that Exchange ActiveSync will be available on a Linux-based device, along with the PalmOS-based Treo 650. While this might seem like the kind of thing to give the Windows Mobile apoplexy, Motorola sees (and has labeled) the A780 as a midtier device that doesn't compete with the feature-rich(er) Windows Mobile devices now on the market. EAS will be integrated with Motorola's propietary MOTOSYNC protocol; it's too early for me to tell what form the integration might take.

I'm working on an article on Exchange ActiveSync for the magazine. Unfortunately, I don't have it working for my device yet-- John's iPaq 6315 works on 3sharp's server, but something is funny with my server here at home, and I'm going to be troubleshooting it this week. A couple of resources that look useful: this extremely detailed TechNet webcast and Chris De Herrera's troubleshooting guide (which mostly covers "regular" ActiveSync) on CEWindows.net.

Comments re-enabled

I have re-enabled comments, with the added requirement that you use TypeKey (which, fortunately, is free). As soon as I can get MT-Blacklist to work properly, I'll enable unregistered comments, but for now you'll need to sign in before commenting. Sorry about the inconvenience.

The publisher was kind enough to send me a review copy of Tony Redmond's latest book, Tony Redmond's Microsoft Exchange Server 2003 : with SP1. I haven't had a chance to even open it yet, but I can say this: at $37.77 from Amazon, and at 4.3 lbs, it comes in at a very respectable US$8.78/lb. By way of comparison, Stanek's Exchange Server 2003 Administrator's Pocket Companion costs $14.13/lb, and my security book weighs in at $14.34/lb. Tthat's just because it's packed full of so much information. Or something.

Jeremy Kelly is reporting an unusual interaction between Entourage and Exchange 2003. The symptom: transaction log bloat. The problem seems to occur when an Entourage client tries to submit a message that's too large for the maximum message size limit set on that user's mailbox store. Instead of reporting the error (and not resubmitting the message), Entourage happily tries to send the message each time it connects. If the message is large enough, and if this goes on long enough, the server will eventually run out of log space. Jeremy recommends a temporary fix of turning off httpdav, removing the offending message from the client, and re-enabling httpdav; no word yet on an ETA for a better fix.

I just ordered an AT&T Audiovox SMT5600, so I went digging for development information. Then I found this page, which will keep me in reading material until at least this time next year. Wow. If you're at all interested in the .NET Compact Framework, this would be a great place to start.

Two Windows Mobile webcasts

Next week is Windows Mobile webcast week. There are two webcasts of particular interest for Exchange 2003 administrators: one on best practices for Windows Mobile deployments, and one for Windows Mobile/Exchange troubleshooting.

New Live Communications Server blog

Tom Laciano has a new blog focused on Live Communications Server. Based on what he's posted so far, this will be one to watch. For example, this post on using certificates for mutual TLS authentication in LCS 2003 is pure technical gold. I plan to follow it regularly.

What do you get when you combine Exchange Server 2003, KVS Enterprise Vault, KVS Discovey Accelerator, and SharePoint?

Microsoft has what's probably the largest deployment of OMA and Exchange ActiveSync. What have they learned about how to scale and provision these services?

Joe has a number of really nifty free tools on his site, including the world-famous ADFind. However, I just stumbled across a new tool he wrote while working on the Exchange chapter of the Windows Server 2003 Cookbook (forthcoming from O'Reilly).

Now <em>this</em> is interesting: Microsoft and Cisco are hooking up and exchanging some network-protection DNA. Microsoft mentioned their Network Access Protection (NAP, a somewhat unfortunate acronym) at their worldwide partner conference in July; now MS is pushing the release of NAP back to Longhorn Server in order to integrate support for Cisco's Network Access Control (NAC). This interview with Windows GM Bob Kelly says that MS and Cisco will work to ensure that NAP and NAC are fully interoperable, which is great news; since NAC is already shipping, it would have been counterproductive for MS to complete their own, incompatible, solution and make customers choose between them.

Best practices: we're not kidding

vpc.png

BugTraq RSS feed

It's hard to keep track of who's blogging, particularly as automated tools that make RSS feeds for automated systems proliferate. Personally, I want to see as much data in RSS form as possible, especially for fast-changing or noisy systems like, oh, mailing lists.

MS releases SP1 for Mac Office 2004

Excellent! Microsoft has released Service Pack 1 for Office 2004. I haven't found a list of fixes yet, and I'm away from my Mac so I can't download it to try it out. It's supposed to be available via the Microsoft AutoUpdate tool or directly from the MS Mac page.

This afternoon I had a call with the PR folks from PalmOne to get their take on the Exchange ActiveSync for Treo announcement. As is to be expected, they were mum on the details most people really want. The new devices, which they didn't explicitly name, are being released "this fall-- before the end of the year". When I asked if they were prepared to say which carriers would offer them, all I got was a chuckle.

This is big and rich: Microsoft announced today that they've licensed the Exchange ActiveSync protocol to palmOne for use in their new, officially-unannounced line of Treo smartphones (including the 650). I want one.

A welcome new spam trend?

Is this the start of a new trend? Vioxx Recall Leads to Worldwide Spam Reduction.

Death knell for Sender ID?

Now, this is interesting: the IETF Sender ID working group is apparently defunct. This is more or less the equivalent of that milestone of farce comedies, the divorce due to irreconcilable differences.

MS announces Data Protection Server

This Computerworld story (and the related MS press release) announce the arrival of a new Windows product: the Data Protection Server (DPS). DPS is basically a distributed tool that puts agents on the file servers you want to protect; the agents then run scheduled disk-to-disk backups. Depending on how this is implemented, this might be a significant improvement over the kind of ad-hoc disk-to-disk backup schemes most small and medium organizations use. DPS combines replication and point-in-time copies, which places it squarely into competition with products from Legato and Veritas (among others).

This is very, very cool: the Exchange Best Practices Analyzer is a new tool from Microsoft that checks your Exchange infrastructure for good design practices. To be more specific, the tool investigates various parameters (including some from AD, a few perfmon counters, the IIS metabase, and your DNS) to see how well your operational configuration conforms to generally accepted best practices.

Plaxo: I told you so?

| 2 Comments | 3 TrackBacks

Thanks to alert cow-orker Tom Meunier, we see that my earlier prediction about Plaxo has indeed come true, sort of.

Another SURBL-compatible Exchange filter

The newest version of XWall supports SURBL.

Controlling Always-Up-To-Date timing

I've been fiddling with Exchange ActiveSync lately, and I'm actually pretty impressed with it-- it's a neat feature. If you're not familiar with it, it basically sends periodic notifications of new mail to your Windows Mobile device; when the device receives the AUTD message, it wakes up and pulls new messages from your Exchange server. This gives you more-or-less continuous access to the contents of your mailbox.

At long last, Microsoft's released a document that describes what you can do to mitigate threats to your network from Windows 98 and Windows NT 4.0 machines: the Windows NT 4.0 and Windows 98 Threat Mitigation Guide.

Another Exchange SURBL filter

I just got a note from Martijn Jongen mentioning that he has a SURBL filter for Exchange.

New IMF hotfix for 15-character names

This is a pretty rare problem, but still: if you're running the Exchange IMF on a machine with a 15-character NetBIOS name, the IMF won't actually filter the inbound messages. This is kind of a silly bug.

Preset the language for OMA users

Imagine that you have a bunch of OMA users who don't use English as their native language. Wouldn't it be nice to set the default OMA language that they see when they log on, without making them learn enough English to navigate OMA's interface and set it themselves?

I hate it when this happens! I just sent off a Troubleshooter column question for the December issue on how to create separate settings on separate IMF servers. My answer involved multiple forests and was fairly ugly. I then decided to relax and do a little blog surfing. Lo and behold, It turns out that (courtesy of Evan's blog) there's a much more elegant solution to this problem.

What's in a SID?

Larry Osterman has a terrific post up today on the guts of Windows security identifiers, or SIDs. A small taste:

Port Reporter is a nifty tool from Microsoft that you can use to log TCP and UDP activity on Windows machines; it logs port activity on ports that you specify to a text file. It's extremely useful for monitoring traffic from specified machines or services, and it has a variety of useful features that I won't enumerate-- go download it already.

VERITAS buys KVS

| 9 Comments

Well, this is interesting: VERITAS buys KVS for $225 million in cash. Considering VERITAS' failure to turn their own archiving product for Windows into a real competitor for KVS, this is an interesting move.

E-mail free Fridays

Jeremy Burton has a good idea: declare Friday as an "email-free day" in his department. This story, which I first saw in the WSJ, has grown legs as people debate whether this is a good idea or not. I think the stimulus that led to Burton's edict is something we can all identify with: he wondered how much time his folks were wasting on email.

Barracuda Spam Firewall: first look

I've been testing the Barracuda Networks Spam Firewall 300 for the last couple of weeks. So far, I'm very pleased with it; it has done an effective job of filtering spam and virus messages. The best thing is that it incorporates rate control along with other more conventional filtering (including Bayesian and header analysis); this saved me from a huge comment-spam attack last week (see the big blue spike on the "daily mail statistics" graph in the picture below). The unit was very easy to set up and install, and it has worked without interruption since I installed it.

So, last week I wrote a column about SURBL. This week's column, which went out today, is about the regexfilter, a free filter that-- among its many other tricks-- happens to support SURBL. No sooner did it go out than I got two press releases from Jeff Chan of SURBL.org.

Free SPF filter

| 3 TrackBacks

I just finished a lengthy article on Microsoft's Sender ID specification; it should hit print in November. One of the points I had to address was the sad fact that Exchange itself currently doesn't support either SPF or Sender ID. This makes it hard to aggressively advocate that people deploy a Microsoft standard that isn't currently supported by their own products.

Passwords vs passphrases, redux

So, Robert Hensing started it off by saying something simple: "you should NOT be using passwords of any kind" on your Windows network. Instead, he recommends that you use passphrases. Good advice... or is it?

I recently posted about LANL's email troubles, and that inspired me to write a column about the same topic. Of course, not all of us have classified data actually on our servers.

Wow. 400+ pages of extremely detailed information about Exchange internals. Microsoft says that this guide is "not for beginning administrators", which means they might as well be posting a big red "READ ME FIRST" on the cover. Most folks don't like to think of themselves as beginners. Ever wonder which ESM operations use MAPI and which use DAV? Want to know how ESM decides to use DNS or WINS to find the server you want to manage? Curious about exactly what's in the link state table? This guide will tell you all that, and a bunch more besides. Highly recommended. Here's a taste:

Man, am I glad to see this: an official statement on MS' support position for VERITAS Storage Foundation. The bottom line is very simple:


To be very clear: Microsoft will provide support for Microsoft Exchange issues if you run Exchange on a VERITAS Storage Foundation platform. However, Microsoft will only troubleshoot and attempt to resolve Exchange-specific issues up to the point that the source of the problem can be reasonably attributed to an issue or incompatibility with VERITAS software. This same principle also applies to other third party products.

RSS feeds from public folders

Thanks to fellow MVP Glen Scales, it's now trivial to create an RSS feed from a public folder. This is very, very cool. Why? Well, for starters, we keep a public folder of security bulletins and alerts from various sources-- presto! it's an RSS feed. Many of my cow orkers who don't pay attention to public folders nonetheless will read anything that shows up in their aggregator.

It's NAP time

| 1 TrackBack

No, not that kind of NAP: in this case, Network Access Protection (NAP) Is Microsoft's name for the network quarantine feature they're shipping in Windows Server 2003 R2. The NAP white paper makes for an interesting read, but the NAP FAQ might be a better place to start. In brief, NAP works by allowing administrators to set policies (like "system must have version X of antivirus product Y") or ("system must have patches A, B, and C from Windows Update").

Can ISPs read your email?

| 1 TrackBack

Following up on yesterday's post on Councilman, I found this interesting article at GigaLaw: "Do ISPs' Policies Allow Them to Monitor E-mail?" At issue: whether ISPs can/should/do have the same kind of "we can monitor you" language in their user agreements as many corporations do in their acceptable use policies.

Last week's column concerned the Councilman decision, in which a US Federal district court seems to say that intercepting email is OK if you're an Internet service provider. I got a couple of reader emails asking what that meant for private organizations who may or may not want to read employee email. The bottom line, according to my non-lawyerly understanding: the Councilman decision means nothing in that context. Why? Councilman concerned an ISP, not a private company. If your employees have to agree to an acceptable use policy that says you can monitor their email, or if you otherwise put them on notice (e.g. by a statement on your OWA front page), the prevailing legal consensus seems to be that you're in good legal shape if you do need to monitor email. However, you still need to tread very carefully. If you really want more details, a) ask your legal department or b) buy my book and read Chapter 20, which was written by an actual lawyer with real legal expertise in the field.

Via my inbox, I found a very interesting blog post that outlines the timeline for fixing the recent shell: vulnerability in Mozilla. I tip my hat to the Mozilla team for their speedy response.. except that they forgot a couple of important things.

Microsoft's released a white paper on how to make Entourage work with Exchange. That's good. Unfortunately, some of the guidance in the troubleshooting section is frustratingly generic. For example, check this note: "In an Active Directory or network infrastructure that is heavily secured, Entourage 2004 Exchange clients can experience difficulty in locating the Active Directory global access server and authenticating the user account. Environments where the servers are locked down and the required ports are closed will experience these problems, and Entourage auto-configure might not work." So, it might not work, but you're not going to tell me why it might not work, nor what to do about it.

Information disclosure vulnerabilities can be quite serious, and they often generate lots of press interest. Sometimes this interest is fanned by organizations that make their living selling security advisories. mi2g has definitely been a major force in publicizing some past vulnerabilities, and now they've found a new one that has worldwide impact.

MSDN Product Feedback Center

This is really cool: a new web-based engine for tracking product bugs and feedback for Microsoft products. It will eventually replace BetaPlace (and not a moment too soon IMHO). You and I can now report bugs, not to mention being able to find existing bugs and "vote" for them to raise their priority/visibility. This doesn't have any direct impact on Exchange, yet, but it's safe to bet that when Exchange Edge Services hits beta that this will be the feedback mechanism for it.

IMF archive reviewing

| 2 TrackBacks

Over at the real Exchange blog, Neil posted a note about a cool web-based tool for reviewing messages archived by the Exchange Intelligent Message Filter. Written by Daryl Maunder, the tool is simple to install (create a new IIS virtual directory on your Exchange server, copy the tool files to it, and voila!) and works well. In the comments to that post, the tireless KC Lemson noted another filter, this one a C# tool written by James Webster of the Exchange team. Both work well; I currently prefer Webster's tool because it shows both the message and the contents of the P2 recipient data, using a sort of preview pane arrangement; I also like the fact that it's open-source. Maunder's web-based tool is cool too because you can access it from other machines on your LAN (or via VPN). Either tool is an improvement over the minimal functionality the IMF itself provides for reviewing archived messages-- try them both and see which you prefer. (Note to both authors: please, please implement a way to select multiple messages for action-- that would be a big help.)

The OWAAdmin tool

This week's column was on the very cool OWAAdmin tool. I neglected to mention that Tosh Meston, one of the developers on the OWA team, mentioned it in his blog-- sorry, Tosh.


This tool, which you can install on any Microsoft IIS server that runs version 1.1 of the Microsoft .NET Framework and ASP.NET, lets you remotely administer your OWA servers from anywhere in the organization. Although OWA offers quite a few features, the process of controlling OWA servers has always been a hassle because it depends on the creation of registry keys or values. Every Windows administrator knows how to do that, I know; the problem arises when you want to make configuration changes to multiple machines. Doing so manually is a bother and is even harder when you factor in common security settings that restrict or prevent remote registry access. You can always create your own Administrative Template file and attach it to a Group Policy Object (GPO), but only if you have the proper permissions in Active Directory (AD). Exchange administrators are often dependent on some other person or group to make directory changes.

You might consider this an error from the book, but it's really more of an omission: I never mentioned that you can use PFDAVAdmin to view, modify, and set public folder permissions, including fixing the "invalid windows handle ID" error that we all know and love. The MS Exchange Blog has a good overview piece, and I made PFDAVAdmin the topic of this week's UPDATE column,

Jeremy Kelly of Microsoft has a great post on online maintenance over at his blog. If you've ever wondered what happens during the online maintenance window, now you can find out.

Finally! You can sign up to get Microsoft security bulletins through RSS. Thanks, guys.

During TechEd last week, Microsoft sneaked out a new white paper on Exchange 2003 journaling. It covers the new SP1 "envelope journaling" feature, as well as finally explaining where Exchange journaling doesn't work. It also, at long last, describes how to deploy journaling as part of an overall DCAR solution. Good stuff.

Check this out: for 15+ years, the permissive action link system that controlled US land-based nuclear missiles was set to (drum roll): all zeroes. Really. Yikes!

Jeremy Reichman of the Rochester Institute of Technology has kindly collected a page of useful hints and FAQs related to using Entourage with RIT's Exchange environment. You should also definitely see the Entourage Help Page, which is chock full of useful info on Entourage 2004. If you don't read anything else, see the FAQ.

MSG381

Just landed in Cincinnati and checked my evals: 7.72. Comments were mostly favorable; a few "not technical enough" and one angry "Microsoft does too support our products" from a VERITAS product manager. However, that means that John humbled me decisively (his Word session racked up an 8.21!) In fact, I was just below the average score for messaging sessions this year. I've got to do better next time.

Update: with 108 evaluations out of a total of 522 attendees, my final score was 7.78. Since the overall for messaging sessions was 7.85, I'm still a little under the curve.

Random TechEd observations

  • This year, the speaker shirts were color-coded so that MS employees and speakers had different colors. This is great, since it makes it much easier for attendees to find FTEs to bother question.
  • A request from all those born and raised in the Southern tradition of good manners: please do not use, talk on, or answer your cell phone while you are in the bathroom. Thank you.
  • The service at Dick's Last Resort is as bad as it's claimed. Unfortunately, the food is worse than reported.
  • The speaker shirt is the first shirt I've ever owned with Spandex in it. It will, God willing, be the only shirt I ever own with Spandex.
  • The San Diego airport has free WiFi service. I can get a signal sitting in my seat (6C) with the boarding door open, but it's intermittent and doesn't allow me to actually log on.

TechEd day 2 wrapup

First thing yesterday, John and I met for breakfast at Cafe 222, where I had some excellent pancakes. The food at the San Diego convention center is pretty good, but it's always nice to take a break from the HUGE CROWDS of people for which TechEd is justly famous, so we did.

I did a session and a half in the "Meet the Technologist" area yesterday, where I continued to be impressed with the level of questions we got. Lots of high-end, thoughtful technical questions, with very few of the howlers or RTFMs common in years past. The cabana idea has worked well, except when Navy SH-60s fly past outside.

Yesterday was my first spin through the exhibit hall. I got to meet with some folks from Quest/Aelita; they have an impressive line of management products that oddly doesn't seem to be well known. The Authentica folks have an interesting product that can do digital rights management protection at the email gateway and via a web service-- very cool stuff. I'll write more about that when I have time to dig into it more.

Interestingly, the two overwhelming giveaway items this year were Xboxes and iPods. Some group of companies was giving away a MINI Cooper, which is kind of neat (although not as cool as the Mercedes SLK that was given away at TechTarget's Enterprise Messaging Decisions show :)

Also on the show floor, I finally met John Osborn, executive editor at O'Reilly. We had a great discussion about Offfice development and books (which we extended later at the O'Reilly author party once JohnP got there). I'm hopeful that we'll be able to turn some of the cool content we did for the Fabrikam project into a book, or two, to help build up our Office dev branding.

In a few minutes, I'm heading back over to Cafe 222 for another stack of pancakes, then it's time to present MSG381 and fly to Cincinnati to rendezvous with my family. In the meantime, let it be known that JohnP's Word dev session yesterday is holding steady at an excellent 8.09/9.00 rating, which is going to be tough for me to beat. However, the folks I linked to last week are still ruling: Steve Riley's sessions have three of the top 10 slots, including an incredible 8.81! Go Steve!

Threat modeling tool released

Microsoft has released a nifty automated tool for building threat modeling documents for applications you develop.

It organizes relevant data points, such as entry points, assets, trust levels, data flow diagrams, threats, threat trees, and vulnerabilities into an easy-to-use tree-based view. The tool saves the document as XML, and will export to HTML and MHT using the included XSLTs, or a custom transform supplied by the user.
This might seem to have low relevance for Exchange, but if you take a look at what's in these documents, you'll get a good jump start on understanding how to build a threat model for your network and deployed messaging applications (yes, even if you're using something besides Exchange).

Caller-ID and SPF converge?

I saw an interesting post by Meng Weng Wong, inventor of the SPF anti-spam mechanism: apparently Microsoft and Wong are working together to converge Caller-ID for Email and SPF. This can only help, as both standards have technical merit but neither provides a complete solution. There's a good overview of what this convergence means in this slideshow.

TechEd Day 1 wrapup

I flew out to San Diego yesterday and got to the convention center about 45 minutes before my first session, a troubleshooting panel with Chris Nelson (from Microsoft's IT group), Karl Robinson of HP, and the legendary Paul Bowden. It was fun to share the stage with three knowledgeable people, and we got some good audience questions.

Next, I had a book signing, at which I sold three whole copies of my book. It was fun nonetheless; I got to spend some time chatting with the legendary Charlie Russel, with whom I've worked but who I've never met, Paul Cayley of the MS UNIX migration team, and Eldon Nelson from Microsoft Press. After that, it was off to the "Meet the Technologist" area (aka "Ask the Experts"). The place was mobbed! Erik Ashby was drawing a steady line of folks asking 5.5 migration questions, and there were lots of miscellaneous troubleshooting questions.

John and I got together for a short visit (wherein I learned that his first session outscored mine by about 0.5-- significant on a 1.0-9.0 scale!) before I headed out to the MVP dinner organized by KC Lemson at the Zocalo Grill. I had the good fortune to sit with Andy and Kim Webb, Andy David, Scott Schnoll, David Sapery, and Sue Hill (all MVPs, save Sue, who works on the Exchange User Education team), and there were a ton of other MVPs (including Sue Mosher, Diane Poremsky [at least it looked like her from the back], Chris Scharff of MessageOne. The product team was well-represented: KC and David Lemson, Ed Wu, Nicole Bonilla, and a few others were there. As a bonus, I finally got to meet Brandon Hoff, the MVP lead for Exchange; he and I have missed each other several times in Redmond, so it was good to finally shake his hand. The food was quite good, and the company was great. (Thanks, KC, for setting it up!)

Today I'm back in the Ask the Experts area for a while, but I should be able to actually attend some sessions-- more on that later.

Very cool news: the Exchange Intelligent Message Filter is out, and it's available at no cost to all Exchange 2003 customers. Microsoft had previously said they would only offer it to SA customers, which generated a lot of discontent. I'm glad to see them reversing their stance. Get the IMF here, and be sure to read the deployment guide. (Oh yeah-- Exchange 2003 SP1 is out, too).

Very cool: Evan Dodds of Microsoft has a blog about (drum roll) Exchange clustering. You should only go there if you want actual factual technical information, though; you'll have to go somewhere else for $spin.

So, Evan, here's a clustering question: can I force all outbound SMTP traffic on a cluster to originate from the IP address of the cluster instead of one of the physical nodes therein?

First review posted

Happily, there's finally a review of Secure Messaging online at the Windows IT Library. My thanks to David Sengupta. (Now, if only Amazon would start posting the reviews that I know are queued up there...)

John Welch is posting a long review of the entire Office 2004 suite. It's not done yet, but the first part-- which, conveniently, covers Entourage in depth-- is ready now.

The gauntlet is down

At the 2002 MEC, John and I were both presenting multiple sessions, and we had a little friendly competition to see who did better. (I honestly don't remember the results; I just remember how psyched he was at successfully evading the wrath of the demo gods). This year, he has a crushing four sessions, all deeply technical (BPR310 is "Office Developer: Programming XML Solutions", BPR311 is "Office Developer: Programming Word XML Solutions", BPRC14 is "Building High Performance InfoPath Solutions", while I have but one (MSG381,"Designing a High Availability Exchange 2003 Solution") , so I have somewhat of an advantage. Both of us have some hard work to do to catch the top guns from last year's TechEd, though.

Architect Road Rally

This sounds cool: a get-together for developers at the San Diego Automotive Museum. The big draw: remote-control racing, with trophies. I won't be there, since it's before I arrive, but I definitely think John should go.

Sigh...

| 1 Comment
Ed's at it again. Rather than waste my time with a long rebuttal, let me just say this: I generally prefer to spend my time explaining technical things that help people understand Exchange better rather than pointing out shortcomings in competing products. I could go on at length about what's wrong with Notes and Domino, but why bother? So, it bothers me when Ed takes an explanatory technical article and twists it around in an attempt to make his competitive point, but hey, he's preaching to a choir of Notes admins, so I shouldn't be surprised. Well, OK, just one rebuttal point: since the column was on geoclustering, I didn't mention the many software replication products [e.g. DoubleTake] that are being used to provide geographically distributed DR without geoclustering; I also didn't mention ballpark hot dogs, '57 Chevrolet Bel Air coupes, or lots of other things that don't relate to geoclustering. Ed's guilty of claiming that there's no other way to solve the problem, which isn't what I said. These replication products have their own limitations, as does Domino replication, but they're not germane to a column on geoclustering, so I didn't mention them. Update: edited to fix a typo and to turn comments back on. Ecto sometimes randomly changes the "allow comments" and "format line breaks" flags between posts, and I don't always catch it.

I've been using Office 2004 for Mac OS X for the last six months or so. It's awesome. Don't take my word for it; go get the 30-day "test drive" version and see for yourself.

Closed comments on old entries

It's fun to see people asking for help cracking Yahoo passwords, but enough's enough. I've closed comments on that article. (Side note: I seemed to get more than my fair share of people with Indian names asking for cracking services... odd.)

I'm starting a topic for Entourage 2004 troubleshooting issues and FAQs, since I'm getting several dozen hits a day from Google on "Entourage 2004" and "Entourage 2004 Exchange". First, remember that there's an active Microsoft presence in the Entourage newsgroup, where some of this material is drawn from.
  • If you're using Exchange 5.5, you can't use Entourage 2004 in Exchange mode. Exchange mode requires WebDAV, which is only supported by Exchange 2000 and Exchange 2003. You can still use IMAP for mail, but you won't be able to sync calendar and contact data with the server.
  • If you don't know what server name to put into the "Public folder server" field, try the name of your Outlook Web Access server with "/public/" on the end of it.
  • If your OWA requires you to use https:// to get to it, you'll need to check the "DAV service requires secure connection (SSL)" checkbox on the Advanced tab of the Exchange account properties dialog.
  • Entourage 2004 can act as a delegate, but you have to use Outlook for Windows to set up delegate access. I plan to write an article explaining how to do this (in my spare time... bwahahaha).
  • If you send a meeting invitation from Outlook, and it arrives as an .ics file in Entourage, the "Accept" and "Decline" buttons may not appear. This is because of a bug in Outlook, and the Entourage team knows about it already.
  • Only the basic Contacts and Calendar folders are supported-- Entourage doesn't allow you to create subfolders of those folders, or to put contacts and calendar items in other folders elsewhere.
  • You can't adjust server-side settings (including the "out of office" state or server-based rules) from Entourage; you'll need to use Outlook or OWA.
If there's a specific question you want answered, feel free to leave a comment here and I'll try to help you.

20 tips for securing Outlook

The fine folks over at SearchExchange (in collaboration with MS Press) have excerpted chapter 13 from Secure Messaging with Microsoft Exchange Server 2003-- that just happens to be the Outlook security chapter. Their excerpt, "20 Tips on Securing Outlook in 20 Minutes", is well worth reading. It includes information on how to set up Outlook to use Windows Rights Management (including info on how to create your own RM templates), as well as information on controlling S/MIME through GPO templates, and how to set up and use RPC-over-HTTPs. f you like the chapter, buy the whole thing!

Everything old is new again

I used to have some old scripts on the website for my Exchange 5.5 book. I took the pages for the book down some time ago, but I still occasionally get queries for the scripts. Without further ado, then, here they are (note that I don't guarantee that they work with any particular configuration; use them at your own risk):

Remember the giblets

Long-time Exchange developer Larry Osterman had a great blog entry today titled "Remember the Giblets". An excerpt:

“Giblets” are the pieces of software that you include in your product that you don’t always remember.  Like zlib, or LHA, or MSXML, or the C runtime library. Whenever you ship code, you need to consider what your response strategy is when a security hole occurs in your giblets.  Do you even have a strategy?  Are you monitoring all the security mailing lists (bugtraq, ntbugtraq) daily?  Are you signed up for security announcements from the creator of your giblets?  Are you prepared to offer a security update for your product when a problem is found in one of your giblets?  How do your customers know what giblets your application includes?

As administrators, how much do you know about the giblets on your servers? Are you paying attention to them, or only to the big chunks (like Exchange or SQL Server)?

Compliance and S/MIME

| 1 TrackBack

In the comments to a previous post, Clement Kent asks a set of good questions about how to combine compliance requirements with encryption. The bottom line: if you have DCAR (discovery, compliance, archive and recovery) requirements, you have to be very careful with message encryption. You have two basic alternatives:


  • Archive the encrypted messages, then make sure that you preserve the key material so you can decrypt them later. This is really, really complicated, since you have to keep the certificates and private keys and CRLs around for however long your DCAR window is. The problem with this approach is that the DCAR system can't index the messages, so you won't have a good way to tell whether those messages are in scope when you do a DCAR query. It's hard enough for most organizations to deploy a PKI in the first place, much less guarantee that they'll be able to retrieve Joe CEO's certificate six or seven years from now.
  • Add the archive system as a recipient on all encrypted messages. The problem with this approach is that it doesn't work out of the box; you'll need to write your own tools. You could accomplish this via a client-side add-in that adds the archive agent as a recipient to any message that's encrypted, or you could use an event sink that would reject (or quarantine/flag for human attention) any encrypted message that the archiving agent couldn't read. As a bonus (mis)feature, this approach creates a very valuable target-- get the key to the archive account, and you can read all the sooper-secret encrypted traffic.

The US Defense Department chose option 2. Consider the situation where Alice and Bob, both CIA analysts, need to communicate securely. Alice is in Langley, and Bob is in Baghdad. If the CIA mail system allows direct encrypted mail between them, there's no way for the CIA itself to inspect the message contents. They work around this by using option 2, and also by allowing the mail to travel around Langley and Baghdad unencrypted, but using a server-to-server superencryption like that described in the Open Group's S/MIME Gateway Profile.

It's less clear how you'd preserve DCAR capability with messages protected by Outlook's IRM features. For messages sent to large groups (like, say, "all employees"), it's a simple matter to add the archiver to the group; then you just have to ensure that you keep the IRM system up and running for the required length of time. For messages sent to individuals, you're back to the requirement of writing code to either add the archiving account or to reject the message, but the code has to be smarter because IRM messages lack the easily-recognized S/MIME headers (not to mention that an ordinary message might have an IRM-protected attachment.. but we won't go there for now).

Off to EMD

I'm speaking today at Enterprise Messaging Decisions 2004. This is actually my first day trip in a while. When I lived in Huntsville, it was possible to fly out at 0530 or 0630, change planes in Atlanta, and make it to pretty much anywhere by noon-- enough time for a meeting or presentation-- and then get home again around 11pm. In Toledo, that's just not happening because of Delta's flight schedule ex Cincinnati. So, since EMD is in Chicago, I'm going to drive-- should be fun. Here's the slide deck.

Sasser on the loose

There's a new Windows worm: W32.sasser. It exploits a vulnerability in the Local Security Authority (LSASS.exe) service; the vuln was fixed by the MS04-011 patch. The original MS bulletin and patch were issued on 4/13, and the MS alert on Sasser was released on 5/1, so you can see the gap between patch and exploit is getting shorter. I'm sure all of you out there have already patched your systems, but tell a friend: install patches when they're released.

Anecdote: on Saturday, 5/1, Delta Airlines had a little dispatch problem that resulted in all their flights out of Atlanta being grounded for almost seven hours. The problem appears to have been with the airport computers used to calculate weight and balance according to FAA specs. One passenger on an affected flight reports that the flight crew attributed the delay to the "Mayday virus". I wonder what the real cause was?

Update: this WSJ article's last paragraph mentions Delta, Goldman Sachs, and JP Morgan Chase as companies affected; it also says that a Delta spokesman wouldn't say whether Sasser was to blame.

MSG381 TechEd deck posted

Well, it's only two weeks late, but hey, who's counting? (Besides the speaker manager at Microsoft, of course!) The first draft of my deck for MSG381, Designing High-Availability Exchange Solutions, is now available here. If you're coming to TechEd, the session is Thursday at 8:30-- stop by and say hello!

Update: Andy Webb was kind enough to point out a bad link, which is now fixed.

Reader Remek Kocz says:


First of all, thanks for writing Secure Messaging. I've been doing a lot of research on Exchange 2K security recently, and your book pretty much filled in all the gaps. The reason I'm writing you is that I have not been able to find an answer to what I thought was a simple question (Usenet wasn't much help, surprisingly). I've been tasked to secure our OWA servers w/SSL, and the issue of certificates came up. Is it possible to obtain a cert from a trusted authority like Verisign and then issue self-issued certificates with a path back to the Verisign one? Being a school district, albeit a large one, we need to look out for every dollar, so I wondered if it would be possible to combine the self-issuing CA &a commercial one. A pure self-issuing CA is not feasible for us, since many people travel without laptops, and there is no way of knowing how they'll access the OWA servers.

This is a classic case for use of a subordinate CA: you want to create a CA that issues certs to end entities (in this case, your OWA servers; it might equally be used to issue certs to users), and you want that CA's cert to be issued by a well-known commercial CA. You might think that Verisign, Thawte, and other commercial certificate vendors would provide this as a service, but as far as I can tell, they don't. Why? Their preference is for you to use them as an issuer, offloading all CA work to them (and, incidentally, paying a per-certificate, per-year fee!) For the specific case you have in mind, Verisign offers their managed PKI service: they issue the certs, and you manage the issuance and revocation process via a web-based admin tool…but you don't run your own CA. Section 3.1.1 of Verisign's certification practices statement talks about the process of registering as a non-Verisign sub CA, but I can't find where you actually do that on their web site. I'll post more details if I can find a better answer.

Update: BeTrusted's OmniRoot service does exactly what you want. Thanks to David Cross for the tip.

Fire suppression

It doesn't matter how secure your server is if it's on fire. The other Scoble has two good posts that describe the current state of the art in fire-suppression systems: here and here. This is actually something I talk about in Chapter 5 (physical &operational security), even though most of us are stuck with whatever physical plant is already in the building. Interestingly, one commenter mentioned pre-action sprinkler systems, which use water but which aren't activated without both heat and smoke alarms. (And hey, the inert suppression gas of choice is Inergen, not "Innergen".)

Entourage 2004 RTMs

Entourage 2004 has been released to manufacturing, so I can now talk about it. I've been working with it for the last several months, and it's a great piece of work. I'm working on a long article on it for Exchange & Outlook Administrator, but in the meantime, you might be able to try it for free. What? It's true. If you have valid Exchange CALs for your users, you're able to use Entourage as a client. See this "how to buy" page for more details (but don't ask me where you're supposed to get the bits, because I don't know!)

E2K3 Routing and Transport Guide

I needed to look up a piece of trivia on the Exchange routing engine for the cookbook, and after a little Googling I found this gem: the Exchange Server 2003 Transport and Routing Guide. I'm not sure how I missed it before, but it's quite comprehensive. Recommended reading if you want a better understanding of how the transport core works. In particular, its description of how the various connection filtering pieces work together is almost as good as what I wrote in Chapter 8 :)

Microsoft's finally taken the lid off a very, very cool addition to their product line: the Feature Pack for Windows Storage Server allows you to put your Exchange 2003 databases on a Windows Storage Server NAS box. There are some limitations: this approach is designed to handle up to 1500 concurrent users, and it requires good network connectivity between the Exchange server and the Windows Storage Server. However, it's a real, live, supported-by-PSS solution that can potentially deliver SAN-scale performance to organizations that can't afford Fibre Channel SANs. Check it out.

TechEd BOF

If you've been around the Internet for a while, you've probably heard of BOF, or "birds of a feather" sessions. BOFs are informal meetings held in parallel with conferences like LISA and regularly scheduled meetings like the IETF conferences. The International .NET Association is coordinating the process of setting up a series of BOFs for TechEd 2004. The cool thing about these sessions is that the BOF topics are proposed by TechEd attendees. Their content isn't driven by MS, or anyone else besides the people in the room. They're not presentations-- they're an opportunity for people with related interests, whatever they are, to get together and hang out for an hour. The MS TechEd staff is encouraging speakers to encourage "their" communities to propose BOFs here. There are tons of potential topics for Exchange, including security, anti-spam, job hunting, mobility, Notes migration, Exchange 2003 SP1... the list goes on. Let the INETA folks know what you'd like to see.

TechEdBloggers.net goes live

TechEdBloggers.net is back again this year. I enjoyed last year's edition; it was cool to see TechEd through the perspective of other speakers and attendees, especially folks who got to go to some of the many sessions I missed out on. To keep things simple, I'm going to post all of my TechEd-related stuff here, not on my personal blog.

I'm currently scheduled for two sessions: a troubleshooting panel discussion and a session on building high-availability Exchange 2003 deployments. Should be fun!

ExchangeFAQ.org relaunches

In 2000, I built a site of Exchange FAQs, driven by a (primitive) set of PHP scripts and a MySQL database. It mostly languished, because I didn't take on the extra effort of keeping it up to date. Meanwhile, Andy Webb and a crew of Exchange MVPs had created a good set of Exchange 2000 and Exchange 2003 FAQs. So, I gave andy the ExchangeFAQ.org domain name, and his new rendition of the site is now live. It looks great.

Still more on iSCSI and Exchange

I just can't help myself sometimes: I am a serial columnist. (Groan. Hey, at least I didn't make a pun on serial-ATA…)

Last week's Exchange UPDATE column was an update to my previous column on iSCSI and Exchange; I'd already blogged about the change, but the column has some additional material, including a discussion of MS' KB article describing support boundaries for NAS/SAN devices with Exchange 2003.

This is really cool: Windows &.NET Magazine now has a page of RSS feeds. The Exchange feed is my favorite. Update: the feeds occasionally time out, and they seem to only have five items in each category. They also don't include the Exchange UPDATE newsletter. Dang. Update again: the Exchange feed hasn't been updated since my original post, which I take as a bad sign. I've emailed my editors to see what's up.

More on iSCSI and Exchange

My column this week (which I can't link to right now, thanks to a bug at the Windows &.NET web site) was on iSCSI and Exchange. A helpful MS PR person wrote to point out an error: there's not actually a separate "certified for Exchange logo". If an iSCSI device has the "Designed for Windows" logo, it's supported for use with Exchange.

Update: it turns out that the Windows Catalog uses the "Designed for Windows XP" logo for iSCSI devices. Even though the column, and the press release which inspired it, talk about the "Designed for Windows" logo, those products listed in the catalog are certified for use with Exchange 2003.

From Microsoft to stand-up

Scott Oseychik, formerly of Microsoft's customer problem response team, has moved on to new things: he's now a stand-up comedian. No, really. I have no idea if he's funny or not, but he was very helpful in explaining the intricacies of the Exchange 2000 and 2003 transport engines when I was writing about them. I wish him luck (and I'll go see him if he's in Detroit, Toledo, or the surrounding area!)

Work for the Exchange team

Want a job working for the Exchange team in Redmond? They're having a hiring spree fair in late April in Seattle. See the jobsblog or send your resume here.

I wrote about a security problem with Plaxo a couple of weeks ago. It's since been fixed, but now I'm starting to hear that companies are barring their employees from using Plaxo, LinkedIn, and other social software. Why? Several reasons. The biggest seems to be that these services enable wholesale exporting of your contact database, which makes it easy for you to find out which of your existing contacts already use the service. This has two problems, though. First, it runs afoul of European Union data privacy laws; many multinational companies in the US have already been working hard to make their internal operations conform to EU regulations because they have EU operations and employees who live and work in the EU. Microsoft, AT&T, General Motors, and American Express come to mind. The other reason, of course, is that companies don't like the idea of a third party getting unrestricted access to a significant portion of their internal contact data. Imagine the bonanza for a clever Sun salesman who managed to steal all of the contact data for an IBM sales rep, for example. This is precisely why very few companies expose even shadow copies of their master directories to the outside world: there's too much risk in doing so, and the reward is fairly limited.

Will these bans work? Beats me. Services like LinkedIn and Plaxo have to reach a certain degree of critical mass before they become useful, but it's difficult to see how such bans can be efficiently enforced. Interestingly, the one ban I've actually seen in written form doesn't say anything about "personal" social software like Orkut and Friendster.

It's shipping!

Secure Messaging with Exchange Server 2003 is now in stock at Amazon. It doesn't look like anyone's actually bought it yet, but hey, you can't have everything. Update: the book has now attained the stratospheric Amazon sales rank of 92,218, despite its being paired as a bundle with Jerry Cochran's excellent Mission-Critical Microsoft Exchange 2003 for only $70. Sigh.

In a press release today, Microsoft announced that they'll be supporting iSCSI and NAS devices for Exchange. The PR doesn't mention any specific devices or vendors, merely that devices that are logo-qualified for the Designed for Windows logo will be supported. We'll have to wait and see what "supported" means in this context.

Exchange Edge Services

Last week, my column was on the forthcoming Exchange Edge Services product. Microsoft hasn't said much about it publicly yet, but it's pretty clear that they have two goals: provide a hardened subset of Exchange functionality for use on the edge, and displace Sendmail/postfix/qmail in shops that have Exchange at the core but not at the edge. Whether they succeed or not will have a lot to do with how they position Edge's capabilities. Personally, I'm really excited about the prospect of being able to build my own services using managed .NET code-- that approach offers a lot of potential over the current event sink model.

Cool new infosec blog

Infosecdaily.net bills itself as a site that aggregates security news for technologies. There's a lot of neat stuff there, including a great blogroll (sample: "A Day in the Life of an Information Security Investigator"). Check it out.

DoJ computer forensics guide

The US Department of Justice has an interesting guide to computer forensics, titled Electronic Crime Scene Investigation: A Guide for First Responders. From the abstract:
Computers and other electronic devices are being used increasingly to commit, enable, or support crimes against persons, organizations, or property. This NIJ Guide (NCJ 187736) is intended for use by law enforcement and other responders who have the responsibility for protecting an electronic crime scene and for the recognition, collection, and preservation of electronic evidence.
For experienced admins, there's not much new here, but it's a good overview of different classes of devices and some of the forensic concerns surrounding them. One question I'm often asked when I teach is whether forensic recovery is important. The answer is a little surprising.
Microsoft's released the Exchange 2003 Security Hardening Guide, which is basically the Exchange 2003 remix of the well-received Exchange 2000 Security Operations Guide. Like its predecessor, it's meant to be used in conjunction with the Windows 2000 or Windows Server 2003 hardening guides. The Exchange guides provide a set of security templates that can be applied to automatically harden Exchange 2003 servers; it also provides prescriptive guidance on protecting against viruses, spam, and DoS attacks. Of course, it's no substitute for a good book on security :)

Exchange and Software Assurance

[meta-note: there's no real security tie-in, but I've decided to post links to the weekly column I write for Windows & .NET Magazine. That at least guarantees fresh content here every Monday!]

This week's column focuses on Microsoft's Software Assurance (SA) licensing, how it works, and why Microsoft is (currently) making the Exchange Intelligent Message Filter available only to SA subscribers.

Late last week, Microsoft made an announcement that has many Exchange Server administrators fuming. The new Exchange Intelligent Message Filter, expected to ship later this year, will be available only to customers enrolled in Microsoft's Software Assurance (SA) program. On the face of it, this decision might seem shortsighted on Microsoft's part; after all, wouldn't the company want to sell its products to anyone who wants to buy them? However, from a long-term strategic point, the decision makes good sense for customers and for Microsoft.

Sig Weber's blog

Sigfried Weber (Exchange MVP, developer par excellence, and gracious host) finally has his own blog. For his most recent trick, he's made SharePoint emit properly formed RSS. Drop by his site and say hello!

A little housekeeping

In honor of the March 17 release date for Secure Messaging with Exchange Server 2003, I've done a little housecleaning. The Exchange 2000 version is still available, so I've tried to update the links in the right column so that they correctly point to the appropriate book. I'll be posting sample chapters as soon as I can get MS Press to send them to me; ditto the TOC and index.

Moving sale: cheap books

This is really an "I'm tired of moving" sale. When I signed to do Secure Messaging with Exchange 2000, I asked MS Press for 50 author copies-- 10 is normal. I figured that I'd have lots of copies to send out for review, give to customers, etc. However, I just cleaned up my office and found two boxes of books-- and any day now, UPS is going to bring me my author copies of the Exchange 2003 version. That means that the E2K versions must gooooo!

So, here's the deal: $20 buys you your own brand-new, signed copy; that's $15 less than Amazon. For $25, I won't sign it :) Email paul AT robichaux DOT net if you're interested. Remember, these make great gifts for Valentine's Day.

A fun game

Thanks to my friends at Lotus, I've discovered a fun diversion to while away the afternoon. Anyone can play! Here's how:


  1. Go to this page
  2. Sign up for a trial Domino Web Access account
  3. Try to send a message to an external SMTP user
  4. Get an error message
  5. Lather. Rinse. Repeat.

Update: This works properly now, and Domino Web Access is actually pretty impressive as a web client. I'd really like to see a neutral evaluation of DWA against OWA from the standpoint of an average user's ability to discover and use its features.

Microsoft's Exchange user documentation team has done it again. they just released a 101-page document convering the details of how recovery storage groups work, what you can do with them, and how to use them to speed up disaster recovery. It's available here. The abstract:


Using the recovery storage group feature in Exchange Server 2003, you can mount a second copy of an Exchange mailbox database on the same server as the original database, or on any other Exchange server in the same Exchange administrative group. You can do this while the original database is still running and serving clients. The recovery storage group can also be useful in disaster recovery scenarios. This book provides information on how to determine if a recovery storage group is useful in your deployment, how to set up a recovery storage group, and how to troubleshoot common problems.

Even though this doesn't have anything overt to do with security, it has a lot to do with availability, and that's actually a component of security: security is about preserving your access to your data, and if you can't get that data because of a failure, it doesn't matter how secure it is.

It's in pages!

Major milestone alert: the Exchange 2003 book is in pages. What that means is that the editors and page layout folks at MS Press have turned the original lightly-formatted Word files (and accompanying screen shots and napkin-drawn line art) into camera-ready pages. Barring any major mishaps, that means that the book's insides are ready to print. The cover's already been designed (see it on Amazon), so that means that with a little luck the book's ready to be printed!

And speaking of pages: I've set up Yet Another Blog, this one focused on the Exchange Cookbook I'm writing with Missy Koslosky and Devin Ganger. Check it out.

Alain Lissoir has a blog

Alain Lissoir, who probably knows more about Exchange scripting than anyone I know, has a blog of sorts. It's mostly a list of his publications, but it's still very useful if you want to know how to script Exchange or Windows using WMI, CDOEX, or CDOEXM.

It's done!

The book is done! (Cue sound of cheering... all coming from my family!) I'm still waiting on the chapter on legal issues to be completed, but since I'm not writing it, I don't count it against my total. Bio, dedication, acknowledgements, and all chapters are in MS Press' hands.

In related news, Amazon finally has a page so you can preorder the book (hint, hint). When time permits, I'll update the sidebar links here to point to both the E2K and E2K3 books.

Slipstick changes hands

My friend (and fellow E&O editor) Sue Mosher is changing jobs:


Effective at midnight tonight, Diane becomes the new proprietor of http://www.slipstick.com and its Exchange Messaging Outlook newsletter.

We'll be moving the developer content to my other site at http://www.outlookcode.com, which I'll continue to maintain and grow as a destination for Outlook developers. (And yes, all moved pages will have redirects to the new site. )

This will let me concentrate on developer issues and maybe get a little long-needed breathing room. I also plan to write a book on deploying Outlook 2003, so send those configuration conundrums my way.

I'm really excited that Diane will be bringing her enthusiasm and a different range of interests to the site, so that it stays fresh and relevant.

ExIMF changes for the book

I'm facing a conundrum. The book must be finished by 12/31. Although I have early access to the Exchange Intelligent Message Filter, if I write about it now it's likely to change before the book hits the shelf; this is obviously bad. What I've decided to do is mention it in the book, limiting myself to talking about what's already been publicly disclosed by MS. Then I'll write some material that describes it in more detail. That material will appear here, either as a bonus chapter for folks who buy the 2003 book or as a separate e-book. That way I can provide fresh material without getting in trouble with the PMs for the IMF or slipping the book any further.

Book progress

There are twenty chapters and three appendices. The first fifteen chapters (plus two appendices) have been written and submitted; several have already come back for author review. Of the remaining material, there are two new chapters written by contributors (one on archiving by Joshua Konkle of KVS, one on legal issues by Jay Friedman of Piper Rudnick) on the way, one revised chapter, and two new chapters (including one on Outlook Mobile Access/Exchange ActiveSync security issues) that I still have to write. Deadline: 12/31. Wish me luck!

Quarantine! Get yer quarantine here!

I managed to miss this, but Microsoft Press has a book out on VPN deployment with Windows Server 2003: Deploying Virtual Private Networks with Microsoft Windows Server 2003 Technical Reference. I haven't read it yet, but it was written by two Microsoft PMs (including the guy who owns the network quarantine feature), so I expect it's pretty good. Network quarantine is an interesting feature, but no one seems to really understand how to make it work. I've asked my editors for a courtesy copy and will post a review once it arrives and I read it.

Integrate Apple's iCal and Exchange

Technically this has nothing to do with security, but it's cool: Snerdware's GroupCal lets you see and share calendar information between Exchange 2000/2003 servers and iCal users. This essentially makes iCal act just like Outlook's native calendar client. I haven't tried it yet, but I'm about to install it on my wife's iMac and we'll see how it works.

From KB 831464:

n Microsoft Windows Server 2003 running Microsoft Internet Information Services (IIS) 6.0, static files that are compressed using gzip may become corrupted and may include content from other files on the Web server. If this behavior occurs, the page that is returned to the client is not rendered correctly. An access violation may also occur.

Translation: if you turn on Gzip compression for use with OWA 2003, your IIS server may get hosed. This patch fixes the problem.

Aelita releases CDO fix tool

I had a nice meeting with some technical folks from Aelita this morning. Among other things, I learned that they've released a free tool to help automate finding and fixing the CDO heap corruption problem (described in KB article 823343) that can occur when Outlook 2003 clients access mailboxes that are later used by CDO-based utilities or tools.

Mac OS X 10.3 and Exchange

Over on the other blog I discuss some pitfalls in getting Panther to synchronize contacts with Exchange 2000/2003 via WebDAV. It mostly works...

Mike Howard's got blog

I'm not normally one to post the same thing on both blogs, but this deserves double posting: Michael Howard (author of Writing Secure Code) has a blog, in which he discusses all sorts of tasty security stuff. (Too bad gotdotnet doesn't support trackbacks.)

You probably already know about the Windows Rights Management Server. It allows users to apply controls to their documents and messages; for example, you can tag an email as "do not forward", and Outlook won't allow it to be forwarded or copied. This capability is being called Information Rights Management, or IRM. IRM isn't ironclad-- after all, someone who wants to leak information can always find a way-- but being able to specify that documents expire, or that they can only be accessed by certain people, is a powerful tool for the documents' owners. (For more on IRM in Office 2003, see this.) One of the coolest IRM features is that by writing your own XrML templates, you can cusotmize which rights users can grant and how they apply. Sling a little XrML, and next thing you know your users can tag messages with things like "do not forward for 7 days" or "only full time employees can read this".

The problem is that getting people to use this technology may be difficult. IRM can offer a good way to ensure that sensitive material isn't accidentally forwarded, disclosed, or kept beyond its lifetime, but only if people use it. Enter Omniva, which makes a nifty server-side product that takes Exchange messages (including those sent with OWA and OMA) and adds XrML to them on the store side to make them IRM-protected. You define a policy once (e.g. "members of the Legal OU should have all mail encrypted, and it should expire after 180 days") and Omniva does the rest.

For more details on Omniva's product, see this. They have two white papers (one on the product and one on general retention issues). Check it out.

Happy Patch Day: MS03-046

Microsoft is moving toward issuing sets of patches once a month instead of in a steady, Chinese-water-torture stream. Accordingly, now there's a big ol' set of patches up on Windows Update. For all you Exchange 2000 and Exchange 5.5 folks, there are two of particular interest: MS03-046 covers a vulnerability that can lead to arbitrary code execution on Exchange 5.5 and Exchange 2000 boxes, while MS03-047 covers a potential cross-site scripting vuln in OWA 5.5. Happy patching!

More Exchange blogs

Turns out that Exchange-related blogs are popping up like housepainters at a beer giveaway. Andy Webb has one (named, of course, "webb log"), and so do the dynamic duo of KC and David Lemson, who just happen to be program managers on the Exchange team. Welcome, y'all!

Book progress

I've just turned in the first 10 chapters of Secure Messaging with Exchange 2003. That means I'm halfway done. The current milestone date for 100% completion is 12/15, which would put the book on store shelves in late February, just about a year after the first book.

This is what happens when you don't have an appropriate retention policy:

A little browsing and up pops a piece of e-mail from an Enron employee complaining about a mother-in-law: "the most selfish person on Earth." Another contains decades-old photos of former chief executive Jeffrey K. Skilling, sent him by his Beta Theta Pi fraternity brothers. A piece of e-mail written by a woman in Portland, Ore., asks an Enron energy trader, "So ... you were looking for a one night stand after all ...?"

The complete database is here. Don't let this happen to you!

New Blueprints edition

Evan Marcus and Hal Stern wrote the best introductory book on high availability, Blueprints for High Availability, back in 1999. It's an easy-to-read but detailed explanation of how to design and plan HA systems. I just found out today that they have a new second edition, just published. If you care about designing reliable, redundant, or resilient systems, get this book.

Excellent Exchange-related blog

While perusing the PVRBlog, I came across an excellent Exchange blog maintained by William Lefkovics, Neil Hobson, and Chris Meirick. It has a ton of good content and is more regularly maintained than my site. It now has pride of place in my RSS aggregator. Keep up the good work, guys!

Orlando now, Vegas later

From this week's Exchange UPDATE:

Attend Exchange Connections, Win a Free Vacation

Learn the latest tech tips and tricks from gurus like Tony Redmond, Sue Mosher, Paul Robichaux, and the Microsoft Exchange Team. Receive free access to concurrently running Windows & .NET Magazine Connections. Plus, youll have a chance to win a 5-day Las Vegas vacation with airfare for two. Register now online, or call 800-505-1201 or 203- 268-3204.

It should be a good show, and I look forward to meeting y'all there!

Book update

I haven't been working on the book much lately. The first 9 chapters are done, leaving me with 13 more to either revise or write from scratch (plus one that's being written by a Real Live Attorney). However, I've been so busy with work (including a really cool Exchange planning guide for the MSA series) that I haven't had any spare time to work on it. If you doubt me, consider this: I haven't even turned on the Xbox in two weeks, so you know I must be busy. It now looks like the book will ship sometime after the first of the new year, or about a year after the first version.

ISA vs DMZ

From a reader at a major whiskey maker (really!):

I purchased Secure Messaging with Microsoft Exchange Server 2000 at a Microsoft Windows 2003 conference in Cincinnati. The reason I purchased this book was for Chapter 14 Securing Outlook Web Access. I had been explaining to my boss that the traditional way of implementing Exchange 2000 (OWA) on a DMZ was not as secure as I would like, since you have to open several ports from the DMZ to the internal network. After explaining what I had found in your book and researching information on Microsofts website and others I convinced him and our corporate office this was the way to go. In June I implement your solution of Publishing OWA with ISA Server to secure our OWA server. This September we were audited by our internal auditors and they are telling us this is not as secure as the traditional way of placing Exchange 2000 (OWA) server on the DMZ. They could not give us a reason way, so I want to challenge them that this is more secure before I am force to change to the traditional way. I need information stating this method of securing Exchange OWA is more secure.

Tell your auditors to get off the glue. When you put an Exchange server of any stripe in the DMZ, you've created two problems. First, you're putting a domain member in the DMZ, and if someone compromises it they may have a springboard to compromise other machines inside the perimeter. Second, to make Exchange work you've got to open a ton of ports. DMZ configurations can be made secure, but the whole point behind ISA is that it gives you strong security by reverse proxying so you don't have to open anything in the DMZ.

InstantSSL for certs

I recently needed a new SSL server certificate, and I didn't want to pay the monopolists (wipe that smile off your face, I'm talking about these guys) an exorbitant fee. Instead, I found InstantSSL, where for a paltry $199 I got a three-year 128-bit certificate. Their administration site and ordering process are well-tuned, and I was able to get quick technical support immediately when I ran into a minor snag. If you need a cert (and you will, if you're enabling RPC-over-HTTP or Outlook Mobile Access), give these folks a try.

Litchfield does it again


From the sewer of misinformation and hype that is ntbugtraq, a rare factual and informative nugget:
For those interested, NGSS [David Litchfield's outfit -- PR] has just published a paper describing how to defeat the mechanism built into Windows 2003 Server to prevent exploitation of stack based buffer overflow vulnerabilities. Previous work done in this area presented methods that only worked in highly specific scenarios - the new methods presented in this paper are generic. The paper can be downloaded from http://www.nextgenss.com/papers/defeating-w2k3-stack-protection.pdf.
This is an interesting paper that will no doubt generate a lot of wailing, moaning, and gnashing of teeth. However, the fact remains that MS at least implemented a mechanism, and no doubt they will improve it as people (inside and outside of MS) learn how to defeat it. It's just another small corner in the Great Security Arms Race. I must say, though, that I'm not thrilled about Litchfield's decision to post exploit code in the paper, but maybe I'm just an old fogey.

RPC over HTTP help

Tom Shinder has an excellent writeup on how to configure RPC over HTTP. It's a highly useful supplement to the directions in the Exchange 2003 Deployment Guide, and it includes information on how to publish RPC-over-HTTP traffic through ISA Server-- always handy to have.

The Exchange library

Microsoft maintains a page of Exchange 2003 documentation here. There are some very cool things here, not least of which is the little "freshness" icon that indicates when each paper or article was revised and how long it's valid. There's not an impressive volume of documentation there (yet... just wait until you see what's planned), but what is there is quite good. My current favorite is the S/MIME quick-start document.

Great article on patching

CSO ("the magazine for the chief security officer") has a terrific, and well-balanced, article on the difficulty, and necessity, of patch management. I highly recommend it.

SPEWS/Osirusoft RBL goes away

According to this Slashdot article, the SPEWS real-time block list is no longer operational. A comment-free version of the same basic story is here. The article points to a lot of discussion on news.admin.net-abuse.email, too, which amkes for interesting reading. Osirusoft shut down SPEWS after being the target of an ongoing distributed-denial-of-service (DDos) attack. The manner in which it was shut down caused lots of bounces (including for my friend Bob Thompson and Kent State University, among others). The problem is that when Joe Jared, Osirusoft operator, shut down his service, he did so by telling the server to blacklist every IP address. Sites that rely solely on SPEWS thus dropped all their incoming mail on the floor.

What does this mean to you, the Exchange administrator? As Andy Lester points out, outsourcing your spam protection completely to a third party puts your mail service at the mercy of that third party. Exchange 2003 includes RBL support, and it's a useful adjunct to heuristic or keyword-based filters. However, RBLs themselves don't provide a complete solution, and you should choose your RBL provider carefully to make sure that a) they provide support for their service and b) they have the resources to stick out this kind of attack.

The other big security story

I figure everyone is sick of hearing about Blaster by now. (Quick recap: 1. Apply patches. 2. Install a firewall. 3. Use up-to-date AV software). There's another, lesser-known story out there that I think is pretty interesting: the master FTP server for GNU was compromised, and now they're scrambling to assess the damage and repair it. It's hard to discuss this without sounding like a fear monger, but I'll try to explain why this is so important.

ftp.gnu.org, the machine that was compromised, is the official central repository for all FSF software. All of the other FSF distribution points (and there are many) mirror its contents. - usually automatically. If you've added an FSF package to your system any time in the last 6 months, chances are that it came from ftp.gnu.org or one of its mirrors. Of course, if you've built any Linux distro in the last 6 months, odds are that you used multiple packages from ftp.gnu.org. Heck, the gcc compiler, which all free Linux software is built with, is officially distributed from ftp.gnu.org, so one might argue all software compiled with a compiler in the last 6 months is potentially impacted. (i.e. someone put a trojan in the compiler sources, placed those sources on ftp.gnu.org. Now anyone that builds that compiler has a trojaned compiler, one which outputs only trojaned binaries).

To recap: any FSF package downloaded from any FSF mirror might have been compromised. The FSF hasn't been cryptographically signing their packages (like Windows Update does) so there's no way to directly verify their integrity other than taking MD5 hashes, but that in turn depends on finding an "original" version of each pacakge and recomputing the hashes. They're going to start signing their packages, as explained here, but... well, horse, barn door, shut.

If this same compromise had happened to Microsoft, you can imagine the press firestorm that would have followed. The press reporting on this has been pretty mild; no one seems to think it's exceptional that an important machine, presumably run by competent admins, was compromised and that no one noticed for four months.

Interestingly, the FSF says that they believe that everything on ftp.gnu.org currently is safe, but they haven't said anything about any piece of software any time in the last 6 months. Their action thus far has been to wipe everything off of ftp.gnu.org and replace stuff that they feel confident hasn't been tampered with. This is the right thing to do from a security standpoint, but it doesn't inspire a lot of confidence in the security of the packages on their server and mirrors.

Password changing and OWA

KB article 331834 describes how Windows 2000 SP4 switches the IIS password change mechanism over to ASP files, instead of the older (and less secure) HTR technology. That's all well and good, except that if you have Windows 2000 on your front-end and Windows 2003 on the back-end (or vice versa), when you drop these new bits on you'll find that things break. Fortunately, help is on the way: use the handy script (also shown below for those who won't/can't download .WSF files directly) to fix up the file names. Note that although this came from a pal of mine at Microsoft, it's not an official MS tool and isn't supported by them.

Exchange 2003 tools center

Microsoft maintains a download page with lots of nifty tools for Exchange 2003. For example, the Archive Sink (which I talk about in ch 9 of the new book) is there, as is ExMerge and a utility for programmatically setting the allow/deny IP list on SMTP virtual servers. Check it out-- most of the tools are for Exchange 2000 and 2003, but a few (like MDBVU32) are useful for any version of Exchange.

Kurt Dillard of Microsoft was kind enough to let me know of the re-release of the Securing Windows 2000 Server solutions guide. This guide is a beefed-up revision of the original, released in February. It's worth your reading time.

We've all heard the canards about how failure to apply critical patches costs billions and billions of dollars. Maybe, maybe not; it's hard to use that argument in any individual setting. Here's a better argument: Verizon failed to keep its service-level agreements because of outages during Slammer. Those outages were the result of poor patch management, so the Maine public service commission made 'em pay up. The outage period? A day.

In Massachusetts, Verizon tried, but withdrew, a similar attempt to claim that the outage wasn't their fault. In Virginia, VZN was facing an $886,619 payback, but I don't know whether they've had to pay it or not.

InstantMessagingPlanet

I've recently been doing a lot of research into enterprise instant messaging systems (three guesses why :). I stumbled across Instant Messaging Planet, which has a huge amount of interesting reading material. I have no idea how accurate their reports are, so I'll have to get back to you on their reportorial quality.

Covert channels

This site has a lot of interesting stuff, provided you know what a covert channel or tunnel is. Happy reading!

Now hiring?

We interrupt our regular security discussions to bring you this news bulletin: America's health insurance situation sucks. While I can't reform it on my own, I can ask you loyal readers to help find a full-time job for a smart, experienced programmer who just happens to need insurance for his ill son. Brad Choate, legendary MT plugin guy, is even offering a reward: a free Xbox, PS2, or Gamecube. Details here, or Brad's original post here.

Physical security on my mind

I've been thinking about physical security a lot, mostly because I happen to be revising chapter 5. Take a minute right now to look around and see whether your physical security procedures are adequate. Could someone easily walk off with a server? (If someone can steal a DC, they can 0wn you totally, basically forever). Do you have adequate environmental protections-- power conditioning? heating/cooling? fire warning & suppression? I could write on and on about this, but I bet that if you spend a few minutes thinking about your environment you'll see what you need to do to improve it, probably at very low cost. The US Army's Field Manual 3-19.30 has some interesting thoughts that may help you.

This is really cool: as part of the Exchange Server 2003 RTM, Microsoft is passing out 7-day trial OWA accounts. This is a great idea for two reasons: it gives MS a chance to further dogfood OWA in xSP-scale deployments, and it gives those who don't have immediate plans to migrate to Exchange 2003 a taste of what the new OWA looks like. Sign up here.

Exchange 2003 RTMs


RTM for Exchange Server 2003 is today, June 30th. That means that the product will be available very, very soon for most customers, depending on your license plan:
  • Availability for Select licensing customers is August 1st
  • Availability for Open licensing customers is also August 1st.
  • Retail availability depends on the availability of Outlook Standard 2003. that means for English versions, you should see the CD in stores mid-September; other languages will follow, although I don't have exact dates.

Evaluation versions will be available for download or purchase on CD after noon Pacific time today.

So, SurfControl has been in place for the last five days. It has a fairly sophisticated set of tools, but with a much more approachable interface than Praetor. I've been using three rules: one screens out malformed MIME messages, one blocks messages with high dictionary scores (according to the spam dictionary that ships with the product), and one blocks messages that are on the collaborative filtering list that SurfControl maintains.

So far, the combination is working reasonably. There are still too many uncaught spams slipping through, largely of the variety that consist only of images (I added a rule for "Please wait while this email loads"; I bet that'll catch a bunch of them). More troubling is the rules service's tendency to abruptly stop processing inbound messages-- so far, I've gotten three or four messages from Microsoft that have choked the rules service. I have a call in to SurfControl tech support, so we'll see how competent they are at diagnosing and fixing the problem.

Update: the problem that caused MailMarshal SurfControl to choke on inbound messages was quickly identified. They fixed it in a patch, and their tech support was very helpful in answering some questions I had about the way the product worked. (Originally I'd typed "MailMarshal" in the above; to clarify, I haven't had to call MailMarshal support so far.)

SurfControl finally bit the dust; its eval period expired, so I knew it was time to try something else. SurfControl is a decent product; my big complaint was that its "Anti-Spam Agent" (a collaborative filtering tool that requires you to download updates from SurfControl) wasn't catching much. Turns out that was due to SurfControl's failure to allow eval customers to get the updates.

As I type this, MailMarshal SMTP is installing. It has a good reputation, so I'm eager to see how it stacks up against the others I've been testing. In the meantime, I have inbound SMTP queueing up for filtering, so MailMarshal should have a fertile set of messages to start with.

Update: Wow. MailMarshal has caught something like 99.2% of the inbound spam so far. I'm very impressed.

Update again: over a five-day test period, MailMarshal flagged 362 messages as spam. 49 (13.6%) of those were actually legitimate messages, most of which should have been allowed through by the "friendly listserver" and "friendly senders" features. None of these messages were critical, and frankly, many of them should probably be considered as spam. During the same time period, I only got *two* real spams. A number of legitimate messages (including some from our customers at MS and from the ntbugtraq mailing list) were flagged because they triggered the double-extension filter (like "document-1.0.5-pk.doc") or because they contained JavaScript. I appreciate the protection, but it's been a bit of a hassle.

I'm impressed with MailMarshal's efficacy, but its reporting tools don't seem to be as good as the ones in SurfControl (which tells you at a glance how long it's been up, how many messages were flagged as spam, and how many passed through.)

Update: Carrie Ward of NetIQ was kind enough to send me pricing info on MailMarshal:

NetIQ MailMarshal 5.5 SMTP is priced by the number of users in an organization and is available as a small business server license for up to

75 users for $1,295 or as an Enterprise version including a four-server license for $2,000 plus $750 per 100 users.

Did they do it?

Here's an interesting article: Foundstone is accused of piracy, being buttheads, and probably mopery on the high seas. Interestingly, the article also claims that Microsoft dropped Foundstone as a vendor shortly after the problems came to light.

MBSA 1.1.1 released

Version 1.1.1 of the Microsoft Baseline Security Analyzer has been released. Why do you care? Because this version adds scanning support for Windows 2003 Server, that's why. Go get it.

MSDN developer security center

MSDN now has a new security center. It's billed as "a one-stop source to help developers write secure code". Check it out. (hat tip: Michael Howard.)

New denial-of-service attacks

This is fascinating. Two folks at Rice's computer science department have written a paper about algorithmic complexity attacks. The basic idea is that an attacker who knows how a program processes input can overwhelm it by choosing patterns of data, or data with specific contents-- not the typical DoS caused by flooding. Here's the abstract:

We present a new class of low-bandwidth denial of service attacks that exploit algorithmic deficiencies in many common applications' data structures. Frequently used data structures have ``average-case'' expected running time that's far more efficient than the worst case. For example, both binary trees and hash tables can degenerate to linked lists with carefully chosen input. We show how an attacker can effectively compute such input, and we demonstrate attacks against the hash table implementations in two versions of Perl, the Squid web proxy, and the Bro intrusion detection system. Using bandwidth less than a typical dialup modem, we can bring a dedicated Bro server to its knees; after six minutes of carefully chosen packets, our Bro server was dropping as much as 71% of its traffic and consuming all of its CPU. We show how modern universal hashing techniques can yield performance comparable to commonplace hash functions while being provably secure against these attacks.

Three things you should read

A hat tip to an (unnamed) pal at Microsoft, who sent me (working) links for three useful documents:
TechEd 2003 is right around the corner. In addition to my session, there are a number of other useful sessions that security-minded folks should consider:
  • Mortimore, SEC301, Best Practices for Security and Patch Management (Arena, Monday, 1330-1445)
  • Attwell, MSG328, Reducing Spam with Exchange Server 2003 and Outlook 2003 (Ballroom C1/2, Tuesday, 1045-1200)
  • Riley, SEC304, Enhancing Exchange, OWA, and IIS Security with ISA Server Feature Pack 1 (Arena, Tuesday, 1045-1200)
  • Morris, MSG329, Controlling Viruses with Exchange Server and Outlook (D171/D173, Thursday, 1700-1815)
  • Riley, SEC499, IPSec Internals and Implementation Examples (Arena, Friday, 1300-1415)
  • Batthish, MSG345, Deploying OWA and FE/BE Topologies for Client Access (Ballroom C1/2, Thursday, 1330-1445)
  • Riley, MSG308, Secure Access to Exchange From the Internet (Ballroom C1/2, Wednesday, 1700-1815)

I won't be able to attend all of these, but I always make it a point to hit Steve Riley's presentations, and if you're interested in baseline security and patch management, Mark Mortimore's session is a must-attend too.

Steve Bass sent out an email alerting me to the fact that Amazon is giving away an anti-spam plugin for Outlook. I haven't used it myself, but Steve's endorsement is good enough for me to recommend it, especially since the $19.99 product carries a $20 mail-in rebate. Check it out and let me know what you think.

Update: Sunbelt was described as a spammer by John Levine, among others; it looks like the world-famous rhyolist spam list contains several entries related to Sunbelt or Stu Sjouwerman, the owner. Stu is also a Scientologist.

TechEd is just around the corner, and I've been invited to give a security session.

SEC306 Secure Messaging and Communications with Exchange Server

This session delivers the critical information that Exchange administrators, security architects, and messaging designers need to understand to protect their Exchange systems. Protecting your organization from malicious content, and misuse of messaging communications is becoming ever more critical as we depend on our messaging systems to provide anytime, anywhere access from a wide variety of devices. If you are serious about secure messaging and communications, you must attend this session. This session will focus on security updates in Exchange 2003 including relay restrictions, OWA security improvements, authenticated and restricted DLs, improved AV & Anti-spam features, and RPC-over-HTTP. Key security concepts for Exchange 2000 and Exchange 5.5 will also be summarized. Come in, sit down, and hold on tight for this fast-paced and demo-packed presentation.

The next product on my evaluation list is CMS' Praetor. My initial impression is that this is a complex, full-featured product, and it's expensive, too. (The fact that CMS is offering a 30% discount if you're using a competing product helps reduce the sting somewhat.) It supports X- headers for filtering and has a range of quarantine options. However, I'm not crazy about three aspects of the product:

  • it doesn't use the Windows Installer, and its custom installer doesn't bother to check for existing SMTP services on a machine

  • it has its own separate administration program (which apparently can't be installed on any machine other than the one running Praetor-- so much for remote administration)

  • it doesn't integrate directly with Exchange. Although CMS says you can run it on your Exchange server, they seem to recommend running it on a separate box, so that's what I'm doing. It didn't coexist well with ISA in my very limited testing, so for now it's on a separate machine.

I'm also not too impressed with the documentation; while it is complete, it's formatted using the old "ransom note" style template, and it's a reference. For a product this complex, a task-oriented doc would be much more useful.

The great spam-off, part 2

MailEssentials has been running for the last week or so. After a little experimentation, I discovered that it wasn't catching spam because I'm an idiot. I hadn't specified any SMTP domains as inbound, so ME was looking for spam sent to *@robichaux.local-- since robichaux.net and 3sharp.com are the domains I use, it wasn't catching anything. After I fixed that, it began behaving as expected. However, its lack of a way to add subject tags to indicate spam means that I have to route all suspected spam to a public folder-- where E2K turns it into an IPM.Post item, so it loses its original addressee information. Redirecting all the spam to a single mailbox works, but that raises the question of how to redirect it; the only way I can see to do it is with a script that adds a spam tag to the subject and redirects the message. That's more trouble than I'm willing to go to for this product. In GFI's favor, their product installs and uninstalls cleanly, it's stable, and it has good documentation. However, it's time to try something else.

UPDATE: GFI support confirms that their product doesn't allow subject rewriting, and they're not likely to add it.

In the balance

So, some reader mail:

What struck me about your editorial was that you were spending time with your family and still checking email. Is your family really that unimportant that you have to check email when you are having family time? This is a prime example of work/family balance having gone all wrong.

There are too many examples of people not knowing how to relax that they eventually succumb to a stress attack that prevents them from working again - or worse, their family loses them permanently. Perhaps it is worthwhile learning that email is like postal mail. You CAN leave it until you have finished the family time. You can also switch off the mobile phone!

Nothing - especially work - should interrupt family time. No wonder the divorce rate is so high.

Now, of course, there's nothing I like better than reader mail, even when it's nosy and presumptuous. In this case, I reassured the writer that my work/life balance was just fine, and that the divorce rate here in the Robichaux family is holding steady at 0% after 11 years. I also pointed out that checking email while the kids are napping hardly constitutes vacation abuse. I didn't bother to explain that checking email regularly is one of those quaint business practices that allows me to make it so my family can eat regularly, and that an IT support manager for a company specializing in HR communications might not understand that so well.

So, the executive summary: I love hearing from y'all, but let's leave my family out of it, 'kay? Otherwise I shall have to improve my work/life balance by sending my three noisy, energetic young sons to your house.

The great spam-off, part 1

So, I finally decided that the volume of spam on my servers had grown past my ability to tolerate. I decided to hold a spam-off by testing several well-known products and reporting the results here. My critieria are simple if unscientific: whichever product gives the best price/performance/usability ratio wins.

I started with GFI MailEssentials, which has been widely praised in a variety of places. It downloaded and installed easily (great installer), but after three days, it hasn't caught any spam, at least according to its own logs! It doesn't offer a way to quarantine spam into a public folder, and there's no way to mark a message as suspected spam. Other than that, it's great :) I'll post an update after I check with their technical support; I can see that the event sink is working because some messages from hosts on the ORBS RBL have been NDR'd (at least according to the logs).

Run E2K admin tools on WinXP

Hallejulah! Microsoft has released a patch that allows the Exchange System Manager tool to run on Windows XP. As it turns out, getting this done took a lot of work from several product teams at Microsoft. Good for them-- this is a welcome, if overdue, release.

TechNet is sponsoring yet another Exchange security chat, this one with folks from the ISA Server product team. April 9, from 1200-1300 EST / 0900-1000 PST / 1600-1700 GMT.

Free SQL security chapter

Just in from NTbugtraq: Erik Birkholz is giving away the SQL Server chapter from his new book, SPECIAL OPS: Host and Network Security for Microsoft, UNIX, and Oracle. I have no idea if the chapter is good or not; I do know that the book's Exchange chapter was written by Jim McBee, who knows how many beans make five. You can get it directly, or check out the book's cool web site (much cooler than this one, I must admit.)

Two more security-related TechNet chats to announce this week:

  • Wireless security (March 5, 1000 PST/1300 EST/1800 GMT). Are you thinking about setting up a wireless network at the office? At home? If so, you won't want to miss this chat. We can answer questions about how to control who accesses your network, WEP, and integration with Windows. (Attend the web cast immediately prior to this chat for additional information on wireless security.)
  • Exchange security (March 5, 0700 PST/1000 EST/1500 GMT) Come and ask your questions relating to Exchange Security. Questions can range from email virus protection to encryption to OWA configurations. Come test your questions against skilled Microsoft Technology Specialists.

Securing Exchange with ISA Server

Sure, you could read my book; if you really wanted the straight scoop, you could buy Shinder's ISA book, which has a wealth of ISA-specific information. You could also read this free article from SecurityFocus to help you get started.

MEC? TechEd? MEC Ed?

The always-subtle Kim Cameron-Webb came up with "MEC Ed" as the new name for this year's TechEd conference; for the first time, its content is being combined with the MEC of yore. Dallas in June? I'll be there. Sign up now and get a $400 discount.

SMTP, or not SMTP?

My question is: Is SMTP the only protocol / port required for basic email connectivity through a firewall?

Here's the scenario. We have a simple exchange 2000 implementation: one server, one network, and one firewall separating us from the outside. We only have a need to send and receive email with the outside. I have a dispute with a fellow admin (who also happens to be the boss and has final say - hence the need for an authoritative answer) that believes ports 135-139, 445 and 61007 need to be open at the firewall for exchange to send/receive correctly. I insist they need to be closed, as they are unnecessary and for security concerns. Thank you for any help you can provide.

For some value of "shallow"...

From a friend who shall remain nameless, lest he get flamed to oblivion. I think this speaks for itself. Physician, heal thyself.

Eric Raymond coined the term "Many eyes make all bugs shallow". he has an open sourceproduct, Fetchmail. in the last six months there have been at least four serious buffer overruns in the product:

Oldest affected version Release date

Vuln date Days til found CVE Number Short comment
5.3 2/22/20 10/11/02 962 CAN-2002-1174 long headers
5.3 2/22/00 10/11/02 962 CAN-2002-1175 DNS records
5.9 8/13/01 12/23/02 497 CAN-2002-1365 "@"s in local addresses
2.5 12/23/96 6/25/02 2010 CAN-2002-0146 Message limits

look at the length of time from the defective version being released to the date the defect was found (or at least made public). makes you wonder about the "many eyes" philosophy, doesn't it :-)

note, the version release date comes from ESR's news page

File this under "there's never a right way to do a wrong thing". In fairness, Sybari is proactively alerting their customers about this bug, and they still make a darn good AV product. However, if they had resisted the temptation to make their product do something that shouldn't be done, they wouldn't have this problem now!

From: support@sybari.com [mailto:support@sybari.com]

Sent: sometime last week

To: faithful E2KSecurity reader

Subject: Re: Configuring Scanned Folder Locations - Antigen for Exchange

7.0

Hello reader,

What build of Antigen are you running? There is a known issue with

corruption of the priv1.stm associated with use of the Disclaimer.

Several clients have seen this, and it is easily resolved by turning the

Disclaimer off. However, this is only a work-around, and, as of now, future

releases of Antigen will not have a resolution to this, since we don't know what

the cause is. We have been unable to reproduce this in house, and we need

someone who is seeing this to run a diagnostic utility that will provide

more information and, hopefully, a solution.

[ snipped some other unrelated stuff ]

Regards,

a support person

Sybari Software, Inc.

E-mail: support@sybari.com

http://www.sybari.com

Early spring cleaning

I've made a couple of minor changes to the site. First, you'll notice that the dorky-looking Amazon blob is gone from the right side bar. No one was clicking on it anyway. Second, there's a new form for signing up for the goodies mailing list-- I've moved from pairlist to Topica's paid publishing service, which means that all y'all will finally have a real interface for subscribing and unsubscribing.

The new phone book is here

My wife's voice floated down the stairwell, jolting me away from my exciting task of filling out a matrix showing how OCS compares to Exchange. "Honey, the FedEx man left about a dozen packages on the front porch!"

Now, you have to understand that the arrival of the FedEx lady at our house is always a time of celebration. The best times are when she unexpectedly brings some kind of goodie, like a piece of review hardware. Next-best are when she brings something I've been anticipating, like salmon chowder or a copy of iLife. (I'll have to tell y'all about the 50 pounds of candy some other time). When I grabbed the boxes to bring them in, I was greeted by a curious sight on the address label: "AOL Time Warner Book Group".

This worried me; I was briefly afraid that I was the victim of a drive-by AOL CD dropoff. A glance at the side of the box, though, revealed that the boxes contained my author copies of the book! O joy! Sure enough, when I opened the first box, two copies were staring right out at me. That means that my contributing editors and reviewers will be getting copies over the next few days; the rest of you, alas, may have to actually buy it.

The crypto gardening guide

Peter Gutmann's done it again; he's produced a wonderful paper for crypto implementers. It posits questions like "Consider whether your design can be implemented on a system with a total of 1kB of memory, or alternatively whether it can process a 1GB data block in a machine with 128MB of memory" and offers pithy comments like "No matter how cool/interesting/useful/mandated in standards a new design is, it won't be used if it requires redeployment of all existing hardware and

software for little apparent gain."

Two new Microsoft webcasts

Microsoft has two upcoming webcasts that may be of interest to all you Titanium-watchers out there.

The first one, on 2/12 at 1000 PST, covers Exchange 2003 deployment methodologies. The second, on 2/20 at 1000 PST, covers Exchange security. The TechNet chat summary page lets you get reminders, add the chats to your Outlook calendar, or spam your friends with reminders. See you there!

XP SP1 "phone home" paper moved

I just got an IM from John Matteson informing me that my link to the whitepaper on how Windows XP SP1 uses the Internet is broken. The paper is now here. It'll probably move again at some point in the future, as MS is wont to do.

The seven seals

The US Navy has helpfully posted a guide to tamper-resistant seals. What does this have to do with Exchange? Basically nothing. However, it's still cool, and it offers some interesting insight into how high-value assets can be physically protected against tampering. In particular, chapter 2 ("The Theory of Effective Sealing") has a lot of good attitudinal information that's worth reading if you're a computer security person.

MS Press still doesn't have the book's page completely put together, but so what: now I have my own samples. You can see them in the nav bar on the right-hand side of this page, or you can get them here:

  • Table of contents: this gives a very detailed look at what's in each chapter.
  • Introduction: if you're not table-driven (sorry, programmer humor), check out this more readable and condensed explanation of what's in the book
  • Chapter 3: Windows and Exchange Security Architecture: this chapter explains the fundamentals of Exchange's security architecture, including what it uses Windows services for.
  • Chapter 4: Risk and Threat Assessment: read this chapter for a new perspective on risks and threats (oddly, it's the perspective that professional risk assessors use...)
  • Chapter 8: SMTP Relaying and Spam Control
  • : read this chapter to learn how to control SMTP relaying and how to restrict spam on your servers (hint: buy a third-party product. just kidding, Microsoft.)

All of the files are PDFs. Please feel free to tell your friends about them; however, I'd appreciate it if you tell them to come here instead of just sending them copies. My children are rapidly approaching college age, y'know.

"Keep it secret, stupid"

Lots of people subscribe to the idea that keeping security vulnerabilities secret is the best way to deal with them. Dr. Matt Blaze, an eminent cryptography and security researcher, had a few thoughts on that the he shared with Dave Farber's Interesting-People list. I post it here as a cautionary tale.

Exchange 2003 webcast

Mark your calendars; on 10 January at 0830 PST (that's 1630 GMT), Microsoft's scheduled a webcast with Ed Wu, product manager for Exchange 2003, to discuss its new features and cool goodies. There will probably be other such events, especially as we get closer to TechEd 2003. (Note to Microsoft: if you're going to have TechEd in the summer, why hold it in sweltering places like New Orleans and Dallas? how about Minneapolis, San Diego, Toronto, or someplace with more moderate weather?)

Exchange 2003 public beta released

Microsoft's released the first public beta of Exchange Server 2003, formerly codenamed Titanium. Exchange 2003 has a ton of new features; my favorites include the ability (when running on Windows .NET Server) to do snapshot backups, and the ability to use signed and encrypted mail with OWA. You can download the Ti bits, or you can order an eval kit with Exchange 2003 beta 2, Windows .NET Server RC2, and Office 11 beta 1 for US$20. The "getting started" guide makes for interesting reading, too.

I had a network account, from a certain large software company, used for my work for them. Due to an administrative snafu, it was disabled and won't be re-enabled until the manager returns after the holidays. I needed a message that had been sent to that account? What to do?

In my case, it was simple: I fired up Outlook 11 and got the message out of my client-side cache. This really isn't a new feature; Outlook's had PST and OST files for a long while. However, Outlook 11's synchronization is seamless and automatic. As an end user, that's great. As an administrator, though, it makes me wonder: what can I do to prevent or restrict the use of cached content? I have a sneaking suspicion that Microsoft has some ideas in this direction, and that we'll be seeing them emerge in future betas of Outlook 11.

Security templates

If you apply the security templates from Microsoft's Exchange 2000 security operations guide, remember that these templates are additive. You must first apply the correct templates from the W2K security operations guide.

VNC update

In a recent column (12/10/02), I more-or-less dismissed VNC as a useful remote access tool. Two readers wrote in to correct me. First, VNC now has a new home, with a slightly more up-to-date version. However, they've dropped the Macintosh version; boo hiss. Second, there's an allegedly optimized version called TightVNC, based on, and interoperable with, the original version. TightVNC has a Java version, so I guess that's what Mac users are supposed to use. I haven't tested either of these, but if you're allergic to Terminal Services they might be worth a look.

AV scanning on connector servers

A reader asks:

Should I do AVAPI virus scanning on connector servers?

It doesn't matter. AVAPI only scans the Exchange information store, so running it on your connector servers won't do any good. Instead, you need an SMTP virus scanner like Trend's VirusWall or Nemx' Power Tools.

A reader asks:

Can you please help with a huge frustration I have with Outlook? After applying one of the "security patches" a while back, Outlook now deletes .txt files and others out of hand without asking me. I work in an environment with many Unix-heads and thus get lots of .txt file attachments, as well as other types I can't think of off the top of my head, that Outlook summarily deletes. Not only is this an asinine excuse for security, it requires I open Netscape and read my mail through its client in order to view the attachment - DUMB! Is there a way for me to go back to sanity without completely reinstalling the Outlook client?

Why, yes, dear reader-- there is.

Apart from the twin facts that they're annoying to outsiders and that they can cause mail loops, the BBC reports on a third excellent reason not to use out-of-office messages to the Internet: people will rob your house while you're away.

Order now for the holidays!

Well, Valentine's Day, that is. According to Amazon, the book will ship 2/5/03. This is a bit later than I'd hoped, but I suppose I should have written it faster.

If you preorder it now, though, you're assured of getting it when they do.

Microsoft is changing the way they distribute security bulletins. In the past, they've blasted out fairly technical bulletins to all subscribers, including the home users and other non-administrator types who took my advice and signed up for the bulletin service. It's a litte daunting when Mom gets a security bulletin for Exchange 2000!

To make it easier for everyone to find out what's what, their new process is a bit different:

  • The existing technical bulletins stay around, but they're now targeted at administrators, not end users
  • In the future, new bulletins for end-user issues (like patches for IE or Office) will be released. These will be less technical, with links to more info on the MS web site.
  • The rating system for vulnerabilities has changed. Since someone else already has a monopoly on color codes, Microsoft's using a scale ranging from "critical" to "low".

I feel much better

I'm always a little leery of technical editors, because I know how most publishers choose them: they look for someone who a) is breathing and b) can spell the name of the product or technology covered in the book. I'm fortunate that MS Press chose Tony Northrup as their TE for this book; his comments have uniformly been useful (even when I didn't agree with them), and he's caught a bunch of my stupid mistakes before they got out into the wild.

There are a number of volunteer TEs, too, whom I'll be introducing over the coming weeks. In particular, a number of Microsoft PMs have volunteered to review material related to their domain expertise, which is really helping strengthen coverage of some key areas.

Book progress report

I basically have three weeks to finish the book. The first 10 chapters are all done and delivered to Microsoft; 9 of them have already been through author review. A total of six chapters have yet to be written, so I've got my work cut out for me. (Actually, one of those 6-- the one on POP/IMAP security-- is all done but for the chapter summary.)

Indexing, proofreading, and printing usually takes about 12 weeks for most publishers. This is my first MS Press book, so I don't know if they're faster or slower than average. As soon as I have more information on an ETA for the book, I'll post it here (although it's not showing up on Amazon.com yet).

About this Archive

This page is a archive of recent entries in the General Stuff category.

Friends & Family is the previous category.

General Tech Stuff is the next category.

Find recent content on the main index or look in the archives to find all content.

Powered by Movable Type 4.21-en