I have a Win10 PC and a Win10 laptop that I use VMware Horizon Client (v4.8) to connect work's VDI server over the past year. Today, on my PC the VMware client is reporting a SSL error when I click to connect to the VDI server (error happens before any auth prompts). However, my laptop doesn't have the issue and is able to connect through ok. Both PC and laptop are on the same home network.

I've had a look at the logs but I don't understand most of it so hoping someone can point out what could be wrong.

Things I have tried on my PC:

• Change SSL confguration to "Do not verify server identity certificates"
• Uninstalled VMware Horizon Client - reboot - reinstall with latest v4.8 installer from vmware.com - reboot

This is the extract from vmware-horizon-viewclient-2018-06-25-160039.txt attached (server name and IP replaced).

I tested connecting to any valid domain name not running vmware infrastructure and appears to get the same SSL error so it just appears the SSL error just a general error if there is no SSL handshake? I can confirm my work's VDI server is working though because as I mentioned I can connect to it from my Win10 laptop fine.

What else can I do?

I have a warning on my cluster

vsphere Ha failoveri n progress. alarm has been on for a few days. any idea why it does not clear?

for hybrid configuration

if each host use one disk group with sata ssd + sas hdd and perform different I/O workload profile tests,

what applications match the specified workloads? is there any document with such details?

EX: "block size 8KB + Read 0%/ + 0% random" workload is suitable for web server?video streaming? system paging?

"block size 8KB + Read 70%/ + 100% random" workload is suitable for database?mail server?or...?

is vSAN different from traditional storage in this part?

thanks!

I have a Lenovo computer with Intel i5 and windows10  When I tried to establish a Linux system through VMware, an error message came up with " this host support Intel-vt-x, but Intel VT-x is disabled". I have tried to reboot with the vt.iso attachment in a USB drive, but it does not work either. I have powered cycle the computer too. I cannot find BIOS/firmware settings my computer. Any idea about how to solve this problem?

I have a vSphere environment.

Build a windows Server Failover  Clustering in the vSphere environment.

But validate configuration is failed.

Storage is failed.

Validate SCSI-3 Persistent Reservation

Node ClusterSvr01.itpro.local successfully issued call to Persistent Reservation RESERVE for Test Disk 0 which is currently reserved by node ClusterSvr02.itpro.local. This call is expected to fail.

Test Disk 0 does not provide Persistent Reservations support for the mechanisms used by failover clusters. Some storage devices require specific firmware versions or settings to function properly with failover clusters. Please contact your storage administrator or storage vendor to check the configuration of the storage to allow it to function properly with failover clusters.

Test failed. Please look at the test log for more information.

ClusterSvr01.itpro.local and ClusterSvr01.itpro.local is cluster Server Name.

what should I do?

Hello,

I have NSX manager version 6.3.3 Build 6276725 deployed with 3 controllers.In Networking & Security > Installation >Management all the controllers status is Disconnected. According to KB2151719 it's known bug. I followed the procedures as in the article, however when run API call of the step 3 I'm getting status code 200 but the body of the reply is the following:

# of controllers: 3

------------------------------------------------------------------

Fix controller: {Controller: 10.60.1.223 [controller-9], apiUser: admin }

  live prompt: <Password: >, SEND reply: <??>

  live prompt: <Password: >, SEND reply: <??>

  live prompt: <Password: >, SEND reply: <??>

  live prompt: <Password: >, SEND reply: <??>

  live prompt: <Password: >, SEND reply: <??>

ERROR in connect: SSH_MSG_DISCONNECT: 2 Too many authentication failures

script failed: com.jcraft.jsch.JSchException: SSH_MSG_DISCONNECT: 2 Too many authentication failures

------------------------------------------------------------------

Fix controller: {Controller: 10.60.1.222 [controller-8], apiUser: admin }

  live prompt: <Password: >, SEND reply: <??>

  live prompt: <Password: >, SEND reply: <??>

  live prompt: <Password: >, SEND reply: <??>

  live prompt: <Password: >, SEND reply: <??>

  live prompt: <Password: >, SEND reply: <??>

ERROR in connect: SSH_MSG_DISCONNECT: 2 Too many authentication failures

script failed: com.jcraft.jsch.JSchException: SSH_MSG_DISCONNECT: 2 Too many authentication failures

------------------------------------------------------------------

Fix controller: {Controller: 10.60.1.221 [controller-7], apiUser: admin }

  live prompt: <Password: >, SEND reply: <??>

  live prompt: <Password: >, SEND reply: <??>

  live prompt: <Password: >, SEND reply: <??>

  live prompt: <Password: >, SEND reply: <??>

  live prompt: <Password: >, SEND reply: <??>

ERROR in connect: SSH_MSG_DISCONNECT: 2 Too many authentication failures

script failed: com.jcraft.jsch.JSchException: SSH_MSG_DISCONNECT: 2 Too many authentication failures

Patch script completed successfully.

And all the controllers remain in disconnected status. Any ideas what could be causing the issue? What credentials are used when NSX Manager tries to connect to controllers and where can it be verified?

Thanks

На хосте стоит всего одна ВМ (называется VMfrac, WS2003x64, контроллер домена). Она не стартует автоматически после перезагрузки esxi, приходится после пропадания электричества стартовать эту ВМ вручную, ошибок при запуске вручную не выдаёт. Эта ВМ находится в Automatic Startup. Поставил для эксперимента ещё одну ВМ на этот хост, она благополучно автоматически стартует.

Хост ESXi-6.0.0-Update2-3620759-HPE на HP ML350 Gen5

Пробовал обновить VMware Tools - с 10.0.6 до 10.0.12 (последняя для WS2003)

Пробовал удалять из проблемной ВМ USB-контроллер и ключ 1С

Сравнивал настройки с другой ВМ WS2003 на другом хосте с таким-же esxi - одинаковы. Настройки смотрел и через vSphere Client и через веб-клиент.

Проблемная ВМ ставилась когда-то на esxi - 4.1, потом переехала на хост с esxi - 6.0, там получила HW version 11, оставила другой ВМ-ке два из четырёх своих дисков и вернулась на старый хост (на старом хосте к тому времени esxi - 4.1 был грохнут и поставлен esxi - 6.0)

Прилагаю vmkernel.log сразу после запуска хоста, когда вторая ВМ уже автоматически загрузилась, а проблемная ВМ - нет. И снимок экрана настроек запуска ВМ-ок.

Вопрос: что делать?

I wish there was more information/logs to look through provide, but here is all I have.  I go to client registration, and enter the automation userid and password.  I can confirm this part authenticates successfully, as using bad data results in an error.

The next screen is where I enter the client id and secret.  I have been using the same info as above - user id for client id, and password for secret.  But after I submit I recieve the error in the title.  Any assistance on how I can begin to troubleshoot would be greatly appreciated.

Unfortunately, we still could not solve the production-preventing problem. Various activities, such as Switch VAAI off and on, update HBA driver according to VMware recommendation, ACT Heartbeat off and on, etc. have so far unfortunately not brought any success.

The last piece of knowledge we've learned is that if you recompose to two disks in the View 7.4 / ESX 6.5 environment, one LUN gets a high write rate (about 120mb / s), while the second LUN gets 13mb / s dulls itself and this value also does not increase when the performant LUN has finished writing.

We have now determined comparative values in the "old" environment under View 6.2.3 / ESX 5.5 and were able to detect a parallel write rate of approx. 50 mb / s in two recorders at the same time. Therefore, the replica files are also finished relatively at the same time and we do not get a timeout.

Can you explain the phenomenon of different writing rates? Can it be that the View Composer is responsible for this and there is the problem to look for? The assumption comes from the fact that VAAI is used in a clone of a machine and here View is out, whereas in a recompose no VAAI is used. Why?

Sorry for my bed english

Hello All,

Could anyone please tell me what is JFrog Artifactory Pro? What was its significance in earlier version of vRA and Code stream? What was it used for? Why was it removed in new versions? What is the new solution and why is the new solution better?

I am keenly looking for the replies and answers. I am curious on this topic.

Any knowledge sharing will be appreciated.

Hi,

  I am trying to find out what ports need to be opened for the following scenario

Client PC Using web client on vlan1

Vcenter 5.5 Server on vlan2

esx server on vlan3

All Vlans have firewalls between them, all ports closed (except 80/443 from the client pc to the vcenter server)

I am trying to use the web client to deploy an ova (stored on the client pc) using Vcenter to the esx server.

Can anyone enlighten me into what ports need to be opened between each of the three clans.

Thanks

Brett

Hello,

I am a bit new to vSphere, is there a way to download just the evaluation license without the ISO installations?

I already have VM servers and just need to check how this works?

Thanks,

Richard

Hello all.

One of my lab devices decided to dislike the Intel dual port NIC out of the blue after it was restarted. The card is listed on the HCG, supported via both e1000e and ne1000 VM modules, and is listed under lspci. And yet, ESXi 6.7 tells me no supported NIC cards are available. The NIC works on another system, so it is not a hardware fault. Both ports are connected and green, with their matching switch ports up.

VMWare ESXi 6.7.0 (VMKernel Release Build 8169922)

My NIC is exactly this - VMware Compatibility Guide - I/O Device Search

[root@vhost01:~] lspci -v | grep -A1 -i ethernet

0000:01:00.0 Ethernet controller Network controller: Intel Corporation 82571EB Gigabit Ethernet Controller [vmnic0]

Class 0200: 8086:105e

--

0000:01:00.1 Ethernet controller Network controller: Intel Corporation 82571EB Gigabit Ethernet Controller [vmnic1]

Class 0200: 8086:105e

[root@vhost01:~] vmkload_mod e1000e

Module e1000e loaded successfully

[root@vhost01:~] dmesg | grep -i e1000

2018-06-25T07:00:30:841Z cpu1:2100918)Loading module e1000e ...

2018-06-25T07:00:30:841Z cpu1:2100918)Elf: 2101: module e1000e has license GPL

2018-06-25T07:00:30:843Z cpu1:2100918)module heap vmklnx_e1000e: Initial heap size = 102400, max heap size = 9666560

2018-06-25T07:00:30:843Z cpu1:2100918)module mempool vmklnx_e1000e_skb: creation succeeded. initial size = 524288, max size = 23068672

2018-06-25T07:00:30:843Z cpu1:2100918)module heap vmklnx_e1000e: using memType 0

2018-06-25T07:00:30:843Z cpu1:2100918)module heap vmklnx_e1000e: creation succeeded. id = 0x4304aa6a0000

2018-06-25T07:00:30:843Z cpu1:2100918)PCI: driver e1000e is looking for devices

2018-06-25T07:00:30:843Z cpu1:2100918)PCIL driver e1000e claimed 0 device

2018-06-25T07:00:30:843Z cpu1:2100918)Mod: 4962: Initialization of e1000e succeeded with module ID 4193.

2018-06-25T07:00:30:843Z cpu1:2100918)e1000e loaded successfully

[root@vhost01:~] esxcfg-nics -l

Name PCI Driver Link Speed Duplex MAC Address MTU Description

[root@vhost01:~] _

Any hints? Thanks!

Hello everyone,

For few days now I have been fighting with vRA 7.4 deployment using vRS Lifecycle Manager 1.2, althought it seems to be a great tool !

What I have one so far:

     - I have deployed a Windows Server 2016 VM called "vra-iaas"

     - I added the necessary DNS entries for both vRA and vRA-IaaS within my lab

     - I did set up vRSLCM as told by the VMware Documentation

     - I created a new environment with vRA deployment only, went through all the settings config steps and passed the Pre-Check at 100%

After I submitted the creation request, everything wend well.

Then I faced an error during the deployment task changing its state from "in progress" to "Failed":

Apparently something went wrong with the vra-iaas certificate. Since I am not really sure about how certificates are used with vRS products, I am stuck at this point.

I don't know what I am missing and I don't know where to look ... Please someone help me !

Many thanks !

Hello,

I have a question, I need to run a script inside the machine with the parameter given by the user in the field, can you guide me to the right path (vRA 7.3)?

Regards,

Piotr

Hi,

I hope anybody can help me. We´re using vRA/vRO 7.3 and 7.4 and the newest AD plugin. We use the AD plugin to find users in AD. But very often we´re facing the error java.lang.NullPointerException which is breaking our workflow. Any idea is welcome.

Hello,

I deployed at a customer offices several Dell R740 servers (laste BIOS) with vSpehre 6.5U1 and vSAN.

I'm using Intel X710 DA 10Gb (2 ports) NIC cards.

My client would like to use SR IOV for somes VMs. These NICS support SR IOV (with i40e and i40en drivers). It's the first time I have to use SR IOV.

I activated "SR-IOV Global" in the Dell BIOS servers and I uses the "esxcli system module parameters set -m NIC_Driver_Module -p "max_vfs=n"" commands on esxi hosts.

I tried with a i40e driver and the i40en drivers.

But after the reboot vSphere still tell me the cards are not supported for SR IOV.

I did the same on a VXrail cluster (vSphere 6.0) with x540 NIC Intel it works well...

Do you have any ideas ?

Thanks for your help

Vincent

From vcenter 6.0 4541947 vCenter Server 6.0 Update 2a

To vcenter 6.0 7037394 vCenter Server 6.0 Update 3c

uninstall.log

2017-02-18 02:23:30,903: CM search failed. ProductId=com.vmware.cis, TypeId=cs.identity

2017-02-18 02:23:30,903: Error connecting to CM: {

    "resolution": {

        "id": "install.default.failure.resolution", 

        "localized": "This is an unrecoverable error, please retry install. If you run into this error again, please collect a support bundle and open a support request.", 

        "translatable": "This is an unrecoverable error, please retry install. If you run into this error again, please collect a support bundle and open a support request."

    }, 

    "detail": [

        {

            "args": [

                "CM search failed. ProductId=com.vmware.cis, TypeId=cs.identity:503 Service Unavailable (Failed to connect to endpoint: [class Vmacore::Http::NamedPipeServiceSpec:00000000018056F0] _serverNamespace = / _isRedirect = false _pipeName =\\\\.\\pipe\\vmware-vpxd-webserver-pipe)"

            ], 

            "id": "install.ciscommon.internal.error", 

            "localized": "Encountered an internal error.\n\nCM search failed. ProductId=com.vmware.cis, TypeId=cs.identity:503 Service Unavailable (Failed to connect to endpoint: [class Vmacore::Http::NamedPipeServiceSpec:00000000018056F0] _serverNamespace = / _isRedirect = false _pipeName =\\\\.\\pipe\\vmware-vpxd-webserver-pipe)", 

            "translatable": "Encountered an internal error.\n\n%(0)s"

        }

    ], 

    "componentKey": null, 

    "problemId": null

}

2017-02-18 02:23:30,903: Failed to unregister node from CM. Error {

    "resolution": {

        "id": "install.default.failure.resolution", 

        "localized": "This is an unrecoverable error, please retry install. If you run into this error again, please collect a support bundle and open a support request.", 

        "translatable": "This is an unrecoverable error, please retry install. If you run into this error again, please collect a support bundle and open a support request."

    }, 

    "detail": [

        {

============================================================================================

soluser_firstboot.py_9276

2018-05-19T05:17:43.701Z   Invoked command: ['C:\\Program Files\\VMware\\vCenter Server\\vmafdd\\vecs-cli.exe', 'store', 'list']

2018-05-19T05:17:43.701Z   RC = 1021

Stdout = 

Stderr = vecs-cli failed. Error 1021: Cannot connect to vmafd service. 

2018-05-19T05:17:43.701Z   Error deleting solution user machine. Error {

    "resolution": null, 

    "detail": [

        {

            "args": [

                "Command: ['C:\\\\Program Files\\\\VMware\\\\vCenter Server\\\\vmafdd\\\\vecs-cli.exe', 'store', 'list']\nStderr: vecs-cli failed. Error 1021: Cannot connect to vmafd service. \r\n"

            ], 

            "id": "install.ciscommon.command.errinvoke", 

            "localized": "An error occurred while invoking external command : 'Command: ['C:\\\\Program Files\\\\VMware\\\\vCenter Server\\\\vmafdd\\\\vecs-cli.exe', 'store', 'list']\nStderr: vecs-cli failed. Error 1021: Cannot connect to vmafd service. \r\n'", 

            "translatable": "An error occurred while invoking external command : '%(0)s'"

        }, 

        {

            "id": "install.ciscommon.vecs.list.stores", 

            "localized": "Error in generating list of VECS store instances.", 

            "translatable": "Error in generating list of VECS store instances."

        }

    ], 

    "componentKey": null, 

    "problemId": null

=============================================================================================    

vmafd-firstboot.py_9276_stderr.log

2018-05-19T05:18:31.873Z   WARNING Value for install-parameter vmdir.password is empty

2018-05-19T05:18:31.873Z   WARNING Value for install-parameter machine.cert.dir is empty

2018-05-19T05:18:31.873Z   WARNING Value for install-parameter upgrade.import.directory is empty

2018-05-19T05:18:31.873Z   WARNING Value for install-parameter upgrade.source.platform is empty

2018-05-19T05:18:31.873Z   WARNING Value for install-parameter upgrade.import.directory is empty

2018-05-19T05:18:31.873Z   WARNING Value for install-parameter vmdir.password is empty

2018-05-19T05:18:31.889Z   WARNING Value for install-parameter vmdir.password is empty

2018-05-19T05:18:31.889Z   Exception: Traceback (most recent call last):

  File "C:\Program Files\VMware\vCenter Server\firstboot\vmafd-firstboot.py", line 121, in main

    controller.uninstall()

  File "C:\Program Files\VMware\vCenter Server\firstboot\vmafd-firstboot.py", line 71, in uninstall

    service.uninstall()

  File "C:\Program Files\VMware\vCenter Server\firstboot\identityinstall\vmcaInstall.py", line 191, in uninstall

    self.utils.stop_service(self.__VMCA_SERVICE_NAME, self.__VMCA_COMPONENT_NAME)

  File "C:\Program Files\VMware\vCenter Server\firstboot\identityinstall\WindowsUtils.py", line 92, in stop_service

    raise ServiceStopException(serviceName)

ServiceStopException: {

    "resolution": null, 

    "detail": [

        {

            "args": [

                "VMWareCertificateService"

            ], 

            "id": "install.ciscommon.service.failstop", 

            "localized": "An error occurred while stopping service 'VMWareCertificateService'", 

            "translatable": "An error occurred while stopping service '%(0)s'"

        }

    ], 

    "componentKey": null, 

    "problemId": null

}

vminst.log           

2018-05-18 23:17:31.236-06:00| vcsInstUtil-7037391| I: ParseStatusFile: STATUS: 87%: "Stopping VMware Single Sign-On User Creation..."

2018-05-18 23:17:31.236-06:00| vcsInstUtil-7037391| I: ParseStatusFile: Calling callback with 83 -> 87 "Stopping VMware Single Sign-On User Creation..."

2018-05-18 23:17:31.236-06:00| vcsInstUtil-7037391| I: Entering function: UpdatePkgMgrProgressFromStatusFile

2018-05-18 23:17:31.236-06:00| vcsInstUtil-7037391| I: ProcessMsiMsg: ACTIONDATA reporting "Stopping VMware Single Sign-On User Creation..."

2018-05-18 23:17:31.252-06:00| vcsInstUtil-7037391| I: Leaving function: UpdatePkgMgrProgressFromStatusFile

2018-05-18 23:17:31.252-06:00| vcsInstUtil-7037391| I: Leaving function: ParseStatusFile

2018-05-18 23:18:31.343-06:00| vcsInstUtil-7037391| I: Entering function: ParseStatusFile

2018-05-18 23:18:31.343-06:00| vcsInstUtil-7037391| I: ParseStatusFile: STATUS: 91%: "Stopping VMware Authentication Framework..."

2018-05-18 23:18:31.343-06:00| vcsInstUtil-7037391| I: ParseStatusFile: Calling callback with 87 -> 91 "Stopping VMware Authentication Framework..."

2018-05-18 23:18:31.343-06:00| vcsInstUtil-7037391| I: Entering function: UpdatePkgMgrProgressFromStatusFile

2018-05-18 23:18:31.343-06:00| vcsInstUtil-7037391| I: ProcessMsiMsg: ACTIONDATA reporting "Stopping VMware Authentication Framework..."

2018-05-18 23:18:31.359-06:00| vcsInstUtil-7037391| I: Leaving function: UpdatePkgMgrProgressFromStatusFile

2018-05-18 23:18:31.359-06:00| vcsInstUtil-7037391| I: Leaving function: ParseStatusFile

2018-05-18 23:18:31.998-06:00| vcsInstUtil-7037391| I: Entering function: ParseStatusFile

2018-05-18 23:18:32.014-06:00| vcsInstUtil-7037391| I: ParseStatusFile: curr error msg: "An error occurred while stopping service 'VMWareCertificateService'"

2018-05-18 23:18:32.014-06:00| vcsInstUtil-7037391| E: ParseStatusFile: Displaying error message for " ": "An error occurred while stopping service 'VMWareCertificateService'"

2018-05-18 23:18:49.408-06:00| vcsInstUtil-7037391| I: Entering function: ShowMessageQueue

2018-05-18 23:18:49.408-06:00| vcsInstUtil-7037391| I: Leaving function: ShowMessageQueue

2018-05-18 23:18:49.408-06:00| vcsInstUtil-7037391| I: Entering function: ShowMessageQueue

2018-05-18 23:18:49.408-06:00| vcsInstUtil-7037391| I: Leaving function: ShowMessageQueue

2018-05-18 23:18:49.408-06:00| vcsInstUtil-7037391| I: ParseStatusFile: got error or success

2018-05-18 23:18:49.423-06:00| vcsInstUtil-7037391| I: ParseStatusFile: keeping completed status file: C:\ProgramData\VMware\vCenterServer\logs\uninstall\fbInstall.json

2018-05-18 23:18:49.423-06:00| vcsInstUtil-7037391| I: Leaving function: ParseStatusFile

2018-05-18 23:18:49.423-06:00| vcsInstUtil-7037391| I: MonitorStatusFile: Parse callback gave final result: 0

2018-05-18 23:18:49.423-06:00| vcsInstUtil-7037391| I: MonitorStatusFile: called parse callback 10 times

2018-05-18 23:18:49.423-06:00| vcsInstUtil-7037391| I: MonitorStatusFile: Process still hasn't terminated, waiting

2018-05-18 23:42:03.177-06:00| vcsInstUtil-7037391| I: MonitorStatusFile: Wait on process has completed: 0

2018-05-18 23:42:03.177-06:00| vcsInstUtil-7037391| I: MonitorStatusFile: Process's job tree still hasn't terminated, waiting

2018-05-18 23:42:03.177-06:00| vcsInstUtil-7037391| I: MonitorStatusFile: Wait on process's job tree has completed: 0

2018-05-18 23:42:03.177-06:00| vcsInstUtil-7037391| I: Leaving function: MonitorStatusFile

2018-05-18 23:42:03.177-06:00| vcsInstUtil-7037391| E: LaunchProcAndMonitorStatus: Failure detected while monitoring status file

2018-05-18 23:42:03.177-06:00| vcsInstUtil-7037391| E: LaunchProcAndMonitorStatus: Job still alive, terminating

2018-05-18 23:42:03.177-06:00| vcsInstUtil-7037391| I: Leaving function: LaunchProcAndMonitorStatus

2018-05-18 23:42:03.177-06:00| vcsInstUtil-7037391| I: Leaving function: LaunchProcAndMonitorCommonStatusFile

2018-05-18 23:42:03.177-06:00| vcsInstUtil-7037391| E: RunFirstLastUpdateboot: Failed to run boot script: "C:\Windows\system32\cmd.exe /S /C ""C:\Program Files\VMware\vCenter Server\bin\run-uninstall-scripts.bat" --operation ROLLBACK""

2018-05-18 23:42:03.177-06:00| vcsInstUtil-7037391| I: Leaving function: VM_RunLastBoot

2018-05-18 23:42:03.520-06:00| vcsInstUtil-7037391| E: wWinMain: MSI result of install of "Z:\vCenter-Server\Packages\vcsservicemanager.msi" may have failed: 1603 (0x00000643)

2018-05-18 23:42:03.520-06:00| vcsInstUtil-7037391| E: LaunchPkgMgr: Operation on vcsservicemanager.msi appears to have failed: 1603 (0x00000643)

2018-05-18 23:42:03.520-06:00| vcsInstUtil-7037391| I: PitCA_MessageBox: Displaying message: "Installation of component VCSServiceManager failed with error code '1603'. Check the logs for more details."

2018-05-18 23:42:20.306-06:00| vcsInstUtil-7037391| I: LaunchPkgMgr: Telling child to revert transaction

2018-05-18 23:42:20.306-06:00| vcsInstUtil-7037391| I: InstallStatus_SetStage: install stage: install-packages / revert-transaction

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: EndTransaction: Chain transaction 1 rollback result 3010

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: wWinMain: We've been told our work is done, terminating

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: wWinMain: Releasing install mutex

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: Leaving function: wWinMain

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: LaunchPkgMgr: DLL got exe done: 3010

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: LaunchPkgMgr: disconnected pipe

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: LaunchPkgMgr: Starting services on update rollback.

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: Entering function: VM_StartVcsServices

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: PitCA_RefreshVMEnvironmentVars: Updating PATH environment variable.

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: PitCA_RefreshVMEnvironmentVars: Var: Path, Val: C:\Program Files (x86)\Java\jre7\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\MIT\Kerberos\bin;D:\Program Files\VMware\vCenter Server\openSSL;C:\Program Files\VMware\vCenter Server\openSSL

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: StartStopVCSServices: Running command '"C:\Windows\system32\cmd.exe" /S /C ""C:\Program Files\VMware\vCenter Server\bin\service-control.bat"" --start --all'...

2018-05-18 23:46:04.104-06:00| vcsInstUtil-7037391| I: StartStopVCSServices: Waiting for VC services to start...

2018-05-18 23:46:09.002-06:00| vcsInstUtil-7037391| E: StartStopVCSServices: Unable to start VC services

2018-05-18 23:46:09.002-06:00| vcsInstUtil-7037391| I: Leaving function: VM_StartVcsServices

2018-05-18 23:46:09.049-06:00| vcsInstUtil-7037391| E: LaunchPkgMgr: Overall operation has failed

Hi,

How vCenter countes the total processors in the cluster ? The cluster in the image has 3 nodes each with 56 logical processors

Thank you