|
|
|
■
|
Enabled. After being created, the desktop pool is enabled and ready for immediate use.
|
■
|
Disabled. After being created, the desktop pool is disabled and unavailable for use, and provisioning is stopped for the pool. This is an appropriate setting if you want to conduct post deployment activities such as testing or other forms of baseline maintenance.
|
|
Connection Server restrictions
|
■
|
None. The desktop pool can be accessed by any View Connection Server instance.
|
■
|
With tags. Select one or more View Connection Server tags to make the desktop pool accessible only to View Connection Server instances that have those tags. You can use the check boxes to select multiple tags.
|
|
Remote desktop power policy
|
Determines how a virtual machine behaves when the user logs off of the associated desktop.
|
Automatically logoff after disconnect
|
■
|
Immediately. Users are logged off as soon as they disconnect.
|
■
|
Never. Users are never logged off.
|
■
|
After. The time after which users are logged off when they disconnect. Type the duration in minutes.
The log off time applies to future disconnections. If a desktop session was already disconnected when you set a log off time, the log off duration for that user starts when you set the log off time, not when the session was originally disconnected. For example, if you set this value to five minutes, and a session was disconnected 10 minutes earlier, View will log off that session five minutes after you set the value.
|
|
Allow users to reset their desktops
|
Allow users to reset their own desktops without administrative assistance.
|
Allow multiple sessions per user
|
Allow a user to connect to multiple desktops in the pool at the same time.
|
Delete desktop after logoff
|
Select whether to delete floating-assignment, full virtual machine desktops.
■
|
No. Virtual machines remain in the desktop pool after users log off.
|
■
|
Yes. Virtual machines are powered off and deleted as soon as users log off.
|
|
Delete or refresh desktop on logoff
|
Select whether to delete, refresh, or leave alone floating-assignment, linked-clone desktops.
■
|
Never. Virtual machines remain in the pool and are not refreshed after users log off.
|
■
|
Delete immediately. Virtual machines are powered off and deleted as soon as users log off. When users log off, View Manager immediately puts virtual machines in a Deleting state.
|
■
|
Refresh immediately. Virtual machines are refreshed as soon as users log off. When users log off, View Manager immediately puts virtual machines in maintenance mode to prevent other users from logging in as the refresh operation begins.
|
|
Refresh OS disk after logoff
|
Select whether and when to refresh the OS disks for dedicated-assignment, linked-clone desktops.
■
|
Never. The OS disk is never refreshed.
|
■
|
Always. The OS disk is refreshed every time the user logs off.
|
■
|
Every. The OS disk is refreshed at regular intervals of a specified number of days. Type the number of days.
The number of days is counted from the last refresh, or from the initial provisioning if no refresh has occurred yet. For example, if the specified value is 3 days, and three days have passed since the last refresh, the desktop is refreshed after the user logs off.
|
■
|
At. The OS disk is refreshed when its current size reaches a specified percentage of its maximum allowable size. The maximum size of a linked clone's OS disk is the size of the replica's OS disk. Type the percentage at which refresh operations occur.
With the At option, the size of the linked clone's OS disk in the datastore is compared to its maximum allowable size. This disk-utilization percentage does not reflect disk usage that you might see inside the desktop's guest operating system.
|
When you refresh the OS disks in a linked-clone pool with dedicated assignment, the View Composer persistent disks are not affected.
|
|
Select the display protocol that you want View Connection Server to use to communicate with View clients.
|
The default option wherever it is supported. PCoIP is supported as the display protocol for virtual-machine desktops and physical machines that have Teradici hardware. PCoIP provides an optimized PC experience for the delivery of images, audio, and video content for a wide range of users on the LAN or across the WAN.
|
|
Microsoft Remote Desktop Connection (RDC) uses RDP to transmit data. RDP is a multichannel protocol that allows a user to connect to a computer remotely.
|
|
Allow users to choose protocol
|
Allow users to override the default display protocol for their desktops by using View Client.
|
|
You can select whether to enable 3D graphics rendering if your pool comprises Windows 7 desktops that run on vSphere 5.0 or later, PCoIP is the selected protocol, and the Allow users to choose protocolsetting is set to No.
With Windows 7 3D Rendering, users can take advantage of graphics enhancements that are provided by applications such as AERO, Microsoft Office 2010, and Google Earth.
If your View deployment does not run on vSphere 5.0 or later, this setting is not available and is inactive in View Administrator.
When you select this feature, you can configure the amount of VRAM that is assigned to desktops in the pool. You can select at most two monitors for your View desktops. The maximum resolution of any one monitor is set to 1920x1200 pixels. You cannot configure this value.
Note
You must power off and on existing virtual machines for this setting to take effect. Restarting a virtual machine does not cause the setting to take effect.
|
|
If you use PCoIP as the display protocol, you can select the maximum number of monitors on which users can display the desktop.
When the Windows 7 3D Rendering setting is not selected, the Max number of monitors setting affects the amount of VRAM that is assigned to desktops in the pool. When you increase the number of monitors, more memory is consumed on the associated ESX hosts.
When the Windows 7 3D Rendering setting is selected, you can select at most two monitors.
Note
You must power off and on existing virtual machines for this setting to take effect. Restarting a virtual machine does not cause the setting to take effect.
|
Max resolution of any one monitor
|
If you use PCoIP as the display protocol and you do not select the Windows 7 3D Rendering setting, you should specify the maximum resolution of any one monitor.
When the Windows 7 3D Rendering setting is not selected, the Max resolution of any one monitorsetting affects the amount of VRAM that is assigned to desktops in the pool. When you increase the resolution, more memory is consumed on the associated ESX hosts.
When the Windows 7 3D Rendering setting is selected, you cannot change the maximum resolution of any one monitor. The resolution is set to 1920x1200 pixels.
Note
You must power off and on existing virtual machines for this setting to take effect. Restarting a virtual machine does not cause the setting to take effect.
|
|
Determines the quality of Adobe Flash content that is displayed on Web pages.
■
|
Do not control. Quality is determined by Web page settings.
|
■
|
Low. This setting results in the most bandwidth savings. If no quality level is specified, the system defaults to Low.
|
■
|
Medium. This setting results in moderate bandwidth savings.
|
■
|
High. This setting results in the least bandwidth savings.
|
|
|
Determines the frame rate of Adobe Flash movies. If you enable this setting, you can reduce or increase the number of frames displayed per second by selecting an aggressiveness level.
■
|
Disabled. No throttling is performed. The timer interval is not modified.
|
■
|
Conservative. Timer interval is 100 milliseconds. This setting results in the lowest number of dropped frames.
|
■
|
Moderate. Timer interval is 500 milliseconds.
|
■
|
Aggressive. Timer interval is 2500 milliseconds. This setting results in the highest number of dropped frames.
|
|
No comments:
Post a Comment