الجمعة، 20 فبراير 2009

Enable .shtml on IIS 6

If you found page cannot be found error after redirect to .shtml with IIS 6
 
you should enable :
* Server Side Includes
* WebDAV
on Web Service Extensions on IIS6
 
Then .shtml files'll work with IIS6
 




What can you do with the new Windows Live? Find out

الخميس، 19 فبراير 2009

How to reset TCP/IP in Windows XP using netsh

When viewing the list of components for a network interface in Windows XP, you may notice that the Uninstall button is grayed out when Internet Protocol (TCP/IP) is selected. You can't uninstall TCP/IP on Windows XP because the TCP/IP stack is considered a core component of the operating system.  In a case, if you have a problem with TCP/IP settings, you can use netsh utility to reset the TCP/IP stack.   This article describes how to use the NetSh utility to reset TCP/IP.

 

To reset TCP/IP, follow these steps:

  1. Click Start>Run
  2. In the Run box, type "cmd" and click OK.
  3. At the DOS prompt, type netsh int ip reset [log_file_name], for example, netsh int ip reset c:\resetlog.txt and press Enter.
  4. Close all open programs and restart the computer.


Connect to the next generation of MSN Messenger  Get it now!

الأحد، 15 فبراير 2009

How To Install VMware ESX Server 3.5 From a Local CD

To Install VMware ESX Server 3.5 From a Local CD :

To perform this procedure you must have the Sun Blade X6240 server module multi-port dongle cable.

1. Connect the multi-port dongle cable to the front of the Sun Blade X6240 server module.

2. Connect the following to the USB ports on the dongle:

    • A CD/DVD drive
    • A USB Keyboard and Mouse

Note - You can also configure keyboard, video and mouse (KVM) access through a JavaRConsole.

3. Connect a monitor connected to the server module (this is not required if you are using Java KVM).

4. Power on the server module.

5. Insert the CD-ROM media into CD/DVD drive. The server will boot from the CD-ROM and display a boot prompt.

boot:

6. To access graphical mode, press Enter.

7. To work in text mode, enter the following:

esx text

8. Refer to the Installation and Upgrade Guide for VMware Infrastructure to guide you through the installation process.

From your network-connected system, go to http://www.vmware.com/support/pubs/vi_pubs.html.

9. Identify the specific network interface for the Sun Blade X6240 server module.

In the service console window on the Sun Blade X6240 server module, identify the available network configuration alternatives (see FIGURE 5-1 for ESX Server 3.5 Update 1).

10. Complete the VMware installation.

This is detailed in the Installation and Upgrade Guide for VMware Infrastructure at http://www.vmware.com/support/pubs/vi_pubs.html.

11. Update the VMware ESX Server 3.5 software with the latest updates and patches, if necessary.

See Updating the VMware Server 3.5 Software With Updates and Patches.

Note - We strongly recommend installing all critical and security patches.



Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! Try it!

How To Install VMware ESX Server 3.5 From a Remote CD or Remote ISO Image


To Install VMware ESX Server 3.5 From a Remote CD or Remote ISO Image:

1. Locate your VMware ESX Server installation CD/DVD or the equivalent ISO image.

2. Connect to the ILOM service processor web interface.

3. Select the Remote Control tab, then the Mouse Mode Settings tab.

4. Select the Redirection tab.

5. Click the Launch Redirection button to start the JavaRConsole application.

6. Log in to the JavaRConsole.

7. Start keyboard and mouse redirection.

Select Keyboard and Mouse in the Devices menu.

8. Start CD/DVD redirection.

From the JavaRConsole Devices menu, you can redirect the CD in two ways:

    • If you are installing a physical CD-ROM into the remote console CD drive, insert the CD-ROM into the drive and select CD-ROM.
    • If you are using an ISO image installed on the remote console, select CD-ROM Image and provide the location.

 

Note - Depending on the number of USB devices in use, you may be prompted for the install location or device. This deviates from the normal installation. To continue installation under these circumstances, select CD-ROM Image. Then, when prompted to select a device driver, select Linux USB Driver.

 

9. Refer to the Installation and Upgrade Guide for VMware Infrastructure to guide you through the installation process.

From your network-connected system go to http://www.vmware.com/support/pubs/vi_pubs.html.

10. Identify the specific network interface for the Sun Blade X6240 server module.

In the service console window on the Sun Blade X6240 server module, identify the available network configuration alternatives.

11. Update the ESX Server 3.5 software with the latest updates and patches, if necessary.

See Updating the VMware Server 3.5 Software With Updates and Patches

 

Note - Installing all critical and security patches is recommended for best performance.



See all the ways you can stay connected to friends and family

السبت، 14 فبراير 2009

VMware ESX Server


VMware ESX Server

VMware ESX Server is an enterprise-level virtualization product offered by VMware, Inc., a division of EMC Corporation. ESX Server is a component of VMware's larger offering, VMware Infrastructure, which adds management and reliability services to the core server product. The basic server requires some form of persistent storage - typically an array of hard disk drives - for storing the virtualization kernel and support files. A variant of this design, called ESX Server ESXi Embedded, does away with the first requirement by moving the server kernels into a dedicated hardware device. Both variants support the services offered by Virtual Infrastructure.

Technical description

VMware, Inc. refers to the hypervisor used by VMware ESX Server as "vmkernel".

Architecture


VMware states that the ESX Server product runs on "bare metal". In contrast to other VMware products, it does not run atop a third-party operating system, but instead includes its own kernel. Up through the current ESX version 3.5, a Linux kernel is started first and is used to load a variety of specialized virtualization components, including VMware's 'vmkernel' component. This previously-booted Linux kernel then becomes the first running virtual machine and is called the service console. Thus, at normal run-time, the vmkernel is running on the bare computer and the Linux-based service console runs as the first virtual machine (and cannot be terminated or shutdown without shutting down the entire system).

The vmkernel itself, which VMware claims is a microkernel, has three interfaces to the outside world:

    * hardware
    * guest systems
    * service console (Console OS)

Guest systems

The vmkernel offers an interface to guest systems which simulates hardware. This takes place in such a way that a guest system itself can run unmodified atop the hypervisor. Because using unmodified drivers in the guest system uses up some system resources, VMware Inc offers special drivers for different operating systems to increase performance. These enhanced drivers are typically installed on the guest OS as part of VMTools, which also add utilities to better connect the guest OS with the underlying vmkernel and/or service console, for things such as better clock synchronization and automatic guest OS shutdown.

 Service console

The Service Console is a vestigial general purpose operating system most significantly used as the bootstrap for the VMware kernel, vmkernel, and secondarily used as a management interface. Both of these Console OS functions are being deprecated as VMware migrates to exclusively the 'embedded' ESX model, current version being ESX 3i.

 Linux dependencies

ESX Server uses a Linux kernel to load additional code: often referred to by VMware, Inc. as the "vmkernel". The dependencies between the "vmkernel" and the Linux part of the ESX server have changed drastically over different major versions of the software. The VMware FAQ[10] states: "ESX Server also incorporates a service console based on a Linux 2.4 kernel that is used to boot the ESX Server virtualization layer". The Linux kernel runs before any other software on an ESX host. On ESX versions 1 and 2, no VMkernel processes run on the system during the boot process. After the Linux kernel has loaded, the S90vmware script loads the vmkernel. VMware Inc states that vmkernel does not derive from Linux, but acknowledges that it has adapted certain device-drivers from Linux device drivers. The Linux kernel continues running, under the control of the vmkernel, providing functions including the proc file system used by the ESX and an environment to run support applications. ESX version 3 loads the VMkernel from the Linux initrd, thus much earlier in the boot-sequence than in earlier ESX versions.

In traditional systems, a given operating system runs a single kernel. The VMware FAQ mentions that ESX has both a Linux 2.4 kernel and vmkernel — hence confusion over whether ESX has a Linux base. An ESX system starts a Linux kernel first, but it loads vmkernel (also described by VMware as a kernel), which according to VMware 'wraps around' the linux kernel, and which (according to VMware Inc) does not derive from Linux..

The ESX userspace environment, known as the "Service Console" (or as "COS" or as "vmnix"), derives from a modified version of Red Hat Linux, (Red Hat 7.2 for ESX 2.x and Red Hat Enterprise Linux 3 for ESX 3.x). In general, this Service Console provides management interfaces (CLI, webpage MUI, Remote Console). This VMware ESX hypervisor virtualization approach provides lower overhead and better control and granularity for allocating resources (CPU-time, disk-bandwidth, network-bandwidth, memory-utilization) to virtual machines, compared to so-called "hosted" virtualization, where a base OS handles the physical resources. It also increases security, thus positioning VMware ESX as an enterprise-grade product.

As a further detail which differentiates the ESX from other VMware virtualization products: ESX supports the VMware proprietary cluster file system VMFS. VMFS enables multiple hosts to access the same SAN LUNs simultaneously, while file-level locking provides simple protection to file-system integrity.


check out the rest of the Windows Live™. More than mail–Windows Live™ goes way beyond your inbox. More than messages