@@ -21,7 +21,7 @@ The purpose of this repo is to host scripts that will be downloaded and used on
2. Name scripts in all lowercase, with dashes for word separators, preferably using the `verb-noun[-noun].ext` convention.
3. This repo is for version control of text-based scripts and configuration files. Don't upload non-text files such as images, or other dependencies such as executables. Keep those on \\\\engr-wintools, or package them in SCCM.
4. Scripts which have associated text/config files should go in their own directory, named after the script if possible.
4. This repo is public. Don't contribute scripts which have confidential information. See the [Securing Credentials](#creds) section below for info on how to use credentials in TSes and scripts.
4. This repo is public. *DO NOT* contribute scripts which have confidential information. See the [Securing Credentials](#creds) section below for info on how to use credentials in TSes and scripts.
5. Powershell scripts are preferred. It's really quite easy to translate batch scripts to Powershell, and they will be much cleaner and more flexible.
The examples above rely on the following custom task sequence variables and local directories. The variables aren't strictly necessary, and you can replace them in the above code with hard-coded paths if you're a masochist.
The examples above rely on the following custom task sequence variables and local directories. The variables aren't strictly necessary, and you can replace them in the above code with hard-coded paths... if you're a masochist.