Considerations

The following considerations apply when utilizing user-based subscriptions with License Manager:

• Win Remote Desktop Services SAL licenses can't be used separately from the supported user-based subscription products.

• Instances that provide user-based subscriptions support up to two active user sessions at a time.

• When you create local users with administrator privileges on instances that provide user-based subscriptions, the instance's health status might change to unhealthy. License Manager can terminate instances that are unhealthy for non-compliance. For more information, see Troubleshooting instance compliance.

• To stop incurring charges for user-based subscriptions, you must disassociate the user from all instances they are associated with. For more information, see Disassociating users from user-based subscriptions.

• When you configure your directory with Microsoft Office products, your VPC must have VPC endpoints provisioned in at least one subnet. If you want to remove all VPC endpoint resources created by License Manager, you must perform the following actions:

  • Disassociate all users from their user-based subscriptions. For more information, see Disassociating users from user-based subscriptions.

  • Remove any directory that is configured from the License Manager settings. For more information, see Removing a directory for user-based subscriptions.

  • Terminate all instances providing user-based subscription products. For more information, see Terminating EC2 instances providing user-based subscriptions.

• The tag key of AWSLicenseManager with the value of UserSubscriptions assigned by License Manager to your instances must not be altered or deleted.

• The two Elastic Network Interfaces (ENIs) created for License Manager must not be altered or deleted for the service to function.

• The objects that License Manager creates in the AWS Managed Microsoft AD directory's AWS Reserved organizational unit (OU) must not be altered or deleted.

• The instances deployed for user-based subscriptions must be managed nodes with AWS Systems Manager and joined to the same domain. For information on keeping your instances managed by Systems Manager, see the Troubleshooting user-based subscriptions section of this guide.