By mike
If you end up using VMware’s VI Client to connect to multiple vCenter servers or ESX/ESXi hosts, you might find yourself a little annoyed at how many saved connections show up when you go to launch a new connection. This becomes ever more annoying when you’re connecting to multiple servers named somewhat the same as the client will start auto-completing your selections. This has reached it’s pain point this week as we transition to similarly-named vCenter servers and I keep fat-fingering what I’m typing.
If you want to clear that saved connections dialog, it’s a simple registry edit in XP. Navigate to:
HKEY_CURRENT_USER\Software\VMware\VMWare Infrastructure Client\Preferences\RecentConnections
and simply delete the connections you don’t want (DO NOT delete the entire key, just the connections in that reg key). Enjoy your clutter-free VI Client…
By mike
So I’ve been restoring some Windows servers from NetApp snapshots today, specifically single hard disks that had been having problems (long story involving Windows problems, etc). I found this pretty easy to do once I got the syntax down – basically, all I was looking to do was to restore the C: of a server, but keep it’s D: intact – that way I’d keep the most recent data, in this case some SQL files, but could roll back to a point where the Windows OS was a little less hosed up. Mostly for my own quick reference in the future, this is how I cranked a bunch of these out.
Read more »
By mike
It’s good to see Lifehacker focusing on backup tools. After literally years of struggling with backing up various computers and laptops I’ve owned over the years, and having learned my disaster-recovery lesson the hard way when I lost the hard drive on my desktop in 1996 or something, I’ve recently settled into a very cozy relationship with Mozy. I signed up for the yearly Home Unlimited plan ($50/yr per machine) and have been nothing short of pleased with it’s performance.
Check out other options over at Lifehacker, but whatever you do? Make sure you’re backing up your data…
If you end up using VMware’s VI Client to connect to multiple vCenter servers or ESX/ESXi hosts, you might find yourself a little annoyed at how many saved connections show up when you go to launch a new connection. This becomes ever more annoying when you’re connecting to multiple servers named somewhat the same as the client will start auto-completing your selections. This has reached it’s pain point this week as we transition to similarly-named vCenter servers and I keep fat-fingering what I’m typing.