0% found this document useful (0 votes)
46 views54 pages

DEN301 Week 4 Webinar

The document discusses installing Windows 10 in a virtual machine. It describes selecting a virtual machine, setting the boot device to an ISO image of Windows 10, and starting the virtual machine to begin installing Windows 10. It also mentions optimizing the virtual machine and installing VMware Tools.

Uploaded by

Fun Toosh345
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
46 views54 pages

DEN301 Week 4 Webinar

The document discusses installing Windows 10 in a virtual machine. It describes selecting a virtual machine, setting the boot device to an ISO image of Windows 10, and starting the virtual machine to begin installing Windows 10. It also mentions optimizing the virtual machine and installing VMware Tools.

Uploaded by

Fun Toosh345
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 54

DEN301 – Virtual Systems and

Services
Week 4 - Webinar
Installing Windows on a Virtual Machine

M. Portnoy, Virtualization Essentials (2nd edition), John Wiley,


2016, ISBN 9781118176719.
TEQSA: PRV14311
CRICOS: 03836J
DEN301 Teaching Team
Unit Coordinator & Class B Class A Lecturer: Mr Class C Lecturer: Ms Class D Lecturer: Ms
Lecturer: Dr Yancong Xie Usman Naseem Ashwini Shivabasappa Ashwini Shivabasappa

Any Questions? Any Questions? Any Questions? Any Questions?

• Class time: • Class time: • Class time: • Class time:


Wednesday: 3.30pm- Wednesday: Friday: 9.00am to Friday: 11.00am-
5.30pm 1.00pm-3.00pm 11:00am 1.00pm

• Email: • Email: • Email: • Email:


[email protected] [email protected] [email protected] [email protected]
u.au w.edu.au u.au du.au
Copyright Disclaimer
All staff and students are required to abide by the Copyright Act 1968, when
providing, accessing and using learning resources and materials. Some
resources are provided under the statutory licence, and you are required to
see this notice:

WARNING
This material has been reproduced and communicated to you by or on behalf
of Sydney International School of Business and Technology in accordance with
section 113P of the Copyright Act 1968 (Act).

The material in this communication may be subject to copyright under the Act.
Any further reproduction or communication of this material by you may be the
subject of copyright protection under the Act.
Do not remove this notice.
TEQSA: PRV14311
CRICOS: 03836J 3 3
Recap of the Previous Webinar
1. Performing P2V Conversions
1. Investigating the Physical-to-Virtual Process
2. Hot and Cold Cloning
2. Loading Your Environment
1. Loading VMware Workstation Player
2. Loading VirtualBox
3. Building a New Virtual Machine
1. Thinking about VM Configuration
2. Creating a First VM

TEQSA: PRV14311
CRICOS: 03836J 4 4
Learning Objectives
1. Loading Windows into a Virtual Machine
1. Installing a Windows 10
2. Installing VMware Tools
2. Understanding Configuration Options
3. Optimizing a New Virtual Machine

TEQSA: PRV14311
CRICOS: 03836J 5 5
Background
• Like a physical server, a virtual machine needs to have an operating system installed to
function and run applications.
• Although there are still dozens of different operating systems that can work on the x86
platform, the bulk of virtualization today is done on the more recent versions of
Windows.
• Understanding how to install Windows and then optimize it for a virtual environment is
crucial.

TEQSA: PRV14311
CRICOS: 03836J 6 6
(1) Loading Windows into a Virtual Machine
• A Windows operating system can be loaded into a virtual machine in a number of ways.
• In the previous chapter, you saw that during the process of creating a virtual machine,
VMware Workstation Player offers the option to install Windows as part of that effort.
• Most virtual machines are created through a template. Templates are virtual machines
that already contain an operating system and often are already loaded with application
software as well.
• These prebuilt VMs are stored in a nonexecutable state that allows an administrator to
rapidly stamp out copies of the selected configuration. Once a copy is created, a few
more personalization and system configuration steps, such as providing a unique system
name and network address, will need to be completed before the new VM can be
deployed.

TEQSA: PRV14311
CRICOS: 03836J 7 7
(1) Loading Windows into a Virtual Machine
• Periodically, a virtual machine requires a pristine copy of Windows.
• Some administrators create a new template with every new major release, while others
merely power on the existing template and apply the service packs.
• Some administrators prefer the new install because it forces them to look at the other
pieces of software in the VM that might also need updates or refreshes.
• Others believe that loading a version of Windows with the service packs (SPs) already as
part of the distribution is somehow intrinsically superior to applying the service packs
separately.
• There is no incorrect choice here. Most people choose a path that works for them.
Instructions for installing VMware Tools follow those for installing Windows 10. These
steps are optional but highly recommended.

TEQSA: PRV14311
CRICOS: 03836J 8 8
(1) Installing a Windows 10
• In order to install Windows, or any operating system, you need the source disks so that
you can execute from them. These disks can take the form of actual CDs, DVDs, or image
files of the software on other media.
• In the case of Microsoft Windows, you can purchase a copy at a retail store and come
home with the disks, or buy it online and download the images to your computer. That
image can be burned to a CD or DVD for backup or execution purposes.
• We are using Windows Evaluation in this subject.

TEQSA: PRV14311
CRICOS: 03836J 9 9
(1) Installing a Windows 10
• The steps that follow are not the only method you can use to create
a Windows 10 virtual machine, but rather one of many possible
options. For these examples, a 64-bit version of Windows 10 was
used (see the right figure). The ISO image is staged on the desktop
for the VM to access.
1. Open VMware Workstation Player.
2. Select the Windows 10 x64 virtual machine you created earlier by
left-clicking on the Windows 10 x64 VM icon shown in the next
slide. You can also select the VM by choosing the Open A Virtual
Machine option on the right, navigating to the Windows 10 x64
directory under the Virtual Machines directory, selecting the .vmx
file, and clicking Open. Either method will work.

TEQSA: PRV14311
CRICOS: 03836J 10 10
(1) Installing a Windows 10

TEQSA: PRV14311
CRICOS: 03836J 11 11
(1) Installing a Windows 10
3. Note that the machine state is powered off.
You need to tell the VM to boot from the ISO
image, much as a physical server needs the CD
or DVD drive in the boot sequence so it can
find the Windows disks you would stage there.
Select Edit Virtual Machine Settings, which
results in the screen shown in the right figure.

TEQSA: PRV14311
CRICOS: 03836J 12 12
(1) Installing a Windows 10
4. As shown in the right figure, select CD/DVD.
5. You can see a number of choices regarding
the CD/DVD devices. Under Connection,
choose Use ISO Image File. This will allow you
to have the VM use the ISO image you have
staged. Use the Browse button to locate and
select the ISO image. Select OK to continue.
Note. If these options are grey and you cannot
click them, please delete the existing VM and
create a new one. After you created a new VM,
you will find that you can select the ISO file
now!

TEQSA: PRV14311
CRICOS: 03836J 13 13
(1) Installing a Windows 10
Note. When you create a new virtual machine,
do not directly select the ISO file as shown in
the left-hand side figure.
If you select the option, when you boot up your
virtual machine, you will come across a
problem saying “windows cannot find the
Microsoft software license terms”!

TEQSA: PRV14311
CRICOS: 03836J 14 14
(1) Installing a Windows 10
6. Now select Play Virtual Machine. You might
get a message similar to that shown in the right
figure. It means that you have additional
hardware devices on your physical computer
that could be added to the virtual machine for
use. Select OK to continue.6.

TEQSA: PRV14311
CRICOS: 03836J 15 15
(1) Installing a Windows 10
Note. When you boot up your virtual
machine, you will see the left-hand side
figure. Upon seeing this, you need to
quickly press any key on your keyboard.
If you don’t do it quickly, you will see
the below time out screen.

TEQSA: PRV14311
CRICOS: 03836J 16 16
(1) Installing a Windows 10
7. The virtual machine boots up and connects to the
Windows 10 ISO image as if it were a DVD in a disk
drive. If you are prompted to download VMware Tools
for Windows 2000 and later, you can accept the
download by choosing Download And Install and
pausing a few moments until it completes the update.
The Windows Setup screen appears, as shown in the
right figure. Notice at the bottom of the screen,
outside of the virtual machine is an alert bar with
some choices regarding the installation of VMware
Tools.

TEQSA: PRV14311
CRICOS: 03836J 17 17
(1) Installing a Windows 10
8. In the VM Window, click inside the Window
Setup window and select your menu choices.
Select Next to continue.
9. The next screen, illustrated in the right figure,
allows you to Repair Your Computer if needed
before continuing. Select Install Now to continue.

TEQSA: PRV14311
CRICOS: 03836J 18 18
(1) Installing a Windows 10
10. As with most software, you will need to accept
the license terms. Select the checkbox as shown in
Figure 5.8, and then select Next to continue.

TEQSA: PRV14311
CRICOS: 03836J 19 19
(1) Installing a Windows 10
11. Because this is a new installation, you will be
doing a Custom installation rather than an upgrade
of an existing system. As shown in the right figure,
choose Custom to continue.

TEQSA: PRV14311
CRICOS: 03836J 20 20
(1) Installing a Windows 10
12. The example VM was created with one 30 GB
disk drive. Select Next to continue. See the right
figure.

TEQSA: PRV14311
CRICOS: 03836J 21 21
(1) Installing a Windows 10
13. The Windows installation process will proceed
with a number of steps, including formatting the
disk storage, creating a file system, and copying
the files to the disk. This is usually the most time-
consuming step. You can see the steps and the
progress in the right figure.

TEQSA: PRV14311
CRICOS: 03836J 22 22
(1) Installing a Windows 10
14. Windows will reboot a number of times during
the process. It will then run through a number of
first-time use initialization steps. The Express
Settings screen, illustrated in the right figure,
allows you to streamline the configuration process
or to customize all of the settings. For our
purposes, streamlining is fine. Select Use Express
Settings to continue.

TEQSA: PRV14311
CRICOS: 03836J 23 23
(1) Installing a Windows 10
15. After a reboot, you will be prompted to select a
connection method. Choose Join A Domain, as
shown in the right figure, and then select Next to
continue.

TEQSA: PRV14311
CRICOS: 03836J 24 24
(1) Installing a Windows 10
16. You will need to choose a username, a
password, and a hint for that password for the user
you just created. The right figure shows this
screen. Enter a username, a password, and a hint,
and then select Next to continue.

TEQSA: PRV14311
CRICOS: 03836J 25 25
(1) Installing a Windows 10
17. The Windows installation process logs into
Windows and does some initial setup. When that
is complete, you will be presented with a Network
screen, as shown in the right figure. Select Yes to
continue.

TEQSA: PRV14311
CRICOS: 03836J 26 26
(1) Installing a Windows 10
18. As you can see in the right figure, Windows will
complete the one-time setup and be ready for use.

TEQSA: PRV14311
CRICOS: 03836J 27 27
(1) Installing VMware Tools
• You have one more step left to complete before you can work in this virtual machine, and
that is adding the VMware Tools.
• VMware Tools are a combination of device drivers and processes that enhance the user
experience with the VM, improve VM performance, and help manage the virtual
machine.
• Although installation of the VMware Tools suite is not mandatory, it is very highly
recommended for VMs in any of the VMware environments.

TEQSA: PRV14311
CRICOS: 03836J 28 28
(1) Installing VMware Tools
1.Select Player from the menu at the top of the
VMware Workstation Player window. Choose the
Manage menu option. Select Install VMware Tools
as shown in the right figure.

TEQSA: PRV14311
CRICOS: 03836J 29 29
(1) Installing VMware Tools
2.The VMware Tools DVD is mounted in the virtual
machine. (If you did not download the VMware
Tools earlier, you may get a prompt to do so now.
Download the Tools and then continue.) Click on
the Disc Mounted message. Illustrated in Figure
5.18 are the choices for the disc. Choose Run
Setup64.exe to continue. Answer Yes to the Allow
Changes screen.

TEQSA: PRV14311
CRICOS: 03836J 30 30
(1) Installing VMware Tools
3.The initial VMware Tools installation screen
appears, as illustrated in Figure 5.19. Choose Next
to continue.

TEQSA: PRV14311
CRICOS: 03836J 31 31
(1) Installing VMware Tools
4. The right figure shows the Setup Type selection
window, which offers short descriptions of the
three options. The default is Typical, which is
sufficient for your needs. Choose Next to continue.

TEQSA: PRV14311
CRICOS: 03836J 32 32
(1) Installing VMware Tools
5.The Install screen appears, as shown in the right
figure. If any changes need to be made, you can
use the Back button to scroll back through the
preceding screens to make those changes. If you
are ready to continue, select Install.

TEQSA: PRV14311
CRICOS: 03836J 33 33
(1) Installing VMware Tools
6.The VMware Tools are installed, and you can
mark the progress on the displayed Status screen.
It is typically a very short process, requiring only a
few minutes. When it is completed, the final
screen, as shown in the right figure, is displayed.
Select Finish.

TEQSA: PRV14311
CRICOS: 03836J 34 34
(1) Installing VMware Tools
7.Finally, you need to reboot the VM one more
time. The system prompts you, as shown in the
right figure. Select Yes to restart the VM.

TEQSA: PRV14311
CRICOS: 03836J 35 35
(2) Understanding Configuration Options
• Now that you have a working VM, let's take a closer
look at what you've built.
• The first thing to observe is that the VM looks identical
to the physical desktop, which is exactly what you
want. If you select the Start icon, you'll see exactly
what you would expect to see in a fresh install of
Microsoft Windows 10, as shown in the right figure.
• It is easy to tell that you are using a virtual machine by
looking at the VMware Workstation Player application
bar at the top of the VM window. However, most
virtual machines are run on servers and are connected
to by users who never see the physical or virtual
servers with which they work.

TEQSA: PRV14311
CRICOS: 03836J 36 36
(2) Understanding Configuration Options
• If you were to connect to this VM via the network using the Remote Desktop Connection, could
you determine if it was a physical or virtual server?
• The answer is yes. There are a number of key giveaways that you could quickly check to make that
determination.
• First, by highlighting the hidden icons at the bottom right, you will see a VM logo. This indicates
that VMware Tools has been installed on this particular VM.
• You can open the About VMware Tools window to verify that the service is running, as shown in
the next figure. Remember, though, that installing the VMware Tools is recommended, but not
mandatory. This means that the absence of VMware Tools does not automatically indicate that it
is a physical machine. Close the About VMware Tools window.

TEQSA: PRV14311
CRICOS: 03836J 37 37
(2) Understanding Configuration Options

TEQSA: PRV14311
CRICOS: 03836J 38 38
(2) Understanding Configuration Options
• There are ways to more definitively determine
what type of system you're using.
• Choose the Start icon and select Settings and then
the Devices icon. Choose Connected Devices and
scroll down on the right side of the screen to the
bottom. Select Devices And Printers. You can
instantly see that some of the devices do not
match any physical vendor hardware.
• The right figure shows a VMware Virtual USB
Mouse, a VMware Virtual S SCSI Disk Drive, and
VMware Virtual USB Sensors; but even more
telling is that when you select the machine icon on
the top left of the devices window.

TEQSA: PRV14311
CRICOS: 03836J 39 39
(2) Understanding Configuration Options
• When you highlight the image, you can see preliminary
information at the bottom of the window. It is fairly obvious
that this computer is of the virtual variety manufactured by
VMware.
• If you follow the same path on your physical computer, you
should see the difference immediately. When you double-
click the computer image, a properties window appears, and
you can see that the VM is a virtual machine. Select the
Hardware tab and scroll through the devices, as shown in the
right figure, to confirm that virtual devices compose the
system. On your physical computer, obviously only physical
devices would be present. Close the windows to continue.

TEQSA: PRV14311
CRICOS: 03836J 40 40
(2) Understanding Configuration Options
• Let's look at two more items that will help illustrate
the differences between what the physical machine
has and what the virtual machine thinks it has.
• Again, select Start &cmdarr; Settings &cmdarr;
System &cmdarr; Storage. Here you can see the single
disk drive that you created; the C: drive still has about
20 GB free out of the 30 GB it has. But what is the
actual size of the storage on this physical system?
• By following the same steps for the physical system,
as shown in the right figure, you can see that the
physical C: drive is considerably larger. Close both the
physical and virtual Storage windows.

TEQSA: PRV14311
CRICOS: 03836J 41 41
(2) Understanding Configuration Options
1.Enter Control Panel into the search bar of your
virtual machine. When the program appears in the
list, select it. Navigate to System and Security
&cmdarr; System.&cmdarr;The key information is
displayed. The Windows version is, as you'd expect,
Windows 10. You have 2 GB of memory (RAM), just
as you configured. The processor information is also
available.
2.Now, in your physical environment, duplicate the
previous steps to show the Control Panel on your
computer. As you can see in the right figure, this
physical machine actually has 8 GB of memory,
again more than what is configured for the virtual
machine.

TEQSA: PRV14311
CRICOS: 03836J 42 42
(2) Understanding Configuration Options
3.You can examine some of the other similarities and differences and then close those windows when
you are done.
• Now let's make one small adjustment to the VM just to experience the flexibility of
changing the configuration. You've allocated 2 GB of memory to the VM, but if you look at
the Microsoft Windows 10 system requirements, a 64-bit implementation, which is what is
deployed, should have a minimum of 2 GB. You haven't done anything yet to stress the
VM from a performance standpoint, so the 2 GB has been sufficient to operate without
any ill effects.

TEQSA: PRV14311
CRICOS: 03836J 43 43
(2) Understanding Configuration Options
1.Select Player from the VMware Workstation Player menu
bar.
2.Select Manage from the menu and then select Virtual
Machine Settings.
3.As shown in the right figure, highlighting the Memory
device in the Hardware tab shows the controls for adjusting
the memory in the VM. There are values that are selected
by VMware Workstation Player as minimum,
recommended, and maximum values. You can adjust the
memory right to those values by selecting the colored
boxes next to those suggestions. You can also manually
adjust memory by moving the slider up or down, or by
entering a specific value into the field indicated by Memory
for this virtual machine.

TEQSA: PRV14311
CRICOS: 03836J 44 44
(2) Understanding Configuration Options
4.Adjust the memory value to 1.5 GB by entering 1536 into the Memory For This Virtual Machine
field. Notice the warning at the bottom of window that states the change will not occur until the
VM is restarted. This is an operating system requirement, not a virtual machine requirement.
In certain versions of the hypervisor applications, the VM would automatically accept the additional
memory and show the new larger value. Here, we would need to shut down the VM, change the
amount of memory, and then reboot the VM for the change to take effect.
To perform the equivalent reconfiguration in a physical server would require not only the same
system restart but actual hardware changes, installing additional memory, which would take
anywhere from tens of minutes to hours, depending on the environment. Multiply the time of that
operation by dozens of servers, or hundreds, and it is easy to see why rapid reconfiguration is one of
the many strengths of virtualization.

TEQSA: PRV14311
CRICOS: 03836J 45 45
(3) Optimizing a New Virtual Machine
• The process we just executed is not very different from what system administrators go
through as they deploy workloads onto a virtual platform.
• There are automation options and other methods of improving their operational
efficiency available, and we'll cover some of these as we progress, but the basic template
is here.
• This, however, is only the first step in creating an application's virtual machine. You have
completed a fairly generic Microsoft Windows installation, but there are two more
important steps you need to take to help the VM perform its very best for the application
that will run there.
• The first is specific to virtual machines, while the second is just good practice for physical
or virtual servers.

TEQSA: PRV14311
CRICOS: 03836J 46 46
(3) Optimizing a New Virtual Machine
• Many services that run as part of the Windows operating system help optimize how the
physical environment runs. Some of these services don't optimize a virtual environment,
so it makes good sense to just disable them.
• Many of the wireless networking services, for example, while perfectly reasonable for a
Windows 10 implementation running on a local laptop, do nothing for a Windows 10 VM
running on a host server because that physical hardware wouldn't normally have access
to a wireless network. There are other physical world features that PCs have that don't
translate to a virtual world.
• Administrators routinely disable power management features because they don't apply
to a VM. Virtualized servers often have many of the personalization features removed or
disabled because fancy fonts and customized sounds are not necessary for an application
server. They also take up disk space and use CPU and memory resources.

TEQSA: PRV14311
CRICOS: 03836J 47 47
(3) Optimizing a New Virtual Machine
• Wallpapers are removed, as are screen savers. Various visual effects, such as Aero, are
often disabled for virtual application servers. The intent of all of these modifications is to
provide VMs that do not needlessly consume extra CPU cycles, memory blocks, I/O
bandwidth, or disk space.
• On one virtual machine, all of these savings are small, but when you stack many multiple
VMs on a physical server, they provide significant efficiencies—and virtualization is all
about improving efficiencies. Administrators apply these optimizations into their
templates so they can be replicated again and again to newly provisioned VMs.

TEQSA: PRV14311
CRICOS: 03836J 48 48
(3) Optimizing a New Virtual Machine
• The second step could apply to either physical or virtual machines.
• One of the best practices for moving physical application workloads to virtual machines is
to ensure that enough resources are allocated to the virtual machine to provide equal or
better performance on a virtual platform.
• So that you can understand what those resource requirements are, some type of
performance metrics need to be collected while the application is still staged in a
physical environment.
• There are professional services engagements as well as automated tools that can help
gather this information and translate it into recommendations for virtual machine
configuration sizes and even host server configurations.

TEQSA: PRV14311
CRICOS: 03836J 49 49
(3) Optimizing a New Virtual Machine
• However those metrics are acquired, the information is vital to properly configuring the
virtual machine.
• Then there are certain applications that seem to have been created for virtualization.
• Very often web servers, which in the physical world typically each require their own
server, can be densely packed onto a single host, because of memory optimization
technologies available within certain hypervisors.

TEQSA: PRV14311
CRICOS: 03836J 50 50
Summary
• This week we learned how to install a Windows OS on your VMware
workstation player.

• At first, we went through the process to install Windows and VMware


tools.

• Then we went through configuration options of your virtual Windows.

• In the last topic, we briefly mentioned how to optimise your virtual


Machine configuration.

TEQSA: PRV14311
CRICOS: 03836J 51 51
Next Topic
• Installing Linux on a Virtual Machine

TEQSA: PRV14311
CRICOS: 03836J 52 52
Your Tasks For The Week
• Review the webinar’s content and the notes taken

• ASK QUESTIONS if you have any

• Start to find a group for your assessment 2 (the deadline of group


registration is week 6).
• To register a group, send an email including your group members’ info to your
lecturer.

TEQSA: PRV14311
CRICOS: 03836J 53 53
Any Questions?

TEQSA: PRV14311
CRICOS: 03836J 54 54

You might also like