<?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>wojtowvm Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>wojtowvm Tracker</description>
    <pubDate>Tue, 21 Nov 2023 08:42:36 GMT</pubDate>
    <dc:date>2023-11-21T08:42:36Z</dc:date>
    <item>
      <title>Re: vSphere Web Client SUCKs so bad that my experience managing and supporting VMware has turn to SH**!</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-Web-Client-is-so-bad-that-my-experience-managing-and/m-p/922216#M77857</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE&gt;
&lt;P style="margin: 2px; font-size: 14px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;I am brand new to vSphere, having gotten it just a year ago. We would not be running it if not for the combination of ESXi and the Web Client. While our shop has plenty of Windows in it, the majority of our virtualized servers are Linux, and our expertise lies there.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P style="margin: 2px; font-size: 14px; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;Having a management interface that is not dependent on Windows is a win for us, and I for one appreciate the fact that VMware moved in this direction. Could it perform better? Yes. Do I want them to quit development on it and go back to a vCenter management interface where I'd have to run a virtualized desktop to run the management interface, or couldn't access it remotely, or couldn't check on the health of my servers from my iPad? No.&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What?&amp;nbsp; Wait.&amp;nbsp; Flash is not supported on iPad, and a modern enough version to run the vSphere web-client is not supported on linux. (as Adobe quit supporting linux on Flash several versions ago)&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, I know there are some unsupported 3rd-party workarounds that sort of make some flash apps kind-of work on both platforms, but certainly this is iffy at best, and are not something updated for the many, many vulnerabilities that the Flash format has.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In either case, the required vmWare browser plug-in, necessary to make key features such as console access work, is not available on iPad or linux. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Nov 2014 18:54:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-Web-Client-is-so-bad-that-my-experience-managing-and/m-p/922216#M77857</guid>
      <dc:creator>wojtowvm</dc:creator>
      <dc:date>2014-11-26T18:54:04Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere Web Client SUCKs so bad that my experience managing and supporting VMware has turn to SH**!</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-Web-Client-is-so-bad-that-my-experience-managing-and/m-p/922063#M77704</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Kahonu84,&amp;nbsp; if you are content with 5.0 and don't need any of the 5.5 features, then it seems like staying with what you have would be a perfectly acceptable choice for now.&amp;nbsp; The announced end of VMware support for 5.0 is&amp;nbsp; 2016/08/24&amp;nbsp;&amp;nbsp; so you've got a little time yet before you won't get security patches anymore.&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I upgraded because I happened to be in the process of redoing my whole vmware infrastructure and it seemed like a good time to make the move for future proofing, the not always true assumption that newer is always better, and without having tried the new web interface yet, it seemed like that'd be handy (manage it from any browser you happened to be in front of!)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But it was a lot of work and getting the new SSO working was frustrating.&amp;nbsp; In the end I'm happy enough with the results, but most all of the benefits I care about were from the new hardware (and a license upgrade) rather than the esxi version upgrade.&amp;nbsp;&amp;nbsp; I've tried to make good use of the web interface, mostly for casual tasks, but still depend on the old client when I'm busy with lots of tasks.&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Jul 2014 19:29:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-Web-Client-is-so-bad-that-my-experience-managing-and/m-p/922063#M77704</guid>
      <dc:creator>wojtowvm</dc:creator>
      <dc:date>2014-07-18T19:29:02Z</dc:date>
    </item>
    <item>
      <title>Re: CD/DVD drive 1 (Connecting...) forever</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/CD-DVD-drive-1-Connecting-forever/m-p/1333095#M123717</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;sorry, no answer, but just to say that I've experienced that too. not, always, but on occasion &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Jul 2014 18:44:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/CD-DVD-drive-1-Connecting-forever/m-p/1333095#M123717</guid>
      <dc:creator>wojtowvm</dc:creator>
      <dc:date>2014-07-18T18:44:05Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere Web Client SUCKs so bad that my experience managing and supporting VMware has turn to SH**!</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-Web-Client-is-so-bad-that-my-experience-managing-and/m-p/922060#M77701</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Kahonu84 - yes that is 99% true if you are not expecting to do anything different than you were in 5.0 (i.e. not use some of the 5.5 only features) - I seem to remember there being one or two initial setup things that required the web client (I believe it was related to configuring identity sources in SSO - which setting up is a challenge in itself)&amp;nbsp;&amp;nbsp; but otherwise you can do everything that you are normally used to doing on a daily basis through the non-web client. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You will be prompted to download an update to the client the first time you try to connect it to the new vcenter server with it, and from then on it will display notice above the username/password dialog warning you that new features won't be available there, but you very quickly get used to completely ignoring that. &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Jul 2014 18:35:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-Web-Client-is-so-bad-that-my-experience-managing-and/m-p/922060#M77701</guid>
      <dc:creator>wojtowvm</dc:creator>
      <dc:date>2014-07-18T18:35:32Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere Web Client SUCKs so bad that my experience managing and supporting VMware has turn to SH**!</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-Web-Client-is-so-bad-that-my-experience-managing-and/m-p/922054#M77695</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;CP7,&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The key is to remember to set the VM hardware version to a lower version than 10 when creating the VM. (it is an easily overlooked setting on in the new vm dialogs on the web client) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Having not done that.&amp;nbsp; You have a few options to try:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;start over (safest) &lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;-or-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN style="line-height: 1.5em; font-size: 10pt;"&gt; Use the "standalone converter" to convert your existing VM to an earlier version. (pretty safe - &lt;/SPAN&gt;especially&lt;SPAN style="line-height: 1.5em; font-size: 10pt;"&gt; since you will still have the original)&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;-or-&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Some people, including me, report success with the following (obviously not recommended for critical stuff but the fastest way):&lt;/LI&gt;&lt;/UL&gt;&lt;OL&gt;&lt;LI&gt; shut down the VM. &lt;/LI&gt;&lt;LI&gt;remove the VM from inventory (careful&amp;nbsp; do not delete)&lt;/LI&gt;&lt;LI&gt;edit the .vmx file (via the host console, ssh, or by downloading via datastore browser, editing and uploading)&lt;/LI&gt;&lt;LI&gt;Change &lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;virtualHW.version&lt;/SPAN&gt; setting in the file to the earlier version. &lt;/LI&gt;&lt;LI&gt;locate the vmx file&amp;nbsp; in datastore browser, right click and add to inventory&lt;/LI&gt;&lt;LI&gt;upon power on, if it asked you if you copied it or moved it, tell it you moved it &lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp; You should certainly back up your VM first in case things go bad.&amp;nbsp; Testing this on a clone of your target vm is also a good idea.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Personally I think the inability to edit/manage version 10 format VMs in the c# client is on purpose to force people to the web interface.&amp;nbsp; It probably would be very little work for them to modify it to support the new VM hardware version since it is very substantially similar from a configuration standpoint.&amp;nbsp; (hence the ability to do the trick above) &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Jul 2014 16:36:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-Web-Client-is-so-bad-that-my-experience-managing-and/m-p/922054#M77695</guid>
      <dc:creator>wojtowvm</dc:creator>
      <dc:date>2014-07-18T16:36:18Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere Web Client SUCKs so bad that my experience managing and supporting VMware has turn to SH**!</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-Web-Client-is-so-bad-that-my-experience-managing-and/m-p/922049#M77690</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Completely agree with the "it sucks" sentiment and nearly all the other posters here.&amp;nbsp;&amp;nbsp;&amp;nbsp; I won't waste space by reiterating all the issues previously mentioned other than to say "me too".&amp;nbsp; Did want to mention a complaint that I haven't read here yet:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The console no longer has a palette of menus and tools at the top of the window like the C# client console windows.&amp;nbsp; (send Ctrl-Alt-Del and Full Screen are the only buttons despite a large banner).&amp;nbsp;&amp;nbsp; If you want to do anything to a VM that you are working intently on (like tweak its settings, take a snapshot, attach an iso, etc) you have to go back and find it on the main screen and get in the right context to make changes.&amp;nbsp; Of course, you likely switched that to some other part of the main window while you were waiting for the VM open in the console to finish installing an update, shutting down or whatever.&amp;nbsp;&amp;nbsp; Working with several of these like that is very time consuming. &lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;P.S.&amp;nbsp;&amp;nbsp; I ha&lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;ve found that the advice elsewhere to speed up responsiveness really does help to make it less sluggish. (right click while the interface is loading and only the vmware logo is displayed, select settings and increase local storage to 10M or unlimited - must right click before the username/password boxes appear as right click is disabled then).&amp;nbsp; Do a browser reload after making this change.&amp;nbsp;&amp;nbsp; Less agonizing now (the trees especially perform faster), but still nowhere close to the experience and usability of the C# client.&amp;nbsp;&amp;nbsp; I've gone from total loathing to mere resentment. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;Running 5.5 (latest updates as of writing this)&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Jul 2014 19:11:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-Web-Client-is-so-bad-that-my-experience-managing-and/m-p/922049#M77690</guid>
      <dc:creator>wojtowvm</dc:creator>
      <dc:date>2014-07-16T19:11:22Z</dc:date>
    </item>
    <item>
      <title>Re: PSOD on Dell R515 BIOS 2.0.2 - ESXi 5.0 Updatetd</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/PSOD-on-Dell-R515-BIOS-2-0-2-ESXi-5-0-Updatetd/m-p/1692156#M153120</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="padding-left: 30px;"&gt;vMotion is not necessary to trigger the bug as it happened multiple times for me on a single R515 that doesn't even have vMotion enabled.&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;OK, thanks for the updatel. This morning our Dell support technician&amp;nbsp; has confirmed, that there is a known bug happening with 62xx processors&amp;nbsp; during vmotion, when the latest BIOS is running. &lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Mar 2013 17:16:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/PSOD-on-Dell-R515-BIOS-2-0-2-ESXi-5-0-Updatetd/m-p/1692156#M153120</guid>
      <dc:creator>wojtowvm</dc:creator>
      <dc:date>2013-03-15T17:16:54Z</dc:date>
    </item>
    <item>
      <title>Re: PSOD on Dell R515 BIOS 2.0.2 - ESXi 5.0 Updatetd</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/PSOD-on-Dell-R515-BIOS-2-0-2-ESXi-5-0-Updatetd/m-p/1692155#M153119</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Interesting that the HP advisory says it is fixed in more recent BIOS for their products and recommend that over downgrading.&amp;nbsp; I wonder if they actually fixed the problem, or just re-released a prior BIOS with the changes that caused the problem backed out (but perhaps keeping other fixes and enhancements)?&amp;nbsp;&amp;nbsp;&amp;nbsp; Dell needs to respond more quickly to this issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Mar 2013 17:05:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/PSOD-on-Dell-R515-BIOS-2-0-2-ESXi-5-0-Updatetd/m-p/1692155#M153119</guid>
      <dc:creator>wojtowvm</dc:creator>
      <dc:date>2013-03-15T17:05:46Z</dc:date>
    </item>
    <item>
      <title>Re: PSOD on Dell R515 BIOS 2.0.2 - ESXi 5.0 Updatetd</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/PSOD-on-Dell-R515-BIOS-2-0-2-ESXi-5-0-Updatetd/m-p/1692143#M153107</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Note that it doesn't seem to be possible to downgrade to the 1.2.4 version of the R515 BIOS that is listed on the download page as an alternative to the 2.0.2 BIOS.&amp;nbsp; It says it successfully loads and that you should reboot to complete the process, but upon rebooting, it says that the loading process failed and returns to the current BIOS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you click on the "previous versions" link below the 2.0.2 BIOS entry on the download page, you have a variety of options to choose from.&amp;nbsp;&amp;nbsp; I chose 1.9.3 which did load successfully on reboot and so far has not crashed with a PSOD.&amp;nbsp; (though its only been a few days).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Feb 2013 16:45:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/PSOD-on-Dell-R515-BIOS-2-0-2-ESXi-5-0-Updatetd/m-p/1692143#M153107</guid>
      <dc:creator>wojtowvm</dc:creator>
      <dc:date>2013-02-21T16:45:06Z</dc:date>
    </item>
    <item>
      <title>Re: PSOD on Dell R515 BIOS 2.0.2 - ESXi 5.0 Updatetd</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/PSOD-on-Dell-R515-BIOS-2-0-2-ESXi-5-0-Updatetd/m-p/1692141#M153105</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'll add a me-to here.&amp;nbsp;&amp;nbsp; Dell R515, updated to 2.0.2 BIOS last week, ESXi5.0&amp;nbsp; have had two PSOD since then.&amp;nbsp;&amp;nbsp; Has never crashed prior to this. Just downgraded to older BIOS and hoping for the best.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2013 18:22:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/PSOD-on-Dell-R515-BIOS-2-0-2-ESXi-5-0-Updatetd/m-p/1692141#M153105</guid>
      <dc:creator>wojtowvm</dc:creator>
      <dc:date>2013-02-19T18:22:06Z</dc:date>
    </item>
  </channel>
</rss>

