Outlook configuration.

Hi friends....

This blog describes how to create a new email profile in Microsoft Office Outlook 2010, in Microsoft Office Outlook 2007, and in Microsoft Office Outlook 2003. Additionally, this article describes how to configure Outlook so that it opens a specific profile, and the article describes how to configure Outlook so that it prompts you for a specific email profile when you start the program.. 

So follow the following steps to create a new mail....

To create a new email profile in Outlook 2010, Outlook 2007 and in Outlook 2003, follow these steps:

1. Click Start, and then click Run.
2. Copy and paste, or type the following command in the Open box, and then press ENTER control panel.
3. Open the Mail Setup dialog box.
   
4. In the Mail Setup dialog box, click Show Profiles.
5. On the General tab, under When starting Microsoft Office Outlook, use this profile, click Prompt for a profile to be used, and then click Add.
6. In the Profile Name box, type the name that you want to use for the new email profile, and then click OK.
7. In the E-mail Accounts dialog box, click Add a new e-mail account, and then click Next.
8. Click the appropriate server type for your new email account, and then click Next.
9. Type your account information in the required boxes, and then click Next.
10. Click Finish, and then click OK.

If you are a domain user, follow these steps:-

1. Click on Manually configure server settings or additional server types and then click on Next.
2. Click on Microsoft Exchange and then click on Next.
3. Enter server name or server IP in the Microsoft Exchange server field.
4. Check the box Use Cached Exchange Mode.
5. Enter your email address in the User Name field, and then click on More Settings.
6. Select the Connection tab and then check the box Connect to Microsoft Exchange using HTTP. 
7. Click on Exchange Proxy Settings.
8. Enter webmail (Example:webmaster.abc.gov.in) in the Use this URL to connect to my proxy server for Exchange field.
9. Check the box On fast networks, connect using HTTP first, then connect using TCP/IP.
10. Change NTLM Authentication to Basic Authentication and then click on OK.
    
11. Click on Apply and then on OK.
12. Make sure your email address is in the User Name field and then click on Check Name. 

Now open your MICRSOFT OUTLOOK and enjoy with new mail.......

Thanx..

Hyper-V and Type 1 Virtualization

Hyper-V implements what is commonly referred to as Type 1 Hypervisor virtualization. In this scenario, a hypervisor runs directly on the hardware of the host system and is responsible for sharing the physical hardware resources with multiple virtualmachines. This concept is illustrated in the following diagram:

In basic terms, the primary purpose of the hypervisor is to manage the physical CPU and memory allocation between the various virtual machines running on the host system.

Hardware Assisted Virtualization

Hyper-V will only run on processors which support hardware assisted virtualization. Before looking at Hyper-V in detail, it is worth providing a brief overview of what this hardware assisted virtualization actually means.

The x86 family of CPUs provide a range of protection levels also known as rings in which code can execute. Ring 0 has the highest level privilege and it is in this ring that the operating system kernel normally runs. Code executing in ring 0 is said to be running in system space, kernel mode or supervisor mode. All other code, such as applications running on the operating system, operate in less privileged rings, typically ring 3.

Under Hyper-V hypervisor virtualization a program known as a hypervisor runs directly on the hardware of the host system in ring 0. The task of this hypervisor is to handle tasks such CPU and memory resource allocation for the virtual machines in addition to providing interfaces for higher level administration and monitoring tools.

Clearly, if the hypervisor is going to occupy ring 0 of the CPU, the kernels for any guest operating systems running on the system must run in less privileged CPU rings. Unfortunately, most operating system kernels are written explicitly to run in ring 0 for the simple reason that they need to perform tasks that are only available in that ring, such as the ability to execute privileged CPU instructions and directly manipulate memory. One solution to this problem is to modify the guest operating systems, replacing any privileged operations that will only run in ring 0 of the CPU with calls to the hypervisor (known as hypercalls). The hypervisor in turn performs the task on behalf of the guest system.

Another solution is to leverage the hardware assisted virtualization features of the latest generation of processors from both Intel and AMD. These technologies, known as Intel VT and AMD-V respectively, provide extensions necessary to run unmodified guest virtual machines. In very simplistic terms these new processors provide an additional privilege mode (referred to as ring -1) above ring 0 in which the hypervisor can operate, essentially leaving ring 0 available for unmodified guest operating systems.

Hyper-V Root and Child Partitions

Running on top of the hypervisor are a root partition (also known as a parent partition) and zero or more child partitions (one for each virtual machine) as illustrated below:

The root partition is essentially a virtual machine which runs a copy of 64-bit Windows Server 2008 which, in turn, acts as a host for a number of special Hyper-V components. The root partition is responsible for providing the device drivers for the virtual machines running in the child partitions, managing the child partition lifecycles, power management and event logging. The root partition operating system also hosts the Virtualization Stack which is responsible for performing a wide range of virtualization functions (the Virtualization Stack and other root partition components will be covered in more detail later in this chapter).

Child partitions host the virtual machines in which the guest operating systems run. Hyper-V supports both Hyper-V Aware (also referred to as enlightened) and Hyper-V Unaware guest operating systems.

The Virtualization Stack and Other Root Partition Components

As previously noted, the root partition contains the Virtualization Stack. This is a collection of components that provide a large amount of the Hyper-V functionality. The following diagram provides an abstract outline of the stack: