Microsoft

Microsoft Shows off Unified Messaging

So I got the usual slew of “you’re selling out, man” from my Linux friends by saying my company is pushing Microsoft software. I’m sorry guys, but the world demands more – more than IRC and GAIM. No, those are not the same as what Microsoft is building, not by a long shot. Take a look at this video to see what Microsoft is doing for communications.

IMG_1853

Above is a demonstration of the new integration of LCS, Office and Unified Messaging. They are showing an integrated system of multiple presentations, multiple presenters and the camera that swings to the person that is actually talking or whose presentation is currently on the screen. Yes, they are working on something really important

But this kind of underscores just what Microsoft is working on and what is coming out. Yes the basics could be pulled off on Jabber, and Skype and eventually thrown together – but virtually anyone involved in software development will tell you that its cheaper to just buy than to sit around and reinvent the wheel over and over again. These will be expensive, thats for sure, but I for one don’t want to spend more time listening to screaming todlers on airplanes.

Has the Small Business Specialist Certification Failed?

There has been quite a bit in the community about the revised Microsoft Small Business Specialist certification exam 70–282. Why? The idiots are complaining that Microsoft made it too hard. As a Microsoft Certified Systems Engineer I can tell you that if you have even the slightest problem passing 70–282 you outright have no right to consult small business on their IT decisions. Plain and simple.

Today a friend of mine called with a question and, in finest Monthy Python tradition, reached abuse:

Ryan: Hey Vlad, can I pick your brain for a moment?

Vlad: Real quick, whats up?

Ryan: What would you suggest in terms of RAM for SBS running Virtual Server running Terminal Services? I just realized Virtual Server 2005 is free.

Vlad: 4 GB.

Ryan: Oh, ok.

Vlad: Yeah, might as well go all the way.

Ryan: I was thinking about perhaps using another board, so I can add more RAM later – 6 or 8GB?

Vlad: Ryan, How did you pass 70–282?

Now it is true that there are many people out there that passed 70–282 but have no reason, ever, to be near a server. You see examples of such in newsgroups every day. But does that invalidate the entire certification, Microsoft’s effort to build a recognizable branding for legitimate small business consultants, official training materials (books, webcasts, coursework, etc) and further promotion of those that pass? Absolutely not.

I get blamed for being hard on Microsoft but at the end of the day our business is promoting and selling Microsoft solutions – I try to beat them up when I see them making decisions that will negatively impact our customers. But you cannot blame the company or the program just because people are dishonest and cheat their way to certification. You cannot blame or look down on a certification just because some who choose to participate are dishonest. That only reflects poorly on those that cheat, not the program itself. Let’s not focus on the crimes of the few and instead look at the triumph of those who succeed with Small Business Specialist badge. Many, present company included, have been more successful with it than the Microsoft Certified Partner badge.

Embracing New Technology: Origami

Call this an op-ed if you will, there is something I would like to share with you about the Origami project Microsoft has been working on for quite some time, along with a spectacular vaporware  marketing campaign. Much like its flashy Apple friend, most were disappointed at what the device actually did and of course only appealed to the few hippies that still dream of sticking it to the man by thinking differently. It almost seems as if Origami is Microsoft’s self-inflicted confession that they are a dull looking midlevel manager that Apple portrays them to be in their latest commercials. Quite the contrary.

Rewind back about ten years with me, please. I worked at a major ISP and one of our NOC engineers was an avid Palm user. He walked through the halls never lifting his head up from the glaring green screen. He would break out the device in the middle of a conversation and almost seemed to do important work as he launched the freecell.

He was the revolutionary geek on the team, he wore his Palm III on his toolbelt.

He was so cool that we renamed him “tool.”

Rhymes with cool but its quite the opposite. I was arguing the concept of wearable computers with Jim Harrison and Tom Shinder last week at TechEd. Their stance was that there is a market between tablets and Pocket PC’s and that every new evolution of computing would be met with some hesitation. But wearable? Oh, heck no. When did we all begin to wear our Pocket PC’s and PDA’s? When they got the phone functionality.

My argument? Wearing a computer is essentially begging to be beaten.

I actually had a chance to meet a fellow MVP that specialized in Mobile Devices and I just had to know how this could possibly be useful. His take?

Well, this device has a stand that I place it in. Monitor, Keyboard, Mouse, peripherals are all plugged in at my desk. If I need to run into a meeting I take the device off and its instantly a tablet.

Now just how this differs from a Tablet PC was a sketchier answer (oh.. size.. weight) and the idea that this gadget was somehow worth 100% markup of a more powerful, more flexible solution was as laughable as any argument that your average Mac user comes up with as a justification for their overpriced, yet highly glossy and polished, WinTel clone choice.

Call me ignorant here but have we solved the problem of blind using computers? How about deaf? How about the millions of people that suffer from carpal tunnel? Is Internet Explorer THAT perfect that we need to lose more money on Xbox while our bank accounts are owned every other day?

I have an idea. Bill. Steve. How about the two of you go back to the garage and come up with a revolutionary way for us to use computers and help those who have physical disabilities — not just empowering the mentally disabled with deep pockets who have a need to be different from the rest of the world as they so casually separate themselves from it with the trendy white headphones.

Linux vs. SBS: Switch!

Excellent point brought up in the comments section today by Josh:

For example, Microsoft wants to argue about stability vs. Linux. In nearly all Linux servers we manage that comparison is laughable. Now, compare RPC-over-HTTP functionality with Linux? You can’t, no such thing on Linux! Where is that among the facts?

This is something that I’ve tried to make very painfully clear in my Linux presentations for SBSers in Florida groups. Here is the thing about winning in small business, you have to know your customers. You also have to know your Microsoft and understand certain “facts”. So here is a little competitive howto on Linux vs. SBS.

Watch Where You Get Your Facts

First and most important thing to understand about Microsoft’s Get The Facts site is that those reports have been paid for by Microsoft and are to a large extent questionable at best and outright false in many respects. Second thing to remember is that those reports are not written or targeted for the SMB market at all - they are written to discourage enterprise and high-end markets from moving their commodity-line servers to Linux and discourage Unix-shops from going to Linux instead of Microsoft. If you’re an SBSer, you will not find your facts there.

Know Your SWOT

Know your strenghts, know your weaknesses… but more importantly know what is not your weakness.

Price

When bidding against Linux you are really competing against this: “Joe Consultant told us that Linux is free.” They are correct, many Linux distributions are free. So in most cases, it will be $599 vs. $0. For the purchase price that is. So on the face of things, Linux wins because its free.

When you dig a little deeper you find out that the “free” is the acquisition cost. If you are losing a client over $599 this is likely a client that you do not want as your business to begin with. If the server costs $1,800 and your labor to set them up and train them for a week will cost them another $4,000 that up-front licensing cost of $599 is going to be less than 10% of the total solution. This is generally what Microsoft talks about when they mention their TCO, total cost of ownership.

But we know our small business owners, don’t we? The same folks that will sign up for a plan with a “free cell phone” (MSRP $99) but agree to a two year contract that costs $20 a month more. If you really want to compete against Linux give them a 10% discount on your labor which will outright displace the licensing costs. Show them that they will be paying the Microsoft penalty anyhow as its very hard to impossible to buy a PC without a Microsoft OS to begin with. 

Upgrades and Migrations

When you bid against Linux you bid against free upgrades, forever, and easy migrations. Thats at least what gets put on the paper and what the Linux guy will say. The truth is much different. Here are a few facts that you might want to consider about some of the most popular Linux distributions out there:

Fedora – Fedora is a free version of Redhat Linux. Redhat Enterprise Linux is a full tested and supported distribution of Linux that retails between $350 and $3000 per server. So whats the difference? Redhat uses Fedora as their bleeding edge distribution, they use it to roll out experimental packages and see what breaks. The software itself is solid, but it is not elegant by a long shot. For example, consider that there is no migration path from version 3 to 4 to 5 – if you Google for “upgrade from FC3 to FC4” you will find a number of hacks that show you how to fool the dependancy checks and hack your way up. Not that it won’t work, but what happens if it fails? Remember, unsupported. There is literally nobody you can call.

Debian – Used to be most popular but recently displaced by its Ubuntu cousin. The trick with Debian is that they are so fanatical about being free that they eliminate any commercial or restricted software (or non GNU) from the base distribution. It is a severly outdated technology (in terms of even years) that nearly everyone seriously running Debian is doing so with the untested– or experimental– branches of the code. Even if you’re not a Linux person you can imagine what thats like. Again, virtually unsupported except for the MVP-like effort.

Gentoo – The concept here is that this is the most optimized version of Linux you can get because virtually everything from kernel on up is upgraded by running an emerge command. What emerge actually does is pretty cool – it downloads the source code along with a spec and compiles it against your hardware – so on a fairly loaded box you are constantly affecting the performance by rolling out your own code. Do you trust that your security patches are deployed as full recompiles of the source code? I don’t even trust most binary patches.

Ubuntu – The darling of the Linux world at the moment. Built on the Debian core with the pretty integrated interfaces and its claim to fame is the ability to roll out LAMP (Linux, Apache, MySQL and PHP) in 15 minutes. Pretty, but unsupported.

Those are the basics of Linux and distributions you will likely come up against. Every now and then someone will propose an Enterprise Linux version, a free community recompile of the popular Redhat Enterprise Linux. Distributions such as CentOS and WhiteBox Enterprise Linux. They are free, but again, unsupported as well.

So here is a real world scenario for you. The upgrade for the above is free– in all cases. They will download an ISO, burn it, stick it in a Linux server and after the reboot the system will be upgraded. All free! Yay.

As far as the technical discussion is concerned, they are right. Here is the dirty secret behind this though that nobody talks about: For most scenarios Linux doesn’t migrate, Linux overwrites. Now lets say your consultant tweaked the /etc/rc.d/rc.local file to automatically delete specific files on the server – generally a Linux distro upgrade would put in the new file in the place and make the original one a rc.local.bak. Let’s say you wanted something special done with your web server – your /etc/httpd/conf/httpd.conf file would have two options – it would get overwritten, or they would copy an httpd.conf.orig or tweak it in another way.

So yes, the upgrade is free. But the time to get this done is not. More importantly, because these migrations are generally done on per-site basis (ok, these guys have Redhat, these are on Fedora, these are on Gentoo) the migration checklist is all but nonexistant.

The truth about Linux deployments is that they are very much done on a per-case, needs basis. The beauty of the system (unlimited flexibility) is also its dagger because by endlessly tweaking the system the documentation part of the setup goes out the window. And when the migration goes bad with the freebies above you will likely have only newsgroups and mailing lists to turn to.

Finally, migrations nearly always include more than the base OS. The reason you deploy a Linux system is to get a flexible, fast and cost effective server. Well, Linux developers don’t think the same way business owners do. Linux developers try to adapt new technology, provide the newest features, create a system that is easiest and fastest to develop for. So when that new distribution comes with MySQL 5.0 and PHP 5.0 – will your PHP 4 script designed on MySQL 3.1 work? Maybe, maybe not. Who do you contact to find out – the webmaster that took the script from some random site? Nope. The commercial software developer? Unlikely, they only support official distributions like Redhat Enterprise Linux and SuSe. Who do you turn to? Good question to ask while providing a competitive bid.

How do you do application migration compatibility tests on Linux? You install the new version and try to hack it into working. If you’re lucky, it will just work. If you’re not lucky, whats the alternative? Another question for the stack. This is not the U part of FUD in uncertainty, this is something that there is no good, reliable, documented process in Linux. For years Linux distributions have tried to fight amongst themselves to develop a unified way that Linux is deployed - with same file system layout, dependancy checks, package management. Today you’re more likely to find multiple package management systems (yum up2date, apt).

Features

For the most part this is your biggest strength. Small business owners and business people in general have habbits that are hard to change. Going from a Windows world to a Linux world is a big transition in anything more complex than a P2P environment. Its easy to replace a pop3 server with an onsite dovecot deployment. But when you’re selling a new server you are selling new functionality. Here are things that you will not find in Linux.

Exchange – Biggest advantage. There are no decent webmail programs for Linux – the best one to date is Scalix and it costs about as much as Exchange does. It does not provide RPC-over-HTTP, it does not provide cached mode, it does not provide advanced connectivity to mobile devices.

ISA – For the most part almost all Linux firewalls are connection based firewalls, nothing provides application-level security. So yes, if you want to block people from going to certain sites, Linux will cut it. Try to set those restrictions in place per employee per hour (ie, no espn updates for Joe between 9AM and Noon) you’ll be SOL.

WSUS – Exists on commercial Linux distributions as a Satellite server but almost all are desktop triggered up2date updates via cron – no ability to see which software is running on which system and no ability to restrict what goes on which workstation without manually adjusting workstations on per-case basis. No grouping. No reporting on which patches failed and no reporting on what may be out of compliance. These could be hacked together but do you really want to hack your security solutions together? Do you think your customers would?

IIS – The biggest reason to deploy LAMP is to get PHP and a free SQL server. Both of those run quite reliably on Windows as well and you can install WAMP on Windows. My personal dev environment for Linux is based on Vertrigo server which rolls out as a single install. So if thats all you need to deploy a new forum, blog, or a survey package your customer saw somewhere – this is the way to do it. And it’s free too. But feature is an advantage here – you have a choice. ASP or PHP? On Linux you have no ASP advantage (they use Chilisoft, Sun’s poor hack of ASP) nor do they have any .NET compatibilities without hacking in mono – but skip back to migrations and upgrades – whats the guarantee that your app will run on a hacked server? Now compare that with IIS. If you’re really familiar with IIS this is almost impossible to do. The cost of a second IIS server is not that great to begin with, Windows 2003 Server Web Edition retails for less than $300 which is likely less than two hours of any consultants time. You’d end up charging them more to download an ISO and read the intro parts of the Apache documentation.

Bus Features

When I worked at Dial ISDN I used to write “If Vlad Gets Hit By A Bus” documentation for everything I did. Why? Because all of our Linux servers were so heavilly tweaked that in case something happened there was no way on earth someone would be able to figure out how I’ve implemented my patch management, version control, monitoring, account creation and race conditions.

How much documentation will the Linux deployment come with? How long will it take someone else to replicate the setup on a new system? What commercial contacts do you have that will validate what you say about Linux? How many “user-geared” books are there on Linux that can get me going with this server immediately? SMB owners are DIY-centric, how much of this can I do through a GUI?

Final question: Give me a place to find other professional Linux consultants.

Where you have hundreds of Windows guys in every area there are only a few Linux solution shops. Most of the “Linux guys” will be people with careers and full time jobs that do consulting on the side and are saving your money out of the goodness of their heart. These are also the types you turn to for support. Do you want to run your business on goodness of strangers or do you want a contract? If you want a contract the savings will go out the window.  

Conclusion

Linux provides a cost effective, flexible and powerful server operating system and Microsoft’s FUD about it is largely a collection of paid distortions, some quite well documented as outright lies. Microsoft will not offer competitive sales support to SMB solutions that are under $10,000 in licensing so you’re on your own. They will also not discuss any of the above because of the irrational fear that if you experience a competitive solution you might find enough in it that you like to leave Microsoft.

On the other end of the fence you have, by comparison, a relatively innovative but young solution that lacks the standardization, unity and certainty with many of its supposed solutions. While the core of it is solid the biggest lacking factors for small businesses are in the areas of available expertise and support systems to fall back on when there are problems. In the areas of affordable business intelligence Linux is behind enough to make it unattractive beyond file servers, basic pop3/imap mail servers and popular web applications. 

In the end, both sides will lie, cheat and FUD to get their points accross. Your advantage is in knowing your customer, knowing their needs, and showing them the solution that will not only solve their problems but be ready for the problems they will encounter as they grow. For what its worth, I’ve been a Linux system administrator for three years longer than I’ve been a Windows guy and work on both platforms daily. 

Update: Welcome LinuxToday.com visitors. As you get outraged at the article above please keep in mind that I own and operate a large ISP whose commodity-level services have been powered by Linux, FreeBSD, dovecot, IMP, Squirrelmail, vsftpd, bind, etc for close to a decade. We also own the largest deployment of Microsoft Small Business Server 2003 and constantly manage both platforms. If you have not seen what Microsoft has been up to for the past 3 or so years please don't waste your time posting comments about how "you can do it" and how "there are solutions that you can customize" because thats the entire point of the article, knowing the audience. Small business owners will not pay for "you to do it" they will only pay for as little labor as possible, which in turn makes the licensing cost negligible. So please don't think you've landed on some bashers site, this post is about recognizing the market.

When Piracy Pays Off

So you got in the office one day and that xxxxx-xxxxx-xxxxx-xxxxx-PRVMG XP Pro key is no longer working for you. Ouch, thats awful, now you have to pay for software like the rest of us. But wait, Uncle Bill has some good news for you. Unlike the legitimate Microsoft customers who are ripped the full $245, you as the criminal (or an unfortunate customer of a criminal) are rewarded! Yes, you get Windows XP Pro upgrade to a full legitimate copy for $100 less than the people that legitimately purchased Windows! No questions asked!
 
Image unavailable
 
I was a firm supporter of what Microsoft has been trying to do with licensing compliance when they gave free copies to people that turned in crooks but this latest move ENCOURAGES piracy, not the other way around. "Yes Bob, that PC is $399. However, if you run towards the door with it and steal it we'll only charge you $299 for it! It's our way of controlling theft." 
 
More screenshots and details on this at Daily Tech. 

Roadshow: No, WSUS can't do that

As mentioned earlier, I am on the road presenting a part of the security content for Microsoft Technet seminars and meeting partners and professionals all over the state. It is quite exciting and most of all - insightful. As a service provider I make my bacon fixing problems out there and sometimes you don't hear all the problems through your own feedback channels, you have to see people face to face.

The speach of the day: "WSUS doesn't fix stupid. I guarantee that nowhere in WSUS categories will you find a patch class for stupid user keeps on clicking on things. You can't fix stupid, but you can eliminate the amount of things they can be stupid with."

To put it into some context I opened my portion of the Microsoft event by saying that at least half of all the security problems with the Microsoft software are Microsofts fault. Not in terms of them writing insecure operating systems, but in terms of system administrators not applying service packs, patches and hotfixes in a timely manner. I held a quick poll asking people if they waited a few days to deploy critical patches. A surprising number of hands went up. Well folks, this is why your networks get pwned. If you don't have a clear schedule every second Tuesday of the month and plan to spend an hour or two at the Wednesday Technet webcast covering the patchday... well, update your resume. There is this notion that nobody wants to be the first to blow things up. Ok, fair enough - thats what testing is for folks. You test the service pack, you roll, you call PSS if you must to clean things up, you define a process. You don't stick your head in the sand, trust that Microsoft published every single thing that patch fixed and put your security in the hands of 16 year olds that got nothing to do between TRL and American Idol. Cleaning up a box with a broken patch is a hell of a lot easier than cleaning up a rootkit, if you even notice you've been pwned to begin with.

The other half of the security blame falls squarely on the user. You can patch your servers. You flash your firewalls. You can define strict firewall rules. You can turn up logging to find potential problems. You can backup. You can patch your workstations 15 different ways. But you can't fix stupid. If your junior admin got his MCSE from a paper-mill and his solution to NTFS permission problem is elevating end user security roles you've got a case of stupid going on. Give it up, you won't be able to train your accountant. Or your marketing guy. Or your boss (unless I'm your boss, in which case you can suck it monkeys - thats why I'm on a separate server than the rest of you serfs). They are untrainable. But you can train your staff. You can define a plan. You can set a schedule. You control your stupid exposure.

Security is a process. Do you have a clear one?

Ding Dong the FrontPage Is Dead!

The wicked witch of the Office system. Microsoft FrontPage will be gone and pull a Jesus move with Microsoft Office SharePoint Designer 2007:

The Microsoft® Office and Server & Tools teams are proud to announce the introduction of two great new tools for application building and Web authoring in 2006:

  1. Microsoft® Office SharePoint® Designer 2007: Automate your business processes and build efficient applications on top of the SharePoint platform, and tailor your SharePoint® site to your needs in an IT-managed environment.
  2. Microsoft® Expression™ Web Designer: Take advantage of the best of dynamic Web site design, enabling you to design, develop, and maintain exceptional standards-based Web sites.

These two new products will join the recently launched Microsoft® Visual Studio 2005, the next-generation tool for developers, to deliver a complete set of instruments for application building and Web authoring.

Good news for web developers, Windows platform, SharePoint collaboration. Bad news for commodity/cheap web hosting providers that have so far relied on RTR's ported version of Frontpage Server extensions to run FrontPage enabled sites and web bots on top of Linux and 8 other Unix platforms. There will be a lot of outcry from the hosting folks and people concerned that Microsoft is yet away locking away technology they previously opened but FrontPage extensions have been dead for quite some time. Honestly, not many will miss them, especially given all the cool stuff thats in SharePoint. So wake up folks, if you want to develop on the SharePoint platform you have to embrace the new technology, new dev tools and new way of doing things.

IIS 7: First Looks

Note: As a Microsoft MVP I'm entitled to some confidential information. All the information contained in this post is public knowledge and does not reflect the final product nor my experience with the beta. Legal stuff out the way: WOW IIS 7 is going to rock. While this will not be very exciting for the Apache faithful its going a long way to help out us IIS admins (hey, its no secret that Microsoft has been copying ncsa httpd / apache since day one - not only is it in the license but one of my close friends dropped out of college to work on IIS ISAPI in the long long ago). Like SQL server, the IIS 7 brings a very friendly XML interface and a 3 panel control panel. It also empowers the web site admin without granting system administrator priviledges (unix folk: read .htaccess). So here are some notes from a recent webcast: Metabase is gone! No more metabase hacks, all the configuration for IIS will be handled by XML files. If you've had a misfortune of dealing with DNN 4 or .NET development you know too well how much must be tweaked with web.config -- well its getting bigger. Not only will you be able to manage your web site (and more) with a web.config but all the configuration for IIS will be in the ApplicationHost.config XML file. Reduced Attack Surface & Enhanced Performance This makes IIS admins mouth water. For the longest time IIS (4/5/6) security involved loading various plugins, application firewalls, checkboxes, metabase hacks and one hotfix after another. Well, thats going away. Because capabilities of IIS7 will be controlled by different DLL's (instead of one major one) you'll be able to selectively turn features on/off (via XML!) and only open up what you need. This is awesome and way overdue. You know how you can restrict IIS from running .NET, FrontPage, WebDav, etc? Well, imagine being able to turn off things the same way you do in Apache with the backing of .NET. It's coming in IIS7. Think about the performance that a stripped down IIS can deliver - specifically if you're using IIS for image or video content serving farms. Tweaks and Wizards, oh my! With the additional functionality and options its going to get a lot more difficult to manage these servers. Do you really want to spend 20 minutes configuring each server to your liking or tweaking around XML files and keeping track of them? Well, IIS 7 will come with a lot more wizards to precisely tune your configuration without XML editing or reinventing the wheel. Of course you can tweak that through XML directly afterwards but the time savings will be significant. We were recently setting up a SQL cluster and Albert literally clicked through maybe 50 screens just to setup cluster aware COM+ properly. The bad news? Still not ready for performance testing. You will still be able to run ASP.NET 1.1 on IIS 7 which means you will still have to support yet another piece of old code which means it can be further ignored and obsoleted by your developers (until they have all found new jobs) and you'll be the one answering questions about why you're constantly being hacked because someone else hired incompetent developers. IIS 7 will only run on Longhorn / Vista so you will have to upgrade/migrate if you want the new feature sets. All in all, I am really looking forward to IIS 7. We manage a ton (well, many many tons in terms of steel alone) of IIS 6 and I would really love the ability to massively roll out and manage my IIS networks the same way we do for our Apache ones. It appears as if that is just around the corner!

Virtually Free Server R2

John Howard recently left Technet and moved on to become a Program Manager for Windows Virtualisation. Today he announces, on the heel of many rumors, that Virtual Server 2005 R2 is indeed free. Why, you may ask?

Although there are many reasons (see presspass site), the nutshell answer is relatively straightforward. If you look into the future of where we're heading with Windows Virtualisation in the Longhorn Server timeframe, virtualisation can be thought of as a "commodity" - commonplace, extensively used and most importantly free functionality out of the box. Windows Virtualisation will include full migration capability from Virtual Server 2005 R2 to Windows Virtualisation, so this is somewhat of a no-brainer to get people onto the next release.

Enterprise edition is free, both 32bit and 64bit one.

Microsofts Desktop Live Strategy

Found a cool new blog with a cool old story but I feel it warrants mentioning if only for the cool community features it brings to the table. Cool! The Live Mail Desktop blog is outlining the features that will be available in the next incarnation of Outlook Express (Windows Vista Mail) and Windows Live Desktop Mail. Windows Vista Mail ... brings the Outlook Express core features plus community integration (Microsoft newsgroups), file based databases for mail and contacts, integrated search with Vista, as well as a spam/phishing protection and spell check. Windows Live Desktop Mail ... goes a few steps further. It integrates an RSS reader, Blog It! features, Photomail, emoticons, separate POP3 inbox folders. This is great news.. for Jen & Sarah and Gmail. You see, these two will hump anything with a Google logo on it. It's kind of like Microsoft Koolade, the undying loyalty for crappy beta-level applications. While there is slim to no chance that Blog It! will integrate with third party blogging tools this might give a lot of folks that rely on Gmail that offline/archiving functionality that is simply critical. Jen recently had a mental breakdown over Gmail going down ("Gmail is ungodly") and she couldn't get to her homework. Now I'll give you that she is a PR major and doesn't understand the meaning of free or beta or TINSTAFL but it illustrates the biggest problem with "free" services in that there is simply no guarantee, no support and no expectation whatsoever. How do I explain this to my PR folks out there... "If it breaks it cannot be unbrokened." There is no support Indian to call, there is nothing you can threaten to sue because you already gave ownership of all your mail to Google (yes dear, read the agreement you accepted to open the account), and you have no backup because.... well, why would you backup if you have 2GB of storage? Right? Right? Wrong. So how do you use Windows Mail in the most suicidal way with Gmail? Well, open two Gmail accounts. Setup the first account with Gmail as pop3 and then store your nightly backups in the second Gmail account using GMail Drive.