build 7bbbddf7 | content blog-content@c8490fa · 338 posts | profiles 20 · corpus 267 | 0 skipped | | format
apiVersion: soultec.ch/v1kind: Postmetadata: name: health-check-neuer-standard-bei-advanced-settings locale: en labels: author: dario-doerflinger series: announcement vendor/vmware: 0.88 annotations: source: blog-content/posts/en/health-check-neuer-standard-bei-advanced-settings.md route: /en/insights/health-check-neuer-standard-bei-advanced-settings/ schema: /nerd/schema/posts.json markdown: /en/insights/health-check-neuer-standard-bei-advanced-settings.mdspec: title: "Health check: a new default in the advanced settings" date: 2024-01-03 author: dario-doerflinger locale: en summary: >- We run a lot of health checks. One advanced setting changed its default in vSphere 8, and it turned up in our reports as a deviation that was not one. vendors: [vmware] series: announcement hero: /blog-assets/health-check-neuer-standard-bei-advanced-settings/hero.webp migrated: 2026-08-24 translationReviewed: false draft: false sections: - body: | We run [health checks](https://soultec.ch/services/consulting/health-check/) for our customers a lot. Our [experts](https://soultec.ch/member) go through the components of the IT infrastructure in detail and then assess them against our good and common practices, the vendors' best practices and the accumulated experience of the team. What comes out of it is a report with a catalogue of measures, which we present to the customer. - heading:

The tools we use for VMware infrastructure

body: | We use several tools to read out the data of a VMware infrastructure. - RVTools - vChecker - VMware Health Analyzer ### RVTools [This application](https://www.robware.net/rvtools/download/) runs on Windows and reads the inventory of vCenter Servers. What makes it stand out is how fast it processes a large amount of data while taking very few resources. ### vChecker Based on the GitHub project vCheck, we created our own fork a long time ago and have extended and rewritten a good number of modules. We publish our work in [this GitHub fork](https://github.com/virtualFrog/vChecker) as it goes along. ### VMware Health Analyzer As a [VMware partner](https://soultec.ch/solutions/vmware/) we get to use the VMware Health Analyzer (vHA), which is partner-only. It reads data from VMware solutions such as vSphere and Horizon and compares it against VMware's catalogue of best practices. This is where we usually get the most false positives, and where we filter the results with our own experience so that the customer only sees the deviations that matter. #### RemoteDisplay.maxConnections Among the many things vHA assesses are the advanced settings, on ESXi and on VM level. One of them, from the security area, is "RemoteDisplay.maxConnections" on the VMs. It sets how many simultaneous connections to a VM console can be opened from the vSphere Client. Out of the box this is not limited, and the recommendation is to set it to 1 or 2. Up to vSphere 7 the default was 0. From vSphere 8.0 it is -1. As a rule -1 means a setting is disabled, which in this case makes more sense than the previous 0. Because of that change, our recent health checks reported -1 as a deviation from the default, which on closer analysis turned out to be another false positive. - heading:

Next steps

body: | If a health check interests you and you want to know where your infrastructure stands, do not hesitate to [get in touch](https://soultec.ch/contact-us/). Our experts are here for you.status: corpus: 267
{ "apiVersion": "soultec.ch/v1", "kind": "Post", "metadata": { "name": "health-check-neuer-standard-bei-advanced-settings", "locale": "en", "labels": { "author": "dario-doerflinger", "series": "announcement", "vendor/vmware": "0.88" }, "annotations": { "source": "blog-content/posts/en/health-check-neuer-standard-bei-advanced-settings.md", "route": "/en/insights/health-check-neuer-standard-bei-advanced-settings/", "schema": "/nerd/schema/posts.json", "markdown": "/en/insights/health-check-neuer-standard-bei-advanced-settings.md" } }, "spec": { "title": "Health check: a new default in the advanced settings", "date": "2024-01-03", "author": "dario-doerflinger", "locale": "en", "summary": "We run a lot of health checks. One advanced setting changed its default in vSphere 8, and it turned up in our reports as a deviation that was not one.", "vendors": [ "vmware" ], "series": "announcement", "hero": "/blog-assets/health-check-neuer-standard-bei-advanced-settings/hero.webp", "migrated": "2026-08-24", "translationReviewed": false, "draft": false }, "sections": [ { "body": "We run [health checks](https://soultec.ch/services/consulting/health-check/) for our customers a lot. Our [experts](https://soultec.ch/member) go through the components of the IT infrastructure in detail and then assess them against our good and common practices, the vendors' best practices and the accumulated experience of the team. What comes out of it is a report with a catalogue of measures, which we present to the customer." }, { "heading": "

The tools we use for VMware infrastructure

",
"body": "We use several tools to read out the data of a VMware infrastructure.\n\n- RVTools\n- vChecker\n- VMware Health Analyzer\n\n### RVTools\n\n[This application](https://www.robware.net/rvtools/download/) runs on Windows and reads the inventory of vCenter Servers. What makes it stand out is how fast it processes a large amount of data while taking very few resources.\n\n### vChecker\n\nBased on the GitHub project vCheck, we created our own fork a long time ago and have extended and rewritten a good number of modules. We publish our work in [this GitHub fork](https://github.com/virtualFrog/vChecker) as it goes along.\n\n### VMware Health Analyzer\n\nAs a [VMware partner](https://soultec.ch/solutions/vmware/) we get to use the VMware Health Analyzer (vHA), which is partner-only. It reads data from VMware solutions such as vSphere and Horizon and compares it against VMware's catalogue of best practices. This is where we usually get the most false positives, and where we filter the results with our own experience so that the customer only sees the deviations that matter.\n\n#### RemoteDisplay.maxConnections\n\nAmong the many things vHA assesses are the advanced settings, on ESXi and on VM level. One of them, from the security area, is \"RemoteDisplay.maxConnections\" on the VMs. It sets how many simultaneous connections to a VM console can be opened from the vSphere Client. Out of the box this is not limited, and the recommendation is to set it to 1 or 2.\n\nUp to vSphere 7 the default was 0. From vSphere 8.0 it is -1. As a rule -1 means a setting is disabled, which in this case makes more sense than the previous 0. Because of that change, our recent health checks reported -1 as a deviation from the default, which on closer analysis turned out to be another false positive." }, { "heading": "

Next steps

",
"body": "If a health check interests you and you want to know where your infrastructure stands, do not hesitate to [get in touch](https://soultec.ch/contact-us/). Our experts are here for you." } ], "status": { "corpus": 267 }}
apiVersion = "soultec.ch/v1"kind = "Post"[metadata]name = "health-check-neuer-standard-bei-advanced-settings"locale = "en"[metadata.labels]author = "dario-doerflinger"series = "announcement""vendor/vmware" = "0.88"[metadata.annotations]source = "blog-content/posts/en/health-check-neuer-standard-bei-advanced-settings.md"route = "/en/insights/health-check-neuer-standard-bei-advanced-settings/"schema = "/nerd/schema/posts.json"markdown = "/en/insights/health-check-neuer-standard-bei-advanced-settings.md"[spec]title = "Health check: a new default in the advanced settings"date = 2024-01-03author = "dario-doerflinger"locale = "en"summary = "We run a lot of health checks. One advanced setting changed its default in vSphere 8, and it turned up in our reports as a deviation that was not one."vendors = ["vmware"]series = "announcement"hero = "/blog-assets/health-check-neuer-standard-bei-advanced-settings/hero.webp"migrated = 2026-08-24translationReviewed = falsedraft = false[[sections]]body = "We run [health checks](https://soultec.ch/services/consulting/health-check/) for our customers a lot. Our [experts](https://soultec.ch/member) go through the components of the IT infrastructure in detail and then assess them against our good and common practices, the vendors' best practices and the accumulated experience of the team. What comes out of it is a report with a catalogue of measures, which we present to the customer."[[sections]]heading = "

The tools we use for VMware infrastructure

"
body = '''We use several tools to read out the data of a VMware infrastructure.- RVTools- vChecker- VMware Health Analyzer### RVTools[This application](https://www.robware.net/rvtools/download/) runs on Windows and reads the inventory of vCenter Servers. What makes it stand out is how fast it processes a large amount of data while taking very few resources.### vCheckerBased on the GitHub project vCheck, we created our own fork a long time ago and have extended and rewritten a good number of modules. We publish our work in [this GitHub fork](https://github.com/virtualFrog/vChecker) as it goes along.### VMware Health AnalyzerAs a [VMware partner](https://soultec.ch/solutions/vmware/) we get to use the VMware Health Analyzer (vHA), which is partner-only. It reads data from VMware solutions such as vSphere and Horizon and compares it against VMware's catalogue of best practices. This is where we usually get the most false positives, and where we filter the results with our own experience so that the customer only sees the deviations that matter.#### RemoteDisplay.maxConnectionsAmong the many things vHA assesses are the advanced settings, on ESXi and on VM level. One of them, from the security area, is "RemoteDisplay.maxConnections" on the VMs. It sets how many simultaneous connections to a VM console can be opened from the vSphere Client. Out of the box this is not limited, and the recommendation is to set it to 1 or 2.Up to vSphere 7 the default was 0. From vSphere 8.0 it is -1. As a rule -1 means a setting is disabled, which in this case makes more sense than the previous 0. Because of that change, our recent health checks reported -1 as a deviation from the default, which on closer analysis turned out to be another false positive.'''[[sections]]heading = "

Next steps

"
body = "If a health check interests you and you want to know where your infrastructure stands, do not hesitate to [get in touch](https://soultec.ch/contact-us/). Our experts are here for you."[status]corpus = 267
<?xml version="1.0" encoding="UTF-8"?><manifest kind="Post"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>health-check-neuer-standard-bei-advanced-settings</name> <locale>en</locale> <labels> <author>dario-doerflinger</author> <series>announcement</series> <entry key="vendor/vmware">0.88</entry> </labels> <annotations> <source>blog-content/posts/en/health-check-neuer-standard-bei-advanced-settings.md</source> <route>/en/insights/health-check-neuer-standard-bei-advanced-settings/</route> <schema>/nerd/schema/posts.json</schema> <markdown>/en/insights/health-check-neuer-standard-bei-advanced-settings.md</markdown> </annotations> </metadata> <spec> <title>Health check: a new default in the advanced settings</title> <date>2024-01-03</date> <author>dario-doerflinger</author> <locale>en</locale> <summary>We run a lot of health checks. One advanced setting changed its default in vSphere 8, and it turned up in our reports as a deviation that was not one.</summary> <vendors> <item>vmware</item> </vendors> <series>announcement</series> <hero>/blog-assets/health-check-neuer-standard-bei-advanced-settings/hero.webp</hero> <migrated>2026-08-24</migrated> <translationReviewed>false</translationReviewed> <draft>false</draft> </spec> <sections> <section> <body>We run [health checks](https://soultec.ch/services/consulting/health-check/) for our customers a lot. Our [experts](https://soultec.ch/member) go through the components of the IT infrastructure in detail and then assess them against our good and common practices, the vendors' best practices and the accumulated experience of the team. What comes out of it is a report with a catalogue of measures, which we present to the customer.</body> </section> <section> <heading>

The tools we use for VMware infrastructure

</heading>
<body>We use several tools to read out the data of a VMware infrastructure.- RVTools- vChecker- VMware Health Analyzer### RVTools[This application](https://www.robware.net/rvtools/download/) runs on Windows and reads the inventory of vCenter Servers. What makes it stand out is how fast it processes a large amount of data while taking very few resources.### vCheckerBased on the GitHub project vCheck, we created our own fork a long time ago and have extended and rewritten a good number of modules. We publish our work in [this GitHub fork](https://github.com/virtualFrog/vChecker) as it goes along.### VMware Health AnalyzerAs a [VMware partner](https://soultec.ch/solutions/vmware/) we get to use the VMware Health Analyzer (vHA), which is partner-only. It reads data from VMware solutions such as vSphere and Horizon and compares it against VMware's catalogue of best practices. This is where we usually get the most false positives, and where we filter the results with our own experience so that the customer only sees the deviations that matter.#### RemoteDisplay.maxConnectionsAmong the many things vHA assesses are the advanced settings, on ESXi and on VM level. One of them, from the security area, is "RemoteDisplay.maxConnections" on the VMs. It sets how many simultaneous connections to a VM console can be opened from the vSphere Client. Out of the box this is not limited, and the recommendation is to set it to 1 or 2.Up to vSphere 7 the default was 0. From vSphere 8.0 it is -1. As a rule -1 means a setting is disabled, which in this case makes more sense than the previous 0. Because of that change, our recent health checks reported -1 as a deviation from the default, which on closer analysis turned out to be another false positive. </body> </section> <section> <heading>

Next steps

</heading>
<body>If a health check interests you and you want to know where your infrastructure stands, do not hesitate to [get in touch](https://soultec.ch/contact-us/). Our experts are here for you.</body> </section> </sections> <status> <corpus>267</corpus> </status></manifest>
News · 2024-01-03

Health check: a new default in the advanced settings

We run a lot of health checks. One advanced setting changed its default in vSphere 8, and it turned up in our reports as a deviation that was not one.

2024-01-03Date
Dario DörflingerAuthor
2Min read
Topics
Vendors VMware 0.88

We run health checks for our customers a lot. Our experts go through the components of the IT infrastructure in detail and then assess them against our good and common practices, the vendors’ best practices and the accumulated experience of the team. What comes out of it is a report with a catalogue of measures, which we present to the customer.

The tools we use for VMware infrastructure

We use several tools to read out the data of a VMware infrastructure.

  • RVTools
  • vChecker
  • VMware Health Analyzer

RVTools

This application runs on Windows and reads the inventory of vCenter Servers. What makes it stand out is how fast it processes a large amount of data while taking very few resources.

vChecker

Based on the GitHub project vCheck, we created our own fork a long time ago and have extended and rewritten a good number of modules. We publish our work in this GitHub fork as it goes along.

VMware Health Analyzer

As a VMware partner we get to use the VMware Health Analyzer (vHA), which is partner-only. It reads data from VMware solutions such as vSphere and Horizon and compares it against VMware’s catalogue of best practices. This is where we usually get the most false positives, and where we filter the results with our own experience so that the customer only sees the deviations that matter.

RemoteDisplay.maxConnections

Among the many things vHA assesses are the advanced settings, on ESXi and on VM level. One of them, from the security area, is “RemoteDisplay.maxConnections” on the VMs. It sets how many simultaneous connections to a VM console can be opened from the vSphere Client. Out of the box this is not limited, and the recommendation is to set it to 1 or 2.

Up to vSphere 7 the default was 0. From vSphere 8.0 it is -1. As a rule -1 means a setting is disabled, which in this case makes more sense than the previous 0. Because of that change, our recent health checks reported -1 as a deviation from the default, which on closer analysis turned out to be another false positive.

Next steps

If a health check interests you and you want to know where your infrastructure stands, do not hesitate to get in touch. Our experts are here for you.

You might also like

Too few qualifying matches. The block stays empty rather than showing one lonely card.