Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Configuring vRealize Configuration Manager from HTTP to HTTPS (54756)

Last Updated: 4/24/2018Categories: How toTotal Views: 2835Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

vRealize Configuration Manager UI is configured to use HTTP and you would like to use HTTPS.

vRealize Configuration Manager Reports are configured to use HTTP and you would like to use HTTPS.

Resolution

Below are instructions to assist you with changing the VCM database to facilitate VCM in using https as well as the reporting.

Open SQL Server Management Studio and connect to your database server.

Click New Query, and select your VCM database.

In the query field, type the following and execute:

select * from ecm_sysdat_configuration_values

where configuration_name like '%iis%'

The fields that need to be updated are 'IIS Server', 'IIS HTTP' and iis_http_port_binding.  To update them, replace the query field with the following and execute:

update ecm_sysdat_configuration_values

set configuration_value=hostname

where configuration_id is configuration_id

Note: Replace hostname with the VCM Server name in FQDN format, and configuration_id with the configuration_id next to IIS Server.

Repeat step 4 for the other fields by replacing configuration_id for IIS Server, IIS HTTP and/or iis_http_port_binding.

In Windows, open IIS Manager and navigate to Server > Sites > Default Web Site.

Note: Replace Server with the name of your VCM server.

Double click SSL Settings and check Require SSL.

To allow users to connect without supplying their own certificate, click Ignore client certificates.

To allow a user to supply their own certificate, use Accept client certificates.

Click Default Web Site, then in the right pane, click Bindings.

Click Add and configure a Type of https, IP address of All Unassigned, Port of 443, and the desired SSL certificate.

In the Windows start menu, run rsconfigtool and connect to your VCM server.

Click Report Manager URL, then click Advanced.

Under Multiple SSL Identities for Report Manager, click Add.

Set IP Address to (All IPv4), SSL Port to 443, and select the desired Certificate, then click OK.

Click OK in the Advanced Multiple Web Site Configuration window.

Open drive:\Program Files (x86)\VMware\VCM\WebConsole\Web.config in a text editor and update the reporting URLs from HTTP to HTTPS.

Example: <value>https://vcmcollector:443/ReportServer/ReportService2005.asmx</value>

Save and close the file.

Restart the IIS Service.

Restart the Reporting Service in the RSConfigTool.

Verify by testing the new HTTPS URL and run a report to ensure it is also showing HTTPS.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vRealize Configuration Manager

Related Versions:

VMware vRealize Configuration Manager 5.x

Take Our Survey

Support Assistant