How do you create a scheduled task (Task Scheduler) on Windows Server 2019 that requires the use of either NT/System or a group managed service account (gmsa)? (These accounts do not have user account profiles). I am faced with increased IT security requirements for which we no longer are allowed to store credentials on the server for performing tasks and the use of ArcGIS Pro / Python 3.x in a concurrent licensing option (which we are provided) only appears to work for an account for which licensing is established and the user has opened ArcGIS Pro. When I first set up arcgis PRO on server with a standard service account, after configuring licensing I was able to get scripts to run in task scheduler. This makes sense as the full context of licensing and security access is available. However, I am forbidden to store credentials for this task, so the task must be run while the user is logged on and the login secession must be maintained for the service account. This is problematic as IT has also instigated a new automatic policy that requires servers to be rebooted weekly. When this automatic reboot happens, the login session is terminated and when the server (virtual) is brought back online, tasks no longer run.#
It would be extremely beneficial for ESRI to provide users a context on common pitfalls and how to utilize the full arcpy and arcgis libraries on servers that have checked out licenses (concurrent) for accounts that may not have user profiles.
Scripts typically use python arcpy and/or arcgis libraries (ArcGIS Pro 2.5.1 or 2.6.0)
Perhaps unrelated, I also notice a severe degradation (4-10x slower) of running python scripts through SQL Job agent now that I have upgraded from 2.x to 3.x.
Please note this thread is a variant of Python 3.x Scheduled Task Fails . Review of this thread indicates that further clarification is needed.