I stumbled across a great new site called Microsoft POPFLY. At first I thought it was very similar to Yahoo Pipes which I use to aggregate RSS feeds into personal feeds like this Virtualization one I use in Firefox. (I love the Live Bookmarks)
It is much more powerful. Not only can you Mashup RSS feed, but you can also mashup other things. As an example, I created the Whack a Twitter Follower game below using PopFly. Bear in mind that I have VERY little programming skills. :)
Like Pipes, you can reuse other people’s work – So feel free to improve the Whack a twitter Game! :)
*Originally for this post I was going to make a Whack a server (the whole Virtualization theme) using images pulled from Flickr but hitting twitter people seemed WAAAY more fun! :)
If you want to see your picture pop up for other people to Whack, be sure to follow me on Twitter.
And of course be sure to post your High Score in the Comments! :)



Backdrop: So this error popped up at a client site recently when they were trying to connect their VI client to an ESX host directly. (VirtualCenter was down at the moment). The client was logging in with ESX credentials and everything looked right. We tried SSHing into the box with the same credentials and encountered no problems. Only when trying to connect via the VI client.
DNS is critical to proper Virtual Infrastructure operations. Whether its client to server or server to server communications, it is important that all parts involved are using the correct DNS settings and are also registered with the appropriate DNS servers. Unlike Windows, ESX servers will not auto-register their IP addresses with the DNS servers. (Windows machines will typically update the DNS servers in an Active Directory when you join them to the domain – Since ESX servers are not Windows servers, they are never joined to the domain). You will have to manually add the ESX hosts to your DNS servers for proper resolution. Without it, expect weird vMotion, DRS and HA issues. Even simple things like adding the host to VirtualCenter or connecting to a virtual machine console will be problematic with screwy DNS. 

So I took a nice trip up to Boston a couple of weeks ago for a 2 day partner training course on Hyper-V and SCVMM. We have Hyper-V up and running in the Labs at
FIOS network test over hardwire connection.
Business class DSL with VOIP at an office over hardwire connection.
Comcast residential cable speeds over a hardwire connection.
Business class Optimum Online cable over a Wireless B connection.
Business class Optimum Online cable over a hardwire connection.
Nothing really earth shattering but it looks like the news of the new name is out in the
![clip_image002[5] clip_image002[5]](http://lh4.ggpht.com/_7FQVgA2yL90/STcDf969JLI/AAAAAAAADgQ/S9NSzc1r5Fw/clip_image002%5B5%5D%5B4%5D.jpg?imgmax=800)
![clip_image004[5] clip_image004[5]](http://lh3.ggpht.com/_7FQVgA2yL90/STcDgCaHB9I/AAAAAAAADgU/PQUMPGp2sCc/clip_image004%5B5%5D%5B6%5D.jpg?imgmax=800)
![clip_image006[14] clip_image006[14]](http://lh5.ggpht.com/_7FQVgA2yL90/STcDgTtIWNI/AAAAAAAADgY/FNcGM1LBJjk/clip_image006%5B14%5D%5B4%5D.jpg?imgmax=800)
![clip_image008[7] clip_image008[7]](http://lh6.ggpht.com/_7FQVgA2yL90/STcDgoVw7hI/AAAAAAAADgc/_FSzKaKMHrg/clip_image008%5B7%5D%5B4%5D.jpg?imgmax=800)
![clip_image010[5] clip_image010[5]](http://lh6.ggpht.com/_7FQVgA2yL90/STcDg_u_yII/AAAAAAAADgg/5acyP94r_sY/clip_image010%5B5%5D%5B4%5D.jpg?imgmax=800)
![clip_image012[11] clip_image012[11]](http://lh6.ggpht.com/_7FQVgA2yL90/STcDhRbtAqI/AAAAAAAADgk/gicl_G-Or7E/clip_image012%5B11%5D%5B3%5D.jpg?imgmax=800)
![clip_image014[5] clip_image014[5]](http://lh5.ggpht.com/_7FQVgA2yL90/STcDhuG_anI/AAAAAAAADgo/558KF8jlUNE/clip_image014%5B5%5D%5B3%5D.jpg?imgmax=800)

Recently, I had the opportunity to call VMware technical support and received a fantastic tip to aid in troubleshooting networking issues. 