<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>kluken Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>kluken Tracker</description>
    <pubDate>Wed, 15 Nov 2023 08:33:00 GMT</pubDate>
    <dc:date>2023-11-15T08:33:00Z</dc:date>
    <item>
      <title>Re: VMware ESXi 5.5 local users for CIM Monitoring role</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/VMware-ESXi-5-5-local-users-for-CIM-Monitoring-role/m-p/1776434#M171459</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Anyone figure this out on 5.5? We have people that need access to Dell's OMSA interface to be able to troubleshoot things like failed HDDs and do not want them to be full root admins, since 5.5 this seems to be an impossible task.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Jun 2015 13:13:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/VMware-ESXi-5-5-local-users-for-CIM-Monitoring-role/m-p/1776434#M171459</guid>
      <dc:creator>kluken</dc:creator>
      <dc:date>2015-06-26T13:13:30Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for a large cluster</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Best-practices-for-a-large-cluster/m-p/932850#M79882</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would be interested in how one app took down the VMs and host. Do you have DRS and SIOC enabled? More details on how your hosts are configured with NICs, VLANs as well as storage such might be helpful. I have had guests that drive the host CPU to 100% and never impacted anything else as DRS and HBA tuning, etc all prevented that from happening. In the one cluster that we do mix DEV and PROD on we set the resources shares to DEV boxes at low, all other to normal and business critical VMs to HIGH for CPU and RAM. I am not a fan of resource pools as they create as many problems as they fix. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Nov 2014 12:17:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Best-practices-for-a-large-cluster/m-p/932850#M79882</guid>
      <dc:creator>kluken</dc:creator>
      <dc:date>2014-11-20T12:17:26Z</dc:date>
    </item>
    <item>
      <title>Re: vmWare ROBO bait and switch smells like vRAM debacle again</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vmWare-ROBO-bait-and-switch-smells-like-vRAM-debacle-again/m-p/2693154#M262749</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Very surprised that no one has reacted to this. I guess not many people using ROBO kits. Our fault for being early adopters I guess as vmware tweaks the licenses every 8-12 months. Huge disappointment for us as it makes our ROBO site costs go up almost 4X. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Nov 2014 12:12:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vmWare-ROBO-bait-and-switch-smells-like-vRAM-debacle-again/m-p/2693154#M262749</guid>
      <dc:creator>kluken</dc:creator>
      <dc:date>2014-11-20T12:12:07Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere Essentials Kit Questions</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-Essentials-Kit-Questions/m-p/2696215#M263348</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Keep in mind that if you grow there are limitations for the Essentials versions. Essentials can NOT be manged by a standard vcenter, it has to use a vcenter essentials and vcenter essentials can not mange more than 3 hosts, so if you so yourself growing past 3 hosts you may need to reconsider. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Oct 2014 12:17:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-Essentials-Kit-Questions/m-p/2696215#M263348</guid>
      <dc:creator>kluken</dc:creator>
      <dc:date>2014-10-14T12:17:43Z</dc:date>
    </item>
    <item>
      <title>Re: vmWare ROBO bait and switch smells like vRAM debacle again</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vmWare-ROBO-bait-and-switch-smells-like-vRAM-debacle-again/m-p/2693153#M262748</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I guess not many folks impacted or concerned with this?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Oct 2014 12:14:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vmWare-ROBO-bait-and-switch-smells-like-vRAM-debacle-again/m-p/2693153#M262748</guid>
      <dc:creator>kluken</dc:creator>
      <dc:date>2014-10-14T12:14:33Z</dc:date>
    </item>
    <item>
      <title>Re: How to use a single USB port on 5 machines at the same time?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/How-to-use-a-single-USB-port-on-5-machines-at-the-same-time/m-p/1795530#M174869</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You need to look at Digi's USB Anywhere devices that allow for network attached USB dongles. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 Oct 2014 11:44:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/How-to-use-a-single-USB-port-on-5-machines-at-the-same-time/m-p/1795530#M174869</guid>
      <dc:creator>kluken</dc:creator>
      <dc:date>2014-10-10T11:44:31Z</dc:date>
    </item>
    <item>
      <title>Re: vmWare ROBO bait and switch smells like vRAM debacle again</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vmWare-ROBO-bait-and-switch-smells-like-vRAM-debacle-again/m-p/2693152#M262747</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Curious how many people are actually leveraging the ROBO licensees and then does this change have a positive or negative impact on you?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 Oct 2014 11:42:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vmWare-ROBO-bait-and-switch-smells-like-vRAM-debacle-again/m-p/2693152#M262747</guid>
      <dc:creator>kluken</dc:creator>
      <dc:date>2014-10-10T11:42:36Z</dc:date>
    </item>
    <item>
      <title>Re: vmWare ROBO bait and switch smells like vRAM debacle again</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vmWare-ROBO-bait-and-switch-smells-like-vRAM-debacle-again/m-p/2693151#M262746</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also one new limitation is no single location can have more than 25 VMs. We were an early adopter of ROBO and vSphere replication and both have been a huge failure for us. Every version of vSphere has substantial changes to replication that also has had negative impacts on us. We use vSphere replication for a few dozen remote locations where SAN based replication would be cost prohibitive. I will give it to MS, they are working hard to make Hyper-V a good solution for ROBO locations and if vmware does not take its head out of its butt they will never win in the ROBO scenarios&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Oct 2014 15:24:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vmWare-ROBO-bait-and-switch-smells-like-vRAM-debacle-again/m-p/2693151#M262746</guid>
      <dc:creator>kluken</dc:creator>
      <dc:date>2014-10-08T15:24:27Z</dc:date>
    </item>
    <item>
      <title>vmWare ROBO bait and switch smells like vRAM debacle again</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vmWare-ROBO-bait-and-switch-smells-like-vRAM-debacle-again/m-p/2693150#M262745</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well looks like vmware is up to is old tricks again. Desperate to make more revenue they baited people in with the ROBO license less than 2 years ago and are now on their newest license model that basically comes across as a bait and switch. When they released ROBO as their response to Hyper-V it was priced very competitively in single CPU SKUs. Then less than a year later they changed the license model to require 10 packs be purchased and now less than a year after that they have switched to a per VM model. WTF!! They bait you in with attractive license model then every few months switch its so it becomes more expensive. On top of that they make these changes and give you less than a&amp;nbsp; month to accommodate them as the old SKUs disappear and you have no option. This time the new license requires that you be at vSphere/Vcenter 5.5 U2 since the new keys do not work in anything older. Under the old model it used to cost us about $30 per VM to deploy 4-6 VMs at a location on a&amp;nbsp; dual socket box, now under the new model it will cost us $120 per VM. Also we are constrained by rigid change control so having to implement 5.5 U2 in order to support new locations is not feasible in a short period and we were waiting for U3 since it is going to have fixes that apply to us. So now I can wait and not deploy any more VMs to my remote locations until U3 is out or I can rush in vcenter 5.5 U2 and update 70 distributed hosts around the country. This reminds me of the vRAM license change that they quickly recalled, and I hope enough of you speak up to your sales teams and voice your concerns to make them reconsider this 4X price increase. vmware wants to know why Hyper-V is&amp;nbsp; in small ROBO locations this should tell them why, I am not spending 4x to do the same thing I was doing the last 18 months just because vmware decided to get greedy. I am regretting the decision to migrate off Hyper-V for our ROBO locations and will stop migrating the remaining 112 sites and instead move them to Hyper-V 2012 R2. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Oct 2014 14:49:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vmWare-ROBO-bait-and-switch-smells-like-vRAM-debacle-again/m-p/2693150#M262745</guid>
      <dc:creator>kluken</dc:creator>
      <dc:date>2014-10-08T14:49:40Z</dc:date>
    </item>
    <item>
      <title>Re: Setting LVM.EnableResignature issue with PowerCLI in vpshere 5.1 and Powercli 5.1 U2</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Setting-LVM-EnableResignature-issue-with-PowerCLI-in-vpshere-5-1/m-p/2698743#M93231</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yup, I found that and pulled in pieces into my script so mine works now, thanks! Not sure why the striaght forwaed Set-VMHostAdvancedConfiguration&amp;nbsp; did not work, but at least I have something.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;foreach ($vh in $vmhosts) {&lt;/P&gt;&lt;P&gt;if ((Get-VMHostAdvancedConfiguration -vmhost $vh -Name LVM.EnableResignature).Values -ne 0){&lt;BR /&gt;&amp;nbsp; Write-Host Resignature value is enabled for host $vh&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Write-Host Resetting resignature value to disabled&lt;BR /&gt;&amp;nbsp; &lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; $Option = New-Object Vmware.Vim.Optionvalue -Property @{&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Key = "LVM.EnableResignature"&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Value = $Value&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; }&lt;BR /&gt; &lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; $OptionArray = $Option&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; $ESX = Get-View $vh.ID&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; $OptMgr = Get-View $ESX.ConfigManager.AdvancedOption&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; $OptMgr.UpdateOptions($OptionArray)&lt;BR /&gt;&amp;nbsp; }&lt;BR /&gt;}&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Sep 2013 18:56:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Setting-LVM-EnableResignature-issue-with-PowerCLI-in-vpshere-5-1/m-p/2698743#M93231</guid>
      <dc:creator>kluken</dc:creator>
      <dc:date>2013-09-11T18:56:41Z</dc:date>
    </item>
    <item>
      <title>Re: Setting LVM.EnableResignature issue with PowerCLI in vpshere 5.1 and Powercli 5.1 U2</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Setting-LVM-EnableResignature-issue-with-PowerCLI-in-vpshere-5-1/m-p/2698741#M93229</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;One thing I notice is when I just dump all the advancedOptions I do not even see LVM.EnableResignature. IIt works via esxcfg, so I wonder why it is not working via PowerCLI&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Sep 2013 16:53:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Setting-LVM-EnableResignature-issue-with-PowerCLI-in-vpshere-5-1/m-p/2698741#M93229</guid>
      <dc:creator>kluken</dc:creator>
      <dc:date>2013-09-11T16:53:12Z</dc:date>
    </item>
    <item>
      <title>Setting LVM.EnableResignature issue with PowerCLI in vpshere 5.1 and Powercli 5.1 U2</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Setting-LVM-EnableResignature-issue-with-PowerCLI-in-vpshere-5-1/m-p/2698740#M93228</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We use SRM and like to make sure that when done with test that the LVM.EnableResignature is set back to 0 since we do relocate hosts often. I have tried 2 different ways to do this and both fail with "A specified parameter was not correct" All the samples I see online are for esx 4.x and below, I have not seen anyone verify this in 5.x.&amp;nbsp; We are 5.1U1 and latest powercli.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help would be greatly appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Method 1:&lt;/P&gt;&lt;P&gt;$vh contains the name of the host to be reset:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if ((Get-VMHostAdvancedConfiguration -vmhost $vh -Name LVM.EnableResignature).Values -ne 0){&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Set-VMHostAdvancedConfiguration -vmhost $vh -Name LVM.EnableResignature -Value 0 -Confirm:$false&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Method 2:&lt;/P&gt;&lt;P&gt;Borrows code from functions I have seen online:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if ((Get-VMHostAdvancedConfiguration -vmhost $vh -Name LVM.EnableResignature).Values -ne 0){&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;$esx = Get-View (Get-VMHost $vh).ID&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;$optmgrMoRef = $esx.configManager.advancedOption&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;$optmgr = Get-View $optmgrMoRef&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;$optarray = $optmgr.QueryOptions("LVM.Enableresignature")&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;$optarray[0].Value = 0&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;$optmgr.UpdateOptions($optarray)&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Sep 2013 16:05:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Setting-LVM-EnableResignature-issue-with-PowerCLI-in-vpshere-5-1/m-p/2698740#M93228</guid>
      <dc:creator>kluken</dc:creator>
      <dc:date>2013-09-11T16:05:41Z</dc:date>
    </item>
    <item>
      <title>Re: SRM and LVM.enableResignature setting</title>
      <link>https://communities.vmware.com/t5/Site-Recovery-Manager-Documents/SRM-and-LVM-enableResignature-setting/tac-p/2775453#M2</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;SRM will set LVM.EnableResignature to 1 for you, the problem is that is not a good setting to leave in place. If you relocate hosts between clusters or have hosts with that setting attaching to storage that is not originally part of that cluster and that setting is left to 1 then a new host coming on line with that setting may resignature VMFS volumes and you will have to manually re-register VMs&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Sep 2013 16:01:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Site-Recovery-Manager-Documents/SRM-and-LVM-enableResignature-setting/tac-p/2775453#M2</guid>
      <dc:creator>kluken</dc:creator>
      <dc:date>2013-09-11T16:01:06Z</dc:date>
    </item>
    <item>
      <title>Quick script to enable/disable copy/paste via vm console</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Quick-script-to-enable-disable-copy-paste-via-vm-console/m-p/902991#M25909</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is a quick script that will prompt for the vcenter name then the vmname and give you the option to enable or disable the copy/pasta function via the vm console. You need to restart the VM for the changes to take effect, but this is better than manually going into advanced config to make the changes.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Jul 2013 12:17:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Quick-script-to-enable-disable-copy-paste-via-vm-console/m-p/902991#M25909</guid>
      <dc:creator>kluken</dc:creator>
      <dc:date>2013-07-10T12:17:46Z</dc:date>
    </item>
    <item>
      <title>Here is a Powercli script to set VM bootdelay option</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Here-is-a-Powercli-script-to-set-VM-bootdelay-option/m-p/2188135#M72092</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We had over 700 Vms that we wanted to set a 5 second boot delay option to give people the option to enter the VM bios or BOOT Order FN keys before booting the guest OS. So I rushed together this script. It will look at powered on VMs only and you can point it to a cluster or it defaults to all VMs in vcenter and will set the option. You need PowerCLI&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Jul 2013 14:44:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Here-is-a-Powercli-script-to-set-VM-bootdelay-option/m-p/2188135#M72092</guid>
      <dc:creator>kluken</dc:creator>
      <dc:date>2013-07-08T14:44:19Z</dc:date>
    </item>
    <item>
      <title>powercli script to list the enable.DiskUUID setting</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/powercli-script-to-list-the-enable-DiskUUID-setting/m-p/1762290#M55917</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Decided I wanted an easy way to list out the status of the enable.DiskUUID since there are known issues with Windows 2008 VMs that can have problems doing application quiescing. This is crude, but gets the job done. You will give the script a vcenter name, and cluster and it will sort the VMs and list them out as whether the values is enabled or disabled and then put the output to a file. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Jun 2013 13:58:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/powercli-script-to-list-the-enable-DiskUUID-setting/m-p/1762290#M55917</guid>
      <dc:creator>kluken</dc:creator>
      <dc:date>2013-06-27T13:58:55Z</dc:date>
    </item>
    <item>
      <title>Re: Automate scheduling hardware upgrade on 5.1U1</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Automate-scheduling-hardware-upgrade-on-5-1U1/m-p/2716038#M94270</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Make sure you have latest PowerCLI 5.1 Release 2&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jun 2013 21:48:13 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Automate-scheduling-hardware-upgrade-on-5-1U1/m-p/2716038#M94270</guid>
      <dc:creator>kluken</dc:creator>
      <dc:date>2013-06-07T21:48:13Z</dc:date>
    </item>
    <item>
      <title>Re: Harware Compatability upgrade</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Harware-Compatability-upgrade/m-p/1820272#M59769</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes make sure you have the latest PowerCLI. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jun 2013 21:45:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Harware-Compatability-upgrade/m-p/1820272#M59769</guid>
      <dc:creator>kluken</dc:creator>
      <dc:date>2013-06-07T21:45:41Z</dc:date>
    </item>
    <item>
      <title>Re: Harware Compatability upgrade</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Harware-Compatability-upgrade/m-p/1820269#M59766</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Cool, I just posted a thread&amp;nbsp; &lt;A _jive_internal="true" href="https://communities.vmware.com/message/2249221#2249221"&gt;http://communities.vmware.com/message/2249221#2249221&lt;/A&gt; where I wrapped this in a&amp;nbsp; quick ps script that you can point to vcenter and optional cluster and it will set it for all powered on vms. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Jun 2013 18:37:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Harware-Compatability-upgrade/m-p/1820269#M59766</guid>
      <dc:creator>kluken</dc:creator>
      <dc:date>2013-06-06T18:37:28Z</dc:date>
    </item>
    <item>
      <title>Automate scheduling hardware upgrade on 5.1U1</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Automate-scheduling-hardware-upgrade-on-5-1U1/m-p/2716036#M94268</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I saw that someone posted how to set the properties on a vm to schedule the the hardware upgrade when there has been a clean os shutdown. I am a novice at powershell, but threw this script together that will automate this for you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It assumes your windows log on account has permission to vcenter and you have powercli installed. It will prompt you for the vcenter name then for the cluster name, if you leave out cluster it will do all powered on VMs that are not at vmx-09 and schedule them for update and next clean reboot. It will display on the screen which VMs it is updating. Hope this helps make your busy day a little easier. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Jun 2013 18:32:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Automate-scheduling-hardware-upgrade-on-5-1U1/m-p/2716036#M94268</guid>
      <dc:creator>kluken</dc:creator>
      <dc:date>2013-06-06T18:32:36Z</dc:date>
    </item>
  </channel>
</rss>

