VMware Server 2.0.1

VMware heeft buildnummer 156745 van zijn virtualisatie software Server 2.0.1 uitgebracht. Dit pakket doet zijn werk onder Linux en Windows en is in staat om via een virtuele machine diverse besturingssystemen op de hostcomputer te laten draaien. Voor de gast computer kan je gebruikmaken van verschillende BSD-varianten, diverse Linux-distributies, Solaris en Windows. Voor meer informatie verwijzen we jullie door naar deze pagina en deze handleiding in pdf-formaat. De lijst met veranderingen voor versie 2.0.1 ziet er als volgt uit:

What’s New
Server 2.0.1 is a maintenance release that resolves security as well as some known issues. With this release of VMware Server, certain new features and support have been added.
Support for New Guest Operating Systems
VMware provides support for the following operating systems for Server 2.0.1:

  • Asianux Server 3.0 Service Pack 1
  • CentoOS 4.7
  • CentOS 5.2
  • Windows Essential Business Server (EBS) and Small Business Server (SBS) 2008
  • Windows Small Business Server 2003 Service Pack 2
  • Windows XP Service Pack 3
  • Windows Vista Service Pack 1

Security Fixes:

  • VMnc codec heap overflow vulnerabilities
    The VMnc codec assists in record and replay of sessions which are records of the dynamic virtual machine state over a period of time. Two heap overflow vulnerabilities might allow a remote attacker to execute arbitrary code on VMware hosted products. For an attack to be successful, the user must visit a malicious Web page or open a malicious video file. The Common Vulnerabilities and Exposures project has assigned the names CVE-2009-0909 and CVE-2009-0910 to these issues.
  • A VMCI privilege escalation on Windows-based hosts or Windows-based guests
    The Virtual Machine Communication Interface (VMCI) provides fast and efficient communication between two or more virtual machines on the same host and between a virtual machine and the host operating system. A vulnerability in vmci.sys might allow privilege escalation on Windows-based machines. This might occur on Windows-based hosts or inside Windows-based guest operating systems. Current versions of ESX Server do not support the VMCI interface and hence they are not affected by this vulnerability. The Common Vulnerabilities and Exposures project has assigned the name CVE-2009-1147 to this issue.
  • A remote denial-of-service vulnerability in authd for Windows-based hosts
    A vulnerability in vmware-authd.exe might cause a denial-of-service condition on Windows hosts. The Common Vulnerabilities and Exposures project has assigned the name CVE-2009-0177 to this issue.
  • Updated vm-support script
    This release improves data collection when the vm-support script is run by the Server administrator on request of VMware support or its support partners. The file that contains the SSL keys for communication between Server and vCenter and other applications is no longer collected. For more details, see the KB article Data Security Best Practices – SSL keys for communicating with VirtualCenter and other applications (KB 1008166).
  • Windows-based host privilege escalation in hcmon.sys
    A vulnerability in an I/O Control (ioctl) function in hcmon.sys might be used to escalate privileges on a Windows-based host. The Common Vulnerabilities and Exposures project has assigned the name CVE-2009-1146 to this issue. New releases of hosted products address a denial-of-service problem described in CVE-2008-3761, which can only be exploited by a privileged Windows account.
  • Denial-of -service vulnerability in a virtual device
    A vulnerability in a guest virtual device driver might allow a guest operating system to cause the host and consequently any virtual machine on that host to fail. The Common Vulnerabilities and Exposures project has assigned the name CVE-2008-4916 to this issue.

Miscellaneous Fixes:

  • Mount installer option mounts current CD-ROM image instead of VMware Tools installer image
    If a CD-ROM image is mounted to a virtual machine with VMware Tools installed, the Mount installer option in the Web UI incorrectly mounts the CD-ROM image instead of the VMware Tools image. The issue is resolved in this release.
  • Unable to install the latest version of VIX API on Server 2.0.x
    You cannot install VMware VIX API 1.6.2 of due to an issue with the MSI installer for VIX API. This issue is resolved in this release.
  • The default VI Web Access HTTP connection port is 8222 and the default HTTPS port is 8333. If you use these defaults, or any values other than 80 (HTTP) and 443 (HTTPS), you must specify the port number when you connect to VMware Server using VI Web Access. You must also allow connection to these ports through your firewall. An example URL to connect to VI Web Access is http://server_host:8222 If you want to use ports 80 (HTTP) and 443 (HTTPS), override the default values during installation. Note: If you are running IIS or Apache web server on the default ports, specify alternate HTTP and HTTP ports when prompted by the Windows installer or vmware-config.pl. Alternatively, stop IIS’s default Web site or any other Web site running on these ports. On Linux, shut down Apache or any other application using these ports and make sure they are not configured to restart automatically. This issue is resolved in this release.

VMware heeft ESX(i) 3.5 U4 Vrijgegeven

VMware heeft update 4 vrijgegeven. Release info bekijk het HIER.

Bekijk zeker de  compatability matrix, ESX(i) 3.5 U4 vereist vCenter 2.5 U2 of hoger.

Nieuwe ondersteunende Functies

Nieuw ondersteunde Operating Systems:

  • SUSE Linux Enterprise Server 11 (32-bit and 64-bit).
  • SUSE Linux Enterprise Desktop 11 (32-bit and 64-bit).
  • Ubuntu 8.10 Desktop Edition and Server Edition (32-bit and 64-bit).
  • Windows Preinstallation Environment 2.0 (32-bit and 64-bit).

Nieuwe ondersteunde SAS/SATA controllers:

  • PMC 8011 (for SAS and SATA drives)
  • Intel ICH9
  • Intel ICH10
  • CERC 6/I SATA/SAS Integrated RAID Controller (for SAS and SATA drivers)
  • HP Smart Array P700m Controller

Expanded support for the Enhanced VMXNET driver :

  • Microsoft Windows Server 2003, Standard Edition (32-bit)
  • Microsoft Windows Server 2003, Standard Edition (64-bit)
  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows Small Business Server 2003
  • Microsoft Windows XP Professional (32-bit)

USB Device Support binnen VMware ESX 3.x and ESXi

Ik was aan het zoeken naar een USB programma of apparaat wat ondersteund wordt door VMWare binnen ESX 3.x en ESXi.
Een bedrijf genaamd Xtravirt heeft een mooi document gemaakt waarin het een en ander wordt uitgelegd over UBS support binnen ESX en ESXi.

Bekijk het document HIER.

Momenteel zijn er de volgende types producten die werken werken met VMware.

Belkin, USB Anywhere & USB Hub http://www.belkin.com/networkusbhub
Digi, AnywhereUSB http://www.digi.com/prducts/usb/anywhereusb.jsp
Fabulatech, USB over Network http://www.fabulatech.com/usb-over-network.html
IncentivesPro, USB Redirector http://www.incentivespro.com/usb-redirector.html
Keyspan-by-Tripp Lite http://www.tripplite.com/EN/products/model.cfm?txtModelID=3913
Lantronix, Ubox 2100/4100 http://www.lantronix.com/device-networking/external-device-servers/ubox.html
Silex, SX-2000U2 http://www.silexeurope.com/en/home/products/usb-device-servers/sx-2000u2.html

Momenteel ondersteund VMWare gedeeltelijk de Digi International AnywhereUSB Remote I/O Concentrator. http://www.vmware.com/pdf/esx_anywhereusb2.pdf

VMware heeft een aantal Knowledge Base Articles geschreven over USB support

1. KB1326, Using USB When ESX Server Disables It, http://kb.vmware.com/kb/1326
2. KB1015, USB devices not supported in ESX host virtual machines, http://kb.vmware.com/kb/1015
3. KB1651, Using USB Storage Devices on the ESX Server Service
Console, http://kb.vmware.com/kb/1651
4. KB1659, USB Device Configuration May Cause Error During
System Boot, http://kb.vmware.com/kb/1659
5. Enabling Belkin network USB hub in a virtual machine, http://kb.vmware.com/selfservice/viewContent.do?externalId=1008372&sliceId=1

 

 

 

 

image

BUG in VMWare Toolkit 1.5 tijdens het maken van een Geplande Taak met een Service Account.

image

Ik had een probleempje met een scriptje van Collega Ivo Beerens. Hij heeft een mooi script
geschreven genaamd Healthscript. Dit wou script wou ik implementeren aangezien ik een nieuwe virtual center center server had ingericht.

Ik liep tegen het probleem dat ik het script niet werkend kreeg met een service account user die deze taak moest uitvoeren. Onder ingelogde account werkte het wel.

Oplossing:

Boven aan het powershell script de volgende code toegevoegd en daarna werkte het als een trein.:
#FIX FOR TOOLKIT 1.5
$USER = $env:username
$APPPATH = "C:Documents and Settings" + $USER + "Application Data"
#SET THE APPDATA ENVIRONMENT WHEN NEEDED
if ($env:appdata -eq $null -or $env:appdata -eq 0)
{
$env:appdata = $APPPATH
}

VMware Server 2.0 Tips and Tricks

 

Hierbij sommige  Tips & Tricks van VMWare Server 2.0

1. Use a web browser (Firefox and Internet Explorer are the two officially supported ones) to
connect to http://yourserver:8222 or https://yourserver:8333 if you selected the default
ports during installation/configuration.

2. If you manage from a Windows client then the VI (Virtual Infrastructure) client is also
available which is what is used to manage ESX/ESXi and Virtual Center too. It is available at
https://yourserver:8333/client/VMware-viclient.exe.

3. The VI Client cannot add USB devices to VMs running at hardware versions greater than 4 –
version 7 is required for USB 2.0 support.

4. Specify yourserver:8333 for the connection in the VI Client.

5. The credentials you specify to logon are admin credentials that you would use on the host
even without VMware installed – VMware does not introduce any credentials/accounts
itself.

6. The admin account you use must have a password defined for it or you will not be able to
login.

7. The remote console is a locally installed application which will be installed when the console
tab is first clicked onto.

8. For remote management through firewalls, VPNs or over SSH tunnels, port 902 is also used as well as 8222/8333. Note that during Linux configuration; you may have selected a
different port from 902 as sometimes it can be statically detected as being in use.

9 .Backing up VMs can be achieved in a number of ways:
a. If the VM is not powered up then simply copy all of its files to another location.
b. If the VM is running, take a snapshot and then copy the base disk file(s) to another
location (*.vmdk except *-00001*.vmdk). A new VM can then be constructed using
this disk. Note that you can only have a single snapshot.
c. In a Windows VM, use a VSS (Volume Shadow copy Service) aware backup tool to
create a backup that can then be restored using the same tool to a bare VM.
d. On a Windows host, use a VSS aware backup tool to backup the files that constitute
the VM.

10. If a VM fails to power on and was not shut down properly, check for .lck files/folders and
remove them if they exist as long as the VM definitely is not running.

11. Server 2.0 stores VMs in datastores – a default datastore is created which is calle
“[standard]” and will map to the root of the folder you select during installation.

12. VMs can be run from external USB drives by defining a datastore for the mount point.

13. Remote datastores can also be added – NFS for Linux hosts and CIFS/SMB for Windows.

Bekijk HIER de volledige PDF met Tips & Tricks van VMWare Server 2.0

VMware vCenter Converter vrij gegeven

clip_image001

VMware vCenter Converter kan op heel verschillende hardware en de meest gebruikte versie van Microsoft Windows and Linux* operating systems. Met dit robuste , enterprise class migratie tool kun je het volgende :

· Quickly and reliably convert local and remote physical machines into virtual machines without any disruption or downtime.

· Complete multiple conversions simultaneously with a centralized management console and an intuitive conversion wizard.

· Convert other virtual machine formats such as Microsoft Virtual PC and Microsoft Virtual Server or backup images of physical machines such as Symantec Backup Exec System Recovery or Norton Ghost to VMware virtual machines.

· Restore VMware Consolidated Backup (VCB) images of virtual machines to running virtual machines.

· Clone and backup physical machines to virtual machines as part of your disaster recovery plan.

clip_image003

Downloaden doe je hier: https://www.vmware.com/download/converter/

*Linux P2V ondersteuning is alleen voor de stand alleen versie alleen

VMWare Toolkit 1.5

PCLI_BlogVMWare heeft VMWare toolkit 1.5 vrij gegeven.
Bekijk HIER de release notes.
Er zijn 32 nieuwe powershell commando’s bij gekomen. Een heleboel zijn uitgebreid en gefikst.
Downloaden doe je HIER

Bekijk ook de volgende Video’s:
HA and DRS in VI Toolkit 1.5
Managing Storage with VI Toolkit 1.5
Some important fixes in VI Toolkit 1.5
Get-Stat Improvements in VI Toolkit 1.5
Resizing Guest Disks with Invoke-VMScript

image

VMReference Card 1.3

VMware reference VI3 kaart is uit gekomen.

Wat is er in bijgewerkt.

  • Updated the details to the latest Confuguration Maximiums PDF.
  • Updated it to include 3.5 update 3 release notes.
  • Changed the versioning to include the latest VMware release, so its more obvious how up to date (or not) your card is.
  • Some minor additions (NAS maximums) and corrections.
  • image

    Deploying Exchange Server 2007 on VMware Infrastructure: A VMware Internal Case Study

    VMWare heeft een nieuw document uitgegeven waar de volgende dingen in beschreven wordt:

    – Exchange 2007 bij VMWare zelf.
    – Exchange 2003 en haar limiten
    – Virtualisatie Exchange en haar voordelen
    – Planning & Eisen
    – Ontwerp & Implementatie
    – Conclusie van VMWare

    image

    Set Hardware Acceleration Level

    Ik vond een mooi script op het Edugeek. Het zet automatisch Hardware Acceleration Level op full.

    Const HKEY_LOCAL_MACHINE = &H80000002
    sComputer = "."
    sMethod = "GetStringValue"
    hTree = HKEY_LOCAL_MACHINE
    sKey = "HARDWAREDEVICEMAPVIDEO"
    sValue = "DeviceVideo0"
    Set oRegistry = GetObject("winmgmts:{impersonationLevel=impersonate}//" & sComputer & "/root/default:StdRegProv")
    Set oMethod = oRegistry.Methods_(sMethod)
    Set oInParam = oMethod.inParameters.SpawnInstance_()
    oInParam.hDefKey = hTree
    oInParam.sSubKeyName = sKey
    oInParam.sValueName = sValue
    Set oOutParam = oRegistry.ExecMethod_(sMethod, oInParam)
    strParse = oOutParam.Properties_("sValue")
    sMethod = "SetDWordValue"
    hTree = HKEY_LOCAL_MACHINE
    sKey = Replace(strParse, "RegistryMachine", "")
    sValueName = "Acceleration.Level"
    ‘* In Windows XP Change the uValue value for Accelleration.Level from 0 (FULL) to 5 (none)
    uValue = 1
    Set oRegistry = GetObject("winmgmts:{impersonationLevel=impersonate}//" & sComputer & "/root/default:StdRegProv")
    Set oMethod = oRegistry.Methods_(sMethod)
    Set oInParam = oMethod.inParameters.SpawnInstance_()
    oInParam.hDefKey = hTree
    oInParam.sSubKeyName = sKey
    oInParam.sValueName = sValueName
    oInParam.uValue = uValue
    Set oOutParam = oRegistry.ExecMethod_(sMethod, oInParam)
    sComputer = Empty
    sMethod = Empty
    hTree = Empty
    sKey = Empty
    sValue = Empty
    sValueName = Empty
    uValue = Empty
    Set oRegistry = Nothing
    Set oMethod = Nothing
    Set oInParam = Nothing
    Set oOutParam = Nothing
    WScript.Quit

    Sla het bovengenoemde script op als een vbs.
    Je kunt dit ideaal gebruiken tijdens het deployen van virtuele machines via MDT in combinatie met automatische uitrol van VMware Tools. Nu hoef je zelf niet meer de Hardware Acceleration level aan te passen. Ik heb het getest onder XP & Windows 2003.

    Translate »