<?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>PowerCLI &#8211; Virtualization, DBaaS &amp; Whatever Crosses My Mind</title>
	<atom:link href="https://magander.se/category/powercli/feed/" rel="self" type="application/rss+xml" />
	<link>https://magander.se</link>
	<description></description>
	<lastBuildDate>Thu, 22 Apr 2021 16:13:45 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://magander.se/wp-content/uploads/2021/01/cropped-Screenshot-2021-01-19-at-22.37.56-32x32.png</url>
	<title>PowerCLI &#8211; Virtualization, DBaaS &amp; Whatever Crosses My Mind</title>
	<link>https://magander.se</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>VMware PowerCLI 12.3 Released</title>
		<link>https://magander.se/vmware-powercli-12-3-released/</link>
		
		<dc:creator><![CDATA[Magnus Andersson]]></dc:creator>
		<pubDate>Mon, 12 Apr 2021 06:24:11 +0000</pubDate>
				<category><![CDATA[PowerCLI]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[magander]]></category>
		<category><![CDATA[magander.se]]></category>
		<category><![CDATA[npx005]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[Polwercli 11]]></category>
		<category><![CDATA[powercli 11.0.0]]></category>
		<category><![CDATA[PowerCLI 11.2.0]]></category>
		<category><![CDATA[VCDX56]]></category>
		<guid isPermaLink="false">https://magander.se/?p=13622</guid>

					<description><![CDATA[Quick note to let you know that VMware PowerCLI version 12.3 was released last week, to be more specific April 8th. I trust most of you knows that PowerCLI is built is a tool built on Windows PowerShell and used for command line management and or scripting purposes. The new release is 12.3 is a &#8230; </p><p><a class="more-link block-button" href="https://magander.se/vmware-powercli-12-3-released/">Continue reading &#187;</a>]]></description>
		
		
		
			</item>
		<item>
		<title>VMware PowerCLI 11.4.0 Released</title>
		<link>https://magander.se/vmware-powercli-11-4-0-released/</link>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Wed, 21 Aug 2019 06:21:41 +0000</pubDate>
				<category><![CDATA[PowerCLI]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[npx005]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[Polwercli 11]]></category>
		<category><![CDATA[powercli 11.0.0]]></category>
		<category><![CDATA[PowerCLI 11.2.0]]></category>
		<category><![CDATA[VCDX56]]></category>
		<guid isPermaLink="false">http://magander.se/?p=12192</guid>

					<description><![CDATA[Just a quick note to let you know that VMware just released a new version of PowerCLI which is tool built on Windows PowerShell and used for command line management or scripting purposes. The new release is 11.4.0 and this dot release comes with the following enhancements: Support for Horizon View 7.9 Storage module – &#8230; </p><p><a class="more-link block-button" href="https://magander.se/vmware-powercli-11-4-0-released/">Continue reading &#187;</a>]]></description>
		
		
		
			</item>
		<item>
		<title>VMware PowerCLI 11.2.0 Released</title>
		<link>https://magander.se/vmware-powercli-11-2-0-released/</link>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Fri, 01 Mar 2019 12:53:05 +0000</pubDate>
				<category><![CDATA[PowerCLI]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[npx005]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[Polwercli 11]]></category>
		<category><![CDATA[powercli 11.0.0]]></category>
		<category><![CDATA[PowerCLI 11.2.0]]></category>
		<category><![CDATA[VCDX56]]></category>
		<guid isPermaLink="false">http://magander.se/?p=11773</guid>

					<description><![CDATA[Just a quick note to let you know that VMware just released VMware PowerCLI 11.2. This dot release comes with quite a few improvements: VMware HCX – New module NSX-T Policy Services support OAuth based connectivity support to vCenter Server – Right now only for GovCloud instances of VMware Cloud on AWS Storage module cmdlets updated &#8230; </p><p><a class="more-link block-button" href="https://magander.se/vmware-powercli-11-2-0-released/">Continue reading &#187;</a>]]></description>
		
		
		
			</item>
		<item>
		<title>VMware PowerCLI 11.0.0 Released</title>
		<link>https://magander.se/vmware-powercli-11-0-0-released/</link>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Thu, 11 Oct 2018 21:22:57 +0000</pubDate>
				<category><![CDATA[PowerCLI]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[npx005]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[Polwercli 11]]></category>
		<category><![CDATA[powercli 11.0.0]]></category>
		<category><![CDATA[VCDX56]]></category>
		<guid isPermaLink="false">http://magander.se/?p=11312</guid>

					<description><![CDATA[Just a quick note to let you know that VMware just released VMware PowerCLI 11.0.0. In my opinion the most valuable updates are support for: Horizon View 7.6 vSphere 6.7 Update 1 vCloud Director 9.5 NSX-T 2.3 There are many more updates and changes in this release such as: New Security module Cmdlets for Host &#8230; </p><p><a class="more-link block-button" href="https://magander.se/vmware-powercli-11-0-0-released/">Continue reading &#187;</a>]]></description>
		
		
		
			</item>
		<item>
		<title>Install Microsoft PowerShell Core 6.0.1 and VMware PowerCLI 10.0.0 On macOS</title>
		<link>https://magander.se/install-microsoft-powershell-core-6-0-1-and-vmware-powercli-10-0-0-on-macos/</link>
					<comments>https://magander.se/install-microsoft-powershell-core-6-0-1-and-vmware-powercli-10-0-0-on-macos/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Fri, 02 Mar 2018 07:18:18 +0000</pubDate>
				<category><![CDATA[PowerCLI]]></category>
		<category><![CDATA[Connect-VIServer]]></category>
		<category><![CDATA[Disconnect-VIServer -confirm:$false]]></category>
		<category><![CDATA[Get-Module VMware* - ListAvailable]]></category>
		<category><![CDATA[Get-VM]]></category>
		<category><![CDATA[Install-Module -Name VMware.PowerCLI -Scope CurrentUser]]></category>
		<category><![CDATA[Microsoft PowerShell]]></category>
		<category><![CDATA[Microsoft PowerShell Core 6.0]]></category>
		<category><![CDATA[npx005]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[PowerCLI 10.0.0]]></category>
		<category><![CDATA[PowerShell Core 6.0]]></category>
		<category><![CDATA[push]]></category>
		<category><![CDATA[Set-PowerCLIConfiguration -InvalidCertificateAction Ignore]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[VMware PowerCLI]]></category>
		<category><![CDATA[VMware PowerCLI 10.0.0]]></category>
		<category><![CDATA[vSphere PowerCLI]]></category>
		<guid isPermaLink="false">http://magander.se/?p=10734</guid>

					<description><![CDATA[Really good news for all Linux &#38; MacBook users out there. A while back Microsoft released Microsoft PowerShell for Linux and MacOS and yesterday, 2018.02.28, VMware released VMware PowerCLI 10.0.0, formerly known as vSphere PowerCLI, and it also supports both platforms. To be able to run VMware PowerCLI on your MacBook you first need to &#8230; </p><p><a class="more-link block-button" href="https://magander.se/install-microsoft-powershell-core-6-0-1-and-vmware-powercli-10-0-0-on-macos/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/install-microsoft-powershell-core-6-0-1-and-vmware-powercli-10-0-0-on-macos/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Disable ESXi host firewall ports using PowerCLI</title>
		<link>https://magander.se/disable-esxi-host-firewall-ports-using-powercli/</link>
					<comments>https://magander.se/disable-esxi-host-firewall-ports-using-powercli/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Tue, 13 Sep 2016 16:46:41 +0000</pubDate>
				<category><![CDATA[ESXi]]></category>
		<category><![CDATA[PowerCLI]]></category>
		<category><![CDATA[DHCP Client]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[PowerCLI 6.3]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[Virtual SAN Clustering Service]]></category>
		<category><![CDATA[Virtual SAN Transport]]></category>
		<category><![CDATA[vSphere Web Access]]></category>
		<category><![CDATA[vvold]]></category>
		<category><![CDATA[WOL]]></category>
		<guid isPermaLink="false">http://magander.se/?p=7495</guid>

					<description><![CDATA[Updated 2017-07-06 to match ESXi 6.5 FW Rule names One thing i do for the majority of my vSphere implementations, today and previous over the years, has been to disable ESXi firewall ports not being used. There are at least a few, not always the same though, ports that will never be used no matter &#8230; </p><p><a class="more-link block-button" href="https://magander.se/disable-esxi-host-firewall-ports-using-powercli/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/disable-esxi-host-firewall-ports-using-powercli/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Upgrade ESXi 5.5 to ESXi 5.5 U1 using HP image fails</title>
		<link>https://magander.se/upgrade-esxi-5-5-to-esxi-5-5-u1-using-hp-image-fails/</link>
					<comments>https://magander.se/upgrade-esxi-5-5-to-esxi-5-5-u1-using-hp-image-fails/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Tue, 22 Jul 2014 08:29:27 +0000</pubDate>
				<category><![CDATA[ESXi]]></category>
		<category><![CDATA[PowerCLI]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[Broadcom_bootbank_net-bnx2_2.2.5d.v55.2-1OEM.550.0.0.1331820]]></category>
		<category><![CDATA[Compliance state Incompatible]]></category>
		<category><![CDATA[esxcli software profile get]]></category>
		<category><![CDATA[esxcli software vib list]]></category>
		<category><![CDATA[esxcli software vib list | grep -i bnx2]]></category>
		<category><![CDATA[esxcli software vib list | grep -i net-cnic]]></category>
		<category><![CDATA[ESXi 5.5 Update 1]]></category>
		<category><![CDATA[Hewlett Packard]]></category>
		<category><![CDATA[HP driver]]></category>
		<category><![CDATA[HP-ESXi-5.5.0-iso-5.72.27]]></category>
		<category><![CDATA[HP-ESXi-5.5.0-Update1-iso-5.74.27]]></category>
		<category><![CDATA[Incompatible]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[vib]]></category>
		<category><![CDATA[vmware -v]]></category>
		<category><![CDATA[VMware-ESXi-5.5.0-Update1-1746018-HP-5.74.27-Jun2014-depot.zip]]></category>
		<guid isPermaLink="false">http://magander.se/?p=3908</guid>

					<description><![CDATA[Before i start an upgrade i usually run two commands just to verify what build number my ESXi host currently uses and what image my ESXi host currently uses: vmware -v – shows the build number  esxcli software profile get – shows the image name and in my case the result before the upgrade was: &#8230; </p><p><a class="more-link block-button" href="https://magander.se/upgrade-esxi-5-5-to-esxi-5-5-u1-using-hp-image-fails/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/upgrade-esxi-5-5-to-esxi-5-5-u1-using-hp-image-fails/feed/</wfw:commentRss>
			<slash:comments>3</slash:comments>
		
		
			</item>
		<item>
		<title>vSphere VM vCPU to ESXi host pCPU core allocation</title>
		<link>https://magander.se/vsphere-vm-vcpu-to-esxi-host-cpu-core-allocation/</link>
					<comments>https://magander.se/vsphere-vm-vcpu-to-esxi-host-cpu-core-allocation/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Sun, 01 Jun 2014 15:51:13 +0000</pubDate>
				<category><![CDATA[ESXi]]></category>
		<category><![CDATA[PowerCLI]]></category>
		<category><![CDATA[Script]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[CPU core]]></category>
		<category><![CDATA[ESXi host]]></category>
		<category><![CDATA[ESXi host CPU]]></category>
		<category><![CDATA[ESXi host CPU core]]></category>
		<category><![CDATA[script]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[VM vCPU]]></category>
		<category><![CDATA[vSphere VM vCPU to ESXi host CPU subscription]]></category>
		<guid isPermaLink="false">http://magander.se/?p=3538</guid>

					<description><![CDATA[There has been quite a lot of discussion regarding resource utilization and resource allocation in vSphere environments lately. There are a lot of tools around doing analysis (some better than others) of your environment and gives suggestions if you need to e.g.: Add more resources (CPU, RAM, Disk, Network) to your vSphere cluster. Down size &#8230; </p><p><a class="more-link block-button" href="https://magander.se/vsphere-vm-vcpu-to-esxi-host-cpu-core-allocation/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/vsphere-vm-vcpu-to-esxi-host-cpu-core-allocation/feed/</wfw:commentRss>
			<slash:comments>14</slash:comments>
		
		
			</item>
		<item>
		<title>Create multiple VMs from existing vSphere VM using PowerCLI</title>
		<link>https://magander.se/create-multiple-vms-from-existing-vsphere-vm-using-powercli/</link>
					<comments>https://magander.se/create-multiple-vms-from-existing-vsphere-vm-using-powercli/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Tue, 25 Feb 2014 17:36:38 +0000</pubDate>
				<category><![CDATA[PowerCLI]]></category>
		<category><![CDATA[Script]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[$y="{0:D2}" -f $_]]></category>
		<category><![CDATA[0:D2]]></category>
		<category><![CDATA[create multiple VMs]]></category>
		<category><![CDATA[customspecification]]></category>
		<category><![CDATA[foreach]]></category>
		<category><![CDATA[get-cluster]]></category>
		<category><![CDATA[get-random]]></category>
		<category><![CDATA[get-vmhost]]></category>
		<category><![CDATA[Get-VMHost -state connected | Get-Random]]></category>
		<category><![CDATA[increment]]></category>
		<category><![CDATA[increment number]]></category>
		<category><![CDATA[VCDX56]]></category>
		<guid isPermaLink="false">http://magander.se/?p=3064</guid>

					<description><![CDATA[I recently published the blog post “Create multiple VMs using PowerCLI” and as i mentioned in the post i thought the next request would be a PowerCLI script to create multiple VMs from an existing vSphere virtual machine (VM). It just took a few days before the request reached my email inbox. I actually received a few &#8230; </p><p><a class="more-link block-button" href="https://magander.se/create-multiple-vms-from-existing-vsphere-vm-using-powercli/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/create-multiple-vms-from-existing-vsphere-vm-using-powercli/feed/</wfw:commentRss>
			<slash:comments>34</slash:comments>
		
		
			</item>
		<item>
		<title>Create multiple VMs using PowerCLI</title>
		<link>https://magander.se/create-multiple-vms-using-powercli/</link>
					<comments>https://magander.se/create-multiple-vms-using-powercli/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Thu, 30 Jan 2014 21:03:00 +0000</pubDate>
				<category><![CDATA[PowerCLI]]></category>
		<category><![CDATA[Script]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[$y="{0:D2}" -f $_]]></category>
		<category><![CDATA[0:D2]]></category>
		<category><![CDATA[create multiple VMs]]></category>
		<category><![CDATA[foreach]]></category>
		<category><![CDATA[get-cluster]]></category>
		<category><![CDATA[get-random]]></category>
		<category><![CDATA[get-vmhost]]></category>
		<category><![CDATA[Get-VMHost -state connected | Get-Random]]></category>
		<category><![CDATA[increment]]></category>
		<category><![CDATA[increment number]]></category>
		<category><![CDATA[VCDX56]]></category>
		<guid isPermaLink="false">http://magander.se/?p=2758</guid>

					<description><![CDATA[A couple of days ago i received a request from a customer asking for a PowerCLI script to create VMs. There were a couple of requirements for the script. Specify the number of VMs to be created. The VMs must be powered on after the creation. The VMs must be placed on all ESXi hosts &#8230; </p><p><a class="more-link block-button" href="https://magander.se/create-multiple-vms-using-powercli/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/create-multiple-vms-using-powercli/feed/</wfw:commentRss>
			<slash:comments>25</slash:comments>
		
		
			</item>
		<item>
		<title>ESXi host VMkernel.Boot.terminateVMOnPDL configuration using PowerCLI</title>
		<link>https://magander.se/esxi-host-vmkernel-boot-terminatevmonpdl-configuration-using-powercli/</link>
					<comments>https://magander.se/esxi-host-vmkernel-boot-terminatevmonpdl-configuration-using-powercli/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Tue, 21 Jan 2014 16:51:58 +0000</pubDate>
				<category><![CDATA[PowerCLI]]></category>
		<category><![CDATA[Script]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[5.1]]></category>
		<category><![CDATA[5.5]]></category>
		<category><![CDATA[configuration]]></category>
		<category><![CDATA[disk.terminateVMOnPDLDefault]]></category>
		<category><![CDATA[ESXi 5.1]]></category>
		<category><![CDATA[ESXi 5.1.x]]></category>
		<category><![CDATA[ESXi 5.5]]></category>
		<category><![CDATA[ESXi host]]></category>
		<category><![CDATA[script]]></category>
		<category><![CDATA[user interaction]]></category>
		<category><![CDATA[VMkernel.Boot.terminateVMOnPDL]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[vSphere 5.5]]></category>
		<guid isPermaLink="false">http://magander.se/?p=2731</guid>

					<description><![CDATA[I have already written a blog post about how you can configure the ESXi host  setting disk.terminateVMOnPDLDefault in vSphere version 5.1. You can find that blog post here. I have received a couple of questions about how to configure the setting, called VMkernel.Boot.terminateVMOnPDL, in ESXi 5.5 so i decided to put together a blog post about it. &#8230; </p><p><a class="more-link block-button" href="https://magander.se/esxi-host-vmkernel-boot-terminatevmonpdl-configuration-using-powercli/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/esxi-host-vmkernel-boot-terminatevmonpdl-configuration-using-powercli/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>ESXi 5.1 VMFS HeapSize configuration using PowerCLI</title>
		<link>https://magander.se/esxi-5-1-vmfs-heapsize-configuration-using-powercli/</link>
					<comments>https://magander.se/esxi-5-1-vmfs-heapsize-configuration-using-powercli/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Wed, 08 Jan 2014 09:11:24 +0000</pubDate>
				<category><![CDATA[ESXi]]></category>
		<category><![CDATA[PowerCLI]]></category>
		<category><![CDATA[Script]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[640]]></category>
		<category><![CDATA[advanced]]></category>
		<category><![CDATA[ESXi advanced configuration]]></category>
		<category><![CDATA[Heap]]></category>
		<category><![CDATA[Max Heap Size]]></category>
		<category><![CDATA[PowerCLI 5.1]]></category>
		<category><![CDATA[set-VMHostAdvancedConfiguration]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[vCenter Server 5.1]]></category>
		<category><![CDATA[VMFS3]]></category>
		<category><![CDATA[VMFS3.MaxHeapSizeMB]]></category>
		<category><![CDATA[Windows 2008 R2 Server]]></category>
		<guid isPermaLink="false">http://magander.se/?p=2860</guid>

					<description><![CDATA[There are a few of my customer still running vSphere 5.1 U1 and one of them reported an issue related to the VMFS Heap Size (VMFS3.MaxHeapSizeMB) configuration a few days ago. Keep in mind that my customer upgraded to U1 from a previous vSphere 5.1 version meaning that the old VMFS3.MaxHeapSizeMB was retained at 80 MB &#8230; </p><p><a class="more-link block-button" href="https://magander.se/esxi-5-1-vmfs-heapsize-configuration-using-powercli/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/esxi-5-1-vmfs-heapsize-configuration-using-powercli/feed/</wfw:commentRss>
			<slash:comments>3</slash:comments>
		
		
			</item>
		<item>
		<title>Backup the virtual machine configuration file (.vmx) using PowerCLI</title>
		<link>https://magander.se/backup-the-virtual-machine-configuration-file-vmx-using-powercli/</link>
					<comments>https://magander.se/backup-the-virtual-machine-configuration-file-vmx-using-powercli/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Tue, 10 Dec 2013 06:25:44 +0000</pubDate>
				<category><![CDATA[PowerCLI]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[backup virtual machine configuration file]]></category>
		<category><![CDATA[backup vm configuration file]]></category>
		<category><![CDATA[backup vmx file]]></category>
		<category><![CDATA[PowerCLI script]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[vmx]]></category>
		<category><![CDATA[vSphere 5.5]]></category>
		<guid isPermaLink="false">http://magander.se/?p=2571</guid>

					<description><![CDATA[For those of you using a backup and restore solution based on a software backup and restore client installed in each virtual machine it is a good idea to secure the virtual machine configuration file, the .vmx file. Backing up the data from within the virtual machine is not enough for making a restore process &#8230; </p><p><a class="more-link block-button" href="https://magander.se/backup-the-virtual-machine-configuration-file-vmx-using-powercli/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/backup-the-virtual-machine-configuration-file-vmx-using-powercli/feed/</wfw:commentRss>
			<slash:comments>4</slash:comments>
		
		
			</item>
		<item>
		<title>Backup vSphere vNetwork Distributed Switches using PowerCLI</title>
		<link>https://magander.se/backup-vsphere-vnetwork-distributed-switches-using-powercli/</link>
					<comments>https://magander.se/backup-vsphere-vnetwork-distributed-switches-using-powercli/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Tue, 29 Oct 2013 20:43:47 +0000</pubDate>
				<category><![CDATA[PowerCLI]]></category>
		<category><![CDATA[Script]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[backup script]]></category>
		<category><![CDATA[script]]></category>
		<category><![CDATA[vDS]]></category>
		<category><![CDATA[VDS Backup]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[vNetwork Distributed switch]]></category>
		<category><![CDATA[vNetwork Distributed Switch backup]]></category>
		<category><![CDATA[vSphere 5.5]]></category>
		<guid isPermaLink="false">http://magander.se/?p=2247</guid>

					<description><![CDATA[A few weeks ago a customer asked me how to automate the export of the vSphere vNetwork Distributed Switches (VDS) configuration. Their existing routine included to make a manual export of the VDS configuration whenever a VDS change was implemented including adding or removing a VDS port group. In the vSphere Web Client you can &#8230; </p><p><a class="more-link block-button" href="https://magander.se/backup-vsphere-vnetwork-distributed-switches-using-powercli/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/backup-vsphere-vnetwork-distributed-switches-using-powercli/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Use PowerCLI to compare virtual machine configured and installed guest operating system</title>
		<link>https://magander.se/use-powercli-to-compare-virtual-machine-configured-and-installed-guest-operating-system/</link>
					<comments>https://magander.se/use-powercli-to-compare-virtual-machine-configured-and-installed-guest-operating-system/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Fri, 02 Aug 2013 18:15:33 +0000</pubDate>
				<category><![CDATA[PowerCLI]]></category>
		<category><![CDATA[Script]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[comare running and configured]]></category>
		<category><![CDATA[compare running and configured]]></category>
		<category><![CDATA[ESXi 5.1]]></category>
		<category><![CDATA[vCenter 5.1]]></category>
		<category><![CDATA[Virtual machine configured guest operating system]]></category>
		<category><![CDATA[virtual machine running guest operating system]]></category>
		<guid isPermaLink="false">http://magander.se/?p=1651</guid>

					<description><![CDATA[When i presented the result from a vSphere health check the other day my costumer was quite surprised that a few of his virtual machines had an installed guest operating system that didn’t match the guest operation system configured in vSphere. Several other blogs covers the importance of having a configured guest operating system in vSphere &#8230; </p><p><a class="more-link block-button" href="https://magander.se/use-powercli-to-compare-virtual-machine-configured-and-installed-guest-operating-system/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/use-powercli-to-compare-virtual-machine-configured-and-installed-guest-operating-system/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Update vSphere DRS rules using PowerCLI</title>
		<link>https://magander.se/update-vsphere-drs-rules-using-powercli/</link>
					<comments>https://magander.se/update-vsphere-drs-rules-using-powercli/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Tue, 09 Jul 2013 17:01:48 +0000</pubDate>
				<category><![CDATA[PowerCLI]]></category>
		<category><![CDATA[Script]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[get-drsrule]]></category>
		<category><![CDATA[set-drsrule]]></category>
		<category><![CDATA[vSphere DRS]]></category>
		<guid isPermaLink="false">http://magander.se/?p=1375</guid>

					<description><![CDATA[I was asked by one customer last week to create a script that adds virtual machines to a vSphere DRS group, “VM DRS Group”, based on virtual machine guest operating. My customer runs vSphere 5.1 and a licensing issue was the underlying cause of the request. My customer have two vSphere clusters running 16 ESXi &#8230; </p><p><a class="more-link block-button" href="https://magander.se/update-vsphere-drs-rules-using-powercli/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/update-vsphere-drs-rules-using-powercli/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
	</channel>
</rss>

<!--
Object Caching 15/243 objects using Disk
Page Caching using Disk: Enhanced 

Served from: magander.se @ 2026-06-22 19:19:15 by W3 Total Cache
-->