In a spirit of adventure, I've been writing this whole series as I go -- all the while praying that I won't mess something up and be unable to take screenshots, write ineffable commentary, etc.
Well, it turns out my steps were incomplete (in a very fun way). To be more specific, the steps to create the WinPE boot-device were incomplete.
So imagine my surprise when (after a half-dozen hurdles) I successfully ran sysprep, rebooted into WinPE, and couldn't execute imagex.
"imagex is not recognized as an internal or external command, operable program, or batch file."
Umm ... no?
cd \
dir imagex* /s...
File not found.
Well, &$%*@%. It's not on the USB.
And about ten seconds of Googling found that -- yup, ImageX is an optional module you need to explicitly add to WinPE.
Well, &$%*@%.
So the happy conclusion of this series will have to wait until I have more time.
On the flip side -- I now have a bright-and-squeaky-clean Windows installation to play with! No hidden cruft lingering in the abominable pit of that Lovecraftian horror of nightmare incomprehension, the Windows Registry (and, like all of the sins of Man, probably seemed like a pretty good idea at the time).
So ... yeah. Now I know.
On the other hand -- fresh system!
So: onwards to glorious triumph!
- Re-do the custom-image process -- and archive that image!
Move the CPU to a back-room/closet-- CHECK and it's AWESOMEGet another NIC- Make a standard VM image
- Make a flock of VMs -- a router/firewall/proxy, a NAS/DLNA server, an Apache server, ...
No comments:
Post a Comment