Local Network Connection 

(Not Remote)

• This is the standard deployment method

• Add Firewall Exceptions for Ansys License Manager‍ 
• Clients must be on the same network as the license server.

VPN 

(most common remote connection)

• 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.

• Add Firewall Exceptions for Ansys License Manager‍ 
• VPN Connection setup by your IT Department.

• 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 via local network to borrow and to return licenses before the checkout date expires.  (VPN or Public facing connection to the license server can work, but is not recommended)

• 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. 

• HOW TO - Make your Ansys License Server Public
• 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.

• Does not require you to setup a license server.
• Your license has to be issued as a Shared Web License.
• If you have a classic FlextNet license, you will have to work with your account manager to migrate to this licensing model.

• Supports 2023R2 or Later
• View this article for more info and a product support list
  INFO - Ansys Shared Web Licensing Overview 

• 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.

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

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

• 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)