Commit 65ed721f authored by mseng3's avatar mseng3
Browse files

Updated readme to reflect the move from the engrit-epm-public group to the engrit-epm group.

parent f1a2446e
Pipeline #178156 canceled with stages
......@@ -17,7 +17,7 @@ The purpose of this repo is to host scripts that will be downloaded and used on
## Rules
<a name="rules"/>
1. Don't keep scripts here which will not be used in SCCM TSes. If they are strictly SCCM/TS-related but won't be used in the TS, give them their own new project under the [engrit-epm](https://gitlab.engr.illinois.edu/engrit-epm) or [engrit-epm-public](https://gitlab.engr.illinois.edu/engrit-epm-public) group. Alternatively, contribute them to the [Official EngrIT Script Repo](https://gitlab.engr.illinois.edu/oesr).
1. Don't keep scripts here which will not be used in SCCM TSes. If they are strictly SCCM/TS-related but won't be used in the TS, give them their own new project under the [engrit-epm](https://gitlab.engr.illinois.edu/engrit-epm), or contribute them to the [Official EngrIT Script Repo](https://gitlab.engr.illinois.edu/oesr).
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.
4. Scripts which have associated text/config files should go in their own directory, named after the script if possible.
......@@ -152,7 +152,7 @@ The examples above rely on the following custom task sequence variables and loca
* Copy `x:\engrit` to `c:\engrit`
* `EngrIT_LogsGoHere` = `c:\engrit\logs`
* `EngrIT_ScriptsGoHere` = `c:\engrit\scripts`
* `EngrIT_TSRepo` = `https://gitlab.engr.illinois.edu/engrit-epm-public/sccm-ts-scripts`
* `EngrIT_TSRepo` = `https://gitlab.engr.illinois.edu/engrit-epm/sccm-ts-scripts`
### Example Task Sequence
<a name="example-ts"/>
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment