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

2. Installeer een Server met daarop Windows 2008 R2. In mijn geval ward-ex02

3. Download Exchange2010-RC1-x64.exe

4. Uitpakken in c:\install2010

5. Instaleren van de prerequisites
    – 2007 Office System Converter: Microsoft Filter Pack
    – ServerManagerCmd -ip Exchange-typical.xml
    – Set-Service NetTcpPortSharing -StartupType Automatic

6. Installeren van Exchange 2010

Finish

2. Open het menu Start, ga naar Alle programma’s dan Accessoires dan Windows PowerShell. Open een verhoogde Windows PowerShell console en voer het volgende commando:

Import-Module ServerManager

3. Gebruik de Servermananger cmdlet het installeren van de nodige onderdelen van het besturingssysteem:

servermanagercmd -i NET-Framework
servermanagercmd -i RSAT-ADDS
servermanagercmd -i Web-Server
servermanagercmd -i Web-Basic-Auth,
servermanagercmd -i Web-Windows-Auth
servermanagercmd -i Web-Metabase
servermanagercmd -i Web-Net-Ext
servermanagercmd -i Web-Lgcy-Mgmt-Console,
servermanagercmd -i WAS-Process-Model,
servermanagercmd -i RSAT-Web-Server
servermanagercmd -i Web-ISAPI-Ext
servermanagercmd -i Web-Digest-Auth
servermanagercmd -i Web-Dyn-Compression
servermanagercmd -i NET-HTTP-Activation
servermanagercmd -i RPC-Over-HTTP-Proxy
servermanagercmd -Restart

http://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspx

4. Nadat het systeem opnieuw is opgestart, meldt u aan als beheerder, opent u een verhoogde Windows PowerShell console en configureren van de Net.Tcp Port Sharing Service voor Automatisch opstarten door het volgende commando:

Set-Service NetTcpPortSharing -StartupType Automatic

5. Installeer Exchange 2010
 

De Lijst:
1. Installeer je VMware Tools.

2. Verwijder overbodige Software.

3. Stop on nodige services die niet meer gebruikt worden.

4. Open command prompt

5. Type “SET DEVMGR_SHOW_NONPRESENT_DEVICES=1″ en enter

6. “START DEVMGMT.MSC”

7. Wanneer je “Device Manager” open hebt ga je naar View en kies voor Show hidden Devices.

8. Verwijder alles wat licht gekleurd is.

Zo ontdoe je van alle oude hardware die tijdens de P2V mee genomen wordt.

Nu krijg je de melding niet dat er op een andere netwerk adapter een IP is ingesteld.

 

De beta van Exchange 2010 wordt alleen op Windows 2008 x64 standaard of Enterprise door Microsoft ondersteund. Windows 2008 R2 kan het wel in werken maar het wordt nog niet ondersteund. Zie voor Exchange 2010 blog voor meer infomatie.

Look here for Prepare Active Directory and Domains.

Algemene Voorbereiding

1. Install Microsoft .NET Framework 3.5.
2. Install Windows Remote Management ( WinRM ) 2.0 Community Technology Preview 3 (CTP3).
3. Install Windows PowerShell V2 CTP3.

4. Install the update for the Microsoft Management Console (MMC) in Windows Server 2008. See Microsoft Knowledge Base article 951725 An update that extends the mechanism for displaying snap-in context Help topics is available for the MMC in Windows Server 2008.

5. Update from KB 951725
Update from KB 950888
Update from KB 951116
Update from KB 952664
Update from KB 953290
Update from KB 958178

Client Access servers

1. Install the Active Directory remote management tools by running the following command:

ServerManagerCmd -i RSAT-ADDS

2. Install the extensions for ASP.NET AJAX 1.0.

3. Install the necessary Internet Information Services (IIS) prerequisites by running the following commands in the order in which they are listed:

ServerManagerCmd -i Web-Server

ServerManagerCmd -i Web-ISAPI-Ext

ServerManagerCmd -i Web-Metabase

ServerManagerCmd -i Web-Lgcy-Mgmt-Console

ServerManagerCmd -i Web-Basic-Auth

ServerManagerCmd -i Web-Digest-Auth

ServerManagerCmd -i Web-Windows-Auth

ServerManagerCmd -i Web-Dyn-Compression

ServerManagerCmd -i NET-HTTP-Activation

ServerManagerCmd -I RPC-over-HTTP-proxy

Edge Transport servers

1. Install Active Directory Lightweight Directory Services (AD LDS), which was previously known as Active Directory Application Mode (ADAM), by running the following command:

ServerManagerCmd -i ADLDS

Hub Transport servers

1. Install the Active Directory remote management tools by running the following command:

ServerManagerCmd -i RSAT-ADDS

1. Install the extensions for ASP.NET AJAX 1.0.
2. Install the necessary Internet Information Services (IIS) prerequisites:

ServerManagerCmd -i Web-Server

ServerManagerCmd -i Web-Metabase

ServerManagerCmd -i Web-Lgcy-Mgmt-Console

ServerManagerCmd -i Web-Basic-Auth

ServerManagerCmd -i Web-Windows-Auth

Mailbox servers

1. Install the Active Directory management tools by running the following command:

ServerManagerCmd -i RSAT-ADDS

1. Install the extensions for ASP.NET AJAX 1.0.
2. Install the 2007 Office System Converter: Microsoft Filter Pack.
3. Install the necessary IIS prerequisites by running the following commands in the order in which they are listed:

ServerManagerCmd -i Web-Server

ServerManagerCmd -i Web-Metabase

ServerManagerCmd -i Web-Lgcy-Mgmt-Console

ServerManagerCmd -i Web-Basic-Auth

ServerManagerCmd -i Web-Windows-Auth

Clustered Mailbox
5. ServerManagerCmd -i Failover-Clustering

Unified Messaging servers

1. Install the extensions for ASP.NET AJAX 1.0.
2. Install the necessary IIS prerequisites by running the following commands in the order in which they are listed:

ServerManagerCmd -i Web-Server

ServerManagerCmd -i Web-Metabase

ServerManagerCmd -i Web-Lgcy-Mgmt-Console

ServerManagerCmd -i Web-Basic-Auth

ServerManagerCmd -i Web-Windows-Auth

1. Install the Microsoft Windows Media Player audio/video codecs required by the Unified Messaging server by running the following command:

Copy Code

ServerManagerCmd -i Desktop-Experience

Exchange Management Tools

1. Install the necessary IIS prerequisites by running the following commands:

ServerManagerCmd -i Web-Metabase

ServerManagerCmd -i Web-Lgcy-Mgmt-Console

To install the latest optional Windows Updates

1. Install multiple Right Management Services (RMS) Client sessions update. See Knowledge Base article 950888 You cannot create multiple RMS Client sessions for one user context on a Windows Vista-based computer.
2. Install performance counter updates. See Knowledge Base article 951116 A memory leak occurs in performance counters that are used to monitor Windows Server 2008-based computers.
3. Install the System Center Operations Manager 2007 console update. See Knowledge Base article 951327 The System Center Operations Manager 2007 console may crash in Windows Server 2008 or in Windows Vista when you open the Health Explorer window.
4. Install the Event Log service update. See Knowledge Base article 952664 The Event Log service may stop responding because of a deadlock on a Windows Server 2008-based computer.
5. Install performance counter values update. See Knowledge Base article 953290 An application may crash when it uses legacy methods to query performance counter values in Windows Vista or in Windows Server 2008.
6. Install Windows PowerShell V2 CTP3.

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.

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

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

Alleen tja hij moet geinstalleerd worden op 10+ pc’s dan doe je het volgende:
Pak een machine wellicht een VM en dubbel klik op licentie agreement en wacht er op dat hij deze uitgepakt heeft en klik vervolgens op OK. Ga vervolgens naar C:Program FilesMSECacheO2007Cnv1033 en kopieer vervolgende de uitgepakte files naar een netwerk schijf bijvoorbeeld ( \serverappsmsi packetsOffice2003fcv) waar alle domein users lees rechten op hebben vervolgens.

Maak een nieuwe GPO of edit een bestaande en koppel aan deze GPO O12Conv.msi. Hang aan deze GPO de juist pc’s/laptop’s en hij wordt automatisch uitgerold.