<?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>FoaRyan Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>FoaRyan Tracker</description>
    <pubDate>Tue, 21 Nov 2023 06:16:54 GMT</pubDate>
    <dc:date>2023-11-21T06:16:54Z</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/922086#M77727</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Another issue I ran into this week was in setting up replication for SRM. There are some features &lt;STRONG&gt;only available&lt;/STRONG&gt; in the web client. And others &lt;STRONG&gt;only available&lt;/STRONG&gt; in the C# client. Personally, even with the slowness of the web client, I would be happy if &lt;STRONG&gt;all&lt;/STRONG&gt; features were available in one place. The hybrid environment just means more programming time, more management time, and more frustrated customers.&lt;/P&gt;&lt;BLOCKQUOTE&gt;
&lt;P&gt;Lets also not even get started on VMware's HORRID documentation that contradicts itself and points to other documents that can put you in an endless loop.&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I agree the documentation needs some work as well. There is a lot of good documentation, but it's in the midst of a sea of outdated and/or superseded documentation, leading to lots of confusion. Add to that many or most KB articles don't specify which versions of ESX/ESXi/VMware do or do not apply. Sometimes I've followed procedures thinking, "I sure hope that step 7 is something that still exists in my environment and wasn't done away with in 5.0."&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Jul 2014 18:20:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-Web-Client-is-so-bad-that-my-experience-managing-and/m-p/922086#M77727</guid>
      <dc:creator>FoaRyan</dc:creator>
      <dc:date>2014-07-31T18:20:49Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter 5.5 Client Integration plug-in not working under IE and Chrome</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-5-5-Client-Integration-plug-in-not-working-under-IE-and/m-p/957222#M12490</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is VMware going to address this issue? I'm starting to get quite frustrated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jul 2014 17:23:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-5-5-Client-Integration-plug-in-not-working-under-IE-and/m-p/957222#M12490</guid>
      <dc:creator>FoaRyan</dc:creator>
      <dc:date>2014-07-14T17:23:57Z</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/922040#M77681</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For those having difficulty with slow responsiveness in the vSphere web client, I have a positive update I'd like to provide. I just switched to a new computer Friday and things are running much more smoothly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Old machine was a Core2 Duo Intel with 4GB of ram, running on 32-bit Windows 7. Hard drive was also almost full. Everything would run slow in the web client (even though with the old client that was never a problem).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;New machine is an Intel i5 with 8GB of memory, and things are running much more smoothly. The wait time after clicking things is drastically reduced. Now I still have my issues with the web client, and think it should be scrapped anyhow, but this is at least making the interaction bearable. If anyone else wants to chime in, what hardware are you accessing vSphere from, and how responsive is it to you?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Jun 2014 20:17:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-Web-Client-is-so-bad-that-my-experience-managing-and/m-p/922040#M77681</guid>
      <dc:creator>FoaRyan</dc:creator>
      <dc:date>2014-06-30T20:17:42Z</dc:date>
    </item>
    <item>
      <title>Re: Increase memory in vCenter VM</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Increase-memory-in-vCenter-VM/m-p/2680627#M89262</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, thank you. I appreciate the help, and I may end up doing that. It's just that prior to upgrading to 5.5 there was no need to manually edit any files to make these changes. I think it's the wrong direction for VMware management is all I'm saying.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Jun 2014 13:04:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Increase-memory-in-vCenter-VM/m-p/2680627#M89262</guid>
      <dc:creator>FoaRyan</dc:creator>
      <dc:date>2014-06-24T13:04:49Z</dc:date>
    </item>
    <item>
      <title>Re: Increase memory in vCenter VM</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Increase-memory-in-vCenter-VM/m-p/2680625#M89260</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"Just shutdown the VM and edit settings for RAM whatever you want to add."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And how would you do that when the VM you shut down *is* vCenter? In 5.5 you can't edit the VM's without vCenter because you need the web client.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There should be an easy solution for this, and from what I'm reading throughout this forum, VMWare hasn't thought of it yet: a scheduled memory increase. We need an option IN THE WEB CLIENT (since we have to use it now), to say "The next time this VM reboots, change the ram from amount X to amount Y." Ironically, this option is exactly how you upgrade the VM hardware from version 8 or 9 to 10, etc.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Jun 2014 21:23:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Increase-memory-in-vCenter-VM/m-p/2680625#M89260</guid>
      <dc:creator>FoaRyan</dc:creator>
      <dc:date>2014-06-23T21:23:43Z</dc:date>
    </item>
    <item>
      <title>Re: ESX 5.5 - How do you update VM settings of your VCenter VM?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESX-5-5-How-do-you-update-VM-settings-of-your-VCenter-VM/m-p/2707636#M265626</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm still looking for a solution to this. I need to double the memory in my vCenter server, but that can only be done with it offline. However, I cannot modify VMs without vCenter being *online* in 5.5, and with hardware at version 10 (i.e. on the 5.5 level). There has to be a way to accomplish this without a workaround. 5.5 has been around since 2013 and I refuse to accept command line workarounds for something as essential as managing virtual hardware. Does anyone know a way to get this done through the "normal" channels?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Jun 2014 18:35:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESX-5-5-How-do-you-update-VM-settings-of-your-VCenter-VM/m-p/2707636#M265626</guid>
      <dc:creator>FoaRyan</dc:creator>
      <dc:date>2014-06-23T18:35:00Z</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/922034#M77675</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I like that you bring up the plugin issue. I'm not sure what bug(s) in particular you're referring to, but to me it seems like having to download and install a plugin defeats the purpose of *not* having to download and install a client. Isn't the purpose of getting rid of the C# client to prevent users from having to download software in order to manage VMware?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Outside of that, I honestly don't understand the industry-wide move toward web interfaces. If you still have to install special plugins and/or software, how are they improving anything? Just some more thoughts!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jun 2014 17:49:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-Web-Client-is-so-bad-that-my-experience-managing-and/m-p/922034#M77675</guid>
      <dc:creator>FoaRyan</dc:creator>
      <dc:date>2014-06-17T17:49:38Z</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/922026#M77667</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Matt, I thank you as well for the response. I ran across this thread from a search for "vsphere web client lacking" after a somewhat frustrating day of working with it. I'm a newcomer to vMWare in general, so I don't have a huge background with the C# client or a bias toward it all that much. But I can say that trying to work with the web client is hard to get used to, even with only a little exposure to the alternative.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Menus are in different places (different doesn't mean bad, necessarily, but it seems like there isn't much reason to many of the changes). It runs much slower than the old client, but I do also know as another poster mentioned that this could be due to resources being underprovisioned on our vSphere (as well as the rest of our virtual environment). That said, the C# client still operates much faster than the web client. In general, I don't like web-based management solutions because they all seem to be less efficient than their predecessors (Lync 2010/2013 vs OCS, for example).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I may be brave and join that volunteer corps myself...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Jun 2014 21:30:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-Web-Client-is-so-bad-that-my-experience-managing-and/m-p/922026#M77667</guid>
      <dc:creator>FoaRyan</dc:creator>
      <dc:date>2014-06-04T21:30:45Z</dc:date>
    </item>
  </channel>
</rss>

