Professional Documents
Culture Documents
P Cubed R2
Horizon Suite
Quick Start Guide
Version 1.92
July 2013
P Cubed Horizon Quick Start Guide
Virtual
SAN
• Pivot3_VM
is
Pivot3
Storage
Virtual
Appliance
| | www.pivot3.com July 2013 | 4
P Cubed Horizon Quick Start Guide
The
Pivot3_
VM
contains
the
vSTAC
operating
system
(vSTAC
OS)
provides
an
intuitive
appliance
approach
as
it
manages
data
distribution
across
Pivot3
vSTAC
Appliances
to
provide
scalable
availability,
performance
and
capacity.
The
vSTAC
OS
runs
on
each
appliance
to
aggregate
the
physical
resources
of
the
appliances,
automatically
load
balance
across
the
appliances
and
protect
against
component
failures.
Advanced
disk
protection
from
the
vSTAC
OS
includes
RAID
1p,
RAID
5e,
RAID
6e
and
RAID
6x:
-‐ With
RAID
5e,
one
disk
failure
or
one
appliance
failure
will
not
affect
data
-‐ With
RAID
1p
and
RAID
6e,
up
to
3
simultaneous
disk
failures
will
not
affect
data
-‐ RAID
1p
and
RAID
6e
also
protects
data
in
the
case
of
an
entire
appliance
failure
and
up
to
1
drive
failure
-‐ With
RAID
6x,
up
to
5
simultaneous
disk
failures
will
not
affect
data
-‐ RAID
6x
also
protects
data
in
the
case
of
an
entire
appliance
failure
and
up
to
2
drive
failures
As
with
any
centralized
resource,
it
is
important
that
the
data
stored
be
available
and
accessible.
The
Pivot3
storage-‐centric
approach
for
application
environments
characterized
by
high-‐capacity
needs
and
I/O-‐intensive
workloads
offers
higher
performance,
lower
cost
and
higher
availability
than
traditional
alternatives.
P
Cubed
is
preconfigured
for
storage,
and
ready
to
scale
out
with
the
addition
of
vSTAC
VDI
appliances.
-‐ Infrastructure
LUN
of
600GB
at
RAID
6,
scaling
out
to
6e.
-‐ Replica
LUN
of
300GB
at
RAID
1,
scaling
out
to
1p.
-‐ Desktop
LUN
of
over
2
TB
at
RAID
1,
scaling
out
to
1p.
-‐ WorkspaceData
LUN
of
1TB
at
RAID
6,
scaling
out
to
6e.
-‐ MirageCache
LUN
of
110
GB
at
RAID
1,
scaling
out
to
1p.
-‐ MirageStorage
LUN
of
2TB
at
RAID
6,
scaling
out
to
6e.
Infrastructure
Services
• AD01
provides
Microsoft
Active
Directory,
DHCP,
DNS,
and
DNS
forwarding.
• ManagementStation
includes
vSTAC
Manager,
and
is
a
handy
VM
to
manage
the
infrastructure
with
Pivot3
and
VMware
tools.
vSTAC
Manager
is
the
configuration
and
management
software
for
Pivot3
STACs.
The
ManagementStation
provides
NAT
and
SMTP
roles
for
POC
deployments.
Horizon
View
• vCenter
is
VMware
Virtual
Center
for
Virtual
Desktops
The
vCenter
Server
is
a
server
that
acts
as
a
central
administrator
for
ESX/ESXi
hosts
that
are
connected
on
a
network.
A
vCenter
Server
provides
the
central
point
for
configuring,
provisioning,
and
managing
virtual
machines
in
the
datacenter.
View
Composer
is
installed
as
a
software
service
on
the
vCenter
to
allow
VMware
View
to
rapidly
deploy
multiple
linked-‐clone
desktops
from
a
single
centralized
base
image.
• ViewConnection
is
VMware
View
Connection
Server
The
VMware
View
Connection
server
is
a
software
service
that
acts
as
a
broker
for
client
connections
by
authenticating
and
then
directing
incoming
user
requests
to
the
appropriate
virtual
desktop.
• Golden_Desktop
is
reference
desktop
for
Windows
7
The
Virtual
Desktop
has
a
View
Agent
that
is
a
software
service
that
is
installed
on
all
guest
virtual
machines
in
order
to
allow
them
to
be
managed
by
VMware
View.
Horizon
Workspace
• gateway-‐va
is
the
endpoint
for
all
end-‐user
communication.
User
requests
come
to
the
gateway-‐
va,
which
then
routes
the
request
to
the
appropriate
virtual
appliance.
• service-‐va
provides
access
to
the
administrator
web
interface,
from
which
users,
groups,
and
resources
may
be
managed.
• connector-‐va
provides
services
for
user
authentication,
directory
synchronization,
ThinApp-‐
catalog
loading,
and
Horizon
View
pool
synchronization.
• data-‐va
controls
file
and
folder
sharing
between
users
and
stores
users’
files.
• configurator-‐va
serves
as
the
configuration
virtual
appliance,
providing
configuration
changes
to
the
rest
of
the
Workspace
vApp.
Horizon
Mirage
• MirageMgmt
contains
the
Mirage
Management
Server
and
Mirage
Management
Console
The
management
server
controls
and
manages
the
mirage
server
cluster.
The
management
console
is
the
user
interface
for
the
management
server.
• MirageServer
provides
the
Mirage
Server
The
Mirage
Server
controls
all
Mirage
operations
and
objects.
It
manages
desktop
images,
centralized
virtual
desktops
(CVDs),
base
layers,
and
application
layers
in
the
datacenter.
The
Mirage
Sever
has
a
local
cache
for
commonly
used
data
blocks.
Network
Configuration
P
Cubed
has
six
Network
Interface
Card
(NIC)
ports.
The
physical
NICs
for
vmnic0
and
vnmic1
auto-‐
negotiate
from
1
to
10
Gigabit
Ethernet.
The
physical
NICs
for
vmnic2
through
vmnic5
are
1
Gigabit
Ethernet.
vmnic4
is
the
VMware
management
network.
The
NIC
allows
connections
for
vSphere
Client
and
a
path
to
the
ManagementStation.
vmnic
2
may
be
used
for
redundancy
of
the
management
network.
Vmnic3
is
to
be
connected
to
the
customer’s
production
network.
The
NIC
allows
access
to
the
View
Connection
server.
vmnic5
may
be
used
for
redundancy
of
the
production
network.
vmnic0
and
vmnic1
are
unused
by
a
P
Cubed
POC
deployment.
Scaling
the
system
with
additional
vSTAC
VDI
appliances
will
require
usage
of
vmnic0
and
vmnic1
for
redundant
iSCSI
Storage
Networks.
Quick
Start
1. Installation
(Refer
to
Installation
on
page
11)
Unbox
Connect
networks
Power
on
2. Network
Resolution
(Refer
to
Network
Resolution
on
page
11.)
Quick
Reference
User
Name
/
Passwords
Component
Username
Password
vSTAC
ESXi
Host
root
vSphereP3
vSTAC
Storage
Admin
Administrator
(upper
case)
Pivot3!
Pivot3_VM
setip
p3setip
pivot3
ManagementStation
Pcube.local\administrator
Pivot3!
Domain
Account
for
vCenter
Pcube.local\administrator
Pivot3!
SQL
Account
for
vCenter
SSO
Admin
Account
admin@System-‐Domain
vCenter
Account
for
View
Domain
Account
to
Install
View
Domain
Account
for
View
Composer
SQL
Login
for
View
Composer
Mirage
Services
Acct
Bind
DN
user
Horizon
Workspace
Connector
admin
admin_pass
Horizon
Workspace
Console
root
root_pass
Horizon
Workspace
domain
admin
HorizonAdmin@pcube.local
HAdminpass
Active
Directory
admin
External
DB
admin
ViewUsers
viewuser1,
viewuser2,
…
viewuser5
viewuser
Networks
DHCP
Addresses
that
are
written
in
below
were
assigned
by
AD01
and
are
on
the
P
Cubed
Network,
and
noted
here
for
your
convenience.
ESXi
Host
Licensing
Windows
Server
Licenses
–
You
have
been
provided
3
DVD’s
containing
the
license
keys
for
Windows
Server
2008
R2
Standard
Edition.
Each
Windows
Key
has
a
Physical
and
Virtual
Key.
You
are
allowed
to
use
the
virtual
key
on
two
separate
virtual
machines.
The
VM’s
that
need
to
be
licensed
are
AD01,
vCenter,
ViewConnection,
Management
Station,
MirageServer,
and
MirageMgmt.
VMware
Horizon
Suite
–
A
60
day
evaluation
of
VMware
Horizon
Suite
100
pack
is
provided.
A
license
email
will
be
sent
to
the
customer
point-‐of-‐contact.
The
evaluation
period
will
begin
upon
license
registration.
Windows
7
-‐-‐
The
Golden_Desktop
image
is
a
Windows
7
Enterprise
90-‐day
Trial.
The
trial
period
begins
upon
activation.
The
Golden_Desktop
has
been
supplied
unactivated.
Microsoft
Virtual
Desktop
Access
–
VDA
lets
use
access
virtual
desktops
from
Software
Assurance
covered
PCs.
Refer
to
Appendix
A:
Document
References
for
a
link
with
more
information.
Network
Resolution
1. After
vSphere
ESXi
completes
booting,
press
F2.
Login
with
root
/
vSphereP3.
2. Configure
the
management
port
based
on
the
management
network;
use
DHCP
or
set
a
static
address.
Return
to
the
main
screen.
Make
a
note
of
this
management
IP
address.
3. On
a
computer
connected
to
the
management
network
launch
vSphere
Client.
Connect
to
the
appliances
management
IP
address.
Login
as
root.
4. The
vSphere
Client
will
show
the
loaded
VMs.
5. Right
click
on
the
icons
to
Power
Up
each
VM
in
the
following
order.
a. ManagementStation
b. AD01
c. vCenter
| | www.pivot3.com July 2013 | 11
P Cubed Horizon Quick Start Guide
d.
ViewConnection
e.
MirageMgmt
f.
MirageServer
g.
Do
NOT
power
up
VMs
labeled
“prod-‐“.
These
are
preconfigured
VMs
without
Horizon
software
installed.
The
“prod-‐“
will
have
the
same
default
IPs
as
the
non
prod-‐
versions,
so
duplicate
IPs
will
result
if
this
warning
is
not
heeded.
6. Open
the
console
for
the
ManagementStation.
Login
with
the
pcube\administrator
account.
7. The
Production
Network
adapter
has
three
static
IP
addresses.
a. The
first
address,
default
of
.150,
allows
access
to
the
ManagementStation
server.
RDP
is
enabled.
This
address
provides
a
NAT
uplink
for
desktop
and
server
VMs
on
the
P
Cubed
Network.
b. The
second
address,
default
of
.151,
provides
external
NAT
access
for
the
View
Connection
Server.
c. The
third
address,
default
of
.152,
provides
external
NAT
access
for
the
Horizon
Gateway.
8. Obtain
3
static
IP
addresses
from
the
customer’s
production
network.
Throughout
the
rest
of
this
section
the
.150,
151,
and
.152
addresses
will
be
changed
to
these
new
static
production
network
IP
addresses.
Record
the
new
addresses
in
the
Quick
Reference
network
table
in
this
document.
a. The
first
address
(.150
by
default)
is
the
RDP/NAT
address.
b. The
second
address
(.151
by
default)
is
the
View
Connection
NAT.
c. The
third
address
(.152
by
default)
is
the
Horizon
Gateway
NAT.
9. Use
Control
Panel
Network
and
Sharing
Center
Change
Adapter
Settings
then
open
Properties
for
the
Production
Network.
10. Select
Internet
Protocol
Version
4
and
click
Properties.
11. Click
the
Advanced
button,
then
IP
settings
tab
.
12. Highlight
each
IP
address
and
click
edit.
Change
each
IP
address
and
subnet
mask
to
the
static
production
network
IP
addresses
obtained
in
step
8.
13. Change
the
default
gateway.
14. Click
Start
Administrative
Tools
Routing
and
Remote
Access.
a. On
the
left
pane,
navigate
to
Routing
and
Remote
Access
ManagementStationIPv4NAT
b. On
the
right
pane,
right
click
Production
Network
and
select
PropertiesServices
and
Ports
i. Select
each
Horizon
service
and
click
Edit.
1. Change
the
“On
this
address
pol
entry”
IP
address
to
the
static
production
network
IP
addresses
obtained
in
step
8.
c. On
the
right
pane,
right
click
Production
Network
and
select
PropertiesAddress
Pool.
i. Click
Add…
and
add
the
address
range
for
the
static
production
network
IP
addresses
obtained
in
step
8.
15. Open
the
console
for
vCenter
and
log
in
as
above
in
step
6,
and
set
the
IPv4
address
for
the
Management
Network.
16. Open
the
Console
for
AD01
and
log
in.
Open
DNS.
Navigate
to
AD01Forward
Lookup
ZonespCube.local.
Edit
the
IP
address
for
pCubeESXi
to
match
the
appliance
management
IP
address.
17. In
each
VM
console
you
opened
above,
open
a
command
prompt.
Type
ipconfig
/flushdns.
From
the
ManagementStation
ensure
that
pcubeesxi.pcube.local
answers
a
ping.
Note
that
the
Windows
Server
VMs
will
not
answer
pings
due
to
firewall
protection.
vCenter
Licensing
1. The
ManagementStation’s
desktop
has
four
preconfigured
programs
installed
and
their
icons
have
been
put
as
shortcuts
on
the
desktop.
A
brief
explanation
of
each
is:
a. Pivot3
vSTAC
Manager
is
Pivot3’s
storage
management
software.
b. VMware
View
Client
will
be
used
to
connect
to
the
View
Connection
server.
c. VMware
vSphere
Client
will
be
used
to
connect
to
the
vCenter
server.
d. Microsoft
Internet
Explorer
has
its
homepage
set
to
connect
to
the
View
Administrator
console.
2. Open the vSphere Client and connect to vcenter.pcube.local. Use the administrator account.
3. Navigate
to
HomeAdministrationLicensing.
Click
on
Manage
vSphere
Licenses…
4. Refer to your VMware email for the Horizon Suite Evaluation Pack of 100 users.
5. Enter
licenses
for
VMware
vSphere
5
Enterprise
Plus
for
Desktop,
and
VMware
vCenter
Server
5
Standard
for
View
5.
7. In
Assign
Licenses,
under
the
vCenter
Server
tab,
click
the
button
to
assign
vCenter
Server
5
Standard
license.
Add
Host
1. Next,
from
ManagementStation,
navigate
back
to
Hosts
and
Clusters,
right
click
on
the
pCube
datacenter.
Choose
Add
Host…
2. In
Connection
enter
in
pcubeesxi.pcube.local,
for
Authorization
specify
the
root
login/password.
Click
Next.
3. Choose
Yes
when
the
Security
Alert
prompts.
5. In
Assign
Licenses,
under
the
ESX
tab,
click
the
button
to
assign
the
VMware
vSphere
5
Desktop
Host
license.
9. vCenter
will
now
have
pcubeesxi
and
the
P
Cubed
VMs
attached.
License
AD01
1. Right
click
on
ADO1
and
choose
Open
Console
2. Log
in
to
windows
using
u/p
administrator/Pivot3!
3. Until
DHCP
has
been
disabled
on
AD01,
do
not
place
it
on
the
production
network
with
internet,
as
this
might
make
it
a
Rogue
DHCP
server.
5. Once
DHCP
is
open
right
click
ad01.pcube.local
and
choose
All
Tasks
-‐>
Stop
| | www.pivot3.com July 2013 | 32
P Cubed Horizon Quick Start Guide
7. Click
Add
8. Click
Ethernet
Adapter
then
Next
10. Determine
Network
connection:
a. If
the
Management
Network
is
the
network
that
is
connected
to
the
internet
click
Next.
b. Otherwise
from
the
Network
Label
choose
Production
Network
from
the
Dropdown
if
that
is
the
network
that
is
connected
to
the
Internet.
11. Click
Next
then
Finish.
12. You
will
see
the
following
while
the
network
card
is
being
added
to
your
VM
13. Click
Ok
14. You
will
see
a
message
similar
to
the
following
once
the
Ethernet
Adapter
has
been
added
to
windows.
15. If
the
network
that
has
internet
is
has
a
DHCP
server
associated
with
it
then
this
NIC
will
grab
an
ip
address
and
you
should
be
able
to
register
windows
per
normal.
16. Once
Windows
has
been
activated
we
are
going
to
reverse
the
process
we
just
did.
17. Click
VM
edit
settings
18. Locate
the
Network
card
that
is
on
your
Internet
Network,
in
this
case
it
is
the
VM
Network,
Click
Remove
19. Your
network
card
will
look
like
this
until
you
click
ok.
20. Click
Ok
21. Now
that
your
connection
to
the
outside
network
has
been
removed,
turn
DHCP
back
on.
Open
DHCP,
right
click
ad01.pcube.local,
click
All
Tasks
-‐>
Start
22. DHCP
is
ready
when
IPv4
&
6
both
show
green
check
marks
23. Close
DHCP
2. Log
in
to
windows
using
u/p
administrator/Pivot3!
3. While
it
completes
the
log
in,
click
VM
-‐>
Edit
Settings
4. Click
Add
6. Change
Type
from
E1000
to
VMXNET
3
b. Otherwise
from
the
Network
Label
choose
Production
Network
from
the
Dropdown
if
that
is
the
network
that
is
connected
to
the
Internet.
8. Click
Next
then
Finish.
9. You
will
see
the
following
while
the
network
card
is
being
added
to
your
VM
10. Click
Ok
11. You
will
see
a
message
similar
to
the
following
once
the
Ethernet
Adapter
has
been
added
to
windows.
12. If
the
network
that
has
internet
is
has
a
DHCP
server
associated
with
it
then
this
NIC
will
grab
an
ip
address,
otherwise
please
give
it
a
static
IP
address.
You
should
be
able
to
register
windows
per
normal.
13. Once
Windows
has
been
activated
we
are
going
to
reverse
the
process
we
just
did.
14. Click
VM
edit
settings
15. Locate
the
Network
card
that
is
on
your
Internet
Network,
in
this
case
it
is
the
VM
Network,
Click
Remove
16. Your
network
card
will
look
like
this
until
you
click
ok.
17.
18. Click
Ok;
this
will
finalize
the
removal
of
the
NIC.
Repeat
these
steps
for
any
additional
Servers
that
need
to
be
licensed.
2. Login
to
VMware
View
Administrator
with
the
pcube/administrator
account.
3. Navigate to View Configuration Product Licensing and Usage. Click Edit License…
4. Locate
the
VMware
View
5.x
license
from
the
VMware
license
email.
Enter
it
in
the
prompt.
5. Verify that the evaluation license is enabled for View Composer.
6. Navigate to View Configuration Servers. Highlight the VIEWCONNECTION server and click Edit…
7. Under
the
General
tab,
set
the
PCoIP
Secure
Gateway
‘s
External
URL
to
the
IP
address
of
the
ViewConnection
server’s
Production
NIC.
This
address
is
the
8. Under
HTTP(s)
Secure
Tunnel,
uncheck
“Use
Secure
Tunnel…”
9. Under
PCoIP
Secure
Gateway,
check
“Use
PCoIP
Secure
Gateway…”
Click
OK.
2. Choose
Automated
Pool,
click
Next.
3. Choose
Floating,
click
Next.
4. Choose
View
Composer
linked
clones,
click
Next.
6. Leave
defaults,
select
Next.
7. Set
Naming
Pattern:
to
sample-‐{n},
set
Max
number
of
desktops
and
Number
of
spare
(powered
on)
desktops
to
5,
or
a
size
of
your
choice.
8. Leave
defaults,
click
Next.
.
9. Check Select Separate datastores for replica and OS disk, and click next.
10. In
Add
Pool,
select
Browse
for
the
Parent
VM:
11. Select the Golden_Desktop in the pop-‐up window and then click ok.
12. In
Select
default
image,
select
the
SampleDesktop
snapshot.
14. In
Virtual
Machine
Folder
Location,
choose
Desktops.
Click
Ok.
15. Browse
for
Host
or
cluster.
16. Select
pcubeesxi.pcube.local,
click
OK.
18. Select
pcubeesxi.pcube.local.
Click
OK.
20. Check
Desktops,
choose
Aggressive
for
Storage
Overcommit
.
Click
Ok
21. Browse
for
Replica
disk
datastores.
22. Choose
Replicas
Datastore.
Click
Ok.
23. Add
Pool
vCenter
Settings
should
now
look
as
follows,
click
Next.
24. Leave
Advance
Storage
Options
settings
as
Default,
click
Next.
26. Browse
and
select
OU=ViewDesktops.
Click
Ok.
27.
In
Ready
to
Complete,
compare
your
configuration
to
the
next
three
screen
shots.
Use
Back
if
you
need
to
make
changes.
Place
a
Check
in
Entitle
users
after
this
wizard
finishes,
and
then
click
Finish.
29. In
Find
User
or
Group,
uncheck
Users
and
in
Name/User
name
type
“view”,
and
hit
Find.
Select
ViewUsers.
30. In
Entitlements
ViewUsers/PCube.local.
Click
OK.
This
will
return
you
back
to
the
View
Administrator
Pools
screen.
View
Client
1. The
SampleDesktop
pool
should
now
be
active.
Launch
the
VMware
View
Client
from
the
desktop
shortcut.
Specify
viewconnection.pcube.local,
click
Connect.
2. Click
Continue.
3. Specify
a
viewuser
account.
For
example,
viewuser1.
Click
Login.
5. The
desktop
session
will
now
launch.
3. In
Device
Type,
select
Ethernet
Adapter,
click
Next.
4. In
Network
connection,
set
Type:
to
VMXNET3.
Set
Network
connection
to
either
VM
Network
or
Production
Network.
This
is
a
network
external
to
P
Cubed
and
must
have
a
DCHP
server.
5. In
Ready
to
Complete,
click
Finish.
6. Right click on the Golden_Desktop, click on Power, Power On.
7. Login
to
the
Golden_Desktop
with
the
pcube/administrator
account.
9. Select
Activate
Windows
online
now.
10. Wait
for
Windows
Activation
to
complete.
11. The
Windows
7
desktop
should
now
indicate
in
the
lower
right
corner
that
the
Windows
License
has
been
activated
for
90
days.
12. Make
any
additional
customization
settings
desired.
This
can
include
loading
applications,
configuring
application
settings,
changing
Windows
settings,
and
installing
Windows
Updates.
Perform
and
Windows
reboots
necessary.
These
settings
will
remain
valid
through
the
90
day
Windows
evaluation
period.
13. From
the
Windows
Start
menu,
shutdown
Windows.
14. On the open console, navigate to VMSnapshot, click Take Snapshot…
15. In
Take
Virtual
Machine
Snapshot
provide
a
unique
name
for
the
snapshot.
The
example
screens
will
use
Activated
Image.
Click
OK.
16. On
the
open
console,
navigate
to
VMSnapshot,
click
Snapshot
Manager…
This
will
display
the
Golden_Deskstop’s
snapshot
history.
The
Activated
Image
snapshot
is
indicate
as
“You
are
here”.
Click
Close.
17. In
the
ManagementStation,
start
Internet
Explorer.
Login
to
View
Adminstrator
with
the
pcube/administrator
account.
Navigate
to
InventoryPools,
click
on
the
SampleDesktop
in
the
ID
column.
18. Select
ViewComposerRecompose.
19. In
Image,
select
Change.
21. In
Image,
highlight
the
new
snapshot.
In
the
example
screens
it
is
named
LicenseActivation.
Click
Next.
22. In
Scheduling,
click
Next.
23. In
Ready
to
Complete,
click
Finish.
The
SampleDesktop
pool
will
now
be
recomposed
to
the
new
snapshot.
24. Monitor
the
vCenter
task
bar
for
progress
and
completion.
25. In
the
ManagementStation,
start
Internet
Explorer.
Login
to
View
Adminstrator
with
the
pcube/administrator
account.
Navigate
to
InventoryPools,
click
on
the
SampleDesktop
in
the
ID
column.
27. Under
the
Provisioning
Settings
tab,
set
Max
Number
of
desktops
and
Number
of
spare
(powered
on)
desktops.
Click
OK.
28. Monitor
the
vCenter
task
bar
for
progress
and
completion.