Explore topic-wise InterviewSolutions in .

Microsoft Virtual SERVER 2005:

Microsoft Virtual Server 2005 allows SYSTEM administrators to consolidate separate hardware servers on to a single server running Microsoft Windows Server 2003 as the host operating system.

Each of the hosted servers RUNS in its own separate and isolated virtual machine environment. This allows the administrator to easily manage, provide for, and MAINTAIN large numbers of servers, and reduces the need to run multiple hardware servers in order to utilize various server products and operating systems.

Another advantage of the virtual machine environment is in test and disaster recovery. Each virtual machine session running under Virtual Server is maintained as a file, which is easily archived or transferred to another hardware server in the event of a failure. New server and system configurations can be deployed and tested in parallel with the existing system without REQUIRING costly downtime during the rollout phase.

Microsoft Virtual Server 2005:

Microsoft Virtual Server 2005 allows system administrators to consolidate separate hardware servers on to a single server running Microsoft Windows Server 2003 as the host operating system.

Each of the hosted servers runs in its own separate and isolated virtual machine environment. This allows the administrator to easily manage, provide for, and maintain large numbers of servers, and reduces the need to run multiple hardware servers in order to utilize various server products and operating systems.

Another advantage of the virtual machine environment is in test and disaster recovery. Each virtual machine session running under Virtual Server is maintained as a file, which is easily archived or transferred to another hardware server in the event of a failure. New server and system configurations can be deployed and tested in parallel with the existing system without requiring costly downtime during the rollout phase.

Accessing Virtual Server USING Visual C++:

Accessing the Virtual Server COM object using VC++ requires a few MANUAL STEPS to set up the development environment PROPERLY. TWO files are included with Virtual Server: "VSComInterfaces.h" and "VSComInterfaces.lib". These two files are located in the "Program FilesMicrosoft Virtual ServerDocumentation" directory after installation.

Accessing Virtual Server using Visual C++:

Accessing the Virtual Server COM object using VC++ requires a few manual steps to set up the development environment properly. Two files are included with Virtual Server: "VSComInterfaces.h" and "VSComInterfaces.lib". These two files are located in the "Program FilesMicrosoft Virtual ServerDocumentation" directory after installation.

Accessing VIRTUAL Server using Visual C#:

To use the Virtual Server object in Visual C#, select Project/Add Reference from the menu, select the COM TAB in the dialog box, then scroll down the list and select Virtual Server 2005 Type LIBRARY. Once the type library is added as a reference, the VirtualServer object can be REFERENCED in the program.

Accessing Virtual Server using Visual C#:

To use the Virtual Server object in Visual C#, select Project/Add Reference from the menu, select the COM tab in the dialog box, then scroll down the list and select Virtual Server 2005 Type Library. Once the type library is added as a reference, the VirtualServer object can be referenced in the program.

Accessing Virtual SERVER using VISUAL Basic:

To use the Virtual Server object in Visual Basic, select Project/Add REFERENCE from the menu, select the COM tab in the dialog box, then scroll down the list and select Virtual Server 2005 Type Library. Once the type library is added as a reference, the VirtualServer object can be referenced and USED in the program.

Accessing Virtual Server using Visual Basic:

To use the Virtual Server object in Visual Basic, select Project/Add Reference from the menu, select the COM tab in the dialog box, then scroll down the list and select Virtual Server 2005 Type Library. Once the type library is added as a reference, the VirtualServer object can be referenced and used in the program.

Virtual Server

Virtual networks in Microsoft Virtual Server allow virtual machines running in the same Virtual Server session to communicate with each other at data rates which are not limited by physical hardware. A virtual network can be configured with a basic DHCP server which is not dependent on any of the virtual machine sessions OPERATING systems.

A new virtual network is initialized when an IVMVirtualNetwork object is created using IVMVirtualServer::CreateVirtualNetwork. The IVMVirtualNetwork object is the equivalent to a multi-port Ethernet switching HUB and the IVMVirtualNetwork's properties allow software monitoring of the virtual network's data transmission statistics.

Each virtual network is automatically equipped with a basic virtual DHCP server. This server is implemented via the IVMDHCPVirtualNetworkServer COM object and can be accessed through the virtual network's DHCPVirtualNetworkServer property value. Since a virtual machine can be attached to multiple virtual networks, a virtual network's associated IVMDHCPVirtualNetworkServer object should be initialized before any virtual machine sessions are attached to that virtual network.

Attaching a virtual machine to a virtual network is a two-step process. First, the virtual machine MUST have an open virtual network adapter, which is created using IVMVirtualMachine::AddNetworkAdapter. Second, the adapter is attached to the virtual network with IVMNetworkAdapter::AttachToVirtualNetwork. PREVIOUSLY existing network ADAPTERS in a virtual machine can be freely connected to and disconnected from any virtual network using IVMNetworkAdapter::AttachToVirtualNetwork and IVMNetworkAdapter::DetachFromVirtualNetwork.

When a virtual network is deleted or unregistered, any virtual network cards connected to the virtual network are logically detached before the IVMVirtualNetwork object is deleted. This is the equivalent of unplugging network cables from a physical switching hub and can result in incomplete data transmission if any virtual machine sessions were transferring data across the virtual network while the network object was being deleted.

Virtual Server

Virtual networks in Microsoft Virtual Server allow virtual machines running in the same Virtual Server session to communicate with each other at data rates which are not limited by physical hardware. A virtual network can be configured with a basic DHCP server which is not dependent on any of the virtual machine sessions operating systems.

A new virtual network is initialized when an IVMVirtualNetwork object is created using IVMVirtualServer::CreateVirtualNetwork. The IVMVirtualNetwork object is the equivalent to a multi-port Ethernet switching hub and the IVMVirtualNetwork's properties allow software monitoring of the virtual network's data transmission statistics.

Each virtual network is automatically equipped with a basic virtual DHCP server. This server is implemented via the IVMDHCPVirtualNetworkServer COM object and can be accessed through the virtual network's DHCPVirtualNetworkServer property value. Since a virtual machine can be attached to multiple virtual networks, a virtual network's associated IVMDHCPVirtualNetworkServer object should be initialized before any virtual machine sessions are attached to that virtual network.

Attaching a virtual machine to a virtual network is a two-step process. First, the virtual machine must have an open virtual network adapter, which is created using IVMVirtualMachine::AddNetworkAdapter. Second, the adapter is attached to the virtual network with IVMNetworkAdapter::AttachToVirtualNetwork. Previously existing network adapters in a virtual machine can be freely connected to and disconnected from any virtual network using IVMNetworkAdapter::AttachToVirtualNetwork and IVMNetworkAdapter::DetachFromVirtualNetwork.

When a virtual network is deleted or unregistered, any virtual network cards connected to the virtual network are logically detached before the IVMVirtualNetwork object is deleted. This is the equivalent of unplugging network cables from a physical switching hub and can result in incomplete data transmission if any virtual machine sessions were transferring data across the virtual network while the network object was being deleted.

Virtual Server

• The virtual machine sessions running in Microsoft Virtual Server are implemented as a set of COM objects which are accessible through the Virtual Server COM API. The virtual machine sessions are isolated from each other and can be viewed as totally separate hardware environments.
• A NEW virtual machine session is initialized when an IVMVirtualMachine object is created using VMVirtualServer::CreateVirtualMachine. The IVMVirtualMachine object contains a standardized set of EMULATED hardware, with the exception of any virtual hard disks or networks which must be created separately and then attached to the IVMVirtualMachine object. A virtual machine session is the EQUIVALENT of a physical hardware system and must be viewed as a separate computer in regards to issues concerning operating system and application software installation and licensing.
• The operating state of a virtual machine session is controlled through the IVMVirtualMachine's Startup, TurnOff, Reset, Save, Pause, and Resume methods. Access to the virtual machine's emulated hardware is through the various property values of the IVMVirtualMachine object, which contain either attribute values of the virtual machine or pointers to other COM objects which implement the various emulated hardware devices such as serial ports, network cards, and so on.
• There is no access to a virtual machine's operating system or application software unless the Virtual Machine Additions software module is installed in the virtual machine session. INSTALLING Additions enables most of the methods and properties of the IVMGuestOS object associated with the virtual machine session. IVMGuestOS allows Virtual Server to execute application programs inside the virtual machine session, perform an orderly Shutdown of the virtual machine's operating system, and to generate a steady "tick" or "HEARTBEAT" event which allows Virtual Server to monitor the operating state of the virtual machine.

Virtual Server

• Host clustering keeps the physical host as cluster NODE and if host stops PERFORMING then the PROCESSES can be given to another host to run, whereas guest clustering keeps the guest as cluster node and if guest stops working then it will fail all other guest that are connected with it.
• Host clustering protects from failure of the computer that is crashed, whereas guest clustering doesn't PROVIDE PROTECTION from failure.

The benefits that are involved in VIRTUAL server host clustering are as follows:

• Server consolidation: allow virtual servers to consolidate multiple servers into one that will be easy to track and maintain virtual MACHINES at one server together.
• INCREASED availability: virtual server host clustering increases the availability of consolidated server due to which if any FAILURE occurs then another server can take up the job that is being served by the first server. The effect of failure is kept to minimum by providing risk management systems.

The benefits that are involved in virtual server host clustering are as follows:

Virtual server consists of virtual network that in turn consists of virtual machines. It allows traffic to be isolated in virtual network while COMMUNICATING with the host operating system. It allows the handling of network devices by virtual machine network service driver. This virtual machine network service driver come with the virtual server setup that is being PERFORMED on the host operating system. The main function of the network driver is to MONITOR the traffic and the routing packets. The virtual network can have several options defined like:

• It is not attached to physical network adapter: it has its own private network with its own DHCP server.
• It can attach to dedicated physical network adapter: in this case the virtual machines don’t have the PERMISSION to read, monitor or capture the host operating system.
• More then one network can attach to same physical network adapter: in this virtual machines can read, monitor and capture the inbound network traffic.
• Virtual machines are attached to same virtual network: same case above but in this they can perform the ACTIONS on the other virtual machines that are attached to the one.

Virtual server consists of virtual network that in turn consists of virtual machines. It allows traffic to be isolated in virtual network while communicating with the host operating system. It allows the handling of network devices by virtual machine network service driver. This virtual machine network service driver come with the virtual server setup that is being performed on the host operating system. The main function of the network driver is to monitor the traffic and the routing packets. The virtual network can have several options defined like:

• To create a virtual network virtual machines are required that has to be configured for the accessing.
• Virtual network is supported by virtual server to connect MANY virtual machines that can be shared with many computers in the network.
• Virtual network require network adapter to be configured and installed to a PHYSICAL computer, this way any computer can access the resources from any other computer.
• Virtual server uses DHCP server to dynamically assign the IP address to the computer SYSTEMS so that they can connect with other systems. Virtual server in this case has virtual DHCP that allows SYSTEM to be UNIQUELY identified. 
• Multiple Virtual network can be configured on a single network adapter by creating and associating the virtual network with a network adapter. After the steps virtual machines can be added to the virtual network of host operating system.

To secure Microsoft the virtual server the steps that are REQUIRED are as follows:

• The configuration file of virtual server services has to be secured
• INDIVIDUAL files that contains the configuration files and resources that are associated with the virtual server has to be secured 
• IIS (Internet information services) has to be secured with the administration website to secure the virtual platform and the virtual machines. 
• Virtual server is configured securely such as the security breaches are lower in number as it only allows those members that are directly associated with the local administrators. The permissions are GIVEN to those who are associated with it. Virtual network configuration file has to be secured to SAVE the further transmission over the web and between DIFFERENT systems.

To secure Microsoft the virtual server the steps that are required are as follows:

• Host clustering protects system from failure due to the fact that guests are configured as clustered resource group and I consists of generic SCRIPT resource, whereas standard clustering provide AUTOMATIC CHECKS to discover the cause of the failure and recover from it.
• Host clustering doesn't MONITOR the CLUSTER services, whereas standard clustering monitors the failure.

• Host clustering keeps the physical host as cluster node and if host stops performing then the processes can be given to another host to RUN, WHEREAS guest clustering keeps the guest as cluster node and if guest stops working then it will fail all other guest that are connected with it.
• Host clustering protects from failure of the COMPUTER that is CRASHED, whereas guest clustering doesn't provide protection from failure.

The benefits that are involved in virtual server host clustering are as follows:

• Server CONSOLIDATION: allow virtual servers to consolidate multiple servers into one that will be easy to track and maintain virtual machines at one server TOGETHER.
• Increased availability: virtual server host clustering increases the availability of consolidated server due to which if any failure occurs then another server can take up the job that is being served by the FIRST server. The EFFECT of failure is kept to minimum by PROVIDING risk management systems.

The benefits that are involved in virtual server host clustering are as follows:

The limitations of Kerberos protocol that is being used by the Microsoft virtual server are as follows:

• There is no provision to apply group policies to virtual server. This means that there is no provision to apply policies on the applications that are running on virtual server. Virtual server object can't define group policies using this protocol.
• Kerberos protocol provides CLUSTERING OPTION but it is limited to a certain server computer object. This object is being MANAGED by active directory by default. 
• There is no provision to rename a network name resource and change the configuration of kerberos authentication at same time. As the actions will be PERFORMED the changes will AUTOMATICALLY be reflected on it.

The limitations of Kerberos protocol that is being used by the Microsoft virtual server are as follows:

Kerberos is the authentication protocol that is being used by virtual servers. It maintains an active directory COMPUTER object that is involved in clustering. This PROVIDES the client security and easy to use FEATURES. It provides the provision of message queuing on a virtual server and allows the clients to PUBLISH the information to other computer systems. It provides clustering as well and by configuring its properties more OPTIONS can be found out to be used.

Kerberos is the authentication protocol that is being used by virtual servers. It maintains an active directory computer object that is involved in clustering. This provides the client security and easy to use features. It provides the provision of message queuing on a virtual server and allows the clients to publish the information to other computer systems. It provides clustering as well and by configuring its properties more options can be found out to be used.

The virtual server provided by MICROSOFT and PHYSICAL server has few THINGS common in between them and these are as follows: 

• Both allow access to network resources that has to be shared between two computers.
• Both publish the resources to the network CLIENTS under a unique server name.
• Both are under same network name and IP address range. 
• Both are used to provide same communication OPTION.
• Both provide the same networking modes of operations through which clients can communicate with each other.

The virtual server provided by Microsoft and physical server has few things common in between them and these are as follows: 

Microsoft Virtual server is USED to access the network application RESOURCE that is in a non-clustered environment. In this clients connected to network must remain connected in case of any failure in network access to the application and RESOURCES get LOST or the connection becomes unavailable. Microsoft Virtual server allows creation of virtual servers. These virtual servers don’t belong to any particular computer and can be damaged within a group too. The server is used to identify a group that belongs or COMMUNICATING with each other in the form of IP addresses.

Microsoft Virtual server is used to access the network application resource that is in a non-clustered environment. In this clients connected to network must remain connected in case of any failure in network access to the application and resources get lost or the connection becomes unavailable. Microsoft Virtual server allows creation of virtual servers. These virtual servers don’t belong to any particular computer and can be damaged within a group too. The server is used to identify a group that belongs or communicating with each other in the form of IP addresses.

Remote site virtualization provides server virtualization and need for remote management for the virtual machines. It is provided due to LIMITED resources that might not exist. The main challenge is to APPLY the server consolidations. Each server is using dedicative SERVICE functions and small servers and not using multiple servers. If SINGLE server approach is being given then there will be less power requirements, SPACE requirements and only one server to manage and backup that will make it prone to fail and reduce the efficiency.

Remote site virtualization provides server virtualization and need for remote management for the virtual machines. It is provided due to limited resources that might not exist. The main challenge is to apply the server consolidations. Each server is using dedicative service functions and small servers and not using multiple servers. If single server approach is being given then there will be less power requirements, space requirements and only one server to manage and backup that will make it prone to fail and reduce the efficiency.

Hyper-V server is a HYPERVISOR that doesn't require any other operating system to run on. It is a GOOD platform for organizations that needs one consolidated single server. This is used where the infrastructure work load is not high. It provides HOST clustering to PRODUCE high availability for virtual machines. Hyper-V server provides added functionalities like MANAGING, creating and distributing the virtual machines. It provides flexible and cost effective solutions for enterprise organizations.

Hyper-V server is a hypervisor that doesn't require any other operating system to run on. It is a good platform for organizations that needs one consolidated single server. This is used where the infrastructure work load is not high. It provides host clustering to produce high availability for virtual machines. Hyper-V server provides added functionalities like managing, creating and distributing the virtual machines. It provides flexible and cost effective solutions for enterprise organizations.

The limitations of Microsoft Virtual server includes:

• It doesn't support 64 bit processors and can't run 64 bit guests.
• It uses SMP but doesn't have virtualization in it. 
• It has limitation for GUEST users to use not more than ONE CPU.
• It decreases the performance of the system as the instruction set also get virtualized which increases the overhead on the application. 
• It has very LIMITED interaction with the host HARDWARE.

The limitations of Microsoft Virtual server includes:

Microsoft Virtual server includes the following FEATURES:

• It includes the SUPPORT for Linux guest OPERATING system.
• It includes Virtual DISK pre-compactor tool that prepares the disk for compacting. 
• It includes SMP (Symmetric multiprocessing) for the host operating system.
• It includes the mounting feature for virtual hard drives on host operating system that enables backups to be taken. 
• It includes the tool to mount VHD IMAGES.

Microsoft Virtual server includes the following features:

Microsoft virtual server PROVIDES virtualization PLATFORM that allows the creation of virtual machine using a windows operating SYSTEM. It is developed by Connectix. This platform provides the provision to create and MANAGE the virtual machines using IIS web based interface that keeps all the SETTINGS and configuration at one place. It also allows the management of network configuration for communicating with host operating system or other guest operating systems.

Microsoft virtual server provides virtualization platform that allows the creation of virtual machine using a windows operating system. It is developed by Connectix. This platform provides the provision to create and manage the virtual machines using IIS web based interface that keeps all the settings and configuration at one place. It also allows the management of network configuration for communicating with host operating system or other guest operating systems.