Per product management:

Team,

There was some back and forth with product management and SUS and me on this.

Just want to clarify for team:

Customer WWE environment:  one gateway G300 (with NAS license) and 2 MDCs and MAC clients.

Customer implementing NAS with authentication to Active directory.

Customer joining MDCs to Active Directory domain.

Customer manipulating ACLS thru “snacl” command on gateway and MDC.

·         WWE has G300 NAS gateways that each require a NAS license, that is not in question

·         It is not a requirement to have a NAS license on the MDC to use G300 NAS gateways

·         It is also not a requirement to have their MDC bound to Active Directory to use G300 NAS gateways

·         They want to manipulate ACLs from their MDC for performance reasons which requires the MDC to be bound to AD, this is basically unrelated to NAS

·         The only supported way to bind the MDC to AD is with the NAS stack (NAS shell), which requires a license on MDC

·         A workaround that would not require a NAS license on the MDC is to manipulate the ACLs from the licensed G300 gateway which may be less performant than manipulating ACLs directly on the MDC