<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Spiceworks with VMware</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/server-virtualization/spiceworks-with-vmware/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/server-virtualization/spiceworks-with-vmware/</link>
	<description>A SearchServerVirtualization.com blog</description>
	<pubDate>Sat, 28 Nov 2009 22:07:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Akp982</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/spiceworks-with-vmware/#comment-1570</link>
		<dc:creator>Akp982</dc:creator>
		<pubDate>Sun, 22 Mar 2009 10:21:25 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2007/03/19/spiceworks-with-vmware/#comment-1570</guid>
		<description>Spiceworks is now 3.6, it is very much inproved from the version in 2007 and has better support for VMware and Mac and Linux.

With a huge community now behind spiceworks its getting better quickly

Spiceworks is a free “everything IT” tool that delivers nearly everything an IT pro needs to simplify your job. Designed for small- and medium-sized businesses, Spiceworks single, easy-to-use interface combines network inventory, monitoring, troubleshooting and reporting with an easy to use help desk. And, it connects you with a community of over half-a-million other IT pros to share ideas, best practices and product recommendations, and in the spirit of helping each other solve problems and make the IT day easier.

And, the best part? It's free, thanks to top technology vendors that sponsor Spiceworks!

Pop along to www.spiceworks.com for more info :)</description>
		<content:encoded><![CDATA[<p>Spiceworks is now 3.6, it is very much inproved from the version in 2007 and has better support for VMware and Mac and Linux.</p>
<p>With a huge community now behind spiceworks its getting better quickly</p>
<p>Spiceworks is a free “everything IT” tool that delivers nearly everything an IT pro needs to simplify your job. Designed for small- and medium-sized businesses, Spiceworks single, easy-to-use interface combines network inventory, monitoring, troubleshooting and reporting with an easy to use help desk. And, it connects you with a community of over half-a-million other IT pros to share ideas, best practices and product recommendations, and in the spirit of helping each other solve problems and make the IT day easier.</p>
<p>And, the best part? It&#8217;s free, thanks to top technology vendors that sponsor Spiceworks!</p>
<p>Pop along to&nbsp;&lt;a href="http://www.spiceworks.com" title="http://www.spiceworks. " target="_blank"&gt;www.spiceworks.com&lt;/a&gt; for more info <img src='http://itknowledgeexchange.techtarget.com/server-virtualization/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GParted: Save yourself from virtual test screw-ups &#8212; Server Virtualization Blog</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/spiceworks-with-vmware/#comment-1053</link>
		<dc:creator>GParted: Save yourself from virtual test screw-ups &#8212; Server Virtualization Blog</dc:creator>
		<pubDate>Fri, 18 Jan 2008 21:27:35 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2007/03/19/spiceworks-with-vmware/#comment-1053</guid>
		<description>[...] Todays episode is&#8230; screwing up your test environment and fixing it. As many know, I test management tools like some people switch socks. I have a simple theory on it - if what I&#8217;m using could be better, and there&#8217;s no business impact in switching, I&#8217;m going to switch. I went from Groundwork Open Source to Spiceworks 1.0 (see my prior post here) to Hyperic. Spiceworks 2.0 is out (and has been for some time), and it&#8217;s even spicier than the last version, although the Chili Peppers were missing for a while. So, time to put it into the demo lab, right? Absolutely! A little short on time? Of course! In so being, I hosed that Spiceworks 2.0 demo box from sheer stupidity. And I mean sheer stupidity. I didn&#8217;t follow any best practices. The worst thing I did was to have put on the app on a default XP build image. It didn&#8217;t need to be on a server OS for the initial testing phase, and I had a blank XP image ready to go. To channel my Inner Yoda - Saved myself some setup time I did. Hosed myself in the long run I had. [...]</description>
		<content:encoded><![CDATA[<p>[...] Todays episode is&#8230; screwing up your test environment and fixing it. As many know, I test management tools like some people switch socks. I have a simple theory on it - if what I&#8217;m using could be better, and there&#8217;s no business impact in switching, I&#8217;m going to switch. I went from Groundwork Open Source to Spiceworks 1.0 (see my prior post here) to Hyperic. Spiceworks 2.0 is out (and has been for some time), and it&#8217;s even spicier than the last version, although the Chili Peppers were missing for a while. So, time to put it into the demo lab, right? Absolutely! A little short on time? Of course! In so being, I hosed that Spiceworks 2.0 demo box from sheer stupidity. And I mean sheer stupidity. I didn&#8217;t follow any best practices. The worst thing I did was to have put on the app on a default XP build image. It didn&#8217;t need to be on a server OS for the initial testing phase, and I had a blank XP image ready to go. To channel my Inner Yoda - Saved myself some setup time I did. Hosed myself in the long run I had. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->