Administration

For example, the average desktop takes two to three minutes to start. Therefore, the concurrent power
operations limit should be 3 times the peak power-on rate. The default seing of 50 is expected to support a
peak power-on rate of 16 desktops per minute.
The system waits a maximum of ve minutes for a desktop to start. If the start time takes longer, other errors
are likely to occur. To be conservative, you can set a concurrent power operations limit of 5 times the peak
power-on rate. With a conservative approach, the default seing of 50 supports a peak power-on rate of 10
desktops per minute.
Logons, and therefore desktop power on operations, typically occur in a normally distributed manner over a
certain time window. You can approximate the peak power-on rate by assuming that it occurs in the middle
of the time window, during which about 40% of the power-on operations occur in 1/6th of the time window.
For example, if users log on between 8:00 AM and 9:00 AM, the time window is one hour, and 40% of the
logons occur in the 10 minutes between 8:25 AM and 8:35 AM. If there are 2,000 users, 20% of whom have
their desktops powered o, then 40% of the 400 desktop power-on operations occur in those 10 minutes. The
peak power-on rate is 16 desktops per minute.
Accept the Thumbprint of a Default SSL Certificate
When you add vCenter Server and View Composer instances to View, you must ensure that the SSL
certicates that are used for the vCenter Server and View Composer instances are valid and trusted by View
Connection Server. If the default certicates that are installed with vCenter Server and View Composer are
still in place, you must determine whether to accept these certicates' thumbprints.
If a vCenter Server or View Composer instance is congured with a certicate that is signed by a CA, and
the root certicate is trusted by View Connection Server, you do not have to accept the certicate
thumbprint. No action is required.
If you replace a default certicate with a certicate that is signed by a CA, but View Connection Server does
not trust the root certicate, you must determine whether to accept the certicate thumbprint. A thumbprint
is a cryptographic hash of a certicate. The thumbprint is used to quickly determine if a presented certicate
is the same as another certicate, such as the certicate that was accepted previously.
N If you install vCenter Server and View Composer on the same Windows Server host, they can use the
same SSL certicate, but you must congure the certicate separately for each component.
For details about conguring SSL certicates, see "Conguring SSL Certicates for View Servers" in the View
Installation document.
You rst add vCenter Server and View Composer in View Administrator by using the Add vCenter Server
wizard. If a certicate is untrusted and you do not accept the thumbprint, you cannot add vCenter Server
and View Composer.
After these servers are added, you can recongure them in the Edit vCenter Server dialog box.
N You also must accept a certicate thumbprint when you upgrade from an earlier release and a
vCenter Server or View Composer certicate is untrusted, or if you replace a trusted certicate with an
untrusted certicate.
On the View Administrator dashboard, the vCenter Server or View Composer icon turns red and an Invalid
Certicate Detected dialog box appears. You must click Verify and follow the procedure shown here.
Similarly, in View Administrator you can congure a SAML authenticator for use by a View Connection
Server instance. If the SAML server certicate is not trusted by View Connection Server, you must determine
whether to accept the certicate thumbprint. If you do not accept the thumbprint, you cannot congure the
SAML authenticator in View. After a SAML authenticator is congured, you can recongure it in the Edit
View Connection Server dialog box.
View Administration
22 VMware, Inc.