<?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: VCSA 7.0 U3 Broken in VMware vCenter™ Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2879631#M44527</link>
    <description>&lt;P&gt;this is serious horse dung. &amp;nbsp;At least they could have provided a tool to convert a backup from esxi 7.0.3 back to 7.0.2 so we dont' need to fully reconfigure the entire thing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I really hope my vcenter fix works cause that's even worse to reconfigure from scratch on a live env. &amp;nbsp;So upset, they could have at least put in a redirect for the update URL. &amp;nbsp;The update was obviously mishandled but now mishandling the pull and making things even worse for us paying a ton of money for this is just horrible.&lt;/P&gt;</description>
    <pubDate>Tue, 23 Nov 2021 21:35:48 GMT</pubDate>
    <dc:creator>BlueFalls</dc:creator>
    <dc:date>2021-11-23T21:35:48Z</dc:date>
    <item>
      <title>VCSA 7.0 U3 Broken</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2873304#M44246</link>
      <description>&lt;P&gt;Anyone else annoyed with VCSA 7.0 U3 (7.0.3) and the growing list of "things that are broke"?&amp;nbsp;&lt;/P&gt;&lt;P&gt;First, Lifecycle Manager requiring a SSO account to work.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Second, the redesign making things difficult to find (missing top bar).&amp;nbsp;&lt;/P&gt;&lt;P&gt;Third, good luck finding where to add columns to the display.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Fourth, everytime you right click on a single object, the "Items Selected" counter increments regardless of how many objects are actually selected.&lt;/P&gt;&lt;P&gt;I've confirmed all four of these are reproducable across vCenter installs and are "Known Issues".&lt;/P&gt;</description>
      <pubDate>Wed, 20 Oct 2021 19:05:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2873304#M44246</guid>
      <dc:creator>Tibmeister</dc:creator>
      <dc:date>2021-10-20T19:05:12Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 7.0 U3 Broken</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2873462#M44252</link>
      <description>&lt;P&gt;Agreed on all points.&lt;/P&gt;&lt;P&gt;I have another, wondering if anyone else sees it.&amp;nbsp; When I login to vCenter using domain\user or just user since the domain is the default identity source, and password, I get invalid credentials.&amp;nbsp; If I check the box to use the session credentials, which will use the same credentials I just tried, I get right in.&lt;/P&gt;&lt;P&gt;Maybe this is a new feature that I just missed, unsure.&amp;nbsp; Is anyone else seeing this?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 21 Oct 2021 13:05:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2873462#M44252</guid>
      <dc:creator>kgmartin</dc:creator>
      <dc:date>2021-10-21T13:05:46Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 7.0 U3 Broken</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2874276#M44302</link>
      <description>&lt;P&gt;They released vCenter 7.0.3a last week that addresses the Lifecycle Manager issue&lt;/P&gt;</description>
      <pubDate>Mon, 25 Oct 2021 15:48:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2874276#M44302</guid>
      <dc:creator>mbartle</dc:creator>
      <dc:date>2021-10-25T15:48:15Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 7.0 U3 Broken</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2874841#M44345</link>
      <description>&lt;P&gt;Ok, I just did an upgrade to vCenter 7.0.3.00000 last friday and today to 7.0.3.00100 (former 7.0.2.00400) but since that upgrade, I am unable to extend disk sizes of VMs, no matter what VM I choose and no matter what type of disk (thin or thick).&lt;/P&gt;&lt;P&gt;As soon as I click 'Edit settings' and try to change the value of the disk size, input is blocked. Selecting a disk results in an empty overview (no disk information available) and a disk size of 0GB.&lt;/P&gt;&lt;P&gt;So vCenter is now out of order regarding this feature and disks must be extended through the ESXi host client instead &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@67A5DA1D81269E9C7CE09DF646BB7A7A/emoticons/1f621.png" alt=":pouting_face:" title=":pouting_face:" /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Oct 2021 19:18:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2874841#M44345</guid>
      <dc:creator>Didi7</dc:creator>
      <dc:date>2021-10-27T19:18:07Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 7.0 U3 Broken</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2874858#M44347</link>
      <description>&lt;P&gt;We had just recently upgraded to 7.02d, looked at 7.03 and figured we'd hold off for awhile, beginning to think that was a good decision.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Oct 2021 20:56:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2874858#M44347</guid>
      <dc:creator>johnmcc22</dc:creator>
      <dc:date>2021-10-27T20:56:36Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 7.0 U3 Broken</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2874948#M44349</link>
      <description>&lt;P&gt;Wise decision!&lt;/P&gt;</description>
      <pubDate>Thu, 28 Oct 2021 10:04:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2874948#M44349</guid>
      <dc:creator>Didi7</dc:creator>
      <dc:date>2021-10-28T10:04:44Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 7.0 U3 Broken</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2875075#M44356</link>
      <description>&lt;P&gt;U3a makes things worse.&amp;nbsp; HA is not functional post-update, and LCM cluster scans have unknown results.&amp;nbsp; Apparently it's related to an intel i40enu nic driver.&amp;nbsp; I'm sick of chasing these issues.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Oct 2021 16:29:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2875075#M44356</guid>
      <dc:creator>dgrove12</dc:creator>
      <dc:date>2021-10-28T16:29:58Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 7.0 U3 Broken</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2875168#M44357</link>
      <description>&lt;P&gt;So really they fixed the LCM issue so we don't have to use a SSO account, but several other things are broke.&amp;nbsp; Does anyone remember such a poo set of updates come out of VMware before in vSphere?&amp;nbsp; I sure don't, so please, UI folks, get your act together and do some quality control before releasing another update, and honestly, I would even say pull the entire 7.0.3 update line off, it's nothing but problems that some of us are stuck with.&lt;/P&gt;</description>
      <pubDate>Fri, 29 Oct 2021 01:35:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2875168#M44357</guid>
      <dc:creator>Tibmeister</dc:creator>
      <dc:date>2021-10-29T01:35:08Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 7.0 U3 Broken</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2876068#M44400</link>
      <description>&lt;P&gt;Anyone else notice that MS Edge also doesn't work with vSphere UI?&amp;nbsp; Mine just goes into this Refresh loop, there the circle arrow refresh button will spin, return to arrow, spin, return to arrow, etc, forever and no page content is loaded.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Nov 2021 14:10:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2876068#M44400</guid>
      <dc:creator>Tibmeister</dc:creator>
      <dc:date>2021-11-03T14:10:08Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 7.0 U3 Broken</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2876070#M44401</link>
      <description>&lt;P&gt;Looks like this is the workaround for your issue specifically&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/85982" target="_blank"&gt;vSphere Lifecycle Manager can show non-compliant status after rollup Remediation, new cluster creation or transition from Baseline-managed cluster to Image-managed cluster for few upgrade paths due to i40en/i40enu driver name change. (85982) (vmware.com)&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Nov 2021 14:15:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2876070#M44401</guid>
      <dc:creator>Tibmeister</dc:creator>
      <dc:date>2021-11-03T14:15:55Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 7.0 U3 Broken</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2876075#M44403</link>
      <description>&lt;P&gt;Oh yeah, almost forgot, add the inability to use SMB for VCSA backups.&amp;nbsp; What a joke.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Nov 2021 14:23:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2876075#M44403</guid>
      <dc:creator>Tibmeister</dc:creator>
      <dc:date>2021-11-03T14:23:01Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 7.0 U3 Broken</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2876312#M44415</link>
      <description>&lt;P&gt;7U3 is an utterly piece of beta garbage that broke a lot more than it fixed or added in features. In a process of rolling everything back. Done with ESXi hosts, now need to downgrade a vCenter itself.&lt;/P&gt;&lt;P&gt;They are calling it a "Biggest update ever", I call it a "Biggest **bleep** up ever" (Windows Me / Vista) style.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Nov 2021 14:58:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2876312#M44415</guid>
      <dc:creator>Podgorny</dc:creator>
      <dc:date>2021-11-04T14:58:33Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 7.0 U3 Broken</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2876324#M44416</link>
      <description>&lt;P&gt;This work around only fixes the update not the remediation.&lt;/P&gt;&lt;P&gt;I ended up doing a fresh install of U3 so I don't have this issue of the intel enu/ens renaming and my remediation is still a mess that doesn't work at all.&lt;/P&gt;&lt;P&gt;Though this is very useful for those that want to upgrade.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Nov 2021 15:29:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2876324#M44416</guid>
      <dc:creator>BlueFalls</dc:creator>
      <dc:date>2021-11-04T15:29:49Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 7.0 U3 Broken</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2876333#M44417</link>
      <description>&lt;P&gt;I've considered downgrading, but what a mess that would be at this point!&amp;nbsp; I have vSAN deployed mainly in 2-Node clusters, so you can imagine how impossible that would be!&lt;/P&gt;</description>
      <pubDate>Thu, 04 Nov 2021 16:20:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2876333#M44417</guid>
      <dc:creator>Tibmeister</dc:creator>
      <dc:date>2021-11-04T16:20:24Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 7.0 U3 Broken</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2876341#M44418</link>
      <description>&lt;P&gt;I was going to as well, but the thought of having to manually re configure all my ESXi nodes cause I can't export a newer config and import it into the last version really causes issues. &amp;nbsp;I'm going to start a backup repo that keeps every version of ESXi backup in it. &amp;nbsp;Thanks VMware this is the extra work I needed &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;</description>
      <pubDate>Thu, 04 Nov 2021 16:41:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2876341#M44418</guid>
      <dc:creator>BlueFalls</dc:creator>
      <dc:date>2021-11-04T16:41:49Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 7.0 U3 Broken</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2879070#M44514</link>
      <description>&lt;P&gt;For your reading pleasure&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/86398" target="_blank"&gt;https://kb.vmware.com/s/article/86398&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/86287" target="_blank"&gt;https://kb.vmware.com/s/article/86287&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/86281" target="_blank"&gt;https://kb.vmware.com/s/article/86281&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I will be rebuilding all of my hosts to ESXi 7.0 Update 2d, what a pain that will be.&amp;nbsp; Thankfully, we aren't production with vSAN and I can move the VMs around and rebuild the cluster, but that's a ton of extra work.&amp;nbsp; As for vCenter itself, well, I'm on the fence of staying with vCenter 7 Update 3a or building a new vCenter on 7 Update 2d.&amp;nbsp; Fun part was as part of an SR with VMware I was in the middle of upgrading vCenter to 7 Update 3b and ESXi 7 Update 3b when they pulled things, so my hosts couldn't get fdm installed for ESXi 7 U3b, which caused some fun there since it was imaged based vLCM, again at VMware Support's suggestion.&lt;/P&gt;&lt;P&gt;This is, in my long memory of VMware (20+ years) the worst pile of trash to come out from them.&amp;nbsp; I hope they get their act together, get good QA, and again release quality and trust worthy products.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Nov 2021 21:48:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2879070#M44514</guid>
      <dc:creator>Tibmeister</dc:creator>
      <dc:date>2021-11-19T21:48:32Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 7.0 U3 Broken</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2879626#M44525</link>
      <description>&lt;P&gt;Man this makes it all worse honestly. &amp;nbsp;How can I downgrade vcenter when I haven't been able to do backups since SMB is broken in, and now it won't get updates even when there is one cause they removed it?!?!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm trying to figure out how I'm going to downgrade to get into a usable state again. &amp;nbsp;And I can't figure out how to do vCenter without a full reinstall. &amp;nbsp;This is HORRIBLE!!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I just forced it to use &lt;SPAN&gt;&lt;A href="https://vapp-updates.vmware.com/vai-catalog/valm/vmw/" target="_blank"&gt;https://vapp-updates.vmware.com/vai-catalog/valm/vmw/&lt;/A&gt;&amp;lt;uuid&amp;gt;/7.0.3.00100.latest/&lt;/SPAN&gt;&amp;nbsp;I hope this works &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;</description>
      <pubDate>Tue, 23 Nov 2021 21:23:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2879626#M44525</guid>
      <dc:creator>BlueFalls</dc:creator>
      <dc:date>2021-11-23T21:23:31Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 7.0 U3 Broken</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2879629#M44526</link>
      <description>&lt;P&gt;I hope a patch is coming soon.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Nov 2021 21:56:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2879629#M44526</guid>
      <dc:creator>dgrove12</dc:creator>
      <dc:date>2021-11-23T21:56:01Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 7.0 U3 Broken</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2879631#M44527</link>
      <description>&lt;P&gt;this is serious horse dung. &amp;nbsp;At least they could have provided a tool to convert a backup from esxi 7.0.3 back to 7.0.2 so we dont' need to fully reconfigure the entire thing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I really hope my vcenter fix works cause that's even worse to reconfigure from scratch on a live env. &amp;nbsp;So upset, they could have at least put in a redirect for the update URL. &amp;nbsp;The update was obviously mishandled but now mishandling the pull and making things even worse for us paying a ton of money for this is just horrible.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Nov 2021 21:35:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2879631#M44527</guid>
      <dc:creator>BlueFalls</dc:creator>
      <dc:date>2021-11-23T21:35:48Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 7.0 U3 Broken</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2879652#M44528</link>
      <description>&lt;P&gt;Yeah, ended up building a new vCenter on 7.0 U2d and using Advanced Cross vCenter vMotion, and rebuilding all my hosts back to ESXi 7.0 U2c.&amp;nbsp;&lt;/P&gt;&lt;P&gt;A complete and utter pain in the arse to be honest, but better safe than sorry since I am running a number of 2-Node vSAN clusters in various branch offices I can't get to.&amp;nbsp; I still have my older ESXi 6.7 hosts that I can use as swing hosts to prevent downtime, but dang this blows.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Nov 2021 03:15:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2879652#M44528</guid>
      <dc:creator>Tibmeister</dc:creator>
      <dc:date>2021-11-24T03:15:44Z</dc:date>
    </item>
  </channel>
</rss>

