Konsole wechseln: ctrl + alt + F1

Blind eintippen: unsupported

vi /etc/inetd.conf

Die Raute (#) vor dem ssh Eintrag entfernen.

/sbin/services.sh restart

Mit dem "vSphere Host Update Utility" können ESX(i)-Hosts gepatcht werden.

Voraussetzung ist, dass alle VMs gestoppt werden, da der Host in den Wartungsmodus gefahren und abschließend neu gestartet wird.

Nach dem Neustart des Hosts bzgl. Host-Update bleibt der ESX(i)-Host im Wartungsmodus.
Jetzt muss mittels der vSphere Console der Wartungsmodus beendet und die VMs gestartet werden.

/bin/vim-cmd solo/registervm <fullpath_to_VMX-File>

 1. Zuerst lade dir folgende Tools herunter: WinRAR, WinImage, event. ISO Tool (UltraISO, ISO Buster, …)
2. Lade dir die ESXi ISO von VMware herunter http://www.vmware.com/de/download/
3. Öffne die ISO mit WinRAR (oder einem ISO Tool)
4. Entpacke die Datei „imagedd.bz2“ in ein Verzeichniss
7. Öffne die Datei „imagedd.bz2“ mit WinRAR und entpacke die „imagedd“
8. Öffne WinImage und klick oben auf Disk / “Restore Virtual Harddisk Image on physical drive”
9. Wähle deinen zu beschreibenden USB Stick aus, und im nächsten Schritt das ESXi 4.1 Image „imagedd“
(Bei Dateityp bitte „all files *.*“ auswählen, sonst wird das Festplatten Image mit der Endung *.dd nicht angezeigt)
10. Klicke auf “yes” to write the DD image to the USB Disk, fertig.

Work around the issue by manually configuring the MAC address on the ESX host as follows:

    In the troubleshooting console run the following command: esxcfg-advcfg -s 1 /Net/FollowHardwareMac.
    Restart the server.

The esxcli command can be used locally or remotely to power off a virtual machine running on ESXi 5.0. For more information, see the esxcli vm Commands section of the vSphere Command-Line Interface Reference.

Auf der ESXi-Shell direkt: esxcli vms vm list

1. Open a console session where the esxcli tool is available, either in the ESXi Shell, the vSphere Management Assistant (vMA), or the location where the vSphere Command-Line Interface (vCLI) is installed.
    
2. Get a list of running virtual machines, identified by World ID, UUID, Display Name and path to the .vmx configuration file, using this command:
   
   esxcli vm process list
    
3. Power off one of the virtual machines from the list using this command:
   
   esxcli vm process kill --type=[soft,hard,force] --world-id=WorldNumber
   
   Note: Three power-off methods are available. Soft is the most graceful, hard performs an immediate shutdown, and force should be used as a last resort.
    
4. Repeat step 2 and validate that the virtual machine is no longer running.

Anzeige der Meldung ausschalten

Wenn man über den SSH Dienst auf dem Server arbeiten möchte, besteht auch die Möglichkeit die Anzeige der Meldung auszuschalten. Hierfür kann man über die Konfiguration > Software > Erweiterte Einstellung > UserVars > UserVars.SuppressShellWarning > 1 die Meldung ausschalten.

VMWare by default enables SSL encryption during the Physical to Virtual (P2V) and Virtual to Virtual (V2V) conversion process.  This has the effect of bringing the transfer rate to a crawl of as low as 200kbs instead of the expected 40mbs or better.

The problem is a VMware proprietary protocol called NFC that is used to create the source image and encrypt the data during the transfer process.

The SSL feature of the NFC VMware proprietary protocol can be disabled in a file called:

converter-worker.xml

located in one of the following places depending on the Operating System:

Windows Vista, Windows 7, Windows 2008
%ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone

Windows XP, Windows 2003, Windows 2000
%ALLUSERSPROFILE%\Application Data\VMware\VMware vCenter Converter Standalone

Find this section of code and change the highlighted TRUE to FALSE.

<nfc>
<readTimeoutMs>120000</readTimeoutMs>
<useSsl>true</useSsl>
<!– Delay is specified in milliseconds, -1 denotes the default.
<acceptTimeoutMs>-1</acceptTimeoutMs>
<requestTimeoutMs>-1</requestTimeoutMs>
<readTimeoutMs>-1</readTimeoutMs>
<writeTimeoutMs>-1</writeTimeoutMs>
<fssrvrReqTimeoutMs>-1</fssrvrReqTimeoutMs>
<fssrvrWriteTimeoutMs>-1</fssrvrWriteTimeoutMs>
–>
</nfc>

—–

Should be:
<useSsl>false</useSsl>

It is CRITICAL that the “VMware vCenter Converter Standalone Worker” Service be restarted.  DO NOT FORGET THIS STEP!

So you’ve installed your ESX servers and installed vCenter along with its SSO, Inventory Services and Web Client, you’ve even installed the Windows vSphere UI just because that’s what you’re used to and now when you’re connecting to your new environment your getting a “You do not have permission to login to this server”

So with this new version of vSphere you need to enable access for your domain users/groups so that they have access to vCenter.

To get you up and running fast follow these simple steps. for best practices configuring SSO please reference the VMware documentation.

1. Login to the Web client “https://client-hostname:9443/vsphere-client” with administrator@vsphere.local using the password of what ever you configured SSO password as. *Note you can only configure SSO using the Web Client*

2. Navigate to vCenter Servers > Manage > Permissions, click on the + to add a user

3. Now add your Domain user or group that you would like to have access to vCenter along with the permissions required and click on OK.

4. Try and login with the user you just configured and you should now have access to the Web client or the Windows vSphere UI.

Reiter "Konfiguration"

-> Erweiterte Einstellungen

-> Syslog.global.logHost = 172.17.1.100