Content Naming Convention Guide
SCCM Naming Conventions
Everything added to SCCM needs to include the unit name as a prefix. In SCCM, the unit name will be the name that was requested at the time of onboarding. A good reference would be the prefix of your unit’s top-level device collection. For example, if your top-level device collection is “Psychology - Devices”, then you would use “Psychology” as your prefix.
Proper prefixing is important for any content added to SCCM by the unit. This includes (but not limited to) Collections, Applications, Packages, Boot Images, and Task Sequences.
Examples
- UFIT-Test Machines (Collection)
- UFIT-Google Chrome (Application)
- UFIT-Windows 10 Test Deployment (OSD Task Sequence)
Please note that it is crucial that the prefix matches your unit name EXACTLY. This includes any hyphenation. For example, if your unit is one of many sub-units, your site will have a xxxx-xxxx format:
- GATR-ALBERT
- GATR-ALBERTA
- GATR-WALLY
If you're in GATR-WALLY, be sure to use 'GATR-WALLY', not 'WALLY'. Not using the entire site name can result in content that cannot be associated with a unit and runs a risk of being removed from the system.
We have made every effort to include every combination of formatting of the hyphenation that lies between the prefix and the content name in our automated cleanup processes, but for continuity, we recommend sticking to the following format for spacing
UFIT-Test Machines
If your unit is a sub unit, it would look like this:
GATR-WALLY-Test Machines