VMware vSphere 5.0 Documentation

VMware vSphere™ 5.0 (“vSphere”) introduces many improvements and new features to extend the benefits and capabilities of vSphere 4.1. These advancements build on the core capacities in vSphere to provide improved scalability; better performance; and easier provisioning, monitoring and troubleshooting. This paper focuses on the following new features and enhancements:

• 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

The “Exchange Server 2010 Technical Video Series” on TechCenter

The Microsoft Exchange team has produced a new portfolio of videos designed to give customers a fundamental technical education on Exchange Server 2010.

The objective of the video series is to provide an introductory curriculum for IT professionals to learn more about the benefits of Exchange Server 2010. While TechNet provides great technical documentation at a more granular level, this video series should help bridge the gap for those who are new to Exchange 2010 and still trying to learn about the technical fundamentals of the product.

Each video runs 20-30 minutes long and includes an overview of the workload as well as a technical demonstration of 3-4 core scenarios related to that workload. The “Exchange Server 2010 Technical Video Series” is hosted by Ann Vu and presented by subject matter experts from the Microsoft Exchange team.

The Video’s can you find HERE.

Microsoft Office 365 Deployment Readiness Tool

The Office 365 Deployment Readiness Tool provides analysis of your on-premises environment in preparation for an Office 365 enterprise deployment. The readiness tool is integrated with the guidance provided in the web edition of the Microsoft Office 365 Beta Deployment Guide.

Download HERE

I run the tool in my test environment. See below the results

Microsoft Office 365 Deployment Readiness Tool


Office 365 Deployment Resource Kit build
modgClick here for the Microsoft Office 365 Beta Deployment Guide for Enterprises


modg Deployment Guide: Adding Your Domain(s) to Office 365
All email domains discovered in your environment:
Total: 3

All primary email domains discovered:
Total: 2

Primary email domain suffixes with greater than 50 users:
Total: 1

User Identity and Account Provisioning

Active Directory


Total number of domains discovered in your forest: 1
Estimated total number of users: 59
Estimated total number of contacts: 0
Estimated total number of groups: 54
Estimated total number of mailboxes: 53
Estimated total number of objects for Directory Synchronization: 113
Note: Filters were applied to obtain the above object counts for an Office 365 deployment.

Forest and Domains

The following domains were discovered in your Active Directory forest:
Total: 1


No forest trusts found
You may deploy AD FS 2.0 and Directory Synchronization without multi-forest constraints

Schema and Forest/Domain Functionality Levels

Active Directory forest schema level: Windows Server 2008 R2
Exchange schema level: Exchange Server 2010 SP1
Domain Functionality:Windows Server 2008 R2
Forest Functionality:Windows Server 2008 R2
Domain Controller Functionality:Windows Server 2008 R2
It appears that your Active Directory schema is prepared for Exchange Rich Coexistence
modg Deployment Guide: Exchange Rich Coexistence Requirements

Active Directory Cleanup

modg Deployment Guide: Active Directory Cleanup

samaccountname (user name) Attribute

Character length test passed
Unsupported character test passed

givenname (first name) Attribute

Character length test passed
Unsupported character test passed

sn (last name) Attribute

Character length test passed
Unsupported character test passed

displayname Attribute

Character length test passed
Unsupported character test passed

mail (email address) Attribute

Character length test passed
Unsupported character test passed
No duplicates found

mailnickname Attribute

Character length test passed
Unsupported character test passed

proxyaddresses (email addresses) Attribute

No duplicates found
Unsupported character test passed

Directory Synchronization

Object count assessment:
Estimated number of objects for Directory Synchronization (entire forest): 113
modg Deployment Guide: Object Count Considerations
Enterprise Admin rights:
It appears that you are an enterprise admin
Directory Synchronization admin requirement met!
modg Deployment Guide: Directory Synchronization Required Permissions
Active Directory recycle bin:
Active Directory recycle bin is enabled in your forest this may impact your total object count quota for Directory Synchronization.

Office 365 Single Sign On and Identity

AD FS 2.0 Directory Cleanup Check:

UserPrincipalName (logon ID for Office 365) Attribute

Update values once you have verified your organization does not have any other application dependencies on the UserPrincipalName attribute.
modg Deployment Guide: Active Directory Cleanup
Unsupported characters test passed
Spaces in logon value test passed
Unicode character test passed
Note: All Unicode characters will be converted to underscores (_) in the UserPrincipalName field.
No UserPrincipalName duplicates found
Discovered users without a user logon name (blank value) for UserPrincipalName
You will need to provide each user a UserPrincipalName in order for these users to sign into Office 365.
Below is a list of your UserPrincipalName domain suffixes in use:
Total: 1
Note: During the Office 365 Beta only one namespace (root and child domains) per AD FS 2.0 farm
Example contoso.com and root.contoso.com would require 1 AD FS 2.0 farm and fabrikam.com would require an additional AD FS 2.0 farm

Password length per domain:

wardvissers.local = 7

Exchange Online

Discovered Exchange Server(s) on-premises:
Estimated total number of Exchange Servers: 1


Estimated total number of users with default mailbox size (True): 53
Estimated total number of users with larger than default mailbox size (False): 0
Estimated total number of objects with Exchange organization level quota: 6

Lync Online

Lync user assessment:
Estimated total number of users leveraging Office Communications/Lync on-premises: 2
Sip domains:
The following sip domains were discovered:
Total: 1

SharePoint Online

User object count assessment:
The number of user objects in your forest is supported.
modg Deployment Guide: Object Count Considerations

Client and End User Experience

modg Deployment Guide: Rich Experience Client Requirements

Summary of client computer readiness (Office 365 single sign-on and rich client checks):

Below is an estimate of computer operating systems NOT ready for Office 365 rich client experience:
Total: 0
Below is an estimate of computer operating systems ready for Office 365 rich client experience:
Windows XP Service Pack 3: 3
Windows 7 Service Pack 1: 3
Total: 6


IP Configuration:

IPv4 Address. . . . . . . . . . . :
IPv4 Address. . . . . . . . . . . :
Subnet Mask . . . . . . . . . . . :
Subnet Mask . . . . . . . . . . . :
Default Gateway . . . . . . . . . :
Default Gateway . . . . . . . . . :

Trace route to your default gateway:

Tracing route to over a maximum of 30 hops
1 1 ms 2 ms 2 ms

Trace Route test to Exchange Online:

Tracing route to outlook.com []
over a maximum of 30 hops:
1 3 ms 2 ms 1 ms
2 * 24 ms 25 ms
3 25 ms 26 ms 26 ms
4 145 ms 146 ms 144 ms
5 * * * Request timed out.
6 * * * Request timed out.
7 reports: Destination net unreachable.
Trace complete.

For additional tests utilize the Exchange Remote Connectivity Analyzer

Port Query Tests:

modg Deployment Guide: Ports and Protocols
Made a TCP 443 connection to portal.microsoftonline.com
Made a TCP 443 connection to outlook.com
Outlook.com IMAP
Made a TCP 993 IMAP connection to outlook.com
Outlook.com POP
Made a TCP 995 POP connection to outlook.com
Outlook.com SMTP
Made a SMTP TCP 587 connection to outlook.com
Active Directory Federation Services End Point
Made a TCP 443 connection to nexus.microsoftonline.com
Directory Synchronization End Point
Made a TCP 443 connection to adminwebservice.microsoftonline.com
Office 365 PowerShell End Point
Made a TCP 443 connection to ps.microsoftonline.com
Outlook.com PowerShell End Point
Made a TCP 443 connection to ps.outlook.com
Office 365 Community End Point
Made a TCP 80 connection to community.office365.com
Lync Online SIP Connection
Made a TCP 443 connection to sipdir.online.lync.com
Lync Online Federation
Made a TCP 5061 connection to sipfed.online.lync.com
Domain Name System (DNS) name records checks:
Found the following MX DNS record(s):
Server: localhost
primary name server = ward-dc01.wardvissers.local
responsible mail addr = hostmaster.wardvissers.local
serial = 761
refresh = 900 (15 mins)
retry = 600 (10 mins)
expire = 86400 (1 day)
default TTL = 3600 (1 hour)
Information Gathered On:
Date: za 07-05-2011
Start Time: 18:19
End Time: 18:21

Microsoft Virtualization for VMware Professionals Jump Start

The “Microsoft Virtualization for VMware Professionals” Jump Start is specially tailored for VMware and Microsoft virtualization technology pros. This cutting-edge course features expert instruction and real-world demonstrations of Hyper-V, many components of the System Center Suite, including VMM 2012, and a myriad of VDI solutions. This course is designed for Data Center Managers, IT Professionals, IT Decision Makers, Network Administrators, Storage/Infrastructure Administrators & Architects. Expert IT infrastructure consultant, Corey Hynes, and Microsoft Technical Evangelist, Symon Perriman, leveraged an engaging "team teaching" approach which makes the class as entertaining as it is educational Smile

Virtualization Jump Start (01): Virtualization Overview
Virtualization Jump Start (02): Differentiating Microsoft & VMware
Virtualization Jump Start (03a): Hyper-V Deployment Options & Architecture | Part 1
Virtualization Jump Start (03b): Hyper-V Deployment Options & Architecture | Part 2
Virtualization Jump Start (04): High-Availability & Clustering
Virtualization Jump Start (05): System Center Suite Overview with focus on DPM
Virtualization Jump Start (06): Automation with Opalis, Service Manager & PowerShell
Virtualization Jump Start (07): System Center Virtual Machine Manager 2012
Virtualization Jump Start (08): Private Cloud Solutions, Architecture & VMM Self-Service Portal 2.0
Virtualization Jump Start (09): Virtual Desktop Infrastructure (VDI) Architecture | Part 1
Virtualization Jump Start (10): Virtual Desktop Infrastructure (VDI) Architecture | Part 2
Virtualization Jump Start (11): v-Alliance Solution Overview
Virtualization Jump Start (12): Application Delivery for VDI

Download all the Video’s:
Video: WMV | WMV (ZIP) | PSP
Audio: WMA | MP3

Now only finding some spare time to watch’s these video’s Winking smile

Exchange 2010 RPC Encryption Requirement

Current Status: Non-issue

Exchange 2010 SP1
With Exchange 2010 RTM, the RPC encryption requirement was an issue with mitigation. However, in Exchange Server 2010 Service Pack 1, the RPC encryption requirement has been disabled by default. This means that any new Exchange 2010 SP1 Client Access Servers (CAS) deployed in the organization won’t require encryption and Outlook 2003 clients will connect without the need to enable the RPC encryption feature in the Outlook profile.

Having the RPC encryption requirement on an Exchange 2010 CAS server disabled doesn’t lower the security between Outlook 2007/2010 and any Exchange 2010 CAS server. RPC communication for these Outlook versions will remain encrypted as long as the client has the RPC encryption feature enabled. It’s only the requirement itself that is disabled on the Exchange 2010 CAS server.

Exchange 2010 CAS servers deployed prior to Service Pack 1, or upgraded to Service Pack 1, will retain the existing RPC encryption requirement setting.

Exchange 2010 RTM
When upgrading or migrating an organization that fully or partly uses Outlook 2003 to Exchange 2010, we hear there are out of the box problems, when trying to connect an Outlook 2003 client to an Exchange 2010 RTM mailbox? We heard this is because an Exchange 2010 RTM Client Access Server by default requires an Outlook client to support RPC encrypted traffic in order to be able to connect.

While it’s true the default configuration of an Outlook 2003 client doesn’t have support for RPC encryption, this requirement is fully supported with Outlook 2003.

There are two methods that can be used in order to have Outlook 2003 clients connect to an Exchange 2010 RTM mailbox:

Method 1: Enable the RPC encryption support in Outlook 2003

If “Encrypt data between Microsoft Office Outlook and Microsoft Exchange Server” is enabled under the “Security” tab in the Outlook 2003 profile (see figure 1), the client will be able to connect to an Exchange 2010 RTM mailbox.

Figure 1:
RPC Encryption enabled in Outlook 2003

If you are working with or for a small organization, it may be acceptable the end user enables this feature manually, but if you have thousands of users in the organization, you would want to enable it using a group policy (GPO). The steps necessary to implement a GPO to enable this setting are included in this KB article.


The “EnableRPCEncryption” registry key mentioned in the KB article was originally introduced via a hotfix for Outlook 2003 SP2. This means that clients that either runs Outlook 2003 SP2 or an older version of Outlook 2003 doesn’t respect this registry key. In addition, Outlook 2003 clients not running SP3 are not supported by Microsoft.

Method 2: Disable the RPC Encryption requirement on the Client Access Servers

Instead of enabling support for RPC encryption in the Outlook 2003 profiles, you also have the option of disabling the requirement for RPC encryption on all Exchange 2010 RTM Client Access Servers in the organization.

This can be accomplished using the Set-RpcClientAccess cmdlet:

Set-RpcClientAccess –Server Exchange_server_name –EncryptionRequired $False

Figure 2:
RPC Encryption requirement disabled on Exchange 2010 CAS servers

As mentioned earlier Exchange 2010 SP1 servers that hasn’t been upgraded from Exchange 2010 RTM has the RPC encryption requirement disabled by default.

The following KB article describes the symptoms and remediation in detail:

The core Exchange 2010 TechNet documentation also describes the configuration that can be used to remediate the issue:

Unmanaged client machines cannot be controlled using GPOs or login scripts. If you have unmanaged machines connecting to Exchange 2010 using Outlook 2003, one solution would be to send those users a script or a registry file which they can run manually on their machine to enable the RPC encryption setting.

Special Thanks to Henrik Walther

Removing the Browser Choice option During deployment with MDT 2010

The Deployment Guys created a nice script to remove the Browser Choice option.

If you are in the European Union, you will have seen the installation of the Browser Choice option from Windows Update. This is a good thing if you are a consumer, however if you are managing Volume Licensed (VL) builds and you don’t want the Browser Choice in your deployment image.
But you do want to make use of the MDT 2010 ability to go off to Windows Update or your WSUS Server and install patches automatically during your deployment task sequence.

Check HERE how to config MDT to use your WSUS server

MDT 2010 comes with a number of task sequence templates. The one I used many times is the standard client task sequence template. As part of this template there are two tasks for applying Windows updates (Pre-Application Installation and Post-Application Installation).
These tasks are really useful as part of the deployment of a client machine because you have always an up to date image.


As part of this automated Windows Update process KB976002 will be downloaded and installed giving the options shown below in your core image.


Recently KB2019411 has been released which provides information about the Browser Choice update for system administrators who are in managed environments that are under a Volume Licensing program . De Deploymentsguys have created a MDT based script for implementing the suggestions in the article KB2019411. Adding the registry entries to control the display of the Browser Choice screen and to remove the Browser Choice icon from the desktop.

The script (CFG-HideBrowserChoice.wsf) should be placed in the MDT Distribution Share\Scripts folder and then a “Run Command Line” task should be added to your image engineering task sequence (after the last Windows Update task but before the sysprep and image capture tasks). The command you should run is cscript.exe CFG-HideBrowserChoice.wsf.

An example of this is shown below.


When the task runs, the script will turn off the Browser Choice and removes the icon from the desktop. You will also find a log file that the script generates in the usual MDT log location (MININT\SMSOSD\OSDLOGS\CFG-HideBrowserChoice.log)

You can get the CFG-HideBrowserChoice.wsf script from the Deployment Guys SkyDrive by clicking HERE

Tested and I worked great

Source: blogs.technet.com

Vizioncore release free VMware Management Pack for OpsMgr

Vizioncore, a wholly owned subsidiary of Quest have released a free Management Pack for System Center Operations Manager 2007 R2 which enables the monitoring of VMware virtual infrastructures.  Now, before I get into the features and capabilities of what the MP gives you, it’s important to point out that this is the first free MP to deliver these capabilities, and may stir things up a little over at both Veeam and Bridgeways, who both have established MP’s for OpsMgr to enable monitoring of VMware environments.  It’s important to say, both Veeam and Bridgeways offer trails of their solutions, so it would be important to compare the different MP’s for yourselves, however looking at a high level, one of the key elements that Veeam seems to have today, is that it’s PRO-enabled, thus provides more automated, dynamic and agile responses within the environment based on changing conditions.  That’s not to say both Bridgeways and Vizioncore won’t evolve their technologies in the future, and bring in PRO capabilities, however today, you would have to classify it as a differentiator for Veeam.  One you have to pay for however.

ScreenshotVizioncore Logo

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.


VMware vSphere 4.1 Released


Installation and Deployment


  • 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.



  • 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.


  • 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

VMware Workstation 7.1 is available

VMWare has released VMware Workstation 7.1.


What’s New in VMware Workstation 7.1

  • Support for 8 virtual processors (or 8 virtual cores) and 2 TB virtual disks.
  • Support for OpenGL 2.1 for Windows Vista and Windows 7 guests.
  • Greatly improved DirectX 9.0 graphics performance for Windows Vista and Windows 7 guests. Up to 2x faster than Workstation 7.
  • Launch virtualized applications directly from the Windows 7 taskbar to create a seamless experience between applications in your virtual machines and the desktop.
  • Optimized performance for Intel’s Core i3, i5, i7 processor family for faster virtual machine encryption and decryption.
  • Support for more Host and Guest Operating Systems, including: Hosts: Windows 2008 R2, Ubuntu 10.04, RHEL 5.4, and more Guests: Fedora 12, Ubuntu 10.04, RHEL 5.4, SEL 11 SP1, and more.
  • Now includes built in Automatic Updates feature to check, download, and install VMware Workstation updates.
  • Ability to import and export Open Virtualization Format (OVF 1.0) packaged virtual machines and upload directly to VMware vSphere, the industry’s best platform for building cloud infrastructures.

    Download VMware Workstation HERE. You need a valid VMware Account to download.

  • Windows 7 Sysprep


    Laatste versie van WAIK : KB3AIK_EN.iso Version 1.0
    Windows 7 Machine

    ISO of DVD van Windows 7 (x86 of x64)

    1. Open Windows System Image Manager

    2. Open de install_Windows 7 ENTERPRISE.clg deze vindt op DVD/ISO onder Sources

    3. Ga naar File New Answer File

    4. Ga naar File à Save Answer File à Ik noem bestand het unattend.xmlclip_image008

    5. Overzicht instellingen

    Overzicht instellingen
    1 WindowsPE


    2 OfflineServicing


    3 Generalize

    4 Specialize


    SkipAutoActivation: true


    Computer Name: * (Randomly generated name, use this to test)
    CopyProfile: false (Werkt niet)
    Registered Organization: Microsoft (laten staan)
    Registered Owner: AutoBVT (laten staan)
    ShowWindowsLive: false
    TimeZone: W. Europe Standard Time

    5 AuditSystem


    6 AuditUser


    7 OobeSystem


    InputLocale: nl-us
    SystemLocale: nl-us
    UILanguage: nl-us
    UserLocale: nl-us


    RegisteredOrganization: Bedrijfsnaam
    RegisteredOwner: Bedrijfsnaam

    x86_Microsoft-Windows-Shell-Setup_neutral component à OOBE:

    HideEULAPage true
    NetworkLocation: Work
    ProtectYourPC: 1

    6. Overzicht

    7. Disable Windows Media Player Networking Sharing Service

    8. Zorg dat je geen overbodige Partitie’s hebt zoals oude recovery partitie

    9. CMD prompt als administrator: net user administrator /active:yes

    10. Kopieer unattend.xml naar C:\windows\system32\sysprep. Even show hidden files & system files aan zetten.

    11. Open command prompt en ga naar C:\windows\system32\sysprep

    12. Voer het volgende commando in: sysprep /generalize /oobe /shutdown /unattend unattend.xml