This article explains how to setup an iPhone to access an Office365 mailbox.

Due to frankly enormous demand for migration services, my company has setup a dedicated team for Office365 migrations. You can view their website here:-www.migrateoffice365.co.uk . If you are looking for help please get in touch!

Add Exchange Account to iPhone

On your iphone go to “Settings”, “Mail, Contacts, Calendars” and select “Add Account”

Select Microsoft Exchange

Enter your email address, your username (usually the same as the email address and your office 365 password. You don’t need to enter anything in the domain field.

Tap next and your iphone will try to autodiscover your server details. If it can’t find these you will need to enter the server name of your office365 server – see below.

Otherwise click save and you have setup your iPhone.

Optional – If asks for server name

You can get the server name from the Office365 webpage.

Logon to office365 at portal.microsoft.com

Go to your inbox and click on the “?” icon and then select about.

Your servername is listed as shown below.

This article explains how to move a DHCP database from a Windows 2003 server to a Windows 2008 R2 server.

It is assume that you are a domain admin and that you have installed the DHCP role on the Windows 2008 R2 server.

Export DHCP database

• On the Windows 2003 server open a command prompt and enter the command:

netsh dhcp server export C:\dhcp.txt all

• This will create a text file containing the DHCP settings for the windows 2003 server. Note that above I have called the text file server212-dhcp.txt
• You may want to stop the DHCP service on the windows 2003 server at this point.

Import the DHCP database

• Copy the file created above onto the Windows 2008 R2 server.
• Open an elevated command prompt

• Then enter the command

netsh dhcp server import c:\dhcp.txt all

Setup DHCP on Windows 2008R2 server

• I suggest opening the DHCP management console on the Windows 2008R2 server and checking that all info has come over. If you haven’t already you will need to authorise the Windows 2008 R2 server for DHCP.

• After a short while you should see a green tick next to IPv4 as shown below.

• I suggest testing this on a client PC to make sure that all is now working.

Disable DHCP on Windows 2003 server

• On the windows 2003 server I recommend removing authorisation for DHCP.

• You can then either uninstall DHCP from add/remove programs or stop and disable the service.

THE END

 

Install Dell OpenManage on Hyper-V Server 2008 R2

 

Note this document explains the installation of Dell Openmanage on Hyper-V Server 2008 R2 – this is the “free” version of Hyper-V based on Windows Core. This does not cover adding the Hyper-V to a “full” installation of Windows.

You will need the Dell Systems Management and Tools DVD. If you do not have this then I suggest downloading Dell OpenManage Managed Node from the Dell website.

Pre-Requisite Checks

• On the Hyper-V console go to the CMD prompt and change to the DVD drive (e.g. d:)
• Then enter:-

  cd \SYSMGMT\srvadmin\windows\PreReqChecker
  

  runprereqchecks.exe /s
  

• You should get no output. If you get an error code returned please see this document for more info

Installation

• Again in the CMD prompt enter:

  cd \SYSMGMT\srvadmin\windows\SystemsManagement\
  

  msiexec /I SysMgmt.msi
  

This will install Dell Open Manage on the server. You then need to open the firewall to allow incoming connections on port 1311. Enter the below command

        netsh firewall add portopening TCP 1311 DellOpman enable subnet

The installation is now complete. You can verify this is working by going to

https://IP-address-of –HyperV-server:1311

e.g.

 

Server 2008 R2 Editions

 

Hyper V installation

Pre-requisites:

• Min 1.4GHz x64 processor
• Intel VT or AMD-V technology enabled
• Hardware Data Executino Prevention (DEP) enabled (Intel XD bit or AMD NX bit)
• 1GB RAM
• 8GB Disk Space

You can install Hyper-V via the following commands

• Start /w ocsetup Microsoft-Hyper-V (full windows installation – not core)
• Add-WindowsFeature Hyper-V (powershell)
• Use “server manager” and select the HyperV role
• Also adding a server to SCVMM will automatically install HyperV

Features

• Dynamic Memory – included with 2008R2 SP1. Allows the memory allocated to a VM to be dynamically adjusted allowing for great VM density.
• Pass-thru – HyperV allows you to directly access storage directly mapped to the HyperV host. To ensure the guest has exclusive access to the disk it should be placed offline.

System Center 2012 Virtual Machine Manager (SCVMM)

Installation Pre-requisites:

 

When deploying or migrating VMs SCVMM it is possible to specify placement goals

• Maximization – Choose this option if you want to fully utilize one host before assigning virtual machines to additional hosts
• Load Balancing – Distribute the performance load of your virtual machines evenly across your hosts.

There are 3 roles that can be assigned in SCVMM

1. Administrator – Full Access
2. Delegate Administrator – Full access to only Host and Libraries defined in the scope
3. Self Service User – Can administer there own VMs via the self service portal.

P2V Conversions

To perform a P2V conversion, your source computer:

• Must have at least 512 MB of RAM.
• Cannot have any volumes larger than 2040 GB.
• Must have an Advanced Configuration and Power Interface (ACPI) BIOS – Vista WinPE will not install on a non-ACPI BIOS.
• Must be accessible by VMM and by the host computer.

Offline P2V conversions:-

• Are required for Windows 2000 computers and FAT volumes
• Are recommended for domain controllers and ensuring data consistency

V2V

iSCSI Configuration on Server Core

• When running server core use iSCSICPL.EXE to launch the iSCSI GUI
• Run iSCSICLI.exe to configure via the command line

Misc

• HyperV does not support NAS devices

Networking

• Internal – Allows VMs on the host to communicate with each other. Not bound to a physical NIC. Can access the host
• Private – allows VMs on 1 host to communicate with each other but not outside the host. Not bound to a physical NIC. Cannot access the host
• External – bound to an physical NIC. Able to access VMs on the host and external network.

VMs

Hardware

• Supports up to 4 SCSI controllers
• The startup disk must be connected to an IDE controller
• You have to shut down the VM to add a disk to an IDE controller. You can add disks to SCSI controllers without shutting down.
• You need to use a “legacy network adaptor” if installing the OS over the network

Files

• .XML – the virtual machine configuration details. There is one of these for each virtual machine and each snapshot of a virtual machine. They are always named with the GUID used to internally identify the virtual machine or snapshot in question.
• .BIN – contains the memory of a virtual machine or snapshot that is in a saved state.
• .VSV – contains the saved state from the devices associated with the virtual machine.
• .VHD – the virtual hard disk files for the virtual machine
• .AVHD – the differencing disk files used for virtual machine snapshots

Snapshots

• If you delete a snapshot when the VM is running the .avhd file is not deleted until the vm is shutdown

 

Important Powershell Commands

• Run the command Add-PSSnapin Microsoft.SystemCenter.VirtualMachineManager to load the VMM cmdlets.
• Disable firewall netsh firewall set opmode disable
• Suspend-clusterresource – put a (clustered) disk into maintenance mode without triggering failover
  

iSCSI

• iscsicli QAddTarget <IQN- of-target> – Add the target
• iscsicli QloginTarget <IQN- of-target> – login to target
• iscsicli PersistentLoginTarget <IQN- of-target> – make persistent

Performance and Resource Optimization (PRO)

• Requires SCVMM and SCOM (System Center Operations Manager)
• PRO can recommend or initiate remedial actions via PROtips
• For example PRO can be used to load balance VMs across Hosts

VMM Library

• Used to store objects not associated with an individual host such as; virtual hard disks, virtual floppy disks, ISO images, templates, operative system profiles, hardware profiles etc.

Live Migration

• Requires failover clustering to be setup on the servers running HyperV
• Each HyperV host must have the same network configuration (i.e. the virtual networks must have the same name) or you may lose VM connectivity after a live migration.
• You can only run 1 live migration per host (concurrently)

Remote Desktop

• Connection Authorization Policy – Used to provide access for remote clients to internal resources

Failover Clusters

• You can identify the network used for cluster shared volumes (CSV) and prioritise the traffic accordingy. To edit the priority use the powershell command Get-ClusterNetwork and edit the metric value.

Managing VMware

• You must add a virtual center server before you can manage any VMWare hosts

In this article I am setting up replication between 2 equallogics based in different offices. The equallogics are in different groups and on different subnets.

Pre-requisites

• 2 Equallogic Arrays each setup in a separate Equallogic groups
• Connectivity between iSCSI networks. i.e. the iSCSI networks must be able to communicate with each other.

Configure Replication Partner

Login to the Array/Group you want to protect and click on “configure partner”

Enter the Group IP address of the other partner

Specify contact information and a password.

Note that in the below you are specifying the amount of space on the HQ SAN for replication from the DR SAN. You may not need this at all.

You should then log onto the Equallogic array in the other office and set this up in the same way.

Create Volume Collection (optional)

A volume collection is a just that – a collection of volumes. It allows you to apply the same replication (or snapshot) settings to a group of volumes.

Setup Replication

Once the Volume set is created you can setup replication for it. You can also do this for individual volumes.

 

Create Schedule

Specify the schedule – the below if for Daily at 8pm.

The LUNs are now configured to replicate.

Monitor Replication

You can monitor the progress of replication here.

END

This article explains how to setup an VMWare vSphere ESXi 5.0 host with an Equallogic array. This is all performed via the GUI.

Note that the setup for this includes a vmkernal heartbeat instance as recommended by vmware (here) and equallogic (here).

Add iSCSI initiator

 

Setup iSCSI vSwitch

In the networking section click on “add networking”

Select the network adaptors you have connected to the iSCSI switch

Give the switch a name (e.g. VMkernal heartbeat)

Assign an IP address

Click finish.

Configure first iSCSI VMkernel instance

Go to the properties of the switch you just created.

Click on add

Select VMkernel. Click next

Give the instance a name – e.g. “iSCSI 1″

Specify an IP address.

Click finish.

We must now edit the NIC binding policy for this iSCSI instance. Go to the properties of the vSwitch.

Click on edit.

Set the failover order so 1 NIC is active and 1 in unused.

Click ok.

You should now have a setup like this.

Now run through the above process again to create a 2^nd iSCSI VMkernal instance. Use a different IP address and when creating the failover properties of the second instance make sure that the other NIC is active.

You should now have a setup like this.

Click close. The networking setup should now look like this.

Bind VMKernal Adaptors

We bind each of the iSCSI instances created above with the iSCSI iniator.

Go to the properties of the iSCSI initiator (created in the first step).

Go to “network configuration”, click “add”. Then select each of the iSCSI instances.

You should end up with a setup like this.

Click close.

Jumbo Frames

I recommend you enable jumbo frames. However you can only enable jumbo frames if they are enabled on every device on your iSCSI network (e.g. the physical iSCSI switches). To enable jumbo frameson the vSwitch change the MTU value as shown below.

You also need to enable jumbo frames on each iSCSI instance

 

Enter Equallogic Details

Go to the properties of the iSCSI initiator.

Go to the dynamic discovery tab and enter the Group IP address of the Equallogic.

If your equallogic array uses chap to control access you will need to specify the details as shown below.

Click ok, then close. You should be prompted to scan the adaptor. Please do so, it may take a few minutes.

Finally – You should now be able to view LUNs

 

 

This article discusses how to install the Equallogic Multipath Extension Module (MEM) using the vSphere CLI.

Download the Equallogic MEM

Go to the equallogic website and download the Multipath Extension Module (MEM).

Copy the MEM to the ESXi server

Extract the .zip file you have downloaded.

Copy the .zip onto a datastore on the ESXi host. (In this example it is dell-eql-mem-esx5-1.1.0.222691.zip)

Download the vSphere 5.0 CLI

If you haven’t already got the vSphere CLI v5.0 installed on your PC you will need to download and install it.

Install the MEM

You will need to put the ESXi host into maintenance mode.

Open the vSphere CLI (vCLI) and enter the below command….

esxcli –server=X.X.X.X software vib install –depot /vmfs/volumes/YYYY/ dell-eql-mem-esx5-1.1.0.222691.zip

where:-

X.X.X.X = the IP address of your ESXi server

YYYY = The name of the datastore – note this is case sensitive

The Dell Equallogic Multipath module is now installed. You can verify this by clicking on the “manage paths” button in you datastore properties.

February special offers from www.123-reg.co.uk

• 25% off hosting packages, using code – febhosting25
• 20% off .org domain, using code – feborg20
• 15% off domain privacy, using code – febwhois15

All these offers will expire February 29th 2012.

If you plan to use these codes please click on my referral link to take you to www.123-reg.co.uk

The below example shows how to open up a Cisco PIX or ASA firewall to allow direct connections to a server on the inside network. In general you need a NAT and access rule to make this work. This is known as adding a static NAT rule or “port forwarding”.

ASA Version 8.3

In the latest versions you can create a NAT rule from the network object. Click on the NAT arrow and fill in the details as shown below.

You then need to create a corresponding access rule

PIX Version 7.2(1)

This shows how to publish a web server (HTTPS)

Access Rule:

 

NAT rule:

INSTALLATION

Hardware Requirements

Taken from vmware.com

• 64-bit x86 CPUs with at least two cores.
• ESXi 5.0 supports only LAHF and SAHF CPU instructions.
• Supports up to 2TB RAM although the free version is limited to 32GB
• ESXi requires a minimum of 2GB of physical RAM. VMware recommends 8GB of RAM to take full advantage of ESXi features and run virtual machines in typical production environments.
• One or more Gigabit or 10Gb Ethernet controllers.
• Any combination of one or more of the following controllers:
  • Basic SCSI controllers. Adaptec Ultra-160 or Ultra-320, LSI Logic Fusion-MPT, or most NCR/Symbios SCSI.
  • RAID controllers. Dell PERC (Adaptec RAID or LSI MegaRAID), HP Smart Array RAID, or IBM (Adaptec) ServeRAID controllers.
  • SCSI disk or a local, non-network, RAID LUN with unpartitioned space for the virtual machines.
• For Serial ATA (SATA), a disk connected through supported SAS controllers or supported on-board SATA controllers. SATA disks will be considered remote, not local. These disks will not be used as a scratch partition by default because they are seen as remote.

Note can upgrade from ESX and ESXI 4.x to ESXi 5.0

Image Builder

• Image Builder allows VMware Admins to customize their installation media by adding and removing VMware Infrastructure Bundles (VIBs).
• You can only add VIBs to an image with an “acceptance level” of VMWareCertified and VMWareAccepted. PartnerSupported and CommunitySupported VIBs cannot be added

Host Profiles

Allows you to create a “baseline” of settings/configurations that can be applied to multiple ESXi servers. It helps maintain consistency. Popular options to set are DNS and NTP.

Auto Deploy

Is setup via an OVF template with DHCP, TFTP, HTTP servers and a deploy-cmd CLi and Database. Note that the ESXi install is stateless – the OS is gone on reboot! The auto-deploy process is:-

• PXE boot the target server
• ESXi is then auto-deployed to the host
• The ESXi host will then be added into your vCenter
• The ESXi host will then have a Host Profile applied to it.

You manage your auto-deploy images via Power-CLI – e.g. you can create rules to associate hosts with image profiles, host profiles and location on vCenter.

STORAGE

VMFS-5

• 64TB device support
• Unified block size (of 1MB). Note that volumes upgraded from VMFS 3 will retain their original block size.
• Improved sub block mechanism – for files smaller than 1kb, sub blocks are used for better performance.
• Support for pass-through RDMs larger than 2TB
• Upgrade from VMFS3 does not require downtime.
• The partition format for upgraded VMFS3 partitions will change automatically & seamlessly from MBR to GPT when the size of the upgrade VMFS-5 volume is grown above the 2TB threshold.
• Supports RDM sizes of 64TB in physical compatibility mode and 2TB-512bytes in virtual compatibility mode

Storage DRS

• Provides smart virtual machine placement and load balancing mechanisms based on I/O and space capacity.
• Works with VMFS and NFS although it’s not recommended to mix the 2 in a datastore cluster.
• Datastore clusters – a collection of datastores. This forms the basis of DRS
  • During the configuration of a virtual machine you can store its drives on a datastore cluster and vSphere will decide where they are physically stored.
• I/O load is evaluated by default every 8 hours.
• Affinity Rules – Decide which virtual disks can be place on the same datastore. There are 3:
  • VMDK Anti-Affinity – Virtual disks of a virtual machine are placed on different datastores.
  • VMDK Affinity – Virtual disks are kept together on the same datastore.
  • VM Anti-Affinity – Two specified virtual machines, including associated disks, are placed on different datastores.
• There is a datastore maintenance mode which will migrate all data off a datastore (i.e. much in the same way as server maintenance mode)

Profile Driven Storage

• Allows the placement of virtual machines based on a number of requirements (performance, availability SLA etc)
• Storage capability are either passed to vSphere via the storage API or they can be manually set
• Support NFS, iSCSI and FC

Storage VMotion

• You can now vMotion VMs with snapshots
• Is more efficient in vSphere 5 due to mirror mode which uses the mirror driver
• You cannot use storage vMotion with NPIV
• You cannot perform a storage vMotion during the installation of VMWare tools

iSCSI Initiator

• No longer requires configuration through the command line
• Discovery methods are “send targets” and “static target”

Fibre Channel over Ethernet Software Initiator

• Enables the use of FCoE without an FCoE adapter
• Requires a network adaptor that can support partial FCoE offload capabilities

Storage I/O Control

• Set shares and limits for datastores (including NFS)
• Doesn’t support RDM
• Doesn’t support datastores with multiple extents
• Must be managed by a single VC

vSphere Storage APIs – Array Integration (VAAI)

• vSphere Thin Provisioning
  • Dead Space Reclamation – informs the array when files are moved/deleted
  • Out-of-Space Conditions – will warn when LUNs are running out of space
• Hardware acceleration for NAS –
  • Full File Clone – Similar to Full Copy. Enables virtual disks to be cloned by the NAS device
  • Reserve Space – Enables creation of thick virtual disk files on NAS
• Complies with the SCSI T10 standard ( for full copy, block zeroing and hardware-assisted locking)

SAN Configuration

• It is recommend to have only 1 VMFS volume per LUN
• The diagnostic partition should not be setup on a SAN (unless the servers are diskless)
• Each LUN must present the same LUN ID to enable multipathing
• You can set the queue depth for the HBA during system setup

Placement Schemes

• The predictive scheme utilises a number of LUNs with different storage capabilities
• Adaptive scheme utilises a smaller number of large LUNs

Multipathing Policies

Where there are multiple paths to storage the following multipathing polices can be used:-

1. Most Recently Used (MRU) – Uses the path found at boot time.
2. Fixed – Uses the “preferred flag” attribute if set.
3. Round Robin (RR) – Cycles through the available paths
4. VMW_PSP_MRU – called VMW_PSP_FIXED_AP in previous versions. Will query the storage array for the preferred path.

NETWORKING

vSwitches

• Now supports Realtek network cards
• Teaming and failover options for virtual Distributed Switches (vDS)

Distributed vSwitches (DvS) v5.0 have the following new features:-

• User-defined network resource pools in network i/o control
• Netflow and port mirroring

The dynamic binding dvport type has been removed in 5.0

Configuration options for vSwitches

• Promiscuous mode – Enables a vNIC to receive all traffic passed on a vSwitch.
• Forged Transmits – Allows a vNIC to send traffic with a “fake” MAC address
• MAC address changes – allows the guest OS on a VM to change its MAC address
• The notify switches option will notifiy physical switches when a virtual NICs location changes – i.e. after vmotion

ESXi shapes outbound traffic on vSS and inbound and outbound traffic on vDS. The following traffic shaping options are given:

• Average bandwidth – The number of bits per second averaged over time (kbits)
• Peak Bandwidth – Maximum number of bits per second when sending or receiving a burst (kbits)
• Burst size – Maximum number of bytes to send in a burst “bonus”. If a port doesn’t use all its allocated bandwidth it has the option to use a burst “bonus” (kbytes)

SplitRX

• Uses multiple CPUs to process a network load. Can provide improved network performance.
• Only support on VMXNET3
• Must be enabled in the vmx file

Network IO Control

Only available for vDS. It allows you to control traffic by class. For each class you can assign shares, specify a host limit or QoS. The predefined classes are:-

ADMINISTRATION

 

Virtual Machines

• Now supports “monster VMs” with up to 32 vCPUs and 1TB of memory
• VMDK’s are still limited to 2TB – 512 bytes
• Thick provisioned eager-zeroed disks provide the best performance (the whole disk is written with zeros.)
• Must be running at least hardware version 4 to be supported by ESXi 5.0
• vlance is a legacy adapter. VMXnet are better optimised and offer gigabit connections but require vmtools

High Availability

• Uses an agent called Fault Domain Manager (FDM)
• vSphere 5 elects one host as the “master” whilst the rest are “slaves”
• The master is responsible for monitoring the state of VMs and restarting failed VMs
• Uses a network and datastore heartbeat to determine whether hosts have failed. The datastore heartbeat is only used when the network heartbeat has failed.
• HA slot sizes are used to calculate the number of VMs that can be powered on in an HA cluster with “Host failures cluster tolerates” selected. The slots size is calculated based on the size of reservations on the VMs in the cluster. HA Admission Control then prevents new VMs being powered on if it would not leave any slots available should a host fail.

vSphere Update Manager

Baselines for VM upgrades:-

• VM Hardware upgrade to match host
• VM Tools Upgrade to match host
• VA upgrade to latest (virtual appliance)
• Cannot upgrade vCenter appliance – need to install a brand new appliance and import the config

vSphere Web Client

An optional component of vCenter that allows for management of vCenter via a web interface (https://localhost:9443/vsphere-client/ui.jsp)

vAPP

A way of grouping VMs, resource pools or other vApps so you can manage then (e.g. apply performance criteria, shutdown, etc)

Backup

• You can backup an ESXi hosts config with vicfg-cfgbackup –s command (in the vi-client or vma).

vCenter Server Linked Mode

• vCenter does not support linked mode with older versions of vCenter
• Will store information for every vCenter server (including roles and licenses) in a Active Directory Application Mode (ADAM) DB on each vCenter.
• Allows you to search across all vCenter instances
• View all inventories in a single view
• You cannot migrate hosts or VMs between vCenter servers connected in linked mode

Unplanned device loss

• This is when a ESXi thinks that a storage device is permanently unavailable – e.g. deleted, unmapped or hardware error
• You should do an adaptor rescan to remove any links to the device
  

Fault Tolerance

• Supports VMDK’s and RDMs that are thick provisioned. If disks are thin provisioned you are prompted to convert them.
• Single vCPU
• VM must be running a supported guest OS (windows, solaris, netware, free BSD)

Scheduled Task Options

Ports

 

PERFORMANCE

 

Resource Pool

In a Resource Pool you can set shares, reservation and limits for CPU and Memory Resources

• Shares – either low, normal or high. A resource pool with a “high” share will have more access to resources that a resource pool with “low” shares.
• Reservation – A guaranteed allocation
• Limits – The maximum amount allocated

Expandable Reservation – when ticked a VM can uses resources from further up the hierarchy if available.

Key ESXTOP/RESXTOP fields

 

VMX Swap

Virtual Machines Executable (VMX) swap files allow ESXI to swap to disk some of the memory it reserves for the VMX process (e.g. virtual device monitor)

Swap to Host Cache

vSphere 5 reclaims memory by storing the swapped out pages in the host cache on a SSD. This is obviously faster than storing on a non-SSD

vNUMA (Non Uniform Memory Architecture)

• Allows Guest OSes to identify that they are running on NUMA topology. Provides a performance increase by cutting down on non-local memory access.
• Only enabled on VMs with more than 8 vCPUs

 

OTHER VMWARE PRODUCTS

vCenter Heartbeat

• Used to provide high availability for vCenter through the use of a backup vCenter.
• Will monitor the network, OS, applications and hardware of the vCenter server. In the event of a failover a backup vCenter server will take over.
• Replicates all settings from the “live” to the “backup” vCenter

vCloud Director

• Used by enterprises to build private clouds
• Software that allows vSphere resources to be managed as a web-based service.

vCenter Orchestrator

• Used to allow for automation and orchestration in your virtual environment

vCenter Data Recovery (vDR)

• The vCenter Data Recovery Appliance is a disk-based backup and recovery solution that enables quick, simple and complete data protection for virtual machines.
• Installed as an OVF appliance you need to install a plugin for vCenter
• There is also a windows installer package that allows you to mount backed up vmdks
• Each vDR appliance can have no more than two dedupe destinations
• It is recommended that each dedupe destination is no more than 1TB in size when using virtual disks, and no more than 500GB in size when using a CIFS network share.

VMWare Storage Appliance

Installed as a vCenter plugin, during installation it automatically

• creates a HA cluster containing selected ESXi servers
• Creates VSA front end and back end as well as vMotion networks.
• Creates a VSA VM on each ESXi server
• Setups up and NFS server in each VSA VM which is present back to ESXi

 

LICENSING

 

vSphere 5 is licensed on a per physical processor basis with a vRAM entitlement. vRAM entitlements can be pooled across multiple servers.

Figure 1 – taken from vmware.com

vSphere Kits

Kits are all in one packages to enable companies to deploy a complete vmware infrastructure.

Figure 2 – taken from vmware.com