flynmooney's Posts

I opened a ticket with VMware because all three different ways I found to change the owner were zeroing out the daily cost and cost to date. Out of that here is a workflow that changes the owner.... See more...
I opened a ticket with VMware because all three different ways I found to change the owner were zeroing out the daily cost and cost to date. Out of that here is a workflow that changes the owner. There are two input requirements: Name of the virtual machine Name of the user   There is also an attribute (vCACCAFEHost) that needs to be set prior to running the workflow.
I did the upgrade to 6.2.1 without any issues in our test environment.  All of our custom resources are still available and work.  I did have to go into vCO configuator and manually update the da... See more...
I did the upgrade to 6.2.1 without any issues in our test environment.  All of our custom resources are still available and work.  I did have to go into vCO configuator and manually update the database by clicking a link.
Nothing changed in regard to this on 6.2 that I can find.
I found this post http://dailyhypervisor.com/vcloud-automation-center-active-directory-machine-account-management-extension/ which might solve your issues.
I ran into the problem with (invalid credentials).  I had the login strategy set to "Session per user" changed to "Share a unique session" and restarted the vCO service and it worked like a charm... See more...
I ran into the problem with (invalid credentials).  I had the login strategy set to "Session per user" changed to "Share a unique session" and restarted the vCO service and it worked like a charm.  Thanks Burke.
I would agree with UmeshAhuja this is probably a permissions issue with not seeing any items in vCenter web client.  I've ran into that before. As for the alerts seen in vCenter Service Healt... See more...
I would agree with UmeshAhuja this is probably a permissions issue with not seeing any items in vCenter web client.  I've ran into that before. As for the alerts seen in vCenter Service Health this is what I've come up with for a solution.  From my searches through the web I have seen that the three services, Storage Profile Service, vSphere Web Client and Orchestrator all try to start on port 31000 by default.  Below this is a known issue in 5.0 U3 and we're running 5.1U1a and still are seeing this crop up. I looked through the 5.1 and 5.5 release notes and didn't find anything related to this Alerts on these three services: License Services - Asset Properties History service - Cannot obtain asset properties from vCenter Server query service VMware vSphere Profile-driven Storage Service - Unable to retrieve health data from http://localhost/sps/health.xml VMware vCenter Storage Monitoring Service - Service initialization failed This is a known issue with vCenter 5.0 U3 VMware vCenter Server 5.0 Update 3 Release Notes KB article VMware KB: VMware vSphere Profile-Driven Storage service fails to start after rebooting vCenter Server More explanation in a community forum Re: vSphere Profile-Driven Storage Service terminates
I also have a similar issue with one environment with the exact same alerts in Service Health. http://localhost/sps/health.xml returns a 503 error on the local server. Anyone find any solu... See more...
I also have a similar issue with one environment with the exact same alerts in Service Health. http://localhost/sps/health.xml returns a 503 error on the local server. Anyone find any solutions?
I believe you need to use "subject alternative names".  X.509 certificates Microsoft KB on subject alternative names How to add a subject alternative name to a secure LDAP certificate
Have you read Derek Seaman's bog on SSL in ESX 5.5?  You can probably start here: http://www.derekseaman.com/2013/10/vsphere-5-5-install-pt-5-ssl-deep.html