Posts mit dem Label ESX werden angezeigt. Alle Posts anzeigen
Posts mit dem Label ESX werden angezeigt. Alle Posts anzeigen

Sonntag, 14. Juni 2020

Failed to Deploy OVF package

ailed to deploy package: File ds:///vmfs/volumes/UUID/_deviceImage-0.iso was not found


While working on setup for a Custom version of our Exchange 2013/2016 Ultimate Bootcamp today, I came across a problem which is not new, but was new to me.

A colleague had saved some VMs to OVA format for deployment in a Master vApp.  As I went to deploy them, I received the following error message:


After doing some research, I came across a couple of articles.  Neither gave me what I needed, but through combining bits and experimenting, I found a solution.

PROBLEM: 

   The VMs had ISOs attached to their CD-ROMs when the were exported to OVA format.
   The OVF file inside the OVA package has information about the attached ISO.

 

SOLUTION:

  1. Uncompressed the OVA file using either TAR on Linux/ESXi or 7-Zip on Windows.
  2. Located the OVF file which contains the configuration of the VM to deploy.


      
  3. In the VMname.OVF file, I searched for “vmware.cdrom.iso”
  4. I replaced vmware.cdrom.iso with vmware.cdrom.remotepassthrough and saved the file.

  5. Calculated a new SHA1 hash for the updated VMname.OVF file using HashMyFiles (Download here: http://www.nirsoft.net/utils/hash_my_files.html)

  6. Edited the VMname.mf file and replaced the SHA1 hash for the VMname.ovf with the new one & saved the file.

        
     
  7. Deployed a new VM using the OVF file.
  8. Optionally you could repackage the OVF to an OVA using either OVFTool or TAR in a host.
    tar cvf VMname.ova VMname.ovf
    tar uvf VMname.ova *.mf *.vmdk

Another option would be to simply delete the MF file.  vSphere deployment of the OVF then wouldn't do a hash check at all and the install will complete as expected.  Your choice!

Montag, 9. Juli 2018

Gemalpto Smart Card Reader only appears as "Shared" not "Passthrough"

you can manually enable passthrough mode. The reason why the passthrough mode was disabled was because we were stepping toes with a service called pcscd service that is required for the shared mode to work. However if you do not want to use the shared mode, you can manually disable shared mode and enable the passthrough mode

Here are the steps:
Shutdown the VM to which you want to passthrough the smart card and:

1) Go to the VM's installation directory. Typically C:\Users\<username>\Documents\Virtual Machines\
2) Open <virtual-machine-name>.vmx file
3) Append the following lines:

      usb.generic.allowCCID = "TRUE"
       usb.ccid.disable = "TRUE"

4) Kill the process corresponding to the PCSC daemon on the Linux host

Do a # ps -ef | grep -i pcsc on your Linux host
       sudo kill -9 <pid of the process that corresponds to pcscd>

Notes:
1) The first line in step 3 enables the passthrough mode
2) The second line in step 3 disables shared mode
3) Since you are killing the pcscd on your host, you wont be able to use the smart card on the host. You can passthrough the smart card now and use it in the VM

Hope this helps,

Freitag, 19. Dezember 2014

ROK Windows auf VMware ESXi installieren



Schon mal versucht einen HP ROK Windows 2008 Server auf VMware ESXi zu installieren? Wenn ja, dann hast du sicher auch erstmal dumm aus der Wäsche gekuckt weil der Installer den HP-Server nicht als solchen erkannt hat – oder?

Der Installer versucht über das Bios herauszufinden ob es sich um einen HP Server handelt. Beim Zugriff auf das VMware Bios findet er aber die notwendigen Informationen nicht und bricht die Installation ab.

Abhilfe schafft ein Parametereintrag in der Konfiguration der virtuellen Maschine:SMBIOS.reflectHost=TRUE


Unter dem Esxi 5.x ist es ein bisschen anders:

Unter Vsphere Rechtsklick auf die virtuelle Maschine

- Einstellungen bearbeiten
- Reiter Optionen
- Menü Allgemein auswählen
- Rechts “Konfigurationsparameter” auswählen
- Neuen Eintrag anklicken
- Links im Feld “SMBIOS.reflectHost” eingeben
- Rechts im Feld den Wert “True” eingeben

Speichern und Maschine neu starten.

Mittwoch, 23. April 2014

Unable to install Microsoft Windows Server 2012 into a VMware ESXi 5.x or Hyper-V virtual machine with HP provided media

Symptom

When users try to install Microsoft Windows Server 2012 using HP provided media into VMware vSphere ESXi 5.1 managed virtual machine or under Microsoft Hyper-V, the Windows Installer will pop-up a window with the following message:
 Debug Assertion Failed!
Program: x:\tools\BIOSCHECK64.exe
File: c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\atlmfc\include\atlsmpstr.h
Line:112
Expression: nRefs !=0
For information how your program can cause an assertion failure, see the Visual C++ documentation on asserts.
(Press Retry to debug the application)"
Users can click on the Ignore button to continue with the installation.

Affected configurations

The system is configured with at least one of the following:
  • Microsoft Windows Server 2012, any service pack
  • VMware ESXi 5.0 Update 1, Update 2
  • VMware ESXi 5.1, any Update
This tip is not system specific.
This tip is not option specific.
Note: This does not imply that the network operating system will work under all combinations of hardware and software.

Workaround

It is recommended to use the retail media rather than HP provided media to install Microsoft Windows Server 2012 into a virtual machine to prevent the warning.
If it is necessary to use HP provided media to install Windows Server 2012 to a virtual machine, the user can do the following:
  • For Hyper-V, the user can just ignore the warning message and go on with the installation
  • For VMware, the user can just ignore the warning message and go on with the installation or follow the instructions below to configure the virtual machine to reflect host System Management Basic Input/Output System (SMBIOS) structure to fix the issue.
Either of the following two (2) methods can do the work:
  • Edit the virtual machine's .vmx file to contain the following line:
 SMBIOS.reflectHost = "true"

Donnerstag, 2. August 2012

Creating (a better) vSphere 5 ESXi embedded USB Stick


In a previous post I blogged about creating a vanilla vSphere 5 ESXi USB drive using the VMware .iso file from VMware. This post shows how to create one using the HP version of vSphere ESXi (5.0_Oct_2011_ESXi_HD-USB-SDImgeInstlr_Z7550-00253.iso).
Note: (You can use any vendor customized vSphere ESXi .iso file: VMware, Dell and IBM).
The HP version comes pre-installed with all the HP CIM providers which work very well with HP servers, including the HP MicroServer. Using the HP version gives you the more details in the Hardware Status tab.
I’m going to be using a different method, recommended by Will Rodbard (thanks Will), who is a colleague of mine at VMware, you can see his comments from the previous post. In summary the steps are:
  1. Find and download the following tools:
  2. Run the HPUSBFW tool, click on the USB drive, select ‘Fat32′ and click Format
  3. Run UNETBOOTIN, select Diskimage and browse to the ESXi 5 ISO file
  4. Select the USB drive you have just formatted and click OK
  5. If you want to make more USB keys for more servers, then now is the time to create .IMG files using WinImage, then you can basically clone the image of the USB key to more USB keys. Or if you don’t wish to use WinImage then just perform steps 1 to 4 again.
Once completed your USB drive will boot into the ESXi 5 installer. Once booted, install the ESXi 5 Hypervisor to the USB drive (overwriting the installer). This will then leave you with the installed ESXi Hypervisor on the USB.
Note that using this method creates a brand new bootable USB key for use in a new installation of vSphere ESXi. You will have to go through the process of installing ESXi onto the USB key, or another disk or LUN on the target server. If you want a USB key that is already installed with ESXi which saves you from going through the installation wizard, you can use the other method in this post.

Samstag, 9. Juni 2012

Building a DD-WRT Image In vSphere 5.0


Introduction

I have a need to put a router between my test ESXi 5.0 server and my network. At home, I use a Linksys E3000 (both 2.4Ghz & 5Ghz Wireless-N, gigabit) router, with OpenSource DD-WRT custom firmware. There is a x86 variant that can be downloaded, people mention in the forums about using it on old PCs, I thought I would give making a VM a go.

Pre-Requisites

    1. An installed copy of ESXi 5.0 (this is almost certain to work on 4.0, but not 3.5)
    2. The DD-WRT x86 Image. I chose the VGA public image. This is a free version, limited to 4096 connections (fine for my purposes) and without Wi-Fi support. The image that is used is here.
    3. physdiskwrite – A Windows tool for writing raw images to a hard disk.
    4. An existing Windows image.
      Installation

      Creating the Virtual Machine

  1. Create a virtual Machine. Select a configuration type of Custom.
    New_VM_-_Custom
  2. Name the VM something appropriate.
  3. Select a datastore for the Virtual Machine.
  4. Select ‘Virtual Machine Version: 8’ (if using ESXi 4.0, using version 7)
    New_VM_-_Virtual_Machine_Version
  5. For Guest Operating System type, choose ‘Linux’ and select ‘Other 2.6.x Linux (32-bit) from the drop down.
    New_VM_-_Guest_Operating_System
  6. Choose 1 virtual sockets, with one core per virtual socket.
    New_VM_-_CPUs
  7. Choose 512MB RAM.
    New_VM_-_RAM
  8. Select the appropriate number of NICs (nearly always 2), E1000, and choose the port groups. (I have found that the first NIC is assigned to the WAN)
    New_VM_-_NICs
  9. SCSI Controller, choose any. This will be replaced.
  10. Choose not to create a disk.
    New_VM_-_No_Disk
  11. Tick Edit the virtual machine settings before.
  12. In the Virtual Machine Properties, click Add. Select Hard Disk.
    New_VM_-_Add_Hard_Disk
  13. Select ‘Create a new virtual disk’
    New_VM_-_Create_New_Virtual_Disk
  14. Make the capacity of the disk 1GB. I chose to make it Thin Provisioned.
    New_VM_-_1GB_Cpacity
  15. Set the Virtual Device Node to IDE (0:0)
    New_VM_-_IDE
  16. Press OK, then Finish. Wait for the VM to be created.

Install the image to the Disk

  1. Choose your Windows VM. Power it off if necessary.
  2. Edit the Windows VM’s properties. Press Add.
  3. Select a Hard Disk.
  4. Choose ‘Use Existing Virtual Disk’
    Edit_VM_-_Add_Exiting_Virtual_Disk
  5. In Advanced Options, ensure that the Virtual Device Node is ‘IDE (0:0)’
  6. Click OK, then Finish. Power on the Windows VM.
  7. Load PhysGUI (make sure you elevate it)
  8. Ensure that you select the ‘VMware Virtual IDE Hard Drive ATA Device’, right click select ‘Image laden’ –> ‘Öffinen’. Select the downloaded DD-WRT image.
    PhysGUI_-_Select_Image
  9. Click OK through the prompts.
    PhysGUI_-_Remove_2GB
  10. Wait until the disk completes writing. Shut down the VM.
    PhysGUI_-_Write_to_Disk
  11. Edit the Windows VM’s properties. Select the DD-WRT virtual disk and press remove. Ensure ‘Remove from virtual machine’ is selected. Click OK.
  12. Start up the DD-WRT VM.

Connecting to the Router

    1. Load another VM on the same LAN as the router. Ensure that it is configured to automatically obtain an IP address.
    2. It should be assigned an IP by the DD-WRT router’s DHCP server service. You can see this by performing an ipconfig (if using a Windows client)
    3. Presuming that you have an IP address, use the web browse to connect to 192.168.1.1
      DD-WRT_System_Information
    4. It will ask to set the username and password. Note that if you SSH into the router at a later point, it will use the username ‘root’ with the password set here.
      DD-WRT_-_Set_Creds
    5. You are presented with the DD-WRT System Information page. This will show the current hardware, configuration, DHCP client list, etc.
Wenn euch das zu viel arbeit ist könnt ihr auch hier die fertige VM herunterladen



Rename Onedrive Business root folder

Rename Onedrive Business root folder Here is what I remember: In the Office 365 web admin pages, change the organization name to a shorte...