Peter Bromberg's UnBlog

Have you ever installed a BETA or CTP or an RC build of some Microsoft product such as Visual Studio, and then been faced with the unhappy situation that it could not find the installation sources when you attempted to uninstall the product, or it just didn’t uninstall “cleanly” – leaving traces of Registry entries that prevented you from installing a later version? It’s certainly happened to me several times. But today I ran into a program called Perfect Uninstaller that, for $35, turned out to be one heck of a bargain. Perfect Uninstaller has three modes to completely and totally uninstall any program. It starts out using the regular Windows Installer, but it doesn’t stop there – even if the installer says “I can’t find the MSI source for this”, it doesn't give up like the Windows MSIEXEC installer would do -- it picks up all the Registry Entries by scanning the Registry, and then it picks up all file traces by scanning the filesystem. The result is a 100% complete and total un...

Quis custodiet ipsos custodes Who shall keep watch over the guardians? Some may  think I write about this subject ( example ) too often, but frankly, I don't think I write about it often enough: Your server (or workstation) machine is important. Having it not boot up properly or operate normally  can often mean serious loss of income. That's real hard-earned dollars that you CANNOT GET BACK.  So why is it that so many Admins don't have a reliable backup and recovery strategy? Maybe we just think "it can't happen to me". Or maybe we're just plain stubborn and dumb! The single most important ingredient of a recovery strategy is the ability to restore a known good Registry.  Registry corruption often occurs when the machine is shutting down as OS changes are being written to the Registry. It can also occur if there is a network (TCP)  glitch or a power glitch. The bottom line is this: NOBODY IS IMMUNE TO REGISTRY CORRUPTION!  NOBODY! R...

Another flaw in the human character is that everybody wants to build and nobody wants to do maintenance.   - Kurt Vonnegut I've written several times about the importance of having a serious backup strategy for your production web server, mostly about ways to backup the Registry. But there are a few other components of a good emergency recovery strategy that are important as well. A significant percentage of developers and webmaster / administrators run production sites on production machines and have no reliable backup strategy for the components of the machine that are critical to the successful operation of IIS. The mere fact that up to now you haven't had a production server blow up on you may actually have increased the statistical likelihood that you will experience such a failure! The three critical components to be protected and backed up -- with an easy path to restore them - are the Windows Registry , the IIS Metabase , and the .NET Framework machine.config file....