Two methods of avoiding Windows Vista product activation

This content is 18 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

A few months back, I wrote about how Windows Vista product activation works for volume license customers.  Last night I was searching to find out what the grace period is before activation is required and I stumbled across some interesting articles. You see, it turns out that there are three main problems with product activation:

  • Corporate IT departments want to produce customised Windows builds.  These builds must be valid when deployed to client PCs (i.e. the product activation period must not have expired!) and, as the product activation timer is ticking away during the customisation process, there needs to be a method to “rearm” product activation.
  • OEMs want to ship pre-activated versions of the operating system (an arrangement with which I’m sure Microsoft are happy to comply as they need OEMs to preload their operating system and not an alternative, like, let’s say… Ubuntu Linux!), so Microsoft provides these so-called Royalty OEMs with special product keys which require no further activation, under as scheme known as system-locked pre-installation (SLP) or OEM activation (OA) 2.0.
  • Anti-piracy measures like product activation is that they are to hackers like a red rag is to a bull.

The net result, it seems, is two methods to avoid product activation.  The first method, can be used to simply delay product activation, as described by Brian Livingston at Windows Secrets. It uses an operating system command (slmgr.vbs -rearm), to reset the grace period for product activation back to a full 30 days.  The Windows Secrets article also describes a registry key (HKEY_LOCAL_MACHINE\ SOFTWARE\Microsoft\Windows NT\CurrentVersion\SL\SkipRearm) and claims that it can be set to 00000001 before rearming, allowing the rearm to take place multiple times (this registry key is reset by the rearm command, which is also available by running rundll32 slc.dll,SLReArmWindows); however, Microsoft claims that the SkipRearm key is ineffective for the purpose of extending the grace period as it actually just stops sysprep /generate (another command used during the imaging process) from rearming activation (something which can only be done three times) and does not actually reset the grace period (this is confirmed in the Windows Vista Technical Library documentation).  Regardless of that fact, the rearm process can still be run three times, giving up to 120 days of unactivated use (30 days, plus three more rearms, each one providing an additional 30 days). That sounds very useful for both product evaluation and for corporate deployments – thank you very much Microsoft.  According to Gregg Keizer at Computer World/PC World Magazine, a Microsoft spokesperson has even confirmed that it’s not even a violation of the EULA.  That is good.

So that’s the legal method; however some enterprising hackers have a second method, which avoids activation full stop.  Basically it tricks the operating system into thinking that its running on a certain OEM’s machine, before installing the relevant certificate and product key to activate that copy of Windows.  The early (paradox) version involved making hex edits to the BIOS (hmm… buy a copy of Windows or turn my PC into a doorstop, I know which I’ll choose) but the latest (vstaldr) version even has an installer for various OEMs, and if that doesn’t work then there is a list of product keys which can be installed and activated using two operating system commands:

slmgr.vbs -ipk productkey
slmgr.vbs -ato

I couldn’t possibly confirm or deny whether or not that method works… but Microsoft’s reaction to the OEM BIOS hacks would suggest that this is not a hoax.  Microsoft’s Senior Product Manager for Windows Genuine Advantage (WGA), Alex Kochis, describes the paradox method as:

“It is a pretty labor-intensive [sic] process and quite risky.”

(as I indicated above).  Commenting on the vstaldr method, he said:

“While this method is easier to implement for the end user, it’s also easier to detect and respond to than a method that involves directly modifying the BIOS of the motherboard”

Before continuing to hint at how Microsoft may respond:

“We focus on hacks that pose threats to our customers, partners and products.  It’s worth noting we also prioritize our responses, because not every attempt deserves the same level of response. Our goal isn’t to stop every ‘mad scientist’ that’s on a mission to hack Windows.  Our first goal is to disrupt the business model of organized counterfeiters and protect users from becoming unknowing victims.   This means focusing on responding to hacks that are scalable and can easily be commercialized, thereby making victims out of well-intentioned customers.”

Which I will paraphrase as “it may work today, but don’t count on it always being that way”.

Ask for genuine Microsoft softwareNote that I’m not encouraging anybody to run an improperly licensed copy of Windows.  That would be very, very naughty. I’m merely pointing out that measures like product activation (as for any form of DRM) are more of an inconvenience to genuine users than they are a countermeasure against software piracy.

Disclaimer

This post is for informational purposes only. Please support genuine software.

Get a Mac? Maybe, but Windows Vista offers a more complete package than you might think

This content is 18 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

I’ll freely admit that I have been critical of Windows Vista at times and I’ll stand by my comments published in Computer Weekly last November – Windows XP will remain in mainstream use for quite some time. Having said that, I can’t see Mac OS X or Linux taking the corporate desktop by storm and the move to Vista is inevitable, just not really a priority for many organisations right now.

Taking off my corporate hat one evening last week, I made the trip to Microsoft’s UK headquarters in Reading for an event entitled “Vista after hours”. Hosted by James Senior and Matt McSpirit it was a demo-heavy and PowerPoint-light tour of some of the features in Windows Vista that we can make use of when we’re not working. Not being a gamer and having bought a Mac last year, I’ve never really paid attention to Microsoft’s digital home experience but I was, quite frankly, blown away by what I saw.

The first portion of the evening looked at some of the out-of-the-box functionality in Windows Vista, covering topics like search, drilling down by searching within results, using metadata to tag objects, live previews and saving search queries for later recall as well as network diagnosis and repair. Nothing mind-blowing there but well-executed all the same. Other topics covered included the use of:

  • Windows Photo Gallery (which includes support for the major, unprocessed, raw mode formats as well as more common, compressed, JPEG images) to perform simple photo edits and even to restore to the original image (cf. a photographic negative).
  • Windows Movie Maker to produce movies up to 1080p.
  • Windows DVD Maker to produce DVD menus with support for both NTSC and PAL as well as 4:3 and 16:9 aspect ratios.
  • Windows Media Player to organise media in many ways (stack/sort by genre, year, songs, album, artist, rating, recently added, etc.) and share that media.

Apple Macintosh users will think “yeah, I have iPhoto, iMovie, iDVD and iTunes to do all that” and they would be correct but Apple says (or at least implies in its advertising) that it’s hard to do these things on a PC – with Vista it’s just not… which moves me on to backup – not provided (at least in GUI form) by the current Mac OS X release (only with a .Mac subscription) and much improved in Windows Vista. “Ah yes, but Leopard will include Time Machine!”, say the Mac users – Windows has had included the volume shadow copy service (VSS/VSC) since Windows XP and Windows Backup includes support for multiple file versions right now as well as both standard disk-based backups and snapshots to virtual hard disk (.VHD) images, which can then be used as a restore point or mounted in Virtual PC/Virtual Server as a non-bootable disk. Now that does sound good to me and I’m sure there must be a way to make the .VHD bootable for physical to virtual (P2V) and virtual to physical (V2P) migrations… maybe that’s something to have a play with another day.

Regardless of all the new Vista functionality, for me, the most interesting part of the first session was Windows Home Server. I’m a registered beta user for this product but must confess I haven’t got around to installing it yet. Well, I will – in fact I’m downloading the April CTP as I write this. Based on Windows 2003 Small Business Server, it provides a centralised console for management of and access to information stored at home. Microsoft claim that it has low hardware requirements – just a large hard disk – I guess low hardware requirements is a subjective term (and I figure that my idea of low hardware requirements and Microsoft’s may differ somewhat), nevertheless it offers the opportunity to secure data (home computer backup and restore, including scheduling), provide centralised storage (a single storage pool, broken out as shared storage, PC backups, operating system and free space), monitor network health (i.e. identify unsafe machines on the network), provide remote access (via an HTTPS connection to a defined web address) and stream media, all controlled through a central console. Because the product is aimed at consumers, ease of use will be key to its success and it includes some nice touches like scheduled backups and automatic router configuration for remote access. Each client computer requires a connection pack in order to allow Home Server to manage it (including associating account information for secuirity purposes) and, in response to one of my questions, Microsoft confirmed that there will be support for non-Windows clents (e.g. Mac OS X 10.5 and even Linux). Unfortunately, product pricing has not yet been released and early indications are that this will be an OEM-only product; that will be a great shame for many users who would like to put an old PC to use as a home server.

Another area covered in the first session was parental controls – not really something that I worry about right now but maybe I will over the next few years as my children start to use computers. Windows Vista includes the ability for parents to monotor their child’s activities including websites, applications, e-mail, instant messages and media. Web filters can be used to prevent access to certain content with an HTTP 450 response, including a link for a parent to approve and unblock access to the content as well as time limits on access (providing a warning before forcing a logout). Similarly, certain games can be blocked for younger users of the family PC. The volume and diversity of the questions at the event would indicate that Vista’s parental controls are fairly simplistic and will not be suitable for all (for example, time limits are on computer access as a whole and not for a particular application, so it’s not possible to allow a child access to the computer to complete their homework but to limit games to a certain period in the evening and at weekends).

If session one had whetted my appetite for Vista, session two (Vista: Extended) blew my mind and by the time I went home, I was buzzing…

I first heard of Windows SideShow as a way to access certain content with a secondary display, e.g. to provide information about urgent e-mails and upcoming appointments on the lid of a laptop computer but it actually offers far more than this – in fact, the potential for SideShow devices is huge. Connectivity can be provided by USB, Wi-Fi, Bluetooth – Windows doesn’t care – and the home automation possibilities are endless. I can really see the day when my fridge includes capabilities for ordering groceries via a SideShow display in the door. There is at least one website devoted to SideShow devices but James Senior demonstrated a laptop bag with a built-in SideShow controller including a cache for media playback. Typically used to expose information from a Windows Sidebar gadget, SideShow devices will wake up a sleeping computer to synchrosise content then put it back to sleep and can be secured with a PIN or even erased when logged off. Access is controlled within the Windows Control Panel and there is an emulator available to simulate SideShow devices.

As elegant as Apple Front Row is, for once Microsoft outshines the competition with Windows Media Center

Next up was Windows Media Center. Unlike with the Windows XP Media Center and Tablet PC editions, Microsoft no longer provides a separate SKU for this functionality, although it is not enabled in all Vista product editions. Media Center is a full-screen application that offers a complete home media hub – sort of like Apple Front Row but with support for TV tuners to include personal video recorder (PVR) functionality. As elegant as Apple Front Row is, for once Microsoft outshines the competition with Windows Media Center – multiple TV tuners can be installed (e.g. to pause live TV, or to record two items at once, as well as the elctronic programme guide (EPG), controls, etc. being displayed as an overlay on the currently playing content. As with Windows Media Player, visualisations are provided and in theory it ought to be possible to remote control a Media Center PC via Windows Home Server and set up a recording remotely. Individual programs, or whole series, can be recorded and many TV tuners include DVB-T (digital terrestrial) support (i.e. Freeview), with other devices such as satellite and cable TV decoders needing a kludge with a remote infra-red controller (a limitation of Sky/Virgin Media network access rather than with Windows). Other functionality includes RSS support as well as integration with Windows Live Messenger and some basic parental controls (not as extensive as elsewhere in Windows Vista but nevertheless allowing a PIN to be set on certain recordings).

The event was also my first opportunity to look at a Zune. It may be a rather half-hearted attempt at producing a media player (no podcast support and, crucially, no support for Microsoft’s own PlaysForSure initiative) but in terms of form-factor it actually looks pretty good – and it includes functionality that’s missing from current iPods like a radio. If only Apple could produce an iPod with a similarly-sized widescreen display (not the iPhone) then I’d be more than happy. It also seems logical to me that as soon as iTunes is DRM-free then the iTunes/iPod monopoly will be broken as we should be able to use music purchased from the largest online music store (iTunes) on the world’s favourite portable media player (iPod) together with Windows Media Center… anyway, I digress…

I mentioned earlier that I’m not a gamer. Even so, the Xbox 360‘s ability to integrate with Windows PCs is an impressive component of the Microsoft’s digital home experience arsenal. With its dashboard interface based around a system of “blades”, the Xbox 360 is more than just a games machine:

As well as the Xbox 360 Core and Xbox 360 Pro (chrome) systems Microsoft has launched the Xbox 360 Elite in the United States – a black version with a 120GB hard disk and HDMI connectivity, although it’s not yet available here in the UK (and there are also some limited edition Yellow Xbox 360s to commemorate the Simpsons movie).

Finally, Microsoft demostrated Games for Windows Livebringing the XBox 360 Live experience to Windows Vista-based PC gaming. With an Xbox 360 wireless gaming receiver for Windows, Vista PC gamers can even use an Xbox 360 wireless controller (and not just for gaming – James Senior demonstrated using it to navigate Windows Live maps, including the 3D and bird’s eye views). Not all games that are available for both PCs and the Xbox will offer the cross-platform live experience; however the first one that will is called Shadowrun (and is due for release on 1 June 2007) bringing two of the largest gaming platforms together and providing a seamless user experience (marred only by the marketing decision to have two types of account – silver for PC-PC interaction and gold for PC-XBox).

Apple’s Get a Mac campaign draws on far too many half truths that will only become apparent to users after they have made the decision to switch… and then found out that the grass is not all green on the other side

So, after all this, would I choose a Mac or a Windows PC? (or a Linux PC?) Well, like so many comparisons, it’s just not that simple. I love my Mac, but Apple’s Get a Mac campaign draws on far too many half truths that will only become apparent to users after they have made the decision to switch, splashed out on the (admittedly rather nice) Apple hardware and then found out that the grass is not all green on the other side. In addition, Apple’s decision to delay the next release of OS X whilst they try to enter the mobile phone market makes me question how committed to the Macintosh platform they really are. Linux is good for techies and, if you can support yourself, it has the potential to be free of charge. If you do need support though, some Linux distros can be more expensive than Windows. So what about Windows, still dominant and almost universally despised by anyone who realises that there is a choice? Actually, Windows Vista is rather good. It may still have far too much legacy code for my liking (which is bound to affect security and stability) but it’s nowhere near as bad as the competition would have us thinking… in fact it hasn’t been bad since everything moved over to the NT codebase and, complicated though the product versions may be, Windows Vista includes alternatives to the iLife suite shipped with a new Macs as well as a superior media hub. Add the Xbox integration and Windows SideShow into the mix and the Microsoft digital home experience is excellent. Consumers really shouldn’t write off Windows Vista just yet.

Coding horror

This content is 18 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

I just stumbled upon Jeff Atwood’s Coding Horror blog and it’s very interesting reading (even for those of us who write very little code). The article that I found was commenting on Jakob Nielsen’s latest tome on web usability. Although Nielsen makes some valid points, the comments are worth a read as they highlight some of the real compromises that website designers and website developers have to make.

I’m sure I could lose many hours reading Jeff’s writing but they all seem well-informed, to the point and interesting… these were just a few of the posts that grabbed my attention this afternoon:

  • When in doubt, make it public looks at how Web 2.0 is really just creating websites out of old Unix commands and that the new business models are really about taking what was once private and making it public!
  • SEOs: the new pornographers of the web looks at how much of the real search engine optimisation is just good web development and that many of the organisations focusing on SEO are all about money and connections – whether or not the assertions that Jeff makes in his post are correct, it’s an interesting view and certainly seems to have a lot of SEOs fighting their corner.
  • Why does Vista use all my memory? looks at how Windows Vista’s approach to memory management (a feature called SuperFetch) and how grabbing all the available memory to use it as a big cache is not necessarily a bad thing.

Don’t be misled by the Windows Vista myths

This content is 18 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

In recent months, there has been a lot of criticism of Microsoft Windows Vista in the press and elsewhere – I know because I wrote some of it; however it’s good to see Deb Shinder’s TechRepublic article entitled don’t be misled by these 10 Windows Vista myths, which seems to be a thoughtful and well-reasoned view of why a lot of the hype (both from Microsoft and from the anti-Microsoft camp) needs to be taken with a pinch of salt.

Unfortunately, many of the comments posted about the article are ill-informed, or even just plain old trolling. Somewhat ironically, I came across the article via MacBreak Weekly (episode 28) – a podcast which often displays Apple fanboy tendencies.

Upgrading my Mac to run Vista

This content is 18 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

“Hah! How can installing Windows on a Mac be an upgrade?”, I hear you ask – surely that’s tainting all that Apple wholesomeness with a BSOD-inducing, spyware-ridden, unreliable piece of software – at least, that’s the impression that you will get if you listen to Scott Bourne

Back in the land of all that is operating system-agnostic, my Mac has been running Mac OS X (most of the time) and Windows XP (a fraction of the time) since the end of July and, as it’s the most advanced piece of PC hardware that I have, I decided to upgrade my Windows partition to Vista. The first thing to note is that Apple only supports Windows XP SP2 for Boot Camp (although others have managed to use alternative operating systems successfully), but then Boot Camp is also beta software (i.e. with limited support) so, not to much to lose then!

I booted into Windows XP, inserted the Vista DVD and ran the upgrade advisor (third time lucky as it first insisted that I install the Microsoft XML Parser 6.0 and then the Microsoft .NET Framework 2.0) after which was very pleased to see that my hardware would run Vista Ultimate with all the 3D effects so I could finally experience Aero glass first-hand (I’ve seen it demonstrated but all the PCs I’ve run Vista on up to now have had low-end onboard graphics cards). The upgrade advisor warned me about a few devices for which it didn’t have drivers (SigmaTel High Definition Audio Codec, Apple Built-In Bluetooth and Canon CanoScan N650U/N656U) as well a couple of applications that may have problems post-installation (Symantec AntiVirus Client and Windows Messenger) but as there were no show-stoppers I went ahead with the upgrade (Vista also gave me the option to perform a clean installation, but I figured upgrading from an existing Windows XP installation with all the correct drivers would be a good starting point).

The upgrade itself was smooth and after a while I had a running Windows Vista Ultimate Edition system (not yet activated). As could be expected, Windows wanted to locate some missing drivers, but strangely they weren’t the ones previously identified by the upgrade advisor: firstly there was my Nikon LS4000ED film scanner (for which the Windows XP driver seemed to work); and another device that stopped working during the upgrade was my graphics tablet, although Wacom has a beta driver for Windows Vista that was easily downloaded and installed, following which the tablet PC input panel appeared. More worryingly, Mediafour MacDrive 6 stopped working under Vista so I have no access to non-Windows partitions and, annoyingly, there was no mention of this from the upgrade advisor, nor does a search for “vista” on the Mediafour website turn up any results (I have since opened a support request and been referred to an article which states that Vista is not supported – apparently that will be in MacDrive 7 next year, and will cost me some more cash). Although I was able to work through the driver issues (if not the MacDrive application issue) I have to question exactly what is the point of an upgrade advisor that doesn’t identify all the likely issues?

Because I had upgraded from a working XP installation that was using Boot Camp v1.0.2 drivers, most of my Mac hardware was recognised by Windows (and Vista was even able to find a driver online for one device that hadn’t previously worked – the Infineon Trusted Platform Module). Even so, more recent versions of Boot Camp provide additional device support – like being able to use F14 for PrtScr – so I decided to upgrade the Apple Keyboard driver. After creating an updated driver CD using the Boot Camp Assistant v1.1.2 under Mac OS X, Tim Gaden’s article on wrangling Boot Camp v1.1.2 drivers into Windows Vista guided me through extracting the driver files to a location on my hard disk (“D:\Install Macintosh Drivers for Windows XP.exe” /A /v), from where I was able to locate the Apple Keyboard driver (in locationofextractedfiles\program files\Macintosh Drivers for Windows XP 1.1.2\Apple Keyboard\) and run the setup wizard. Tim’s article was written for Vista RC2, but I can confirm that the same fatal error occurs with the RTM build (build 6000) if the /a /v switches are not used to extract the setup files and run them individually.

Feature transfer error: Error -1603 Fatal error during installation

Once the Apple Keyboard driver was properly installed, I could use the extra function keys but as the UK Apple keyboard lacks a # character, I couldn’t type # directly (Alt+3 no longer works) although Alt+035 does the trick (note that the 035 must be typed on the number pad, not using the numeric keys above above qwertyuiop).

There were still a couple of devices with warnings in Device Manager – no driver seems to be available for the performance counters (at least that’s one step ahead of the Windows XP installation which simply referred to this item as a PCI device) and I have a USB Human Interface Device for which the drivers won’t start (hardware ID USB\VID_05AC&PID_8240&REV_0110 – this was also unrecognised under XP and 05AC denotes Apple but I’m not sure which device 8240 relates to). Sadly, the Apple remote still doesn’t work – a shame really as I much prefer Microsoft’s Windows Media Center to Apple’s FrontRow.

During the upgrade, I also noticed a nice feature as I held down the Alt/option key on each reboot to select the Windows partition – as well as Macintosh HD and Windows, the boot loader offered the choice of booting from the Windows DVD (I’m not sure if this is available to Mac users without Boot Camp?).

I have previously criticised the Vista user interface but I’m finding that I actually like the full experience with all the 3D effects turned on (sorry Microsoft). Flip 3D is cool; so is the taskbar thumbnail preview; and I like the way that Windows fade in/out as I maximise/minimise them.

Flip-3D

Thumbnail preview

Extolling the virtues of Vista’s user interface does not in any way reverse the opinion I have previously expressed as a Microsoft business customer – by and large, corporates don’t care about 3D graphics and the main requirement is for a reliable and secure operating system, something for which only time can tell if Windows Vista is or is not.

As for those who point out the similarities between Windows Vista and Mac OS X (I did blog about the spoof videos earlier this year and yes, I have seen David Pogue’s video article on the New York Times site, to which it should be added that Pogue is a well-known Mac user – he even writes books about Apple software!), let’s play that particular criticism back another way (which I haven’t seen anybody comment on)… it’s well publicised that it took many years for Microsoft to write Vista and Microsoft is far less secretive about new features than Apple is – who says that Apple didn’t steal some of Microsoft’s ideas in the meantime and bring them to market first? After all, the much acclaimed Time Machine feature in the forthcoming version of OS X sounds very like a feature we have had in Windows for years (the volume shadow copy service). Or maybe (and more likely in my opinion), consumers expect features like a calendar application and digital media management built in to our operating system (heaven knows that Outlook Express was long overdue an update). As for gadgets/widgets and desktop search (Spotlight) – they are not Apple inventions either (in fact, many Mac users eschew Mac OS X’s Spotlight search in favour of Quicksilver).

I’ll still be running Mac OS X most of the time (at home anyway – I need to use Linux and Windows XP for work) but it’s good to be able to test Vista in all it’s glory and it seems to run well on my Mac Mini. In fairness, I do have a Core Duo processor and 2GB of RAM, but it feels responsive (at least as much so as OS X) and the overall experience is positive – and that’s on a machine which only scores a Windows experience index of 3.0 (dragged down by the built-in Intel GMA950 graphics – the other metrics are all above 4).

Performance information and tools

As I’ve written previously, Windows Vista is a fantastic achievement on Microsoft’s part, although I do wish that there had been simultaneous consumer and business launches (if only to stop all this ¨we don’t support it because it’s not available yet¨ nonsense from software vendors who should have been getting ready for Vista months ago). Now we just need to stop all the noise from David Pogue and others about how Microsoft copied Apple and just live with the fact that Vista will be on hundreds of millions of PCs by this time next year – regardless of whether or not it is the best operating system. Despite my initial reservations, I like running Mac OS X, I also like running Linux, and I like running Windows too – they all have their good and bad points so let’s play nicely together.

(In the interests of my operating system-agnostic credentials, I should add that I started to write this post on a PC running Fedora Core 5 whilst the Mac was being upgraded, then I switched to the Mac, adding details whilst booted under both Windows Vista and Mac OS X!)

Keeping up with the news (plus some tips for Windows Vista)

This content is 18 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Clicking through from one of Victor Laurie’s sites, I found Ed Bott’s 10 expert tips and tweaks for Windows Vista – it looks as though there are some nice tips there.

I regularly read Paul Thurrott‘s writing (as well as listening to his Windows Weekly podcast with Leo Laporte) and I occasionally check out what Stephen Bink and Ryan Hoffman have to say but it seems Ed Bott’s Microsoft Report is another useful resource for those keeping up-to-date with the latest news from Redmond (there is also the official Microsoft news is at Presspass, but it’s all so clinical and corporate).

Of course, Ed Bott writes at ZDNet, who have loads of writers churning out news on Microsoft, Google, Apple and others but it’s just so hard to keep up (and RSS feeds are worsening my information overload instead of making it better!) – just thought I’d make a note of it up here on the blog in case it turns out useful for someone.

Microsoft EVO launch

This content is 18 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Microsoft UK EVO Launch

Let’s get one thing straight. Over the last twelve-or-so years I’ve built a reasonably-successful career out of working with Microsoft products. At times, I’ve even been accused of bias towards Microsoft; however, I don’t exclusively use Microsoft products. I’m also aware that I’ve been fairly critical of Microsoft of late – but that’s because I am “not backwards in coming forwards” – i.e. I will say what I think. One of those times was a recent blog post about Office Groove 2007 and at the time I chose not to name the Microsoft presenter in question (so I won’t now either); however for an organisation that claims to crave feedback, my comments, written on blog with a relatively-small readership, do seem to have touched a raw nerve. Regardless of the comments I made on that particular presentation, I will also give credit where credit is due – the majority of Microsoft events I attend are informative and generally represent a good use of my time.

I spent today at Ready for a New Day: Microsoft’s Launch of Exchange, Vista and Office (EVO) (there was an earlier UK business launch event held at Arsenal FC’s Emirates Stadium, to coincide with the US launch at NASDAQ) – I’m pleased to say that it was well worth it (and I know that a lot of hard work went into a day where PowerPoint was dumped in favour of back-to-back demonstrations).

Despite being critical of the Windows Vista marketing message (clear, confident and connected), I’ve commented in the past that Windows Vista does have a lot to offer. I’ve also been impressed with Office 2007 (although the ribbon interface does take some getting used to; once you get the hang of it, everything works well) and since last April I’ve wanted to write lots about Exchange Server 2007 but was prevented by NDA (Exchange Server 2007 was released to manufacturing last week and I consider it to be just about the most exciting new version of Exchange Server since the original v4.0 launch in 1996 – more on that in a moment – I’m not alone as it seems that Gartner are pretty fired up about Exchange Server 2007 too).

The event was introduced by Phil Cross, Microsoft UK’s Audience Marketing Manager, who first took a look at the history of Windows, Office and Exchange and whilst it’s a bit of a diversion from the topic of this blog post, it represents a nice trip back down memory lane.

It seems that technology doesn’t always help us to do our work and according to a survey conducted by Microsoft and YouGov, in this ever-connected world, almost 40% of respondents admit to working extended hours and around 25% regularly work through lunch – despite the all-pervasive IT that’s supposed to make life easier. Also interesting is what has been important to information workers over the last 30-or-so years: in the 1970s, 32% considered a telephone on their desk to be the ultimate status symbol and 23% craved access to a computer terminal; by the 1990s the ‘phone was ubiquitous and 56% considered a PC to be essential; and in 2000 58% of respondents consider e-mailed to be an essential business tool.

Looking back to the early 90s, Microsoft MS-DOS 6.22 and Microsoft Windows for Workgroups 3.1 were the desktop operating system and windowing environments of choice, with Microsoft and IBM still working out the future of LAN Manager and OS/2.

In 1993, Microsoft’s UK server business was worth just £6m, of which £5m was revenue from Microsoft Mail. SQL Server cost £100,000 and needed to run on OS/2 and there were only three Microsoft server products (NT Server, SQL Server and Mail). Today, Microsoft has around 30 server products and the associated revenue in the UK is around £800m.

Just 10 years ago, in 1996, Microsoft launched Exchange Server – of particular relevance to me as it was the first time I worked with Microsoft. At the time, Phil Cross was the UK Product Manager and I worked for ICL, one of the Microsoft Solution Providers who joined Microsoft on the UK launch tour (I probably still have a t-shirt with our tour dates but I remember driving a van around the country with our presentation materials as we took a stand to every Microsoft event and ran our own events on the days in between).

I’m not going to repeat the whole day’s worth of presentations, but some of the key messages from the day appear below, with demonstrations structured around 4 key tracks, introduced by Eileen Brown:

  • Simplify how people work together.
  • Help protect and manage content.
  • Find information and improve business insight.
  • Reduce IT costs and improve security.

Looking firstly at simplifying how people work together, Jane Lewis demonstrated:

  • Outlook autoconfiguration – creating a profile based on just the user’s e-mail address, auto-populated from Active Directory.
  • Office Groove 2007 – quickly setting up a collaborative workspace and inviting an external contact, then synchronising changes as they collaborated on documents before finally uploading the content to Windows SharePoint Services for long-term storage.
  • Exchange Server 2007 proxying links to internal document shares to allow access without a VPN connection and providing web-ready document viewing (HTML rendering of documents, so that no temporary files are left behind when accessed via a public PC).
  • The ever-improving Outlook Web Access – now richer than ever – and unified messaging, with voicemail in the Inbox, along with the ability to add notes for searching and indexing voice messages and finally, self-service PIN reset for voicemail access.

Jason Langridge followed this up with demonstrations of some of Microsoft’s mobile technology including:

  • The Windows Vista Mobility Center (for quick and easy switches to PC configurations – e.g. presentation mode).
  • Outlook Mobile, including folder access, global address list lookup and spell-checking.
  • Word Mobile, with full support for document formatting.
  • Excel Mobile, with the ability to summarise data in charts.
  • PowerPoint Mobile, with read only access to presentations, including animations.
  • Setting up a new device, then seeing the application of device policies including mandatory passwords and the ability to wipe a device remotely.
  • Exchange Server 2007 self-service management of connected devices including a log of device interaction with the server, the ability to remove devices from the list, password display and remote wipe capabilities.
  • The Windows Mobile Device Center – replacing ActiveSync and built into Windows Vista, managed via Active Directory and allowing access to device settings (partnerships/synchronisation settings), file transfer, as well as the ability to tag and rate pictures, music and video.
  • Finally, Jason demonstrated OneNote Mobile, creating meeting notes with embedded pictures and audio.

Some key facts from Jason’s presentation included:

  • In the UK, 90% of 9-year-olds and above have a mobile phone (we actually have move handsets than there are people… I carry two and so do many others that I know!).
  • 250m PCs will be sold this year, but this is eclipsed by the 1.5bn mobile devices.
  • The Samsung BlackJack has 4 times the power of a PC from just 5 years ago with HSDPA allowing 1.8Mbps access to data.
  • Microsoft supports 46,000 mobile users using just 8 HP ProLiant DL350 servers (it could be less if it wasn’t for the requirement to provide global coverage and resilience).

The next demonstration was given by Arthur Pounder of the Microsoft Unified Communications User Group UK and the Microsoft Messaging and Mobility User Group UK, who started out by explaining the difference between unified messaging (an asynchronous technology from the combination of voicemail and e-mail) and unified communications (synchronous communications with multiple parties simultaneously) before demonstrating how instant messaging (IM) and presence awareness reach new levels in the forthcoming Office Communications Server 2007 (formerly Live Communications Server) and Office Communicator 2007 with multiparty conferencing and voice over IP (VOIP). Arthur demonstrated:

  • Replying to an e-mail with an instant message (reply or reply all).
  • Inclusion of formatted data (from Excel) within an instant message.
  • Multiple levels of presence (i.e. sharing some contact details with certain individuals but not all).
  • Documents with smart tags indicating presence information where a name is recognised in Active Directory.
  • Enabling VOIP on an organisational or per-user basis, including the routing of calls across the corporate network until they reach a break-out point.
  • Policies for control of conferencing settings as well as archival and call detail records for IM, conferencing and VOIP.
  • Intelligent IM filter, including URL filtering and file-type filtering.

Moving on to the protection and management of content (brought to every IT Manager’s attention with the recent theft of a laptop, containing millions of customers’ personal details, from the home of a Nationwide Building Society employee), Andy Malone from Quality Training showed how the forthcoming Longhorn Server product implements network access protection (describing it as analogous to a nightclub bouncer enforcing standards for dress) through the Network Policy Server and a number of health validators. He continued by examining Windows Vista’s user account control and the Windows Firewall with advanced security, which now supports, domain, public and private profiles for both inbound and outbound rules, along with connection security and monitoring. Andy then went on to look at the current beta of Forefront client security, analysing and reporting on the security of PCs across the enterprise, as well as Exchange Hosted Services (a development of the anti-spam and anti-malware technologies acquired with FrontBridge) and Forefront for Microsoft Exchange with real-time capture and incident reporting. Finally, Andy showed Outlook 2007 disabling links in suspicious messages as well as Internet Explorer 7’s anti-phishing filter (using a demonstration phishing site).

Brett Johnson is one of my favourite Microsoft speakers – charismatic and full of energy – and, in the first of two Exchange Server 2007 sessions, he examined some of the controls that can be put in place from the view of compliance and records management, in the process highlighting that:

  • Exchange Server 2007 is available as a 32-bit application for test purposes only and only the 64-bit version is supported by Microsoft.
  • Many organisations have an issue relating to compliance and e-mail as mailbox restrictions lead to a proliferation of personal folder (.PST) files spread around the network, with consequential issues of management.
  • With Exchange Server 2003, message journalling (sending a copy of every message sent to a particular mailbox or mail-enabled document store) was either on or off – and it affects server performance. Exchange Server 2007 allows message journalling to be set at the per-user or per-group level within the hub transport as well as controlling the scope to global, internal or external messages.
  • The Exchange Server 2007 Exchange System Manager gives details of the equivalent PowerShell command at the end of each GUI operation.
  • Managed content folders can be used to control the placement of messages within a mailbox – e.g. expiring Exchange voicemail messages to a particular folder after a number of days (a similar function has been possible in Outlook, but appears to be more granular and is configured by the Exchange administrator).
  • Each message can be assigned a message classification (e.g. confidential) and new classifications can be created to, for example, mark a message as being suitable for a particular audience (e.g. internal account use only).

In the last session before lunch, Jessica Gruber took a look at protecting corporate intellectual property (IP). Unfortunately, despite Jessica’s offers of huge thanks when something worked, the demo gods were not with Jessica but she soldiered on and used her witty responses to keep the audience on her side. I have no doubts that had it not been for an incorrect system clock (and consequential Kerberos authentication issues) from a previous demonstration (used to avoid product activation – proving that even Microsoft has problems with keys!) which made life extremely difficult for Jessica, she would have been able to completely demonstrate:

  • Exchange Server 2007’s hub transport role being used to create an ethical firewall within an organisation (preventing one part of the organisation from communicating with another) and control what happens to the associated messages (e.g. bounce with a custom reply).
  • Even though information rights management (IRM) and rights management services (RMS) are not new Microsoft technologies, Exchange Server 2007 pre-processes the tasks (rather than relying on the client to implement them).
  • Device installation restrictions within group policy (e.g. to prevent the installation of a USB key or to control the ability to write to CD/DVD).
  • Application of information management policies within SharePoint to enable auditing, expiration, etc.
  • SharePoint allowing multiple document types within a single library.
  • The information panel within Office exposing document properties for completion (used within SharePoint to organise the data).
  • The Document Inspector, which may be used to remove internal comments, etc. prior to publication.
  • SharePoint Designer (formerly FrontPage) being used to define control the workflow around approving a document and assigning it to a particular site collection or list, without writing any code.

As the day moved on to the topic of finding information and improving business insight, Melville Thomson did a fine job of demonstrating a SharePoint dashboard with webparts connecting to BizTalk Server and SQL Server providing a sales scorecard. Using this web interface, business data can be exposed to managers who may not have Microsoft Excel on their PC, including the ability to view comments stored with data values and to drill down into the data. For more detailed analysis, the data was then opened within Excel and a pivot table used, along with conditional formatting (with new data bars and colour scales, and now understanding hierarchical data to apply a similar scheme to related cells) allowing the user to visualise the data and identify problem areas. Melville then created a chart which was active, changing dynamically along with the data exposed by the pivot table and published the results to a SharePoint library. Finally, he used the new data mining capabilities within Excel (an add-in from the forthcoming SQL Server 2005 SP2) to examine the demographics within the sales data and identify key influencers, allowing marketing to be targetted to the appropriate group of prospective customers.

I will confess that I was the guy on the front row who fell asleep in the next session (a combination of post-lunch weariness, sleep deprivation and the mention of Microsoft Project letting my mind wander to the stresses of my current assignment and immediate desire to forget it all) as Bob Walker spoke about Microsoft’s Enterprise Project and Portfolio Management products, which facilitate strategic decision making rather than focusing on task-oriented milestones.

(At this point I should make an observation – in my experience, most Project and Programme Managers are completely task-led and think a Gantt chart is a project plan. I’ve never yet worked in an organisation that uses Microsoft Project Server to co-ordinate individual plans and provide a programme-level view of operations).

Bob demonstrated:

  • Microsoft Office Portfolio Server, featuring a builder, optimiser and dashboard to allow analysis of potential projects to be balanced against available resource at a programme, project or application level.
  • Microsoft Project Server, now featuring multiple undo levels, the ability to highlight milestones and to view the impact of timescale changes using colour and reporting, with export to an Excel pivot table.
  • Microsoft Project Web Access, which runs on Windows SharePoint Services to provide a lightweight project client for others to view projects.
  • Integration of Microsoft Project with Outlook tasks and timesheets.

Next up was Rod Gordon of the Access User Group and Office User Group, who gave a very interesting demonstration of linking Microsoft Visio to a dynamic data source. In Rod’s example, he used an Excel spreadsheet of PC audit data to link it to a Visio diagram with an office floor layout. Key features of the demonstration included:

  • Use of the control and shift keys with the mouse to drag a box around an area of the diagram to zoom in on and a pan and zoom window to drag the selected area and highlight different sections of the diagram.
  • Using Visio’s data menu to link a Visio diagram to source data from a number of sources including Microsoft Access, Excel, SQL Server and Windows SharePoint Services.
  • Selection of data within the external data pane and dragging/dropping it onto the appropriate shape in order to create a link (alternatively, by setting a primary key and populating just that field for each shape, the data can be automatically linked). Once the link has been created, a simple right click on the shape allows the associated data to be viewed and the shape can have conditional formatting defined in order to highlight certain conditions.
  • Editing of source data with a manual (or periodical) refresh of the corresponding data in Visio.
  • Use of multi-layered diagrams to expose different layers for viewing/printing.

The last topic area of the day was focused on reducing IT costs and improving security and another friendly face from Microsoft UK, Steve Lamb, gave a short demonstration of some of Windows Vista’s security features including:

  • BitLocker, which encrypts the hard disk such that a key is required to start up the computer (stored on a USB key, within the computer’s trusted platform module, or entered manually). Using a drive analysis tool (diskscape.exe), Steve showed how an encrypted hard disk looks the same throughout, whereas a non-encrypted drive has definite areas of data that can be detected.
  • The Application Compatibility Manager (replacing the Application Compatibility Toolkit), which now incorporates community feedback on the steps required to make a particular application run successfully on a modern Windows system.
  • The Business Desktop Deployment (BDD) deployment workbench, which allows the customisation of Windows images to choose the appropriate operating system version, integrate new drivers, create new builds, edit default settings using the Windows System Image Manager and finally prepare the build for deployment using a single server, deployment share, removable media or the Microsoft SMS Operating System Deployment (OSD) feature pack.
  • Demonstration of a program’s ability to inflict malware on a system running as a Windows XP Administrator, Windows XP unprivileged user, Windows Vista user (by default unprivileged) and Windows Vista user running with elevated permissions, at which point User Account Control (UAC) intervened.
  • (Did we tell you that Internet Explorer 7 has new anti-phishing capabilities?)

Next up was Brett Johnson, continuing his Exchange Server 2007 theme by looking at Exchange Server efficiency:

  • Exchange System Manager 2007 is based on the new MMC 3.0 console and exposes more properties in each view – making it easier to find what is required.
  • Exchange Server 2007 actually has three default levels of administration – organisation, server and user (e.g. create a mailbox and make limited changes). In effect, the Active Directory and Exchange Server administration roles combine to allow flexibility in managing the organisation’s e-mail infrastructure.
  • Resources (e.g. rooms and equipment) now have their own mailbox type (not just customised user mailboxes).
  • There are 4 main server roles in Exchange Server 2007 – mailbox, hub transport, client access, and unified messaging (there is also a fifth role – edge services – but that is deployed on a separate server – generally inside the DMZ).
  • Exchange Server logfiles are now 1MB in size (down from 5MB).
  • Exchange Server 2007 offers two new forms of resilient architecture:
  • Local continuous replication (LCR) creates a second copy of the database and log files (e.g. on a separate storage system) for local resilience.
  • Clustered continuous replication (CCR) extends this capability to span multiple cluster nodes.
  • Hub transport rules can be used to customise message flow (e.g. Jessica Gruber’s earlier creation of an ethical firewall, or adding a disclaimer message to all e-mail.
  • The Exchange Server Best Practice Analyzer (ExBPA) is now available, along with various Microsoft Product Support Services (PSS) tools within Exchange System Manager. Quoting Brett, “We are making this product a cinch to use”.
  • PowerShell (I still can’t stand that name) offers powerful scripting capabilities, including the ability to perform Exchange Server functions from the command line, using one of the many commandlets provided by Microsoft. It’s also possible to create a log of PowerShell activities using the start-transcript command.
  • The last demonstration was from Adam Shepherd, looking at how Windows Vista improves operational efficiency:

    • There are 700 new group policy settings in Windows Vista (e.g. new settings to deploy printers via GPO or enforce power management).
    • After deliberately sabotaging a system by using the Windows Recovery Environment to rename a core system file, Windows Vista detected the fault and repaired it at reboot time.
    • The Windows diagnostics infrastructure can be used to warn of impending faults (e.g. utilising the SMART technology in modern hard disks).
    • The entire hard disk from a Windows Vista system can be backed up to a virtual hard disk (.VHD) file for later recovery.
    • Windows Vista includes guided help, with options to watch as the computer performs the operation or to be guided on a step-by-step basis. What I found really impressive is that the Windows Automated Installation Kit (WAIK) includes a guided help studio for creation of custom guided help routines in little more than a few clicks, recorded with a task recorder.

    In all the event was PowerPoint light and demo-heavy – with a huge amount of resource involved and a lot of hard work. I found it very worthwhile (although the format wouldn’t suit all events – it’s sometimes good to have the PowerPoint slides as a takeaway).

    It was interesting to hear James O’Neill comment to a couple of attendees that the event was originally targetted at Microsoft’s enterprise customers but was later opened to a larger audience after a lack of interest (opening the floodgates and leading to an event with very low levels of “no-show”). It seems to me that Microsoft Exchange Server 2007, Microsoft Windows Vista and Microsoft Office 2007 are all remarkably advanced products with a lot to offer and today’s demonstrations just scraped the surface. Quoting Steve Ballmer, “These are game-changing products. It’s an incredible step forward for business computing in a year of unprecedented innovation from Microsoft”.

    Considering Windows Vista in isolation may not be a convincing argument for an upgrade but once you add Exchange Server 2007 and the 2007 Office System into the mix then there is plenty of scope for using IT to support new ways of working (maybe even reducing those long hours). Find out more, by following the links below or check out one of the upcoming Microsoft TechNet UK Technical Roadshow 2007 events:

    Will Vista’s 3D effects work in a virtual machine?

    This content is 18 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

    As a Windows Vista beta tester who filed at least one bug report, I was recently given a complementary copy of Windows Vista Ultimate Edition (thanks Microsoft); however as I’ve been rationalising my PC infrastructure of late I only have a couple of PCs that could make full use of the visual effects in Vista – my Mac (which runs Mac OS X most of the time) and a 2.4GHz Pentium 4-based PC (which runs Windows Server 2003 and Virtual Server 2005 R2). Consequently I’ve been wondering if the best way to make use of my new Vista license (bearing in mind the restrictions of product activation should I later try to move it between PCs) would be in a virtual machine.

    It seems not, as I checked with John Howard, who is a Microsoft Program Manager for Windows virtualisation (and was formerly an IT Pro Evangelist here in the UK) as to the likelihood of ever receiving suitable VM Additions or 3D device drivers within a Windows virtualisation product.

    John kindly replied, pointing out that the S3Trio video adapter which is emulated within the Microsoft virtualisation products is nowhere near the level required to support Vista’s 3D graphics. He went on to add that there are no plans to change this within Virtual PC 2007 or Virtual Server 2005 R2 SP1, nor in Windows Server Virtualization (which is seen as a server solution and therefore unlikely to require client-focused features such as 3D graphics).

    John’s reply doesn’t fill me with hope and despite VMware’s current push into enterprise desktop virtualisation I’m not sure that their position would be any different. In the meantime, it looks as though 2D graphics will be the limit to those of us who are heavy users of virtualisation on the desktop.

    Note to ego: I am a blogger, not a journalist

    This content is 18 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

    Last week I wrote about how I was expecting to feature in a couple of upcoming articles for Computer Weekly and The Independent. In future, I should remember that what is said to a journalist is not always the message that makes it to paper and what is written is not always what is published!

    My part in Rob Griffin’s how to blog your way to fame and fortune article was short and sweet, but that’s fine – Rob was a nice guy to chat to and getting so much information into 1500 words is always going to mean that there’s only room for a small soundbites from the likes of me. I’m also a techie, whereas the target audience for the article was a typical consumer who’s heard about blogging and wants to give it a go. The original idea was that I might feature in a case study, but in reality I’m a small-time blogger who can cover his hosting costs and buy the odd gadget with his advertising revenue – nowhere near the £2000 a month that the chosen case study (Craig Munro) says is possible. In fact, whilst that figure is theoretically possible, most bloggers won’t get near that sort of income because it would be a full-time task (and someone who can write that much original content could earn more in a proper full-time job).

    Computer Weekly’s pretty interfaces alone do not make a business case was slightly disappointing. I was asked to rewrite two existing blog posts into about 500 words for publishing in Computer Weekly. After a few hours of unpaid editing and redrafting, I submitted a piece entitled Windows Vista is finally here… but XP’s not dead yet; however editorial considerations have meant that just over 500 words became just under 300. I’ll admit that what was published was much punchier than my original submission, but it inevitably lost some of the background information and slightly distorted the message (this is what I actually wrote). Still, at least I got a link back to this blog from a well-respected publisher (which may help to drive traffic to the site – a cursory glance over my web stats reveals no evidence of that yet though).

    So what should be learnt from this? Firstly, that bloggers are not journalists (at least most of us aren’t). Blogging is a time-consuming creative process that can be fun but is unlikely to make you a fortune. Secondly, print media is a hard world that takes no prisoners. If you submit something for publishing, expect the final result to differ from your original creation.

    Windows Vista imaging and deployment

    This content is 18 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

    However much I try to avoid it, as an IT infrastructure consultant, I always seem to get involved in operating system deployment. With that in mind, a couple of days back, I went along to an event at which Microsoft UK’s James O’Neill gave an interesting presentation on Windows Vista imaging and deployment.

    Deployment of a PC operating system ought to be simple. It isn’t. Well, it can be, but only after a lot of hard work and planning. You see, unlike a closed system such as Apple Mac OS X, a Windows deployment typically has to support a plethora of different PCs – each with their own hardware variants (very few organisations have the luxury of a 100% standardised infrastructure – IT hardware simply changes too quickly for that). For many years now, the approach to deploying a PC operating system has been to use imaging software, e.g. Symantec Ghost, but there are complications around which images can be applied on what hardware, as well as licencing implications for any software included in the image – often images are created based on a combination of target hardware and end-user roles. Then there’s the data to consider – how are applications to be deployed, what will happen to user data (e.g. in an upgrade scenario), and what about system settings (Outlook profile, etc.). A managed deployment has many advantages around consistency (between images), manageability and reliability; however there is a huge cost attached to maintaining each image.

    Since the creation of Windows NT, administrators have been able to automate Windows deployment using a system of answer files and either a product CD or a distribution share. This can be customised to roll out additional applications as well as to alter the Windows configuration and add OEM-specific items and it works well, but is slow to deploy and costly to maintain (often scripted installations are used to deploy to reference PCs from which images are taken).

    Windows 2000 introduced the concept of booting a PC across the network using the pre-boot execution environment (PXE) to connect to a remote installation services (RIS) server and download an image. Later, this was extended to create the solution accelerator for business desktop deployment (BDD) and enhanced through the creation of Microsoft automated deployment services (ADS) – now renamed Windows deployment services.

    Windows Vista employs a totally new deployment approach – using Windows Image (.WIM) files – look on a Vista DVD and there is no i386 folder (the main setup file on my Vista RC2 DVD is called install.wim). Those who have worked with BDD and ADS may already be familiar with an older version of the .WIM file format and the new version supports deployment to a new system, side-by-side installation, or in-place upgrades (actually, an in-place upgrade is a side-by-side installation which then transfers the settings from the old copy of Windows, which can safely be destroyed later). The Windows imaging approach supports modularisation of components, single instance storage, compression and file-based imaging – allowing many images and many image variants to be installed in a single .WIM file for deployment from optical media, or using deployment solutions such as BDD or Microsoft SMS. Importantly, deployment is non-destructive. Furthermore, Windows Vista does not have any of the restrictions around hardware abstraction layers (HALs) and so there is no requirement for hardware-specific images; and because the image is file-based (cf. disk block-based images), it can be mounted as a file system and manipulated offline.

    .WIM files are structured as follows:

    • Header – with signature, version, GUID and indexes to images.
    • File resources – the actual image files.
    • Metadata – information about the files within the image.
    • Resource table(s) – effectively a directory tree for the files within the image, defining the file system.
    • XML data – information used to customise the image.

    Windows imaging uses a system of filters, e.g. the .WIM file system filter (to edit image contents) and the WIM boot filter (not surprisingly to boot from an image). The main tool used for manipulation of .WIM files is imagex.exe (previously known as ximage.exe). imagex.exe allows the mounting and unmounting of .WIM files as a file system, whereby changes can be made before they are committed to the .WIM file. It is also used to create, append to and split image files, as well as for viewing the XML data about an image file. There’s also an API for programmatic manipulation of .WIM files – WIMGAPI. It’s important to note that, whilst there are both 32- and 64-bit versions of the Windows Vista deployment tools, they are compatible, so images created/modified with a 64-bit version of imagex.exe will still work on a 32-bit system, etc. Also worth noting is that the System Preparation Tool (sysprep.exe) still exists – images still need to be sysprepped – but there are new options around what the system should do on its first boot.

    Whilst imagex.exe can be used to capture the contents of a running system, it’s not good practice, and Microsoft recommends that the Windows pre-installation environment (WinPE) is used instead. Because WinPE runs entirely in memory there are no issues around locked files and Windows PE 2.0 will be made more widely available than previous versions. James’ presentation also indicated that a file called winscript.ini can be used to specify exclusions (e.g. pagefile.sys, hiberfil.sys, \WINDOWS\CSC, \RECYCLER, System Volume Information, \$ntfs.log, etc.); however he’s since blogged that the .INI file is not required – the key point is that there are files which you will almost certainly want to exclude from an image.

    Another important tool is the Windows System Image Manager – setupmgr.exe on steroids! This is used to build a catalog of .WIM file contents and then customise the file – e.g. to add components, or to customise settings, before validating the resulting unattend.xml answer file.

    Other deployment tools, available for previous Windows versions but updated for Vista include the application compatibility toolkit and the files and settings transfer wizard (formerly the user state migration toolkit).

    Bootable .WIM files are always called boot.wim. The boot process is as follows:

    1. Read boot configuration database (BCD) file. This tells the system what to execute and effectively replaces the boot.ini file found in previous versions of Windows NT/2000/XP/2003; however, unlike boot.ini it is not a text file – it must be edited using bcdedit.exe.
    2. Mount boot.sdi
    3. Attach boot.wim to boot.sdi
    4. Continue boot process.
    5. Install .WIM file system filter

    The use of .WIM files is not limited to Windows Vista imaging – although they may be unsupported with other operating systems and there may be complications (e.g. I wrote a post last year about deploying Windows XP using ADS). Indeed, Windows Vista imaging technologies will also be used for the next Windows Server product (codenamed Longhorn), although because this is still a beta product, the details may be subject to change. Importantly, the tools provided for working with Windows Vista .WIM files are not all compatible with legacy operating systems.

    It looks as though the new Windows Vista approach to imaging and deployment will be a steep learning curve for us all, but it should result in a more flexible, and manageable, approach to deployment – more information about Windows Vista deployment enhancements is available on the Microsoft website.