Linux Guest Different MAC Address Error on VMware vSphere

Converted a Linux (Fedora 5) PC to a VMware vSphere guest.  The Linux guest OS shows a failed message when shutting down interface eth0.

Fix: edit /etc/sysconfig/network-scripts/ifcfg-eth0’s HWADDR to match the MAC address assigned the Linux guest OS.

Linux Guest Hangs at “Starting udev” on VMware vSphere

Converted a Linux (Fedora 5) PC to a VMware vSphere guest.  The Linux guest OS hangs at “Starting udev”.

Fix:

1. Restart the Linux guest OS;
2. Press any key at the GRUB boot menu, press e to edit, and add the highlighted words at the “kernel” line; press enter, and then b to boot;
   kernel /vmlinuz-2.6.18-1.2257.fc5smp ro root=/dev/sdb1 clock=pmtmr divider=10 hgb quiet
3. Once it boots in the console, edit /boot/grub/grub.conf with the same setting.

Reference: http://itsecureadmin.com/2010/03/linux-guest-hangs-at-starting-udev-vmware-vsphere/
or http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006427

Error 2753 The file “???” is not marked for installation

Get this error when trying to remove an application managed by a group policy installer package.

Fix: Install Windows Installer CleanUp Utility (msicuu2) to remove the application.

Windows Server 2008 R2 Hyper-V Server License

Q. Which edition of Windows Server 2008 R2 should I buy for my Hyper-V server?
John Savill

A. The decision about whether to purchase the Standard, Enterprise, or Datacenter edition of Windows Server 2008 R2 should depend on two major factors: the number of virtual machines (VMs) you intend to run and your high availability requirements.

High availability is only available with the Enterprise and Datacenter SKUs, so if you want clusters and features like Live Migration, you have to use Enterprise or Datacenter edition.

The next factor is the number of VMs. Standard Edition supports one physical OS and one virtual OS (VM), Enterprise supports one physical OS and four virtual OSs, and Datacenter supports one physical OS and an unlimited number of virtual OSs. Note that Standard and Enterprise are purchased on a per-server basis while Datacenter is purchased on a per-processor basis, and at least two processors (sockets) must be licensed on each server with Datacenter.

You can assign multiple licenses to a single physical server. For example, I could purchase two copies of Enterprise Edition and assign them to a single physical server, which would allow me to run eight VMs. I could also buy eight copies of Standard Edition or just two of Datacenter (I need two because two is the minimum number purchasable with Datacenter—two sockets).

• Generally, the following is a good guideline for the most cost effective SKU to buy, but remember to consider future growth.
• Standard Edition is most cost efficient for one to three VMs per server. Note that if you run three VMs, you'll need to buy three copies of Standard Edition.
• Enterprise Edition is most cost efficient from four VMs on a server up to four VMs per processor. For example, if I have a dual processor box and want to run eight VMs, I could buy two copies of Enterprise edition.
• Datacenter Edition is most cost efficient for more than four VMs per processor, because you can run an unlimited number of VMs per processor and license each processor. While Datacenter is more expensive than Enterprise when running four VMs per processor, you have more scalability and support for future growth, so you could, potentially, adopt Datacenter over Enterprise when you consider future requirements. Remember that you have to license all processors in the server.

Microsoft offers an online calculator that can help you choose the right SKU to buy.

Remember that if you're using the maximum number of virtual instance rights, you can't run any workloads other than Hyper-V in the parent partition. If you run additional workloads in the parent partition (which isn't recommended), you lose one of your virtual instance rights. So if you're running Enterprise Edition and you're also running a file and print server on the Hyper-V host, you can only run three virtual OS instances.

When you purchase a SKU of Windows Server, you have the right to run that version and any lower version in your virtual environments. For example, if I buy Datacenter Edition, I can run Datacenter, Enterprise, or Standard in my VMs. If I buy Enterprise edition, I can run Enterprise or Standard in my VMs.

Finally, remember you can't move these virtual OS environment rights between servers. If you want to run four VMs on each server and have the ability to live migrate them to another server (which would mean it would run eight VMs), you need two licenses of Enterprise on the target server (or Datacenter). This is why when you're using Live Migration and clusters, it's normally advised to purchase Datacenter.

Q. If I'm performing a physical to virtual migration, can I move my physical Windows license to the virtual environment?

A. Assuming you're turning off the physical box and wiping the OS, you can move a Windows license from a physical to a virtual environment based on Microsoft's 90 day move rights. These rights allow licenses to be moved once every 90 days between servers, including moving to a virtualization host.

Symantec Extend WG Protocol Driver Error

Event ID: 7000, Source: Service Control Manager - “The Extend WG Protocol Driver service failed to start due to the following error: The system cannot find the file specified.”

The following steps fix the error message:
1. Open Device Manager
2. Click View > Show hidden devices
3. Expand Non-Plug and Play Drivers and uninstall the Extend WG Protocol Driver
4. Open regedit
5. Delete the key "WGX" in HKLM\SYSTEM\CurrentControlSet\Services
6. Reboot system

Access SkyDrive as a Map Drive

Requirement:

• Windows 7 (some says Windows XP would work, not test)
• Office 2010 (beta is fine; need to verify if this is optional)
• Windows Live account

Set up:

• Download SkyDrive Simple Viewer for WebDAV
• Run dumpurls.exe <Windows Live UserName> <Password> to get a list of addresses
• Map a network drive with one of the addresses
• Enter Windows Live ID and password

VMware vSphere 4 Notes

1. vSphere Editions for Small Businesses Comparison

Basic ESXi physical hardware limit: 2 physical processors, 6 cores per processors, 256GB memory.

 

2. VMware vCenter Server

VMware vCenter Server Installation

• Hardware requirements (for up to 50 ESX(i) hosts and 250 VMs):
• 2 CPUs
• 4 GB RAM
• 3 GB Disk
• Software requirements:
• Windows Server 2003 or 2008 x32 or x64
• SQL Server 2005 or 2008 or Express Edition
• Can be installed in a physical or virtual machine.
• Reference:
• What Is New in VMware vCenter Server 4
• Upgrading to ESX 4.0 and vCenter 4.0 best practices

VMware vCenter Server Administration

• After installing vCenter Server:
• Create a datacenter
• Join ESX(i) host to vCenter Server