In most cases you can simply delete such files. However, it's always advisable to double check whether the file is still required.
This can be done by e.g. checking the file's time stamp, and/or checking whether the file appears in the VM's *.log file(s).
Unless you are 100% sure, I'd recommend that you move the zombie file to another folder, and if everything continues to work as expected, delete it at a later time.
André
Hello
I have installed oneview for vcenter v9.1 for vcenter 6.5u2. configuration is done but I cant see in web client. I did some research and found out url string in extension is not configured right.
it should be like this: "https://{oneviewFQDNhere}:3504/static/vsphere-web-client/com.hp.ov4vc.ngc.all.v6.0.zip"
but its:"https://localhost.localdomain:3504/static/vsphere-web-client/com.hpe.ov4vc.zip"
How can edit this string?
Welcome to the Community,
This can be tricky. As a first step make sure that - in the Virtual Network Editor - the Brigded Network has a dedicated physical adapter (your Wifi adapter) assigned to it, rather than "Automatic".
Also check whether your wireless router/access point allows multiple MAC addresses (Host + VM) on a single connection.
André
Resolved, I don't know how.
vRO instance embedded in vRA is accessible on port 443 instead of port 8281 for standalone vRO appliance.
However, even if you register the embedded vRO as vCenter server extension, you won't be able to use it to launch vRO workflows from vSphere Web client UI. The reason is simple - embedded vRO is configured with vRA authentication, and vSphere Web client calls vRO REST API using SAML tokens (vCenter SSO) for authentication. As vRA authentication and vCenter SSO authentication are incompatible, REST calls made by vSphere Web client to vRO REST API will fail.
In short, to use vRO integration with vSphere Web client, you need to have a standalone vRO appliance configured with vSphere authentication against the same vCenter SSO instance used by Web client. Not very convenient for customers who want to leverage single vRO instance for both vSphere and vRA use cases, but that's the current situation.
Will need to start at the beginning to see all your parameters. Why would you be installing a version of vRA that is two behind the current release?
There will be no live migration possible (if you mean vMotion) between those two versions. Also, VMware Converter isn't probably the best tool for this job. You can simply move that VM on some form of storage from source to destination, or use a third party tool (depending on your license level) to do this.
Thanks for that! That's useful and makes sense.
So I guess I have two final questions - can I have two vRO registered to a vCenter without issue? I don't mind deploying a standalone vRO but want to make sure I can register vCenter to it and then also use the extension for vCenter without stepping on my vRA vCO setup.
Additionally, do you know whether or not vRO (7.4, but I can try any version) has a valid extension for the vCenter 6.5 web client (flex is fine)? Been testing in a lab and haven't had a lot of success getting the extension to register.
Thanks!
Hi There,
On my new laptop which is windows 10, I am running vmware workstation 10.0.7 on which win2008 servicer is running. After i start the VM, I could not click anything inside the vm see below screenshot or nither allows to minimize the screen or open any software Byt this work on my another laptop windows 7.
v
On the first question - yes, you can have two or more vRO instances registered as extension to a same vCenter instance. There will be a single extension com.vmware.vco, with different vROs having their URLs in client and server array properties within the extension
On the second question - yes, vRO 7.4 should work just fine with vSphere 6.5 Flex-based Web client. It has a known issue with vSphere 6.7 Web client, but there is another build available at https://communities.vmware.com/docs/DOC-35002 that is compatible with vSphere 6.7
What kind of problems do you have with vSphere 6.5? Is is that the workflow fails, or after you register the extension you don't see vRO workflows in the vSphere Web client UI?
Hello.
There are two patterns of "DHCP" and "IP Pool" in the IP address assignment method of VTEP,
Which one is recommended?
As far as I looked
I think both automatic and manual IP address assignment to VTEP is possible.
If there is no difference, IP Pool that does not need to build a DHCP server thinks it is the best.
Reference materials
https://communities.vmware.com/docs/DOC-27683
→ There is no description about IP Pool
Just a follow up question to this.. Is it possible to perform the deletion of Invalid (due to deletion) VMs inside of protection group using PowerCLI? Since we've moved to a CI/CD model the manual cleanup of deleted VMs is painful thru the GUI. I've worked with Ben Meadowcroft's SRM PowerCLI cmdlets but it doesn't seem to allow protection removal on deleted/invalid VMs.
7.2 is the version in infrastructure I’m going to work on, I am staring from scratch as I’m beginner to vRA so I’ll upgtade it to latest In next step.
Though self signed certificates were generated in wizard but I’m not seeing certificate validation (as pic attached). Something is wrong with certificates I need to check.
Hi,
I have quite big problem with vCenter server installed on Windows 2012 R2. All was working fine, there was no software updates, but now since few days most of the VMware services can not be started at all:
Services status:
Name StartType Status
---- - -------- ------
VMWareAfdService Automatic Stopped
VMwareCAFManagementAgentHost Automatic Running
VMWareCertificateService Automatic Stopped
vmware-cis-config Automatic Stopped
VMwareDirectoryService Automatic Stopped
VMwareDNSService Automatic Stopped
VMwareIdentityMgmtService Automatic Stopped
vmware-psc-client Automatic Stopped
VMwareSTS Automatic Stopped
vmware-ufad-vci Automatic Running
When trying to connect to the DB:
C:\Program Files\VMware\vCenter Server\vPostgres\bin>psql -d VCDB -U vc
psql: could not connect to server: Connection refused (0x0000274D/10061)
Is the server running on host "localhost" (127.0.0.1) and accepting
TCP/IP connections on port 5432?
could not connect to server: Connection refused (0x0000274D/10061)
Is the server running on host "localhost" (::1) and accepting
TCP/IP connections on port 5432?
or when trying to list all services:
C:\Program Files\VMware\vCenter Server\bin>service-control --list
Traceback (most recent call last):
File "C:\Program Files\VMware\vCenter Server\bin\\service-control", line 14, in <module>
from cis.svcscfg import (platform, isCorePnidService, loadServicesFile,
ImportError: cannot import name platform
Additionally vpdx.log has been attached.
Any advice what is wrong and how to fix it?
BR
Szczepan
If you're doing self signed through the wizard, chances are the problem is not there so we'll need to look elsewhere. What version of Windows are you using for the IaaS box?
VMware ESXi 5.5: I'm trying to build an OVA with a small included ISO file. I WANT to keep this ISO in the build (googling for a solution on this has returned numerous threads on how to remove the ISO from the OVA, I'm not interested in this). I DID check the box to include image files when I exported the VM to OVA. When I try to deploy a new VM from the OVA, it says it can't find the ISO file. If I extract the OVA, I can see the ISO file, with the same name as the one it is saying does not exist. Initially the ISO image file was in the same folder as the VM. Is this a bug in 5.5? Do I need to upgrade? Am I doing something wrong? Seems like if they give you the option to include ISOs, it should work...
We're going on vacation and need to be able to access our home server. We currrently have a website hosted on one of our vms so how would i configure this to work if 443 and 80 are already being used to connect to a website? Is there some way to disable https and use http with a different port? Thanks in advance.
What version of vROps are you using?
Hi,
May be I can help you here.
The HA buffer in vRealize Operations 6.7 is not gone. It is auto-calculated and subtracted from Total Raw Capacity.
Hence Usable Capacity = Total Capacity - HA Buffers out of the box and you do not need to set any configurations or policies to consider this buffer.
With 6.7, HA Buffers are automatically read from your HA Admission Control Policy. Since HA buffers are defined for Reserving Capacity in case of HA failures, the source of truth for these buffers are in vCenter HA configuration. Hence if you need to reserve capacity of HA Failover, this should be configured in vCenter HA Admission Control Setting. Have Admission Control disabled or not configured and buffering HA capacity just in vROps is not a good practice since while you think you have enough capacity on a cluster from vROps point of View, your availability policy will not honor that.
Hence in 6.7 we made this configuration out of box and we honour your HA policies based on that
Please refer to out of box "Utilization Overview Dashboard" to get more details.
Hope this helps. If you have more questions or feedback on vRealize Operations 6.7, feel free to reach out to me on duas@vmware.com
Regards
Sunny
Excellent info.
My issue is that I had a /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com.vmware.vco-7.5.0 or something similar that I deleted per the link you sent (I had found that a bit ago).
I set my vRO up for vSphere authentication, it works. I open the Orchestrator Client (java) and run the register workflow and then register extension workflow to this VCSA and I do not see anything come back into the vsphere-client-serenity folder on the VCSA and no extension in web client.
I can browse the VCSA from with Orchestrator Client, so that part is working at least but not registration within vCenter.
root@kcloud1vcsa1 [ /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity ]# ls
com.vmware.nsx.ui.h5-6.4.0.7564187 com.vmware.vsan.health-6.7.0.11000
com.vmware.nsx.ui.h5-6.4.1.8599035 com.vmware.vShieldManager-6.4.0.7564187
com.vmware.vcHms-6.5.1.656014425 com.vmware.vShieldManager-6.4.1.8599035
com.vmware.vrops.install-6.7.0.11000 com.vmware.vsphere.client.h5vsan-6.7.0.11000
com.vmware.vsan.health-6.6.1.13000
Thanks for the insight!