We are running SD4.5 SP12 and it doesn't appear that the system account can be change from a named user. I am setting up a seperate admin user that will be a concurrent user save on named users and I want to be able to re-use the named user license that system is using without deleting the default account.
System account should remain named. What if you have a problem that needs system account to log on with and all concurrents are taken?? Additional admin accounts may be concurrent but again it is advisable to have system admins as named.
I understand the intent of having it named, but didn't realize that when purchasing X named users, you really are only getting X-1 because the system account is taking up 1. Anytime you add more named users than you have licenses for, none of the named users can log into the WebConsole due to license usage rules. I haven't tested it out with the Client to see if they could login or not. We realized this when we first setup our accounts and setup the named users that we allocated to be and none of them could login to the WebConsole.
chapter 2 admin guide: Service Desk Administrator account. Each installation of the Service Desk application server must have at least one Service Desk administrator account. This administrator account has all the roles and authorization requirements to access every function of the Service Desk application. The Service Desk administrator does not count as one of your licensed users.
Well, I can't recreate the error in the WebConsole. OVSD will not even let you assign more named users than you have. When I saw the error in the WebConsole, I backed out one of the named users. All is well now.