Patch Vmware ESXi without vCenter via SSH

1. Connect to your local ESX Server over SSH.
2. copy this link to the ssh session
esxcli software vib install -v
3. copy the vib file you want to install behind the above command
for example: https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vib20/esx-base/VMware_bootbank_esx-base_6.0.0-1.17.3029758.vib

press enter and let you esx server download the vib file and install.
4. After installation, you have to reboot you esx server depending on which vib you just installed.

if not already happend, stop your virtual machines before rebooting.

thats it! saved a lot of bucks 🙂

vSphere 6 Update – Datastore not connected

Mit vSphere Client verbinden,

  • Konfiguration -> Speicher -> Speicher hinzufĂĽgen -> Festplatte / LUN oder fĂĽr iSCSI dann NFS auswählen.
  • Die Festplatten werden nun mit ihren alten GUIDs angezeigt
  • Die gewĂĽnschte Festplatte auswählen und mit Weiter in das System einbinden
  • Es kommt nun eine Abfrage, ob eine neue Signatur geschrieben werden soll oder die alte Signatur genutzt werden soll. Dies bezieht sich primär auf die Signatur, welche der VMware Server bei der Ersteinstallation vergeben hat.
  • Hier dann unbedingt Signatur behalten wählen, ansonsten sind eure Daten hinĂĽber.
  • Danach ist der Datastore wieder eingebunden und kann genutzt werden. Zur einfacherern Verwaltung, kann dieser auch wieder umbenannt werden.
  • Es empfiehlt sich, den gleichen Namen zu verwenden, wie auf eurem alten System – ist aber nicht zwingend.
  • Danach ĂĽber den Datastore Browser eure Maschinen per Rechtsklick auf die VMX Datei -> Zu Bestandsliste hinzufĂĽgen, wieder in das System einbinden
  • Bei Bedarf dann auch gleich die Autostart Einstellungen korrigieren unter Konfiguration -> Software -> VM starten/herunterfahren

Have Fun!

Hyper-V Rolle auf VMware ESX 5.x 6.x installieren

All the credits for this very helpful post goes to Derek Seaman. If this post help you to fix your problem visit his site and show him your appreciation – http://www.derekseaman.com

 

1. Deploy your standard Windows Server 2012 R2 template. Mine happened to be fully patched, and included the spring “update” which gave us back a semi-functional start button. I also used customizations specifications to automatically rename the VM, install license key, change the SID, etc. Nothing earth shattering here. I also used vHW v8, versus the newer v10 VM.

2. Power off your freshly deployed WS2012 R2 VM, and unregister it from vCenter.

3. Download the corresponding .VMX file to your computer and open it in Wordpad.

4. Somewhere in the VMX file add the two following lines:

vhv.enable = “TRUE”

hypervisor.cpuid.v0 = “FALSE”

2014-06-19_18-59-58

5. If you have upgraded your VM to vHW 10 then you can follow William Lam’s tip and set the guestOS to use to be “windowsHyperVGuest”. If you are using vHW v8 then I just left it to the default “windows8svr-64″.

2014-06-20_8-03-26

6. Save the VMX file and re-upload it to the datastore, overwriting the old file.

7. Right click on the VMX file and register the VM.

8. Now I didn’t need to do this, but saw some other users that had to configure this setting. In vCenter open the properties of the VM and change the CPU/MMU virtualization option. Select the bottom option.

2014-06-19_19-04-14

 

9. Power on your VM, then login to Windows.

10. Install the Hyper-V role, and you shouldn’t get any warnings. Reboot after the roll is installed, and now you are ready to rock and roll with Hyper-V 2012 R2.

2014-06-19_19-16-51

Failed to lock bios – Windows Installation on vmware

Anmelden bei VMware vSphere

  1. Rechtsklick auf die virtuelle Maschine
  2. Einstellungen bearbeiten
  3. Reiter Optionen
  4. Menü Allgemein auswählen
  5. Rechts “Konfigurationsparameter” auswählen
  6. Neuen Eintrag anklicken
  7. Links im Feld “SMBIOS.reflectHost” eingeben
  8. Rechts im Feld den Wert “True” eingeben
  9. Speichern mit OK
  10. Virtuelle Maschine starten und freuen.

PS: Funktioniert auch mit EFI statt BIOS

 

Deploying vCenter 5.5 U1 – Error vpxd must be stopped

Die üblichen Bauchschmerzen bei neuen vCenter Installationen und deren Lösung. Dieser zielführende Artikel kam von: vninja.net thanks!

VMWARE VCENTER SERVER APPLIANCE ERROR: VPXD MUST BE STOPPED TO PERFORM THIS OPERATION

While deploying a fresh vCenter Server 5.5 Appliance, I ran into an issue getting it configured.

When the appliance is deployed, the first time you log in you get presented with the configuration wizard. The wizard clearly states that if you want to set a static ip, or hostname, you should cancel the wizard, do the network configuration and then re-run the wizard after the fact.

Well, that´s what I did, and it resulted in the following error when trying to create the embedded database:

VC_CFG_RESULT=410(Error: VPXD must be stopped to perform this operation.)

I even tried redeploying the appliance from scratch, but sadly that had the same outcome.

In the end, I was able to complete the configuration by opening an SSH session to the vCenter appliance, and running the following command to stop the vmware-vpxd service mentioned in the error message:

~ # service vmware-vpxd stop

After that I could successfully complete the Setup Wizard. Hopefully this will help someone finding themselves in the same conundrum in the future.

Update:

Since my setup is a single host, and at the moment of deploying the vCenter Server Appliance there was no existing vCenter in place, I deployed the appliance directly to an ESXi host. When you do this, you do not get the OVF deployment wizard that asks your IP adresses, netmasks etc. I suspect that this is the root cause of this issue, and that this is something you can/will run into of you deploy it in this manner.

Virtuelle Maschine ĂĽber USB Stick? Ja klar!

USB Sticks sind nun ja in geeigneten Größen und angenehmer Performance verfügbar.

Warum also nicht auch mal eine ganze VM auf dem Stick mitnehmen, um überall und schnell einsatzfähig zu sein? Wie das funktioniert, zeigt uns dieser Artikel samt Video von VMware.

 

To create and deploy ACE packages:
  1. Launch VMware workstation.
  2. Click VM > ACE and click New Package.
  3. In the New Package Wizard, click Next.
  4. Name the package being created, specify where to save the package and click Next.
  5. Select the type of the package and click Next.
    • Full – installs a new ACE instance
    • Policy update – updates policies of existing ACE instances
    • Custom – allows a selection of package components
  6. Select a package distribution format and click Next.
    • Network image – a single folder containing all created files
    • Multiple folders for creating DVDs or CDs – allows you to fit each folder on DVD or CD and label the disc as well
  7. Review the package summary and click Next.
  8. After the package is created, click Finish.

To create and deploy Pocket ACE packages:

  1. Launch VMware Workstation.
  2. Click VM > ACE and click New Pocket ACE package.
  3. In the Pocket ACE package wizard, click Next.
  4. Name the package being created, specify where to save the package and click Next.
  5. Select the player to be included in the Pocket ACE package and click Next.
  6. When the Pocket ACE is deployed to a portable device, set a password for the package and click Next.
  7. Review the package summary and click Next.
  8. After the package is created, deploy the portable device and click Finish.
  9. In the VMware Pocket ACE Deploy wizard, select the portable device or select a custom folder.