This shows you the differences between two versions of the page.
|
es:zoo:virtualdesktop [2017/05/04] |
es:zoo:virtualdesktop [2020/08/14] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ======Rhino y la virtualización de escritorio====== | ||
| + | > **Product: | ||
| + | > **Summary: | ||
| + | =====Question===== | ||
| + | Our school is using Microsoft [[http:// | ||
| + | |||
| + | =====Answer===== | ||
| + | Technically, | ||
| + | |||
| + | Rhino should also run in VDI environments if installed as a network-node, | ||
| + | |||
| + | Rhino 4.0, however, will not run in VDI environments. | ||
| + | |||
| + | That said, __we cannot make a recommendation__ on whether or not you should run Rhino in this manner, as we (McNeel) neither test nor use Rhino in a VDI environment. | ||
| + | |||
| + | Rhino is a CPU, memory, and graphics-intensive application. Imagine logging onto your own computer 5, 10, 20 or even 30 times and trying to run Rhino in each logon session. | ||
| + | |||
| + | Our customers have reported mixed results running Rhino in VDI environments. Some say that Rhino' | ||
| + | |||
| + | Clearly, your results will vary depending on the products and technologies your organization has chosen to implement. | ||
| + | |||
| + | If you are considering running Rhino in a VDI environment, | ||
| + | |||
| + | When you finish your testing, please share your results with our [[tech@mcneel.com|technical support]] staff. We are interested in hearing about your experience. | ||
| + | |||
| + | \\ | ||
| + | |||
| + | {{tag> | ||