I'm researching new esx vsphere host servers for one place I work.

I'm planning Proliant Gen10 DL360 host servers with the 32GB SD storage for VMware, at least 8 NICs, 128 or 192 GB RAM apiece, nothing else.

Simple basic Essentials Plus 3-host setup with a basic iSCSI SAN.

I'm puzzled how to choose which processor to put in it.

We only need maybe at least 10 cores per CPU (based on current usage), not too many more so Windows Server costs don't become exce$$ively outrageou$, with 2 physical CPUs per host.

I know the Proliant Gen10s are on the HCL as follows:

Proliant Gen10 with:

Xeon Gold, Silver, Platinum, Bronze

Xeon E-2200, 4,6,8 core

How do I appropriately choose which processor to get??

I'm sure it has to be one of the Xeon metal flavors but how do I know even which ones to consider??????

I assume Gold costs the most and Bronze the least.

Thank you, Tom

Hello,

After updating ESX Host to VMware ESXi, 6.5.0, 13635690 my iSCSI Datastore is inactive and VM´s are inaccessable.
iSCSI Target is Synology RS812RP+

Any ideas?

thanks

iosman

Hello!

     I'm trying to install using a USB drive and I've found something I can't get around. I've verified that my ks.cfg file works.

Steps:
Rufus install 6.7u1

Copy ks.cfg to root

change kernelopt=runweasel  to kernelopt=ks=usb:/ks.cfg within efi\boot\boot.cfg

Doing this using the MBR setting within Rufus it works fine. I can boot and the kickstart runs without issue even within a UEFI boot

When I use the GPT option within rufus I get the following Error:

exception.HandledError: Error (See Log for more info)

cannot find kickstart file on usb with path -- /ks.cfg

I'm trying to figure out if anyone knows what i'm missing or what my issue is.

Attached:
image of errorboot.cfg in question

I'm trying to update a ESXi Host from 6.0 to 6.7U1, but I get the following error:

  Unsupported devices [4040:0100 103c:705b] [4040:0100 103c:705b] found on the host.

When I looked up the compatibility matrix, the device is supported on 6.7U1

Not quite sure where to go from here. Any pointers would be really appreciated!

PS: My vCenter (6.7U3) is installed in this host.

Hello, we're in an environment that contains two separate VMAs to manage different groups of hosts. IN trying to upgrade one of the hosts I'm follow the procedure that requires the VMware Migration Assistant. Since there are 2 VMAs that me connect to and manage from a single VCenter app, the migration assistant insists on connecting with the VMA we're not upgrading and seems to have no options to choose otherwise

Any suggestions

vSphere 7.0 Converge & Migration Process

Glad that you are seeking options to upgrade to our brand new offering vSphere 7.0

Please note that starting from vCenter 7.0, it will be only appliance based no options for integrating with any external database.

Community Support:

Did you know that VMware has a dedicated Install/Upgrade community ?

This sub community has an active user base and helps on common queries/errors during upgrade.

If you ever encounter any errors during the upgrade, feel free to post in our official install/upgrade forum - vSphere Upgrade & Install

This article focuses on migrating 6.5 Windows vCenter with external PSC to 7.0 vCenter Server

The steps are more or less same for migrating 6.7 windows to 7.0 vCenter Server

What has been deprecated in vCenter 7.0:

• No option provided for deployed external PSC
• No option provided for deploying Windows based vCenter
• No inclusion of flash based Web client

Who can upgrade:

Click here to check the vCenter Server version upgrade compatibility

Click here to get update sequence for vSphere 7.0

Licensing:

For vSphere 7.0, the existing license needs to be upgraded and you can contact VMware licensing team for upgrade options specific to your existing license.

Click here to learn more about licensing requirement for vCenter Server 7.0

Download:

Click here to download the latest version of vCenter 7.0

What you require:

• A jump box, preferably windows 10 or any windows server 2008/20212/2016
• It is advised to keep the jump box and the destination vCenter 7.0 on the same subnet, same port group/VLAN as the source vCenter appliance that you are planning to upgrade

          This way we can eliminate most of the network related errors during the upgrade phase.

• User has access to windows based external PSC and vCenter
• Make sure you have taken complete backup of the vCenter database

A quick summary of actions we will be performing for this migration process:

The migration task is split into stage 1 and stage 2.

Stage 1

Deploy a new 7.0 vCenter VM with active network connection set to communicate via the temporary IP address

 

Stage 2

The installer exports the data from the existing 6.5 vCenter to the new 7.0 vCenter using temporary IP

Performs convergence, shuts down source vCenter and reverts the network back to the same IP as the source vCenter

Performs First-Boot of vCenter 7.0 services and then imports copied data to the 7.0 vCenter

Steps with Screenshot :

___________________________________________________________________________________________

Stage 1

___________________________________________________________________________________________

Once you have read the above documents proceed to mount the downloaded image on the jump box

Inside the mounted directory, copy the "migration-assistant" folder

Log into the source windows vCenter server and paste the "migration-assistant" folder

___________________________________________________________________________________________

<On the source 6.5 windows vCenter>

Navigate to the folder and Run the migration assistant as Administrator

___________________________________________________________________________________________

Enter the SSO password and wait for the installer to perform pre-checks and shows prompt "waiting for migration to start"

DO NOT CLOSE THIS WINDOW - KEEP IT RUNNING

___________________________________________________________________________________________

<Login back to the Jump Box where you have mounted the installer ISO>

Navigate to the following directory and run the installer as Administrator and Select "Migrate"

___________________________________________________________________________________________

Once the installer starts, on the Introduction page, we have a quick recap of the two stage process which we had discussed earlier

Click "Next" and accept the EULA (End User License Agreement)

___________________________________________________________________________________________

Here you need to enter the FQDN of the source vCenter server

Also your local SSO administrator username and the password and click "Next"

(Make sure to correct the domain vsphere.local in case if you have set a different local SSO domain)

The installer gives prompt "Converge to an embedded Platform Services Controller"

This is to let users know that it has read the underlying vCenter configuration.

It automatically detects that the source vCenter has external SSO and will perform a converge operation during Migration

___________________________________________________________________________________________

Enter the host/vcenter name or IP on which the new 7.0 VM is going to get deployed

Since I have set the host IP address, I have set the username as root

If you had entered vCenter name, you should be entering the SSO admin user which is administartor@vsphere.local

___________________________________________________________________________________________

The VM name is the name on which the new VM will be deployed on the inventory

Also here you are given option to set the root password for the 7.0 vCenter

___________________________________________________________________________________________

Set the appliance deployment size based on your environmental requirement

You can refer the table in the above screenshot to size it accordingly

___________________________________________________________________________________________

You select the Datastore where the new VM will be deployed

___________________________________________________________________________________________

It is advised you select the same port-group where the source vCenter VM resides

Provide the temporary IP address, subnet, gateway and DNS server

All these steps are mandatory and cannot be skipped

___________________________________________________________________________________________

You are given one final view of all the network settings provided

Once confirming the details, click on Finish to start Stage1 deployment

___________________________________________________________________________________________

The deployment of the new vCenter 7.0 VM starts

You can check its progress by logging into the ESXi host and check the tasks pane

The installer might freeze at 80% but do not panic as this is common

At 80% is where it installs the RPM packages for the appliance

___________________________________________________________________________________________

Once completed, you should see the screen as above

___________________________________________________________________________________________

At this point, it is advised to take a snapshot of the newly deployed vCenter 7.0 appliance

If by any chance if the installer fails, you can revert back to the end of Stage1 installation and retry the upgrade again

 

To restart the upgrade from this point, you just simply enter the temporary IP address with port 5480

Example: If my temporary IP is 192.168.0.111

Then I restart the upgrade process from browser https://192.168.0.111:5480

___________________________________________________________________________________________

Stage 2

Click continue to go to Stage 2 Introduction page where the process is explained

Click "Next" to take you to the "Connect to source vCenter" page

___________________________________________________________________________________________

The installer detects the existing vCenter details which were provided earlier

Click "Next" to run the pre-migration checks for Stage 2

___________________________________________________________________________________________

This is the new option introduced

You can select the default option in case if you have single PSC and vCenter like we used in this guide

___________________________________________________________________________________________

Optional - Only for reference purpose

This is how you can select to manage convergence in case if the PSC has multiple vCenter registered

___________________________________________________________________________________________

You are given option to enter the username which has privilege to add machines to the Domain

This step automatically adds vCenter appliance to the AD domain

___________________________________________________________________________________________

You can choose to keep tasks, events and performance charts data

You can also skip and go only with the configuration data of the source vCenter

___________________________________________________________________________________________

You can check this box to join VMware customer experience improvement program

Click "Next" to continue

___________________________________________________________________________________________

You are given options to validate your inputs

You have to check the "I have backed up..." to continue

If all the entered data is correct, start the final step by clicking on "Finish"

___________________________________________________________________________________________

Stage 2 starts and it will power off the source vCenter

The new vCenter 7.0 VM will take the same IP as the source and the temporary IP will be deleted

Once complete you will see installation successful 100% complete.

___________________________________________________________________________________________

This marks the end of Stage 2 and completion of the migration process

Additional Notes:

Only the source windows vCenter is only powered off

If you notice the source PSC is still powered on

Also if you check the replication partner, you will still see the source PSC registered with the new vCenter 7.0 appliance

This is kept so that customers can continue the migrate paths for other vCenter which are connected to the same PSC

Once the entire environment is migrated, you can decommission the source windows PSC following this link

- Jonathan Ebenezer

Good day,

I am an absolute novice with VMWare and want to build a test bench environment.

I have tried to do an install of VMware vSphere Hypervisor 7.0 but that failed due to the network card not being found/compatible.

After some research I found the ESXi Customizer PS and have been trying to create an ISO with my network card driver included,,,, but the script times out.

Script commands I have tried are:

.\ESXi-Customizer-PS-v2.6.0 -v67 -load net-r8168 -outDir G:\ -log G:\ESXi-Customizer-PS.log -nsc

.\ESXi-Customizer-PS-v2.6.0 -v67 -load net-r8168 -outDir C:\Users\james\Desktop\ESXI -log C:\Users\james\Desktop\ESXI\ESXi-Customizer-PS.log -nsc

.\ESXi-Customizer-PS-v2.6.0 -v67 -load net-r8168 -pkgDir C:\Users\james\Desktop\ESXI\Driver -outDir G:\ -log G:\ESXi-Customizer-PS.log -nsc

The script proceeds well and then always seems to fail at the same point...

An unexpected error occured:

[WinError 10054] An existing connection was forcibly closed by the remote host

I have attached a copy of the log file for your info.

Thanks in advance for the assistance.

Regards James

Since I install esxi6.7 without RAID driver, I need to inject the driver into esxi6.7.iso. The problems I encounter are as follows:

PS E:\t1> $DeployNoSignatureCheck=$true

PS E:\t1> .\ESXi-Customizer-PS-v2.6.0.ps1 -v67 -vft -pkgDir E:\t1\drivers

安全警告

请只运行你信任的脚本。虽然来自 Internet 的脚本会有一定的用处，但此脚本可能会损坏你的计算机。如果你信任此脚本，请使用 Unblock-File cmdlet

允许运行该脚本，而不显示此警告消息。是否要运行 E:\t1\ESXi-Customizer-PS-v2.6.0.ps1?

[D] 不运行(D)  [R] 运行一次(R)  [S] 暂停(S)  [?] 帮助 (默认值为“D”): r

This is ESXi-Customizer-PS Version 2.6.0 (visit https://ESXi-Customizer-PS.v-front.de for more information!)

(Call with -help for instructions)

Logging to C:\Users\Song\AppData\Local\Temp\ESXi-Customizer-PS-12712.log ...

Running with PowerShell version 5.1 and VMware PowerCLI version 12.0.0.15939655

Connecting the VMware ESXi Online depot ... [OK]

Connecting the V-Front Online depot ... [OK]

Getting Imageprofiles, please wait ... [OK]

Using Imageprofile ESXi-6.7.0-20200404001-standard ...

(dated 04/21/2020 06:45:14, AcceptanceLevel: PartnerSupported,

Updates ESXi 6.7 Image Profile-ESXi-6.7.0-20200404001-standard)

Loading Offline bundles and VIB files from E:\t1\drivers ...

   Loading E:\t1\drivers\aacraid-esxi6.0-1.2.1.58012.zip ... [OK]

      Add VIB scsi-aacraid 6.0.6.2.1.58012-1OEM.600.0.0.2494585 [OK, replaced 1.1.5.1-9vmw.670.0.0.8169922]

   Loading E:\t1\drivers\vmware-esxi-drivers-scsi-aacraid-600.6.2.1.58012.-1.0.6.2494585.x86_64.vib ... [OK]

      Add VIB scsi-aacraid 6.0.6.2.1.58012-1OEM.600.0.0.2494585 [IGNORED, already added]

Exporting the Imageprofile to 'E:\t1\ESXi-6.7.0-20200404001-standard-customized.iso'. Please be patient ...

An unexpected error occured:

Could not find a trusted signer: self signed certificate

If requesting support please be sure to include the log file

   C:\Users\Song\AppData\Local\Temp\ESXi-Customizer-PS-12712.log

I've got DHCP configured and working

I've got TFTP server configured and working.

I've got images and Deploy rules configured (I believe correctly. They match similar rules i used in 6.5 and 6.7 autodeploy instances

When a host PXE boots it gives this error

Hi guys

I got the following issue that mine lsi megaraid  is not recognized.

The installer gives an unsupported pci card.

While the lsi 9240 card is supported bij 7.0.0 by the hardware compatiblity guide ( if ai am not wrong)

Any help to solve this

Regards

Peter

Hi,

Im getting an error when using the ssl-updater.bat (for 5.5) trying to update the SSO certificate.  I have created a V3 root cert using OpenSSL (after finding out V1 certs are not supported) and signed each of the CSR's that I generated using the tool, with the rootCa.workgroup cert.  I've created the pem chain for the SSO certificate and have attempted to replace, but the import fails with (in the cmd window)'The Service is not installed on that machine' and gives the output in the log below.   The certificate is valid in my MMC and the root is in the Trusted root store.

Any ideas? Stumped at step one of the plan......

Thanks

Nick

2015-07-21T16:57:32.278+0100 [execution] INFO  TOOL START

2015-07-21T16:57:33.001+0100 [c.v.s.c.c.i.ServerSslConfigFactoryImpl] INFO  Loading private key file C:\certs\requests\vCenterSSO-VirtualCenter\rui.key

2015-07-21T16:57:33.106+0100 [c.v.s.c.c.i.ServerSslConfigFactoryImpl] INFO  Loading certificate chain file C:\certs\requests\vCenterSSO-VirtualCenter\rui.pem

2015-07-21T16:57:33.175+0100 [c.v.s.c.c.i.ServerSslConfigFactoryImpl] INFO  Loaded X.509 certificate for Subject: CN=VirtualCenter.WORKGROUP, OU=vCenterSSO-VirtualCenter, O=QuickFixPC Limited, L=Southampton, ST=Hampshire, C=GB

2015-07-21T16:57:33.178+0100 [c.v.s.c.c.i.ServerSslConfigFactoryImpl] INFO  Loaded X.509 certificate for Subject: CN=RootCA.WORKGROUP, OU=vCenterRoot, O=QuickFixPC Limited, L=Southampton, ST=Hampshire, C=GB

2015-07-21T16:57:33.179+0100 [c.v.s.c.c.i.ServerSslConfigFactoryImpl] INFO  Successfully loaded 2 certificate(s) from the chain file.

2015-07-21T16:57:33.277+0100 [c.v.s.c.c.i.ServerSslConfigFactoryImpl] INFO  The effective SSL certificate chain is:

2015-07-21T16:57:33.281+0100 [c.v.s.c.c.i.ServerSslConfigFactoryImpl] INFO     [0] CN=VirtualCenter.WORKGROUP, OU=vCenterSSO-VirtualCenter, O=QuickFixPC Limited, L=Southampton, ST=Hampshire, C=GB

2015-07-21T16:57:33.281+0100 [c.v.s.c.c.i.ServerSslConfigFactoryImpl] INFO     [1] CN=RootCA.WORKGROUP, OU=vCenterRoot, O=QuickFixPC Limited, L=Southampton, ST=Hampshire, C=GB

2015-07-21T16:57:33.288+0100 [c.v.s.c.c.i.ServerSslConfigFactoryImpl] INFO  Checking certificates validity period.

2015-07-21T16:57:33.308+0100 [c.v.s.c.c.i.ServerSslConfigFactoryImpl] INFO  Checking leaf certificate's suitability for the current machine.

2015-07-21T16:57:33.324+0100 [c.v.s.c.c.i.ServerSslConfigFactoryImpl] DEBUG Machine's FQHN: VirtualCenter.WORKGROUP

2015-07-21T16:57:33.328+0100 [c.v.s.c.c.i.DNSResolver] DEBUG DNS validation: resolving DNS for VirtualCenter.WORKGROUP (A/CNAME)

2015-07-21T16:57:33.394+0100 [c.v.s.c.c.i.ServerSslConfigFactoryImpl] DEBUG Machine has a resolvable hostname: VirtualCenter.WORKGROUP

2015-07-21T16:57:33.416+0100 [c.v.s.c.c.i.ServerSslConfigFactoryImpl] DEBUG Checking if leaf certificate is suitable for candidate address VirtualCenter.WORKGROUP.

2015-07-21T16:57:33.422+0100 [c.v.s.c.c.i.ServerSslConfigFactoryImpl] DEBUG Leaf certificate is suitable for VirtualCenter.WORKGROUP

2015-07-21T16:57:33.423+0100 [c.v.s.c.c.i.ServerSslConfigFactoryImpl] INFO  Checking the certificates key lengths.

2015-07-21T16:57:33.432+0100 [c.v.s.c.c.i.ServerSslConfigFactoryImpl] DEBUG Checking certificates signature algortihm types.

2015-07-21T16:57:33.462+0100 [execution] INFO  BEGIN UPDATE

2015-07-21T16:57:33.540+0100 [c.v.s.c.ConfigureWindowsSslCommand] INFO  Beginning certificate replacement procedure for Single Sign-On.

2015-07-21T16:57:33.541+0100 [c.v.s.c.ConfigureWindowsSslCommand] DEBUG Checking if vCenter Single Sign-On service is running.

2015-07-21T16:57:33.700+0100 [c.v.s.c.c.i.RollbackSupportImpl] INFO  The existing configuration will be backed up to C:\certs\backup\sso-ssl-updater.backup

2015-07-21T16:57:33.742+0100 [c.v.s.c.c.i.RollbackSupportImpl] INFO  The backup directory `sso-ssl-updater.backup' did already exist and was moved to `sso-ssl-updater.backup.4'

2015-07-21T16:57:33.744+0100 [c.v.s.c.ConfigureWindowsSslCommand] INFO  Checking the password of administrator user Administrator.

2015-07-21T16:57:33.744+0100 [c.v.s.c.ConfigureWindowsSslCommand] DEBUG Checking if vCenter Single Sign-On service is running.

2015-07-21T16:57:33.747+0100 [c.v.s.c.c.i.ServerToolsImpl] INFO  Creating remote Lookup Service tools with host 127.0.0.1 and port 7080

2015-07-21T16:57:33.758+0100 [c.v.s.c.c.i.ServerToolsImpl] DEBUG Trying to connect to Lookup Service at http://127.0.0.1:7080/lookupservice/sdk

2015-07-21T16:57:34.112+0100 [c.v.v.i.i.LookupServiceAccess] DEBUG Creating VMODL client for LookupService

2015-07-21T16:57:34.778+0100 [c.v.v.i.i.AdminServiceAccess] DEBUG Creating client for SSO Admin on address: http://127.0.0.1:7080/sso-adminserver/sdk/vsphere.local

2015-07-21T16:57:35.584+0100 [c.v.v.s.a.c.v.i.AbstractClient] WARN  ******* WARNING ****** WARNING ****** WARNING *******

2015-07-21T16:57:35.584+0100 [c.v.v.s.a.c.v.i.AbstractClient] WARN  Possible remote API mismatch detected. Operation will continue, but errors are likely.

2015-07-21T16:57:35.584+0100 [c.v.v.s.a.c.v.i.AbstractClient] WARN  ******* WARNING ****** WARNING ****** WARNING *******

2015-07-21T16:57:35.846+0100 [c.v.v.s.c.SecurityTokenServiceConfig$ConnectionConfig] WARN  This configuration will establish untrusted connection with the STS server.It is acceptable for developing purposes only!

2015-07-21T16:57:38.783+0100 [c.v.v.s.a.c.v.i.AbstractClient] WARN  ******* WARNING ****** WARNING ****** WARNING *******

2015-07-21T16:57:38.783+0100 [c.v.v.s.a.c.v.i.AbstractClient] WARN  Possible remote API mismatch detected. Operation will continue, but errors are likely.

2015-07-21T16:57:38.783+0100 [c.v.v.s.a.c.v.i.AbstractClient] WARN  ******* WARNING ****** WARNING ****** WARNING *******

2015-07-21T16:57:38.798+0100 [c.v.s.c.ConfigureWindowsSslCommand] DEBUG Checking if vCenter Single Sign-On service is running.

2015-07-21T16:57:38.800+0100 [c.v.s.c.ConfigureWindowsSslCommand] INFO  The vCenter Single Sign-On service is currently running but it must be stopped in order to perform a portion of the SSL certificate update operation.

2015-07-21T16:57:38.800+0100 [c.v.s.c.ConfigureWindowsSslCommand] INFO  Stopping the vCenter Single Sign-On service.

2015-07-21T16:57:38.804+0100 [c.v.s.c.c.i.ServiceControlImpl] INFO  Waiting for service VMwareSTS to stop, 15 seconds.

2015-07-21T16:57:41.811+0100 [c.v.s.c.c.i.ServiceControlImpl] INFO  Service did stop successfully.

2015-07-21T16:57:41.811+0100 [c.v.s.c.ConfigureWindowsSslCommand] INFO  Updating service container configuration

2015-07-21T16:57:41.811+0100 [c.v.s.c.ConfigureWindowsSslCommand] DEBUG Updating STS Files

2015-07-21T16:57:41.811+0100 [c.v.s.c.c.i.RollbackSupportImpl] DEBUG Backing up (move) file C:\ProgramData\VMware\cis\runtime\VMwareSTS\conf\ssoserver.crt to C:\certs\backup\sso-ssl-updater.backup

2015-07-21T16:57:41.811+0100 [c.v.s.c.c.i.RollbackSupportImpl] DEBUG Backing up (move) file C:\ProgramData\VMware\cis\runtime\VMwareSTS\conf\ssoserver.p12 to C:\certs\backup\sso-ssl-updater.backup

2015-07-21T16:57:41.811+0100 [c.v.s.c.ConfigureWindowsSslCommand] DEBUG Writing the sso SSL certificate in C:\ProgramData\VMware\cis\runtime\VMwareSTS\conf\ssoserver.crt

2015-07-21T16:57:41.811+0100 [c.v.s.c.ConfigureWindowsSslCommand] DEBUG Writing the sso SSL certificate and private key in C:\ProgramData\VMware\cis\runtime\VMwareSTS\conf\ssoserver.p12

2015-07-21T16:57:41.905+0100 [c.v.s.c.ConfigureWindowsSslCommand] TRACE In updateLsIfCan

2015-07-21T16:57:41.905+0100 [c.v.s.c.ConfigureWindowsSslCommand] DEBUG Checking if vCenter Single Sign-On service is running.

2015-07-21T16:57:41.905+0100 [c.v.s.c.ConfigureWindowsSslCommand] INFO  The vCenter Single Sign-On service is not currently running but it must be started in order to perform a portion of the SSL certificate update operation.

2015-07-21T16:57:41.905+0100 [c.v.s.c.ConfigureWindowsSslCommand] INFO  Starting the vCenter Single Sign-On service.

2015-07-21T16:57:41.920+0100 [c.v.s.c.c.i.ServiceControlImpl] INFO  Waiting for service VMwareSTS to start, 15 seconds.

2015-07-21T16:57:44.952+0100 [c.v.s.c.c.i.ServiceControlImpl] INFO  Service did start successfully.

2015-07-21T16:57:44.952+0100 [c.v.s.c.c.i.ServerToolsImpl] INFO  Creating remote Lookup Service tools with host 127.0.0.1 and port 7080

2015-07-21T16:57:44.952+0100 [c.v.s.c.c.i.ServerToolsImpl] DEBUG Trying to connect to Lookup Service at http://127.0.0.1:7080/lookupservice/sdk

2015-07-21T16:57:44.952+0100 [c.v.v.i.i.LookupServiceAccess] DEBUG Creating VMODL client for LookupService

2015-07-21T16:58:26.683+0100 [c.v.v.i.i.AdminServiceAccess] DEBUG Creating client for SSO Admin on address: http://127.0.0.1:7080/sso-adminserver/sdk/vsphere.local

2015-07-21T16:58:27.359+0100 [c.v.v.s.a.c.v.i.AbstractClient] WARN  ******* WARNING ****** WARNING ****** WARNING *******

2015-07-21T16:58:27.360+0100 [c.v.v.s.a.c.v.i.AbstractClient] WARN  Possible remote API mismatch detected. Operation will continue, but errors are likely.

2015-07-21T16:58:27.360+0100 [c.v.v.s.a.c.v.i.AbstractClient] WARN  ******* WARNING ****** WARNING ****** WARNING *******

2015-07-21T16:58:27.616+0100 [c.v.v.s.c.SecurityTokenServiceConfig$ConnectionConfig] WARN  This configuration will establish untrusted connection with the STS server.It is acceptable for developing purposes only!

2015-07-21T16:58:30.549+0100 [c.v.v.s.a.c.v.i.AbstractClient] WARN  ******* WARNING ****** WARNING ****** WARNING *******

2015-07-21T16:58:30.549+0100 [c.v.v.s.a.c.v.i.AbstractClient] WARN  Possible remote API mismatch detected. Operation will continue, but errors are likely.

2015-07-21T16:58:30.549+0100 [c.v.v.s.a.c.v.i.AbstractClient] WARN  ******* WARNING ****** WARNING ****** WARNING *******

2015-07-21T16:58:30.550+0100 [c.v.s.c.ConfigureWindowsSslCommand] INFO  Updating the SSO endpoints in the Lookup Service.

2015-07-21T16:58:30.565+0100 [c.v.s.c.ConfigureWindowsSslCommand] INFO  This is Single Sign-On single-node install. All Single Sign-On endpoints are served from this node.

2015-07-21T16:58:31.155+0100 [c.v.s.c.c.i.LookupServiceToolsRemoteImpl] DEBUG Updating the Lookup Service record for the Security Token Service

2015-07-21T16:58:31.958+0100 [c.v.s.c.ConfigureWindowsSslCommand] DEBUG Checking if vCenter Single Sign-On service is running.

2015-07-21T16:58:31.969+0100 [c.v.s.c.ConfigureWindowsSslCommand] INFO  The vCenter Single Sign-On service is currently running but it must be stopped in order to undo a portion of the SSL certificate update operation.

2015-07-21T16:58:31.969+0100 [c.v.s.c.ConfigureWindowsSslCommand] INFO  Stopping the vCenter Single Sign-On service.

2015-07-21T16:58:32.026+0100 [c.v.s.c.c.i.ServiceControlImpl] INFO  Waiting for service VMwareSTS to stop, 15 seconds.

2015-07-21T16:58:35.041+0100 [c.v.s.c.c.i.ServiceControlImpl] INFO  Service did stop successfully.

2015-07-21T16:58:35.041+0100 [c.v.s.c.c.i.RollbackSupportImpl] DEBUG File C:\ProgramData\VMware\cis\runtime\VMwareSTS\conf\ssoserver.crt successfully restored from sso-ssl-updater.backup\ssoserver.crt

2015-07-21T16:58:35.041+0100 [c.v.s.c.c.i.RollbackSupportImpl] DEBUG File C:\ProgramData\VMware\cis\runtime\VMwareSTS\conf\ssoserver.p12 successfully restored from sso-ssl-updater.backup\ssoserver.p12

2015-07-21T16:58:35.041+0100 [c.v.s.c.ConfigureWindowsSslCommand] ERROR An error ocurred during the certificate replacement procedure:null

2015-07-21T16:58:35.041+0100 [c.v.s.c.ConfigureWindowsSslCommand] DEBUG

com.vmware.vim.binding.vmodl.fault.SecurityError: null

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[na:1.7.0_76]

at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) ~[na:1.7.0_76]

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) ~[na:1.7.0_76]

at java.lang.reflect.Constructor.newInstance(Unknown Source) ~[na:1.7.0_76]

at java.lang.Class.newInstance(Unknown Source) ~[na:1.7.0_76]

at com.vmware.vim.vmomi.core.types.impl.ComplexTypeImpl.newInstance(ComplexTypeImpl.java:171) ~[vlsi-core.jar:na]

at com.vmware.vim.vmomi.core.types.impl.DefaultDataObjectFactory.newDataObject(DefaultDataObjectFactory.java:26) ~[vlsi-core.jar:na]

at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.ComplexStackContext.<init>(ComplexStackContext.java:33) ~[vlsi-core.jar:na]

at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.parse(UnmarshallerImpl.java:135) ~[vlsi-core.jar:na]

at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.unmarshall(UnmarshallerImpl.java:98) ~[vlsi-core.jar:na]

at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:84) ~[vlsi-core.jar:na]

at com.vmware.vim.vmomi.client.common.impl.SoapFaultStackContext.setValue(SoapFaultStackContext.java:37) ~[vlsi-client.jar:na]

at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.unmarshal(ResponseUnmarshaller.java:97) ~[vlsi-client.jar:na]

at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.unmarshalResponse(ResponseImpl.java:245) ~[vlsi-client.jar:na]

at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setResponse(ResponseImpl.java:203) ~[vlsi-client.jar:na]

at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:126) ~[vlsi-client.jar:na]

at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:98) ~[vlsi-client.jar:na]

at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall(MethodInvocationHandlerImpl.java:533) ~[vlsi-client.jar:na]

at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall(MethodInvocationHandlerImpl.java:514) ~[vlsi-client.jar:na]

at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall(MethodInvocationHandlerImpl.java:302) ~[vlsi-client.jar:na]

at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeOperation(MethodInvocationHandlerImpl.java:272) ~[vlsi-client.jar:na]

at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke(MethodInvocationHandlerImpl.java:169) ~[vlsi-client.jar:na]

at com.sun.proxy.$Proxy32.updateService(Unknown Source) ~[na:na]

at com.vmware.sso.cfg.components.impl.LookupServiceToolsRemoteImpl.updateService(LookupServiceToolsRemoteImpl.java:242) ~[sso-updater.jar:na]

at com.vmware.sso.cfg.components.impl.LookupServiceToolsRemoteImpl.rollbackSsoRecords(LookupServiceToolsRemoteImpl.java:119) ~[sso-updater.jar:na]

at com.vmware.sso.cfg.ConfigureWindowsSslCommand.undoLsChanges(ConfigureWindowsSslCommand.java:340) ~[sso-updater.jar:na]

at com.vmware.sso.cfg.ConfigureWindowsSslCommand.updateLsIfCan(ConfigureWindowsSslCommand.java:186) ~[sso-updater.jar:na]

at com.vmware.sso.cfg.ConfigureWindowsSslCommand.updateSsoIfCan(ConfigureWindowsSslCommand.java:171) ~[sso-updater.jar:na]

at com.vmware.sso.cfg.ConfigureWindowsSslCommand.execute(ConfigureWindowsSslCommand.java:128) ~[sso-updater.jar:na]

at com.vmware.sso.cfg.ConfigureWindowsSslCommand$execute.call(Unknown Source) [sso-updater.jar:na]

at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) [groovy-all-1.8.8.jar:1.8.8]

at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) [groovy-all-1.8.8.jar:1.8.8]

at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) [groovy-all-1.8.8.jar:1.8.8]

at com.vmware.sso.cfg.SsoUpdaterMain.main(SsoUpdaterMain.groovy:67) [sso-updater.jar:na]

2015-07-21T16:58:35.041+0100 [c.v.s.c.ConfigureWindowsSslCommand] DEBUG Checking if vCenter Single Sign-On service is running.

2015-07-21T16:58:35.041+0100 [c.v.s.c.ConfigureWindowsSslCommand] INFO  The vCenter Single Sign-On service is not currently running but it was in the beginning. Starting it.

2015-07-21T16:58:35.056+0100 [c.v.s.c.ConfigureWindowsSslCommand] INFO  Starting the vCenter Single Sign-On service.

2015-07-21T16:58:35.181+0100 [c.v.s.c.c.i.ServiceControlImpl] INFO  Waiting for service VMwareSTS to start, 15 seconds.

2015-07-21T16:58:38.212+0100 [c.v.s.c.c.i.ServiceControlImpl] INFO  Service did start successfully.

2015-07-21T16:58:38.212+0100 [execution] INFO  TOOL END with status code = 2

Is there a document to provide the procedure for upgrading ESXi 5.5.0 U3 to ESXi 7.0 (and updates) remotely?

Thank you in advance

Hi all

Im planning to build my vmware esxi 6.5 home lab using either ((that will help me for VCP DCV 6.5 and my CCIE LAb))

1) IBM X3650 M3  2x Quad core Xeon X5570 or  2X  HEX core Xeon X5670 system

OR

2) HP Proliant DL380 G6  2 x Quad core Xeon X5550

but CPU compatible list says these both CPU support ESXi 6.5 .

but when i search for IBM X3650 system and HP system , vmware compatibility list says it does not support ESXi 6.5.

im Little confused with this mismatch , please help to clarify this confusion.

Hello Everybody.

I have a system on 5.1 with 3x ESXi and 20 virtual machines attached from a SAN. I want to create a new system on 7.0 with new licence for it with same configuration as a old one on new servers. The old servers want be used any more as ESX-s.

What are the best practices.

Can vm-s  be upgraded from version 9 to 17.

Thank you.

Hi, i've just purchased a vSphere 7 Essentials license and i what to a dowgrade to the 6.5 version.

It's possible?

How can i get it?

During the standard upgrade of 6.7 vSphere to 7.0. Step 1 requires the deployment of a new vSphere instance. All goes through well until the start of the deployment, never reaching past 0% erroring out with the following message: Failed to send file [disk-0.vmdk] to the host [plumbus.cloud], please check the network connection. I have attached the log for reference. Has anyone else come across this issue?

Hi when I try to upgrade I get this error. Is this issue will be fixed once HPE updates the custom image. Appreciate any advise/help 

Hello,

We are currently seeing the following error when upgrading to VCSA 7.0 from 6.7, this error occurs durning step 2 of the new VCSA.

Error

Encountered an internal error. Traceback (most recent call last): File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 1752, in main vmidentityFB.boot() File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 367, in boot self.registerTokenServiceWithLookupService() File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 654, in registerTokenServiceWithLookupService raise e File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 650, in registerTokenServiceWithLookupService dynVars=dynVars) File "/usr/lib/vmware-cm/bin/cloudvmcisreg.py", line 710, in cloudvm_sso_cm_register serviceId = do_lsauthz_operation(cisreg_opts_dict) File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 1058, in do_lsauthz_operation ls_obj = LookupServiceClient(ls_url, retry_count=60) File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 314, in __init__ self._init_service_content() File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 294, in do_retry return req_method(self, *args, **kargs) File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 304, in _init_service_content self.service_content = si.RetrieveServiceContent() File "/usr/lib/vmware/site-packages/pyVmomi/VmomiSupport.py", line 556, in <lambda> self.f(*(self.args + (obj,) + args), **kwargs) File "/usr/lib/vmware/site-packages/pyVmomi/VmomiSupport.py", line 368, in _InvokeMethod return self._stub.InvokeMethod(self, info, args) File "/usr/lib/vmware/site-packages/pyVmomi/SoapAdapter.py", line 1448, in InvokeMethod conn.request('POST', self.path, req, headers) File "/usr/lib/python3.7/http/client.py", line 1252, in request self._send_request(method, url, body, headers, encode_chunked) File "/usr/lib/python3.7/http/client.py", line 1298, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/usr/lib/python3.7/http/client.py", line 1247, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/usr/lib/python3.7/http/client.py", line 1026, in _send_output self.send(msg) File "/usr/lib/python3.7/http/client.py", line 966, in send self.connect() File "/usr/lib/vmware/site-packages/pyVmomi/SoapAdapter.py", line 1085, in connect six.moves.http_client.HTTPSConnection.connect(self) File "/usr/lib/python3.7/http/client.py", line 1414, in connect super().connect() File "/usr/lib/python3.7/http/client.py", line 938, in connect (self.host,self.port), self.timeout, self.source_address) File "/usr/lib/python3.7/socket.py", line 727, in create_connection raise err File "/usr/lib/python3.7/socket.py", line 716, in create_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused

Resolution

This is an unrecoverable error, please retry install. If you encounter this error again, please search for these symptoms in the VMware Knowledge Base for any known issues and possible resolutions. If none can be found, collect a support bundle and open a support request.

We are currently unsure why this error is occurring. This error appears as the Security Token Service (STS) is starting up during the install.

Hi,

We have tree ESXi 6.5 hosts running in a VMware cluster managed by a vCenter 6.7 u2.

Now we have installed a new vCenter 7.0.0a and we want to migrate those tree ESXi host to that vCenter into a new Vmware cluster.

What is the best way to do this without put the ESXi hosts in maintenance mode. We want that the VMs should be still running on the ESXi host during the migration?

Thank you in advance for your response!

Best regards,

Audun