Client infra team is telling to install Orch on the server with my personal id .t There is a service account which has access to the database. We told installation should be done using the service account too since the app pool identity settings will by default take my account details and once I am rolled off , my ID would be inactive and this will put the entire application at stake.Am i right in this understanding? Is there a vendor document to support the same ? Can orchestrator installation take place without the service account access with admin rights to the app server ?
Hi!
Is this in regards to the Orchestrator Database Settings, or the Application Pool Settings?
I can’t think of a good reason to deviate from the default/standard path described in this document:
Orchestrator - The Windows Installer
Sorry, I read your post again 
Here’s some documentation regarding installation of the SQL database.
Seems like a strange requirement from the Client Infra Team.
You could install with your own account, but then change to a service account afterwards, but that’s just more work than simply installing with a service account.