Remote Access Type

Description

What to Know

Requirements

Local Network Connection 

(Not Remote)

Ansys clients are located on the same network as the license server.  This is the standard, non-remote method used.

• This is the standard deployment method

• Allow applications/ports through the windows firewall
• Clients must be on the same network as the license server.

VPN 

(most common remote connection)

A VPN allows someone from home or a remote location to connect to their office network, where their Ansys license server is located.

• Requires IT Expertise to Setup
• Can be unreliable or disconnect periodically depending on how it's implemented and or the reliability of connections.  This can cause long solves to be interrupted. 
• Ideal for users who travel to different locations.

• VPN Connection setup by your IT Department.

Borrowing a License‍ 

Borrowing a license allows you to use Ansys software without accessing the license server.  

• You can only borrow a license for up to 30 days at a time and a maximum of 90 days per year.
• The user who borrows a license has exclusive access to it during the period they check it out for.  
• Identifying what specific licenses/features you require to borrow can be tricky. 
• Checking out over a VPN or unreliable, high latency connections can be slow, fail or get stuck mid process.

• License must be enabled as a borrowable license. (term "borrowable" must be listed in the license file)
• The client must connect to the license server to borrow and to return licenses before the checkout date expires.

Public Facing License Server‍ 

• Allows your license server to be used by any IP address you specify, anywhere on the internet, without a VPN.  
• This option is required when using Ansys Cloud Bring Your Own Licensing (BYOL).

• Requires  IT Expertise to Setup
• Security is controlled by allowing client via their public IP address.  Home IP's can  change and can require frequent updates to firewall rules.
• Workable solution for Cloud VM's hosted on AWS, Azure, etc., with a small user base.
• Not ideal when you have many Ansys clients needing to connect due to IP's changing.
• Not practical for users who are "road warriors" who travel to new locations often. 

• A public domain with the ability to add an A record/subdomain.
• A public static IP address that you can configure to point traffic to your license server.
  • Obtainable for ~$5/mo from your ISP.
• A public static IP address that your Ansys client will be connecting from.
  • Obtainable for ~$5/mo from your ISP.
• A firewall that can forward traffic to your license server from only specified IP addresses.

Remote Desktop over VPN

Connect to a computer located on your corporate network. 

• Performance is dependent on connection speed and reliability.

• VPN Connection setup by your IT Department.
• Dedicated computer located on your corporate network 
• Another computer your connecting from when remote.
• Remote computer must have RDP enabled.

3rd Party Remote Desktop Software

Software such as TeamViewer, SplashTop, GoToMyPC, LogMeIn, and other 3rd party solutions can be used as remote desktop tools.

• Performance is dependent on software and connection speed and reliability.

• Setup 3rd party software
• Company IT policies must approve this

Ansys Cloud Essentials

Ansys Cloud Essentials is a pay-per-use product that allows you to perform your entire workflow in the cloud.  

• Prep/Post work is performed in a Cloud VDI environment (via browser or RDP client) and Solves are performed in the cloud VM dedicated to solving.
• More information - https://www.ansys.com/products/platform/ansys-cloud

• Ansys Cloud Essentials Subscription
• Ansys Hardware Currency (AHC)
• Ansys Elastic Currency (AEC)