ScriptingAnswers Forums

VBScript : NIC Power Management

Wed, 22 Feb 2012 12:27:34 +0000

Author: jvierra
Subject: NIC Power Management
Posted: 22 Feb 2012 at 12:27

After looking at this code for awhile I can see that it will never work. The location of teh PnP driver information will never be stable. The 'Class' key is a collection that has to be enumerated.

Most of this is why we usually are required to use the vendors configuration utilities.

There is a utility that works on most newer adapters called PowerCfg

This will tell you if your device is programmabe.

powercfg /DEVICEQUERY wake_programmable

This will enable the device assuming it is programmable.

powercfg /DEVICEENABLEWAKE "compliant device id"

This utility uses APIs that are not available to scripting to resolve device configuration.

VBScript : NIC Power Management

Wed, 22 Feb 2012 11:57:34 +0000

Author: jvierra
Subject: NIC Power Management
Posted: 22 Feb 2012 at 11:57

Well it is clear that the code cannot work becuse it was never written correctly.

What the user is trying to do will only work on one specific machine which has only one setting. Most machines will have multiple entries for the network GUID.

Edited by jvierra - Today at 12:29

Windows PowerShell : Slow WMI query

Wed, 22 Feb 2012 11:10:16 +0000

Author: jhicks
Subject: Slow WMI query
Posted: 22 Feb 2012 at 11:10

Absolutely. Even though this thread started out as a discussion of improving WMI performance, it really is about the right way to use PowerShell. My example was more on that than overall WMI performance. The bottom line is find the time to learn how to use PowerShell the way it was designed and you'll eventually get more done with less work.

VBScript : NIC Power Management

Wed, 22 Feb 2012 11:01:25 +0000

Author: jvierra
Subject: NIC Power Management
Posted: 22 Feb 2012 at 11:01

Are you saying that it runs wih no errors eeven after removing the On Error line?

Are you sure the adapter can use power management.

These setting changes will require a restart to function.

Windows PowerShell : Slow WMI query

Wed, 22 Feb 2012 10:59:47 +0000

Author: jvierra
Subject: Slow WMI query
Posted: 22 Feb 2012 at 10:59

Nise Jeff.

One note. When querying multiple computers it may be faster to ping first because WMI timeout talkes too long.

Try/Catch on Get-WMIObject is useful for whenWMI is faulty or misconfigured. In this case I find using -ea 0 and -ev myerror and checking the error an easier constuct in some cases.

Heirich, Don's book is worth the time. Get a copy.

The PowerShell TFM book is good as a learning tool and as a reference.

I believe both books are available electronically.

VBScript : NIC Power Management

Wed, 22 Feb 2012 08:27:51 +0000

Author: octoj2011
Subject: NIC Power Management
Posted: 22 Feb 2012 at 08:27

Thanks for the suggestion. I've just tried that but still not working.

Windows PowerShell : Slow WMI query

Wed, 22 Feb 2012 08:13:21 +0000

Author: jhicks
Subject: Slow WMI query
Posted: 22 Feb 2012 at 08:13

Here's another attempt to show you the object nature of PowerShell. You are still just writing strings with added value. I'm not saying this is exactly what you need but it is similar.


$servicenames="spooler","dns","MOM","wuauserv"

$Computers="serenity","foo","quark"

foreach ($computer in $computers) {

Try {

    Write-Host "Checking $computer" -ForegroundColor Green

    $wmi=get-wmiobject -class win32_service -ComputerName $computer -ErrorAction "Stop"    

    if ($wmi) {

    Write-Host "Found $($wmi.count) services" -ForegroundColor Green

    #create a hash table to be used for new object properties

    $hash=@{

    Computername=$wmi[0].Systemname

    Connected=$True

    }  

    #check each service in the list

    Write-Host "Processing Services" -ForegroundColor Green

    foreach ($service in $servicenames) {

        #find the service

        $s=$wmi | where {$_.name -eq $service}   

        if ($s) {

        Switch ($s.state) {

         "Running" {$status=$True}

         "Stopped" {$status=$False}       

         Default {$status=$False}

         } #switch

         $name=$s.name

        }

        else {

            #service not found so set status to not found

            Write-Host "$service not found" -ForegroundColor Red

            $status="Not found"

            $name=$service

        } 

        #add an entry to the hash table

        $hash.Add($Name,$status)        

        } #foreach service

        #create a custom object and write to the pipeline

        New-Object -TypeName PSObject -Property $hash

    } #if $wmi

    Remove-Variable wmi,s

} #try

Catch {

    Write-Warning "Failed to get services from $computer. $($_.Exception.Message)"

}

} #foreach computer

This has the benefit of writing a custom object to the pipeline like this:

Spooler      : True
MOM          : Not found
Connected    : True
Computername : QUARK
wuauserv     : True
dns          : Not found

If I run this script I can now use it many ways. I can save the results to a variable and then sort or filter. I can export to a CSV file. I can send to a printer. Or any combination. I understand PowerShell is tough to get started and you are making a valiant effort. You might consider getting a copy of Learn PowerShell in a Month of Lunches by Don Jones. Or take a look at my blogand Prof. PowerShell column.

Edited by jhicks - Today at 08:15

Windows PowerShell : Slow WMI query

Wed, 22 Feb 2012 05:48:03 +0000

Author: jvierra
Subject: Slow WMI query
Posted: 22 Feb 2012 at 05:48

You will waste more time guessing than you will reading. If you are time-bound then you really need to learn PowerSHell correctly as it can save you a tremendous amount of time.

Without the basics you will never know when someone is sending you down a rabbit hole. There are a great many people on the INternet giving bad advice on PowerSHell. Knowing the basics will protect you from this.

Edited by jvierra - Today at 05:48

Windows PowerShell : Slow WMI query

Wed, 22 Feb 2012 05:44:23 +0000

Author: heinrichxs
Subject: Slow WMI query
Posted: 22 Feb 2012 at 05:44

Thank you wil give it a try.

Problems are not getting the books, it is finding the time to read them. So much to learn, so little time to do it in :-)

Windows PowerShell : Slow WMI query

Wed, 22 Feb 2012 05:23:16 +0000

Author: jvierra
Subject: Slow WMI query
Posted: 22 Feb 2012 at 05:23

This is closer to what you want.

Get-Content Servers.txt |
    ForEach-Object{
        if (Test-Connection $_ -count 1 -quiet){
            $OS = Get-WmiObject -class Win32_OperatingSystem -computername $_ 
            $services =  Get-WMIObject -class Win32_Service -ComputerName $_ 
            If ($services | Where-Object{$_.Name -eq 'VMTools'} ) {$VMT = "Yes"}  else {$VMT = "No"}
            If ($services | Where-Object{$_.Name -eq 'dmexplorer'}) {$DMX = "Yes"}  else {$DMX = "No"}
            If ($services | Where-Object{$_.Name -eq 'vxsicld'}) {$VXS = "Yes"}  else {$VXS = "No"}
            If ($services | Where-Object{$_.Name -eq 'vrtshal'})  {$VRT = "Yes"}  else {$VRT = "No"}
            If ($services | Where-Object{$_.Name -eq 'vmicheartbeat'}) {$VMIC = "Yes"}  else {$VMIC = "No"}
            If ($services | Where-Object{$_.Name -eq 'CcmExec'}) {$CCM = "Yes"}  else {$CCM = "No"}
            If ($services | Where-Object{$_.Name -eq 'MOM'}) {$MO = "Yes"}  else {$MO = "No"}
            If ($services | Where-Object{$_.Name -eq 'HealthService'}) {$Health = "Yes"}  else {$Health = "No"}
            If ($services | Where-Object{$_.Name -eq 'awservices'}) {$aws = "Yes"}  else {$aws = "No"}
            If ($services | Where-Object{$_.Name -eq 'NetBackup Client Service'}){$NetB = "Yes"}  else {$NetB = "No"}
            $fcadap = Get-WmiObject -class MSFC_FCAdapterHBAAttributes -computername $_ -ea 0
            if ($fcadap) {$fca = "Yes"} else {$fca = "No"}
            "$_ ; $($os.caption) ; $($os.version) ; $VMT ; $DMX ; $VXS ; $VRT ; $VMIC ; $CCM ; $MO ; $Health ; $aws ; $NetB ; $fca"
        }else{
            Write-Host "Unable to contact $_" -ForegroundColor red
        }
    }

I recommend getting a book on PowerShell. You sem to be a bit confused about how it works.

You are using try/catch in an odd way. You are also querying computers before testing for their existence. You have suppressed all errors when you do not want to do that.

I suspect you are copying and pasting bits without really understanding what they do. A book will get you back on a more successful path.

If you are not a programmer or skilled scripter PowerShell will confuse you if you don't get the fundamentals correct.

PowerShell is very easy to learn but you cannot guess at how it works. How PowerShell works is counter-intuitive. It is an object system and dŒs not easily succomb to linear programming ideas.

Edited by jvierra - Today at 05:25