Windows 7 wmi script

Fixed it now and added another section to get the computers name. Cheers VBScab. Haha on the George Osborne Ogle but was on a time frame and the searching I was doing at the time wasnt bring up what I was after. Rating comments in this legacy AppDeploy message board thread won't reorder them, so that the conversation will remain readable.

Answer this question. Posted by:. Thegunner Ninja since: 17 years ago. Don't be a Stranger! Sign up! View more:. Scripting Questions. Script never finishes running. Unassigned Ticket Notification Rule. Trying to run a Script that keeps failing.

Getting Status code Many people have security concerns when it comes to PowerShell, but the truth is you have exactly the same permissions in PowerShell as you do in the GUI.

No more and no less. The problem in the previous example is that the user running PowerShell doesn't have rights to query WMI information from the DC01 server. But, trust me, that isn't a good idea because then anything that I run from PowerShell would be running as a domain admin. That could be dangerous from a security standpoint depending on the situation. Using the principle of least privilege, I elevate to my domain admin account on a per command basis using the Credential parameter, if a command has one.

Get-CimInstance doesn't have a Credential parameter so the solution in this scenario is to create a CimSession first. Notice that I also specified the Get-Credential cmdlet in parentheses so that it executes first, prompting me for alternate credentials, before creating the new session.

I'll show you another more efficient way to specify alternate credentials later in this chapter, but it's important to understand this basic concept before making it more complicated. There are several additional benefits to using CIM sessions instead of just specifying a computer name.

When running multiple queries to the same computer, using a CIM session is more efficient than using the computer name for each query.

Creating a CIM session only sets up the connection once. Then, multiple queries use that same session to retrieve information. Using the computer name requires the cmdlets to set up and tear down the connection with each individual query. It's actually not the PowerShell version that matters, it's the stack version.

The stack version can be determined using the Test-WSMan cmdlet. It needs to be version 3. To find the location of a given WMI class, look at the reference page. Alternately, you can manually explore a namespace using get-WmiObject. As such, in order to retrieve the child instances, you need to only search for the parent class. For more information, see Common Information Model. WMI supplies an entire schema of such preinstalled classes that allow you to access and control managed objects. Together, this is known as the WMI object path.

In addition to namespace and class name, a WMI object will also have a key property, which uniquely identifies that instance compared to other instances on your machine. Finally, the Relative path is simply a shortened form of the path, and includes the class name and key value.

For more information, see Modifying an Instance Property. ConnectServer method. Note that you can only use alternate credentials on a remote system. For more information, see Securing Scripting Clients.

For PowerShell, use the -ComputerName parameter. For PowerShell, use the -Authentication and -Impersonation parameters, respectively. In VBScript in particular, error handling is also supported using the native Err object.

You may also access the SWbemLastError object, as described above.