I’ve done more than my share of Windows upgrades. I’m fond of telling people that my first proper project in IT as a professional involved updating the software supplied on the company’s computers from Windows 1.03 to Windows 2. I didn’t run NT as my desktop OS until version 4, and never ran Windows 98 or ME, other wise I ran just about every release of DOS from 3.1 forwards, and Windows 1,2, 2.1 (/286 and /386) 3.0, 3.1, 3.1-for-workgroups and 3.11 for workgroups, NT 4, Windows 2000, XP, Vista and 7, including the betas of most of them. I’ve managed plenty of non-Microsoft stuff, and all my experience has taught me that in-place upgrades save you a few minutes only to cost you hours later. I understand that there are cases where people need to do an in place upgrade (the classic case being where a machine is supplied with bundled software, and a recovery image disk but no separate installation disks), but its best avoided.
My experience with upgrading to the release version of Windows 7 has been slightly convoluted, and is still the best I’ve had by some margin. Firstly I was running 7 on a spare hard disk. So I went back to my original disk for release. The over the network installation takes a couple of hours, but it needs seconds of my time. It went like this
Someone called me a curmudgeon recently, and the complaint I’m left with after putting Windows 7 on is there is no sense of achievement; no sense of having overcome something: when I used a USB stick to put it onto a netbook at home I was expecting to hunt down drivers and be able to point to something at the end and say “I did that”; it did it all by itself. The image at work just takes that to another level. Microsoft IT have a harder job than you might think – a commitment to running pre-release software in production and most employees think they know better. I can remember a time when the laptop images which Microsoft IT put a machine were so far from being useful the best thing you could was to round up a stack of CDs,wipe it and build it properly yourself. The new imaging technology which came in with vista means they provided a very small number of images and devote their time to getting those right. (Previously they had to maintain many images – and couldn’t spend enough time on any of them. Now the reverse is true – the standard image is now so good that the idea of getting the stuff together to do my own has no appeal whatsoever. One of the guys from Microsoft IT told me they got some great scores on their internal feedback survey about the pre-release of Windows 7, and this will form the basis of a story on IT showcase. It’s made them into heroes.
As it says in a Jonny Cash song “Well, up till now my plan went alright”… I have just got a new 500GB disk for my secondary laptop – which runs as a hyper-v server and needs the space for a zillion VHD files: now it has the space this machine will dual boot into Server 2008, or a VHD based Server 2008-R2 image. Until this week it has been on 2008 only. The process was to do an image backup of Windows 2008 to plug in an external drive and do a Windows image backup; change hard-disks, boot off the Windows 2008 setup disk and do a full image restore. The process ran like clockwork , but at the end I had a 160GB disk which was going to gather dust and 100GB disk in my laptop. Why hadn’t I done this upgrade first ? Time to swap drives… So I went to Windows 7 backup and made an image of the machine I’d just built. At the end of this, the backup process offered to make a recovery disk , and I took that option. I swapped the drive, booted from my new recovery disk and a couple of clicks and a cup of coffee later the machine was waiting for me to logon as if nothing had happened. At least here my 20 years experience upgrading systems paid off – I had to extend the disk partition after the restore. But even that has got so much easier since the days of risky 3rd party tools which would extend a partition.
Last night I ran into an issue with Winodws 7 RTM image backup where I wanted to backup my laptop's OCZ 120GB SSD and restore it to an Intel 160GB SSD. The creation of the system image backup to my server went fast and true. Then I swapped the drives, and then booted to the Win7x64 USB key and told it to repair, restore system image, browse to it on the network, and go. It aborts right away with an "invalid parameter" message. Bing'd that and found it may have something to do with the new drive not having the same partition arrangement? Your 500GB drive did not have partitions, correct? I resorted to Acronis True Image, but would have liked to stay with MS tools.
The new drive had not been partitioned. For the reinstallation of Win7 on the old server drive I deleted the partitions before starting.