Solution Request
Yes, another.
I am familiar with several methodologies to test installation, patches, configuration changes, etc. in the enterprise environment. What about on a small scale?
How can I, for example, test installation cleanly on a laptop? I would want full rollback to alleviate the problem of leftover "junk" from install/uninstall (regedits that weren't cleaned, files that were leftover, etc.).
I've toyed around with the idea of setting up my laptop to just be a host system with virtualization slices for real computing (which can be easily rolled-back with saved states), but this seems like overkill. Anybody use a simpler system?
I am familiar with several methodologies to test installation, patches, configuration changes, etc. in the enterprise environment. What about on a small scale?
How can I, for example, test installation cleanly on a laptop? I would want full rollback to alleviate the problem of leftover "junk" from install/uninstall (regedits that weren't cleaned, files that were leftover, etc.).
I've toyed around with the idea of setting up my laptop to just be a host system with virtualization slices for real computing (which can be easily rolled-back with saved states), but this seems like overkill. Anybody use a simpler system?