<?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>aravindgopalakr Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>aravindgopalakr Tracker</description>
    <pubDate>Wed, 15 Nov 2023 14:49:46 GMT</pubDate>
    <dc:date>2023-11-15T14:49:46Z</dc:date>
    <item>
      <title>Log browser unavailability in vSphere 6.7</title>
      <link>https://communities.vmware.com/t5/Legacy-User-Blogs/Log-browser-unavailability-in-vSphere-6-7/ta-p/2765800</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-family: 'book antiqua', palatino; font-size: 10pt;"&gt;&lt;SPAN style="color: black;"&gt;LogBrowser is disabled 6.5 onwards and is not longer available in Flex/H5 client. &lt;/SPAN&gt;This was made as part of the last set of improvements of the Flex Client prior to 6.5 GA. Log browser was removed and is not available afterwards.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; font-family: 'book antiqua', palatino;"&gt;Feature is not part of vSphere Client (HTML5).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; font-family: 'book antiqua', palatino;"&gt;Official documentation to be updated very soon on VMware websites. Tentative dates for the documents and articles to be updated is post the release of vSphere 6.7 U1.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; font-family: 'book antiqua', palatino;"&gt;Hence, this post concludes that though the feature might work on a few builds of vSphere 6.5 - they are not officially supported.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Oct 2018 05:10:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Legacy-User-Blogs/Log-browser-unavailability-in-vSphere-6-7/ta-p/2765800</guid>
      <dc:creator>aravindgopalakr</dc:creator>
      <dc:date>2018-10-12T05:10:53Z</dc:date>
    </item>
    <item>
      <title>A local user in vSphere web client will not be able to change/update his password</title>
      <link>https://communities.vmware.com/t5/ESXi-Documents/A-local-user-in-vSphere-web-client-will-not-be-able-to-change/ta-p/2790679</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;User experiences an error, 'failed to change password' when trying to change his password.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Below was the entry that was showing up in var/log/hostd.log: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2018-07-05T22:39:17.954Z info hostd[FA81B70] [Originator@6876 sub=Solo.Vmomi opID=db0a2561 user=test] Throw vim.fault.NoPermission&lt;/P&gt;&lt;P&gt;2018-07-05T22:39:17.954Z info hostd[FA81B70] [Originator@6876 sub=Solo.Vmomi opID=db0a2561 user=test] Result:&lt;/P&gt;&lt;P&gt;--&amp;gt; (vim.fault.NoPermission) {&lt;/P&gt;&lt;P&gt;--&amp;gt; faultCause = (vmodl.MethodFault) null,&lt;/P&gt;&lt;P&gt;--&amp;gt; faultMessage = &amp;lt;unset&amp;gt;,&lt;/P&gt;&lt;P&gt;--&amp;gt; object = 'vim.Folder:ha-folder-root',&lt;/P&gt;&lt;P&gt;--&amp;gt; privilegeId = "Host.Local.ManageUserGroups"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As per the above snippet, we proceeded into the custom role that we had created and assigned the privilege --&amp;gt; Host&amp;gt;Local&amp;gt;ManageUserGroups. We then proceeded to update the password for the user and it worked perfectly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This issue occurs, if the user who is attempting to change his password is not assigned with the required privilege.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Below are the steps to add the missing privilege to the user: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Login to the ESXi host web client with root credentials.&lt;/P&gt;&lt;P&gt;2. Select Manage&lt;/P&gt;&lt;P&gt;3. Click on Security &amp;amp; users tab and in the left page &amp;gt; Select Roles&lt;/P&gt;&lt;P&gt;4. Find and select the role that is assigned to the non-administrative user in question, and click on Edit role&lt;/P&gt;&lt;P&gt;5. From the list, scroll down and click on Host &amp;gt; then click on Local &amp;gt; then select or check mark, ManageUserGroups privilege and click on Save&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The non-administrative user who has this role assigned should be able to update or change his password himself.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note: Resetting passwords privilege for any user accounts still remain with the administrator/root user account.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Sep 2018 19:14:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Documents/A-local-user-in-vSphere-web-client-will-not-be-able-to-change/ta-p/2790679</guid>
      <dc:creator>aravindgopalakr</dc:creator>
      <dc:date>2018-09-24T19:14:15Z</dc:date>
    </item>
    <item>
      <title>Resetting VMware Update Manager Database on a vCenter Server Appliance 6.7</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Documents/Resetting-VMware-Update-Manager-Database-on-a-vCenter-Server/ta-p/2780439</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Purpose: The following article outlines how to reset the VMware Update Manager Database and Patch Store on a vCenter Server Appliance 6.7.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Starting with vCenter Server Appliance 6.5, the VMware Update Manager is embedded into the vCenter Server Appliance 6.5 and 6.7.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The issue is caused by a proxy.dat file that is used for encrypting and decrypting the proxy password in the VUM database. During the 6.5 to 6.7 upgrade, the file gets replaced and the VUM service can't decrypt the proxy settings in the database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Resolution: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cautions: The following is a destructive task. Ensure you have working backups and/or snapshots of the vCenter Server Appliance 6.5 before proceeding.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Connect to vCenter Server Appliance 6.7 via SSH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Run the shell command to switch to the BASH Shell:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;shell&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. Stop the VMware Update Manager Service:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service-control --stop vmware-updatemgr &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4. Run the following command to reset the VMware Update Manager Database:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/usr/lib/vmware-updatemgr/bin/updatemgr-utility.py reset-db&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;5. Run the following Command to delete the contents of the VMware Update Manager Patch Store:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rm -rf /storage/updatemgr/patch-store/*&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;6. Start the VMware Update Manager Service:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service-control --start vmware-updatemgr&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note: You may need to log out and log back into any instances of the vSphere Web Client.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Sep 2018 18:15:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Documents/Resetting-VMware-Update-Manager-Database-on-a-vCenter-Server/ta-p/2780439</guid>
      <dc:creator>aravindgopalakr</dc:creator>
      <dc:date>2018-09-24T18:15:43Z</dc:date>
    </item>
    <item>
      <title>Re: Windows vCenter 6.7 to vcsa 6.7 migration</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Windows-vCenter-6-7-to-vcsa-6-7-migration/m-p/479914#M5999</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;And to add to it - same version migration is not supported in any versions. So, if you wish to migrate - you may have to wait for the next version to release.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Sep 2018 18:01:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Windows-vCenter-6-7-to-vcsa-6-7-migration/m-p/479914#M5999</guid>
      <dc:creator>aravindgopalakr</dc:creator>
      <dc:date>2018-09-19T18:01:43Z</dc:date>
    </item>
    <item>
      <title>Re: Windows vCenter 6.7 to vcsa 6.7 migration</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Windows-vCenter-6-7-to-vcsa-6-7-migration/m-p/479913#M5998</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is currently not supported. Might be available soon with 6.7 U1 round the corner. The best option at this point (if you are not willing to wait), deploy a fresh vCenter Appliance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have dvswitches, you could simply export and import them to the new vCenter. You might lose the other configurations like DRS resource pools if configured. If you have none, then you are good to deploy a fresh Appliance and join the ESXi hosts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You would be losing the following if configured already on your existing vCenter: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- DVSwitches&lt;/P&gt;&lt;P&gt;- Roles / Permissions&lt;/P&gt;&lt;P&gt;- VM/Templates Folders and Permission&lt;/P&gt;&lt;P&gt;- Alarms&lt;/P&gt;&lt;P&gt;- vCenter Configuration&lt;/P&gt;&lt;P&gt;- DRS Rules / Groups&lt;/P&gt;&lt;P&gt;- vCenter Customize Attributes&lt;/P&gt;&lt;P&gt;- Resource Pools&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please mark this as answered or helpful if you find this info helpful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Sep 2018 01:02:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Windows-vCenter-6-7-to-vcsa-6-7-migration/m-p/479913#M5998</guid>
      <dc:creator>aravindgopalakr</dc:creator>
      <dc:date>2018-09-19T01:02:56Z</dc:date>
    </item>
  </channel>
</rss>

