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

- 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

What’s New in VMware Workstation 7.1

1. First, locate your PDC Server. Open the command prompt and type: C:\>netdom /query fsmo
2. Log in to your PDC Server and open the command prompt.
3. Stop the W32Time service: C:\>net stop w32time
4. Configure the external time sources, type: C:\> w32tm /config /syncfromflags:manual /manualpeerlist: “0.vmware.pool.ntp.org
5. , 1.vmware.pool.ntp.org,2.vmware.pool.ntp.org”
6. Make your PDC a reliable time source for the clients. Type: C:\>w32tm /config /reliable:yes
7. Start the w32time service: C:\>net start w32time
8. The windows time service should begin synchronizing the time. You can check the external NTP servers in the time configuration by typing: C:\>w32tm /query /configuration
9. Check the Event Viewer for any errors.

You can use MAP to inventory the following platforms:

• Windows 7
• Windows Vista
• Windows XP® Professional
• Windows Server 2008 or Windows Server 2008 R2
• Windows Server 2003 or Windows Server 2003 R2
• Windows 2000 Professional or Windows 2000 Server
• VMware ESX
• VMware ESXi
• VMware Server

Reporting
- Identification of currently installed Windows client operating systems, their hardware, and recommendations for migration to Windows 7 and Windows Vista. The tool also reports if desktops have anti-virus and anti-malware programs installed and if the Windows Firewall is turned on.
- Identification of currently installed Windows Server operating systems, their hardware, and recommendations for migration to Windows Server 2008 R2 and Windows Server 2008.
- Identification of currently installed Microsoft Office software and recommendations for migration to Microsoft Office 2007.
- Detailed assessment and reporting of server utilization gathered using the Performance Metrics Wizard.
- Recommendations for server consolidation and virtual machine placement using Hyper-V
- Assessment of client machines, servers, and the technology environment for the implementation of Microsoft Application Virtualization (APP-V)
- Identification of machines where Microsoft SQL Server components are installed.
- Identification of virtual machines, their hosts, and details about each.
- Identification of Windows Server Roles

Hardware Requirements:
- Windows 2003 x86/x64 or Windows 2008 x86/x64
- 1,5 GB (2 GB 2008)

Software Requirements:
- NET Framework 3.5 SP1
- Windows Installer 4.5
- Microsoft Office Word 2007 or Word 2003 SP2
- MIcrosoft Office Excel 2007 or Excel 2003 SP2
- SQL Server 2008 Express Edition, SQL Server 2008, or SQL Server 2005

Download Microsoft Assessment and Planning (MAP) Toolkit HIER

Wat heeft hij allemaal gedaan:
- All graphics updated to vSphere4
- All new theme of the New York and New Jersey – Protected and Recovery Site
- How setup replication for EMC Celerra, Clariion CX3, NetApp Filers and HP Lefthand VSA
- Integrated with these three storage vendors  – so I cover what happens in EMC, NetApp, and HP when recovery plans are tested or run
- Coverage of the new “Shared Site” configuration
- Integrating PowerCLI scripts to the Recovery Plan
- How to automate VMware SRM using the SRM SDK API
- Updated PowerCLI chapter specific to the new vSphere4 Distributed vSwitches

Dit boek is gratis te downloaden als PDF. Klik op het boek om het te downloaden. Je kunt het ook bestellen maar dan is het niet gratis.

 
mkdir /mnt/cdrom
mount /dev/cdrom /mnt/cdrom
mount: block device /dev/cdrom is beveiligd tegen schrijven, gemount als alleen-lezen

Mount zal de link naar de cdrom / mnt / cdrom directory.en de installatie te starten.
cd /mnt/cdrom /
rpm-i VMwareTools-4.0.0-219382.i386.rpm

Voordat draait VMware Tools voor de eerste opstart moet hij geconfigureerd worden voor de kernel met het volgende commando:
"/usr/bin/vmware-config-tools.pl"
Om gebruik te maken van de VMXNET Driver moet je het volgende doen: ma
/etc/init.d/network stop
rmmod pcnet32
rmmod vmxnet
modprobe vmxnet
/etc/init.d/network start

Verwijder VMWare Tools binnen CentOS
rpm-e VMwareTools

VMWare View Client GPO settings
- Enable the shade
- Pin the shade
- Don’t check monitor alignment on spanning
- Color depth
- Desktop background
- Show contents of window while dragging
- Menu and window animation
- Themes
- Cursor shadow
- Font smoothing
- Desktop composition
- Audio redirection
- Redirect drives
- Redirect printers
- Redirect serial ports
- Redirect smart cards
- Redirect clipboard
- Redirect supported plug-and-play devices
- Bitmap caching
- Shadow bitmaps
- Cache persistence active
- Enable compression
- Windows key combination redirection
- Bitmap cache file size

The VMware View ADM files can be found on the following place:

“C:\Program Files\VMware\VMware View\Server\Extras\GroupPolicyFiles”

- vdm_agent.adm contains properties relating to the authentication and
environmental components of a client desktop controlled by View Agent
-  vdm_client.adm contains properties relating to the configuration parameters of
View Client
- vdm_server.adm contains properties relating to View Connection Server
- vdm_common.adm contains properties relating to all components of View Manager
- pcoip.adm PCOIP Performance properties

Meer hierover vindt je in VMWare View Manager Administration Guide & VMWare XP deployment Guide

1. Windows XP SP3 ISO nodig
2. Maak een XP virtuele machine aan met een buslogic harddisk van 16GB en 512MB geheugen 
2. Maak een een harddisk aan van SCSI harddisk aan van 16GB.
3. Boot vanaf de ISO
4. Mount the vmscsi-1.2.0.2.flp”
5. Op de VM ga naar edit settings en dan naar de Options tab en in General gedeelte haal het vinkje weg bij Enable logging.
6. Na installatie Verwijder the Serial, Parallel and Floppy ports.
7. Installeer VMWare Tools custom zonder de Shared Folders driver.
8. Installeer de VMWare View Client
9. Werk de VM helemaal bij zonder de volgende updates.
    – Microsoft Base Smart Card Cryptographic Service Provider Package: x86
    – Microsoft Windows Search 4.0 for Windows XP

Configuren van de XP Template

1. Deze Computer, Advanced tabblad, Performance settings. Kies voor “Adjust for best performance”.

2. Disable Automatisch Updates

3. Turn Off System Restore

4. Verwijder alle overbodige Windows Componenten.

5. Open User Accounts, click Change the way users log on or off, Uncheck both boxes .

6. Verwijder alle overbodige snelkoppelingen onder All Users Profiel.

7. Disable de volgende services:
- Computer Browser
- Help and Support
- Indexing Service
- IPSec Service
- Network Local Awareness
- Security Center
- Shell Hardware Detection
- SSDP Discovery Service
- System Restore Service
- Task Scheduler
- Themes
- Windows Firewall/Internet Connection Sharing (ICS)
- Wireless Zero Configuration

8. Start –> Run –> FSUTIL behavior set disablelastaccess 1

9. Start –> Run –> sfc /purgecache

10. Start –> Run –> sfc /cachesize=0

11. Start –> Run –> Regsvr32.exe /u msutb.dll

12. Start –> Settings –> Printers and Faxes.
      File, Server Properties, Advanced tab verwijder alle vinkjes

13. Installeer User Profile Hive Cleanup Service

14. Start –> Control Panel –> Network Connections –> LAN –> Properties Internet Protocol (TCP/IP)
–> Properties > Stel het IP address van je DNS Servers in. 

15. Verwijder alle overbodige mappen. Zoals C:\WINDOWS\$hf_mig$

16. Draai Disk Clean Up

17. Defragmenteer de Schijf

18. Vergeet ook niet op RDP aan te zetten

19. Maak een nieuwe gebruiker aan en configureer dit profiel en als je klaar bent log dan in met administrator account en kopieer het profiel naar de default user

20. Verwijder de tijdelijke gebruiker die je hier voor hebt aangemaakt.

21. Zet de VM uit en maak een snapshot en convert to template.

 
3.  Aanmaken van een Desktop Pool.

4. Zorg dat in Active Directory een groep hebt gemaakt waarin elke user zit die een desktop mag gebruiken. Ik heb groep View Gebruikers aan gemaakt.

5. En dat was het.

VMware View Connection Server
• Pentium IV 2.0Ghz processor or higher — dual processors are recommended
• 2GB RAM or higher — 3GB RAM is recommended for deployments of 50 or more View Manager desktops. VMware View connection server can handle 2,000 connections in clear mode and 750 in tunneled mode.
• One or more 10/100Mbps network interface controllers (NIC) — 1Gbps NIC is recommended

Supported Operating Systems
The VMware View Connection Server can be installed on the following 32-bit operating systems:
• Windows Server 2003 R2 Standard Edition with SP2
• Windows Server 2003 Standard Edition with SP2
• Windows Server 2003 R2 Enterprise Edition with SP2
• Windows Server 2003 Enterprise Edition with SP2

VMware View Connection Server Licences:
• VMware View Manager
• VMware View Manager with View Composer
• VMware View Manager with View Composer, and Offline Desktop

2. Maak op de server waar ook vCenter geïnstalleerd is een nieuwe database aan genaamd View Composer.
3.

Een ex-collega Duncan Epping had ook een blog. Genaamd Yellow Bricks.
Ik vond wel interessant dat bloggen. Dus ook maar gaan bloggen over VMWare & Microsoft.

Een dikke jaar later zijn de statistieken als volgt zonder bots:
74.588 Unieke bezoekers
167.496 Hits

Het aantal hits schommelt tussen de 700 en 1500 hits per dag.

Wat is nu de EcoShell:
De Virtualization EcoShell biedt een eenvoudige, consistente en geïntegreerde beheer user interface voor het creëren, debuggen en vereenvoudiging van het beheer van Windows PowerShell scripts.
Voor downloads en informatie over het installeren van de Virtualisatie EcoShell, bezoekt u de Virtualisatie EcoShell download pagina.

Meer en meer bedrijven gebruiken Windows PowerShell scripts op verschillende platformen.
De Virtualisatie EcoShell gepositioneerd is voor IT-beheerders, adviseurs, en consultants die alles moeten beheren en terug kerende taken te automatiseren . Gecentraliseerd beheer van servers. De Virtualisatie EcoShell bespaart dagelijks tijd voor beheerders voor het beheer van virtuele omgevingen.

Wat heb je nodig om er gebruik van te kunnen maken.

Windows PowerShell Version 1.0
VMware PowerCLI 4.0
Quest PowerShell Commands for Active Directory Version 1.2
32-Bit  |  64-Bit
Virtualization EcoShell Build 1.2.0.154

Zo ziet de Virtualization EcoShell er uit.

VMware vSphere PowerCLI 4.0 U1

PowerCLI Quick Reference van virtu-al.net

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

Features: -Simplified Desktop Management - Automated Desktop Provisioning - Advanced Virtual Desktop Image Management - Su-erior End User Experience - Built-in Security - Availability and Scalability - Streamlined Application Management - Offline Desktop (Experimental) - Windows 7 Support (Technology Preview) - Thin Client Support

Downloaden doe je hier: Download

Bekijk HIER de gave demo die tijdens de introductie van VMWare View 4.0 in Nederland gemaakt werd door Eric Sloof

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