<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: PowerCLI: Set-dvSwitch</title>
	<atom:link href="http://ict-freak.nl/2009/10/06/powercli-set-dvswitch/feed/" rel="self" type="application/rss+xml" />
	<link>http://ict-freak.nl/2009/10/06/powercli-set-dvswitch/</link>
	<description>VMware, Linux, Scripting...</description>
	<lastBuildDate>Mon, 21 May 2012 13:28:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: afokkema</title>
		<link>http://ict-freak.nl/2009/10/06/powercli-set-dvswitch/comment-page-1/#comment-15501</link>
		<dc:creator><![CDATA[afokkema]]></dc:creator>
		<pubDate>Fri, 25 Mar 2011 18:41:51 +0000</pubDate>
		<guid isPermaLink="false">http://ictfreak.wordpress.com/2009/10/06/powercli-set-dvswitch/#comment-15501</guid>
		<description><![CDATA[Thanks for the tip.]]></description>
		<content:encoded><![CDATA[<p>Thanks for the tip.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VirtualizationCOE</title>
		<link>http://ict-freak.nl/2009/10/06/powercli-set-dvswitch/comment-page-1/#comment-15500</link>
		<dc:creator><![CDATA[VirtualizationCOE]]></dc:creator>
		<pubDate>Fri, 25 Mar 2011 17:52:53 +0000</pubDate>
		<guid isPermaLink="false">http://ictfreak.wordpress.com/2009/10/06/powercli-set-dvswitch/#comment-15500</guid>
		<description><![CDATA[We solved our own issue with the help of Onyx.    You need to add some additional device specs to maintain your previous NICS settings:

Here is the updated code:

$spec = New-Object VMware.Vim.VirtualMachineConfigSpec
$devChange = New-Object VMware.Vim.VirtualDeviceConfigSpec
$devChange.operation = &quot;edit&quot;
 
$dev = New-Object (&quot;VMware.Vim.&quot; + $tgtdev.GetType().Name)
$dev.deviceInfo = New-Object VMware.Vim.Description
$dev.deviceInfo.label = $tgtdev.DeviceInfo.Label
$dev.deviceInfo.summary = $tgtdev.DeviceInfo.Summary
$dev.Backing = New-Object VMware.Vim.VirtualEthernetCardDistributedVirtualPortBackingInfo
$dev.Backing.Port = New-Object VMware.Vim.DistributedVirtualSwitchPortConnection
$dev.Backing.Port.PortgroupKey = $dvPGKey
$dev.Backing.Port.SwitchUuid = $dvSwitchUuid
$dev.Key = $tgtdev.Key

$dev.connectable = New-Object VMware.Vim.VirtualDeviceConnectInfo
$dev.connectable.startConnected = $tgtdev.connectable.startConnected
$dev.connectable.allowGuestControl = $tgtdev.connectable.allowGuestControl
$dev.connectable.connected = $tgtdev.connectable.connected
$dev.connectable.status = $tgtdev.connectable.status
$dev.controllerKey = $tgtdev.controllerKey
$dev.unitNumber = $tgtdev.unitNumber
$dev.addressType = $tgtdev.addressType
$dev.macAddress = $tgtdev.MacAddress
$dev.wakeOnLanEnabled = $tgtdev.wakeOnLanEnabled

$devChange.Device = $dev
$spec.deviceChange = $devChange
 		
$taskMoRef = $vm.ReconfigVM_Task($spec)]]></description>
		<content:encoded><![CDATA[<p>We solved our own issue with the help of Onyx.    You need to add some additional device specs to maintain your previous NICS settings:</p>
<p>Here is the updated code:</p>
<p>$spec = New-Object VMware.Vim.VirtualMachineConfigSpec<br />
$devChange = New-Object VMware.Vim.VirtualDeviceConfigSpec<br />
$devChange.operation = &#8220;edit&#8221;</p>
<p>$dev = New-Object (&#8220;VMware.Vim.&#8221; + $tgtdev.GetType().Name)<br />
$dev.deviceInfo = New-Object VMware.Vim.Description<br />
$dev.deviceInfo.label = $tgtdev.DeviceInfo.Label<br />
$dev.deviceInfo.summary = $tgtdev.DeviceInfo.Summary<br />
$dev.Backing = New-Object VMware.Vim.VirtualEthernetCardDistributedVirtualPortBackingInfo<br />
$dev.Backing.Port = New-Object VMware.Vim.DistributedVirtualSwitchPortConnection<br />
$dev.Backing.Port.PortgroupKey = $dvPGKey<br />
$dev.Backing.Port.SwitchUuid = $dvSwitchUuid<br />
$dev.Key = $tgtdev.Key</p>
<p>$dev.connectable = New-Object VMware.Vim.VirtualDeviceConnectInfo<br />
$dev.connectable.startConnected = $tgtdev.connectable.startConnected<br />
$dev.connectable.allowGuestControl = $tgtdev.connectable.allowGuestControl<br />
$dev.connectable.connected = $tgtdev.connectable.connected<br />
$dev.connectable.status = $tgtdev.connectable.status<br />
$dev.controllerKey = $tgtdev.controllerKey<br />
$dev.unitNumber = $tgtdev.unitNumber<br />
$dev.addressType = $tgtdev.addressType<br />
$dev.macAddress = $tgtdev.MacAddress<br />
$dev.wakeOnLanEnabled = $tgtdev.wakeOnLanEnabled</p>
<p>$devChange.Device = $dev<br />
$spec.deviceChange = $devChange</p>
<p>$taskMoRef = $vm.ReconfigVM_Task($spec)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VirtualizationCOE</title>
		<link>http://ict-freak.nl/2009/10/06/powercli-set-dvswitch/comment-page-1/#comment-15496</link>
		<dc:creator><![CDATA[VirtualizationCOE]]></dc:creator>
		<pubDate>Fri, 25 Mar 2011 14:05:33 +0000</pubDate>
		<guid isPermaLink="false">http://ictfreak.wordpress.com/2009/10/06/powercli-set-dvswitch/#comment-15496</guid>
		<description><![CDATA[We are using this to migrate VM&#039;s from standard vSwitches to vDS.  The only problem we are having is that the MAC addresses seem to change on the NICs after migration.  Is there a way to avoid this?]]></description>
		<content:encoded><![CDATA[<p>We are using this to migrate VM&#8217;s from standard vSwitches to vDS.  The only problem we are having is that the MAC addresses seem to change on the NICs after migration.  Is there a way to avoid this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VMware vSphere - виртуализация ЦОД &#187; Что такое и как работает vSphere 4.0 vSphere 4.0 vNetwork Distributed Switch (vDS).</title>
		<link>http://ict-freak.nl/2009/10/06/powercli-set-dvswitch/comment-page-1/#comment-10591</link>
		<dc:creator><![CDATA[VMware vSphere - виртуализация ЦОД &#187; Что такое и как работает vSphere 4.0 vSphere 4.0 vNetwork Distributed Switch (vDS).]]></dc:creator>
		<pubDate>Sun, 11 Oct 2009 20:05:41 +0000</pubDate>
		<guid isPermaLink="false">http://ictfreak.wordpress.com/2009/10/06/powercli-set-dvswitch/#comment-10591</guid>
		<description><![CDATA[[...] Blog Posts: Eric Sloof, Barry Combs, Luc Dekens, ICT-Freak [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Blog Posts: Eric Sloof, Barry Combs, Luc Dekens, ICT-Freak [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vSphere 4.0 vNetwork Distributed Switch (vDS) - Video Demonstration + Architecture Diagram &#124; The deep core of the phenomena&#124; HyperViZor</title>
		<link>http://ict-freak.nl/2009/10/06/powercli-set-dvswitch/comment-page-1/#comment-10579</link>
		<dc:creator><![CDATA[vSphere 4.0 vNetwork Distributed Switch (vDS) - Video Demonstration + Architecture Diagram &#124; The deep core of the phenomena&#124; HyperViZor]]></dc:creator>
		<pubDate>Sat, 10 Oct 2009 09:39:56 +0000</pubDate>
		<guid isPermaLink="false">http://ictfreak.wordpress.com/2009/10/06/powercli-set-dvswitch/#comment-10579</guid>
		<description><![CDATA[[...] Blog Posts: Eric Sloof, Barry Combs, Luc Dekens, ICT-Freak [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Blog Posts: Eric Sloof, Barry Combs, Luc Dekens, ICT-Freak [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitter Trackbacks for PowerCLI: Set-dvSwitch « ICT-Freak.nl [ict-freak.nl] on Topsy.com</title>
		<link>http://ict-freak.nl/2009/10/06/powercli-set-dvswitch/comment-page-1/#comment-10572</link>
		<dc:creator><![CDATA[Twitter Trackbacks for PowerCLI: Set-dvSwitch « ICT-Freak.nl [ict-freak.nl] on Topsy.com]]></dc:creator>
		<pubDate>Tue, 06 Oct 2009 19:59:35 +0000</pubDate>
		<guid isPermaLink="false">http://ictfreak.wordpress.com/2009/10/06/powercli-set-dvswitch/#comment-10572</guid>
		<description><![CDATA[[...] PowerCLI: Set-dvSwitch « ICT-Freak.nl  ict-freak.nl/2009/10/06/powercli-set-dvswitch &#8211; view page &#8211; cached  Last weekend I was playing around with the new dvSwitch feature in vSphere. So I created a dvSwitch and wanted to migrate my VM’s to it. Unfortunately this was not possible with the current version... (Read more)Last weekend I was playing around with the new dvSwitch feature in vSphere. So I created a dvSwitch and wanted to migrate my VM’s to it. Unfortunately this was not possible with the current version of PowerCLI. Normally you should be able to change the Network switch via: Get-VM &#124; Get-NetworkAdapter ` &#124; Set-NetworkAdapter -NetworkName &quot;traditional vswitch&quot; -Confirm:$false (Read less) &#8212; From the page [...]]]></description>
		<content:encoded><![CDATA[<p>[...] PowerCLI: Set-dvSwitch « ICT-Freak.nl  ict-freak.nl/2009/10/06/powercli-set-dvswitch &ndash; view page &ndash; cached  Last weekend I was playing around with the new dvSwitch feature in vSphere. So I created a dvSwitch and wanted to migrate my VM’s to it. Unfortunately this was not possible with the current version&#8230; (Read more)Last weekend I was playing around with the new dvSwitch feature in vSphere. So I created a dvSwitch and wanted to migrate my VM’s to it. Unfortunately this was not possible with the current version of PowerCLI. Normally you should be able to change the Network switch via: Get-VM | Get-NetworkAdapter ` | Set-NetworkAdapter -NetworkName &quot;traditional vswitch&quot; -Confirm:$false (Read less) &mdash; From the page [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

