We have a Terminal Server running 2012R2 with an Access-based program installed using Access Runtime2k3. We are noticing that when users execute the program for the first time, the program runs through an automated first time configuration, after which the user is prompted to restart the system to complete the setup. If the user clicks No, the program opens and runs fine, but if they click Yes, the entire server restarts.
We need to find a way to prevent the users from being able to restart the server as this would completely interrupt other users that are logged in. We have already modified several Group Policy settings to prevent users access to Shutdown and Restart options, as well as prevent them from opening the Run dialogue box. We have also modified Local Policies of the Server to specify that only administrators have the ability to shut down the server, however, when this program runs the first time configuration and prompts the user for a restart, it seems to get around all of that.
Is there some other GPO setting that would completely prevent a system from being restarted by a standard user, even if the restart is initiated from a program that the user has access to? Is there a way to possibly prevent the program from prompting for user input? The users have a desktop shortcut that points to a .adp file so I'm thinking some kind of quiet switch /q or something that could follow this and prevent user input we could possibly try?