VMware ESX and GSX Server.

VMWARE GSX doesn exist anymore. It is replaced by VMWARE Server which is free.

VMWARE server is a free virtualization software that run on a Windows Server platform. Good for testing and smaller environments

VMWARE ESX Is the Hypervisor from VMWARE.

VMWARE ESX server can run up to 128 VM’s at the same time. Your main limits are determined by how much RAM and CPU Power you have.

It has its own OS, so can not be installed upon Windows. But must be installed on the server itself. It uses it own file system: VMFS.
Has really nice features like Vmotion, HA and resource groups.

ESX is a server version and GSX is a client version, ESX is a linux kernal based os, GSX is a program which runs on windows, or even ESX

Compare VMware ESX Server and ESXi Server.

VMware ESX Server and ESXi Server.

1. VMware ESXi Server has no service console.
The traditional (full) ESX Server has a special built-in virtual machine called the “service console”.

2. VMware ESXi Server uses RCLI instead of service console utilities.
As ESXi doesn’t have any CLI with VMware-related or Linux utilities, VMware needed to provide a CLI interface to ESXi. What VMware came up with is the Remote Command line Interface (RCLI).

3. VMware ESXi Server is extremely thin = fast installation + faster boot.
The service console has been removed from ESXi, the footprint in memory has been reduced to just 32MB. You can run a hypervisor, allowing you to run virtual machines on your server, with just 32MB of RAM overhead. In comparison, the full ESX Server on disk footprint is about 2GB.

4. VMware ESXi Server can be purchased as an embedded hypervisor on hardware.
While ESXi is so small that it can be easily installed and can even be booted from a USB Flash disk, what is truly unique about ESXi is that it is being sold by hardware vendors as a built-in hypervisor.

5. VMware ESXi Server has a “yellow firmware console”.
Instead of the full ESX Server “service console” boot (which looks like a Linux server booting), ESXi has a tiny “Direct Console User Interface (DCUI)”.

6. VMware ESXi Server has server health status built in.
With ESXi some hardware monitoring features are built into the hypervisor. With ESX Server, this is not yet built in. Instead, you must install hardware monitoring software in the service console.

7. VMware ESXi Server requires fewer patches and less rebooting.
The full ESX server essentially has a modified Linux system as the service console, there are many patches that have to be deployed to keep it secure. With ESXi, on the contrary, the server has very few patches that need to be applied. Because ESXi has no service console and it is considered more secure and more reliable. Security, Reliability, and Maintainability, are all major factor when considering a hypervisor.

HP RAID Configuration

HP RAID Configuration

Steps involved in HP Array configuration.










Performance Tab in Windows Task Manager

Understanding the Performance Tab in Windows Task Manager.

The performance tab is always a good thing to keep your eye on. It a valuable tool to monitor performance and troubleshoot performance problems. I will try to explain the confusing data that is presented in the Performance tab of Task Manager.

Note: I know all of us have 2gigs or more of memory, and memory performance is not really an issue but this is just some knowledge you can use. You can tell your parents that you learned something interesting today.

Typical Performance Tab
Windows Monitoring

Numbers look daunting and confusing

Keep in mind that the values expressed in the Physical Memory, Commit Charge, and Kernel Memory panels are in kilobytes. As such, dividing by 1024 reveals the megabyte value.


CPU Usage – This is pretty obvious, it indicates the percentage of processor cycles that are not idle at the moment.

PF Usage – Indicates the percentage of the paging file that is currently being used. This value is sort of misleading, it actually shows the amount of physical memory/page file space being used by your system. Synchronous to Total under Commit Charge (K).

CPU Usage History – Just a graph which indicates how busy the process has been recently, the number of graphs correspond to the number of cores your processor has.

Page File Usage History – Same as CPU Usage History just for your page file usage since Task Manager has been opened.

Now for the data that is confusing but valuable.

Totals Section
Windows Monitoring

Handles – represents the number of specific input/output (I/O) instances running. Displays the total number of resources the OS is working with at one time. Resources can be anything, files, directories, events, processes and registry keys.

Threads – represents the number of objects that are currently executing program instructions

Process – is a single executable program, a process may have multiple threads each of which in turn have multiple handles. If you’re running 3 word documents, there will be three processes running. This corresponds with the number of processes running under the Process Tab.

Physical Memory (K) Section
Windows Monitoring

Total – the amount of physical memory that your system has installed and that the OS has detected. According to the graph my system is 2GB.

Available – The amount of physical memory you have available for the system to use. If you find very low ram available continuously, you are going to bottleneck your system, because if you have none available, the OS will resort to using virtual memory and accessing your harddrive.. Time to add some more memory. According to the graph my system has 1.2GB available

System Cache – Not important for system bottlenecks. If you must know, it is an area of memory used by system processes.

Commit Charge (K) Section
Windows Monitoring

Total – How much memory (physical and virtual) is actually in use by program and processes. In the above table i am using 702MB of 4GB of memory (physical and virutal combined)

Limit – this is the maximum possible value for Total. This is the sum of the current pagefile size plus your total physical memory. 4GB is available, 2GB physical + 2GB virtual

Peak – represents the highest combined total of physical memory and virtual memory that has been used since boot up. As you can see I only used a little under 1GB of memory in my highest peak.

Kernal Memory (K) Section
Windows Monitoring

In the Kernel Memory panel, you will find statistics on the memory that is being used by the operating system and device drivers.

Total – value represents the amount of physical memory that the OS uses for core operations and for managing device drivers. In the above example, it comes out to be 83 megabytes

Paged – value represents the amount of memory used by core operations and device drivers that can be moved from physical memory to the page file if necessary. In the above example, it comes out to be 55 megabytes

Nonpaged – value represents the amount of core components and device drivers that can never be moved from physical memory to the page file. In the above example, it comes out to be 28 megabytes

Okay so what does all this tie into, here are some several points which relate to memory and are good to remember. Starting from the top.

* If the Commit Charge Total value regularly exceeds the Physical Memory Total value, your system has to rely more frequently on the much slower page file (virtual memory). Its time to add more physical memory.

* If the Commit Charge Total value is near the value of Commit Charge Limit value then WTF are you doing, not only did you use up all your physical memory but also you used up all your virtual memory. Your computer is at its knees begging for mercy.

* If your Commit Charge Peak value is near the Commit Charge Limit value then you are completely maxing out at one point or another during your computer being turned on. Your computer is at its knees begging for mercy once in a while for a few seconds.

* If your Commit Charge Peak value comes close to or exceeds the Physical Meory Total value, your computer had to access virtual memory once or twice. Performance might not be affected, but you are at the upper limit of using all your memory.

* More than 50% of the core operating system components and drivers can be swapped out from physical memory to the page file, moving such portions of the OS can significantly yield a performance hit. This again indicates the advantage of using more physical memory.

HP ILO Configuration

HP ILO Pre-Deployment Configuration:

1. Boot the server and verify local console access.

2. During boot, press the F8 key at the ILO prompt.

HP ilo

3. Navigate to the Network “DNS/DHCP” selection:

HP ilo

4. Change the DHCP Enable field to OFF by pressing the space bar.

HP ilo

5. Modify the DNS Name using the format -ilo.

HP ilo

6. Press F10 to save after DHCP is set to OFF and the DNS Name is configured.
7. Navigate to the Network “NIC and TCP/IP” selection.

HP ilo

8. Change the network settings as shown below. Use the IP address configured in DNS. Click F10 to save and exit.

HP ilo

HP Servers BurnIn Process.

HP SmartStart is a single-server deployment tool that simplifies HP ProLiant server setup, providing a repeatable way to deploy consistent configurations.

1. Boot the required HP Server using SmartStart CD or ISO. This may take several minutes.

Note: Booting an ISO over VPN or WAN may not work properly.

SMARTCD Initialization

HP SmartCD

HP SmartCD

HP SmartCD

HP SmartCD

HP SmartCD

HP SmartCD

HP SmartCD

HP SmartCD

HP SmartCD

HP SmartCD

HP SmartCD

HP SmartCD

HP SmartCD

HP SmartCD

HP SmartCD

HP SmartCD

HP SmartCD

Troubleshoot startup problems in Windows Server 2003.

A successful Windows startup includes of the following four phases:

1. Initial phase
2. Boot loader phase
3. Kernel phase
4. Logon phase

If a problem occurs during one of these phases, Windows may not start correctly and you may experience one of the following problems:

The computer stops responding (hangs).
You receive an error message.

If a startup problem occurs after you click Microsoft Windows Server 2003 from boot loader menu, files that the operating system needs may be missing or damaged.

Windows provides a variety of options that you can use to troubleshoot this issue, including Safe mode, the Recovery Console, and an Automated System Recovery. You may opt for the below listed options to recover your windows:

• The Last Known Good Configuration.

• Start the Computer in Safe Mode.

• Use Event Viewer to Identify the Cause of the Startup Problem.

• Use System Information to Identify the Cause of the Startup Problem.

• View the Safe Mode Boot Log File.

• Use Device Manager to Identify the Cause of the Startup Problem.

• Use System Configuration Utility (msconfig.exe).

• Isolate Problems by Using System Startup Options.

• Troubleshoot the System.ini File.

• Use the Microsoft Windows Recovery Console.

• Confirm That Your Hard Disk or File System Is Not Damaged.

• Use Automated System Recovery.

• Create an ASR Disk Set by Using Backup.

• Repair Your Installation of Windows.

• Use the Microsoft Product Support Services Web Site to Find a Solution.