Some of our customers are making the move over to a Virtual Desktop environment. While the Connect application itself is developed with the individual machine in mind, it can function in a virtual space. Here are some things to consider when preparing to implement Connect in your virtual environment:
System Requirements:
Whether on a physical machine or on a virtual desktop, you must meet our system requirements:
You should also consider Adobe's best practice recommendations, as this will effect our ability to work within these applications
Persistent vs. Non-persistent
Persistent: The Virtual Desktop persists through being shut down. When the user logs into it next, everything should be as it was when they last logged in. Akin to how a physical desktop would persist
Non-persistent: The Virtual Desktop is dissolved upon shut down, with a brand new Virtual Desktop created each time the user logs in. Connect was not designed to work in non-persistent environments
Shared Resources
Virtual Desktops all run off a shared pool of CPU cores, RAM, and disk space. Some environments even share registries (like if multiple people were using the same computer). When our application activates fonts it does so directly with the Windows Registry, causing problems if multiple people are accessing it simultaneously
Where folks using an individual machine would need to wait their turn, virtual environments allow for multiple logins to the same instance. This will interfere with the basic mechanics of our application and is not recommended
Permissions
Connect is designed with local storage in mind, or via Connect's own integrated cloud storage (check out our TrueEdit feature!). That being said some customers successfully work with files stored in a network location. While access is largely managed internally within your organization, some things to consider are:
- How restrictive are your user permissions for network folders?
- Do you have any group policies preventing file/folder access for both locations storing main files and linked files?
- Network Security Applications that could prevent Connect's access to network locations (see our file/folder exclusions list: Antivirus, Malware & Cleaning Application Exclusions)
If you have further questions or need additional assistance please contact Technical Support