VMware vSphere: Products, Price and Features

VMware vSphere is the first cloud computing systems in information technology industry. There is no doubt about ESX’s reliability and performance. With the release of ESX 4.0 aka vSphere, there will be few features inbuilt into ESX 4.0 and rest are add on depending on how deep is your wallet. 

vSphere basic components are VMware ESX or VMware ESXi hypervisor, VMware VMFS, VMware vSphere Client, Four-way vSMP support. ESX products are divided in two categories with sub-categories based on customer needs and affordability.

Figure: ESX Product comparison source http://www.vmware.com

ESX aka vSphere small business product is available in Essentials and Essential Plus sub-category. These are bundled products with targeting small business customer who aren’t willing to spend money but to have virtualized servers. Hence saving money for hardware and management cost. These version of license doesn’t contain any DRS, vMotion, hot Add, vShield  luxury. But it works perfect if you want to virtualize 20+- servers. You can have maximum 3 ESX hosts with 2 processors each up-to 6 core per processor.  ESX small business editions are priced in-between USD995 to USD2995. Essential got an year support within price. But you have buy additional support for Essential Plus and it’s mandatory. I reckon, Mr Paul Maritz  released these editions to target Microsoft Hyper-v and off course you can use ESX without getting your hand into wallet i.e.  ESXi single server version without spending $$$.

vSphere Editions sub-divided into standard, Advanced, Enterprise and Enterprise plus categories. These four editions got variety of flavour a VMware Administrator wants to play with. VMware data recovery, fault tolerance, hot add, Host profiles, thin provisioning, vNetwork distributed switch, vSheild Zones, DRS, DPM, vMotion and lots more. You can have these cool features based on your need and $$$$. vSphere editions are priced from US$795/processor (six core/processor) to US$2875/processor (six core/processor). A minimum one year support agreement is required with all vSphere products.

To deploy ESX with complete functionality you must have vCentre server and SAN. You can manage, update, secure, provision and orchestrate any operation through vCentre. You have to purchase vCentre Server separately to do all cool stuff.

In conclusion, I would recommend investigating individual need and business objectives. It’s good to have a business case and technical overview what you are going to achieve after spending on hardware and hypervisor.

References:

Virtualization Assessment Tool 

Pricing Guide

TCO/ROI Calculator

Technical Resources

How to create answer file for windows 7 WDS client

Download and install Windows 7 AIK on admin PC or WDS server

Open windows system image manager>File>New Answer File>Yes

Browse>select install.wim file>yes

Now modify according to your need. you may delete unnecessary catalogs. If you are using existing image then you don’t need to use create partition option. Modify partition is ok. You must keep join domain catalog.  Also it doesn’t hurt anybody if you mention product key. Don’t mention domain credential in log in catalog then it will not ask domain credential after pressing F12. It’s unsafe. Now save this file in WDS server in WDS_unattended folder. 

You may also create answer file using sample answer file provided in %WINDIR%\program files\Windows AIK>Samples. In this case, don’t modify original. Copy original and paste>rename>modify and use it.

Now, Systems Admin can

Deploy Windows 7 using Microsoft Deployment Toolkit 2010……..Life is easy for Systems Admin

Have you added drivers after riprep in Windows 2003 RIS? Moreover, you prepared master pc, patched up, installed application and waited hours to do riprep. If you forgot to add a patch or application then gotcha!! Redo the whole thing again. I bet, you been through all these. That’s over now.

Microsoft Deployment Toolkit 2010 (MDT 2010) is a comprehensive tool that makes Windows 7 and windows Server 2008 deployment easy. I would say it made my life more comfortable when I deployed Windows 7. You will not go through all the hassles you did while adding drivers and applications in a deployable reprip image in RIS server. It’s more fun with Windows Deployment Services, windows 7 Automated Installation Kit and MDT 2010. Cheers to Microsoft. You can fully automate desktop and server deployment using Microsoft Deployment Toolkit 2010.

MDT provides you with the following benefits:

• common deployment console for desktop and server deployment
• Reduced deployment time and standardized desktop and server images
• Fully automated Zero Touch Installation
• Access from anywhere i.e. WDS server, DFS shares, Admin PC or organisation wide
• Manage drivers, operating systems, applications, packages and tasks
• Automate using Windows PowerShell command.
• Choose x86 or x64 depending on host hardware and OS
• Build ISO image or WIM file

Systems Requirement:

Windows Server 2008

Windows Deployment Services

Windows Automated Installation Kit for Windows 7

Windows 7 DVD/source

Microsoft Deployment Toolkit 2010

Working with MDT 2010:

Download and install Windows  AIK and MDT in admin pc. Create two shared folder, copy all source files (windows 7, drivers and applications) in one folder and another for WIM and ISO that will be created by MDT. Now follow the screen shots.

Step1: Prepare MDT

Step2: Add Windows 7 Source files

For this article, I kept only Business Edition and remove other versions.

Step3: Add Applications like Office 2007, Adobe, Antivirus

Step4: Add drivers. for this article I added Intel DQ35JOE drivers

Step5:Create task. Here you have the option to create ISO or WIM file for WDS.

 

Step6: Run Update

Once update finish, you can use boot disk ISO. If you select sysprep and capture without selecting standard client task sequesnce you can create WIM file, then you can directly insert into WDS server and deploy.

I found MDT is very handy and smarter tools for systems administrator. I would recommend to create a testbed before going for full deployment. Then you will have the flexibility to get desired image.

Windows XP SP3: Network deployment

• Download Windows XP SP3
• Save it in network share
• Open command prompt and go to the location where you have saved service pack 3
• Type WindowsXP-KB936929-SP3-x86-ENU /x to extract service pack
• Open group policy management console
• Create and link new GPO and name it as XP SP3
• Right click on SP3 GPO>Edit>Computer Configuration>Software Settings>Software installation
• Right click software installation>new>Package
• Browse location of Win XP SP3\i386\update\update.msi , select update.msi and click on assign>apply
• On next reboot of desktop fleet, Windows XP SP3 will automatically be deployed.

ESX 4.0: tech support mode and command ref

Just like another Linux operating systems, you can access ESX 4.0 from console. On the console, press ALT+F1 to log on to tech support mode. Another option is to telnet or ssh using putty. You have to know Linux command and other propitiatory command used by VMware.

• Download Putty
• Open Putty>type IP address of ESX Host
• Select Protocol i.e. Telnet or SSH (Must be enabled in ESX Host)
• Click open>yes.

 

Command References

Hostname  #hostname

Version #vmware -v

Name and management IP # vi /etc/hosts

DNS Name #vi /etc/resolv.conf

NTP server #vi /etc/ntp.conf

Telnet/SSH #vi /etc/inetd.conf

 

Gateway #vi /etc/sysconfig/network

Management NIC #esxcfg-vswitch –l

 

master Config #vi /etc/vmware/esx.conf

Virtual machine #cd /vmfs/volumes/datastore1

Show all files and folder #ls -la

Seeking help with ESX Command, type the command followed by –h

Lists of few Commands

Networking	Storage	Service Console Administration
esxcfg-firewallesxcfg-routeesxcfg-vmknic esxcfg-vswitch esxcfg-nics esxcfg-vswif	esxcfg-dumppartesxcfg-mpathesxcfg-nas esxcfg-rescan esxcfg-swscsi	esxcfg-infoesxcfg-advcfgesxcfg-resgrp vmkpcidivy

Exchange 2010: installation error

I experienced few errors while installing exchange 2010 on test bed. I reckon, I should share the resolution with you guys testing exchange 2010…

hub transport role fails to install

The execution of: “$error.Clear(); if($RoleStartTransportService) { start-SetupService -ServiceName MSExchangeTransport }”, generated the following error: “Service ‘MSExchangeTransport’ failed to reach  status ‘Running’ on this server.”

Cause: TCP/IP6 disabled or unchecked on TCP/IP properties of windows 2008 server.

Resolution: If you are not using tcp/ip6 then disable TCP/IP6 permanently to resolve the issue. To completely disable IPv6 on a Windows Server 2008, follow these steps:

1. Start menu>run>regedit.exe>ok
2. HKLM>system>CurrentControlSet>Services>tcpip6>parameters
3. Right Click on Parameters>New>DWORD (64-bit) value
4. Type DisabledComponents, and then press ENTER.
5. Double-click DisabledComponents and then type 0xffffffff in Hexadecimal or 4294967295 in Decimal
6. Reboot server

2007 Office System Converter: Microsoft Filter Pack

I have been given warning for 2007 Office System Converter pack not installed while prerequisite check before installation start.

Resolution: Download Office System Converter and install before proceed further.

Desktop Experience Features

I installed exchange 2010 on Windows 2008 R2. I have been given another warning for Desktop Experience feature not installed in server.

resolution: install desktop experience

Start menu>Administrative tools>Server Manager>Features>Add Features>follow installation screen

Microsoft Exchange 2010 RC —–First Look