Question: Scenario: You work for a consulting firm as a VMware vSphere implementation expert, and your firm was recently selected to implement vSphere Enterprise Plus into an existing network. This will be a brand new install with no existing virtualization products present.

As you are being brought up to speed on the project you find out the following information about the infrastructure you are moving over to vSphere:

1. There are 15 physical servers, all running Windows 2008.

2. Applications in use:

• Exchange Server

• SQL Server

• SAP

• SharePoint Server

3. All existing servers are using less than 750 GB of drive space each, and no server is using more than 8 GB of RAM.

4. There is only a single location for this organization, and the network has two subnets one for the clients and one for the servers:

• Server subnet is 10.1.0.X

• Client subnet is 10.2.0.X

5. The customer has agreed to allow you to move over one server at a time, but full migration must be done within seven days.

The new infrastructure to which you are moving consists of the following:

• Four new servers with 300 GB of RAM each

• A new Storage Area Network (SAN) connected via Fiber Channel with 20 TB of usable storage capacity

• Each server is connected to existing network with 10 Gbps

You have been tasked with creating an installation/migration plan proposal to submit for customer approval. This plan should be 2 to 3 pages in length. If there are details missing that might prevent you from completing the migration plan, go ahead and make assumptions, but be sure to document them. Your 2- to 3-page plan should include the following:

1. Products - Include which VMware products need to be installed and used for the scope of this project. Make sure to include any VMware virtual machines that may be needed to support your configuration.

2. Obstacles - Use the knowledge you have gained from the lab assignments to anticipate obstacles. Address any obstacles that should be considered for the installation and configuration of vSphere. Document how you could overcome these obstacles, and apply what you learned.

3. Configuration - Include how vSphere should be configured at a high level, specifically covering:

• Configuration of virtual switches

• How to connect to the storage provided

• How templates can be used during the migration

• How resources should be allocated to virtual machines

• What tasks can be automated

• How to monitor performance after you migrate each physical system to ensure resources are allocated properly

4. Timeline - Create a high level timeline for this entire project. Make sure to consider the build time for your vSphere environment, time to migrate each server, and time to test the migration.