So right now, I’m somewhat in a quandry. “Why John”, I hear you ask. “Well readers”, I respond: At TechEd Europe this year, I’m going to present a couple of sessions. One will be around the contents of the Solution Accelerator for Consolidating and Migrating LOB (Line of Business) Applications. Here’s the official summary of the SA:
This Solution Accelerator package provides technical information and recommendations, processes, build notes, job aids, test scripts, and documented test validation of the processes. The objective of the documentation set is to enable partners and enterprise customers to efficiently consolidate and migrate their existing Windows NT 4.0 based line-of-business (LOB) applications to Windows Server 2003-based technologies, including .NET Framework 1.1, WSRM, and Virtual Server 2005.
Now as it happens, the Virtual Server Migration Toolkit (VSMT) has a big part to play in this in terms of the migration to Virtual Server 2005 solution part. Naturally, I’ll be doing a demonstration of a migration live – it’s a pretty impressive demo to see live and I always get some great feedback when people see it for real. However, note the particular part of the summary above “…their existing Windows NT 4.0 based“. The SA is equally applicable to Windows 2000 (and Windows Server 2003), but doesn’t go to town mentioning this. Now, do I (as a Microsoft Employee, remember) stand up and show a Windows NT4 based machine being migrated, which is now “end of life” for want of a better term, or do I bend the rules slightly and show a Windows 2000 Server being migrated. At the UK Technical roadshows over the past few weeks, I’ve been doing a similar demonstration using Windows 2000 as the server being migrated, simply on account of the “end of life”-ness of NT4.
I’d appreciate a quick comment with your thoughts – play it safe, or be a rebel? FWIW – I’m swaying towards Rebel, but if you were in the audience and saw something which wasn’t explicit in the material being talked about, would you mark the session down?