CRACK VMware VSphere Client 5.5.0-1281650 EXE (2013)
Marnie Monteverde
I've been struggling for a while with a vmware lab installation environment. I have installed ESXi 5.1 on two separate hosts and installed vcenter on one of them. After finishing the installation I cannot log into the vCenter administration panel from the vSphere client. I installed the web client as well to add the domain that the lab servers are members of to the authorized domains.
I can now log into the vCenter administration from the web client with my domain credentials but when I try to log into vCenter server with the vSphere client I get the following error: " The vSphere client could not connect to "hostname". You do not have permission to log in to the server "hostname".
I have also tried with the admin@system-domain account that was created during the install, but I get the same message there. I can log into the web client with the admin@system-domain username as well.
But I am not sure if I understand what you mean with "You will also have to add your domain id or the system-admin\_administrator_ group to the permissions in Vcenter. If your id is not added in vcenter permissions, you won't be able to login." What other permissions are there to set than the SSO users and groups?
Please check the screenshot attached. Your user should be added to the vcenter and should have permission as admin, or read-only depending upon the access needed. You can provide those rights to the user by logging in to VC using either admin@System-Domain. I think you might also want to try logging in to VC using the service account that you used to install SSO and VC and then add the necessary permissions to the ids that need to access VC. Not sure if this is of any help.
But that is my problem , I cannot log int vCenter with any account at all even when running the vSphere client on the vCenter server. So even with the admin@system-domain I can't log in to the administration panel. Both my domain account and my admin@system-domain account work on the web client...
With vCenter Server for Windows, the local "Administrators" group should have permissions by default. What you may do is to login through the Web Client and check the permissions and/or try to login through the vSphere Client on the vCenter Server itself (using the local Windows Administrator credentials) to see whether this works.
Thanks for the reply! I have tried logging into the vSphere client on the local machine using the both the local administrator username/password and the domain administrator username/password. Both accounts are members of the local Administrator group on the vCenter server.
I have even added new accounts to the SSO users and groups in the web client that I am allowed to log in with afterwards. In the web client login menu it's enough to just write the domain user name and password while on the vsphere client I have tried domain/username username@domain and just username with no luck..
I also had this issue. it was due to my AD evironment issue. i think this thing is also the same issue. Did you get any errors while trying to install the SSO? If that is so, definetely you have a error with your Domain. you should have to manually add the domain to the SSO. after that it will be ok...
We were experiencing this same issue for one user only. I removed him from the AD group in that gave him his permissions for vcenter, and then re-added him to the group. Had him log off and back on, and this fixed it. Worth a shot at least.
We have two ESXi hosts that are connected to varies networks for varies purposes: management, NFS, iSCSI, vMotion and FT. Although some of these features (perhaps all?) could use single adapter, this is not considered a best practice.
Now when we have two virtual ESXi hosts, we need a tool to manage them. This tools is called vSphere Client. We can download this tool from VMware site. We have several choices here about where we would install this client. Similar to a DNS server installation. We could run it from a host OS, which is Windows8 in our case, we can run it from a VM inside the VMware workstation, or we could run it from a VM installed within a ESXi host that is running as a VM inside the Workstation. Fun stuff again ?
Depending on several choices, the amount of RAM required can vary. For lab environment I would suggest at least 2GB. More is better, but we are limited by the max amount of physical RAM on our laptop. For CPU, we can go with the defaults in our environment:
Please note that the NFS share should have these options enabled: rw, no_root_squash and appropriate host access wildcard (in our case 2.2.2.*). If everything goes well, we should see our shared storage:
Hi thanks for this nice information,
I did the same thing but I used vCenter Server apliance and Openfiler, I reserved 6 GB for one host which I installed the appliance, but it was sooooooo slow to start the server, I coudlnt do at least login with vClient, why is that? I also have 8 GB RAM, core i3 lap top
I have tried myself vCenter Server Appliance and never made it, so I went for the Windows version. Even on Windows it took some time for vCenter Server services to start, so perhaps you should wait a while with the appliance.
Thanks for this great piece, it was quite informative and practical enough until I got to the point of adding my 2nd Host (ESXi_1) to the datastore which is point I got stucked. My Windows vCenter VM was created inside ESXi_2 but it was amazing that I cannot ping (communicate) with the ESXi_1. Please is there a way I can make my vCenter to be able to communicate with the second host. I will appreciate if you can send me your e-mail address so that i can be able to send you screenshots of the error.
You said you can communicate with one but not the other ESXi host. Can you attach screenshots of network settings from both to be compared?
Also please attach screenshots of network settings of vCenter Server.
However, if your default gateway for laptop is 192.168.1.1, it should be default gateway for ESXi hosts and VMs. In my lab, there is no need for static toutes, because ESXi hosts are in the same segment as storage devices (iSCSI, NFS) but if they were not you should log in to your ESXi hosts (first enable SSH, because it is disabled by default) and, depending on version, you type:
I have a small question, right now trying to choose a laptop which later will be used to setup such labs, what do you think of the following if we assume that the RAM is 16GB and will have one 120GB SSD for the ESXi(maybe two ESXi hosts?), what processor can i go for? Core-i5 (2 cores) would be enough or Core-i7 (4 cores) is a must? The SSD and the RAM I think are the most important but the processor you know is the brain, so wondering how it will be with i5 the above lab for example?
I thank you for this excellent article. Rarely I have found articles written very clearly as this one; also because, as I always said, sometimes a screenshot is more meaningful that 1000 words.
That said, I have some questions for you:
1) How many VM could I run within esxi 5.5?
With my PC (16gb ram, fast HD, and a quadcore) I had been able to run about 10 vm using just vmware workstation, having a complete Exchange test lab.
But, because I would study esxi 5.5, I would setup vm INSIDE esx (as you described) so that, to sum up, ONLY esxi would runs directly on top of vmware workstation.
In your opinion, how many vm would be able to run inside esx?
3) VLAN
In enterprise environments, VLANs are always involved. Is possibile to add some more complexity to your lab using VLANs? If yes, do you have any suggestion? What could I do? Maybe using something like vyatta as described in this post? -with-vyatta-and-home-routing/
I have installed the vsphere client , but when i am trying to login to the esx host with the ip throws an error invalid username and password ..
i am able to ping the ip from my laptop cmd prompt and able to login into the esx host with the credentials which i am giving in the vsphere client to login.
thanks to this post I have been able to setup an ESXi 6 lab like this. I just added vyos acting as router providing connectivity between networks. Anyway there is an item that I have not been able to understand even spending days reading documentation and blogs:
b1e95dc632