What is the most suitable path on Windows workstations to store admin scripts? [closed]

Posted on

What is the most suitable path on Windows workstations to store admin scripts? [closed] – Managing your servers can streamline the performance of your team by allowing them to complete complex tasks faster. Plus, it can enable them to detect problems early on before they get out of hand and compromise your business. As a result, the risk of experiencing operational setbacks is drastically lower.

But the only way to make the most of your server management is to perform it correctly. And to help you do so, this article will share nine tips on improving your server management and fix some problem about windows, group-policy, filesystems, scripting, file-permissions.

We have a need for a GPO to store admin scripts locally on Windows workstations (7 and above), and I was wondering if Microsoft has any recommendations or if you have any experience or thoughts on which path would be most suitable to store such scripts? I have searched the net for a recommendation but have been unsuccessful so far.

I realize that this might be a bit unusual, but it is for managing wireless connections on laptops before users log on hence the need to store the scripts locally.

Edit (additional info from comments): Creating a C:scripts and creating a new folder in C:users were both proposed and rejected. Creating a folder inside C:userspublic was not outright rejected, but does not seem ideal. The essence of my question is where does it make the most sense to store these script files?

Solution :

There is no per-defined location, but as your admin does not want a created path on the c:, like c:script I suggest using %programfiles%UnivercityNAME, that way if someday you deploy new application or script, it’s a location easy to give to your user to execute them.

As talked I don’t recommend in the user profile, as it’s a policy to be run on as a computer script.

A list of good documented variable exist there: https://technet.microsoft.com/en-ca/library/cc749104%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396

In practice make a hidden folder off of C: called C:$admin.000

I am not aware of a way to restrict the access such that the user would be able to run the scripts located therein, but not be able to read them, or list the contents of the folder. Of course, in *nix, that is a non-issue.

There is no standard or recommendation. Whatever you choose, you probably want to consider the following:

  • easy to remember
  • documented
  • backed up
  • possibly added to a PATH env var.

Leave a Reply

Your email address will not be published.