Vous êtes sur la page 1sur 20

2016

Purdue University

CNIT 242

Section 001

Authors: Benya Chongolnee Noah Grostefon Emily Harshman TA: Professor Hands Due Date: 11/03/16 Date Submitted: 10/31/16

-On Blackboard

Lab 02: Enterprise Virtualization

Table of Contents Executive Summary

2

Background & Business Scenario

3

Procedures

4-7

Phase 1……………………………………………………………

4-5

PC Check…………………………………………………………

4

Installed VMware ESXI Server on the Optiplex 7010/990.…….4

Move the Windows 7 virtual machine …………………….…

4-5

Perform a P to V operation on the domain controller……

….5

5

5

Install VMware Tools to virtual machines………………… Phase 2……………………………………………………………….….5-7

5

Migrating domain controller to the ESXi Server……… Install ESXi on Optiplex 990……………………………………

Configure Additional Datastores………………………

……

5-6

Manage Virtual Machines……………………………………

6-7

Results

8-10

Network Diagram

13-14

Conclusions and Recommendations

15-16

References

17

Appendix

18

Appendix A: Problem Solving and Troubleshooting

18

Appendix B: Cisco PIX Configuration

19

Executive Summary

The purpose of this report is to describe how Hands Publishing™ virtualized their

software and hardware, and how they plan on implementing the software and hardware

to expand their business without having to add further expenses. The report shows the

in depth steps that were taken in order to ensure a successful setup in order for Hands

Publishing™ employees to be able to access their company accounts both on company

computers and on their personal computers. This would allow for the employees to be

more mobile in and out of the office; therefore, allowing more productivity for the

business.

A relevant literature review was conducted in order to ensure a successful setup

for the virtualization software. In this report, this report explores 3 main topics:

1) The client need for this particular virtualization software

2) The software used in order to implement the setup

3) The recommendations from team members to ensure a relatively easy setup

With this set up, important recommendations for improving implementation was

identified including continual updates of software and training into this new software

being used.

2

Background and Business Scenario

Since Hands Publishing™ is a new business, the company is still in the process

of growing. With that being said, Hands Publishing™ requires more servers and

computers to keep their Domain Controllers, Windows 2012, Windows 7, and vCenter

Server. They requires more machines to run their growing business; however, since

they are still new, they do not have a lot of budget to spend on physical computers and

hardware. The solution to this issue is to virtualize their computers. This not only save

the company money from not purchasing extra hardware, it will also give their staff the

ability to work outside of their office and not on their office computer. On top of this,

virtualizing the company’s servers also make everything more convenience and easier

to use. Hands Publishing™ now have a Domain Controllers, Windows 2012, Windows

7, and vCenter Server virtualized on the local Windows Server 2012. They are able to

access these virtualized machines using vSphere Client.

By virtualizing the computers, the staff of Hands Publishing™ are able to run and

edit the machines right off their personal computer or laptop using the vSphere Client

software when they are connected to the network. In order to do so, they must know

their server’s IP address as well as the credentials for it. On top of this, by installing

many different machines onto one computer, Hands Publishing™ also will be able to

save a lot of money by not purchasing extra physical servers and computers. The

company could instead use the money saved on expanding the company.

3

Procedures

Phase 1

PC Check:

1. Checked PCs and cables to make sure that they are connected correctly

Installed VMware ESXI Server (6.0) on the Optiplex 7010/990:

1. Installed WIndows 7 Vm on vSphere

​ ​ a. Opened vSphere client | ​File | New | Virtual Machine | Typical
a. Opened vSphere client | ​File | New | Virtual Machine | Typical | Entered
Name | ​Next | Datastore 1 | Next | Microsoft Windows | Selected ​Windows
7 from drop down menu | ​Next | Allocated storage to the virtual disk | ​Next
| Install
b. Ran the virtual machine | ​Mount drive to VM | Selected Windows 7 iso file
from RTFM server | Rebooted VM​ | Followed installation process until
Windows 7 desktop loaded
2. Replaced the Optiplex 7010/990 Windows with a VMware vSphere (ESXi) server
a. Inserted Disc4 into optical drive | Rebooted machine and went into the
BIOS | Booted from disc
b. Launched ESXi installer | ​Enter | F11 to accept | Selected disk drive |
Confirmed installation | Enter to reboot
3. Installed the VMware viClient to Windows 10 machine
a. Started the Windows 10 machine | launched ​Windows Explorer | Navigate
to ​\\rtfm.cit.lcl | Located viclient installer within rtfm.cit.lcl | Launched
installer
b.
Selected vSphere Client in the installer | followed installation steps as
guided by the installer
4. Installed a clean virtual Windows Server 2012 R2 (with GUI)
a.
Launched vSphere client | Entered IP address, username, and password
of the ESXi server previously installed | Selected the ESXi server within
vSphere | ​File | New | Virtual Machine | Typical | Entered VM Name |​ Next
| Microsoft Windows | Selected ​Windows Server 2012 | Next | Allocated
storage to virtual disk | ​Next | Install
b. Ran the newly created VM | ​Mount drive to VM | Selected Windows Server
2102 R2 iso file from RTFM server | Rebooted VM | Followed installation
process until Windows Server 2012 loaded to desktop

Move the Windows 7 virtual machine by copying the VM folder:

4

1. Selected Windows 7 virtual machine in the vSphere client | Right-click | Migrate | Change host | Next | Selected ESXi server as new host | Selected resource pool | Next | High Priority | Next

Perform a P to V operation on the domain controller, migrating it to the ESXi Server:

1. Launched vmWare Converter | Selected source type and specified the machine to be converted | Next | Selected VMware Infrastructure virtual machine from drop-down | Next | Selected appropriate system parameters | Next | Finish

Install ESXi on Optiplex 990 previously hosting the domain controller:

1. Inserted Disc into optical drive | Rebooted machine and went into the BIOS | Booted from disc

2. Launched ESXi installer | Enter | F11 to accept | Selected disk drive | Confirmed installation | Enter to reboot

Install VMware Tools to virtual machines (excluding Windows 7 VM):

1. Selected Windows Server 2012 VM | Right-clicked | Guest | Install/Upgrade VMware Tools | Started up Windows Server 2012 VM | Opened console | Navigated to Windows Explorer | Right-clicked D: drive | Ran VMware Tools installer | Followed Installation process | Rebooted VM

2. Selected Domain Controller VM | Right-clicked | Guest | Install/Upgrade VMware Tools | Started up Domain Controller VM | Opened console | Navigated to Windows Explorer | Right-clicked D: drive | Ran VMware Tools installer | Followed Installation process | Rebooted VM

Phase 2

Configure Additional Datastores:

1. Disconnected Optiplex 990 machine housing the ESXi datastore | checked that a second HDD was installed | Reconnected machine | Rebooted ESXi server

2. Configured both ESXi servers to access an iSCSI SAN LUN and formatted as VMFS datastore

a. Selected storage adapters | Added software iSCSI Adapter | Right-clicked iSCSI Software Adapter | Selected add under Network Configuration |

5

Chose iSCSI port group | Clicked Add in the Dynamic Discovery tab | Added the IP address of the SAN server (‘192.168.50.1’) | Clicked Add Storage under Storage → Hardware | Selected DISK/LUN | Next | Chose iSCSI server | OK

b. Repeated the process on the second ESXI server with the IP address of ‘192.168.171’ as addressed inTable 3.

Manage Virtual Machines:

1. Used VMware Snapshots to protect configurations during changes

a. Selected the VM to take snapshot of | Inventory | Virtual Machine | Snapshot | Take Snapshot

b. Repeated process for various VMs throughout.

2. Controlled virtual machine access by adding vCenter to AD Domain (Vanover & Fgrehl)

a. Opened vCenter Server | Logged in using 10.18.17.9 | Opened console for Windows Server 2012

b. Opened VMware vSphere Web Client with 10.18.17.9 | signed in as administrator@vsphere.local | Clicked green plus icon by navigating to Administration → Single Sign-On → Configuration → Identity Sources |

Chose Active Directory as an LDAP server | Added group17.c24200.cit.lcl for Name | Added DC=group17, DC=c24200, DC=cit, DC=lcl for Base DN for users | Added group17.c24200.cit.lcl for Domain name | Added DC=group17, DC=c24200, DC=cit, DC=lcl for Base DN for groups | Added Idap://10.18.17.11:3268 for Primary Server URL | Added group17\administrator for Username | Typed the password for Password

3. Moved running virtual machines with vCenter and vMotion

a. Launched vSphere client | Inventory | Windows 7 VM | Migrate | Change Datastore | Next | Selected SAN datastore as new datastore | Selected resource pool | Next | High Priority | Next | Finish

b. Launched vSphere client | Inventory | Windows 7 VM | Migrate | Change Host | Next | Selected ESXi server that was previously the domain

controller as the new host | Selected resource pool | Next | High Priority | Next | Finish

4. Configured failover for the Windows 7 VM

a. Launched vSphere | Inventory | Right-clicked | New cluster | VMware HA | Next | Finish

b. Drag and dropped ESXi servers into the newly created cluster | Right-clicked Windows 7 VM | Enable failover | Finish

6

5. Installed a fresh Windows Server 2012 and applied all updates and service packs then saved VM as a template

a. Opened vSphere client | File | New | Virtual Machine | Typical | Entered Name | Next | Datastore 1 | Next | Microsoft Windows | Selected Windows Server 2012 R2 from drop down menu | Next | Allocated storage to the virtual disk | Next | Install

b. Launched newly created VM | Mount drive to VM | Selected Windows Server 2012 iso file from RTFM server | Rebooted VM| Followed installation process until Windows Server 2012 desktop loaded

c. Launched Control Panel | System and Security | Windows Update | Check for updates | Install

d. Launched vSphere | Inventory | Clean Windows Server 2012 VM | Right-clicked | Create template from VM | Finish

7

Overview of Results

Upon completion of lab two, the team successfully set up two ESXi servers on

the two Optiplex 990 machines in addition to the pre-existing Windows 10 machine on

the Optiplex 620 from the previous project. The Active Directory domain controller from

lab one overwent a physical to virtual conversion and was running on one of the ESXi

servers as a virtual machine. Three other virtual machines were created as well (two

Windows Server 2012 VMs and a Windows 7 VM). One of the Windows Server 2012

virtual machines was updated to the most recent service pack and converted to a

template within vSphere. The second Server 2012 machine was running as a vCenter

server. Each machine was connected to the network per the network addresses in

Table 1. The two ESXi servers and the vCenter server were set up following Table 2.

VCenter was added to the AD domain in order to allow for permissions to be set

to the specific users and groups of Hands Publishing™ created in previous project.

These permissions also can be accessed using the vSphere Web Client with the adress

8

of 10.18.17.9

of 10.18.17.9 vSphere Web Client with the address of 10.18.17.9 Failover and VMware High-Availability were added

vSphere Web Client with the address of 10.18.17.9

Failover and VMware High-Availability were added to vCenter as well in order to

protect data and provide a failsafe in the event of a failure or interruption in the runtime

of a virtual machine on the ESXi servers. With that being said, in order to avoid

mistakes, the company should always “take” snapshots of their virtual machines before

changing the state of it. This “saves” the current file system of the virtual machine. This

snapshot method helps the company go back to the previous state of the machines.

Lastly, the ESXi servers were configured to access an iSCSI SAN LUN and

formatted it as a VMFS datastore. This helps Hands Publishing™ manage their data as

well as turn the ESXi into Virtual machine file system.VMFS is used to store large disc

images and the files that make up a virtual machine or template. VMTools were also

installed onto the virtual machines to improve I/O responses.

onto the virtual machines to improve I/O responses. ESXi servers configured to access datastore1 and iSCSI

ESXi servers configured to access datastore1 and iSCSI datastores

servers configured to access datastore1 and iSCSI datastores VMware Tools are running on the Windows Server

VMware Tools are running on the Windows Server 2012 vCenter machine as well as other machines

10

IP Schema and Services

Table 1. IP Addresses

Operation

IP Address

Subnet mask

Default

DNS

System

Gateway

ESXi Server 1

10.18.17.3

255.255.255.0

10.18.17.1

10.2.1.11;

10.2.1.12

ESXi Server 2

10.18.17.4

255.255.255.0

10.18.17.1

10.2.1.11;

10.2.1.12

vCenter

10.18.17.9

255.255.255.0

10.18.17.1

10.18.17.11;

10.2.1.12

Domain

10.18.17.11

255.255.255.0

10.18.17.1

10.2.1.11;

Controller

10.2.1.12

First Windows

10.18.17.101

255.255.255.0

10.18.17.1

10.18.17.11;

10

10.2.1.12

Second

10.18.17.102

255.255.255.0

10.18.17.1

10.18.17.11;

Windows 10

10.2.1.12

Table 1. IP Addresses

Table 2. Credentials [Usernames & Passwords]

Host(s)

Username

Password

ESXi Server 1

root

Group17

ESXi Server 2

root

Group17

vCenter

administrator@vsphere.local

Group17!

Table 2. Usernames and Passwords

Table 3. The ESXi IP addresses and name of the iSCSI drive

Group Number

IP addresses for ESXi servers

iSCSI Drive Name (iQN)

17

192.168.50.170 &

studentsan.cit.lcl:student1

192.168.50.171

7

Table 3. ESXi IP addresses and name of the iSCSI drive

● The IP address of the SAN server is 192.168.50.1

● iSCSI is running on port 3260

● Subnet Mask is 255.255.255.0

● Domain name is group17.c24200.cit.lcl

Network Diagram

Network Diagram Network Diagram that was implemented for this project 13

Network Diagram that was implemented for this project

10.18.17.3 Virtual Machines Diagram 10.18.17.3 Virtual Machines Diagram 14

10.18.17.3 Virtual Machines Diagram

10.18.17.3 Virtual Machines Diagram 10.18.17.3 Virtual Machines Diagram 14

10.18.17.3 Virtual Machines Diagram

Conclusions and Recommendations

In conclusion, Hands Publishing™ needed a virtualization software that would

allow employees to not only work on the company computer, but also be able to access

their company account on their own individual computers. The company needed a way

to expand their company without having to pay extra for added software. With the added

virtualization software, both needs from the company and employees will be sufficiently

met.

A test pilot was run on the software the team is hoping to implement in order to

test for any issues or errors that the system might encounter. The test pilot successfully

implemented two ESXi servers to the company network. Through these tests, the team

believes that implementing this software into the company will be a success. Benefits

from adding the software will include: mobility, cost sustainability, and accessibility in

and out of the office. In order for the implementation to go smoothly, full employee and

CEO support is necessary so training of the new software can be carried out through

the company. The employee training needed for this new software will cost the

company some money but is predicted to have a high return on investment rate in the

long run.

Few issues were run into by the team throughout the test pilot. A few of those

issues happened during VMware and Vsphere setup. There were a few connectivity

issues that were resolved quickly by the team as well as some issues implementing the

physical to virtual conversion. All issues were easily troubleshot and fixed in a timely

manner and are listed below.

15

Overall, the pilot team highly recommends implementing the virtualization

software. They believe it will benefit the company more than it will cost the company in

the long run. With a little training, this software implementation will benefit both the

company and employees.

References*

Vanover, R. (2014). How To Set Active Directory Authentication with vCenter Server Appliance. Virtualization Review. Retrieved from

Fgrehl. (2015). How to add AD Authentication in vCenter 6.0 (Platform Service Controller). Virten. Retrieved from

http://www.virten.net/2015/02/how-to-add-ad-authentication-in-vcenter-6-0-

platform-service-controller/

*Please note that the references do not include the teacher assistance and the CNIT242 lectures

17

Appendices Appendix A: Problem Solving and Troubleshooting

Problem: Unable to connect to VMWare Cause:Loose ethernet cords Resolution: When connecting to the VMWare, the program stated: “Unable to contact the specified host ‘10.18.17.2’. The host might not be available on the network, there might be a network configuration problem, or the management services on this host are not responding.” This means that there is some networking issue. The first thing that was done is to check the ethernet cord. It was found that the cords were loose; therefore, reconnecting it would fix this issue.

Problem: Unable to get the ISO to the Virtual Machine Cause: Unable to add files to the Virtual Machine Resolution: After installing the Virtual Machines, ISO must be move to the Virtual Machine. In order to do so, the ISO file must be added to the Virtual Machine. To add ISO file to the Virtual Machines, VM Control must be launched.

Problem: No local machine when selecting the source type. Solution: Install VMWare Resolution: When connecting to the converter port, local machine must be selected when selecting the source type. Since that does not exist, VMWare must be installed first on the domain controller. From then on, VMWare can be connected to the client port (10.18.17.3).

Problem: Unable to add an identity source Cause: Wrong username when logging into the vSphere Web Client Resolution: In order to add vCenter to the AD domain, web client needs to be accessed using the IP address of 10.18.17.9. The username of the Web Client is “administrator@vsphere.local” and password of “Group17!”. Then, to add an identity source navigate to Administration > Single Sign-On > Configuration.

Appendix B: NetGear PIX Configuration

(GS108T V1H1 - 3.0.2)

Port number

Cable label

1

CA

2

CB

6

Ethernet cable for DESKTOP_1

7

Ethernet cable for DESKTOP_2

8

Ethernet cable for DESKTOP_3