You have your "network administrator" account set to log in for the Altiris Deployment Server DB Management and Altiris eXpress Server services for your GSS (Ghost Solution Suite) server.
You would like to know if you can change the "Log on as" section to the "Local System account", or "LOCAL SERVICE, NETWORK SERVICE, or Local Administrator".
Also, if this type of change will cause any issues with the services by swapping the "Log on as" account.
Questions:
1. With recent GSS 3.3 releases, is still true that the "Log On" account used to run these services (Altiris Deployment Server DB Management and Altiris eXpress Server services) needs to be a domain account with DB rights and to the database?
2. Is there a minimal permissions/privileges that the account should have?
GSS 3.3 RU12 or later
As background information:
Those 2 services (Altiris Deployment Server DB Management and Altiris eXpress Server services) are the main requirement for "valid" account is:
"The account has been added as a User in the Database"
Since those services need database access, we want to make sure the desired "Account" has valid User rights to our express database. You can see this KB article for Steps to add a user to the Ghost Solution Suite database
If the desired account doesn't have the proper rights to the database as mentioned above, it can cause the services to crash as described under KB article Service 'Altiris Deployment Server DB Management' crashing in Ghost Solution Suite
There is more details on what type of account you can use for GSS services in the documentation under Service Logon Account
You can also change your network administrator account to some other service logon account by using this documentation Symantec Ghost Solution Suite Server Configuration Utility under the "Account" section
This area has not changed recently, so the information provided under the "Cause" section above still remains valid.
If you need to change the service account, the account must have Administrator rights on the Ghost Solution Suite server and it also must be configured with appropriate permissions on the SQL Server: