I need to rebuild one of my PCs before lending it to someone for a few days but before I do that I want to take an image of it. If I had the Microsoft Deployment Toolkit 2008 set up at home then that would be reasonably straightforward but I don’t, and the old drive imaging technologies will be fine for this – at least that’s what I thought until I spent half the night and a good chunk of this morning fighting with Symantec Ghost… So, here’s a few of the things that I’ve (re-)discovered about Ghost in the last few hours.
- Using Ghost in peer-to-peer mode does require the slave and the master machines to be running the same version of Ghost – it will present a version mismatch if you try and run different versions.
- Ghost 6.x Enterprise has a multicast option but I couldn’t get it to work (it was always greyed out for me). Symantec’s knowledge base suggests that this may be down to TCP/IP issues and I’m pretty sure that packet-level network drivers are required with the MS-DOS client (the Windows server can use the normal Windows network settings) but, even with a suitable packet driver loaded, I gave up after a few hours without success.
- GhostCast Server uses (UDP) port 6666 for communications.
- GhostCast Server 8.x will create a Windows Firewall exception for itself but the exception still needs to be enabled manually.
- On a multi-homed server, there seems to be no way to select the NIC on which the GhostCast Server presents a session.
- Multicasting also seems to need the client and server versions to match one another. 16-bit Ghost 7.x should work with an 8.x server but it wasn’t working out for me with 7.5 and 8.2 (32-bit 8.x clients were connecting to the server fine, so I knew it was working, but I didn’t want to image those machines – and I didn’t have a copy of the 7.x server).
- Compression adds a lot of time to the imaging process.
Eventually, I got everything working with a 16-bit copy of Ghost 8.2 running on MS-DOS (to be completely accurate, it was a Windows ME startup disk created from Windows XP) communicating with a GhostCast Server 8.2 running on Windows Server 2008.
And for anyone who is wondering why I was messing about with 16-bit executables and MS-DOS (in these days of Windows PE), Toffa suggested that I should try a Windows PE disk with the 32-bit ghost client. Although that would have let me access USB-attached external storage, I didn’t have enough space on a USB drive and was storing my image on a server. Windows XP (and so PE) doesn’t natively recognise the network card on the machine I was imaging, so that would have required me to extend the Windows PE image and provide additional driver support. Somehow, using a universal network boot disk seemed like the easy option.
This is a bit voyeurstic, but it’s also a great way to see other peoples photos…
After
No sooner had Java finished updating itself then the Apple Updater popped up and said “hey, we’d like you to update QuickTime. We can’t be bothered to give you just a patch, so please download 29MB of our bloatware” (I said no because I was using a mobile connection), “and while you’re at it why not install our web browser that seems to have more than its fair share of security issues… that will be another 23MB” (of course, I am paraphrasing here – but you can see the dialog box… complete with checkbox selected by default. Can you imagine the uproar there would be if the Microsoft Office for Mac Updater tried to install another Microsoft product on people’s computers?
Last week,
Earlier this evening, I was trawling through the fine print on the O2 website (hey, I have to do something whilst I’m eating alone in a hotel restaurant) and I found a reference to free Wi-Fi access from
I tried to use the BT Openzone at the Hilton East Midlands hotel last night (7 July) with my iPhone and it worked. Just like at