Can we use gMSA account to run AEM application as windows as a service

Hi,

We are running AEM 6.5 on-premises as a Windows Service, and the service is currently configured to run under the Local System account.

We have a new requirement for the AEM application to access a shared folder located outside the AEM server. As part of enabling the necessary permissions, we have been advised to run the AEM Windows Service using a gMSA (Group Managed Service Account) instead of the Local System account.

Has anyone implemented this approach for AEM running as a Windows Service? Is using a gMSA considered a recommended or standard approach for accessing network resources such as shared folders?

Additionally, I would appreciate guidance on:

• Any prerequisites or permissions required before making the change.
• The steps involved in configuring the AEM Windows Service to run under a gMSA account.
• Any potential risks or considerations when applying this change to production AEM instances.
• Whether there are any AEM-specific considerations when moving from Local System to a gMSA account.

Thank you for any advice or experience you can share.