Alivad.Com

iTWire: To give your Microsoft Exchange users the most flexible access options you really need an independent verified SSL certificate. Here’s how to do it fast and efficiently with a minimum of fuss and confusion.

iTWire: The problem with corporate networks is they not only stop the bad guys coming in but also your users who want to work remotely, whether at home, at a client site or on the road. Here is where a VPN product comes in, and the simplest to deploy on Windows is a Linux virtual appliance called OpenVPN.

Thanks to Andrew Coates, I’ve just registered to take Microsoft exam 70-642 on Windows Server 2008 networking, next week.

I’m also interested in doing 70-640 but for some reason the Prometric web site didn’t list English as a language choice … !

You know a virus is big news when suddenly your users start asking about it instead of the usual “Good news” hoax variants (you know, “my friend’s brother’s uncle’s IT guy said don’t open an e-mail with the title ‘good news’ or it will melt your whole computer and eat your house. Microsoft has said there is NO cure !!!!!!”)

Now, good network admins already have their infrastructure under control – both for present and for future threats.

So, it’s prudent to send out an affirming message at this time letting your users know that they can have confidence their data will be protected from harm and they won’t suffer downtime.

Here are some template e-mails you can use – and not just for Windows, but for the Linux and MacOS guys too!

iTWire: With virtualisation becoming a mainstream technology, it’s becoming reasonable that Linux distros like Ubuntu will not always require a dedicated computer but instead be contained within a virtualised environment, whether on a Windows desktop or as part of a consolidated server farm. It’s not always plain sailing though – here are some problems you might encounter as well as their solutions.

ITWire: Here’s a real-world Linux app written for, and used by, an ISP. It gave help desk staff the ability to perform any sysadmin task which could be scripted for them. The app gave a controlled menu environment, using sudo to launch scripts with elevated permissions if necessary.

Digg it here.

It’s well known now that Windows Vista is suffering from backwards-compatibility issues (and to be fair, not necessarily Microsoft’s fault but that of sluggish third-party vendors.) I’ve written about this on mailing lists and other sites and once here.

What’s received a lot less publicity – owing to being less for the general public – is the 64-bit nature of Microsoft Exchange Server 2007.

I’ve started my new role as CIO for an exciting startup company (and, by the way, I chose the ASUS Lamborghini VX2 laptop.) Although there will be a lot of strategy required soon, the immediate task is to get an online presence.

I bought a 64-bit HP server with dual Xeon processors and 4Gb RAM. It’s running Windows Server 2003 standard – 64-bit edition – and Exchange 2007. The Exchange install was a breeze; Microsoft have made an excellent job of reducing its complexity and giving it a very focused administrative interface. I had it running quickly, along with OWA.

After a day of running this, I felt confident enough to move along and install BlackBerry Enterprise Server 4.1.3. Now, everyone who knows me know I am a rabid BlackBerry enthusiast. I’ve been involved in IBBUG (before they just seemed to die out …), I’ve sent well over 10,000 thumb-typed messages and I’ve advocated BlackBerry among the tech and journo communities. However, I really have to vent my rage on RIM for mucking up my server here ……..

Oh, the BES install was flawless – with one minor problem; BES 4.1.3 complained that MAPI was not available. A quick Google gave a download link from Microsoft for the benefit of Exchange 2007 users, as this component no longer ships with the product. That satisfied BES and the install completed.

However ……. my dummy web site no longer worked. Nor did OWA. (And sure, it’s not best practice to run mail and web and BlackBerry all on the one machine, but hey, we’re a startup – and it cost over $36K for this kit as it was!)

At first I wondered if the BES’ new MDS services were at fault, possibly having set itself in place as the machine’s web server. Yet IIS was indeed still running – but the application pools had failed to start for “unspecified easons”. A trawl through the application log revealed a .NET framework mismatch – and oddly enough I then noticed IIS listed .NET framework 1.1 as being available but .NET framework 2.0 had disappeared.

Repairing the .NET framework 2.0 got me further – the dummy web site returned and OWA’s login page showed – but it was still not perfect; clicking login just gave an error page. IIS no longer listed any problems with the application pools – but it did list the .NET framework 2.0 as being in 32-bit mode. That got me thinking, given Exchange 2007 is a 64-bit system.

To cut to the chase – the BES wouldn’t run without .NET framework v1.1 installed; it gave C++ run-time errors when removed. Yet, with it, IIS was slashed down to operating in 32-bit mode – and this was no good for OWA.

The end result? .NET 1.1 is gone, .NET 2.0 was repaired again, and IIS returned to 64-bit mode. So, I have OWA back but no BES. I considered trying out the two BES 4.1.3 hotfixes out but it was getting late. My thinking now is to leave as is, and set up POP for the benefit of the BlackBerry handhelds at this time. After all, we’re a startup: we have a sum total of two handhelds at the moment (the spiffing 8800 model.) I’ll return to the BES with a dedicated machine once our usage is heavier.

So, Vista is not the only modern Microsoft environment with compatibility problems. I can do one better and bring the two together: previously Exchange shipped with management tools for use on desktop operating systems. The Exchange 2007 DVD did not. The explanation I got was because it’s a 64-bit system and most client PCs are 32-bit, although that was fairly lame. In fact, I found a link on Microsoft’s web site where the 32-bit management tools for Exchange 2007 can be downloaded so they definitely exist but just didn’t get included on the DVD.

It’s all moot though: one of the first steps in the installation prompts for Microsoft’s new PowerShell to be installed. 32- and 64-bit versions exist but here’s the rub: they’re only for Windows XP or Windows Server 2003. There’s no Vista release. Trying to install the 32-bit XP version just fails. So, ultimately, Vista and Exchange 2007 have such compatibility problems that they don’t even cohabit.