MAPI communication with Exchange 2010

If you're having fun with a pre-2007 version of Outlook, or any non-Microsoft product trying to talk MAPI to an Exchange 2010 server you might be interested in knowing that the defaults have now changed in the new version, and it expects traffic to be encrypted. This caught us out today as we'd only tested Outlook 2007 before rolling one of our boxes over to 2010 over the weekend.

Two options;

  1. Disable the encryption requirement, although this isn't recommended Set-RpcClientAccess –identity SERVERNAME –EncryptionRequired $false
  2. Enable encryption for the MAPI connection (for Outlook 2003 this is under the More Settings, Security tab)

Acronyms, acronyms, acronyms

"Engineers are really good at labeling and branding things," said his sarcasm. "If we had named Kentucky Fried Chicken, it would have been Hot Dead Birds." - Vint Cerf

Zend Framework and the PHP Sqlsrv extension

On the off chance you're intending to do any development with using SqlSrv and ZF, I'd suggest taking a cursory look at ZF-7431 before hand. Equally if you're planning on doing any dev with Sqlsrv and plan to migrate to other SQL platforms later, then it could be just as helpful.

The fact that SqlSrv will return PHP objects is rather nice, unless you already have existing code that assumes strings are returned, like almost all other database extensions available for PHP. The easiest "fix" to allow your code to work across as many systems as possible is to ensure that you pass in ReturnDatesAsStrings as an option.

Vendor documentation scares me most of all

Today I noticed a page appear on technet detailing the use of Windows Home Server in a Small Business Server environment, to backup your desktops. This made me cringe.

In an environment where companies, who are or want to be total or near-total Microsoft setups, are trying to spend less money Microsoft's documentation team are advising the use of a product which many very small customers are looking to as an alternative to SBS. After all why bother with SBS when you can use WHS and Google (or any number of other hosted service providers) for mail/calendaring/sharepoint/wiki services?

For some companies WHS and hosted services might well be a good thing. For the purposes of the rest of my post I'll be ignoring this and assuming the company already has a SBS installation.

The thing that scares me most about this document is the fact that it exists. I really don't see the point of using WHS in a SBS environment. I mean, obviously, you technically can. I just don't see why you would want to. You should be educating your users to never store anything critical in an area that isn't backed up. In combination with redirected folders and/or roaming profiles, and network drives you shouldn't have a problem. By doing this early on you won't need to re-educate your users as you grow. Even if you do have a special desktop that has some magic bit of software, then you should have a special procedure just for that desktop or you should consider replacing it with an alternative item of software/hardware and eliminate the single point of failure. But what about laptops, I hear you cry? That's irrelevant as the laptops still need to be on-site or VPN'ed in to be covered by WHS.

The document strikes me as being aimed at someone who either doesn't know what SBS is capable of underneath the pretty console (in which case should the functionality not be exposed, or explained more clearly?), or as a method of bringing in more revenue.

Perhaps I'm just cynical, but the answer seems to be one of managing documentation. SBS builds on other products and perhaps it could benefit from including or referencing these other product documentation libraries more frequently? Admitedly I don't write documentation for living, but it does still seems logical to me...

HP PSC printers and Terminal Servers

I've written about specifying drivers for redirected printers in the past, but it's not something I've had to do for a few months.

Last week we had to get a 1500 series HP PSC working on a home workers terminal server session, and it turns out that the "proper" driver isn't correct and doesn't install. Luckily it seems that a lot of the HP PSC's use the same internals as the HP Deskjet series. As most of the Deskjet series work with the Deskjet 550C driver we tried the 550C for the HP PSC 1500, and it works like a dream.

Just thought the world might be interesting in knowing.