►
From YouTube: Red Hat OpenShift Virtualization - How to create a Windows Server 2019 template image manually
Description
Installing an operating system to newly created virtual machines is tedious and error prone. It’s much easier, and faster, to use template images that are used as the base for each new virtual machine.
This video will walk through the process of manually creating a virtual machine, installing Windows Server 2019, and converting it to a template to be used for additional virtual machines.
Learn more at openshift.com
A
This
video
will
focus
on
creating
a
windows,
server,
2019
template
to
be
used
for
creating
additional
virtual
machines
and
openshift
virtualization.
Please
note
that
this
process
will
be
the
most
labor
intensive
of
creating
templates
we're
doing
this.
The
long
way,
the
hard
way,
if
you
will,
in
order
to
show
that
it
is
possible.
However,
keep
in
mind
that
there's
a
lot
of
other
tools
and
a
lot
of
other
ways
to
do
this,
that
make
it
much
simpler
and
much
easier.
A
We
do
this
by
browsing
to
the
persistent
volume
claims,
we'll
click
this
create
with
data
upload
form.
This
will
utilize
the
containerized
data
importer
or
cdi
to
upload
the
disk
from
my
local
system
into
a
persistent
volume.
Claim
first
step
is
to
choose
the
disk
that
we're
going
to
use
you
see
here.
I
have
a
server
2019
eval
iso
that
I'm
going
to
use
I'll,
give
it
a
very
simple
name:
iso-server
2019,
so
I
can
identify
it,
we'll
give
it
a
size.
A
A
After
clicking
the
upload
button,
the
containerized
data
importer
is
going
to
request
the
pvc
we'll
wait
for
our
csi
provisioner
to
create
the
volume
it
will
then
create
a
pod
and
that
pod
will
be
used
to
upload
the
data
from
my
system
into
the
persistent
volume
claim,
which
is
the
process
going
on
now
I'll
accelerate
this
process.
So
we
don't
have
to
wait
for
it
to
complete
in
the
video.
A
A
The
next
step
is
to
provision
a
virtual
machine,
a
2019
server,
2019
virtual
machine
using
that
iso.
These
templates
provide
a
lot
of
hints
and
a
lot
of
configuration
to
the
underlying
kvm
and
utilized
by
openshift
virtualization.
So
we
want
to
choose
a
template
here
that
matches
the
operating
system.
We're
going
to
be
installing,
so
I'm
going
to
use
this
server
2019
vm
template,
even
though
I
don't
have
a
source
here,
I
can
still
choose
to
create
a
virtual
machine
based
off
of
it
and
provide
my
own
source.
A
So
here
I'm
going
to
boot
by
cloning,
an
existing
persistent
volume
claim.
I
will
point
it
to
the
pvc
that
we
just
created
iso
server
2019
and
we
do
want
to
mount
the
cd-rom
as
a
boot
source,
I'll
customize,
this
virtual
machine,
I'm
going
to
give
it
a
name
in
this
instance
tmpl
or
template
server
2019.
A
A
If
I
need
to
change
the
networking
we
can
see
here
that
it
defaults
to
using
the
pod
network,
if
I
want
to
connect
it
directly
to
an
external
layer
2,
for
example,
a
vlan
interface.
I
can
do
that
from
here
and
I
can
modify
the
disk
information
notice
that
we
have
three
disks
available
here.
The
first
one
root
disk
is
going
to
be
the
cd-rom
that
we
are
cloning
from
that
pvc.
A
We
then
have
the
windows
guest
tools
down
here
at
the
bottom
and
in
the
middle
we
have
the
disk
that
will
actually
be
used
to
install
the
operating
system.
Now
I
can
modify
some
information
for
this
by
clicking
edit,
for
example.
If
I
want
to
select
a
storage
class,
you
can
see
that
lab
silver
is
default,
so
it
would
automatically
be
used.
Even
if
I
hadn't
selected
it
I'm
going
to
do
things
like
change
the
size,
etc.
I'm
going
to
change
the
name
of
this
disk
to
make
it
a
little
bit
easier
to
identify.
A
We
do
want
to
ensure
that
the
boot
source
here
is
selected
as
the
root
disk,
which
is
our
iso
our
server
2019
install
iso.
I
don't
need
to
provide
any
additional
information
at
this
point.
I'm
going
to
click
next.
We
do
want
to
start
this
virtual
machine
after
it's
created,
so
we'll
leave
that
checkbox
there.
A
And
we
will
go
ahead
and
review
our
virtual
machine
now
see
that
it
is
stuck
in
this
or
it
is
currently
in
this
importing
process
now
what's
happening
here
is
in
behind
the
scenes.
Containerized
data
importer
has
cloned
that
iso
pvc
and
it
has
attached
it.
We
have
also
waited
for
it
to
provision
the
second,
the
install
the
os
install
disk.
A
So
I'm
going
to
step
through
the
install
process
here
more
or
less
we're
going
to
accept
the
defaults
until
we
get
to
the
point
where
it
wants
us
to
select
a
disk
to
install
to.
At
that
point,
we
will
leverage
the
windows
tools,
iso
that
has
been
attached
to
the
virtual
machine.
To
then
choose
which
one
of
the
or
to
choose
a
driver
for
the
disk
notice.
I
am
choosing
the
desktop
experience.
This
is
simply
for
illustrative
purposes.
A
A
Now
notice,
here
that
there
are
no
disks
listed
as
available
for
before
installs,
I
need
to
load
a
driver
to
do
that.
I'm
going
to
click
load,
driver
and
then
browse.
I
will
choose
this
vert.
I
o
win
iso
that
is
attached
in
the
first
directory
amd
64
I'll
choose
the
folder
for
2k
19,
because
I'm
using
server
2019.
A
Once
doing
that,
we
have
two
drivers
available:
the
scuzzy
controller
and
the
scuzzy
pass-through
controller,
we're
not
using
pass-through
so
I'll
select
the
top
one.
After
a
moment
it
will
load
the
driver
rescan
the
drives,
and
it
will
offer
that
20
gigabyte
disk
that
we
attached
through
the
gui
a
few
moments
ago.
A
A
A
A
A
A
A
A
A
A
I'll
close
this
console
window,
I
want
to
see
when
the
virtual
machine
shuts
down
here.
I
did
not
change
the
run
strategy
for
this
virtual
machine,
which
means
that
when
the
guest
shuts
down
openshift
will
automatically
restart
it,
it
does
not
know
that
it
is
supposed
to
be
shut
down.
It
thinks
that
it
should
be
running
at
all
times,
so
we
just
need
to
catch
it
and
not
let
it
restart.
The
virtual
machine
also
note
that
during
this
sysprep
process,
I
did
not
specify
an
unattend.xml
or
other
customization
options
to
be
used
with
the
sysprep.
A
A
So
at
this
point
we're
done
with
this
template
virtual
machine.
We
have
installed
windows,
we've
sys
prepped
it
it's
ready
for
the
disk
to
be
used
for
additional
vms,
so
I'm
going
to
go
ahead
and
delete
the
virtual
machine.
However,
I
want
to
make
sure
to
uncheck
this
box
to
delete
the
disks,
along
with
the
virtual
machine
definition.
A
We
can
browse
to
our
storage
and
persistent
volume
claims.
When
we
look
at
these
pvcs,
we
see
two
additional
ones
that
were
just
created.
One
is
the
root
disk.
This
was
the
clone
of
our
iso
pvc.
We
can
go
ahead
and
remove
that
one.
The
other
one
is
the
server
2019
template
disk.
This
is
the
one
that
we
want
to
use.
This
one
will
be
used
for
the
image
of
any
additional
cloned
virtual
machines
based
off
of
the
disk.
A
The
next
step
is
going
to
be
creating
a
custom
template
for
our
virtual
machines.
Now
I
could
modify
this.
I
could
add
a
source
to
our
server
2019
vm
template
here.
What
will
happen
then
is:
I
will
choose
the
pvc
that
we
just
created
in
the
background
openshift
virtualization,
we'll
copy
that
data
we'll
clone
that
data
into
a
specific
namespace
into
the
os
image
template
namespace,
when
we
then
create
virtual
machines
based
off
of
that
template.
It
would
copy
that
data
into
the
new
disks
there's
nothing
wrong
with
this
process.
A
A
To
use
that
process,
we'll
select
the
three
dot
menu
over
here
and
we'll
select
create
new
template
from
for
our
windows.
Server,
2019
vm
template
we'll
give
our
template
a
name.
I'm
going
to
very
simply
call
this
temple
template
server,
2019
the
provider
here
I'm
going
to
provide
is
my
organization
name.
This
can
be
any
arbitrary
value.
A
We
do
want
to
keep
the
operating
system
set
to
server
2019.
However,
we
do
not
need
to
mount
the
windows
guest
tools.
We
did
that
when
we
installed
the
operating
system
before
next,
we'll
select
the
boot
source,
which
is
to
clone
an
existing
pvc,
and
we
will
select
the
pvc
that
we
created
a
moment
ago.
A
We
can
choose
a
default
flavor
to
be
used
with
this
template
along
with
workload
type,
I'm
not
going
to
modify
those.
We
can
modify
the
network
interface
that
will
be
associated
with
virtual
machines
created
for
the
template.
Again.
I
will
keep
this
connected
to
the
pod
network
and
my
disks.
I
will
keep
connected
a
20
gigabyte
disk
connected
to
the
lab
silver
storage
class.
A
At
this
point,
when
I
come
down
in
my
template
list,
I
see
we
see
we
have
this
template
server
2019.
That
was
just
created
this
time,
I'll
select
create
on
this
option.
This
will
create
a
virtual
machine
based
off
of
this
template,
we'll
change
the
name
here,
we're
using
notable
alligator
the
generated
name
and
from
here
we
simply
create
virtual
machine.
A
Now
the
reason
for
creating
the
template
that
way
was
so
that
we
could
do
csi
clones.
We
can
see
that
our
virtual
machine
is
already
up
and
running.
If
I
select
notable
alligator
here
and
I
select
the
console,
let
me
see
that
windows
is
booting
now
this
will
go
through
the
out-of-box
experience.
It's
going
to
set
up
a
few
things,
so
I'm
going
to
accelerate
this
first
boot
for
the
virtual.
A
A
Okay,
the
first
boot
is
complete.
We
now
complete
the
out
of
box
experience
for
windows
server.
2019
again,
you
could
choose
to
automatically
answer
these
using
an
unattend.xml
file.
If
you
wanted
to,
you
can
also
attach
that
unattend.xml
through
a
secret
or
a
config
map,
so
that
it
can
be
read
during
the
initial
setup
process.
You
can
attach
those
dynamically
when
the
virtual
machine
is
created.