<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>highball.se &#187; vmware</title>
	<atom:link href="http://highball.se/tag/vmware/feed/" rel="self" type="application/rss+xml" />
	<link>http://highball.se</link>
	<description>Out of Clutter, Find Simplicity</description>
	<lastBuildDate>Thu, 05 Aug 2010 06:47:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>How I ThinApp:ed Office 2007 for both Windows XP and Windows 7</title>
		<link>http://highball.se/2009/11/how-i-thinapped-office-2007-for-both-windows-xp-and-windows-7/</link>
		<comments>http://highball.se/2009/11/how-i-thinapped-office-2007-for-both-windows-xp-and-windows-7/#comments</comments>
		<pubDate>Fri, 13 Nov 2009 15:42:59 +0000</pubDate>
		<dc:creator>Carl-Fredrik</dc:creator>
				<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[Microsoft Office 2007]]></category>
		<category><![CDATA[thinapp]]></category>
		<category><![CDATA[vmware]]></category>
		<category><![CDATA[Windows 7]]></category>
		<category><![CDATA[Windows XP]]></category>

		<guid isPermaLink="false">http://highball.se/?p=390</guid>
		<description><![CDATA[
This week I have played around quite a bit with the latest version of ThinApp from VMware (version 4.0.4). The goal have been to make a ThinApp package of Microsoft Office 2007.
The only problem have been to create a single working package for Windows XP and Windows 7 (32-bit and 64-bit).
Yesterday I finally made it!
Here&#8217;s [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://highball.se/wp-content/uploads/2009/11/thinapp-diagram-deploy.jpg"><img class="alignnone size-medium wp-image-392" title="thinapp-diagram-deploy" src="http://highball.se/wp-content/uploads/2009/11/thinapp-diagram-deploy-300x194.jpg" alt="thinapp-diagram-deploy" width="300" height="194" /></a></p>
<p>This week I have played around quite a bit with the latest version of ThinApp from VMware (version 4.0.4). The goal have been to make a ThinApp package of Microsoft Office 2007.</p>
<div>The only problem have been to create a single working package for Windows XP and Windows 7 (32-bit and 64-bit).</div>
<div>Yesterday I finally made it!</div>
<div>Here&#8217;s how I did it&#8230;</div>
<div>
<ol style="clear: both">
<li>Install a clean install of Windows XP PRO</li>
<li>Install .NET 2 and 3</li>
<li>Run a complete Windows Update</li>
<li>Install ThinApp 4.0.4</li>
<li>ThinApp the Office installation by following [<a href="http://blogs.vmware.com/thinapp/2008/10/how-to-thinap-1.html" target="_blank">Step by Step Instructions on How to ThinApp Microsoft Office 2007</a>] but during the Office 2007 installation choose to install the application to C:\Office2007 instead of the regular %Program Files%. This will fix the problem with 32-bit and 64-bit having different paths to %program files% (On 64-bit editions %Program FIles% points to <em>Program Files</em> and not <em>Program Files (x86)</em>)</li>
</ol>
</div>
<p style="clear: both">ThinApp is a wonderful application!</p>
<p><br class="final-break" style="clear: both" /></p>
]]></content:encoded>
			<wfw:commentRss>http://highball.se/2009/11/how-i-thinapped-office-2007-for-both-windows-xp-and-windows-7/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>New KB about the problem with VI-Client in Windows 7</title>
		<link>http://highball.se/2009/11/new-kb-about-the-problem-with-vi-client-in-windows-7/</link>
		<comments>http://highball.se/2009/11/new-kb-about-the-problem-with-vi-client-in-windows-7/#comments</comments>
		<pubDate>Wed, 11 Nov 2009 22:40:58 +0000</pubDate>
		<dc:creator>Carl-Fredrik</dc:creator>
				<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[vmware]]></category>
		<category><![CDATA[Windows 7]]></category>
		<category><![CDATA[Windows Server 2008]]></category>

		<guid isPermaLink="false">http://highball.se/?p=382</guid>
		<description><![CDATA[
Today I came across a KB article about the problem with VI-Client in Windows 7.
Link: Cannot launch vSphere Client after installing in Windows 7 or Windows 2008 R2
]]></description>
			<content:encoded><![CDATA[<p><img class="alignnone" title="VMware Logo" src="http://www.abbatech.com/partners/vmware/vmware-logo.jpg" alt="" width="361" height="138" /></p>
<p>Today I came across a KB article about the problem with VI-Client in Windows 7.</p>
<p>Link: <a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1011329">Cannot launch vSphere Client after installing in Windows 7 or Windows 2008 R2</a></p>
]]></content:encoded>
			<wfw:commentRss>http://highball.se/2009/11/new-kb-about-the-problem-with-vi-client-in-windows-7/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How-to auto Login to Virtual Center with VI Client</title>
		<link>http://highball.se/2009/08/how-to-auto-login-to-virtual-center-with-vi-client/</link>
		<comments>http://highball.se/2009/08/how-to-auto-login-to-virtual-center-with-vi-client/#comments</comments>
		<pubDate>Wed, 26 Aug 2009 07:00:39 +0000</pubDate>
		<dc:creator>Carl-Fredrik</dc:creator>
				<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[tips]]></category>
		<category><![CDATA[vmware]]></category>

		<guid isPermaLink="false">http://highball.se/?p=366</guid>
		<description><![CDATA[vladan.fr posted how you can create a auto login to your Virtual Center server.
via How-to auto Login to Virtual Center with VI Client.
]]></description>
			<content:encoded><![CDATA[<p>vladan.fr posted how you can create a auto login to your Virtual Center server.</p>
<p>via <a href="http://feedproxy.google.com/~r/EsxVirtualization/~3/ltjWoVsl5K0/">How-to auto Login to Virtual Center with VI Client</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://highball.se/2009/08/how-to-auto-login-to-virtual-center-with-vi-client/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Latest version of VMware converter is out!</title>
		<link>http://highball.se/2009/04/latest-version-of-vmware-converter-is-out/</link>
		<comments>http://highball.se/2009/04/latest-version-of-vmware-converter-is-out/#comments</comments>
		<pubDate>Wed, 29 Apr 2009 15:05:30 +0000</pubDate>
		<dc:creator>Carl-Fredrik</dc:creator>
				<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[converter]]></category>
		<category><![CDATA[vmware]]></category>

		<guid isPermaLink="false">http://highball.se/2009/04/latest-version-of-vmware-converter-is-out/</guid>
		<description><![CDATA[Yesterday I tested the latest version of VMware converter. Or VMware vCenter Converter..
I really liked the new version!

I can&#8217;t wait for the new VMware suit to get released! :)
Download: http://vmware.com/download/converter/

]]></description>
			<content:encoded><![CDATA[<p style="clear: both"><a href="http://highball.se/wp-content/uploads/2009/04/vmwareconverter-full.jpg" class="image-link"><img class="linked-to-original" src="http://highball.se/wp-content/uploads/2009/04/vmwareconverter-thumb.jpg" height="232" align="left" width="379" style=" display: inline; float: left; margin: 0 10px 10px 0;" /></a><br style="clear: both" />Yesterday I tested the latest version of VMware converter. Or VMware vCenter Converter..</p>
<p style="clear: both">I really liked the new version!</p>
<p style="clear: both"><a href="http://highball.se/wp-content/uploads/2009/04/picture-1.png" class="image-link"><img class="linked-to-original" src="http://highball.se/wp-content/uploads/2009/04/picture-1-thumb.png" height="289" width="380" style=" text-align: center; display: block; margin: 0 auto 10px;" /></a></p>
<p style="clear: both"><a href="http://highball.se/wp-content/uploads/2009/04/picture-4.png" class="image-link"><img class="linked-to-original" src="http://highball.se/wp-content/uploads/2009/04/picture-4-thumb.png" height="297" width="380" style=" text-align: center; display: block; margin: 0 auto 10px;" /></a>I can&#8217;t wait for the new VMware suit to get released! :)</p>
<p style="clear: both">Download: <a href="http://vmware.com/download/converter/" target="_blank">http://vmware.com/download/converter/</a></p>
<p><br class="final-break" style="clear: both" /></p>
]]></content:encoded>
			<wfw:commentRss>http://highball.se/2009/04/latest-version-of-vmware-converter-is-out/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Manage VMware server 2.0 from VI client</title>
		<link>http://highball.se/2008/12/manage-vmware-server-20-from-vi-client/</link>
		<comments>http://highball.se/2008/12/manage-vmware-server-20-from-vi-client/#comments</comments>
		<pubDate>Wed, 10 Dec 2008 16:04:20 +0000</pubDate>
		<dc:creator>Carl-Fredrik</dc:creator>
				<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[tips]]></category>
		<category><![CDATA[vmware]]></category>

		<guid isPermaLink="false">http://highball.se/?p=70</guid>
		<description><![CDATA[If you have tested the latest version of VMware server 2.0 you&#8217;ll notice the lack of a decent console interface. In my personal opinion the web console leaves much to the imagination.
Luckily there is a quick fix. You can use the Virtual infrastructure client, the one that is used with the VI3 suit. All you [...]]]></description>
			<content:encoded><![CDATA[<p>If you have tested the latest version of VMware server 2.0 you&#8217;ll notice the lack of a decent console interface. In my personal opinion the web console leaves much to the imagination.</p>
<p>Luckily there is a quick fix. You can use the Virtual infrastructure client, the one that is used with the VI3 suit. All you have to point the client to the address used by the standard web-gui of the VMware 2.0 server.</p>
<p><a href="http://highball.se/wp-content/uploads/2008/12/2008-12-10_1653.png"><img class="aligncenter size-medium wp-image-72" title="2008-12-10_1653" src="http://highball.se/wp-content/uploads/2008/12/2008-12-10_1653.png" alt="" width="300" height="257" /></a></p>
<p>Works like a charm.</p>
<p>Source:</p>
]]></content:encoded>
			<wfw:commentRss>http://highball.se/2008/12/manage-vmware-server-20-from-vi-client/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Enable SSH on VMware ESXi 3.5 Update 2</title>
		<link>http://highball.se/2008/11/enable-ssh-on-vmware-esxi-35-update-2/</link>
		<comments>http://highball.se/2008/11/enable-ssh-on-vmware-esxi-35-update-2/#comments</comments>
		<pubDate>Mon, 24 Nov 2008 09:37:28 +0000</pubDate>
		<dc:creator>Carl-Fredrik</dc:creator>
				<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[ESXi]]></category>
		<category><![CDATA[SSH]]></category>
		<category><![CDATA[vmware]]></category>

		<guid isPermaLink="false">http://highball.se/?p=18</guid>
		<description><![CDATA[I found a great way to enable SSH on ESXi.

At the console of the ESXi host, press ALT-F1 to access the console window.
Enter unsupported in the console and then press Enter. You will not see the text you type in.
If you typed in unsupported correctly, you will see the Tech Support Mode warning and a [...]]]></description>
			<content:encoded><![CDATA[<p>I found a great way to enable SSH on ESXi.</p>
<ol>
<li>At the console of the ESXi host, press ALT-F1 to access the console window.</li>
<li>Enter <strong>unsupported</strong> in the console and then press Enter. You will not see the text you type in.</li>
<li>If you typed in unsupported correctly, you will see the Tech Support Mode warning and a password prompt. Enter the password for the root login.</li>
<li>You should then see the prompt of ~ #. Edit the file inetd.conf (enter the command <strong>vi /etc/inetd.conf</strong>).</li>
<li>Find the line that begins with #ssh and remove the #. Then save the file. If you&#8217;re new to using vi, then move the cursor down to #ssh line and then press the Insert key. Move the cursor over one space and then hit backspace to delete the #. Then press ESC and type in <strong>:wq</strong> to save the file and exit vi. If you make a mistake, you can press the ESC key and then type it :q! to quit vi without saving the file.</li>
<li>Once you&#8217;ve closed the vi editor, run the command <strong>/sbin/services.sh restart</strong> to restart the management services. You&#8217;ll now be able to connect to the ESXi host with a SSH client.</li>
</ol>
<p>With Update 2 the service.sh command no longer restarts the inetd process which enables SSH access. You can either restart your host or run <strong>ps | grep inetd </strong>to determine the process ID for the inetd process. The output of the command will be something like 1299 1299 busybox      inetd, and the process ID is 1299. Then run <strong>kill -HUP &lt;process_id&gt; </strong> (kill  -HUP 1299 in this example) and you&#8217;ll then be able to access the host via SSH.</p>
<p>Original post: <a href="http://www.vm-help.com/esx/esx3i/ESXi_enable_SSH.php">http://www.vm-help.com/esx/esx3i/ESXi_enable_SSH.php</a></p>
]]></content:encoded>
			<wfw:commentRss>http://highball.se/2008/11/enable-ssh-on-vmware-esxi-35-update-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
