Hi

im considering upgrade my vcenter server from 6.5u3g(15505374) to vcenter 6.7u3f(15976714).

i read the "back in time release upgrade restrictions (kb67077)" i looked over the matrix and noticed that my vcenter is not upgadable.

i check the release dates of the version and i can see that my vcenter has no "back in time" secnario. (and yet, it appears as no upgradeble at the matrix.)

my vcenter version and release date: vcenter 6.5U3g 15505374 released 1/30/2020.
the latest vcenter version and release date:vcenter 6.7 15976714 released 4/9/2020.

do i miss something?

i have to make sure before any progress on my evvironment.

thanks for your help

Dor

Hi Guys!

Im able to succesfully migrate from 6.7 to 7.0. Everything is up and running.

Now i want to use my company signed wildcard certificate for the web client for avoid SSL error in browser.

Probably this is where is messed up the 6.x badly, so anyone can help me out?

As i understand i need the solution user certificate, the fifth menu option in the console certificate manager. Right?

If i replace the machine cert the whole system messed up, i figured out already. So this is a clean and fresh system, everything is working. I really dont want to mess up this part again, but we need the signed cert.

Thanks!

[root@clientVM1 lin64]# ./vcsa-deploy install /root/vcenter/config/embedded_vCSA_on_ESXi.json --accept-eula --no-esx-ssl-verify --no-ssl-certificate-verification --log-dir=/root/vcenter/log

Run the installer with "-v" or "--verbose" to log detailed information

Updating log file location, copying '/tmp/vcsaCliInstaller-2020-04-21-03-14-69v3uwr0/vcsa-cli-installer.log' to desired location as a backup: '/root/vcenter/log/workflow_1587438887538/vcsa-cli-installer.log.bak'

Consuming the installer build:15393115

Workflow log-dir /root/vcenter/log/workflow_1587438887538

=================================================== [START] Start executing Task: To validate CLI options at 03:14:47 ===================================================

Command line arguments verfied.

========= [SUCCEEDED] Successfully executed Task 'CLIOptionsValidationTask: Executing CLI optionsValidation task' in TaskFlow 'template_validation' at 03:14:47 =========

=========================================== [START] Start executing Task: To validate the syntax of the template. at 03:14:47 ===========================================

Template syntax validation for template '/root/vcenter/config/embedded_vCSA_on_ESXi.json' succeeded.

Syntax validation for all templates succeeded.

======== [SUCCEEDED] Successfully executed Task 'SyntaxValidationTask: Executing Template Syntax Validation task' in TaskFlow 'template_validation' at 03:14:47 ========

[START] Start executing Task: To check the version of each template, and for each older template that supports CEIP, convert it to the latest template format, and save

it to the Template Blackboard at 03:14:47

CEIP is not enabled because the template key 'ceip_enabled' in section 'ceip', subsection 'settings' in template '/root/vcenter/config/embedded_vCSA_on_ESXi.json' was

set to 'false'.

CEIP is not enabled because the template key 'ceip_enabled' in section 'ceip', subsection 'settings' in template '/root/vcenter/config/embedded_vCSA_on_ESXi.json' was

set to 'false'.

CEIP is not enabled because the template key 'ceip_enabled' in section 'ceip', subsection 'settings' in template '/root/vcenter/config/embedded_vCSA_on_ESXi.json' was

set to 'false'.

Template version processing for template '/root/vcenter/config/embedded_vCSA_on_ESXi.json' succeeded.

Version processing for all templates succeeded.

======= [SUCCEEDED] Successfully executed Task 'VersionProcessingTask: Executing Template Version Processing task' in TaskFlow 'template_validation' at 03:14:47 =======

============= [START] Start executing Task: To validate the template structure against the rules specified by a corresponding template schema. at 03:14:47 =============

Template structure validation for template '/root/vcenter/config/embedded_vCSA_on_ESXi.json' succeeded.

Structure validation for all templates succeeded.

===== [SUCCEEDED] Successfully executed Task 'StructureValidationTask: Executing Template Structure Validation task' in TaskFlow 'template_validation' at 03:14:47 =====

[START] Start executing Task: To create a dependency graph for the provided templates, with an edge pairing two templates that are dependent on each other. Such graph

relationships will affect whether certain templates can be deployed in parallel, or must be deployed sequentially. at 03:14:48

Dependency processing for all templates succeeded.

==== [SUCCEEDED] Successfully executed Task 'DependencyProcessingTask: Executing Template Dependency Processing task' in TaskFlow 'template_validation' at 03:14:48 ====

=================================== [START] Start executing Task: Validate that requirements are met in the source VCSA. at 03:14:48 ===================================

InstallRequirementCollector: Reached gathering requirement

================ [SUCCEEDED] Successfully executed Task 'SrcRequirementTask: Running SrcRequirementTask' in TaskFlow 'embedded_vCSA_on_ESXi' at 03:14:48 ================

=================================================== [START] Start executing Task: Perform precheck tasks. at 03:14:49 ===================================================

============================ [START] Start executing Task: Verify that the provided credentials for the target ESXi/VC are valid at 03:14:49 ============================

The certificate of server '1.2.3.4' will not be verified because you have provided either the '--no-ssl-certificate-verification' or '--no-esx-ssl-verify' command

parameter, which disables verification for all certificates. Remove this parameter from the command line if you want server certificates to be verified.

============================ [SUCCEEDED] Successfully executed Task 'Running precheck: TargetCredentials' in TaskFlow 'install' at 03:14:49 ============================

============================== [START] Start executing Task: Verify the target host type matches the one given in the template at 03:14:49 ==============================

============================== [SUCCEEDED] Successfully executed Task 'Running precheck: TargetHostType' in TaskFlow 'install' at 03:14:49 ==============================

========================== [START] Start executing Task: Verify that the target ESXi or VC version meets the minimum requirements at 03:14:49 ==========================

============================== [SUCCEEDED] Successfully executed Task 'Running precheck: TargetVersion' in TaskFlow 'install' at 03:14:49 ==============================

================================ [START] Start executing Task: Validate that the OVA image has the required OVA properties. at 03:14:50 ================================

============================== [SUCCEEDED] Successfully executed Task 'Running precheck: OVAProperties.' in TaskFlow 'install' at 03:14:50 ==============================

====================================== [START] Start executing Task: Validate the provided ip/fqdn is available to use at 03:14:50 ======================================

Pinging IPv4 address 5.6.7.8

5.6.7.8 seems not in use.

Pinging IPv4 address vcenter1.esxi1.lab

Pinging IPv4 address vcenter1.esxi1.lab

Pinging IPv4 address vcenter1.esxi1.lab

5.6.7.8 seems not in use.

=============================== [SUCCEEDED] Successfully executed Task 'Running precheck: IpFqdnInUse' in TaskFlow 'install' at 03:15:34 ===============================

===================== [SUCCEEDED] Successfully executed Task 'Running precheck: LinkingTargetHostnameValidation' in TaskFlow 'install' at 03:15:35 =====================

========================================= [START] Start executing Task: Validate the target ESXi management status at 03:15:35 =========================================

=========================== [SUCCEEDED] Successfully executed Task 'Running precheck: ESXManagementStatus' in TaskFlow 'install' at 03:15:35 ===========================

============================== [START] Start executing Task: Precheck CPU, memory and datastore size requirements for a host. at 03:15:35 ==============================

=============================== [SUCCEEDED] Successfully executed Task 'Running precheck: HostConfigs' in TaskFlow 'install' at 03:15:37 ===============================

=============================== [START] Start executing Task: Validate the provided target appliance name is available to use at 03:15:37 ===============================

============================== [SUCCEEDED] Successfully executed Task 'Running precheck: ApplianceName' in TaskFlow 'install' at 03:15:37 ==============================

============================================================== [START] Start executing Task:  at 03:15:37 ==============================================================

============================================== [SUCCEEDED] Successfully executed Task '' in TaskFlow 'install' at 03:15:37 ==============================================

====================== [START] Start executing Task: Check whether the datastore's free space accommodate the VCSA's deployment option at 03:15:38 ======================

============================ [SUCCEEDED] Successfully executed Task 'Running precheck: TargetDsFreespace' in TaskFlow 'install' at 03:15:38 ============================

=========================== [START] Start executing Task: Verify the provided SSO info is valid by connecting to the STS service. at 03:15:38 ===========================

============================== [SUCCEEDED] Successfully executed Task 'Running precheck: SSOCredentials' in TaskFlow 'install' at 03:15:38 ==============================

============================= [START] Start executing Task: Verify that the provided external SSO (PSC)/Embedded info is valid at 03:15:38 =============================

=============================== [SUCCEEDED] Successfully executed Task 'Running precheck: SSOExternal' in TaskFlow 'install' at 03:15:38 ===============================

======================= [SUCCEEDED] Successfully executed Task 'PrecheckTask: Running prechecks.' in TaskFlow 'embedded_vCSA_on_ESXi' at 03:15:38 =======================

=========================== [START] Start executing Task: Invoke OVF Tool to deploy VCSA for installation, upgrade, and migration at 03:15:39 ===========================

OVF Tool: Opening OVA source: /mnt/cdrom/vcsa-cli-installer/lin64/../../vcsa/VMware-vCenter-Server-Appliance-7.0.0.10100-15934039_OVF10.ova

OVF Tool: The manifest validates

OVF Tool: The provided certificate is in valid period

OVF Tool: Source is signed but could not verify certificate (possibly self-signed)

OVF Tool: Certificate information:

OVF Tool:   CertIssuer:/C=US/ST=California/L=Palo Alto/O=VMware, Inc.

OVF Tool:   CertSubject:/C=US/ST=California/L=Palo Alto/O=VMware, Inc.

OVF Tool:   -----BEGIN CERTIFICATE-----

OVF Tool:   ... <DELETED> ...

OVF Tool:

OVF Tool:   -----END CERTIFICATE-----

OVF Tool: Opening VI target: vi://root@1.2.3.4:443/

OVF Tool: Deploying to VI: vi://root@1.2.3.4:443/

OVF Tool: Disk progress: 99%

OVF Tool: Transfer Completed

OVF Tool: Powering on VM: Embedded-vCenter-Server-Appliance

OVF Tool: Task progress: 0%

OVF Tool: Task Completed

OVF Tool: Waiting for IP address...

OVF Tool: Received IP address: 5.6.7.8

OVF Tool: Completed successfully

====================== [SUCCEEDED] Successfully executed Task 'Deploying vCenter Server Appliance' in TaskFlow 'embedded_vCSA_on_ESXi' at 03:21:31 ======================

================================= [START] Start executing Task: Monitor the entire VCSA deployment using appliance REST API at 03:21:31 =================================

Checking if the target VCSA is powered on and ready for operations...

Successfully verified that the target VCSA 'Embedded-vCenter-Server-Appliance' has been powered on and is now ready for operations

Checking if the target VCSA appliance API is available for query

The certificate of server '5.6.7.8' will not be verified because you have provided either the '--no-ssl-certificate-verification' or '--no-esx-ssl-verify' command

parameter, which disables verification for all certificates. Remove this parameter from the command line if you want server certificates to be verified.

Where ,

1.2.3.4 - ESXi host

5.6.7.8 - vCenter IP

clientVM1 is on the another server , a RHEL VM created, which has access to the DNS server. Reverse mapping of DNS is also done on the DNS server.

Environment:

VMware ESXi, 6.7.0, 15160138

vCenter: 6.7.0.41000 build number: 14836122

We cannot remove one crashed VMware host from our datacenter. We do not have any clusters configured. We do have a vDS. Other hosts are working fine and in production. Remove from inventory is greyed out in vCenter.

The following action I already tried:

Disconnect the host (succesfully)

Remove host from vDS (succesfully)

Remove from inventory is greyed out

Used PowerCLI but came with this error:

Remove-VMHost : 21-4-2020 08:23:16      Remove-VMHost           The method is disabled by 'com.vmware.vcIntegrity'

At line:1 char:1

+ Remove-VMHost ESXVN0XX.FQDN

Any ideas?

I'm running a freshly installed vCenter Server 6.5 embedded on a new ESXi host. There's no problem logging into vCenter SSO with the default administrator-user. However, I've tried adding a new user but I'm simply not allowed to login with it, I've added it to all the administrator-groups in vCenter too for the sake of testing. It's in the same local domain as the administrator "@vsphere.local" (which I'm using to login as well) and for simplicity I've even given them the same password. It's not joined to any AD or such, just local users. But all I get is "Invalid credentials" when I try to use it.

I've tried everything I can imagine, is there something else I might have missed? Are there logs anywhere I can check for what's actually wrong?

I could add images etc, but adding a user and logging in shouldn't be rocket science, setting up everything else has not been a problem.

I'm running a vCenter Server 6.5. There's no problem logging into vCenter SSO with the default administrator-user. However, I've tried adding a new user but I'm simply not allowed to login with it, I've added it to all the administrator-groups in vCenter too for the sake of testing. It's in the same local domain as the administrator "@vsphere.local" (which I'm using to login as well) and for simplicity I've even given them the same password. It's joined to AD or such, local users. But all I get is "Invalid credentials" when I try to use it when I try to loggining with newly added users..

I see this community Invalid credentials for newly added user  but url http://www.virtuallypeculiar.com/2016/11/vsphere-65-login-to-web-client-fails.html does not open.

We use an automated pipeline to create VM templates and then register then in Vcenter using govc. Our exact code is:

register-template(){

   echo"Registering the template"

   GOVC_DATACENTER="${dst_dc}"GOVC_DATASTORE="${dst_ds}" govc vm.register -dump=true-template-host="${host}""${template}/${template}.vmtx"

}

However, I've updated our VCSA appliance from 6.7 to 7.0 and now this command causes the vcenter-service to fail and causes the API endpoints and Vsphere UI to become unresponsive and display the message no object exists . In searching these forums I'm not seeing anyone else having this issue. We're a small shop and don't have SDK support. Does anyone know if there was an API change that might be causing this? Or any other suggest work around? I had to roll our VCSA appliance back to the previous version (6.7) and now the gitlab pipeline that includes this code completes without error.

The admin walked out the door and I have no access other than RDP into the server and use my windows login.

Any advice on how to promote to have the sso role. My backup server cant login remotely to run back ups.

I used to be able to run the client from my desktop and login using my admin account. But now I can only run the client from the actual server.

Any advice or documentation to help me get this function back?

Thanks!

DC

Hi all,

I haven't worked with VMware for the last 4 years or so and - as it does - the landscape has changed somewhat.

I'm currently working on upgrading vCenter 6.0 to v6.7, and we've opted to move to a appliance-based VCSA, and retire the Windows Server host that the vCenter environment is currently sitting on.

Initially, I was under the impression that VCSA could be deployed as a standalone VM/box, and we could move the hosts to it. So far, all the documentation seems to point towards "ingesting" the VCSA into an existing environment, then moving all your assets across.

Is there any way of having a standalone VCSA box from scratch?

I hope I'm making some sense, and thanks upfront

Hello Everyone,

we are in the middle of converting few Hyper-V VMs to Vmware, and we landed with an error message "permission to perform this operation was denied". can some body help us here.

regards

VK

A driver or provider component kit can be installed on esxi host using esxcli commands. However a user needs to login to the esxi host using a SSH client and then issue esxcli software install commands. Can this same operation be done via vSphere web client ? A file i.e. the kits can be copied to the local data-store of the esxi host using vSphere. After this is there a way to issue esxcli software install commands on the esxi hosts connected to vSphere?

When we run Get-VM | Get-TagAssignment | Select Entity,Tag in PowerCli we get this error:

HTTP response with status code 429 and no content (enable debug logging for details)

We have installed latest Powershell and PowerCli, but same problem.

429 means that vCenter gets to many requests, but we only have 1500vm´s, so can that really be true?

The above cmd, is quiet normal, and we use to be able to run it without errors.

Is there a place where i can see logs regarding PowerCLI calls to vCenter (logs on vCenter)?

Wow can i fix the problem?

Maybe an other way to get the same result?

In esxupdate.log when checking compliance in VUM:

ValueError: VIBs ELX_bootbank_elx-esx-libelxima.so_12.0.1108.0-03 and ELX_bootbank_elx-esx-libelxima.so_12.0.1108.0-03 have unequal values of the 'payloads' attribute: '[elx-esx-libelxi: 1602.936 KB]' != '[elx-esx-libelxi: 1493.833 KB]

This is from a host that was installed with the 6.7U2 HPE Custom ISO then patched with the "critical" VUM baseline.  It seems the baseline installs a conflicting vib which breaks VUM compliance checks from that point forward.

If I remove the vib with esxcli software vib remove -n elx-esx-libelxima.so, it allows VUM compliance scanning to resume but then the host reports as non-compliant against the critical patch baseline.

Is there a definitive fix for this?  Can I somehow blacklist this vib within VUM?  We don't even need it -- we don't have this hardware!

Hi guys,

We have been a VMWare shop for quite some time and although had some stability issues in the past(VSphere 6.x with VDI), as a whole it has been a great and stable experience. Like everybody though, we have managers, budgets and with Microsoft pushing harder and harder down VMWare's throat, need to find a way to cut expenses in software/licensing.

Long story short, here is our current setup :

3 x VCenter servers ( running off Windows 2012 R2 ) for each different use case ( 1 x VCloud, 1 x VDI, 1 x Corp VM's)

12-16 hosts per VCenter so definitely not very heavy

VM's : ~2500 ( 1250 VDI, 1000 VCloud, 250 Corp )

Although I would rather not go that route, since we aren't pushing the boundaries of even 1 VCenter in terms of maximum VM's or Hosts, I was wondering if we could move to a clustered appliance(with 6.5) approach that would run all of the different scenarios under one roof. So the cluster would control the following :

44 hosts total (11 VCloud, 17 VDI, 16 Corp)

~ 2500 VM's

I am not worried about how VCenter can handle the tasks, but mostly if there could be an issue handling different tasks. Since we do Refresh on logoff for VDI and that keeps VCenter busy throughout the day(School environment, average of 1200-1500 students logging in and out ), VCloud vApps turning on and off every X amount of hours + all the networking backing, and then more simple Corp tasks for backups, vMotions.

If anyone has ideas, pros and cons, anything that could help us take the right decision, it would be greatly appreciated. I'd rather revamp or rethink our current environment and stick with VMware instead of dropping it and moving to another solution mostly because of cost.

Thanks everyone,

Ben

Hello all. I am currently a student working in a lab environment and am having some interesting issues with my ESXI upgrade.

A little more info about my environment, I have two Dell Poweredge R630's with ESXI 6.5 installed. I have two Vcenter 6.7 servers, one on each host and one 6.5 VCenter on a single host. These are not Windows boxes, They are the ESXI version (I dont know exactly what to call it).

So I was planning to upgrade each host from the VCenter on the opposing server. I uploaded the ESXI 6.7 ISO to Update Manager and created a baseline. I was entering the ESXI host into maintenance mode when Update Manager became completely blank. I could see the tabs for Baseline, updates, ESXI ISOs but there was nothing underneath, no menu or anything so I could not remediate the host as I planned.

After many refreshes of the web browser we decided to restart the VCenter server which is where we ran into many more problems. now we get the "503 Service Unavailable" which I usually brush off as just the server starting up but it has been well over an hour (I also restarted the 6.5 server and it has already come back up). I am able to console to the VCenter host via ESXI and can SSH to it as well.

root@photon-machine [ ~ ]# service-control --status

Running:

applmgmt lwsmd vmafdd vmcad vmdird vmdnsd vmonapi vmware-analytics vmware-cis-license vmware-eam vmware-pod vmware-postgres-archiver vmware-rhttpproxy vmware-statsmonitor vmware-sts-idmd vmware-stsd vmware-vapi-endpoint vmware-vmon vmware-vpostgres vsphere-client vsphere-ui

Stopped:

pschealth vmcam vmware-cm vmware-content-library vmware-imagebuilder vmware-mbcs vmware-netdumper vmware-perfcharts vmware-rbd-watchdog vmware-sca vmware-sps vmware-updatemgr vmware-vcha vmware-vpxd vmware-vpxd-svcs vmware-vsan-health vmware-vsm vsan-dps

I used this link and ran update manager and ran option 3

VMware Knowledge Base

I got a few errors but one that caught my eye was:

Error while reverting certificate for store : MACHINE_SSL_CERT

My theory so far are that I either did not get the correct 6.7 VCenter ISo (Do i need 6.7 u2?) or that the hostnames are being weird with having multiple VCenters. I always named the FQDN to be the IP address but in ESXI the hostname is listed as Photon-machine.

Wondering if anyone else has experienced my issues with VCenter and Update Manager?

Thanks in advance

James

Edit: Currently trying to do an upgrade via command line of the ESXI host. I originally thought I could not enable SSH without being at the console.

Edit#2: Got it upgraded with the offline bundle and SSH. Definitely a learning experience. Now time to see if my VCenter servers are back. I will mark the post as answered.

Message was edited by: James Bowman

Hi,

I have the following problem. Currently, I installed a new Vcenter Server Appliance in version 6.5.0.14000. I can not cope with sending notifications via VCSA that does not work.

My external mail server for sending notifications works fine. Notifications from other devices affect my inbox.

I would also like to emphasize that our mail server (mail.companydomain.com) is open to the IP address and ports of the VCSA server.

Configuration in the VCSA GUI is in the instructions (Vcenter General-> Mail) in the fields are filled in as follows:

• mail server - mail server address (mail.companydomain.com),

• mail sender - (helpdesk@companydomain.com)

When using the VCSA console, the command:

echo "Subject: sendmail test" | sendmail -v my.email@companydomain.com

the mail is forwarded to my mailbox.

This is how my sendmail works in VCSA. Where to look for a problem?  It's need any additional settings?

best wishes,

Hi all,

I suspect this is a bit of a silly question, but is it possible to deploy the vCloud Usage Meter VM on another hypervisor platform other than ESXi?

Thanks in advance

I need to add another identity source to my VCenter environment and having trouble. I've read other posts of people having similar trouble and I have not had much luck. I suspect there may be a few reasons why this isn't working and I need help understanding the why and if its even possible.

We have multiple identity sources configured and for sake of brevity I won't share them all.

These names are fictional for security sake..

We currently have an identity source using ldap setup as:

Name: business.college.edu

Server url: ldap://business.college.edu:389

Domain: business.college.edu

Alias: business

I would like to add an identity source to this site and instead of using ldap, I want to use ldaps. This is how I tried adding it as:

Name: business.college.edu

Server url: ldaps://business.college.edu:636 (I've also tried port 3269)

Domain: business.college.edu

Alias: business

I also include the SSL cert

Then I try adding it, I get the following error:

Check the network settings and make sure you have network access to the identity source

Is it possible to have 2 identity sources, one using ldap and the other ldaps?(We're working toward just using ldaps)?

Can the Name of the identity source be anything?

Do you see anything else that may be causing this?

Also, I when I edit the ldap identity source to look at those settings, The information in several fields - particularly the AD information flashes and shows me different results. For example, for Base distinguished name for users, instead of showing (what I think it is set to) DC=business,DC=college,DC=edu, it switches to DC=college,DC=edu.

Is that normal? I suspect that this is because I am logged in with an account in the business.college.edu domain and don't have access to the college.edu domain, but not sure... Either way, I am entering credentials with an account with domain admin rights on the business.college.edu domain. I also, suspect that the true settings for the ldap identity source may be different than I understand and what I see may not be good and the reason why my attempt at adding an ldaps identity source is failing.

Any and all help that gets me closer to a solution or better understanding is appreciated!

James

Hi, I did English using a translator.

I have problem unresolved matters.

I made vCenter in Centos 6.5.

I experienced many of problem.

<running vCenter>

first, I faced initializing SMTP error running vCenter.

Second, Failed services in runlevel 3 : sendmail vmware-vpxd

<after vCenter Login>

third, initialize.... failed .

I attach error image capture.

First Error.

Second Error

I need of solution this problem.

Please, help me,

This is the error I get while running the migration assistant on my Windows 5.5 vCenter server.  VMware update manager is working correctly so my guess is that the database is available and working.

Error messages: Error: Unable to connect to VMware Update Manager Database, Cannot proceed with migration

Resolution: Please check that VMware Update Manager Database is reachable before migration and Please make sure Migration Assistant is launched under service account for VMware Update Manager

My guess is that my current account does not have enough permissions to access the database.  I'm currently running the migration assistant with my admin account which is a domain admin account with administrator rights locally on the machine.