To download just click on the picture .

Testing shows the effectiveness of vSphere 5 to add compute power by scaling up Exchange Server VMs, in increments, from 2 to 12 virtual CPUs. This allowed the total number of very heavy Exchange users to increase from 2,000 to 12,000 while sendmail latency remained well within the range of acceptable user responsiveness. Processor utilization remained low, at about 15% of the total host processing capacity for 12,000 very heavy Exchange users.

Testing also shows that scaling out to eight Exchange Server VMs supports a workload of up to 16,000 very heavy users, with the load consuming only 32% of the ESXi host processing capacity.

Additional tests were undertaken to show the performance improvements of vMotion and Storage vMotion in vSphere 5. vMotion migration time for a 4-vCPU Exchange mailbox server VM showed a 34% reduction in vSphere 5 over vSphere 4.1. Storage vMotion migration time for a 350GB database VMDK showed an 11% reduction in vSphere 5 over vSphere 4.1.

For the full paper, see Microsoft Exchange Server 2010 Performance on vSphere 5.

VMware ESXi 5.0 (Build 469512)

VMware vCenter 5.0 (Build 456005)

VMware Data Recovery 2.0 (Build 433157)

vSphere Storage Appliance 1.0

VMware vShield Zones for vSphere 5 (Build 216288)

• Virtual machine enhancements
• Improved SSD handling and optimization
• Command-line enhancements
• VMware® ESXi™ firewall
• vSphere Image Builder
• vSphere Auto Deploy server
• vSphere Host Profiles
• VMware vCenter™ Update Manager

• What’s New in VMware vSphere 5.0: Platform
• What’s New in VMware vSphere 5.0: Storage
• What’s New in VMware vSphere 5.0: Performance
• What’s New in VMware vSphere 5.0: Networking
• What’s New in VMware vSphere 5.0: Availability
• vSphere 5.0 Licensing, Pricing and Packaging Whitepaper

Solution:

Starting with vSphere 4.1, the Copy and Paste options are, by default, disabled for security reasons.

To be able to copy and paste between the guest operating system and the remote console, you must enable the Copy and Paste options using the vSphere Client. Alternatively, you can use RDP (Remote Desktop Protocol) to connect to the Windows virtual machines.

To enable this option for a specific virtual machine:

1. Log into a vCenter Server system using the vSphere Client and power off the virtual machine.
2. Select the virtual machine and click the Summary tab.
3. Click Edit Settings.
4. Navigate to Options > Advanced > General and click Configuration Parameters.

5. Click Add Row and type the following values in the Name and Value columns:

6. • isolation.tools.copy.disable – false

   • isolation.tools.paste.disable – false
     Note: These options override any settings made in the VMware Tools control panel of the guest operating system.

7. Click OK to close the Configuration Parameters dialog, and click OK again to close the Virtual Machine Properties dialog.
8. Power on the virtual machine.

Note: If you vMotion a virtual machine to a host where the isolation.tools.*="FALSE" is already set, the copy and paste options are automatically activated for that virtual machine.

To enable this option for all the virtual machines in the ESX/ESXi host:

1. Log in to the ESX/ESXi host as a root user and open the /etc/vmware/config file using a text editor.
2. Add these entries to the file:
   isolation.tools.copy.disable="FALSE"
   isolation.tools.paste.disable="FALSE"
3. Save and close the file. The Copy and Paste options are only enabled when the virtual machines restart or resume the next time.

For more information, see the Limiting Exposure of Sensitive Data Copied to the Clipboard section of the  ESX Configuration Guide.

http://kb.vmware.com/kb/1026437

 httpv://www.youtube.com/watch?v=waO-Q_TSnso

VMware has released another great “technical paper” regarding Performance Best Practices for VMware vSphere 4.1. It can be found in the Technical Resource Center which by the way contains a lot of awesome docs.

The technical paper, Performance Best Practices for VMware vSphere 4.1, provides performance tips that cover the most performance-critical areas of VMware vSphere 4.1. It is not intended as a comprehensive guide for planning and configuring your deployments.

Chapter 1 – “Hardware for Use with VMware vSphere,” provides guidance on selecting hardware for use with vSphere.

Chapter 2 – “ESX and Virtual Machines,” provides guidance regarding VMware ESX™ software and the virtual machines that run in it.

Chapter 3 – “Guest Operating Systems,” provides guidance regarding the guest operating systems running in vSphere virtual machines.

Chapter 4 – “Virtual Infrastructure Management,” provides guidance regarding resource management best practices.

http://www.vmware.com/pdf/Perf_Best_Practices_vSphere4.1.pdf

Source

System Requirements
The only requirement is Virtual Center 2.5 or higher. The Hyper9 product is NOT required.

Download HERE

- Use de VMXNET 3 Adapter
- Use per Disk a SCSI Controller
- Store the Log & Database files on physical Lun on a SAN
- Use the LSI LOGIC SAS controller for Windows 2008 & 2008 R2
- Use the VMware Paravirtual SCSI (PVSCSI) Controller for Every physical Raw Device Mapping (RDM).

Another TIP.  Exchange 2007 & Exchange 2010 needs a lots of Memory. When choosing the size for the OS partition, swap file need also al lot of space.

So, what are the key features of the Vizioncore MP?

• Essential alerts from the virtual infrastructure to reduce mean time to resolution (MTTR) of problems
• Integration to System Center Operations Manager to centralize and consolidate monitoring efforts
• Low cost and simple to use while allowing administrators to work in their familiar System Center Operations Manager views
• Native management pack delivers alert and event management as well as trending inside the SCOM console
• Agentless architecture for simple deployment and low overhead
• Performance monitoring & availability event monitoring for fast resolution in the virtual environment
• Out-of-the-box reports for host and guest metrics provides flexibility and clear communication between stakeholders

There’s even more features here…

What’s nice from my perspective, is the growth of the ecosystem around the Microsoft virtualisation platform, from Partners that have, in the past, been quite VMware focused.  That’s more Vizioncore than Quest, but still, it’s moving in the right direction.

If you’re interested, you can get all the info, and download the MP, from here.

Source

Installation and Deployment

• VMware ESX. VMware vSphere 4.1 and its subsequent update and patch releases are the last releases to include both ESX and ESXi hypervisor architectures. Future major releases of VMware vSphere will include only the VMware ESXi architecture.
  • VMware recommends that customers start transitioning to the ESXi architecture when deploying VMware vSphere 4.1.
  • VMware will continue to provide technical support for VMware ESX according to the VMware vSphere support policy.
  • To learn more about the ESXi architecture and how to migrate from ESX to ESXi, go to the VMware ESX to ESXi Upgrade Center.
• Scripted Install for ESXi. Scripted installation of ESXi to local and remote disks allows rapid deployment of ESXi to many machines. You can start the scripted installation with a CD-ROM drive or over the network by using PXE booting. You cannot use scripted installation to install ESXi to a USB device. See the ESX and vCenter Server Installation Guide, the ESXi Installable and vCenter Server Setup Guide, and the ESXi Embedded and vCenter Server Setup Guide.
• vSphere Client Removal from ESX/ESXi Builds. For ESX and ESXi, the vSphere Client is available for download from the VMware Web site. It is no longer packaged with builds of ESX and ESXi. After installing ESX and ESXi, users are directed to the download page on the VMware Web site to get the compatible vSphere Client for that release. The vSphere Client is still packaged with builds of vCenter Server. See the ESX and vCenter Server Installation Guide, the ESXi Installable and vCenter Server Setup Guide, and the ESXi Embedded and vCenter Server Setup Guide.

Storage

• Boot from SAN. vSphere 4.1 enables ESXi boot from SAN (BFN). iSCSI, FCoE, and Fibre Channel boot are supported. Refer to the Hardware Compatibility Guide for the latest list of NICs and Converged Adapters that are supported with iSCSI boot. See the iSCSI SAN Configuration Guide and the Fibre Channel SAN Configuration Guide.
• Hardware Acceleration with vStorage APIs for Array Integration (VAAI). ESX can offload specific storage operations to compliant storage hardware. With storage hardware assistance, ESX performs these operations faster and consumes less CPU, memory, and storage fabric bandwidth. See the ESX Configuration Guide and the ESXi Configuration Guide.
• Storage Performance Statistics. vSphere 4.1 offers enhanced visibility into storage throughput and latency of hosts and virtual machines, and aids in troubleshooting storage performance issues. NFS statistics are now available in vCenter Server performance charts, as well as esxtop. New VMDK and datastore statistics are included. All statistics are available through the vSphere SDK. See the vSphere Datacenter Administration Guide.
• Storage I/O Control. This feature provides quality-of-service capabilities for storage I/O in the form of I/O shares and limits that are enforced across all virtual machines accessing a datastore, regardless of which host they are running on. Using Storage I/O Control, vSphere administrators can ensure that the most important virtual machines get adequate I/O resources even in times of congestion. See the vSphere Resource Management Guide.
• iSCSI Hardware Offloads. vSphere 4.1 enables 10Gb iSCSI hardware offloads (Broadcom 57711) and 1Gb iSCSI hardware offloads (Broadcom 5709). See the ESX Configuration Guide, the ESXi Configuration Guide, and the iSCSI SAN Configuration Guide.
• NFS Performance Enhancements. Networking performance for NFS has been optimized to improve throughput and reduce CPU usage. See the ESX Configuration Guide and the ESXi Configuration Guide.

Network

• Network I/O Control. Traffic-management controls allow flexible partitioning of physical NIC bandwidth between different traffic types, including virtual machine, vMotion, FT, and IP storage traffic (vNetwork Distributed Switch only). See the ESX Configuration Guide and the ESXi Configuration Guide.
• IPv6 Enhancements. IPv6 in ESX supports Internet Protocol Security (IPsec) with manual keying. See the ESX Configuration Guide and the ESXi Configuration Guide.
• Load-Based Teaming. vSphere 4.1 allows dynamic adjustment of the teaming algorithm so that the load is always balanced across a team of physical adapters on a vNetwork Distributed Switch. See the ESX Configuration Guide and the ESXi Configuration Guide.
• E1000 vNIC Enhancements. E1000 vNIC supports jumbo frames in vSphere 4.1. See the ESX Configuration Guide and the ESXi Configuration Guide.

Availability

• Windows Failover Clustering with VMware HA. Clustered Virtual Machines that utilize Windows Failover Clustering/Microsoft Cluster Service are now fully supported in conjunction with VMware HA. See Setup for Failover Clustering and Microsoft Cluster Service.
• VMware HA Scalability Improvements. VMware HA has the same limits for virtual machines per host, hosts per cluster, and virtual machines per cluster as vSphere. See Configuration Maximums for VMware vSphere 4.1 for details about the limitations for this release.
• VMware HA Healthcheck and Operational Status. The VMware HA dashboard in the vSphere Client provides a new detailed window called Cluster Operational Status. This window displays more information about the current VMware HA operational status, including the specific status and errors for each host in the VMware HA cluster. See the vSphere Availability Guide.
• VMware Fault Tolerance (FT) Enhancements. vSphere 4.1 introduces an FT-specific versioning-control mechanism that allows the Primary and Secondary VMs to run on FT-compatible hosts at different but compatible patch levels. vSphere 4.1 differentiates between events that are logged for a Primary VM and those that are logged for its Secondary VM, and reports why a host might not support FT. In addition, you can disable VMware HA when FT-enabled virtual machines are deployed in a cluster, allowing for cluster maintenance operations without turning off FT. See the vSphere Availability Guide.
• DRS Interoperability for VMware HA and Fault Tolerance (FT). FT-enabled virtual machines can take advantage of DRS functionality for load balancing and initial placement. In addition, VMware HA and DRS are tightly integrated, which allows VMware HA to restart virtual machines in more situations. See the vSphere Availability Guide.
• Enhanced Network Logging Performance. Fault Tolerance (FT) network logging performance allows improved throughput and reduced CPU usage. In addition, you can use vmxnet3 vNICs in FT-enabled virtual machines. See the vSphere Availability Guide.
• Concurrent VMware Data Recovery Sessions. vSphere 4.1 provides the ability to concurrently manage multiple VMware Data Recovery appliances. See the VMware Data Recovery Administration Guide.
• vStorage APIs for Data Protection (VADP) Enhancements. VADP now offers VSS quiescing support for Windows Server 2008 and Windows Server 2008 R2 servers. This enables application-consistent backup and restore operations for Windows Server 2008 and Windows Server 2008 R2 applications.

Management

• vCLI Enhancements. vCLI adds options for SCSI, VAAI, network, and virtual machine control, including the ability to terminate an unresponsive virtual machine. In addition, vSphere 4.1 provides controls that allow you to log vCLI activity. See the vSphere Command-Line Interface Installation and Scripting Guide and the vSphere Command-Line Interface Reference.
• Lockdown Mode Enhancements. VMware ESXi 4.1 lockdown mode allows the administrator to tightly restrict access to the ESXi Direct Console User Interface (DCUI) and Tech Support Mode (TSM). When lockdown mode is enabled, DCUI access is restricted to the root user, while access to Tech Support Mode is completely disabled for all users. With lockdown mode enabled, access to the host for management or monitoring using CIM is possible only through vCenter Server. Direct access to the host using the vSphere Client is not permitted. See the ESXi Configuration Guide.
• Access Virtual Machine Serial Ports Over the Network. You can redirect virtual machine serial ports over a standard network link in vSphere 4.1. This enables solutions such as third-party virtual serial port concentrators for virtual machine serial console management or monitoring. See the vSphere Virtual Machine Administration Guide.
• vCenter Converter Hyper-V Import. vCenter Converter allows users to point to a Hyper-V machine. Converter displays the virtual machines running on the Hyper-V system, and users can select a powered-off virtual machine to import to a VMware destination. See the vCenter Converter Installation and Administration Guide.
• Enhancements to Host Profiles. You can use Host Profiles to roll out administrator password changes in vSphere 4.1. Enhancements also include improved Cisco Nexus 1000V support and PCI device ordering configuration. See the ESX Configuration Guide and the ESXi Configuration Guide.
• Unattended Authentication in vSphere Management Assistant (vMA). vMA 4.1 offers improved authentication capability, including integration with Active Directory and commands to configure the connection. See VMware vSphere Management Assistant.
• Updated Deployment Environment in vSphere Management Assistant (vMA). The updated deployment environment in vMA 4.1 is fully compatible with vMA 4.0. A significant change is the transition from RHEL to CentOS. See VMware vSphere Management Assistant.
• vCenter Orchestrator 64-bit Support. vCenter Orchestrator 4.1 provides a client and server for 64-bit installations, with an optional 32-bit client. The performance of the Orchestrator server on 64-bit installations is greatly enhanced, as compared to running the server on a 32-bit machine. See the vCenter Orchestrator Installation and Configuration Guide.
• Improved Support for Handling Recalled Patches in vCenter Update Manager. Update Manager 4.1 immediately sends critical notifications about recalled ESX and related patches. In addition, Update Manager prevents you from installing a recalled patch that you might have already downloaded. This feature also helps you identify hosts where recalled patches might already be installed. See the vCenter Update Manager Installation and Administration Guide.
• License Reporting Manager. The License Reporting Manager provides a centralized interface for all license keys for vSphere 4.1 products in a virtual IT infrastructure and their respective usage. You can view and generate reports on license keys and usage for different time periods with the License Reporting Manager. A historical record of the utilization per license key is maintained in the vCenter Server database. See the vSphere Datacenter Administration Guide.
• Power Management Improvements. ESX 4.1 takes advantage of deep sleep states to further reduce power consumption during idle periods. The vSphere Client has a simple user interface that allows you to choose one of four host power management policies. In addition, you can view the history of host power consumption and power cap information on the vSphere Client Performance tab on newer platforms with integrated power meters. See the vSphere Datacenter Administration Guide.

Platform Enhancements

• Performance and Scalability Improvements. vSphere 4.1 includes numerous enhancements that increase performance and scalability.
  • vCenter Server 4.1 can support three times more virtual machines and hosts per system, as well as more concurrent instances of the vSphere Client and a larger number of virtual machines per cluster than vCenter Server 4.0. The scalability limits of Linked Mode, vMotion, and vNetwork Distributed Switch have also increased.
  • New optimizations have been implemented for AMD-V and Intel VT-x architectures, while memory utilization efficiency has been improved still further using Memory Compression. Storage enhancements have led to significant performance improvements in NFS environments. VDI operations, virtual machine provisioning and power operations, and vMotion have enhanced performance as well.

  See Configuration Maximums for VMware vSphere 4.1.

• Reduced Overhead Memory. vSphere 4.1 reduces the amount of overhead memory required, especially when running large virtual machines on systems with CPUs that provide hardware MMU support (AMD RVI or Intel EPT).
• DRS Virtual Machine Host Affinity Rules. DRS provides the ability to set constraints that restrict placement of a virtual machine to a subset of hosts in a cluster. This feature is useful for enforcing host-based ISV licensing models, as well as keeping sets of virtual machines on different racks or blade systems for availability reasons. See the vSphere Resource Management Guide.
• Memory Compression. Compressed memory is a new level of the memory hierarchy, between RAM and disk. Slower than memory, but much faster than disk, compressed memory improves the performance of virtual machines when memory is under contention, because less virtual memory is swapped to disk. See the vSphere Resource Management Guide.
• vMotion Enhancements. In vSphere 4.1, vMotion enhancements significantly reduce the overall time for host evacuations, with support for more simultaneous virtual machine migrations and faster individual virtual machine migrations. The result is a performance improvement of up to 8x for an individual virtual machine migration, and support for four to eight simultaneous vMotion migrations per host, depending on the vMotion network adapter (1GbE or 10GbE respectively). See the vSphere Datacenter Administration Guide.
• ESX/ESXi Active Directory Integration. Integration with Microsoft Active Directory allows seamless user authentication for ESX/ESXi. You can maintain users and groups in Active Directory for centralized user management and you can assign privileges to users or groups on ESX/ESXi hosts. In vSphere 4.1, integration with Active Directory allows you to roll out permission rules to hosts by using Host Profiles. See the ESX Configuration Guide and the ESXi Configuration Guide.
• Configuring USB Device Passthrough from an ESX/ESXi Host to a Virtual Machine. You can configure a virtual machine to use USB devices that are connected to an ESX/ESXi host where the virtual machine is running. The connection is maintained even if you migrate the virtual machine using vMotion. See the vSphere Virtual Machine Administration Guide.
• Improvements in Enhanced vMotion Compatibility. vSphere 4.1 includes an AMD Opteron Gen. 3 (no 3DNow!™) EVC mode that prepares clusters for vMotion compatibility with future AMD processors. EVC also provides numerous usability improvements, including the display of EVC modes for virtual machines, more timely error detection, better error messages, and the reduced need to restart virtual machines. See the vSphere Datacenter Administration Guide.

Partner Ecosystem

• vCenter Update Manager Support for Provisioning, Patching, and Upgrading EMC’s ESX PowerPath Module. vCenter Update Manager can provision, patch, and upgrade third-party modules that you can install on ESX, such as EMC’s PowerPath multipathing software. Using the capability of Update Manager to set policies using the Baseline construct and the comprehensive Compliance Dashboard, you can simplify provisioning, patching, and upgrade of the PowerPath module at scale. See the vCenter Update Manager Installation and Administration Guide.
• User-configurable Number of Virtual CPUs per Virtual Socket. You can configure virtual machines to have multiple virtual CPUs reside in a single virtual socket, with each virtual CPU appearing to the guest operating system as a single core. Previously, virtual machines were restricted to having only one virtual CPU per virtual socket. See the vSphere Virtual Machine Administration Guide.
• Expanded List of Supported Processors. The list of supported processors has been expanded for ESX 4.1. To determine which processors are compatible with this release, use the Hardware Compatibility Guide. Among the supported processors is the Intel Xeon 7500 Series processor, code-named Nehalem-EX (up to 8 sockets).

You can download VMware vSphere 4.1 HERE

Je krijgt dan de volgende error:

De standaard driver die VMWare mee levert in VMWare Tools werkt niet binnen een Windows PE image. Wel als Windows een maal geïnstalleerd is.

Oplossing:
Download van de AMD site de NDIS5 driver voor Microsoft Windows Server 2003, Windows XP

PCNET Family Software vind je HIER en de juiste driver voor MDT (WinPE) vind je HIER

VMWare heeft vorige week Update 1 voor vSphere vrijgegeven.
Met deze update wordt de vSphere client volledig ondersteund op Windows 7 & Windows 2008 R2.

Download de client (Je moet wel een account hebben om in te loggen)

VMware ESX 4 Update 1 verbeteringen:
- VMware View 4.0
- Windows 7 and Windows 2008 R2 support
- Enhanced Clustering Support for Microsoft Windows
- Enhanced VMware Paravirtualized SCSI Support
- Improved vNetwork Distributed Switch Performance
- Increase in vCPU per Core Limit
- Enablement of Intel Xeon Processor 3400
The new VMware ESX 4 update 1 build is 208167

VMware vCenter Server 4.0 Update 1 verbeteringen:
- IBM DB2 Database Support for vCenter Server
- VMware View 4.0 support
- Windows 7 and Windows 2008 R2
- Pre-Upgrade Checker Tool
- HA Cluster Configuration Maximum
- VMware recommends installing vCenter Server on a 64-bit Windows operating system.

VMware Data Recovery (vDR) version 1.1 verbeteringen:
- File Level Restore Functionality is Officially Supported
- Integrity Check Stability and Performance Improved
- Integrity Checks Provides Improved Progress Information
- Enhanced CIFS Shares Support

vSphere PowerCLI 4.0 Update 1 verbeteringen:
- Downloaden doe je HIER.

VMware vCenter Server Heartbeat 5.5 Update 2 verbeteringen:
- Support for Windows Server 2008 SP1 and SP2 (x86/x64)
- Support for Windows Server 2003 Enterprise SP2 (x64Protection of VMware vCenter Management   Web – Services
- Introduction of the WinZip Self-Extracting executable file for Setup
- 60-day evaluation
- Tomcat Monitoring Rule

Wat ik gedaan heb om het te halen staat allemaal hier onder:

Cursus
VMware vSphere: Install, Configure, Manage

PDF’s
VMware Certified Professional on vSphere 4 Blueprint
VMware Education Services
VMware vSphere 4.0 Documentatie
vSphere Configuration Maximum
vSphere 4 reference card
vSphere 4 notes
Virtualisedreality vSphere 4 Cue Cards
VMware port numbers drawing

Practice Exams:
Simon Long vSphere 4 Practice Exams
VMware Mock test examen

DVD Cursus
Train Signal VMware vSphere training

Boeken
Mastering VMware vSphere 4 (Scott Lowe)

[HKEY_USERS\.DEFAULT\Control Panel\Desktop]
“ScreenSaveActive”=”0″
“SCRNSAVE.EXE”=”C:\WINDOWS\system32\scrnsave.scr”

[HKEY_CURRENT_USER\Control Panel\Desktop]
“ScreenSaveActive”=”1″
“ScreenSaverIsSecure”=”1″
“SCRNSAVE.EXE”=”C:\WINDOWS\system32\scrnsave.scr”

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
“NtfsDisableLastAccessUpdate”=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
“DisableCAD”=dword:00000001

Uitzetten Time Servicec.cmd
net stop w32time
sc config w32time start= disabled

Aanzetten Time Sync VMWare Tools.cmd
“C:\Program Files\VMware\VMware Tools\VMWareService.exe” –cmd “vmx.set_option synctime 0 1”

2. Ga naar Inventory –> Host & Clusters –> Configuration –> Storage.

3. Add Storage –> Next

4. In de afbeelding heb ik de juiste gegevens ingevuld –> Next

folder = /nfs/(jefoldernaam)

5. Next

6. Finish
 

7.

2. Tabblad Settings
  
3. Network Services
 

4. NFS
 
5. Enable NFS Services & Apply

6. Tabblad Shared Storage

7. Klik op Add

 
8. Apply & daarna OK
9. Overzicht Shares. Je kunt nu de share vmware toevoegen aan je ESX of ESXi Server

Inventory

Administration

Management

Virtual Machine

Eerst moet je de  VpxClient.exe.config bestand bewerken die te vinden is in
C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher map.

Het moet er uit komen te zien als hier onder.

<?xml version="1.0" encoding="utf-8"?>
<configuration>
<system.net>
<connectionManagement>
<clear/>
<add address="*" maxconnection="8" />
</connectionManagement>
</system.net>
<appSettings>
<add key = "protocolports" value = "https:443"/>
</appSettings>
<runtime>
<developmentMode developerInstallation="true"/>
</runtime>
</configuration>

Vervolgens hebben we een bestand genaamd System.dll  nodig die niet bestaat op een niet Windows 7 machine.

Het is ook mogelijk om het config bestand en dll HIER te downloaden

Plaats de config bestand in C:\Program Files\Vmware\Infrastructure\Virtual Infrastructure Client\Launcher map.

In de Launcher maken we een nieuwe  map aan genaamd Lib en in deze map plaatsen we het gedownloade DLL-bestand.

Ga naar systeem eigenschappen en maak een nieuwe ‘Environment Variable en noem deze "Devpath” met de waarde van C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib. Je kunt deze vinden onder Control Panel –> System and Security –> System –> Advanced system settings

Herstart de PC en VMware vSphere Client nu moeten werken, zonder foutmeldingen.

BRON: http://communities.vmware.com/thread/211440

Status vinkje bij Enabled OK

Tabblad Dynamic Discovery

Kies vervolgens voor add..

Vul je hier het ip adres in van de iSCSI target in.

Klik vervolgens op Close.

Vervolgens krijg je de volgende melding

Of je kunt dit ook doen door middel van naar datastores te gaan en daar een rescan uit te voeren.
 

 
Ik heb hiervoor een 10GB schijf ingesteld maar met starwind kun je tot 2TB gaan met de gratis versie.
Er zijn ook leuke nassen op de mark van bijvoorbeeld iOmega Storcenter die officieel door VMWare gesupport worden. iOmega Storcenter ondersteund NFS & iSCSI zodat je HA & DRS thuis kunt testen: http://go.iomega.com/en/products/network-storage-desktop/storcenter-network-storage-solution/?partner=4740