The SAS installer account is also used to start basic services, where it is often necessary to be the owner of certain files. Since the account was used during installation, this is guaranteed.
So, basically, one SAS installation -> one SAS installer account.
To separate between a test and prod environment, you do not need separate SAS installations (unless you also physically separate the SAS servers), but you use separate definitions of contexts in a single metadata environment.
The SAS installer account is also used to start basic services, where it is often necessary to be the owner of certain files. Since the account was used during installation, this is guaranteed.
So, basically, one SAS installation -> one SAS installer account.
To separate between a test and prod environment, you do not need separate SAS installations (unless you also physically separate the SAS servers), but you use separate definitions of contexts in a single metadata environment.
If your company requires this kind of (totally unnecessary, believe me) separation, you best run two separate servers.
Keep in mind that this would force you to have two installations in parallel, including the web application stack. How you keep those two running without interfering with each other (on Windows, to boot!), I have no idea.
Get some real IT people whose brains have not been burned through by prolonged exposure to crapware (Windows).
Mind that the installer account is not used to run SAS software (with the exception of the metadata server and the web application infrastructure).
Workspace servers are run with the logged-in user's account, pooled servers (e.g. stored process servers) with sassrv. These are relevant security-wise.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.