{"id":35620,"date":"2018-10-31T13:00:54","date_gmt":"2018-10-31T12:00:54","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=35620"},"modified":"2023-07-16T11:30:31","modified_gmt":"2023-07-16T09:30:31","slug":"vsphere-6-7-update-1-whats-new-and-upgrade","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/vsphere-6-7-update-1-whats-new-and-upgrade\/","title":{"rendered":"vSphere 6.7 Update 1 what's new and upgrade"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-35825 size-large\" title=\"vsphere-67-update1-01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/11\/vsphere-67-update1-01-600x201.jpg\" alt=\"vsphere-67-update1-01\" width=\"600\" height=\"201\" \/><\/p>\n<p>After releasing <a href=\"https:\/\/nolabnoparty.com\/en\/vmware-vsphere-6-7-released\/\">vSphere 6.7<\/a> some months ago, VMware recently released <strong>vSphere 6.7 Update 1<\/strong> introducing some new features and bug fixes.<\/p>\n<p>Some features introduced in previous versions have been <strong>re-designed<\/strong> to optimize performance simplyfing the user experience. vCSA HA, Content Libraries and PSC for example are some areas where the Update 1 introduces the most significant changes.<!--more--><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35827 size-large\" title=\"vsphere-67-update1-02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/11\/vsphere-67-update1-02-600x188.jpg\" alt=\"vsphere-67-update1-02\" width=\"600\" height=\"188\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>What's new\u00a0in vSphere 6.7 Update 1<\/h2>\n<p>Update 1 introduces several new features where the most interesting can be summarized as follows:<\/p>\n<p>&nbsp;<\/p>\n<h4>vSphere vCenter Server 6.7 Update 1<\/h4>\n<p><strong>vSphere Client<\/strong>\u00a0- The vSphere HTML5-based client provides now\u00a0<strong>all the vSphere features<\/strong> and has been optimized in terms of performance. Note the <strong>Home<\/strong> page now displays <strong>resource utilization<\/strong> information.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35829 size-large\" title=\"vsphere-67-update1-03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/11\/vsphere-67-update1-03-600x338.jpg\" alt=\"vsphere-67-update1-03\" width=\"600\" height=\"338\" \/><\/p>\n<p>&nbsp;<\/p>\n<p><strong>Dark theme<\/strong>\u00a0- Update 1 introduces the dark theme that provides a dark background for the vSphere Client for a better view. To switch theme, click the top-right corner next to the username and select <strong>Switch Theme<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35892 size-large\" title=\"vsphere-67-update1-04\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/11\/vsphere-67-update1-04-1-600x359.jpg\" alt=\"vsphere-67-update1-04\" width=\"600\" height=\"359\" \/><\/p>\n<p>&nbsp;<\/p>\n<p><strong>Search<\/strong>\u00a0- It's now possible to search vSphere objects such as VMs, datastores, clusters and so on <strong>using strings<\/strong> and with the option to save the search.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35833 size-large\" title=\"vsphere-67-update1-05\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/11\/vsphere-67-update1-05-600x304.jpg\" alt=\"vsphere-67-update1-05\" width=\"600\" height=\"304\" \/><\/p>\n<p>&nbsp;<\/p>\n<p><strong>Change architecture from PSC external to embedded<\/strong>\u00a0- Update 1 introduces a <strong>CLI tool<\/strong> that allows to embed\u00a0an external PSC in vCenter. It works for the\u00a0<strong>vCSA only<\/strong> (Windows deployments are not supported) and vSphere 6.7 Update 1 must be installed in both PSC and vCenter Server appliances.<\/p>\n<p>The tool can be found in the\u00a0<strong>vcsa-converge-cli<\/strong> folder (two\u00a0JSON templates can be found: decomission and converge) from the vCSA's ISO installation file.<\/p>\n<p><strong>vCSA HA new design<\/strong>\u00a0- The <a href=\"https:\/\/nolabnoparty.com\/en\/vmware-vcenter-high-availability-setup-pt-1\/\">vCSA HA<\/a> feature has been re-designed and <strong>Basic and Advanced options have been removed<\/strong> leaving only one configuration procedure.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35835 size-large\" title=\"vsphere-67-update1-06\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/11\/vsphere-67-update1-06-600x411.jpg\" alt=\"vsphere-67-update1-06\" width=\"600\" height=\"411\" \/><\/p>\n<p>From a\u00a0<strong>single pane of glass<\/strong>\u00a0you can now create the Passive and Witness nodes by cloning the Active node or manually configure the three nodes for an advanced configuration.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35837 size-large\" title=\"vsphere-67-update1-07\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/11\/vsphere-67-update1-07-600x495.jpg\" alt=\"vsphere-67-update1-07\" width=\"600\" height=\"495\" \/><\/p>\n<p>&nbsp;<\/p>\n<p><strong>Content Libraries<\/strong>\u00a0- <a href=\"https:\/\/nolabnoparty.com\/en\/working-with-content-libraries-in-vsphere-6-5\/\">Content Libraries<\/a> is a cool feature introduced in vSphere 6.0 to perform centralized deployments. With this update, Content Libraries now support also\u00a0<strong>templates and OVA files<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35839 size-large\" title=\"vsphere-67-update1-08\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/11\/vsphere-67-update1-08-600x401.jpg\" alt=\"vsphere-67-update1-08\" width=\"600\" height=\"401\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>Additional info can be found in the\u00a0<a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/6.7\/rn\/vsphere-vcenter-server-671-release-notes.html\" target=\"_blank\" rel=\"noopener\">vCenter Server 6.7 Update 1 Release Notes<\/a>.<\/p>\n<p>&nbsp;<\/p>\n<h4>vSphere ESXi 6.7 Update 1<\/h4>\n<p><strong>Extended supported hardware<\/strong> - Additional hardware components are now supported with the Update 1.<\/p>\n<p><strong>vMotion enhancements<\/strong> -\u00a0VMs configured with NVIDIA virtual GPU types can now be moved using vMotion to other hosts with compatible NVIDIA Tesla GPUs.<\/p>\n<p><strong>Update Manager Download Service<\/strong>\u00a0- A database for the\u00a0Update Manager Download Service (UMDS) is no longer required and the installation procedure is now simpler.<\/p>\n<p>Additional info can be found in the <a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/6.7\/rn\/vsphere-esxi-671-release-notes.html?src=vmw_so_vex_akjaer_1025\" target=\"_blank\" rel=\"noopener\">VMware ESXi 6.7 Update 1 Release Notes<\/a>.<\/p>\n<p>&nbsp;<\/p>\n<h4>vSAN 6.7<\/h4>\n<p>Update 1 introduces the new vSAN 6.7 version.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35846 size-large\" title=\"vsphere-67-update1-09\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/11\/vsphere-67-update1-09-600x360.jpg\" alt=\"vsphere-67-update1-09\" width=\"600\" height=\"360\" \/><\/p>\n<p>&nbsp;<\/p>\n<p><strong>Quickstart wizard<\/strong>\u00a0- The creation of the vSAN cluster can be done through the\u00a0Quickstart wizard that simplifies the overall procedure with a <strong>guided process<\/strong>\u00a0covering every aspect of the initial configuration.<\/p>\n<p><strong>Historical and usable capacity reporting<\/strong>\u00a0- A historical capacity dashboard has been introduced showing <strong>capacity usage<\/strong> over a period of time. A <strong>capacity estimator<\/strong> is also included in this new release.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35887 size-large\" title=\"vsphere-67-update1-10\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/11\/vsphere-67-update1-10-600x355.jpg\" alt=\"vsphere-67-update1-10\" width=\"600\" height=\"355\" \/><\/p>\n<p>&nbsp;<\/p>\n<p><strong>Maintenance mode enhancements<\/strong>\u00a0- Data evacuation simulation can be now performed to determine if the operation can be completed successfully. In case of test failure, maintenance mode operation is halted preventing unnecessary data movements.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35850 size-large\" title=\"vsphere-67-update1-11\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/11\/vsphere-67-update1-11-600x313.jpg\" alt=\"vsphere-67-update1-11\" width=\"600\" height=\"313\" \/><\/p>\n<p>&nbsp;<\/p>\n<p><strong>HBA firmware update through VUM\u00a0<\/strong>- Firmware for storage I\/O controller used in vSAN hosts can now be updated through vSphere Update Manager. It is also supported the upgrade using <strong>custom ISOs<\/strong> for vCenter Server not connected to Internet.<\/p>\n<p><strong>Health check enhancements<\/strong>\u00a0- To provide additional flexibility, <strong>multiple approved firmware levels<\/strong> are now supported in the storage controller firmware health check.<\/p>\n<p>Additional info can be found in the\u00a0<a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/6.7\/rn\/vmware-vsan-67u1-release-notes.html\" target=\"_blank\" rel=\"noopener\">VMware vSAN 6.7 Update 1 Release Notes<\/a>.<\/p>\n<p>&nbsp;<\/p>\n<h2>Install vSphere 6.7 Update 1<\/h2>\n<p>&nbsp;<\/p>\n<h4>Upgrade the vCSA<\/h4>\n<p>As usual the first vSphere component to upgrade is the vCenter Server. Download the Update 1 patch from the\u00a0<a href=\"https:\/\/my.vmware.com\/group\/vmware\/patch\" target=\"_blank\" rel=\"noopener\" name=\"&amp;lpos=Release Notes : content link : 465\">VMware Patch Download Center<\/a> and choose\u00a0<strong>VC\u00a06.7.0<\/strong> option.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35853 size-large\" title=\"vsphere-67-update1-12\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/11\/vsphere-67-update1-12-600x289.jpg\" alt=\"vsphere-67-update1-12\" width=\"600\" height=\"289\" \/><\/p>\n<p>Upload the downloaded patch to a datastore where the vCSA has access or to a subscribed\u00a0<a href=\"https:\/\/nolabnoparty.com\/en\/working-with-content-libraries-in-vsphere-6-5\/\">Content Library<\/a>. When the upload has completed successfully, right click the vCSA and select <strong>Edit Settings<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35855 size-large\" title=\"vsphere-67-update1-13\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/11\/vsphere-67-update1-13-600x417.jpg\" alt=\"vsphere-67-update1-13\" width=\"600\" height=\"417\" \/><\/p>\n<p>Select the <strong>Datastore ISO File<\/strong> option and attach the patch in <strong>ISO format<\/strong> to the vCSA <strong>CD\/DVD drive<\/strong>. Thick the\u00a0<strong>Connected<\/strong>\u00a0check box then click\u00a0<strong>OK<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35857 size-large\" title=\"vsphere-67-update1-14\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/11\/vsphere-67-update1-14-600x563.jpg\" alt=\"vsphere-67-update1-14\" width=\"600\" height=\"563\" \/><\/p>\n<p>To proceed with the upgrade, <strong>SSH the vCSA<\/strong> and login using <strong>root credentials<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35859 size-large\" title=\"vsphere-67-update1-15\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/11\/vsphere-67-update1-15-600x223.jpg\" alt=\"vsphere-67-update1-15\" width=\"600\" height=\"223\" \/><\/p>\n<p>Although <strong>staging the ISO<\/strong> is not required, it allows to run the installation later on. Run the following command to stage the ISO and <strong>accept the EULA<\/strong> to\u00a0proceed:<\/p>\n<p><span style=\"color: #0000ff;\"># software-packages stage --iso<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35867 size-large\" title=\"vsphere-67-update1-16\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/11\/vsphere-67-update1-16-600x142.jpg\" alt=\"vsphere-67-update1-16\" width=\"600\" height=\"142\" \/><\/p>\n<p>To install the Update 1 in the vCSA run the command below and\u00a0<strong>reboot the appliance<\/strong>\u00a0to complete the installation when the procedure has finished.<\/p>\n<p><span style=\"color: #0000ff;\">#\u00a0software-packages install --staged<br \/>\n# reboot<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35869 size-large\" title=\"vsphere-67-update1-17\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/11\/vsphere-67-update1-17-600x310.jpg\" alt=\"vsphere-67-update1-17\" width=\"600\" height=\"310\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>When the boot has been completed, the vCSA's\u00a0new version number is now <strong>6.7.0.20000 build 10244745<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35871 size-large\" title=\"vsphere-67-update1-18\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/11\/vsphere-67-update1-18-600x400.jpg\" alt=\"vsphere-67-update1-18\" width=\"600\" height=\"400\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>Upgrade the ESXi host<\/h4>\n<p>Once the vCSA has been upgraded, to take advantage of new features introduced with Update 1 all ESXi hosts must have same version and they can be easily <strong>updated using VUM<\/strong>.<\/p>\n<p>Select the cluster where the ESXi hosts to upgrade are located and go to <strong>Updates<\/strong> tab. Select <strong>Host Updates<\/strong> in the <strong>Overview<\/strong> area and select the appropriate baseline to attach. Click <strong>Stage<\/strong> to save new patches directly to the hosts.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35879 size-large\" title=\"vsphere-67-update1-19\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/11\/vsphere-67-update1-19-600x293.jpg\" alt=\"vsphere-67-update1-19\" width=\"600\" height=\"293\" \/><\/p>\n<p>When stage process has completed, click <strong>Remediate<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35881 size-large\" title=\"vsphere-67-update1-20\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/11\/vsphere-67-update1-20-600x245.jpg\" alt=\"vsphere-67-update1-20\" width=\"600\" height=\"245\" \/><\/p>\n<p>The Update 1 is being installed in the selected cluster. If vSAN cluster is configured in your infrastructure, VUM ensures that <strong>data availability<\/strong> is not affected by the upgrade process.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35883 size-large\" title=\"vsphere-67-update1-21\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/11\/vsphere-67-update1-21-600x362.jpg\" alt=\"vsphere-67-update1-21\" width=\"600\" height=\"362\" \/><\/p>\n<p>The vCSA 6.7 Update 1 dashboard.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35885 size-large\" title=\"vsphere-67-update1-22\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/11\/vsphere-67-update1-22-600x338.jpg\" alt=\"vsphere-67-update1-22\" width=\"600\" height=\"338\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>Upgrade vSAN to version 6.7<\/h4>\n<p>The procedure to upgrade vSAN to version 6.7 is pretty simple and a detailed how-to guide can be found in <a href=\"https:\/\/nolabnoparty.com\/en\/vsphere-6-7-upgrade-vsan-6-6-to-6-7-pt-4\/\">this post<\/a>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-35889 size-large\" title=\"vsphere-67-update1-23\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/11\/vsphere-67-update1-23-600x493.jpg\" alt=\"vsphere-67-update1-23\" width=\"600\" height=\"493\" \/><\/p>\n<p>After the release of the Update 1, vSphere 6.7 is more stable and robust. Organizations may now consider to <strong>perfom a safe upgrade<\/strong> of their virtual infrastructures to vSphere 6.7 U1.<\/p>\n<p><img decoding=\"async\" title=\"signature\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/images\/firma.jpg\" alt=\"signature\" \/><\/p>\n","protected":false},"excerpt":{"rendered":"<p>After releasing vSphere 6.7 some months ago, VMware recently released vSphere 6.7 Update 1 introducing some new features and bug fixes. Some features introduced in previous versions have been re-designed to optimize performance simplyfing the user experience. vCSA HA, Content Libraries and PSC for example are some areas where the Update 1 introduces the most significant changes.<\/p>\n","protected":false},"author":3,"featured_media":35825,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[903,2701],"tags":[1920,1551,1664,1879],"class_list":["post-35620","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-vsphere-en","tag-update-1-esxi","tag-vcsa","tag-vsan","tag-vsphere-6-7","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/35620","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=35620"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/35620\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/35825"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=35620"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=35620"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=35620"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}