{"id":13305,"date":"2015-07-20T10:00:00","date_gmt":"2015-07-20T08:00:00","guid":{"rendered":"http:\/\/nolabnoparty.com\/?p=13305"},"modified":"2023-07-16T11:25:17","modified_gmt":"2023-07-16T09:25:17","slug":"vcsa-6-0-setup-vsphere-update-manager-pt-1","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/vcsa-6-0-setup-vsphere-update-manager-pt-1\/","title":{"rendered":"VCSA 6.0: setup vSphere Update Manager - pt. 1"},"content":{"rendered":"

\"installvum60vcsa01\"<\/p>\n

In the new VCSA 6.0 (vCenter Server Appliance), vSphere Update Manager (VUM) is the only \"Windows\" component required by vSphere 6.0.<\/p>\n

To run the VUM service when the VCSA is used as vCenter Server, you need a Windows server and a SQL database. For small scale deployment (up to five hosts) SQL Express 2012<\/strong> is bundled in the vCenter Installer but for bigger environments SQL Server and Oracle<\/strong> are the preferred platforms to use.<\/p>\n

<\/p>\n

 <\/p>\n

Blog series<\/h2>\n

VCSA 6.0: setup vSphere Update Manager - pt. 1
\nVCSA 6.0: install vSphere Client and VUM plugin - pt. 2<\/a>
\nVCSA 6.0: configure vSphere Update Manager - pt. 3<\/a><\/p>\n

 <\/p>\n

Create the Update Manager DB and DSN<\/h2>\n

If you are NOT going to use the embedded SQL Express Server<\/strong> provided with VMware vCenter Installer, you need to create the VUM database and the DNS entry manually in the SQL server before beginning the VUM installation.<\/p>\n

From the SQL Server open the Server Management Studio<\/strong>, right click Databases<\/strong> item and select New Database<\/strong> option.<\/p>\n

\"installvum60vcsa02\"<\/p>\n

Type\u00a0the Database name<\/strong> like VIM_UPD<\/em> then click OK<\/strong>.<\/p>\n

\"installvum60vcsa03\"<\/p>\n

The database is being created.<\/p>\n

\"installvum60vcsa04\"<\/p>\n

The database has been created successfully and listed in the installed databases.<\/p>\n

\"installvum60vcsa05\"<\/p>\n

Close the Server Management Studio<\/strong> and open the ODBC Data Sources (32-bit)<\/strong> to configure the DSN<\/strong>.<\/p>\n

Select System DSN<\/strong> and click on Add<\/strong> button. From the list select the SQL Server Native Client 11.0<\/strong> and click Finish<\/strong>.<\/p>\n

\"installvum60vcsa06\"<\/p>\n

Give a Name<\/strong>, a Description<\/strong> and select the SQL Server<\/strong> you want to connect to then click Next<\/strong>.<\/p>\n

\"installvum60vcsa07\"<\/p>\n

Leave default then click Next<\/strong>.<\/p>\n

\"installvum60vcsa08\"<\/p>\n

Enable\u00a0the Change the default database to<\/strong> option and select VIM_UPD<\/strong> from the drop-down menu. Click Next<\/strong>.<\/p>\n

\"installvum60vcsa09\"<\/p>\n

Leave default values and click Finish<\/strong>.<\/p>\n

\"installvum60vcsa10\"<\/p>\n

Click Test Data Source<\/strong> to test the connection.<\/p>\n

\"installvum60vcsa11\"<\/p>\n

If the tests are completed successfully, click OK<\/strong> twice to close the windows.<\/p>\n

\"installvum60vcsa12\"<\/p>\n

The just created System Data Source<\/strong>\u00a0is now listed. Click OK<\/strong> to close.<\/p>\n

\"installvum60vcsa13\"<\/p>\n

Run the VMware vCenter installer<\/strong> and select the Server<\/strong> option under vSphere Update Manager<\/strong> section.<\/p>\n

Check Use Microsoft SQL Server 2012 Express as the embedded database<\/strong> option to install SQL Express 2012 in the server. The built-in installer takes care of the complete setup of SQL Express and no additional configuration<\/strong> is required (previous steps are not needed).<\/p>\n

\"installvum60vcsa14\"<\/p>\n

Click Next<\/strong> to continue.<\/p>\n

\"installvum60vcsa15\"<\/p>\n

Accept the EULA then click Next<\/strong>.<\/p>\n

\"installvum60vcsa16\"<\/p>\n

Don't enable\u00a0Download updates from default sources immediately after installation<\/strong>\u00a0option then click Next<\/strong>.<\/p>\n

\"installvum60vcsa17\"<\/p>\n

Type the VCSA FQDN and the Username<\/strong> and Password<\/strong>. Click Next<\/strong> when done.<\/p>\n

\"installvum60vcsa18\"<\/p>\n

Select the Data Source Name<\/strong> previously created then click Next<\/strong>.<\/p>\n

\"installvum60vcsa19\"<\/p>\n

Click Next<\/strong> to proceed.<\/p>\n

\"installvum60vcsa20\"<\/p>\n

From the drop-down menu, select the FQDN name<\/strong> of the vSphere Update Manager then click Next<\/strong>.<\/p>\n

\"installvum60vcsa21\"<\/p>\n

Configure if required the location for downloading<\/strong> patches and click Next\u00a0<\/strong>to continue.<\/p>\n

\"installvum60vcsa22\"<\/p>\n

Click Install<\/strong> to begin the installation.<\/p>\n

\"installvum60vcsa23\"<\/p>\n

Update Manager is being installed in the server.<\/p>\n

\"installvum60vcsa24\"<\/p>\n

When completed, click Finish<\/strong> to exit the Wizard.<\/p>\n

\"installvum60vcsa25\"<\/p>\n

If you need to install also the vSphere Update Manager Download Service, select Download Services<\/strong> option and click on Install<\/strong> button.<\/p>\n

\"installvum60vcsa26\"<\/p>\n

If you are installing the Download Service in the same server<\/strong> where VUM is installed, you receive this error since Download Service and VUM can't co-exist on the same system<\/strong>. An additional Windows Server<\/strong> is then required.<\/p>\n

\"installvum60vcsa27\"<\/p>\n

When the vSphere Update Manager server installation is complete, you need to access the service and configure the plugin. Part 2<\/a> will cover the installation of the vSphere Client<\/strong> and the VUM plugin<\/strong> to manage the VMware updates.<\/p>\n

\"firma\"<\/p>\n","protected":false},"excerpt":{"rendered":"

In the new VCSA 6.0 (vCenter Server Appliance), vSphere Update Manager (VUM) is the only \"Windows\" component required by vSphere 6.0. To run the VUM service when the VCSA is used as vCenter Server, you need a Windows server and a SQL database. For small scale deployment (up to five hosts) SQL Express 2012 is bundled in the vCenter Installer but for bigger environments SQL Server and Oracle are the preferred platforms to use.<\/p>\n","protected":false},"author":3,"featured_media":13278,"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":[1551,700,1579],"class_list":["post-13305","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-vsphere-en","tag-vcsa","tag-vsphere-en","tag-vum","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/13305","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=13305"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/13305\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/13278"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=13305"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=13305"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=13305"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}