Hi Everyone,

We are moving down the vSphere 6 road. We are building hosts and vCenter. I have a post install script that I run to do various post install things and when it runs the first thing it does is connect to the host via connect-viserver to the host in questions and connects via the root usename and password. This failed with an error: Permission to perform this operation was denied. Required privilege 'System.View' on managed object with id 'Folder-ha-folder-root'

I have never seen this before and I am not sure what to do?

thoughts?

I run several monitoring scripts (that I inherited) from vMA appliances. We patched our vCenters with vSphereTlsReconfigurator-6.5 so it only listens using TLSv1.1 & TLSv1.2.

Now our scripts no longer connect using Java app "Remote host closed connection during handshake" or Perl scipt:"Server version is unavailable at https://servername:443/sdk/vimService.wsdl"

I suspect I need to update my SDKs - Any guidance on resolving? Guidance on updating SDK on VMware vMA?

I have a vSphere environment

2 ESXi hosts

Enable vSphere HA

1 VM

Right-Click the VM, Select Fault Tolerance > Turn on Fault Tolerance

Hi there,

I have this (for me) weird issue with vRealize Business For Cloud. While I see all business units in my overview, it only shows VMs inside half of them. All the folders that I want to be included are on the same hierarchy level, but just some VMs are discovered in these folders, and some are not. When looking at the folder level in vCenter, all the VMs are thereand the security access rights for the vRB service account are the same for every folder (inherited).

Interestingly enough, the amount of shown VMs changes. It used to be 230, then it went down to 98, then up again to 230, down to 98 and yesterday up to 102. Can't figure it out, any idea where to look?

Best,

Dave

Version 7.4.0.19475

hi,

what is the difference between vmkernel and hypervisor?

vmkernel is the core of hyperisor?

is this the reason why vmkernel control the vmotion,iscsi,nfs and management acces?

tnx

Hi,

I am looking for simple script to collect the Orphaned disks in my vcenter.

where my most of the VMs will have snapshots too, so need to get the report exclude of the snapshot disks.

i found from LuCD (Orphaned Files Revisited - LucD notes ) it is high advanced.

so please help me with simple method to collect the information.

I'm having this problem with a new cloud hosted identity manager tenant.  I am unable to find any documentation thus far.  This is happening on both my iPhone 7 and iPad Mini 2.  I've tried uninstalling the workspace one app, reinstalling, restarting the devices, etc.  Factory wipe isn't an option so I haven't tried that yet.  Does anybody have advice?  The weird part is that it was working for a while on my iPad and then stopped.

These devices were enrolled in a separate AirWatch/Identity Manager deployment in the past.  I verified that they were removed from inventory and the MDM profile was removed.  I found this link, which seems to describe the problem, but does not apply to me.  The "Remove account" option no longer exists in the WSOne App.

Workspace ONE Common Errors and Best Practices - VMware TestDrive Support

Edit: While Workspace One functions from the Chrome browser on a Win10 desktop, I get a similar error when trying the Native WS One App.  It leads me to believe something is sticking around from the prior IDM connection, but I'm not sure where to clear it out.  Any suggestions?

Edit 2: Removing the WS One App on Win 10 and reinstalling cleared it up.  Still no such luck for IOS though

Hello,

i switched to a new Monitor with a resolution of 2560 x 1440.

On my Windows 10 host, i set a user scale for char size of 115 %.

When i start my Windows 10 guest, the user scale for char size is set to 125 %. Which is too big.

When i now set the scale to 110, then on next restart, VMWare Tools resets this to 125 %.

How to get also 115 % in my Windows 10 guest

Thank you community (support).

Hi everybody,

I'm having some trouble with VCSA 6.0u2.

Let's start from the beginning: in the first place, pointing the browser to vCenter FQDN brought a page with an error like this: 503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x7f009c095810] _serverNamespace = / _isRedirect = false _pipeName =/var/run/vmware/vpxd-webserver-pipe).

Then I tried to login as root directly to the VCSA VM, but the system refused to allow me in.

I followed this KB to reset the password and also found out that /storage/log and /dev/sda3 were filled with unrotated logs and a really big audit.log.

Cleaned up, applied suggestions from this KB, rebooted and then I could log in normally to the appliance vm, but still no luck with the web side.

So I checked the stopped services and respective logs, and found the entry "invalid credentials LDAP Error 49" in inv-svc.log, so I followed this other KB to reset the password.

Now vmware-invsvc started normally and web client started to show the login page (but giving a blank page after logging in); I checked again the stopped services and tried to start them one by one, and noticed that the one crashing was vmware-eam and that eam.properties was empty.

I rebuilt the file with the help of this thread, but vmware-eam still crashes and I have no clue about how to solve.

This is the output of service-control --start vmware-eam

INFO:root:Service: vmware-eam, Action: start
Service: vmware-eam, Action: start
2018-07-12T14:44:02.873Z   Running command: ['/sbin/chkconfig', u'vmware-eam']
2018-07-12T14:44:02.929Z   Done running command
2018-07-12T14:44:02.929Z   Running command: ['/sbin/service', u'vmware-eam', 'status']
2018-07-12T14:44:03.003Z   Done running command
2018-07-12T14:44:03.003Z   Running command: ['/sbin/chkconfig', '--force', u'vmware-eam', 'on']
2018-07-12T14:44:03.059Z   Done running command
2018-07-12T14:44:03.059Z   Running command: ['/sbin/service', u'vmware-eam', 'start']
2018-07-12T14:44:07.837Z   Done running command
2018-07-12T14:44:07.837Z   Invoked command: ['/sbin/service', u'vmware-eam', 'start']
2018-07-12T14:44:07.837Z   RC = 1
Stdout = Starting VMware ESX Agent Manager...
Waiting for VMware ESX Agent Manager.......
WARNING: VMware ESX Agent Manager may have failed to start.
Last login: Thu Jul 12 14:42:09 UTC 2018

Stderr =
2018-07-12T14:44:07.837Z   {    "resolution": null,    "detail": [        {            "args": [                "Command: ['/sbin/service', u'vmware-eam', 'start']\nStderr: "            ],            "id": "install.ciscommon.command.errinvoke",            "localized": "An error occurred while invoking external command : 'Command: ['/sbin/service', u'vmware-eam', 'start']\nStderr: '",            "translatable": "An error occurred while invoking external command : '%(0)s'"        }    ],    "componentKey": null,    "problemId": null
}
ERROR:root:Unable to start service vmware-eam, Exception: {    "resolution": null,    "detail": [        {            "args": [                "vmware-eam"            ],            "id": "install.ciscommon.service.failstart",            "localized": "An error occurred while starting service 'vmware-eam'",            "translatable": "An error occurred while starting service '%(0)s'"        }    ],    "componentKey": null,    "problemId": null
}
Unable to start service vmware-eam, Exception: {    "resolution": null,    "detail": [        {            "args": [                "vmware-eam"            ],            "id": "install.ciscommon.service.failstart",            "localized": "An error occurred while starting service 'vmware-eam'",            "translatable": "An error occurred while starting service '%(0)s'"        }    ],    "componentKey": null,    "problemId": null
}

This is the log entry of /var/log/vmware/eam/wrapper.log related to the service start

STATUS | wrapper  | 2018/07/12 14:44:03 | --> Wrapper Started as Daemon
STATUS | wrapper  | 2018/07/12 14:44:03 | Java Service Wrapper Professional Edition 64-bit 3.5.24
STATUS | wrapper  | 2018/07/12 14:44:03 |   Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper  | 2018/07/12 14:44:03 |     http://wrapper.tanukisoftware.com
STATUS | wrapper  | 2018/07/12 14:44:03 |   Licensed to VMware Global, Inc. for VMware vCenter ESX Agent Manager
STATUS | wrapper  | 2018/07/12 14:44:03 |
INFO   | wrapper  | 2018/07/12 14:44:03 | Event Command 'wrapper_start': Command line[0] : /usr/sbin/cloudvm-ram-size
INFO   | wrapper  | 2018/07/12 14:44:03 | Event Command 'wrapper_start': Command line[1] : -J
INFO   | wrapper  | 2018/07/12 14:44:03 | Event Command 'wrapper_start': Command line[2] : vmware-eam
INFO   | wrapper  | 2018/07/12 14:44:03 | Event Command 'wrapper_start': Command line[3] : -O
INFO   | wrapper  | 2018/07/12 14:44:03 | Event Command 'wrapper_start': Command line[4] : /etc/vmware/java/vmware-eam_jvm.conf
INFO   | wrapper  | 2018/07/12 14:44:03 | Event Command 'wrapper_start': Command launched (pid: 3617), blocking for up to 3600 seconds...
INFO   | wrapper  | 2018/07/12 14:44:03 | Event Command 'wrapper_start': Command completed with exit code: 0
INFO   | wrapper  | 2018/07/12 14:44:03 | Event Command 'wrapper_start': Command completed with exit code: 0  Continuing.
INFO   | wrapper  | 2018/07/12 14:44:03 | Event Command 'jvm_prelaunch': Command line[0] : /opt/vmware/bin/python
INFO   | wrapper  | 2018/07/12 14:44:03 | Event Command 'jvm_prelaunch': Command line[1] : ../wrapper/bin/update_pnid.py
INFO   | wrapper  | 2018/07/12 14:44:03 | Event Command 'jvm_prelaunch': Command line[2] :
INFO   | wrapper  | 2018/07/12 14:44:03 | Event Command 'jvm_prelaunch': Command line[3] :
INFO   | wrapper  | 2018/07/12 14:44:03 | Event Command 'jvm_prelaunch': Command line[4] :
INFO   | wrapper  | 2018/07/12 14:44:03 | Event Command 'jvm_prelaunch': Command launched (pid: 3620), blocking for up to 15 seconds...
INFO   | wrapper  | 2018/07/12 14:44:03 | Event Command 'jvm_prelaunch': Command completed with exit code: 0
INFO   | wrapper  | 2018/07/12 14:44:03 | Event Command 'jvm_prelaunch': Command completed with exit code: 0  Continuing.
STATUS | wrapper  | 2018/07/12 14:44:03 | Launching a JVM...
INFO   | jvm 1    | 2018/07/12 14:44:03 | Picked up JAVA_TOOL_OPTIONS: -Xms32M -Xmx128M
INFO   | jvm 1    | 2018/07/12 14:44:03 | WrapperManager: Initializing...
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp:
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error: Encountered an error running main:
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'stsCertManager' defined in class path resource [eam-server-beans.xml]: Cannot resolve reference to bean 'cmClient' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'cmClient' defined in class path resource [eam-server-beans.xml]: Cannot resolve reference to bean 'vcTrustStore' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'vcTrustStore' defined in class path resource [eam-server-beans.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public static java.security.KeyStore com.vmware.eam.identity.KeyStoreFactory.createKeyStore(java.lang.String,java.io.File,java.lang.String,java.lang.String)] threw exception; nested exception is com.vmware.eam.EamException: Unsupported keystore type: VKS
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:275)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:104)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:474)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:342)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:901)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:815)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at java.security.AccessController.doPrivileged(Native Method)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:220)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:254)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:254)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:254)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:429)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:729)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:381)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:139)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:83)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at com.vmware.eam.util.Main.main(Main.java:50)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at java.lang.reflect.Method.invoke(Unknown Source)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:290)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at java.lang.Thread.run(Unknown Source)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error: Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'cmClient' defined in class path resource [eam-server-beans.xml]: Cannot resolve reference to bean 'vcTrustStore' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'vcTrustStore' defined in class path resource [eam-server-beans.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public static java.security.KeyStore com.vmware.eam.identity.KeyStoreFactory.createKeyStore(java.lang.String,java.io.File,java.lang.String,java.lang.String)] threw exception; nested exception is com.vmware.eam.EamException: Unsupported keystore type: VKS
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:275)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:104)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:474)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:342)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:901)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:815)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at java.security.AccessController.doPrivileged(Native Method)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:220)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:269)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       ... 35 more
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error: Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'vcTrustStore' defined in class path resource [eam-server-beans.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public static java.security.KeyStore com.vmware.eam.identity.KeyStoreFactory.createKeyStore(java.lang.String,java.io.File,java.lang.String,java.lang.String)] threw exception; nested exception is com.vmware.eam.EamException: Unsupported keystore type: VKS
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:423)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:901)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:815)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at java.security.AccessController.doPrivileged(Native Method)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:220)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:269)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       ... 50 more
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error: Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public static java.security.KeyStore com.vmware.eam.identity.KeyStoreFactory.createKeyStore(java.lang.String,java.io.File,java.lang.String,java.lang.String)] threw exception; nested exception is com.vmware.eam.EamException: Unsupported keystore type: VKS
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:127)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:414)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       ... 62 more
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error: Caused by: com.vmware.eam.EamException: Unsupported keystore type: VKS
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at com.vmware.eam.identity.KeyStoreFactory.createKeyStore(KeyStoreFactory.java:48)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at java.lang.reflect.Method.invoke(Unknown Source)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:115)
INFO   | jvm 1    | 2018/07/12 14:44:05 | WrapperSimpleApp Error:       ... 63 more
STATUS | wrapper  | 2018/07/12 14:44:07 | <-- Wrapper Stopped

And this is /var/log/vmware/eam/eam.log

2018-07-12T14:44:04.322Z |  INFO | WrapperSimpleAppMain | Main.java | 47 | Initializing Spring from 'standalone.xml' and 'eam.properties'
2018-07-12T14:44:04.365Z |  INFO | WrapperSimpleAppMain | AbstractApplicationContext.java | 412 | Refreshing org.springframework.context.support.ClassPathXmlApplicationContext@8461829: display name [org.springframework.context.support.ClassPathXmlApplicationContext@8461829]; startup date [Thu Jul 12 14:44:04 UTC 2018]; root of context hierarchy
2018-07-12T14:44:04.487Z |  INFO | WrapperSimpleAppMain | XmlBeanDefinitionReader.java | 323 | Loading XML bean definitions from class path resource [standalone.xml]
2018-07-12T14:44:04.638Z |  INFO | WrapperSimpleAppMain | XmlBeanDefinitionReader.java | 323 | Loading XML bean definitions from class path resource [eam-server-beans.xml]
2018-07-12T14:44:04.780Z |  INFO | WrapperSimpleAppMain | AbstractApplicationContext.java | 427 | Bean factory for application context [org.springframework.context.support.ClassPathXmlApplicationContext@8461829]: org.springframework.beans.factory.support.DefaultListableBeanFactory@8e89bed
2018-07-12T14:44:04.949Z |  INFO | WrapperSimpleAppMain | PropertiesLoaderSupport.java | 178 | Loading properties file from class path resource [eam.properties]
2018-07-12T14:44:05.014Z |  INFO | WrapperSimpleAppMain | DefaultListableBeanFactory.java | 414 | Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@8e89bed: defining beans [org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0,commonMapStore,vibServices,esxAgentMgr,vcTrustStore,eamKeyStore,eamKeyAccess,vimAndVumConnectionExecutor,vpxdConnection,vumConnection,vcOptions,serverAddr,serverAddrDepr,serverUrl,serverUrlDepr,vcListener,l10n,httpNfcLeaseTimeoutHandler,nameManager,vcDatastoreManager,vcEventManager,vcKeyValueStore,messageSource,vibServer,vibServerDepr,vibPackageDepot,vibPackageDepotDepr,secureHostsStartVersion,vibPackageDepots,vcInventory,springContext,scanForUnknownAgentVms,cmClient,stsCertManager,scheduler,heathStatusTaskScheduler,vmodlContext,versionFinder,clientAuthConnectionExecutor,clientAuthConnection,clientAuthenticator,localizationFilter,firstMobStep,mobConnectionExecutor,mobConnection,mobAuthenticator,localClient,localCorrelator,localFilterStartStep,localCompletionStep,sessionManager,dispatcher,adapterServer,eamVersion,bodyHandler,eamVersion2,bodyHandlerVersion2,eamVersion2_5,bodyHandlerVersion2_5,eamVersion3,bodyHandlerVersion3,eamVersion6,bodyHandlerVersion6,internalEamVersion1,internalBodyHandlerVersion1,internalEamVersion2,internalBodyHandlerVersion2,internalEamVersion2_5,internalBodyHandlerVersion2_5,internalEamVersion3,internalBodyHandlerVersion3,internalEamVersion6,internalBodyHandlerVersion6,httpResponseCorrelator,firstStep,validationStartStep,completionStep,filterStartStep,invocationStep,continuerStep,rejectedHandler,executor,httpServerEndpoint,listener,mob,jspServlet,fileServlet,health,log4j,managementUi,cmHealthServlet,cmResourceBundleServlet,vmomiService,mobService,jspService,filesService,healthService,managementService,vibService,vibdService,cmHealthService,cmResourceBundleService,logConfiguratorManualFilter,logConfiguratorAutoFilter,httpServer]; root of factory hierarchy
2018-07-12T14:44:05.026Z |  INFO | WrapperSimpleAppMain | DefaultSingletonBeanRegistry.java | 396 | Destroying singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@8e89bed: defining beans [org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0,commonMapStore,vibServices,esxAgentMgr,vcTrustStore,eamKeyStore,eamKeyAccess,vimAndVumConnectionExecutor,vpxdConnection,vumConnection,vcOptions,serverAddr,serverAddrDepr,serverUrl,serverUrlDepr,vcListener,l10n,httpNfcLeaseTimeoutHandler,nameManager,vcDatastoreManager,vcEventManager,vcKeyValueStore,messageSource,vibServer,vibServerDepr,vibPackageDepot,vibPackageDepotDepr,secureHostsStartVersion,vibPackageDepots,vcInventory,springContext,scanForUnknownAgentVms,cmClient,stsCertManager,scheduler,heathStatusTaskScheduler,vmodlContext,versionFinder,clientAuthConnectionExecutor,clientAuthConnection,clientAuthenticator,localizationFilter,firstMobStep,mobConnectionExecutor,mobConnection,mobAuthenticator,localClient,localCorrelator,localFilterStartStep,localCompletionStep,sessionManager,dispatcher,adapterServer,eamVersion,bodyHandler,eamVersion2,bodyHandlerVersion2,eamVersion2_5,bodyHandlerVersion2_5,eamVersion3,bodyHandlerVersion3,eamVersion6,bodyHandlerVersion6,internalEamVersion1,internalBodyHandlerVersion1,internalEamVersion2,internalBodyHandlerVersion2,internalEamVersion2_5,internalBodyHandlerVersion2_5,internalEamVersion3,internalBodyHandlerVersion3,internalEamVersion6,internalBodyHandlerVersion6,httpResponseCorrelator,firstStep,validationStartStep,completionStep,filterStartStep,invocationStep,continuerStep,rejectedHandler,executor,httpServerEndpoint,listener,mob,jspServlet,fileServlet,health,log4j,managementUi,cmHealthServlet,cmResourceBundleServlet,vmomiService,mobService,jspService,filesService,healthService,managementService,vibService,vibdService,cmHealthService,cmResourceBundleService,logConfiguratorManualFilter,logConfiguratorAutoFilter,httpServer]; root of factory hierarchy

Hope somebody can help

What I wanted was

VSPHERE 5.5 is CC certified, but I want to know whether CC certification will be passed or not.

Some sites do not allow installation if they are CC certified. Is there anything you can do to respond to this?

Therefore, you can not install VSPHERE 6.5 on that site.

I would like to know if VSPHERE 6.5 has plans for CC certification.

I know this question could also be considered a vRealize Automation question. I posted in the vRO forums because vRO is the engine to get these done.

My question is this: Listed below are some use cases I have implemented. What are some other use cases for vRA/vRO?

I am especially interested in Infrastructure as a Service but feel free to post any use case!

What I do today:

VM Provisioning (Windows 2012 R2, Windows 2016, RHEL, Other Linux)

Run REST API against RHEL Satellite

VM Disk Add/Remove w/ vAPI commands against OS for Online and Extends

Add Memory to VM

Add CPU to VM

Add to specific vSphere Folder (for EMC Avamar Backups management)

vmnic Modifications, Add, Remove

VM Tagging

Guest OS Modifications via (vAPI); Example: Restart a Service

VMtools Upgrades

VM Hardware Version Upgrades

MS Cluster - Shutdown/Startup

Change Guest-OS Type

Cisco UCSM API Calls (Add VLAN to Port Channel)

Cisco UCS Central API Calls (Roll out new template)

Cisco UCS Director API Calls (Mainly used to gather information)

Fabric Zone Creation - Brocade & Cisco MDS

PureStorage - Multiple: volume creation, protection groups, snapshots, etc

EMC Isilon - Create departmental shares

SSL Certificate Generation

VMware SRM Integration - configure VM for DR and remove when decomissioned

BIG IP F5 - Multiple tasks; example: Add to Load Balancing Group and Create Redirects

Active Directory (CRUD)

DNS (CRUD)

Integrations:

Thycotic for password/username

Solarwinds IPAM for IP Management

SNOW (ServiceNow)

Almost all of the above is done directly through SNOW catalog requests.

Any other Automation\Orchestration ideas out there? Would be cool to start a discussion on ideas/possibilities.

We haven't integrated Chef, Puppet, Ansible or Salt run books yet but are working towards it.

What has been useful to you or your organization?

It seems when adding features to vRA, accompanying workflows to manage those features in vRO are slow to come by. The new component profiles have been around for a few releases, but I still cannot find anyway to update them programmaticlly from vRO. We want to use the image profiles to allow for more dynamic blueprints. The issue is we have over 100 templates to use and manually adding them to the GUI image profile value sets is very tedious.

The feature was added in vRA:

But there is no inventory item in vRO that reflects them:

When can we expect to have workflows or actions in vRO that match this new feature? It would really help us out to be able to create these entries using a for loop in vRO and then update them programmatically using vRO over time, as we update the templates.

Had workers in our office, shut down power without telling us and our UPS failed. Now my VMware keeps crashing. Says that the Operation on file failed.  Help! Running Windows 7 on Mac

I'm having issues with backing up Windows 2008 R2 VM using data protection... it stucks at 92 % and lasts like forever, unless I cancel the job. Does anyone have solution to this already? I've seen a lot from the community...

The question is recover point for storage replication whether we can replicate specific datastore luns with SRM combinations using current recoverpoint rather than whole vmware clusters.

Example: 4 lun allocated in vmware cluster and i want to replicate 2 luns only not all 4 luns so that my VM in 2 luns can be recovered on 2 nd site not all vms in the cluster. Would that be possible?

I have seen the below two lines in the SRM Best practices document, that makes me confuse.

Placeholder datastores must meet certain criteria.

Если я правильно понимаю то vSwitch не использует для коммутации таблицу коммутации как в обычном физическом свиче. Вместо этого он просто смотрит на сами виртуалки и на то какие MAC адреса на их виртуальных интерфейсах которыми они включены в сам свич.

Однако, в моем случае, одна из виртуалок создает тоннель который соединяется мостом с этим самым интерфейсом и ожидается что таким образом можно будет продлить L2 сегмент. Однако, как только какая либо машинка хочет отправить пакет другой машинке которая находится за тоннелем то дальше vSwitch эти пакеты не ходят. Видимо из за того, что в этом пакете, в поле disitination mac находится MAC адрес который сам vSwitch не видит ни в одной ВМки подключенной к нему.

Конечно если включить Promiscuous mode то все начинает работать. Однако, это не выход.

Можно ли как то заставить vSwitch работать так же как физический свич? то есть заставить его работать используя таблицу коммутации вместо того, что бы смотреть на мак адреса подключенных к нему ВМок?

Hello,

I have some questions about a configuration on my ESX cluster.

So, here my configuration :

3 HP servers with VMware ESXi, 6.7.0, 8169922

A vcsa on 6.7 version

On each ESX, we have 2 network cards with 4 nics. The configuration is :

2 actives nic (1 per network card) for the management network ; load balancing with "Route based on the originating virtual port"

2 actives nic (1 per network card) for vMotion ; load balancing with "Route based on the originating virtual port"

2 actives nic (1 per network card) for virtual machines traffic ; load balancing with "Route based on IP hash" and configuration of etherchannel on Cisco side.

The last two nics are free, maybe we use them later for vSphere replication.

All the nics are connected to a Cisco switch.

My question is :

why I have an important loss packets on a VM Windows 2016 or Windows 2008 when I use "Route based on IP hash" ?

we have seen loss packets with tools like mtr command line or smokeping software ; we are loosing packets during a test copy of 26go folder.

Nothing with a linux VM (redhat).

when I change the load balancing mode for the virtual machine traffic to the option "Route based on the originating virtual port", we don't see loss packet, everything is fine on Windows 2008 or Windows 2016.

Do I have to change some options in the VMXnet driver ?

What's the problem with Windows ? It's not compatible with "Route based on IP hash" ?

Thank you for your replies.

Is there a way / guide on how to set up Horizon 7.5 connection server(s) in a failover configuration?

Our organization has users connected 24/7 and it would be nice to be able to have automatic failover.

The problem is when the server needs a reboot or updates we can't  have users get kicked out.

На хосте в configure есть табличка со всеми VM, где у каждой можно поставить, будет ли она стартовать в след за  хостом. Если включено HA то все эти настройки серые. Настройки HA у меня следующие

host failure  -restart VMs

host isolation - shut down and restart VMs

Недавно вырубились все хосты по электропитанию, последовательность их включения сказать не могу(меня не было в конторе). Все машины стартовали. Возможно, что одна выключенная на момент аварии машина не стартовала, что мне и требуется.

Достаточно ли выключить VM, чтоб она потом не стартанула вместе с хостом?

Может сетевушки еще отключать дополнительно?

Есть ли способ выставить принудительно "не стартовать" при включенном HA?

Спасибо.

Hello, I am trying to connect ESXi to my storage server "NAS4Free" over iSCSI connection. I have 4 gigabit nic ports on the storage server and 4 gigabit nic ports on the HP server (hosting the ESXi), and all 8 ports are connected to a central switch. I have finished the setup for the storage server side providing iSCSI over 4 IPs in 4 different subnets as recommended.

Now, on ESXi side, I am planning to host a pfSense virtual machine as firewall. Therefore, the network setup should have a WAN and a LAN interfaces. So I am not sure how many virtual switches and port groups should I add to ESXi to be able to satisfy the pfSense requirements of WAN and LAN and the 4 for the iSCSI.

Currently, I have the default vSwitch0 added and connected to vmnic0. I have added the remaining 3 vmnic1 to vmnic3.

I really appreciate your advises and thanks in advance.