Manual for installing ESXi and vCenter (novice mode enabled)


    An extra server appeared on my hands and suddenly for some reason I really wanted to create a virtual environment =) I do not have much experience with virtualization. Where to begin? We get involved in vmware and download a product image called Esxi (vSphere). Download completed! Now you need to make a boot device. You can slice a disc or use a removable device.

    Take a USB drive. In order for everything to load normally, you need to use the unetbootin utility .


    The interface is quite simple, the main thing is not to forget to choose a USB Drive. Half a minute and you're done. We take the flash drive to its server. In the BIOS, do not forget to set the boot from USB - it should be the name of the manufacturer of the flash drive (sometimes it starts to be seen only after a reboot).
    If everything is correct, then Installer will start loading - component by component. After it will offer to press Enter and agree with EULA. Now you need to choose the installation location, here is the “feint with your ears" and select our USB drive. Because installation files already in RAM nothing bad will happen. The nuance is this, take a larger volume so that there is a place where ESXi will write logs. Further according to the plan and DO NOT forget the root password. After installation, ESXi will ask you to reboot.

    Then you need to remember to configure the network interface for remote access via vsphere client or web and connect the cord. We checked the availability of the network and go back to the workplace. We start the client, see the host and configure it a bit (data stores, network) and deploy win server 2012 with IP from the control network range.

    For centralized management of VM there is such a product - vCenter. Let's try to install it on a virtual win server 2012, which we have already deployed to the ESXi host. It is not in our domain and has a real one! network address.

    The requirements for vCenter are .netFramework 3.5 and SQL DB. “Hmm, in 2012 there are 4 frames, I won’t install 3.5”, but no, you need to install anyway - this is done through add features.


    As for the database, the installer of the center has SQL Express, but it is better to use the full version. Install SQL Server, create a database for vCenter, and give rights to database users. Next, run SQL Agent manually! and publish the connector! to the database through this snap-in in System DSN.


    If there is a connection to the database, then the result will be “TESTS COMPLETED SUCCESSFULLY”.

    You can reboot and start the installation of vCenter - 4 components, simple install:
    1. Do not forget the administrator password vsphere.local.
    2. Select the DSN created above.
    3. Again we remember the password of the administrator and further.
    4. And, if you do not have DNS, then we write the real IP everywhere, instead of the name, otherwise nothing will work, even when editing \ etc \ hosts.

    After installation, vCenter is available through the web client. When you join, you can scold for a certificate, ignore and axcept. Done! Now with vCenter you can manage ESXi hosts by creating a DataCenter, cluster them, use vDS for switching, Vlan and PVlan, etc.

    Empirically, it was determined that any other sequence leads to vCenter inoperability. Have a good experiment.

    PS DSN and DNS are different abbreviations.
    When installing on windows server 2012 R2, the problems described here will occur . How to solve them is described in the comments or in the article by reference.

    Also popular now: