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…

As soon as I got home, I simply dumped the collection into my Picasa albums folder and let the software crank through it. But only a few days ago did I stumble upon the facial recognition features of Picasa – and it opened up an totally unexpected world of family history for me. You see, in sorting through all of the faces and tagging them with names either from my already-imported contacts list or by adding new ones on the fly, I’ve begun to gain a deeper understanding of my family history. I’ve always known the basics, such as my grandparents and some aunts and uncles here and there. But putting names to the faces of people like my father’s aunt, sitting down to dinner dressed to the nines in the 1930’s with her dapper husband Jack, has just brought a whole new level of appreciation to where I’ve come from and how deep my roots – and my own growing family’s roots – are and will continue to be for generations to come. And yes, that’s my father leaning out of the back of that 1960’s Beetle, not me. Something about the apple falling somewhere in close proximity to the tree…

Google has updated Gmail to include a “Buzz” tab, where you can prevent the public from seeing your followers list, remove the Buzz inbox from Gmail, and, as the nuclear option, completely kill your Buzz account

That last link, with the warning sign and red text, completely removes Buzz from your Google Profile, according to its wording. A commenter notes that it might also kill your Google Profile entirely, so be cautious if that’s something you want to keep around.

I’m blocked from Gmail at work and can’t bring up the full desktop version from my iPhone, so I guess I’ll have to wait to do this until later this eve. But there is that note about deleting your Google Profile that will be interesting to watch. I find it interesting that Google is taking a course of action here that will not just bring you back to where you started before Buzz, but actually to a lower level of end-user engagement by deleting profiles. If anything, this privacy debacle has made me take a good look at what I use my Google account for besides email, if not thinking about pulling my personal email from Google entirely – with the full support from my lovely wife who noted that it’s not like I haven’t changed my address a bunch of times recently.

UPDATE: Yup, it works as advertised from what I can tell. No more Buzz and no more Google Profile.

You’ve got to wonder how badly you foobered up your product release when the Electronic Frontier Foundation has this to say about Buzz:

If you’re going to use Google Buzz, we recommend that you opt-out during profile creation. If you have already created a profile, change it to private immediately. Then go through the suggested list, and edit it as appropriate before making it public again. PC World has a helpful privacy checklist to help users understand the privacy implications of Google Buzz options.

How many people are going to want to read through such checklists and really tweak their profile/settings in order to actually take advantage of Buzz while maintaining some semblance of privacy? I just turned it off and removed anything I could find related to Buzz in my profile. If anything, it made me take a closer look at how open my profile was on Google.

Fail, Google. Really really really huge fail.

Didn’t realize that Google Buzz gets turned on with some really, really huge privacy-nuking options. WTF, Google?

From the Silicon Valley Insider:

A Google spokesperson asked us to phrase this claim differently. Like this: “In other words, after you create your profile in Buzz, if you don’t edit any of the default settings, someone could visit your profile and see the people you email and chat with most (provided you didn’t edit this list during profile creation).”

I guess I could take some time to figure out how to protect myself, but instead I’ll be sitting it out for now with a tech tip from Consumerist:

You can go into Buzz and selectively follow/unfollow certain people to avoid this kind of incident, but the best evasive maneuver is to scroll down to the bottom of the screen and click “Turn off Buzz.”

Wow… just wow, Google.

So, found my snapshot and all the files of the VM (one line):

/vmfs/volumes/NFSSTORE/.snapshot/nightly.2010-01-31_0000/SERVERNAME

I then found my destination, or where the VM currently lives:

/vmfs/volumes/NFSSTORE/SERVERNAME

I’m particularly interested in SERVERNAME.vmdk, which is the C: in this case. In order to not run into myself, I renamed the current, not-booting SERVERNAME.vmdk using vmfsktools while in the working directory of the current VM:

vmkfstools -E SERVERNAME.vmdk SERVERNAME_old.vmdk

Then, this is as simple as importing the .vmdk from the .snapshot directory to the current working directory of the VM. Yes, you can use cp to do this, but vmfsktools is hella faster (one line):

vmkfstools -i /vmfs/volumes/NFSSTORE/.snapshot/nightly.2010-01-31_0000/SERVERNAME/SERVERNAME.vmdk /vmfs/volumes/NFSSTORE/SERVERNAME/SERVERNAME.vmdk

Since the .vmx file is still configured with the SERVERNAME.vmdk and SERVERNAME_1.vmdk disk files, there shouldn’t be any need to reconfigure the VM before powering it on. Finally, I verified that the machine was booting normally and deleted the _old file to save disk space.

…when I flipped the page over on my desk calendar this morning and noticed that the January 31st Virtualization Tip of the Day from the fine folks at PrintedOwl.com has this to say:

It’s a best practice to keep the number of COS software installations to a minimum. Here’s a case that’s justified for some environments to ensure graceful host shutdowns. Mike at motogobi has done some leg work & put up a procedure: http://www.motogobi.com/2008/11/13/setting-up-powerchute-network-shutdown-in-vmware-esx-35/

I’m flattered

Although they didn’t compare an ix-series Bimmer, did they? via Jalopnik