Hi All,
I'd like to know what are all the places in a SAS environment that are tied up internally with the SAS installer account?
Would I be able to start/stop SAS services with installer account even after removing its identity from SAS metadata?
I'm trying to remove the installer account from everywhere within SAS except for start/stop of SAS services, is it possible to achieve?
Thanks!
IMHO, best practice is to use the SAS installer account just for installing and configuring and nothing else. Then have another SAS server account (often called sassrv) for running SAS servers, then a SAS admin account (often called sasadm) for administration. Of course things can be a bit more granular than that to suit your SAS site.
As a SAS administrator myself I don't have any problem just using my own account for manually starting and stopping services.
What is the reason for fiddling around with something that might possibly render your SAS installation inoperable?
Why do you use the installer account to stop and start services? Any account with admin privileges is able to do that.
IMHO, best practice is to use the SAS installer account just for installing and configuring and nothing else. Then have another SAS server account (often called sassrv) for running SAS servers, then a SAS admin account (often called sasadm) for administration. Of course things can be a bit more granular than that to suit your SAS site.
As a SAS administrator myself I don't have any problem just using my own account for manually starting and stopping services.
Thank you @SASKiwi and@AnandVyas for your suggestions, we are planning to remove SAS installer from metadata. For some reason, SAS installer account gets locked often from one of the test servers and that's the reason we're planning to have separate ones for prod and test.
@AnandVyas I'm curious to know if we could use other user accounts with admin privileges to start/stop services? (as suggested by @SASKiwi ).
Do you think doing so would cause any undesirable effects?
Thanks!
I haven't tried it myself as I was never in a scenario where there is a requirement to vault or not use the installer account to start/stop services. If @SASKiwi has done it successfully I am sure you can give it a try too!
Please be careful with permissions and users who start/stop services.
Lock/pid files and log files with different owners and permissions can cause those "undesirable" situations.
Good luck!
@SASWayne , I would say by default, it does, with the same account. However, perhaps design or installed had to decide otherwise. The best you can do is to check what account generated the logs/temp files for each daemon,
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.