Virtualization Adapted Adapting Business Processes for Virtual Infrastrcuture (and vice-versa)


TECHNOTE: VMware Converter Standalone v4

Filed under: virtualization — Tags: , , , , , — iben @ 07:55

VMware Converter Standalone

VMware converter is used for migrating Physical servers to Virtual Machines, Virtual Machines to Virtual Machines.

Directions for conducting a V2V or P2V for Windows Servers

1. Update or Open a tracking ticket to track progress
2. Ensure system is documented and monitored on portal
3. Notify stakeholders via DL – setup DL if needed
4. Login to the Machine to be converted
5. Run defrag and diskcheck if possible
6. Run Microsoft Update
7. Do a reboot test to ensure machine stability
8. Download VMware Converter Standalone version 4 – VMware-converter-4.0.0-146302.exe
9. Download Sysprep tools – unzip but do not run
10. Download NewSID – unzip but do not run
11. Download and run BGinfo – apply
12. Download and run treesize free and clean up unneeded files
13. Install VMware Converter
14. Copy Sysprep files to correct location – c:\documents and settings\all users
15. Launch VMware Converter
16. Import Machine
17. Select the device type; Physical Computer, Virtual Computer from ESX or VMware Workstation.
18. Enter in the remote IP address of the target:
19. Do not select Automatically uninstall the files when the import is successful
20. Select all the drives you wish to migrate to the new Virtual Machine
21. Select ESX or Virtual Center
22. Enter the Virtual Center and user credentials
23. Select the Virtual Machine name
24. Select the ESX host
25. Select the appropriate DataStore
26. Select the appropriate network
27. Check the box install vmware tools
28. If you desire to customize the settings, check the box.
29. Select Finish
30. When completed test new machine and configure.
31. Run newsid if new host names is needed… Keep in mind you cannot have two machines with same name or IP on same network.
32. Run BGinfo and apply again.
33. Verify reboot test and monitoring is functioning.
34. Verify system time.
35. Adjust services as needed.
36. Remove old hardware’s software.
37. Notify stakeholders when old machine is off and new machine is on.

See also:


TechNote: duplicate IP address after P2V of Windows Guest with VMware Convertor

Filed under: virtualization — Tags: , , , , , , , , , — iben @ 15:17

This issue is coming up more as we convert Physical machines to Virtual.  It can also happen when you want to change from the old “Flexible” to the newer “Enhanced vmxnet” network adapters.

Flexible shows up in Windows Device Manager as an “VMware Accelerated AMD PCNet Adapter” and Enhanced vmxnet show up as “VMware PCI Ethernet Adapter”.  You may also see “Broadcom NetXtreme 57xx Gigabit Controller” from a Dell or other desktop.

  • 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 which driver initializes it. VMware Tools versions recent enough to know about the Flexible network adapter include the vmxnet driver but identify it as an updated Vlance driver, so the guest operating system uses that driver. When using the Flexible network adapter, you can have vmxnet performance when sufficiently recent VMware tools are installed. When an older version of VMware Tools is installed, the Flexible adapter uses the Vlance adapter (with Vlance performance) rather than giving no network capability at all when it can’t find the vmxnet adapter.
  • Enhanced vmxnet — The enhanced vmxnet adapter is based on the vmxnet adapter but provides some high-performance features commonly used on modern networks, such as jumbo frames. This virtual network adapter is the current state-of-the-art device in virtual network adapter performance, but it is available only for some guest operating systems on ESX Server 3.5. This network adapter will become available for additional guest operating systems in the future.
  • Networking Error, IP Address Already Assigned to Another Adapter
    KB Article 1179
    Updated Jan. 07, 2009

    VMware Converter
    VMware ESX
    VMware GSX Server
    VMware P2V Assistant
    VMware Workstation

    Why do I see an error message that “The IP address XXX.XXX.XXX.XXX…” is already assigned to another adapter?

    Under certain conditions, you may see the following error message from a Windows guest operating system:

    The IP address XXX.XXX.XXX.XXX you have entered for this network adapter is already assigned to another adapter Name of adapter. Name of adapter is hidden from the network and Dial-up Connections folder because it is not physically in the computer or is a legacy adapter that is not working. If the same address is assigned to both adapters and they become active, only one of them will use this address. This may result in incorrect system configuration. Do you want to enter a different IP address for this adapter in the list of IP addresses in the advanced dialog box?

    In this message, XXX.XXX.XXX.XXX is an IP address that you are trying to set and Name of adapter is the name of a network adapter that is present in the registry but hidden in Device Manager.

    This can occur when you change a network connection’s TCP/IP configuration from DHCP to a static IP address if:

    * You have upgraded VMware virtual network adapters (for example when you migrate a virtual machine from an older to a new version of VMware software.)
    * You have added and removed network adapters multiple times.

    The cause of the error is that a network adapter with the same IP address is in the Windows registry but is hidden in the Device Manager (My Computer > Properties > Hardware > Device Manager). This hidden adapter is called a ghosted network adapter.

    Using the Show hidden devices option in the Device Manager (View > Show hidden devices) does not always show the old virtual NIC (ghosted adapter) to which that IP Address is assigned

    Microsoft addresses this issue in their Knowledge Base article 269155, which is available at the time of this writing at

    To resolve this problem, follow these steps to make the ghosted network adapter visible in the Device Manager and uninstall the ghosted network adapter from the registry:

    1. Select Start > Run.
    2. Enter cmd.exe and press Enter. This opens a command prompt. Do not close this command prompt window. In the steps below you will set an environment variable that will only exist in this command prompt window.
    3. At the command prompt, run this command:
      set devmgr_show_nonpresent_devices=1
    4. In the same command prompt run this command:
      Start DEVMGMT.MSC (press Enter to start Device Manager.)
    5. Select View > Show Hidden Devices.
    6. Expand the Network Adapters tree (select the plus sign next to the Network adapters entry).
    7. Right-click the dimmed network adapter, and then select Uninstall.
    8. Close Device Manager.
    9. Close the Command Prompt

    Another method of resolving this problem is to use the DevCon utility. This is a command-line utility that acts as an alternative to Device Manager. When you use DevCon, you can enable, utility disable, restart, update, remove, and query individual devices or groups of devices.

    To use DevCon:

    1. Download the DevCon tool from Microsoft Knowledge Base: 311272 (
    2. Unpack the 32bit or 64bit DevCon tool binary to a local folder.
    Click Start > Run.
    Type cmd and press Enter.
    5. Type CD:\path_to_binaries to navigate to the devcon.exe is located.
    6. Use the following syntax to find installed network adapters:

    devcon findall *net* or
    devcon listclass net

    Note: In the output of the previous commands, there is a line for the ghosted network adapter that is similar to, PCI\.
    Run the following command to remove the adapter:

    devcon remove @device\name

    For example, devcon remove “@PCI\VEN_14E4&DEV_1600&SUBSYS_01C21028&REV_02\4&378EDFA4&0&00E2” .

    Note: IDs that include an ampersand character (&) must be enclosed in quotation marks as seen in the example.

    Reboot the system and you no longer see the ghost network adapters.

    Product Versions

    VMware Converter 3.0.x
    VMware ESX 1.5.x
    VMware ESX 1.x
    VMware ESX 2.0.x
    VMware ESX 2.1.x
    VMware ESX 3.0.x
    VMware GSX Server 2.0.x (Linux hosts)
    VMware GSX Server 2.0.x (Windows hosts)
    VMware GSX Server 2.5.x (Linux hosts)
    VMware GSX Server 2.5.x (Windows hosts)
    VMware GSX Server 3.x (Linux hosts)
    VMware GSX Server 3.x (Windows hosts)
    VMware P2V Assistant 1.x
    VMware P2V Assistant 2.0.x
    VMware P2V Assistant 2.1.x
    VMware Workstation 3.x (Linux Hosts)
    VMware Workstation 3.x (Windows Hosts)
    VMware Workstation 4.x (Linux hosts)
    VMware Workstation 4.x (Windows hosts)

    urlz; migration; upgrade; 1179; ghost; hidden; NIC
    This Article Replaces

    converter NIC issue (1000212)
    Not able to remove ghost network adapter per the instructions in KB Article: 1179 (1003003)

    Subject: VMware: Solution for “The IP address XXX.XXX.XXX.XXX…” is already assigned to another adapter” error

    Go here:


    VMware Security Compliance Tools

    Filed under: virtualization — Tags: , , , , , , , , , — iben @ 10:37
    This is a short list of Tools and Documents concerning security in a Virtual Infrastructure.
    Tools – page 1
    Documents – page 2



    • Configuresoft’s Center for Policy and Compliance (CP&C) has led the industry in forming opinion and bringing together published security and compliance information to build a rich library of compliance toolkits that are available for download by Configuresoft customers from These CP&C Compliance Toolkits include:
    • VMware Infrastructure 3 Security Hardening Guidelines and VMware Virtual Center Best Practices
    • FISMA Compliance Toolkit for Virtual Computing
    • GLBA Compliance Toolkit for Virtual Computing
    • HIPAA Compliance Toolkit for Virtual Computing
    • Sarbanes-Oxley (404) Compliance Toolkit for Virtual Computing
    • DISA STIG Compliance Toolkit for Virtual Computing


    HyTrust Appliance –

    • The HyTrust™ Appliance offers IT managers and administrators of virtual
      infrastructure a centralized, single point of control and visibility for:
    • configuration management
    • compliance auditing
    • access management
    • best practices
    • process workflow
    • security controls



    • ConfigCheck rapidly assesses the security of ESX 3.0 and 3.5 hypervisors compared to the Virtual Infrastructure 3 Security Hardening Guidelines.
    • ConfigCheck assesses nearly 100 configurations of the ESX server, and most VI professionals who run the test find significant vulnerabilities. ConfigCheck’s remediation report provides detailed, step-by-step guidance to bring your virtual environment into a state that is secure. ConfigCheck helps you:
      • Ensure recommended ESX configurations
      • Discover possible vulnerabilities
      • Deploy virtualization safely and securely
      • Increase security posture of the entire enterprise
      • Reduce configuration drift


    • VMinformer is a security tool designed to check the security posture of your VMware environment. The tool comes with pre-defined policies that can be customized to suit your specific requirements and are based on industry best practices such as ‘VMware’s Security best practice hardening guide’ and the ‘DISA ESX STIG’ hardening guide. The policies also contain rules that have been based on extensive research and industry experience.
    • Features:
    • Connects to your ESX hosts or Virtual Center (v3.0, 3.5 and VC 2.5)
    • Pre-defined policies based on industry best practices (VMware security hardening guide)
    • Policies can be customized for your environment
    • Provides full visibility and monitoring of your ESX hosts and Virtual machines
    • Dashboard – Provides a graphical overview of VM’s and Security Posture
    • Reporting
    • Remediation guidance



    VMware ESX host command line configuration script

    Filed under: Uncategorized — Tags: , , , , — iben @ 14:46

    #customize esxXX by IR Date YYYYMMDD
    # ESX host configuration script for
    # configure as needed for esxXX by changing IP addresses below…
    # configure 4 nics for nfs storage
    # nic 1 and 3 – cos1, vms, vmotion
    # nic 2 and 4 – vmkernel for nfs storage

    #configure SYSLOG
    echo “*.*” >> /etc/syslog.conf
    service syslog restart

    # List current config
    /usr/sbin/esxcfg-nics -l
    /usr/sbin/esxcfg-vswitch -l

    #creating virtual switches
    /usr/sbin/esxcfg-vswitch -a vSwitch1
    /usr/sbin/esxcfg-vswitch -L vmnic1 vSwitch1
    /usr/sbin/esxcfg-vswitch -L vmnic3 vSwitch1
    /usr/sbin/esxcfg-vswitch -L vmnic2 vSwitch0
    #enable CDP advertise and listen mode
    /usr/sbin/esxcfg-vswitch -b vSwitch0
    /usr/sbin/esxcfg-vswitch -b vSwitch1
    /usr/sbin/esxcfg-vswitch -B both vSwitch0
    /usr/sbin/esxcfg-vswitch -B both vSwitch1
    /usr/sbin/esxcfg-vswitch -b vSwitch0
    /usr/sbin/esxcfg-vswitch -b vSwitch1

    #creating portgroups
    /usr/sbin/esxcfg-vswitch -A “ITG-VLAN2” vSwitch0
    /usr/sbin/esxcfg-vswitch -A “PUBLIC-VLAN4” vSwitch0
    /usr/sbin/esxcfg-vswitch -A “VMkVMotion-VLAN209” vSwitch0
    /usr/sbin/esxcfg-vswitch -A “VMkStorage-VLAN207” vSwitch1
    #/usr/sbin/esxcfg-vswitch -A “Service Console” vSwitch0
    /usr/sbin/esxcfg-vswitch -A “Service Console 2” vSwitch0
    /usr/sbin/esxcfg-vswif -a -i -n -p “Service Console 2” vswif1
    /usr/sbin/esxcfg-vswitch -A “ESX-VLAN208” vSwitch0
    /usr/sbin/esxcfg-vmknic -a -i -n VMkStorage-VLAN207
    /usr/sbin/esxcfg-vmknic -a -i -n VMkVMotion-VLAN209
    /usr/sbin/esxcfg-route -a
    /usr/sbin/esxcfg-vswif -l
    /usr/sbin/esxcfg-vmknic -l

    vmware-vim-cmd hostsvc/net/vswitch_setpolicy –nicteaming-policy=loadbalance_ip vSwitch0
    vmware-vim-cmd hostsvc/net/vswitch_setpolicy –nicteaming-policy=loadbalance_ip vSwitch1
    vmware-vim-cmd /hostsvc/net/vswitch_setpolicy –failurecriteria-check-beacon 0 vSwitch0
    vmware-vim-cmd /hostsvc/net/vswitch_setpolicy –failurecriteria-check-beacon 0 vSwitch1
    vmware-vim-cmd hostsvc/net/vswitch_setpolicy –securepolicy-promisc=false vSwitch0
    vmware-vim-cmd hostsvc/net/vswitch_setpolicy –securepolicy-macchange=false vSwitch0
    vmware-vim-cmd hostsvc/net/vswitch_setpolicy –securepolicy-forgedxmit=false vSwitch0
    vmware-vim-cmd hostsvc/net/vswitch_setpolicy –securepolicy-promisc=false vSwitch1
    vmware-vim-cmd hostsvc/net/vswitch_setpolicy –securepolicy-macchange=false vSwitch1
    vmware-vim-cmd hostsvc/net/vswitch_setpolicy –securepolicy-forgedxmit=false vSwitch1

    #configuring vlans
    /usr/sbin/esxcfg-vswitch -l
    /usr/sbin/esxcfg-vswitch -v 2 -p “ITG-VLAN2” vSwitch0
    /usr/sbin/esxcfg-vswitch -v 4 -p “PUBLIC-VLAN4” vSwitch0
    /usr/sbin/esxcfg-vswitch -v 207 -p “VMkStorage-VLAN207” vSwitch1
    /usr/sbin/esxcfg-vswitch -v 209 -p “VMkVMotion-VLAN209” vSwitch0
    /usr/sbin/esxcfg-vswitch -v 208 -p “Service Console” vSwitch0
    /usr/sbin/esxcfg-vswitch -v 208 -p “Service Console 2” vSwitch0
    /usr/sbin/esxcfg-vswitch -v 208 -p “ESX-VLAN208” vSwitch0
    /usr/sbin/esxcfg-vswitch -l

    #delete vmnic1 from vSwitch0 (run these if necessary)
    #/usr/sbin/esxcfg-vswitch -N vmnic1 -p “ITG-VLAN2” vSwitch0
    #/usr/sbin/esxcfg-vswitch -N vmnic1 -p “PUBLIC-VLAN4” vSwitch0
    #/usr/sbin/esxcfg-vswitch -N vmnic1 -p “VMkStorage-VLAN207” vSwitch0
    #/usr/sbin/esxcfg-vswitch -N vmnic1 -p “VMkVMotion-VLAN209” vSwitch0
    #/usr/sbin/esxcfg-vswitch -N vmnic1 -p “Service Console” vSwitch0
    #/usr/sbin/esxcfg-vswitch -N vmnic1 -p “Service Console 2” vSwitch0
    #/usr/sbin/esxcfg-vswitch -N vmnic1 -p “ESX-VLAN208” vSwitch0

    #add vmnics to each port group
    /usr/sbin/esxcfg-vswitch -M vmnic2 -p “ITG-VLAN2” vSwitch0
    /usr/sbin/esxcfg-vswitch -M vmnic2 -p “PUBLIC-VLAN4” vSwitch0
    /usr/sbin/esxcfg-vswitch -M vmnic1 -p “VMkStorage-VLAN207” vSwitch1
    /usr/sbin/esxcfg-vswitch -M vmnic3 -p “VMkStorage-VLAN207” vSwitch1
    /usr/sbin/esxcfg-vswitch -M vmnic2 -p “VMkVMotion-VLAN209” vSwitch0
    /usr/sbin/esxcfg-vswitch -M vmnic2 -p “Service Console” vSwitch0
    /usr/sbin/esxcfg-vswitch -M vmnic2 -p “Service Console 2” vSwitch0
    /usr/sbin/esxcfg-vswitch -M vmnic2 -p “ESX-VLAN208” vSwitch0
    /usr/sbin/esxcfg-vswitch -l

    sleep 10

    #setup vmotion on the first vmk network
    #vmware-vim-cmd “hostsvc/vmotion/netconfig_get” (check config)
    vmware-vim-cmd hostsvc/vmotion/vnic_set vmk1

    #/usr/sbin/esxcfg-vswitch -l

    vmware-vim-cmd /hostsvc/net/portgroup_set –nicorderpolicy-active=vmnic0 vSwitch0 “Service Console”
    vmware-vim-cmd /hostsvc/net/portgroup_set –nicorderpolicy-standby=vmnic2 vSwitch0 “Service Console”
    vmware-vim-cmd /hostsvc/net/portgroup_set –nicorderpolicy-active=vmnic0 vSwitch0 “Service Console 2”
    vmware-vim-cmd /hostsvc/net/portgroup_set –nicorderpolicy-standby=vmnic2 vSwitch0 “Service Console 2”
    vmware-vim-cmd /hostsvc/net/portgroup_set –nicorderpolicy-active=vmnic0 vSwitch0 “VMkVMotion-VLAN209”
    vmware-vim-cmd /hostsvc/net/portgroup_set –nicorderpolicy-standby=vmnic2 vSwitch0 “VMkVMotion-VLAN209”

    #adding Network Attached data store
    /usr/sbin/esxcfg-nas -l
    /usr/sbin/esxcfg-nas -a -o NAS1-ip -s /vol/vmw_datastore1 vmw_datastore1
    /usr/sbin/esxcfg-nas -a -o NAS2-ip -s /vol/vmw_datastore2 vmw_datastore2
    #/usr/sbin/esxcfg-nas -a -o NAS3-ip -s /vol/vol3_vmware_test nfs_vol_netapp
    /usr/sbin/esxcfg-nas -l

    #configure resolv.conf
    /bin/cat /dev/null > /etc/resolv.conf
    echo “nameserver ns1-ip” >> /etc/resolv.conf
    echo “nameserver ns2.ip” >> /etc/resolv.conf
    echo “search” >> /etc/resolv.conf
    cat /etc/resolv.conf

    #configure hostname
    vmware-vim-cmd hostsvc/net/dns_set –dns-hostname=esxXX
    vmware-vim-cmd hostsvc/net/dns_set –

    #configure NTP
    /usr/sbin/esxcfg-firewall -e ntpClient
    /usr/sbin/ntpdate -u
    chkconfig –list ntpd
    chkconfig –level 35 ntpd on
    chkconfig –list ntpd
    echo “restrict ntp1-ip mask nomodify notrap noquery” >> /etc/ntp.conf
    echo “server” >> /etc/ntp.conf
    echo “restrict ntp2-ip mask nomodify notrap noquery” >> /etc/ntp.conf
    echo “server” >> /etc/ntp.conf
    echo “restrict ntp3-ip mask nomodify notrap noquery” >> /etc/ntp.conf
    echo “server” >> /etc/ntp.conf
    echo “driftfile /var/lib/ntp/drift” >> /etc/ntp.conf
    echo “ntp1-ip” > /etc/ntp/step-tickers
    echo “ntp2-ip” >> /etc/ntp/step-tickers
    echo “ntp3-ip” >> /etc/ntp/step-tickers
    service ntpd restart
    hwclock –systohc

    #configure SUDO

    esxcfg-boot -g
    esxcfg-boot -b

    esxcfg-advcfg -s 32 /NFS/MaxVolumes

    # make sure that NFS locks are not disabled
    esxcfg-advcfg -s 0 /NFS/LockDisable

    # this should already be set correctly, but just to make sure
    esxcfg-advcfg -s 12 /NFS/HeartbeatFrequency

    # this should also be set correctly already
    esxcfg-advcfg -s 10 /NFS/HeartbeatMaxFailures

    # increase the heap size. Default is 9.
    esxcfg-advcfg -s 30 /Net/TcpIpHeapSize

    # increase heap max. Default is 30.
    esxcfg-advcfg -s 120 /Net/TcpIpHeapMax

    #configure AD
    /usr/sbin/esxcfg-auth –enablead – –
    useradd IT1
    useradd IT2
    #useradd Administrator

    #configure SNMP
    /bin/cat /dev/null > /etc/snmp/snmpd.conf
    echo “syscontact” >> /etc/snmp/snmpd.conf
    echo “syslocation Company-Location” >> /etc/snmp/snmpd.conf
    echo “rocommunity RO-String” >> /etc/snmp/snmpd.conf
    echo “trapcommunity RO-String” >> /etc/snmp/snmpd.conf
    echo “trapsink RO-String” >> /etc/snmp/snmpd.conf
    echo “dlmod SNMPESX /usr/lib/vmware/snmp/” >> /etc/snmp/snmpd.conf
    echo “smuxpeer .” >> /etc/snmp/snmpd.conf

    #install Dell OpenManage Agent
    esxcfg-firewall -o 80,tcp,out,http
    tar -xvf OM_5.5.0_ManNode_A00.tar.gz
    cd linux/supportscripts/
    ./ -b -w -r -s start
    esxcfg-firewall -o 1311,tcp,in,OpenManageRequest

    #test by going to

    # service mgmt-vmware restart # if needed

    #end of script


    VMware ESX setting static mac addresses

    Filed under: Uncategorized — Tags: , , , , — iben @ 15:22

    1. Select a static MAC. NOTE: Static MAC addresses must be in the range of 00:50:56:00:00:00-00:50:56:3F:FF:FF to work with this procedure.
    2. Remember to record the Static MAC addresses registered for future reference.
    3. Unregister vm:
    4. Note the datastore, vm inventory folder, and name for the vm in the summary tab
    5. Power down the virtual machine
    6. Right click the vm and select remove from inventory
    7. Edit vmx:
    8. Ssh to the esx host system (use putty)
    9. cd /vmfs/volumes/
    10. cd to the system’s folder
    11. cp .vmx to .vmx.bak
    12. vi .vmx
    13. find the ethernet0 section
    14. make the following changes:
    15. change ethernet0.addressType = “vpx” to ethernet0.addressType = “static”
    16. ethernet0.generatedAddress = “00:50:56:01.01.00” to ethernet0.address = “00:50:56:01.01.00”
    17. rearrange so the following items are in this order and grouped together: ethernet0.address, ethernet0.addresstype, uuid.location, uuid.bios
    18. Write the changes to the disk and exit
    19. Reregister the vm:
    20. In virtual center, browse to the host datastore (configuration, storage, double click on the vm’s datastore)
    21. Browse to the edited .vmx file
    22. Right click the .vmx file and select Add to Inventory
    23. Enter the system name
    24. Select the host
    25. Select the resource pool
    26. Click Finish
    27. Power on the vm and verify the mac address
    28. Windows: ipconfig /all find “Physical Address”
    29. Linux: ifconfig /a grep Hwaddr


    ethernet0.address = “00:50:56:88:6f:98”

    ethernet0.addressType = “static”

    uuid.location = “56 4d 6b b4 70 cc 85 24-59 1b 2d 24 0a 2b d7 7a”

    uuid.bios = “50 08 5b 0d e1 f7 fb 8b-ba 39 74 1b 30 fc 0c 40”

    Posted by Jae Ellers at Monday, January 28, 2008.

    This post rocks! Helped me out of a tight bind today.

    ESX versus ESXi – feature comparison – Dell Open Manage

    Filed under: virtualization — Tags: , , , , , , — iben @ 11:55

    The following information was obtained from Dell’s web site:

    Monitoring Comparison between ESX and ESXi

    Systems Management
    Feature Description: Inventory
    Processor Information including brand, processor version, current speed, core count, model, stepping information, 64-bit support, HyperThreading (HT), Virtualization Technology (VT), Demand Based Switching (DBS), and Execute Disable (XD).
    Cache information including status, level, max size, installed size, type, location, write policy, set associativity, and error correction.

    ESX Classic
    All of the above Inventory information is available through OpenManage Server Administrator.

    Processor brand, processor version, current speed, core count, model, and stepping information is also available in IT Assistant

    Only Processor brand, processor version, current speed, core count, and model available using the VI Client.


    VMware ESX Cost Per GB Calculator

    Filed under: virtualization — Tags: , , , , , , , — iben @ 09:51

    I ran some numbers for a customer recently and discovered the single processor high-RAM hardware configurations can be more cost effective for most corporate windows applications hosted on VMware ESX. Keep in mind that the number of processors a server has doesn’t always need to equal the number of sockets.

    This includes the cost of hardware, ESX Enterprise, and Microsoft Windows Data Center Edition.

    What did I miss in these calculations. There are also per port costs to include for Network, Storage, backup agents, etc.

    NOTE: Recently updated to show HP blades with 16 GB DIMMS

    VMware’s Multi-Core Pricing & Licensing Policy

    VMware’s End User License Agreement
    1.6 "Processor" means a single, physical chip that houses no more than six (6) processor cores.


    Pano Logic Cube Video Resolution Settings

    Filed under: virtualization — Tags: , , , , , , , , , — iben @ 10:50

    When logging into a PanoLogic virtual desktop console for the first time…

    The default display resolution was 1024×768 standard 4:3 XGA

    The HP w1707 LCD monitor has a native resolution of 1680×1050@60Hz 16:10 WSXGA+

    Using the pano logic control panel I was only able to set the max resolution to 1440×900@69Hz 16:10 WSXGA

    List of Supported Reslutions:


    New vSphere product names from VMware

    Filed under: virtualization — Tags: , , , , — iben @ 14:22

    Old Name –> New Name

    VMware VirtualCenter –> VMware vCenter Server

    VMware Lifecycle Manager –> VMware vCenter Lifecycle Manager

    VMware Converter –> VMware vCenter Converter
    (for the version integrated into vCenter)

    –> VMware vCenter Converter Standalone
    (for the separately downloadable version)

    VMware Lab Manager –> VMware vCenter Lab Manager

    VMware Stage Manager –> VMware vCenter Stage Manager

    VMware Update Manager –> VMware vCenter Update Manager

    VMware Site Recovery Manager –> VMware vCenter Site Recovery Manager

    VirtualCenter Foundation –> vCenter Server Foundation

    VMFS –> VMware vStorage VMFS

    VMware Virtual Desktop Infrastructure –> VMware View

    Virtual Desktop Manager (VDM) –> VMware View Manager

    VMware Administrator Interface –> VMware View Administrator

    VDM Agent –> VMware View Manager Agent

    VDM Web Access –> VMware View Portal

    VDM Client for Windows –> VMware View Client for Windows

    VDM Client for Linux –> VMware View Client for Linux


    Is Cisco California right for your data center?

    Filed under: virtualization — Tags: , , , , , , — iben @ 23:12

    The Cisco Unified Fabric – California – is getting a lot of buzz lately.

    This video gives some idea of the implications…

    “All your base are belong to us”

    Let the debates begin…

    Will IBM buy SUN as part of this?

    Juniper lowers CAPEX and OPEX and ensures flexibility and choice, and customer feedback verifies that we deliver a high-performance network.

    « Newer PostsOlder Posts »

    Powered by WordPress