Frequently Asked Questions¶
Can I use a screensaver?¶
Yes. However, a blank, static screensaver will provide the most efficient CPU and network bandwidth usage.
Why can't I use the maximum number of monitors or monitor resolution?¶
GPU profile licensing, GPUs, or clients may limit monitor resolution and monitor count, which will prevent you from utilizing the full agent specification. For more information, see supported displays.
Which graphics rendering APIs are supported?¶
The Graphics Agent captures and delivers the output from the GPU, which is responsible for providing rendering APIs like OpenGL. See the documentation for your GPU for more information about rendering APIs.
How quickly does a Anyware agent complete a connection?¶
Anyware agents can usually achieve a connection in 15 to 30 seconds. We use the statistical value Top Percentile (TP) to measure the time to establish a session:
- TP99: Ninety-nine percent of connections complete in under 30 seconds.
- TP50: Fifty percent of connections complete in under 15 seconds.
Why is my application not sending audio?¶
The Anyware agent delivers audio over PCoIP connections by reassigning the system's default audio device. Only applications that use the system default audio device will send or receive audio over PCoIP; applications that are configured to use non-default devices will not work. If you don't hear audio from your application, make sure it is configured to use the system default audio device.
I'm using Anyware Cloud Licensing. What network blocks should I leave open?¶
If you are using Anyware Cloud Licensing, you will need to add the following to your allowlist:
- teradici.flexnetoperations.com
- teradici.compliance.flexnetoperations.com
If you use an IP-based allowlist, we recommend your IT team add the following network blocks to your allowlist:
-
IPv4: 185.146.155.64/27
-
IPv6: 2620:122:f005::/56
Important: Migrating from the previous specification
Previously, our allowlist specification looked like this:
- Production: 64.14.29.0/24
- Disaster Recovery: 64.27.162.0/24
If you have an existing implementation using an IP-based allowlist like this, we recommend you leave it in place until the new allowlist is active and tested.