HP t310 PCoIP Management Console User Manual - Page 14

DNS Server - zero client password

Page 14 highlights

PCoIP Management Console User Manual 1.1.2 PCoIP Management Console The management console for PCoIP protocol devices (MC) lets you centrally manage a PCoIP deployment. It lets you: • Access and update the configuration of your PCoIP devices • Apply the same configuration settings to groups of devices • Update device firmware • Reset devices • Control the power state of host devices that support power management • Power off zero client devices • View status information • Manage the monitoring of device event logs • Automatically configure newly discovered zero clients with a profile (optionally with firmware and OSD logo) based on device password, IP address and DHCP option values The MC is packaged as a VMware virtual machine (VM) and runs on VMware Player. This lets you install and run the MC on any host machine that can run VMware Player. You can also install and run the MC on any VMware ESX server. See section 2.4 for details on installing the MC into your existing VMware ESX server. A web browser is used to access and control the MC. The MC must be connected to the same network to which the PCoIP devices are connected. This lets the tool communicate with the PCoIP devices. Connection Broker A connection broker is an optional component that lets you manage user access to computing resources. Note that this component is not shown in Figure 1-1. In a PCoIP deployment, a connection broker is used to assign connections between PCoIP host and zero client devices. Deployments having the following requirement must install a connection broker: • hosts are dynamically assigned to zero clients based on the login credentials of the person using the zero client DNS Server Figure 1-1 shows a DNS server with the MC DNS SRV record. This component is optional, but highly recommended. The MC must discover the PCoIP host and zero client devices, and the MC DNS SRV record facilitates automatic device discovery. You can also install a connection broker DNS SRV record on the DNS server. PCoIP devices use this record to notify the connection broker of their existence. When a PCoIP device boots, it reads these records, which contain the addresses of the MC and/or connection broker. After reading the records, the device sends messages to the MC and/or connection broker notifying them of the devices existence. This ensures the MC and/or connection broker is aware of the devices in the deployment as they are powered on. The MC DNS SRV record is not required when one of the following conditions is true: • PCoIP DHCP Vendor Class Options are configured in the DHCP server. See section 1.3.3.2 for details on configuring these options. TER0812002 Issue 9 15

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87

PCoIP Management Console User Manual
TER0812002 Issue 9
15
PCoIP Management Console
The management console for PCoIP protocol devices (MC) lets you centrally manage a
PCoIP deployment. It lets you:
Access and update the configuration of your PCoIP devices
Apply the same configuration settings to groups of devices
Update device firmware
Reset devices
Control the power state of host devices that support power management
Power off zero client devices
View status information
Manage the monitoring of device event logs
Automatically configure newly discovered zero clients with a profile (optionally with
firmware and OSD logo) based on device password, IP address and DHCP option
values
The MC is packaged as a VMware virtual machine (VM) and runs on VMware Player. This
lets you install and run the MC on any host machine that can run VMware Player. You can
also install and run the MC on any VMware ESX server. See section 2.4 for details on
installing the MC into your existing VMware ESX server.
A web browser is used to access and control the MC.
The MC must be connected to the same network to which the PCoIP devices are connected.
This lets the tool communicate with the PCoIP devices.
Connection Broker
A connection broker is an optional component that lets you manage user access to computing
resources. Note that this component is not shown in Figure 1-1. In a PCoIP deployment, a
connection broker is used to assign connections between PCoIP host and zero client devices.
Deployments having the following requirement must install a connection broker:
hosts are dynamically assigned to zero clients based on the login credentials of the
person using the zero client
1.1.2
DNS Server
Figure 1-1 shows a DNS server with the MC DNS SRV record. This component is optional,
but highly recommended. The MC must discover the PCoIP host and zero client devices, and
the MC DNS SRV record facilitates automatic device discovery. You can also install a
connection broker DNS SRV record on the DNS server. PCoIP devices use this record to
notify the connection broker of their existence.
When a PCoIP device boots, it reads these records, which contain the addresses of the MC
and/or connection broker. After reading the records, the device sends messages to the MC
and/or connection broker notifying them of the devices existence. This ensures the MC and/or
connection broker is aware of the devices in the deployment as they are powered on.
The MC DNS SRV record is not required when one of the following conditions is true:
PCoIP DHCP Vendor Class Options are configured in the DHCP server. See section
1.3.3.2 for details on configuring these options.