Monday, December 10, 2012 9:14 PM
I have figured out how to customize the Customsettings.ini file to deploy packages based on PC model. But we also have packages here that need to be deployed by PC name. For example on classroom we have here is named NYC-LAB-W01. The PCs in this room need a printer package installed based on the Room Location.
I tried to have my Customsettings.ini file setup this way
But this doesn't seem to work.
Any help is truly appreciated.
Monday, December 10, 2012 9:48 PM
[Settings] Priority=Model, Default, ByName [Optiplex 760] PACKAGES001=SomePackage1 [ByName] Subsection=#Left("%OSDComputerName%",9)# [NYC-LAB-W] PACKAGES002=SomePackage2 [Default] OSInstall=Y SkipCapture=YES SkipAdminPassword=NO SkipProductKey=YES
EDIT: To explain the code if you dont understand i create a priority property named "ByName" and then in that Section i call the "Left"-Function to get the first 9 characters from the OSDComputerName variable. Then i create a section named "NYC-LAB-W" with a package in it. If the first 9 characters is NYC-LAB-W in the computername then PACKAGE002 will be installed.
- Edited by Samus-Aran Monday, December 10, 2012 9:58 PM
Monday, December 10, 2012 10:53 PMSince you are doing this in SCCM, if you don't want to mess with customizing your CustomSettings.ini, you could put all the classroom machines (either manually or by dynamic query) into a Collection, set a Collection variable for that Collection, and in the Task Sequence just check for the variable and if it is found to be true, then run an install software command.
David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek
- Marked As Answer by Stephen Perrott Thursday, December 27, 2012 6:31 PM
Wednesday, December 12, 2012 3:56 PM
So if I am getting this right....
I should set a collection variable for OSDComputerName in the collection. Then as a condition in the task sequence for the Install Software command I could set it to something like this below?
Thursday, December 27, 2012 6:33 PM
Sorry I took so long to reply. But doing it by setting the collection variable and having it check it during the task sequence worked beautifully.