<?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>Tinto1970 Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>Tinto1970 Tracker</description>
    <pubDate>Sat, 11 Nov 2023 23:58:50 GMT</pubDate>
    <dc:date>2023-11-11T23:58:50Z</dc:date>
    <item>
      <title>Re: ESXi 7.03 SU DL380 GEN9</title>
      <link>https://communities.vmware.com/t5/Italian-Discussions/ESXi-7-03-SU-DL380-GEN9/m-p/2986526#M13127</link>
      <description>&lt;P&gt;puoi probabilmente usare i vari tool che fanno immagini ma come ti dicevano sopra, la cosa migliore è salvare la configurazione e tenersi da parte una ISO di installazione di ESXi con la stessa bulid che hai attualmente.&lt;BR /&gt;&lt;BR /&gt;In caso di disastro ripristini il disco fisico, installi ESXI da zero (ci vuole poco!) e poi gli carichi la configurazione salvata. Fai mooolto prima e sicuro&lt;/P&gt;</description>
      <pubDate>Wed, 13 Sep 2023 12:21:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Italian-Discussions/ESXi-7-03-SU-DL380-GEN9/m-p/2986526#M13127</guid>
      <dc:creator>Tinto1970</dc:creator>
      <dc:date>2023-09-13T12:21:01Z</dc:date>
    </item>
    <item>
      <title>Re: Weird disk latency issue on new R760 with onboard storage. Please help.</title>
      <link>https://communities.vmware.com/t5/Storage-Performance/Weird-disk-latency-issue-on-new-R760-with-onboard-storage-Please/m-p/2976967#M5508</link>
      <description>&lt;P&gt;hi, it sounds really strange and I don't think shere is something wrong with the hypervisor.&lt;BR /&gt;&lt;BR /&gt;If the machine is not yet in production, you could try maybe with a linux live cd and test the virtual volume performance (i guess you'll need to destroy the current datastore and forma in a linux usable filesystem)&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jul 2023 15:10:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Storage-Performance/Weird-disk-latency-issue-on-new-R760-with-onboard-storage-Please/m-p/2976967#M5508</guid>
      <dc:creator>Tinto1970</dc:creator>
      <dc:date>2023-07-12T15:10:39Z</dc:date>
    </item>
    <item>
      <title>Re: New added disk not visible in my Linux VM</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/New-added-disk-not-visible-in-my-Linux-VM/m-p/2976921#M182027</link>
      <description>&lt;P&gt;after you add an hard disk you need to force the operating system to rescan the SCSI Bus. The easiest way is to reboot, but you can find many tricks on the internet to do it without rebooting&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.debuntu.org/how-to-rescan-a-scsi-bus-without-rebooting/" target="_self"&gt;https://www.debuntu.org/how-to-rescan-a-scsi-bus-without-rebooting/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jul 2023 10:25:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/New-added-disk-not-visible-in-my-Linux-VM/m-p/2976921#M182027</guid>
      <dc:creator>Tinto1970</dc:creator>
      <dc:date>2023-07-12T10:25:25Z</dc:date>
    </item>
    <item>
      <title>Re: Interesting observation with two enivornments using the same SAN</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Interesting-observation-with-two-enivornments-using-the-same-SAN/m-p/2976896#M94595</link>
      <description>&lt;P&gt;first of all, you no longer need shared storage to perform VM live migrations.&lt;/P&gt;&lt;P&gt;Finally, the only "one" who can automatically&amp;nbsp;&lt;U&gt;restart&lt;/U&gt; a VM on another host is the &lt;EM&gt;vSphere HA&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;A standalone host, even if it can access the VM directories and files, will never register (take ownership) of VMs until some one clicks on the .vmx file and issue the register command.&lt;/P&gt;&lt;P&gt;And more: if the host is under the same vCenter of the "legal" owner of the VM, the register operation will fail.&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jul 2023 07:02:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Interesting-observation-with-two-enivornments-using-the-same-SAN/m-p/2976896#M94595</guid>
      <dc:creator>Tinto1970</dc:creator>
      <dc:date>2023-07-12T07:02:12Z</dc:date>
    </item>
    <item>
      <title>Re: caccia allo snapshot (VM needs consolidation)</title>
      <link>https://communities.vmware.com/t5/Italian-Discussions/caccia-allo-snapshot-VM-needs-consolidation/m-p/2976895#M13118</link>
      <description>&lt;P&gt;ciao, in quel caso si trattava di NetWorker, ma penso possa capitare un po' con tutti i software. Capitava anche con Veeam, poi hanno introdotto questa funzione: &lt;A href="https://helpcenter.veeam.com/docs/backup/vsphere/snapshot_hunter.html?ver=120" target="_blank" rel="noopener"&gt;Snapshot Hunter&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In generale è importante avere un qualcosa che ti avvisi in caso di snapshot dimenticati (e di datastore che si riempiono). Molto spesso, anche in contesti grandi, ho visto trascurare questo controllo, spesso con danni, perdite di tempo e cene rovinate.&lt;/P&gt;&lt;P&gt;Sono di parte perché ci lavoro come partner ma... &lt;A href="https://www.veeam.com/it/virtual-server-management-one-free.html" target="_blank" rel="noopener"&gt;Veeam One&lt;/A&gt;&lt;/P&gt;&lt;P&gt;anche in versione community e gratuita, svolge perfettamente questo compito&amp;nbsp;&lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@9A8352F02F49809A161B25D7C247110D/emoticons/1f609.png" alt=":winking_face:" title=":winking_face:" /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jul 2023 06:55:13 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Italian-Discussions/caccia-allo-snapshot-VM-needs-consolidation/m-p/2976895#M13118</guid>
      <dc:creator>Tinto1970</dc:creator>
      <dc:date>2023-07-12T06:55:13Z</dc:date>
    </item>
    <item>
      <title>Re: License downgrade 8.0 -&gt; 6.0</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/License-downgrade-8-0-gt-6-0/m-p/2976742#M34769</link>
      <description>&lt;P&gt;where did you find this "incompatibility"?&lt;/P&gt;&lt;P&gt;if you have found it in the VMware Compatibility Matrix&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Tinto1970_0-1689081261143.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/102534i7ED38F87F4F90C02/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="Tinto1970_0-1689081261143.png" alt="Tinto1970_0-1689081261143.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;it does not mean that ESXi7 won't install&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 13:14:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/License-downgrade-8-0-gt-6-0/m-p/2976742#M34769</guid>
      <dc:creator>Tinto1970</dc:creator>
      <dc:date>2023-07-11T13:14:43Z</dc:date>
    </item>
    <item>
      <title>Re: License downgrade 8.0 -&gt; 6.0</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/License-downgrade-8-0-gt-6-0/m-p/2976734#M34767</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/65293"&gt;@gbartolini&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;Tinto, you miss the point that ESXi7 will not install on a R610 server&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;are you sure about that or you&lt;EM&gt; suppose&lt;/EM&gt; it?&lt;/P&gt;&lt;P&gt;Finally: the answer to your question is &lt;STRONG&gt;NO&lt;/STRONG&gt;: vsphere 6 is "out of sale" since 2020.&lt;/P&gt;&lt;P&gt;Sorry if i was trying to suggest a workaround, please forgive me&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 12:55:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/License-downgrade-8-0-gt-6-0/m-p/2976734#M34767</guid>
      <dc:creator>Tinto1970</dc:creator>
      <dc:date>2023-07-11T12:55:12Z</dc:date>
    </item>
    <item>
      <title>Re: License downgrade 8.0 -&gt; 6.0</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/License-downgrade-8-0-gt-6-0/m-p/2976724#M34763</link>
      <description>&lt;P&gt;&lt;A href="https://lifecycle.vmware.com/#/" target="_blank"&gt;https://lifecycle.vmware.com/#/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;end of availability of version 6 is gone (3 years ago)&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Tinto1970_0-1689075396183.png" style="width: 800px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/102532i45F842246ED81438/image-dimensions/800x62/is-moderation-mode/true?v=v2" width="800" height="62" role="button" title="Tinto1970_0-1689075396183.png" alt="Tinto1970_0-1689075396183.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;once again: it's not important if "&lt;SPAN&gt;PowerEdge R610 certified by Dell up to ESXi 6.0 at maximum": you/your customer will be ANYWAY out of support.&lt;BR /&gt;I see no higher risks in using an out of support ESXi7 instead of an out of support ESXI6. But lower risks instead...&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 12:28:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/License-downgrade-8-0-gt-6-0/m-p/2976724#M34763</guid>
      <dc:creator>Tinto1970</dc:creator>
      <dc:date>2023-07-11T12:28:47Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade path</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrade-path/m-p/2976704#M34762</link>
      <description>&lt;P&gt;hello, in short: upgrade from u3g to u3n directly. It's a really minor update.&lt;/P&gt;&lt;P&gt;In general, take a look at this &lt;A title="Upgrade Paths" href="https://kb.vmware.com/s/article/70785" target="_blank" rel="noopener"&gt;Upgrade Paths&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 10:28:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrade-path/m-p/2976704#M34762</guid>
      <dc:creator>Tinto1970</dc:creator>
      <dc:date>2023-07-11T10:28:09Z</dc:date>
    </item>
    <item>
      <title>Re: Thick provision disk type is missing</title>
      <link>https://communities.vmware.com/t5/vSphere-Storage-Discussions/Thick-provision-disk-type-is-missing/m-p/2976703#M24782</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/5632982"&gt;@mjmderecho&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/5622196"&gt;@AnaghB&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;&lt;BR /&gt;Thank you for the info, upon checking, the hardware acceleration is not supported. Is there a workaround to enable the thick provision?&lt;BR /&gt;&lt;BR /&gt;Btw, I'm using IBM Cloud Storage for my VMware datastore.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="mjmderecho_0-1689035524170.png" style="width: 999px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/102527i53888811F85A2BA4/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="mjmderecho_0-1689035524170.png" alt="mjmderecho_0-1689035524170.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;I think no. But you can use the thin disk, this will not affect performance. Just monitor your storage to put under control or avoid overprovisioning&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 10:25:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Storage-Discussions/Thick-provision-disk-type-is-missing/m-p/2976703#M24782</guid>
      <dc:creator>Tinto1970</dc:creator>
      <dc:date>2023-07-11T10:25:05Z</dc:date>
    </item>
    <item>
      <title>Re: HDD Capacity Calculator</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/HDD-Capacity-Calculator/m-p/2976701#M288958</link>
      <description>&lt;P&gt;If I understand well, you have two 1.9TB drives in RAID1 configuration, and the datastore free space is "only" 1.6TB?&lt;BR /&gt;&lt;BR /&gt;If so, I think it's normal because the 1.9 size is "unformatted": the really usable size of the HDD is less than the "raw" amount which is written on the HDD's box&amp;nbsp;&lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@9A8352F02F49809A161B25D7C247110D/emoticons/1f609.png" alt=":winking_face:" title=":winking_face:" /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 10:15:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/HDD-Capacity-Calculator/m-p/2976701#M288958</guid>
      <dc:creator>Tinto1970</dc:creator>
      <dc:date>2023-07-11T10:15:06Z</dc:date>
    </item>
    <item>
      <title>Re: License downgrade 8.0 -&gt; 6.0</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/License-downgrade-8-0-gt-6-0/m-p/2976699#M34756</link>
      <description>&lt;P&gt;but are you sure that ESXi 7 cannot install on the hardware? Did you try?&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 10:10:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/License-downgrade-8-0-gt-6-0/m-p/2976699#M34756</guid>
      <dc:creator>Tinto1970</dc:creator>
      <dc:date>2023-07-11T10:10:16Z</dc:date>
    </item>
    <item>
      <title>Re: Maintenance mode</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Maintenance-mode/m-p/2976691#M288957</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/60446"&gt;@tractng&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am so reluctant to power any hardware especially the SAN down when they have been running many years.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;a good advice is to be reluctant to let the SAN run for many years without an update&amp;nbsp;&lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@9A8352F02F49809A161B25D7C247110D/emoticons/1f609.png" alt=":winking_face:" title=":winking_face:" /&gt;&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 09:33:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Maintenance-mode/m-p/2976691#M288957</guid>
      <dc:creator>Tinto1970</dc:creator>
      <dc:date>2023-07-11T09:33:12Z</dc:date>
    </item>
    <item>
      <title>Re: Sharing datastore cluster between  ESXi 7.0.3  Clusters for VM Migration</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Sharing-datastore-cluster-between-ESXi-7-0-3-Clusters-for-VM/m-p/2976688#M45586</link>
      <description>&lt;P&gt;yes it's supported. But keep in mind that live VM migration is supported also without shared storage.&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-vcenter-esxi-management/GUID-561681D9-6511-44DF-B169-F20E6CA94944.html" target="_blank"&gt;https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-vcenter-esxi-management/GUID-561681D9-6511-44DF-B169-F20E6CA94944.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 09:27:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Sharing-datastore-cluster-between-ESXi-7-0-3-Clusters-for-VM/m-p/2976688#M45586</guid>
      <dc:creator>Tinto1970</dc:creator>
      <dc:date>2023-07-11T09:27:28Z</dc:date>
    </item>
    <item>
      <title>Re: License downgrade 8.0 -&gt; 6.0</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/License-downgrade-8-0-gt-6-0/m-p/2976685#M34752</link>
      <description>&lt;P&gt;6 months of an old and unpatched system is not as short time... anyway I think you should get in contact with a VMware sales representative and ask him/her fi they can help you.&lt;/P&gt;&lt;P&gt;And, let me ask: why do you want to "&lt;SPAN&gt;&amp;nbsp;license an old hardware with esx 6.0 as &lt;U&gt;maximum supported version&lt;/U&gt;" if there is NO support?&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;In other words: you will be out of support both with esxi 6 and 7: why don't you try upgrading to ESXI 7?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 09:24:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/License-downgrade-8-0-gt-6-0/m-p/2976685#M34752</guid>
      <dc:creator>Tinto1970</dc:creator>
      <dc:date>2023-07-11T09:24:40Z</dc:date>
    </item>
    <item>
      <title>Re: License downgrade 8.0 -&gt; 6.0</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/License-downgrade-8-0-gt-6-0/m-p/2976676#M34746</link>
      <description>&lt;P&gt;sorry, i guess no, no way. The Licensing page in your MyVMware site should not allow you to do so. Give it a try, but I'm pretty sure.&lt;/P&gt;&lt;P&gt;You could try to buy a "second hand" old license of vSphere 6: the key should work but you probably know the contras of using an out of support software, even in labs or non production environments.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 09:04:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/License-downgrade-8-0-gt-6-0/m-p/2976676#M34746</guid>
      <dc:creator>Tinto1970</dc:creator>
      <dc:date>2023-07-11T09:04:58Z</dc:date>
    </item>
    <item>
      <title>Re: How does ESXi run?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/How-does-ESXi-run/m-p/2976675#M288954</link>
      <description>&lt;P&gt;hello, you could probably find interesting infos at the following link&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/ESXi_architecture.pdf" target="_blank"&gt;https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/ESXi_architecture.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 09:00:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/How-does-ESXi-run/m-p/2976675#M288954</guid>
      <dc:creator>Tinto1970</dc:creator>
      <dc:date>2023-07-11T09:00:10Z</dc:date>
    </item>
    <item>
      <title>Re: Interesting observation with two enivornments using the same SAN</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Interesting-observation-with-two-enivornments-using-the-same-SAN/m-p/2976672#M94590</link>
      <description>&lt;P&gt;hi, first of all it would be better that old hosts could not see datastores they don't have to use &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@9A8352F02F49809A161B25D7C247110D/emoticons/1f609.png" alt=":winking_face:" title=":winking_face:" /&gt;&lt;/P&gt;&lt;P&gt;anyway I don't understand... are you saying that the old 6.5 hosts have registered "automatically" VMs that were not present in their Inventory?&lt;BR /&gt;&lt;BR /&gt;It sounds reeealy strange...&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 08:44:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Interesting-observation-with-two-enivornments-using-the-same-SAN/m-p/2976672#M94590</guid>
      <dc:creator>Tinto1970</dc:creator>
      <dc:date>2023-07-11T08:44:07Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter/Photon OS Passwortreset</title>
      <link>https://communities.vmware.com/t5/German-Discussions/vCenter-Photon-OS-Passwortreset/m-p/2976668#M1286</link>
      <description>&lt;P&gt;Hallo, Ich habe nicht gut verstanden das Problem.&lt;/P&gt;&lt;P&gt;Sie müssen auf die Webkonsole (oder Remote Console) der vCenter VM zugreifen, um das Verfahren durchzuführen.&lt;/P&gt;&lt;P&gt;Was passiert? Können Sie bitte einen Screenshot der Webkonsole hier posten?&lt;/P&gt;&lt;P&gt;Danke&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 08:29:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/German-Discussions/vCenter-Photon-OS-Passwortreset/m-p/2976668#M1286</guid>
      <dc:creator>Tinto1970</dc:creator>
      <dc:date>2023-07-11T08:29:22Z</dc:date>
    </item>
    <item>
      <title>caccia allo snapshot (VM needs consolidation)</title>
      <link>https://communities.vmware.com/t5/Italian-Discussions/caccia-allo-snapshot-VM-needs-consolidation/m-p/2974407#M13114</link>
      <description>&lt;P&gt;ciao, più che una domanda volevo condividere un mio breve articoletto in cui racconto come ho fatto a scoprire la causa di uno quel maledetti "VM consolidation needed" che non se ne volevano andare via... perché qualcuno aveva "rapito" il disco alla VM in questione.&lt;/P&gt;&lt;P&gt;Eccolo:&amp;nbsp;&lt;A href="https://www.linkedin.com/pulse/vm-needs-consolidation-warning-backup-software-alessandro-tinivelli" target="_self"&gt;https://www.linkedin.com/pulse/vm-needs-consolidation-warning-backup-software-alessandro-tinivelli&lt;/A&gt;&lt;/P&gt;&lt;P&gt;ogni commento ed esperienza analoga è benvenuto!&lt;/P&gt;</description>
      <pubDate>Fri, 23 Jun 2023 16:05:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Italian-Discussions/caccia-allo-snapshot-VM-needs-consolidation/m-p/2974407#M13114</guid>
      <dc:creator>Tinto1970</dc:creator>
      <dc:date>2023-06-23T16:05:05Z</dc:date>
    </item>
  </channel>
</rss>

