Can FluidFlow be Installed on Microsoft Azure?

This article addresses common questions about using FluidFlow licenses on Azure Virtual Desktop (AVD) environments and clarifies licensing requirements for virtual desktop deployments.

Can one FluidFlow license be used simultaneously on both a physical desktop and Azure Virtual Desktop?

No.

FluidFlow uses concurrent user licensing, which means one license permits one concurrent user at any given time. A single license cannot be used to run FluidFlow simultaneously on both a physical desktop and an AVD session. When a user accesses FluidFlow through one method (desktop or AVD), the license is occupied until they close the application.

Are there specific licensing requirements for Azure Virtual Desktop installations?

No. FluidFlow's standard licensing terms apply to AVD deployments. There are no special license agreements, rules, or separate licenses required specifically for AVD installations. AVD is simply treated as another delivery method for accessing FluidFlow, similar to any other network installation.

How FluidFlow Works on Azure Virtual Desktop

Installation Process

1. License Server Setup

   • Install FluidFlow on a Windows Server VM within your Azure environment (either in your AVD deployment or a dedicated VM) or on an on-premises server if network connectivity is robust and reliable.

   • Select "Network server" during installation to configure the license server correctly.

   • Activate the license using the FluidFlow License Manager.

2. Network Configuration

   • Share the necessary FluidFlow installation folders with appropriate read/write permissions for users.

   • Configure network paths on the AVD session hosts to point to these shared folders.

   • Ensure proper network connectivity and firewall rules allow communication between AVD session hosts and the license server.

3. AVD Session Host Configuration

   • Install the FluidFlow client on AVD session host VMs. Alternatively, you can create shortcuts to the network installation executable directly on the session hosts.

   • Users will access FluidFlow via these shortcuts, which launch the application from the network location.

Concurrent User Management

FluidFlow's concurrent licensing model works seamlessly with AVD's multi-session capabilities:

• Multiple users can share the same AVD VM and access FluidFlow.

• License tracking occurs irrespective of the access method (physical desktop or virtual AVD session).

• When users log off their AVD session or close FluidFlow, licenses are immediately released and become available for other users.

Benefits for AVD Deployments

• Cost Efficiency: AVD's multi-session capability can reduce the number of virtual machines required, while FluidFlow's concurrent licensing model optimizes license utilization.

• Flexibility: Users can access FluidFlow from any device (desktop, laptop, tablet) through AVD, providing remote and flexible work options.

• Centralized Management: Both FluidFlow licenses and AVD resources are managed centrally, simplifying administration and maintenance.

• Scalability: AVD can automatically adjust capacity based on user demand, ensuring FluidFlow is always available when needed.

Important Considerations

• Network Connectivity: Ensure reliable and low-latency network connectivity between AVD session hosts and the FluidFlow license server. Poor connectivity can lead to performance issues or license access problems.

• License Count: Plan your concurrent license count based on your projected peak user sessions, not the total number of users who might potentially access FluidFlow.

• Geographic Proximity: Consider network latency if your AVD deployment and the FluidFlow license server are located in different geographical regions. Ideally, they should be co-located or have a high-speed, dedicated connection.

• Documentation: Standard FluidFlow network installation documentation and best practices apply to AVD deployments. Refer to these resources for detailed setup instructions.

Compliance and Software Asset Management

For organizations conducting Software Asset Management (SAM) reviews:

• Usage Tracking: FluidFlow licensing is based on concurrent usage, not the number of installations. Focus your SAM efforts on tracking peak concurrent users.

• Documentation: Document your peak concurrent user requirements and how they align with your FluidFlow license purchase.

• Standard Terms: Apply standard FluidFlow licensing terms to your AVD environments. No additional or special licensing documentation is required for virtual deployments.

Need More Information?

For specific licensing questions or to discuss your AVD deployment requirements in detail, please contact our sales team at sales@fluidflowinfo.com