The downgrade process will involve downloading the version of Tools you want, then mounting the CD on the VM, and installing Tools. The only difference is that the launch process isn’t the usua...
See more...
The downgrade process will involve downloading the version of Tools you want, then mounting the CD on the VM, and installing Tools. The only difference is that the launch process isn’t the usual VM > Guest > Install/Upgrade VMware Tools, but rather just mounting and running the Tools installer from the .ISO image like any other piece of software. To download tools: Index of /45848/tools/esx Regards Girish
Sorry! i didnt see the part about it being physical server.. which version of VC is this? Some resources that might help: VMware KB: VMware vCenter Server resource usage is 100% and becomes ...
See more...
Sorry! i didnt see the part about it being physical server.. which version of VC is this? Some resources that might help: VMware KB: VMware vCenter Server resource usage is 100% and becomes unresponsive http://brian-kayser.blogspot.in/2013/04/vmware-virtualcenter-server-high-memory.html Regards Girish
Why use the local switches in between? Can't you simply use the migrate networking option on the VDS to get the VM networking directly to a VDS? Regards Girish
Try uninstalling the plugin, and install it by right clicking->run as administrator and then try launching the console. See if this works for you. Regards Girish
Did you add the jars to the library of the project?(via the option of add external jars) What files are listed there under project properties? Regards Girish
Well it would depend on a lot of factors, namely what is the inventory size you are going to be managing, how much resources do you have on the machines where you are going to install VC. For a s...
See more...
Well it would depend on a lot of factors, namely what is the inventory size you are going to be managing, how much resources do you have on the machines where you are going to install VC. For a small setup, you can get away with having everything in 1 machine. Regards Girish
Hmm.. if you are using 5.1, then you have SSO and he behavior is expected..But your post earlier indicated that you had a pre 5.1 env(without SSO) 4.x VC doesnt have SSO and so you dont need the ...
See more...
Hmm.. if you are using 5.1, then you have SSO and he behavior is expected..But your post earlier indicated that you had a pre 5.1 env(without SSO) 4.x VC doesnt have SSO and so you dont need the domain stuff. Regards Girish
Well your rui.crt and rui.key files have become 0 sized which is why this problem is occurring. Stop the autodeploy service and try the installation again. Regards Girish
You would just need to add the hosts back.. you would probably get a warning that these hosts are being managed by another VC. just ignore that and proceed. Regards Girish
What version of VC are you using? VUM is tied to a particular version so for eg: If you have an 5.0 Update 1 VC, you need to install the 5.0u1 version of VUM. Regards Girish
Yes that's why i mentioned site.. so while installing 5.5 you will create 2 sites. "Each site is represented by one vCenter Single Sign-On instance, with one vCenter Single Sign-On server, or ...
See more...
Yes that's why i mentioned site.. so while installing 5.5 you will create 2 sites. "Each site is represented by one vCenter Single Sign-On instance, with one vCenter Single Sign-On server, or a high-availability cluster. " Regards Girish
You can install 5.5 on the new site.. but the communication part with 5.1 SSO will not work.. Better option would be to upgrade both sites to 5.5 or keep both at 5.1 for now. Regards Girish