As part of a task sequence there is a VB script that runs which validates via WMI that the hardware being built is known. It simply has a string of if then else's, the problem is that each time a new piece of hardware is added this script has to be modified. Ive been asked to look at modifying the script which is easy enough. In terms of long term I could modify the script to simply pull the valid devices from a text file to avoid having to modify the script but is there a more elegant way or even a feature in SCCM 2012 that I could make use of to maintain a list of valid devices.
Quick SCCM 2012 related question?
- Thread starter IAmATeaf
- Start date
Associate
- Joined
- 15 Jul 2005
- Posts
- 1,227
- Location
- UK
eh?
just to clarify, do you mean if you run a TS on a machine, it has to match Dell \ HP as the manufacturer ? and if it doesnt, the TS would fail? but if you introduce another brand (e.g. lenvo) you would have to modify the VBS to get the TS to function?
cant you just use a WQL query within the task sequence itself? you can just modify that directly instead of a VBS.
you could also prestage computer accounts in SCCM, and then modify the TS to ignore unknown devices. I think on SCCM, its best practice to prestage computer accounts anyway.
just to clarify, do you mean if you run a TS on a machine, it has to match Dell \ HP as the manufacturer ? and if it doesnt, the TS would fail? but if you introduce another brand (e.g. lenvo) you would have to modify the VBS to get the TS to function?
cant you just use a WQL query within the task sequence itself? you can just modify that directly instead of a VBS.
you could also prestage computer accounts in SCCM, and then modify the TS to ignore unknown devices. I think on SCCM, its best practice to prestage computer accounts anyway.
Sort of, the TS would only continue if it's a known/approved type of machine. At the moment the VB script has to be modified to add systems/machines so for example a Lenova machine had already been added but after it had its motherboard replaced it reported itself as a slightly different system/model so the TS failed. So I'm looking for advice on if there's a way of managing this within SCCM.
Associate
- Joined
- 15 Jul 2005
- Posts
- 1,227
- Location
- UK
yeah you can....
within the task sequence, create a "folder step" near the start of the sequence, and add a WQL query containing your models, then it will run the rest of the steps in the folder. you can scrap the VBS all together then, and maintain it within SCCM
if your doing it more for security... its quite a poor way to do it really... the logical way would be just to add a Password to the PXE boot role in SCCM, so you dont get random people plugging their laptops in trying to steal your image.
hope this helps.. and is clear!
within the task sequence, create a "folder step" near the start of the sequence, and add a WQL query containing your models, then it will run the rest of the steps in the folder. you can scrap the VBS all together then, and maintain it within SCCM
if your doing it more for security... its quite a poor way to do it really... the logical way would be just to add a Password to the PXE boot role in SCCM, so you dont get random people plugging their laptops in trying to steal your image.
hope this helps.. and is clear!
Last edited:
As per the above reply. The best and common way to achieve is to use a group of wmi checks for the models you want to be supported. You then simply add a new entry into the wmi checks section as required. The only other way that might be a little more dynamic would be to setup a collection for each model I.e a collection based on a wmi check. This would the populate a collection variable of assets fall into one of those collections. If it's not a valid model it would hence not be set. That means you could then simply have a group of collections for each supported model. A new model would just need a new collection defining which would also then be re-usable for other targeting reasons.
Just my two peneth anyway.
Just my two peneth anyway.