AWS license-manager documentation change
Summary
Added troubleshooting sections for Microsoft RDS Licensing failures and Microsoft Office activation failures, including VPC connectivity requirements and CAL management guidance
Security assessment
Changes address operational troubleshooting of licensing mechanisms and network connectivity requirements, but do not indicate any security vulnerabilities or weaknesses being patched. The guidance focuses on proper configuration rather than security protections.
Diff
diff --git a/license-manager/latest/userguide/user-based-subscriptions-troubleshoot.md b/license-manager/latest/userguide/user-based-subscriptions-troubleshoot.md index 6380ded68..8d52ec740 100644 --- a//license-manager/latest/userguide/user-based-subscriptions-troubleshoot.md +++ b//license-manager/latest/userguide/user-based-subscriptions-troubleshoot.md @@ -5 +5 @@ -Troubleshoot instance complianceTroubleshoot license complianceTroubleshoot instance connectivityTroubleshoot failures to join the domainTroubleshoot Systems Manager connectivityTroubleshoot Systems Manager Run Command +Troubleshoot instance complianceTroubleshoot license complianceTroubleshoot instance connectivityTroubleshoot failures to join the domainTroubleshoot Systems Manager connectivityTroubleshoot Systems Manager Run CommandTroubleshoot Microsoft RDS Licensing failuresTroubleshoot Microsoft Office activation failures @@ -24,0 +25,4 @@ The following are troubleshooting tips to help solve issues that can occur with + * [Troubleshoot Microsoft RDS Licensing failures](./user-based-subscriptions-troubleshoot.html#usubs-troubleshoot-rds-licensing) + + * [Troubleshoot Microsoft Office activation failures](./user-based-subscriptions-troubleshoot.html#usubs-troubleshoot-office-activation) + @@ -59,0 +64,21 @@ Run Command, a capability of Systems Manager, is used with instances providing u +## Troubleshoot Microsoft RDS Licensing failures + +If you experience issues with CAL (Client Access License) issuance, check whether there are additional Microsoft RDS licensing servers present in your server farm or Terminal Servers group. We do not recommend having additional licensing servers in these locations, as that can interfere with CAL issuance and lead to licensing complications. + +To resolve this issue, ensure that only the intended Microsoft RDS servers remain in your server farm and Terminal Servers group. + +When troubleshooting licensing issues, be aware that connections using the /admin flag bypass standard licensing checks, as this flag is intended for administrative purposes, and doesn't consume a CAL. This can mask underlying licensing problems. To diagnose licensing issues, verify that standard user connections (without the /admin flag) are functioning correctly for license management. + +## Troubleshoot Microsoft Office activation failures + +If Microsoft Office activation fails, verify that your instance has access to the VPC that's defined for License Manager. Either of the following options satisfies this requirement: + + * Your instance is running in the VPC that's onboarded with License Manager (through VPC endpoint) + + * Your instance is running in a VPC that's peered with the License Manager onboarded VPC. + + + + +To resolve this issue, ensure that your instance is moved to the correct VPC, or establish VPC peering with the License Manager onboarded VPC. +