<?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>topic Re: productLocker location getting changed when applying any patches via VUM? in ESXi Discussions</title>
    <link>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2919158#M282862</link>
    <description>&lt;P&gt;Confirmed - its fixed with&amp;nbsp;&lt;A href="https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u3f-release-notes.html" target="_blank"&gt;VMware ESXi 7.0 Update 3f&amp;nbsp;Release Notes&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@AFD68144037A4FCBF57922535EA65C26/emoticons/1f60e.png" alt=":smiling_face_with_sunglasses:" title=":smiling_face_with_sunglasses:" /&gt;ty&lt;/P&gt;</description>
    <pubDate>Mon, 18 Jul 2022 14:36:04 GMT</pubDate>
    <dc:creator>UKE</dc:creator>
    <dc:date>2022-07-18T14:36:04Z</dc:date>
    <item>
      <title>productLocker location getting changed when applying any patches via VUM?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2899045#M280726</link>
      <description>&lt;P&gt;I have a fleet of hosts running ESXi 7.0 U3c - these hosts all have motherboard-based micro-SD card boot devices.&amp;nbsp; As part of the recommended mitigations to reduce I/O to this type of boot device configuration, I have from the beginning (even back when these hosts were ESXi 6.5/6.7) always configured productLocker to point to a shared storage location.&amp;nbsp; In addition to the I/O reduction to the boot device, this is a convenient way to keep all vm's tools installation current and consistent regardless of what host they are running on, because vmTools are backward and forward compatible to host version.&amp;nbsp; When a new vmtools version is released, I simply replace the files in my shared storage location (and restart mgmt agents on hosts) to compare guests' Tools version against the newly-uploaded version.&lt;/P&gt;&lt;P&gt;The desired productLocker symlink is shown from the ls -n output:&lt;/P&gt;&lt;P&gt;&lt;FONT color="#00FFFF"&gt;productLocker&lt;/FONT&gt; -&amp;gt; &lt;FONT color="#0000FF"&gt;/vmfs/volumes/5e2b25a0-281972a8-507b-5cb901ffba10/SharedLocker&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;After upgrading these hosts from 7.0U2d to 7.0 U3c (using the vendor-custom image profile) whenever I run any subsequent VUM updates to patch drivers, etc and reboot, the productLocker value reverts to:&lt;/P&gt;&lt;P&gt;&lt;FONT color="#00FFFF"&gt;productLocker&lt;/FONT&gt; -&amp;gt; /&lt;FONT color="#FF0000"&gt;SharedLocker&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;where the SharedLocker text is in red indicating it is an invalid or accessible location.&amp;nbsp; I can reset this using the API call like:&lt;/P&gt;&lt;P&gt;$esxName = '&amp;lt;hostname&amp;gt;.&amp;lt;domain&amp;gt;.net'&lt;BR /&gt;$dsName = '&amp;lt;Datastore label&amp;gt;'&lt;BR /&gt;$dsFolder = 'SharedLocker'&lt;BR /&gt;$esx = Get-VMHost -Name $esxName&lt;BR /&gt;$ds = Get-Datastore -Name $dsName&lt;BR /&gt;$oldLocation = $esx.ExtensionData.QueryProductLockerLocation()&lt;BR /&gt;$location = "/$($ds.ExtensionData.Info.Url.TrimStart('ds:/'))$dsFolder"&lt;BR /&gt;$esx.ExtensionData.UpdateProductLockerLocation($location)&lt;BR /&gt;Write-Host "Tools repository moved from"&lt;BR /&gt;Write-Host $oldLocation&lt;BR /&gt;Write-Host "to"&lt;BR /&gt;Write-Host $location&lt;/P&gt;&lt;P&gt;which resets the value to the desired location appropriately, and this setting DOES then persist across reboots from that point on...but if I then subsequently apply ANY additional driver update using VUM it resets the productLocker symlink value back to /SharedLocker on reboot.&amp;nbsp; Has anyone else seen this behavior or know the reason why this happens and how to prevent it?&amp;nbsp; Note, I do NOT see this behavior on my few hosts that have local high-endurance bootable media. and yes, I will be retrofitting all my hosts with M.2 disks, but I'd prefer to not have to deal with this in the interim every time I patch a host.&lt;/P&gt;</description>
      <pubDate>Thu, 24 Mar 2022 13:39:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2899045#M280726</guid>
      <dc:creator>PatrickDLong</dc:creator>
      <dc:date>2022-03-24T13:39:36Z</dc:date>
    </item>
    <item>
      <title>Re: productLocker location getting changed when applying any patches via VUM?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2900300#M280836</link>
      <description>&lt;P&gt;ive seen this in our environment last week after upgrading ESXi with Fujitsu ISO 7.0.3c. After rebooting all hosts showing an Host Profile Missmatch with the ProductLocker location.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Connected via ssh, the symlink /ProductLocker got removed!&lt;/P&gt;&lt;P&gt;It could be replaced my applying the Host Profile again, but strange behavior, and i think vmware esxi or vum has just another/new bug &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@D171507CB0E0B5EC481A1762311D7DA8/emoticons/1f615.png" alt=":confused_face:" title=":confused_face:" /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Mar 2022 08:01:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2900300#M280836</guid>
      <dc:creator>UKE</dc:creator>
      <dc:date>2022-03-24T08:01:02Z</dc:date>
    </item>
    <item>
      <title>Re: productLocker location getting changed when applying any patches via VUM?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2901536#M280947</link>
      <description>&lt;P&gt;We are also having the same issue.&amp;nbsp; I have had several support cases open, but the issue still persists when applying updates with a host reboot.&lt;/P&gt;</description>
      <pubDate>Thu, 31 Mar 2022 12:26:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2901536#M280947</guid>
      <dc:creator>stanm88</dc:creator>
      <dc:date>2022-03-31T12:26:05Z</dc:date>
    </item>
    <item>
      <title>Re: productLocker location getting changed when applying any patches via VUM?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2901562#M280950</link>
      <description>&lt;P&gt;I have opened a case for this as well.&amp;nbsp; Will post updates here when I have one.&amp;nbsp; I continue to see this issue when applying 7.0 U3d build&amp;nbsp;&lt;SPAN&gt;19482537&lt;/SPAN&gt; via VUM/vLCM to hosts that were previously on version 7.0 U3c&lt;/P&gt;</description>
      <pubDate>Thu, 31 Mar 2022 14:09:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2901562#M280950</guid>
      <dc:creator>PatrickDLong</dc:creator>
      <dc:date>2022-03-31T14:09:35Z</dc:date>
    </item>
    <item>
      <title>Re: productLocker location getting changed when applying any patches via VUM?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2901564#M280951</link>
      <description>&lt;P&gt;Here are the steps from the last ticket I opened:&lt;BR /&gt;1- SSH to the host&lt;BR /&gt;2- rm /productLocker -rf&lt;BR /&gt;3- ln -s &amp;lt;vmtoolpath&amp;gt; /productLocker&lt;BR /&gt;4- esxcli system settings advanced set -o /UserVars/ProductLockerLocation -s &amp;lt;vmtoolpath&amp;gt;&lt;BR /&gt;5- /sbin/auto-backup.sh (to keep settings after reboot)&lt;/P&gt;&lt;P&gt;This did work across reboots, but as soon as any updates are run, the symlink for productLocker no longer works.&lt;/P&gt;</description>
      <pubDate>Thu, 31 Mar 2022 14:12:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2901564#M280951</guid>
      <dc:creator>stanm88</dc:creator>
      <dc:date>2022-03-31T14:12:40Z</dc:date>
    </item>
    <item>
      <title>Re: productLocker location getting changed when applying any patches via VUM?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2903857#M281104</link>
      <description>&lt;P&gt;Quick case update - GSS advised me to ensure that&amp;nbsp;&lt;SPAN&gt;UserVars.ToolsRamdisk value was set to 1 and reboot&amp;nbsp; prior to application of VUM updates, however I proved that setting does NOT eliminate the productLocker location getting reset from &amp;nbsp;productLocker -&amp;gt; /vmfs/volumes/&amp;lt;volume_name&amp;gt;/SharedLocker to new value productLocker -&amp;gt; /SharedLocker on the reboot following any VUM application of updates.&amp;nbsp; Tried it with UserVars.ToolsRamdisk set to both 0 and 1, it does not make a difference in the result.&amp;nbsp; Uploaded more logs, still in progress.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Apr 2022 12:19:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2903857#M281104</guid>
      <dc:creator>PatrickDLong</dc:creator>
      <dc:date>2022-04-12T12:19:05Z</dc:date>
    </item>
    <item>
      <title>Re: productLocker location getting changed when applying any patches via VUM?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2903859#M281105</link>
      <description>&lt;P&gt;I have a session set up today with VMWare support. I will post any updates that I receive.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Apr 2022 12:36:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2903859#M281105</guid>
      <dc:creator>stanm88</dc:creator>
      <dc:date>2022-04-12T12:36:26Z</dc:date>
    </item>
    <item>
      <title>Re: productLocker location getting changed when applying any patches via VUM?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2904378#M281148</link>
      <description>&lt;P&gt;Today's update:&lt;/P&gt;&lt;P&gt;We are..."engaging the engineering team to provide a fix for this issue"&lt;/P&gt;</description>
      <pubDate>Thu, 14 Apr 2022 19:23:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2904378#M281148</guid>
      <dc:creator>PatrickDLong</dc:creator>
      <dc:date>2022-04-14T19:23:59Z</dc:date>
    </item>
    <item>
      <title>Re: productLocker location getting changed when applying any patches via VUM?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2904379#M281149</link>
      <description>&lt;P&gt;My support session ended with the tech telling me to this commands in the following order:&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;1- SSH to the host&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2- rm /productLocker -rf&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;3- esxcli system settings advanced set -o /UserVars/ProductLockerLocation -s &amp;lt;vmtoolpath&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;4- ln -s &amp;lt;vmtoolpath&amp;gt; /productLocker&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;5- /sbin/auto-backup.sh (to keep settings after reboot)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I haven't gotten a chance to verify if the value holds after updates as all out hosts are up to date.&amp;nbsp; I did see there were some updates today, but I'll have to wait until our next patch cycle to test&lt;/P&gt;</description>
      <pubDate>Thu, 14 Apr 2022 19:27:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2904379#M281149</guid>
      <dc:creator>stanm88</dc:creator>
      <dc:date>2022-04-14T19:27:51Z</dc:date>
    </item>
    <item>
      <title>Re: productLocker location getting changed when applying any patches via VUM?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2904389#M281150</link>
      <description>&lt;P&gt;thanks&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/360674"&gt;@stanm88&lt;/a&gt;&amp;nbsp;. But I think that's just the standard set of commands to delete and recreate the productLocker symlink to your target location? I've been doing the autobackup.sh for some time as well.&amp;nbsp; &amp;nbsp;While your new productLocker symlink setting will be retained across multiple reboots so long as you do not use VUM/vLCM, I believe 100% this symlink is going to get reverted to&amp;nbsp;productLocker -&amp;gt; /SharedLocker when you next apply any update via VUM (and perform the subsequent reboot.) Does not matter whether it is a single driver update that is performed or a minor revision upgrade like 7.0 U3c to 7.0 U3d, the symlink gets reverted by invoking VUM to do the work.&amp;nbsp; The same driver update or ESXi update applied manually via CLI followed by manual reboot does NOT revert the symlink.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Apr 2022 22:18:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2904389#M281150</guid>
      <dc:creator>PatrickDLong</dc:creator>
      <dc:date>2022-04-14T22:18:39Z</dc:date>
    </item>
    <item>
      <title>Re: productLocker location getting changed when applying any patches via VUM?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2904738#M281171</link>
      <description>&lt;P&gt;You were correct, tested on a host this morning and the productLocker location was again reset......&lt;/P&gt;</description>
      <pubDate>Mon, 18 Apr 2022 12:49:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2904738#M281171</guid>
      <dc:creator>stanm88</dc:creator>
      <dc:date>2022-04-18T12:49:30Z</dc:date>
    </item>
    <item>
      <title>Re: productLocker location getting changed when applying any patches via VUM?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2905393#M281224</link>
      <description>&lt;P&gt;Latest update from GSS:&amp;nbsp; "engaged our engineering team who have acknowledged this issue and are actively working on a fix. Currently in an internal testing phase"&lt;/P&gt;</description>
      <pubDate>Fri, 22 Apr 2022 02:37:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2905393#M281224</guid>
      <dc:creator>PatrickDLong</dc:creator>
      <dc:date>2022-04-22T02:37:19Z</dc:date>
    </item>
    <item>
      <title>Re: productLocker location getting changed when applying any patches via VUM?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2905950#M281271</link>
      <description>&lt;P&gt;Just upgraded our Cisco usc blades to 7.0.3d - encounter same problem.&lt;/P&gt;</description>
      <pubDate>Tue, 26 Apr 2022 07:26:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2905950#M281271</guid>
      <dc:creator>JoergenKaare</dc:creator>
      <dc:date>2022-04-26T07:26:32Z</dc:date>
    </item>
    <item>
      <title>Re: productLocker location getting changed when applying any patches via VUM?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2906265#M281292</link>
      <description>&lt;P&gt;Here is what I just got back from support:&lt;/P&gt;&lt;P&gt;Hello (name removed),&lt;BR /&gt;I hope you are doing great.&lt;BR /&gt;&lt;BR /&gt;We were able to reproduce the issue in our labs and it is a known bug.&lt;BR /&gt;This issue will be fixed in the next major release (8.0) and our back engineers are working on it.&lt;BR /&gt;&lt;BR /&gt;In the meanwhile kindly go with the workaround until the next release.&lt;BR /&gt;&lt;BR /&gt;Please let me know if you'd require any further assistance, I'd be more than happy to help out.&lt;BR /&gt;Otherwise, I'll proceed with placing this Support Request in temporary archival mode, but I'll be notified in case you decide to share any updates/inquiries with me.&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;Stay safe and have a wonderful day.&lt;BR /&gt;--&lt;BR /&gt;(name removed)&lt;BR /&gt;Technical Support Engineer&lt;BR /&gt;Global Support Services, VMware Inc.&lt;BR /&gt;Office Hours: Monday-Friday [8:00 AM - 4:00 PM EST]&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Apr 2022 14:37:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2906265#M281292</guid>
      <dc:creator>stanm88</dc:creator>
      <dc:date>2022-04-27T14:37:20Z</dc:date>
    </item>
    <item>
      <title>Re: productLocker location getting changed when applying any patches via VUM?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2907529#M281408</link>
      <description>&lt;P&gt;My response from support included:&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Engineering has confirmed that the fix will be part of next ESXi 7 u3 release, planned tentatively to be released in later part of June 2022.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;(Note: Release timeline is tentative and could vary depending on internal scenarios).&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So it may be released in a future rev of 7.0 U3 or future 8.0 - but in either case it appears to be an acknowledged bug that will have a fix.&lt;/P&gt;</description>
      <pubDate>Thu, 05 May 2022 16:35:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2907529#M281408</guid>
      <dc:creator>PatrickDLong</dc:creator>
      <dc:date>2022-05-05T16:35:23Z</dc:date>
    </item>
    <item>
      <title>Re: productLocker location getting changed when applying any patches via VUM?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2911149#M281913</link>
      <description>&lt;P&gt;Same issue here. The Problem: after installing updates, we're unable to deploy any tools update, because the Update Manager makes a wrong symlink to /ProductLocker. It links to itself.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Fix it ASAP!!!&lt;/P&gt;</description>
      <pubDate>Wed, 25 May 2022 15:46:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2911149#M281913</guid>
      <dc:creator>Zahni</dc:creator>
      <dc:date>2022-05-25T15:46:54Z</dc:date>
    </item>
    <item>
      <title>Re: productLocker location getting changed when applying any patches via VUM?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2911167#M281918</link>
      <description>&lt;P&gt;I've been running this as a powershell script for each of my servers and it seems to "fix" the location until the next update.&amp;nbsp; Hope maybe this helps someone:&lt;/P&gt;&lt;P&gt;connect-viserver (server IP) -User root -Password (root password) -wa 0&lt;BR /&gt;Get-VMHost | Get-AdvancedSetting -Name "UserVars.ProductLockerLocation" | Select-Object Entity,Value&lt;BR /&gt;Get-VMhost -Name (server IP) | %{$_.ExtensionData.UpdateProductLockerLocation_Task("location of your vmware tools")}&lt;/P&gt;</description>
      <pubDate>Wed, 25 May 2022 17:08:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2911167#M281918</guid>
      <dc:creator>stanm88</dc:creator>
      <dc:date>2022-05-25T17:08:31Z</dc:date>
    </item>
    <item>
      <title>Re: productLocker location getting changed when applying any patches via VUM?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2911518#M281947</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;same problem and what adds to it&lt;/P&gt;&lt;P&gt;Changing the product locker location via MOB doesn't work either. (UpdateProductLockerLocation_Task)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 27 May 2022 19:50:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2911518#M281947</guid>
      <dc:creator>technikus</dc:creator>
      <dc:date>2022-05-27T19:50:43Z</dc:date>
    </item>
    <item>
      <title>Re: productLocker location getting changed when applying any patches via VUM?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2918464#M282788</link>
      <description>&lt;P&gt;This fix did not make it into ESXi 7.0 U3e - or at least I should say I am still experiencing this issue when upgrading 7.0 U3d to ESXi 7.0 U3e via VUM.&amp;nbsp; Perhaps Support gave me incorrect information, or perhaps this fix is in there, but only protects ProductLocker from reverting on updates applied AFTER installing 7.0 U3e.&amp;nbsp; I'll report back as soon as I apply any post-U3e patches.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Jul 2022 23:39:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2918464#M282788</guid>
      <dc:creator>PatrickDLong</dc:creator>
      <dc:date>2022-07-12T23:39:54Z</dc:date>
    </item>
    <item>
      <title>Re: productLocker location getting changed when applying any patches via VUM?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2918537#M282798</link>
      <description>&lt;P&gt;No sooner do I post the above than I see that 7.0 U3f is now released... and it includes this fix!!!&amp;nbsp; I will be patching a few hosts today and will report results.&lt;/P&gt;&lt;P&gt;&lt;A title="https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u3f-release-notes.html" href="https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u3f-release-notes.html" target="_blank" rel="noopener noreferrer"&gt;https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u3f-release-notes.html&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;PR 2964856: Path to the /productLocker directory on a datastore truncates after patching ESXi 7.x&lt;/STRONG&gt;&lt;P&gt;After the first upgrade or update of your system to ESXi 7.x, with each consecutive update, also called a patch, you might see a truncation in the path to the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;/productLocker&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;directory on a datastore. For example, if your first patch on ESXi 7.x is from 7.0 Update 2 to 7.0 Update 3, the path to the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;/productLocker&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;directory originally is similar to&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;/vmfs/volumes/xxx/VMware-Tools/productLocker/. However, for each consecutive patch, for example from 7.0 Update 3 to 7.0 Update 3c, the path becomes similar to&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;/VMware-Tools/productLocker/.&lt;/P&gt;&lt;P&gt;This issue is resolved in this release.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Wed, 13 Jul 2022 13:11:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/productLocker-location-getting-changed-when-applying-any-patches/m-p/2918537#M282798</guid>
      <dc:creator>PatrickDLong</dc:creator>
      <dc:date>2022-07-13T13:11:23Z</dc:date>
    </item>
  </channel>
</rss>

