‎May 16, 2021 04:38 AM
As stated by Chris, you can use any account to run the Scheduled Tasks, as long as it has the same Windows access and DB Access. In effect, you may as well use the Service Account. It must be a full Admin to the Windows Server, it must have the Local Security Policy to run as a batch job, and it needs DBO access to the FNMS databases.
‎May 17, 2021 06:12 AM
As far as I know, the Microsoft Task Scheduler as used by FlexNet Manager Suite has a hard dependency on the "Network access: Do not allow storage of passwords and credentials for network authentication" policy setting being disabled. I haven't looked for some time, but I know in the past I was not able to find any way around that.
You might consider using some other scheduling tool to run scheduled tasks and batch processes instead of using Microsoft Task Scheduler. Scheduling tools other than the Microsoft tool may be considered more acceptable from a security perspective. Regardless of what tool is used, it will somehow need to store a user identity to run batch process. You would need to manage configuration of tasks in your tool of choice to ensure it runs similar tasks to what the FlexNet Manager Suite configuration process automatically configures in Microsoft Task Scheduler for you.
‎May 19, 2021 02:33 AM
Scheduled tasks can generally be run using any account with appropriate rights - this could be the FlexNet Manager Suite service account itself, or another account with the same rights if you had some reason you didn't want to use the service account itself.
‎May 16, 2021 08:55 PM
As stated by Chris, you can use any account to run the Scheduled Tasks, as long as it has the same Windows access and DB Access. In effect, you may as well use the Service Account. It must be a full Admin to the Windows Server, it must have the Local Security Policy to run as a batch job, and it needs DBO access to the FNMS databases.
‎May 17, 2021 06:12 AM
‎May 17, 2021 09:51 AM
If that security policy is enabled, then the installation of the Scheduled Tasks will fail. It is a requirement for this specific policy to be disabled.
On the FNMS Server, you must disable this policy. If you have an Active Directory policy that forces this to be enabled, then you must create an exception to this policy for the FNMS Server.
‎May 17, 2021 09:56 AM
‎May 17, 2021 09:29 PM
As far as I know, the Microsoft Task Scheduler as used by FlexNet Manager Suite has a hard dependency on the "Network access: Do not allow storage of passwords and credentials for network authentication" policy setting being disabled. I haven't looked for some time, but I know in the past I was not able to find any way around that.
You might consider using some other scheduling tool to run scheduled tasks and batch processes instead of using Microsoft Task Scheduler. Scheduling tools other than the Microsoft tool may be considered more acceptable from a security perspective. Regardless of what tool is used, it will somehow need to store a user identity to run batch process. You would need to manage configuration of tasks in your tool of choice to ensure it runs similar tasks to what the FlexNet Manager Suite configuration process automatically configures in Microsoft Task Scheduler for you.
‎May 19, 2021 02:33 AM
‎May 17, 2021 09:54 AM
‎May 17, 2021 09:56 AM
@nagaeendra - in relation to the kudos, another user has given kudos on some of the posts in this thread, but as you have noted you have not marked kudos on any posts. I can't see anything that has happened automatically or incorrectly there.
In relation to the solution, the post marked as a solution is an accurate and correct answer to the question raised by this thread. I expect a moderator of this forum has marked it as the solution to the question to help the next person who has the same question.
‎May 17, 2021 07:46 PM