Home » HP Manuals » Desktops » HP t310 » Manual Viewer

HP t310 PCoIP Management Console User Manual - Page 30

Installation and Setup

Add to My Manuals
Save this manual to your list of manuals

Page 30 highlights

PCoIP Management Console User Manual 2 Installation and Setup This section describes how to install and set up the MC. It also describes how to migrate from an old version of the MC to a new version. 2.1 Management Console host System Requirements The MC server machine must meet the requirements of the virtualization environment that the MC VM will run in. • The MC server machine must meet the requirements of the VMware Player. For a VMware Player installation, see the VMware Player documentation (http://www.vmware.com/pdf/vmware_player250.pdf) for the most up-to-date requirements. The current requirements are: o Standard x86-compatible or x86-64-compatible PC o Processor speed-733 MHz or faster o Memory-512 MB minimum, 2 GB recommended. You must have enough memory to run the host operating system, the virtual machine, and applications on the host and guest operating systems. o Hard disk-At least 1 GB of free disk space for each guest operating system. For installation, VMware Player requires approximately 250 MB (Windows) or 200 MB (Linux) of free disk space. • The MC server machine CPU requirements differ based on the number of PCoIP devices managed. If the MC manages less than 1000 devices, the server machine CPU should be a 2 GHz or faster Intel Pentium 4 or better processor. If the MC manages 1000 or more devices the server machine CPU should be an Intel Core™2 Duo Processor or better. • The MC virtual machine is configured to use 640 MB of RAM. For best performance, the server machine should have at least 1 GB of RAM to avoid excessive swapping. • The MC server machine must have 4 GB of available disk space to accommodate the virtual machine's disk image. 2.2 Contents of the Management Console Package The zip file contains the following files: • Teradici_PCoIP_Management_Console_Agreement.pdf: Teradici PCoIP Management Console ("Software") license file • PCoIP_MC_relA-B-C_vDEF.vmx: Teradici PCoIP Management Console VMware configuration file for the virtual machine that hosts the management console • PCoIP_MC_relA-B-C_vDEF.vmdk: Teradici PCoIP Management Console VMware virtual disk file containing the virtual machine's hard drive. The size of this file increases as the MC is used. The maximum size of the file is 4 GB. • README.txt: file describing the contents of the zip file • TER0812002_Issue_X-PCoIP_Management_Console_User_Manual.pdf: Teradici PCoIP Management Console User Manual, where X is the current issue number TER0812002 Issue 9 31

Section	Page
Revision History	3
Contents	5
Table of Figures	8
Tables	10
Definitions	11
Introduction	12
About this Document	12
1 Overview	13
1.1 PCoIP Deployment Components	13
1.1.1 Managing PCoIP Devices	13
Device Web Interface	13
PCoIP Management Console	14
Connection Broker	14
1.1.2 DNS Server	14
1.1.3 DHCP Server	15
1.2 Management Console Limitations	15
1.3 Management Console Concepts	16
1.3.1 Groups and Profiles	16
1.3.2 Fixed Seating	17
1.3.3 Device Discovery	18
1.3.3.1 Installing a DNS Service Record on the DNS Server	19
1.3.3.2 Configuring DHCP Vendor Class Options on the DHCP server	20
1.3.3.3 PCoIP Management Console DNS-Based Discovery Prefix	23
System Requirements	23
Algorithm	23
Example	24
1.3.3.4 Manual Device Discovery	24
1.3.4 AutoConfig	25
1.4 Management Console and Firmware Version Compatibility	27
2 Installation and Setup	30
2.1 Management Console host System Requirements	30
2.2 Contents of the Management Console Package	30
2.3 Installing the Management Console using VMware Player	31
2.4 Installing the Management Console into your Existing VMware ESX™ server	31
2.5 Running the Management Console	31
2.6 Migrating to a New Version of the Management Console	32
2.6.1 Potential Problems and Workarounds	32
2.6.2 What Information is Imported	33
2.6.3 Database Migration Procedure	33
3 Virtual Machine Features	35
3.1 Refresh Status	35
3.2 Set Web Interface Password	35
3.3 Change hostname	35
3.4 Manage Networking	36
3.4.1 View Network Configuration	36
3.4.2 Configure IP Address	36
3.4.3 Configure DNS	37
3.5 Database Management	37
3.5.1 Back Up Database	38
3.5.2 Restore Database	38
3.5.3 Delete Database	38
3.6 Change Time Zone	39
3.7 Restart Management Console Daemon	39
3.8 Halt Virtual Machine	39
4 Web Interface	40
4.1 Accessing the Management Console Web User Interface	40
4.1.1 Installing the MC Certificate in Internet Explorer	41
4.1.2 Installing the MC Certificate in Firefox	41
4.1.3 Logging into the MC Web User Interface	42
4.1.4 Accepting the MC License Agreement	42
4.1.5 Using the MC Home Page	43
4.2 Device Management	44
4.2.1 Device Discovery (optional)	45
4.2.2 Legend	45
4.2.3 Querying Devices and Update Database	47
4.2.4 Filtering Devices	47
4.2.5 Configuring a Device Group	48
4.2.6 Linking Devices	49
4.2.7 Access Device Webpage	50
4.2.8 Deleting Devices	51
4.2.9 Summary Device Information	51
4.2.10 Configure Device Name	51
4.2.10.1 Access Device Details	52
4.2.10.2 Delete Device from Management Console Database	52
4.2.10.3 View Device Event Log	52
4.2.11 Device Details	52
4.2.11.1 Device Configuration and Status	53
4.2.11.2 Refresh Device Settings Stored in Management Console	54
4.2.11.3 Write Profile Settings to Device	54
4.2.11.4 Open Device Profile	54
4.2.11.5 Access Device & Peer Webpages	54
4.2.11.6 View Device Log	54
4.3 Group Management	55
4.3.1 Manage Groups	56
4.3.1.1 Create a Group	56
4.3.1.2 Modify a Group	56
4.3.1.3 Delete a Group	56
4.3.1.4 Profile Application Status	56
4.3.1.5 Apply a Profile to a Group	57
4.3.2 View Profile Application Status	58
4.3.3 Manage AutoConfig	59
4.3.4 Persistent AutoConfig	61
4.3.5 View AutoConfig Status	63
4.3.5.1 View Status Information	63
4.3.5.2 Retry AutoConfig	64
4.3.5.3 Apply AutoConfig	64
4.4 Profile Management	64
4.4.1 Create a Profile	65
4.4.2 Duplicate a Profile	65
4.4.3 Delete a Profile	65
4.4.4 Modify Profile Name & Description	65
4.4.5 Modify Profile Properties	66
4.4.5.1 OSD Logo in a Profile	67
4.4.5.2 Firmware in a Profile	67
4.4.5.3 Certificates in a Profile	68
4.4.6 Import a Profile	68
4.4.7 Export a Profile	69
4.5 Power Management	69
4.5.1 Sending Reset and Power off Commands	69
Reset Commands	70
Power Off Commands	70
4.5.2 Power Management Status	71
4.5.3 Schedule Remote Power Down	72
4.5.4 View Remote Power Down Status	74
4.6 Update Firmware	74
4.6.1 Import Firmware	75
4.6.2 Update Device Firmware	75
4.6.3 View Status	77
4.7 Device Log Monitoring	78
4.7.1 Device Tree	78
4.7.2 Logging Controls	78
4.7.3 Status	79
4.8 Manage Settings	79
4.8.1 Database Management	79
Uploading a Database	80
Downloading a Database	80
4.8.2 Environment Settings	80
4.8.3 Manage Device Naming	81
4.9 Site Status	81
4.10 Online Help	83
5 Getting Started	84
5.1 Start the Management Console	84
5.2 Discover Devices	84
5.3 Adding Devices to a Group	84
5.4 Peering Devices	85
5.5 Configuring Zero Clients for VMware View	86

Match case Limit results 1 per page

PCoIP Management Console User Manual

TER0812002 Issue 9

Installation and Setup

This section describes how to install and set up the MC. It also describes how to migrate from

an old version of the MC to a new version.

2.1

Management Console host System Requirements

The MC server machine must meet the requirements of the virtualization environment that

the MC VM will run in.

•

The MC server machine must meet the requirements of the VMware Player. For a

VMware Player installation, see the VMware Player documentation

(http://www.vmware.com/pdf/vmware_player250.pdf) for the most up-to-date

requirements. The current requirements are:

Standard x86-compatible or x86-64-compatible PC

Processor speed–733 MHz or faster

Memory–512 MB minimum, 2 GB recommended. You must have enough

memory to run the host operating system, the virtual machine, and applications

on the host and guest operating systems.

Hard disk–At least 1 GB of free disk space for each guest operating system. For

installation, VMware Player requires approximately 250 MB (Windows) or 200

MB (Linux) of free disk space.

•

The MC server machine CPU requirements differ based on the number of PCoIP

devices managed. If the MC manages less than 1000 devices, the server machine

CPU should be a 2 GHz or faster Intel Pentium 4 or better processor. If the MC

manages 1000 or more devices the server machine CPU should be an Intel Core™2

Duo Processor or better.

•

The MC virtual machine is configured to use 640 MB of RAM. For best

performance, the server machine should have at least 1 GB of RAM to avoid

excessive swapping.

•

The MC server machine must have 4 GB of available disk space to accommodate the

virtual machine’s disk image.

2.2

Contents of the Management Console Package

The zip file contains the following files:

•

Teradici_PCoIP_Management_Console_Agreement.pdf: Teradici PCoIP

Management Console (“Software”) license file

•

PCoIP_MC_relA-B-C_vDEF.vmx: Teradici PCoIP Management Console VMware

configuration file for the virtual machine that hosts the management console

•

PCoIP_MC_relA-B-C_vDEF.vmdk: Teradici PCoIP Management Console VMware

virtual disk file containing the virtual machine's hard drive. The size of this file

increases as the MC is used. The maximum size of the file is 4 GB.

•

README.txt: file describing the contents of the zip file

•

TER0812002_Issue_X-PCoIP_Management_Console_User_Manual.pdf: Teradici

PCoIP Management Console User Manual, where X is the current issue number