Suggested Label Naming Conventions
Since I've had so many customers request my Smart Label Naming Conventions, I thought I'd share them here. r2
My philosophies are pretty simple – for Machine Labels, I think the purpose of the label is what I want in the name and the criteria in the notes field – for Patch Labels, however, I like the criteria in the name and any additional information (e.g. REGEX code) stored in the notes field – for Software Labels the vendor and app title in the name, but the label criteria in the notes field.
Machine Label examples: ML – HW – Laptops ML – HW – Desktops ML – HW – Servers – All ML – HW – Servers – Physical ML – HW – Servers – Virtual ML – OS – MS – Win XP ML – OS – MS – Win 7 ML – OS – Mac – OSX 10.6 ML – OS – Mac – OSX 10.7 ML – UPG – ADB – Reader X ML – UPG – MS – Office 2010 PPß Note that this is an “upgrade†label, since it DOES look for a previous version ML – UPG – MS – Office 2010 Std ML – INST – APL – iTunes 10 ß Note that this one is an “install†label, since it DOES NOT look for a previous version ML – LOC – MA – LEX – BLDG A – Floor 01 – IP ß Note that this is a location label, done using IP Address begins with (1st floor, building A, in Lexington, Massachusetts) ML – LOC – MA – LEX – AD ß Note that this is a location label, done by LDAP grabbing machines in a specific Organizational Unit Software Lable examples: SL – ADB – Acrobat 9 Pro SL – ADB – Acrobat 10 Std SL – MS – Office 2010 PP SL – MS – Office 2010 Std
My philosophies are pretty simple – for Machine Labels, I think the purpose of the label is what I want in the name and the criteria in the notes field – for Patch Labels, however, I like the criteria in the name and any additional information (e.g. REGEX code) stored in the notes field – for Software Labels the vendor and app title in the name, but the label criteria in the notes field.
Machine Label examples: ML – HW – Laptops ML – HW – Desktops ML – HW – Servers – All ML – HW – Servers – Physical ML – HW – Servers – Virtual ML – OS – MS – Win XP ML – OS – MS – Win 7 ML – OS – Mac – OSX 10.6 ML – OS – Mac – OSX 10.7 ML – UPG – ADB – Reader X ML – UPG – MS – Office 2010 PPß Note that this is an “upgrade†label, since it DOES look for a previous version ML – UPG – MS – Office 2010 Std ML – INST – APL – iTunes 10 ß Note that this one is an “install†label, since it DOES NOT look for a previous version ML – LOC – MA – LEX – BLDG A – Floor 01 – IP ß Note that this is a location label, done using IP Address begins with (1st floor, building A, in Lexington, Massachusetts) ML – LOC – MA – LEX – AD ß Note that this is a location label, done by LDAP grabbing machines in a specific Organizational Unit Software Lable examples: SL – ADB – Acrobat 9 Pro SL – ADB – Acrobat 10 Std SL – MS – Office 2010 PP SL – MS – Office 2010 Std
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
ronco
12 years ago
Second Attempt with better formatting:
My philosophies are pretty simple – for Machine Labels, I think the purpose of the label is what I want in the name and the criteria in the notes field – for Patch Labels, however, I like the criteria in the name and any additional information (e.g. REGEX code) stored in the notes field – for Software Labels the vendor and app title in the name, but the label criteria in the notes field. r2
Machine Label examples:
ML – HW – Laptops
ML – HW – Desktops
ML – HW – Servers – All
ML – HW – Servers – Physical
ML – HW – Servers – Virtual
ML – OS – MS – Win XP
ML – OS – MS – Win 7
ML – OS – Mac – OSX 10.6
ML – OS – Mac – OSX 10.7
ML – UPG – ADB – Reader X
ML – UPG – MS – Office 2010 PP Note that this is an “upgrade†label, since it DOES look for a previous version
ML – UPG – MS – Office 2010 Std
ML – INST – APL – iTunes 10  Note that this one is an “install†label, since it DOES NOT look for a previous version
ML – LOC – MA – LEX – BLDG A – Floor 01 – IP  Note that this is a location label, done using IP Address begins with (1st floor, building A, in Lexington, Massachusetts)
ML – LOC – MA – LEX – AD  Note that this is a location label, done by LDAP grabbing machines in a specific Organizational Unit
Software Lable examples:
SL – ADB – Acrobat 9 Pro
SL – ADB – Acrobat 10 Std
SL – MS – Office 2010 PP
SL – MS – Office 2010 Std
My philosophies are pretty simple – for Machine Labels, I think the purpose of the label is what I want in the name and the criteria in the notes field – for Patch Labels, however, I like the criteria in the name and any additional information (e.g. REGEX code) stored in the notes field – for Software Labels the vendor and app title in the name, but the label criteria in the notes field. r2
Machine Label examples:
ML – HW – Laptops
ML – HW – Desktops
ML – HW – Servers – All
ML – HW – Servers – Physical
ML – HW – Servers – Virtual
ML – OS – MS – Win XP
ML – OS – MS – Win 7
ML – OS – Mac – OSX 10.6
ML – OS – Mac – OSX 10.7
ML – UPG – ADB – Reader X
ML – UPG – MS – Office 2010 PP Note that this is an “upgrade†label, since it DOES look for a previous version
ML – UPG – MS – Office 2010 Std
ML – INST – APL – iTunes 10  Note that this one is an “install†label, since it DOES NOT look for a previous version
ML – LOC – MA – LEX – BLDG A – Floor 01 – IP  Note that this is a location label, done using IP Address begins with (1st floor, building A, in Lexington, Massachusetts)
ML – LOC – MA – LEX – AD  Note that this is a location label, done by LDAP grabbing machines in a specific Organizational Unit
Software Lable examples:
SL – ADB – Acrobat 9 Pro
SL – ADB – Acrobat 10 Std
SL – MS – Office 2010 PP
SL – MS – Office 2010 Std
Posted by:
ronco
12 years ago
Here's a new one I just worked with a customer on yesterday: ML - HFx - MS - Office 2007 - SP3 kb2526086
This was a Machine (smart) Label, obviously. But the new part was the HFx (hotfix/patch/service pack, etc.) "purpose" bit. We kicked around other bit abbreviations, but HFx was the best we could come up with. Anyway, they wanted to use Managed Installations (MI) to distribute Service Pack 3 for Office 2007. So, we built a Custom Inventory Rule (CIR) to detect it's presence (file version), and the smart label discovered machines that DID NOT have the CIR. We could then use the label as a target for the MI. r2
p.s. Anyone else have any label naming ideas?
This was a Machine (smart) Label, obviously. But the new part was the HFx (hotfix/patch/service pack, etc.) "purpose" bit. We kicked around other bit abbreviations, but HFx was the best we could come up with. Anyway, they wanted to use Managed Installations (MI) to distribute Service Pack 3 for Office 2007. So, we built a Custom Inventory Rule (CIR) to detect it's presence (file version), and the smart label discovered machines that DID NOT have the CIR. We could then use the label as a target for the MI. r2
p.s. Anyone else have any label naming ideas?
Posted by:
rmeyer
12 years ago
What I've done is fairly simple and good enough for me so far :)
Machine Labels: (Is it my head what is "automatic" labels, automaticly added depending on a local file/OS/what ever)
A_64 bit OS
A_7-Zip Missing
A_Lenovo X220
A_Microsoft Office 2003/2007/2010 Missing
A_Screensaver Disabled
A_Screensaver Enabled
A_Windows XP
etc
Software Labels: (manually added applications via labels)
S_Adobe Acrobat x
S_Microsoft Project 2010 Professional
S_SAP GUI 7.20
etc
Then I also have "location" labels depending on subnets for remote site installation
Location_"Sitename"_"Country"
Location_Hoersholm_DK
Location_Milwaukee_US
etc
Machine Labels: (Is it my head what is "automatic" labels, automaticly added depending on a local file/OS/what ever)
A_64 bit OS
A_7-Zip Missing
A_Lenovo X220
A_Microsoft Office 2003/2007/2010 Missing
A_Screensaver Disabled
A_Screensaver Enabled
A_Windows XP
etc
Software Labels: (manually added applications via labels)
S_Adobe Acrobat x
S_Microsoft Project 2010 Professional
S_SAP GUI 7.20
etc
Then I also have "location" labels depending on subnets for remote site installation
Location_"Sitename"_"Country"
Location_Hoersholm_DK
Location_Milwaukee_US
etc
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.