Monday, December 17, 2012

ESXI license KY Lable Change for vSphere 4.x nad 5.x

Managing Licenses for the vSphere environment seems to be always a challenge for most of the administrators.

One complexity that gets added is if we have a single license Key spanning across multiple clusters.

 

I have come across similar situation. I used to use VMware Key Label field to specify the cluster for which the license is for.

So when it comes to this case we will have to sometimes go for renaming or changing the VMware Key Label values.

So if people like me are stuck then here is a simple way of changing the VMware License Key Label value from the vSphere Client.

 

 

The Label can be edited by.

1.)    Go to vSphere Licensing Page from Vsphere client

 

2.)    Select View By Product

3.)    Select the license Key which you would like to re-label

4.)    Click on the Label name

5.)    And Enter the desired Name.

Wednesday, April 25, 2012

Choosing The right Adapter for your VM environment.

Available Network Adapters

Only those network adapters that are appropriate for the virtual machine you are creating, are available configuration options in the Choose Networks window.

  • Vlance — An emulated version of the AMD 79C970 PCnet32- LANCE NIC, an older 10Mbps NIC with drivers available in most 32-bit guest operating systems except Windows Vista and later. A virtual machine configured with this network adapter can use its network immediately.
  • VMXNET — The VMXNET virtual network adapter has no physical counterpart. VMXNET is optimized for performance in a virtual machine. Because operating system vendors do not provide built-in drivers for this card, you must install VMware Tools to have a driver for the VMXNET network adapter available.
  • Flexible — The Flexible network adapter identifies itself as a Vlance adapter when a virtual machine boots, but initializes itself and functions as either a Vlance or a VMXNET adapter, depending on which driver initializes it. With VMware Tools installed, the VMXNET driver changes the Vlance adapter to the higher performance VMXNET adapter.
  • E1000 — An emulated version of the Intel 82545EM Gigabit Ethernet NIC. A driver for this NIC is not included with all guest operating systems. Typically Linux versions 2.4.19 and later, Windows XP Professional x64 Edition and later, and Windows Server 2003 (32-bit) and later include the E1000 driver.

    Note: E1000 does not support jumbo frames prior to ESX/ESXi 4.1.
  • E1000e - This feature emulates a newer model of Intel gigabit NIC (number 82574) in the virtual hardware. This is known as the "e1000e" vNIC. e1000e is available only on hardware version 8 (and newer) VMs in vSphere5. It is the default vNIC for Windows 8 and newer (Windows) guest OSes. For Linux guests, e1000e is not available from the UI (e1000, flexible vmxnet, enhanced vmxnet, and vmxnet3 is available for Linux).

  • VMXNET 2 (Enhanced) — The VMXNET 2 adapter is based on the VMXNET adapter but provides some high-performance features commonly used on modern networks, such as jumbo frames and hardware offloads. This virtual network adapter is available only for some guest operating systems on ESX/ESXi 3.5 and later.

    VMXNET 2 is supported only for a limited set of guest operating systems:
    • 32- and 64-bit versions of Microsoft Windows 2003 (Enterprise, Datacenter, and Standard Editions).

      Note: You can use enhanced VMXNET adapters with other versions of the Microsoft Windows 2003 operating system, but a workaround is required to enable the option in VMware Infrastructure (VI) Client or vSphere Client. See
      Enabling enhanced vmxnet adapters for Microsoft Windows Server 2003 (1007195) if Enhanced VMXNET is not offered as an option.
    • 32-bit version of Microsoft Windows XP Professional
    • 32- and 64-bit versions of Red Hat Enterprise Linux 5.0
    • 32- and 64-bit versions of SUSE Linux Enterprise Server 10
    • 64-bit versions of Red Hat Enterprise Linux 4.0
    • 64-bit versions of Ubuntu Linux

In ESX 3.5 Update 4 or higher, these guest OS are also supported:

    • Microsoft Windows Server 2003, Standard Edition (32-bit)
    • Microsoft Windows Server 2003, Standard Edition (64-bit)
    • Microsoft Windows Server 2003, Web Edition
    • Microsoft Windows Small Business Server 2003

Note: Jumbo Frames are not supported in the Solaris Guest OS for VMXNET 2.

  • VMXNET 3 — The VMXNET 3 adapter is the next generation of a paravirtualized NIC designed for performance, and is not related to VMXNET or VMXNET 2. It offers all the features available in VMXNET 2, and adds several new features like multiqueue support (also known as Receive Side Scaling in Windows), IPv6 offloads, and MSI/MSI-X interrupt delivery.

    VMXNET 3 is supported only for virtual machines version 7 and later, with a limited set of guest operating systems:
    • 32- and 64-bit versions of Microsoft Windows XP,7, 2003, 2003 R2, 2008, and 2008 R2
    • 32- and 64-bit versions of Red Hat Enterprise Linux 5.0 and later
    • 32- and 64-bit versions of SUSE Linux Enterprise Server 10 and later
    • 32- and 64-bit versions of Asianux 3 and later
    • 32- and 64-bit versions of Debian 4
    • 32- and 64-bit versions of Ubuntu 7.04 and later
    • 32- and 64-bit versions of Sun Solaris 10 U4 and later

Notes:

    • In ESX/ESXi 4.1 and earlier releases, Jumbo Frames are not supported in the Solaris Guest OS for VMXNET 2 and VMXNET 3. The feature is supported starting with ESXi 5.0 for VMXNET 3 only.

      For more information, see Enabling Jumbo Frames on the Solaris Guest OS (2012445).
    • Fault Tolerance is not supported on a virtual machine configured with a VMXNET 3 vNIC in vSphere 4.0, but is fully supported on vSphere 4.1.

 

·         For more information on network types, see Understanding networking types in hosted products (1006480).

 

Monday, January 9, 2012

How to Change Window XP Product Key and activation Code

XP promptly converts it into the system's product ID. Because of security concerns about piracy, Microsoft does not provide a tool that allows you to view the Product Activation Key (or CD Key) that was used to install the operating system. However, Windows XP Service Pack 1 ships with a list of the two product IDs that are created by the pirated product volume license product keys. (The Product ID can be found by right clicking My Computer and choosing Properties.)

To determine eligibility for the update, Service Pack 1 compares the Windows XP product ID on the system to this list. The comparison and the list reside locally on the users PC and no information is sent to Microsoft as part of this process. Service Pack 1 for Windows XP will fail to install on installations of Windows with one of the following product IDs: XXXXX-640-0000356-23XXX and XXXXX-640-2001765-23XXX

The following message will be displayed if installation fails for this reason:

Service Pack 1 Setup Error: The product key used to install Windows is invalid. Please contact your system administrator or retailer immediately to obtain a valid product key. You may also contact Microsoft Corporation's Anti-Piracy Team by emailing piracy@microsoft.com if you think you have purchased pirated Microsoft software. Please be assured that any personal information you send to the Microsoft Anti-Piracy team will be kept in strict confidence.

How to change your Product Activation Key in Windows XP
If the product ID matches the invalid keys above, you may need to change the key (re-enter a valid key) in order to install Windows XP service pack 1, and to make sure your environment is legal. You could completely re-install Windows XP Professional or you can try the method below. (Please backup your system before attempting this.) This workaround is only for the corporate editions of Windows XP Professional using a compromised or illegitimate key. Windows XP Home Edition and retail versions of XP Professional are not affected by Service Pack 1. Although this procedure may work with other versions of XP, we have only tested it on the corporate edition (volume license version) of Windows XP Professional.

Note: Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs.

Backup your Registry/System State

  • Backup your system state by clicking Start --> Run > and typing ntbackup -->. Click the Advanced Mode button in the Backup Utility Wizard. Click the Backup tab, then in Click to select the check box for any drive, folder, or file that you want to back up, select the System State.
  • As an alternative, you can backup just the Registry by clicking Start --> Run --> and type in Regedit From within the Regedit screen, right click My Computer, choose Export, name the file whatever you choose, and click Save.

To change the product ID

  • Log in as the local Administrator
  • Click Start --> Run --> and type in Regedit
  • Browse to: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\wpaevents
  • In the right pane, right-click OOBETimer, and then click Modify
  • Change at least one digit of this value to deactivate Windows
  • Click OK and close regedit
  • Click Start --> Run and type in: "%systemroot%\system32\oobe\msoobe.exe /a"
  • Click "Yes, I want to telephone a customer service representative to activate Windows, and then click Next
  • Click Change Product Key (at the bottom)
  • Enter your valid Corporate Product Key
  • Press Update and close the window.
  • If you are returned to the previous window, click Remind me later
  • Restart your computer

Verify the change

  • After the workstation restarts, click Start --> Run
  • Type in: "%systemroot%\system32\oobe\msoobe.exe /a" without the quotes.
  • Make sure the dialog box says 'your copy of windows is already activated'

If you performed the above steps incorrectly, or used an invalid key, your system may not be able to boot. Use the F8 key to boot to the last known good configuration and retry with a valid key.

Troubleshooting
If you tried the above steps and nothing happens:

  • Make sure you are logged in with the local administrator account, not just an account with Administrator privileges.
  • Try replacing the %systemroot% variable with the actual drive letter that your actual directory path, especially when dual booting, or if the system path is on a drive other than C:\
  • On a normal Windows XP installation, your systemroot should be C:\windows\ so the command should be C:\Windows\system32\oobe\msoobe.exe /a
  • On systems upgraded from Windows NT/2000, the systemroot directory may be C:\Winnt\ so the command should be C:\winnt\system32\oobe\msoobe.exe /a
  • Make sure you include a space between .exe and /a in the command:
    * Correct - C:\winnt\system32\oobe\msoobe.exe /a * Incorrect - C:\winnt\system32\oobe\msoobe.exe/a
  • Product keys for XP Home Edition and retail versions of XP Professional will not activate a corporate or OEM version of XP Professional. The algorithms are different.
  • If you do not have a valid installation key for Windows XP, DO NOT e-mail us asking for a key, keygen or a crack.

Scripting the process
Microsoft has provided sample scripts for remotely updating the Product ID on multiple machines in KB Article Q328874.

 

Monday, January 2, 2012

Feature comparisons of Windows 7 Versions.

Feature comparisons of Windows 7 Versions.









Starter



Home Premium
Upgrade
$119.99*
Professional
Upgrade
$199.99*
Ultimate
Upgrade
$219.99*
Communication
Entertainment
Create and play DVDs
Performance
Productivity
Safety and Security
Advanced Backup and Restore (Network Backup and Group Policy)
For IT Professionals
Direct Boot from VHD
Enterprise Search Scopes
Virtual Desktop Infrastructure (VDI) enhancements***