<?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>A Technical Journey &#187; Vmware</title>
	<atom:link href="http://www.technicaljourney.com/category/vmware/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.technicaljourney.com</link>
	<description>www.technicaljourney.com - Web Blog Of Paul McSharry, Technical Consultant &#38; Trainer.</description>
	<lastBuildDate>Sun, 19 Sep 2010 15:30:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Disable Copy &amp; Paste in a VMware guest Virtual machine</title>
		<link>http://www.technicaljourney.com/2010/09/disable-copy-paste-in-a-vmware-guest-virtual-machine/</link>
		<comments>http://www.technicaljourney.com/2010/09/disable-copy-paste-in-a-vmware-guest-virtual-machine/#comments</comments>
		<pubDate>Sun, 19 Sep 2010 15:28:40 +0000</pubDate>
		<dc:creator>Paul McSharry</dc:creator>
				<category><![CDATA[Vmware]]></category>

		<guid isPermaLink="false">http://www.technicaljourney.com/?p=213</guid>
		<description><![CDATA[VMware tools provides a copy and paste function between the machine running the vSphere client and the guest virtual machine. In some production environments this maybe inappropriate. It is possible to disable this feature on a per virtual machine basis, by editing the guest Virtual machine configuration (.vmx) file. Procedure 1. Log into your vCenter client [...]]]></description>
			<content:encoded><![CDATA[<p>VMware tools provides a copy and paste function between the machine running the vSphere client and the guest virtual machine.<br />
In some production environments this maybe inappropriate.</p>
<p>It is possible to disable this feature on a per virtual machine basis, by editing the guest Virtual machine configuration (.vmx) file.</p>
<p><em>Procedure<br />
</em>1. Log into your vCenter client<br />
2. Power off the guest Virtual machine.<br />
3. Open advanced options  ( Edit Settings &gt; Options &gt; General &gt; Configuration Parameters )<br />
4. Add the following parameters (click <strong>Add Row</strong>),<br />
            <em><strong>  isolation.tools.setGUIOptions.enable = false<br />
              isolation.tools.copy.disable = true<br />
              isolation.tools.paste.disable = true</strong></em></p>
<p><strong> </strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.technicaljourney.com/2010/09/disable-copy-paste-in-a-vmware-guest-virtual-machine/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to reset a forgotten or lost Root password on VMware vSphere ESX 4</title>
		<link>http://www.technicaljourney.com/2010/08/how-to-reset-a-forgotten-or-lost-root-password-on-vmware-vsphere-esx-4/</link>
		<comments>http://www.technicaljourney.com/2010/08/how-to-reset-a-forgotten-or-lost-root-password-on-vmware-vsphere-esx-4/#comments</comments>
		<pubDate>Thu, 12 Aug 2010 10:09:12 +0000</pubDate>
		<dc:creator>Paul McSharry</dc:creator>
				<category><![CDATA[Vmware]]></category>

		<guid isPermaLink="false">http://www.technicaljourney.com/?p=205</guid>
		<description><![CDATA[In the event the root password is unknown,  connect to the ESX host console and restart the machine. 1. When the ESX host boots to the grub menu, hit the “a” key. 2. Add the command  “single” to the string and click enter 3. Wait for ESX to go through the boot process 4. At [...]]]></description>
			<content:encoded><![CDATA[<p>In the event the root password is unknown,  connect to the ESX host console and restart the machine.</p>
<p>1. When the ESX host boots to the grub menu, hit the “a” key.<br />
2. Add the command  “single” to the string and click enter<br />
3. Wait for ESX to go through the boot process<br />
4. At the command prompt type “passwd.”<br />
5. Enter your new password.<br />
6. Restart the host ie.  shutdown -r now</p>
<p>This process is only used to reset a lost or forgotten password. <br />
A video demo of this process is shown on my virtualisation website <a href="http://www.elasticsky.co.uk/videos">http://www.elasticsky.co.uk/videos</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.technicaljourney.com/2010/08/how-to-reset-a-forgotten-or-lost-root-password-on-vmware-vsphere-esx-4/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Install VMware vCenter On 64 Bit Windows Server</title>
		<link>http://www.technicaljourney.com/2010/07/install-vcenter-64-bit/</link>
		<comments>http://www.technicaljourney.com/2010/07/install-vcenter-64-bit/#comments</comments>
		<pubDate>Sun, 18 Jul 2010 21:40:15 +0000</pubDate>
		<dc:creator>Paul McSharry</dc:creator>
				<category><![CDATA[Vmware]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://www.technicaljourney.com/?p=199</guid>
		<description><![CDATA[The vCenter server role is a critical component of a vSphere deployment.   The role requires a database  such as SQL or Oracle.   To install the vCentre a 32 bit ODBC connection is required.  When installing the role on a 64 bit server OS (ie Windows 2008 R2),  the installer will fail giving the error shown in [...]]]></description>
			<content:encoded><![CDATA[<p>The vCenter server role is a critical component of a vSphere deployment.   The role requires a database  such as SQL or Oracle.  </p>
<p>To install the vCentre a 32 bit ODBC connection is required.  When installing the role on a 64 bit server OS (ie Windows 2008 R2),  the installer will fail giving the error shown in the screenshot below.</p>
<p><a href="http://www.technicaljourney.com/wp-content/uploads/2010/07/32bit_required.jpg"><img class="size-medium wp-image-200 alignleft" title="32bit_required" src="http://www.technicaljourney.com/wp-content/uploads/2010/07/32bit_required-300x103.jpg" alt="" width="300" height="103" /></a></p>
<p>To configure a 32 BIT Odbc connection on a 64 Bit version of windows use the following;</p>
<p><em>Start &gt; Run<br />
%systemdrive%\Windows\SysWoW64\Odbcad32.exe<br />
Click ok<br />
Select System DSN  and complete the wizard in the normal manner</em>.</p>
<p>Please note that a 32 Bit odbc connection will not be dispayed in the default 64 bit odbc data source administrator manager.  Use odbcad32.exe  to view the settings.</p>
<p><strong><em>Update : This method is for vCenter 4.0,  following the update of vCenter 4.1 , the application is now no longer a 32 bit application but a 64 bit version.  A 64 bit system dsn is required for the 4.1 edition</em></strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.technicaljourney.com/2010/07/install-vcenter-64-bit/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Add static route to VMware ESX 4 Host</title>
		<link>http://www.technicaljourney.com/2010/06/add-static-route-to-vmware-esx-4-host/</link>
		<comments>http://www.technicaljourney.com/2010/06/add-static-route-to-vmware-esx-4-host/#comments</comments>
		<pubDate>Wed, 23 Jun 2010 10:38:16 +0000</pubDate>
		<dc:creator>Paul McSharry</dc:creator>
				<category><![CDATA[Vmware]]></category>

		<guid isPermaLink="false">http://www.technicaljourney.com/?p=182</guid>
		<description><![CDATA[In a infrastructure with multiple networks,  it can be necessary to configure the routing on the ESX hosts rather than at the router. This is  achieved using the below command route add &#8211; net &#60;network ID &#62; netmask &#60;subnet mask&#62; gw &#60;gateway interface&#62; ie :   route add -net 10.44.0.0 netmask 255.255.0.0 gw 192.168.0.12 In the [...]]]></description>
			<content:encoded><![CDATA[<p>In a infrastructure with multiple networks,  it can be necessary to configure the routing on the ESX hosts rather than at the router.</p>
<p>This is  achieved using the below command</p>
<p><strong><em>route add &#8211; net &lt;network ID &gt; netmask &lt;subnet mask&gt; gw &lt;gateway interface&gt;</em></strong></p>
<p style="text-align: left;"><strong>ie :   route add -net 10.44.0.0 netmask 255.255.0.0 gw 192.168.0.12</strong></p>
<p>In the above example,  all traffic for the 10.14.X.X network will be routed via 192.168.0.12</p>
<p>Note:  This route will <strong>not be persistent through reboots</strong>.  If the ESX host is restarted the route will need to be re-added. </p>
<p>To ensure the route is persistent add the command to the bottom of the following config  file using a text editor <span style="font-family: Courier New;">/etc/rc.local</span></p>
<p><span style="font-family: Courier New;"><em>For example</em></span></p>
<p style="text-align: left;"><span style="font-family: Courier New;"><em>Change directory  &#8211;  <strong>cd /etc/</strong><br />
Open Text Editor &#8211; <strong>nano rc.local</strong><br />
Specfiy the route at the end of the file  -</em> <strong>route add -net 10.44.0.0 netmask 255.255.0.0 gw 192.168.0.12</strong> <br />
<em>Exit Text Editor  -</em> <strong>ctrl -x , Yes to confirm</strong></span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.technicaljourney.com/2010/06/add-static-route-to-vmware-esx-4-host/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Enable the Root user SSH access in vSphere ESX 4</title>
		<link>http://www.technicaljourney.com/2010/06/enable-the-root-user-ssh-access-within-vsphere-esx-4/</link>
		<comments>http://www.technicaljourney.com/2010/06/enable-the-root-user-ssh-access-within-vsphere-esx-4/#comments</comments>
		<pubDate>Sun, 20 Jun 2010 21:35:07 +0000</pubDate>
		<dc:creator>Paul McSharry</dc:creator>
				<category><![CDATA[Vmware]]></category>

		<guid isPermaLink="false">http://www.technicaljourney.com/?p=156</guid>
		<description><![CDATA[As a security meaure,  SSH access to the service console  using the Root account is disabled by default on vSPhere ESX 4.   Although not best practice,  there are times you may wish to enable access to the Root user. Method &#8211; CLI commands show in bold Login as Root to the ESX console Go to [...]]]></description>
			<content:encoded><![CDATA[<p>As a security meaure,  SSH access to the service console  using the Root account is disabled by default on vSPhere ESX 4.   Although not best practice,  there are times you may wish to enable access to the Root user.</p>
<p><em>Method &#8211; CLI commands show in bold</em></p>
<ol>
<li>Login as Root to the ESX console</li>
<li>Go to the SSH directory  &#8211;  <strong>cd /etc/ssh</strong></li>
<li>Open the ssh_config<strong>  </strong>file &#8211;  <strong>nano sshd_config</strong></li>
<li>Change PermitRootLogin no  to<strong> PermitRootLogin yes</strong></li>
<li>Save and exit the config file   &#8211; <strong>CTRL+ X , click Y to confirm</strong></li>
<li>Restart the SSHD service  &#8211; <strong>service sshd restart </strong></li>
<li>Amend the service console firewall rules -   <strong>esxcfg-firewall -e sshClient</strong> and <strong>esxcfg-firewall -e sshServer </strong></li>
</ol>
<p>The Root account should now be able to connect remotely using SSH</p>
<p>Please note, this applies to ESX only,  ESXi does not have a Service Console.   Access is provided using the remote command line interface or pearl toolkit.  SSH access can be configured to the  support mode, however it is enabled in a different manner.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.technicaljourney.com/2010/06/enable-the-root-user-ssh-access-within-vsphere-esx-4/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Inconsistent Virtual Machine folders after renaming a machine.</title>
		<link>http://www.technicaljourney.com/2010/05/inconsistent-virtual-machine-folders-after-renaming-a-machine/</link>
		<comments>http://www.technicaljourney.com/2010/05/inconsistent-virtual-machine-folders-after-renaming-a-machine/#comments</comments>
		<pubDate>Tue, 25 May 2010 14:52:03 +0000</pubDate>
		<dc:creator>Paul McSharry</dc:creator>
				<category><![CDATA[Vmware]]></category>

		<guid isPermaLink="false">http://www.technicaljourney.com/?p=154</guid>
		<description><![CDATA[When a virtual machine is renamed ,  the underlying datastore folder is unchanged.    This can cause confusion in various scenarios. To overcome this quickly and easily,  simply migrate the virtual machine datastore using storage vmotion.  During the process the virtual machine files are renamed automatically.]]></description>
			<content:encoded><![CDATA[<p>When a virtual machine is renamed ,  the underlying datastore folder is unchanged.    This can cause confusion in various scenarios.</p>
<p>To overcome this quickly and easily,  simply migrate the virtual machine datastore using storage vmotion.  During the process the virtual machine files are renamed automatically.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.technicaljourney.com/2010/05/inconsistent-virtual-machine-folders-after-renaming-a-machine/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Place an ESX Host into maintenance mode using the command line.</title>
		<link>http://www.technicaljourney.com/2010/05/place-an-esx-host-into-maintenance-mode-using-the-command-line/</link>
		<comments>http://www.technicaljourney.com/2010/05/place-an-esx-host-into-maintenance-mode-using-the-command-line/#comments</comments>
		<pubDate>Mon, 24 May 2010 13:56:41 +0000</pubDate>
		<dc:creator>Paul McSharry</dc:creator>
				<category><![CDATA[Vmware]]></category>

		<guid isPermaLink="false">http://www.technicaljourney.com/?p=151</guid>
		<description><![CDATA[To enter maintenance mode using the command line interface, vimsh -n -e /hostsvc/maintenance_mode_enter To exit maintenance mode use vimsh -n -e /hostsvc/maintenance_mode_exit]]></description>
			<content:encoded><![CDATA[<p>To enter maintenance mode using the command line interface,</p>
<p>vimsh -n -e /hostsvc/maintenance_mode_enter</p>
<p>To exit maintenance mode use</p>
<p>vimsh -n -e /hostsvc/maintenance_mode_exit</p>
]]></content:encoded>
			<wfw:commentRss>http://www.technicaljourney.com/2010/05/place-an-esx-host-into-maintenance-mode-using-the-command-line/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Checked Builds Of Windows 2008 BSOD STOP: 0x0000008E Error With Vmware</title>
		<link>http://www.technicaljourney.com/2010/04/checked-builds-of-windows-2008-bsod-stop-0x0000008e-error-with-vmware/</link>
		<comments>http://www.technicaljourney.com/2010/04/checked-builds-of-windows-2008-bsod-stop-0x0000008e-error-with-vmware/#comments</comments>
		<pubDate>Sat, 03 Apr 2010 20:01:46 +0000</pubDate>
		<dc:creator>Paul McSharry</dc:creator>
				<category><![CDATA[Vmware]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://www.technicaljourney.com/?p=142</guid>
		<description><![CDATA[When creating a Vmware Virtual Machine guest,  running a  Windows Server 2008 checked build from sources such as technet, or MSDN, a blue screen of death may occur ( ie  STOP:0x0000008E). This is caused by the windows HAL being violated within the Virtual Machine.  A fix for this issue is to  add the below line [...]]]></description>
			<content:encoded><![CDATA[<p>When creating a Vmware Virtual Machine guest,  running a  Windows Server 2008 checked build from sources such as technet, or MSDN, a blue screen of death may occur ( ie  STOP:0x0000008E).</p>
<p>This is caused by the windows HAL being violated within the Virtual Machine. </p>
<p>A fix for this issue is to  add the below line to the virtual machine&#8217;s configuration (.vmx file).</p>
<p><strong>piix4pm.smooth_acpi_timer = TRUE</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.technicaljourney.com/2010/04/checked-builds-of-windows-2008-bsod-stop-0x0000008e-error-with-vmware/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How To Install Vmware VSphere ESX 4 From USB Flash Drive</title>
		<link>http://www.technicaljourney.com/2010/04/how-to-install-vmware-vsphere-esx-4-from-usb/</link>
		<comments>http://www.technicaljourney.com/2010/04/how-to-install-vmware-vsphere-esx-4-from-usb/#comments</comments>
		<pubDate>Fri, 02 Apr 2010 18:24:53 +0000</pubDate>
		<dc:creator>Paul McSharry</dc:creator>
				<category><![CDATA[Vmware]]></category>

		<guid isPermaLink="false">http://www.technicaljourney.com/?p=135</guid>
		<description><![CDATA[In case the server  has no DVD/optial drive or  you have an iso but no DVD-r available.  It is possible to install ESX 4 using a USB flash drive. 1.  Use a bootloader application such as  Unetbootinto create a bootable flash drive using the iso (simply point to the iso file, specify the USB flash [...]]]></description>
			<content:encoded><![CDATA[<p>In case the server  has no DVD/optial drive or  you have an iso but no DVD-r available.  It is possible to install ESX 4 using a USB flash drive.</p>
<p>1.  Use a bootloader application such as  <a href="http://unetbootin.sourceforge.net/">Unetbootin</a>to create a bootable flash drive using the iso (simply point to the iso file, specify the USB flash drive and click ok) .<br />
2.  Boot the server from the USB flash drive<br />
3.  Click Tab when the ESX install options appear<br />
4.  Add the command <strong>askmedia  </strong>to the  end of the  syslinux bootloader string  that appears.</p>
<p>The ESX4 installation process will continue as normal, however an additional option of selecting a media path such as USB, FTP and NFS will be available.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.technicaljourney.com/2010/04/how-to-install-vmware-vsphere-esx-4-from-usb/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Useful Networking Commands In Vmware ESX CLI</title>
		<link>http://www.technicaljourney.com/2010/04/useful-networking-commands-in-vmware-esx-cli/</link>
		<comments>http://www.technicaljourney.com/2010/04/useful-networking-commands-in-vmware-esx-cli/#comments</comments>
		<pubDate>Thu, 01 Apr 2010 18:52:21 +0000</pubDate>
		<dc:creator>Paul McSharry</dc:creator>
				<category><![CDATA[Vmware]]></category>

		<guid isPermaLink="false">http://www.technicaljourney.com/?p=116</guid>
		<description><![CDATA[The VI Client is excellent, however when you cannot connect to the ESX host,  its time to go to the CLI. A few useful commands shown below; Network Card information: ifconfig Display the network cards availible in ESX: esxcfg-nics -l Display the network card linked to service console: esxcfg-vswitch -l Unlink Vmnic from vswitch esxcfg-vswitch [...]]]></description>
			<content:encoded><![CDATA[<div id="_mcePaste">The VI Client is excellent, however when you cannot connect to the ESX host,  its time to go to the CLI.</div>
<div>A few useful commands shown below;</div>
<blockquote>
<div>Network Card information:<strong> </strong><em><strong>ifconfig</strong></em></div>
<div id="_mcePaste">Display the network cards availible in ESX: <em><strong>esxcfg-nics -l</strong></em></div>
<div id="_mcePaste">Display the network card linked to service console: <em><strong>esxcfg-vswitch -l</strong></em></div>
<div id="_mcePaste">Unlink Vmnic from vswitch<em> </em><em><strong>esxcfg-vswitch -U vmnic0 vSwitch0  <em><strong> </strong></em></strong></em></div>
<div id="_mcePaste">link a vmnic to vSwitch0 <em><strong>esxcfg-vswitch -L vmnic1 vSwitch0</strong></em></div>
<div><em><strong><span style="font-weight: normal;">Change the Vlan ID of the console port in ESX:</span><strong> esxcfg-vswitch vSwitch0 -v 15 -p “Service Console” </strong><span style="font-weight: normal;">(where 15 is the Vlan ID)</span></strong></em></div>
</blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.technicaljourney.com/2010/04/useful-networking-commands-in-vmware-esx-cli/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

