The key field we were missing was “(models included:)” in the description which looks to list the systems mainboard options. We boot to winpe and ran “Get-WMIObject -Class Win32ComputerSystem” and “Get-WmiObject Win32BaseBoard” in PS and ensured our manual package had the right name and description. All good now! Browse the driver database with powershell? Machines that I have driver support will pull from their respective folder E.G. Windows 7 Dell Inc. Optiplex 7010 whereas systems that do not will pull from a pool of storage and ethernet drivers. (Get-WmiObject -Class:Win32Computersystem).Manufacturer. Get the path to the.
I was not sure what all it is certainly you are usually trying to do, particularly given that you pointed out actions structured on model but after that proceeded to link to content working with asset tags. Possibly you (and everyone else) understands how to décode these on thé travel, but I perform not. That mentioned, if I had been to perform something, I would possibly begin Iike this:
With thát, I now have the design of the regional personal computer. I can after that take care of that string into either a adjustable or a text message document for easy referrals or further make use of.In keeping with functioning on the regional system, we can operate a question against that for further activity. For example:
Presumably, you something more powerful than just state 'Complement.' So, rather, you can call another screenplay/task in that stop.
At this point, it would simply be a matter of expanding on your 'what to do' if statements.
You can expand on this by nourishing it a text document with a checklist of pc names which you would like to operate it ágainst.
Edit: Aftér re-réading it looks like you are wanting to perform asset label management based on the producer. Is definitely that proper?
In which situation, that should not really be a problem. One minimal change:
Implemented by the additional small change(t) in the If statements:
You can questions details from any of these classes with the Gét-wmiObject cmdIet. This command will supply basic info on the queried item and appears like this for the Gain32ComputerSystem class.
Get-wmiObject Get32ComputerSystem
The result on one of my systems is usually
Domains : WORKGROUP
Manufacturer : Dell Inc.
Model : Dell DM051
Title : MIKE-PC
PrimaryOwnerName : MIKE
TotalPhysicalMemory : 3756154880
TipThe Gét-wmiObject cmdlet offers its own alias of gwmi Rather of keying in in the whole control, you can substitute it with gwmi whenever preferred For example, the right after two instructions are construed the same:
You can use the same order for any Get32 class to notice what kind of information is provided.
You can also change what information is supplied. For instance, by incorporating the Structure- Checklist cmdlet, you'll see significantly even more fine detail on the queried item. Instead of simply a few commonly utilized attributes, it will list all of the qualities:
Get-wmiObject Win32ComputerSystem Format-List.
If you execute these instructions, you may notice that some of the properties start with two underscores (such as Genus, Course, and so on). These are utilized by the program and are known to as system courses. If you wish to get rid of them, you can use the pursuing control to list attributes that begin with a notice:
Get-wmiObject Gain32ComputerSystem Format-List a-z.