Skip to main content

Read The Help Files

By

One of the things that I urge, if not plead, in my PowerShell classes is to read the help files.  I’ve been working with PowerShell since it was called Monad.  I honestly cannot work with PowerShell unless I use the help system.  One of the reasons why I want IT Pros to read the help files is so they do not “assume” something.  Take this code that I looked at on PowerShell.Com’s forums.

  get-content -path c:\temp\servers.txt |

 foreach {Get-WmiObject win32_service} |

 select pscomputername, displayname, startname

 

The problem that the IT Pro was having is that the PSComputerName property was always his local client, not the remote computer.  The help file for Get-WMIObject says this about the ComputerName parameter:

-ComputerName [<String[]>]

    Specifies the target computer for the management operation. Enter a fully

    qualified domain name, a NetBIOS name, or an IP address. When the remote

    computer is in a different domain than the local computer, the fully

    qualified domain name is required.

   

    The default is the local computer. To specify the local computer, such as

    in a list of computer names, use "localhost", the local computer name, or

    a dot (.).

   

    This parameter does not rely on Windows PowerShell remoting, which uses

    WS-Management. You can use the ComputerName parameter of Get-WmiObject

    even if your computer is not configured to run WS-Management remote

    commands.

   

    Required?                    false

    Position?                    named

    Default value                none

    Accept pipeline input?       false

    Accept wildcard characters?  false

 

The assumption here is that ComputerName would be populated by the name of the computer in the Pipeline.  Two things are wrong here.  The first is that ComputerName parameter is Name, not positional.  It also cannot accept anything from the pipeline.  That means that if you do not type –ComputerName, it will not be used.  Get-WMIObject will execute against the local client.  The other problem is that inside of ForEach-Object, you need to make a reference to the current object in the PowerShell Pipeline.  You do this with $_ or $PSItem  

The site user CMartin16 provided the correct answer to this problem:

 get-content -path c:\temp\servers.txt |

 foreach {Get-WmiObject win32_service -ComputerName $_} |

 select pscomputername, displayname, startname

 

As an update to this, take a look at Get-CIMInstance and using a CIMSession.  You could also use Invoke-Command and take advantage of PowerShell remoting to contact the remote clients.

Get-Content -Path c:\temp\servers.txt |

 ForEach-Object {Get-CimInstance -ClassName Win32_Service -ComputerName $_} |

 Select-Object -Property pscomputername, displayname, startname

 

The ComputerName parameter of Get-CIMInstance creates an ad-hoc Session to each client. Here is another example.

Get-CimInstance -ClassName Win32_Service -ComputerName (Get-Content -Path c:\temp\servers.txt)|

Select-Object -Property pscomputername, displayname, startname

 

An example using PowerShell remoting.

Invoke-Command -ComputerName (Get-Content -Path c:\temp\servers.txt) -ScriptBlock {

    Get-CimInstance -ClassName Win32_Service

}| Select-Object -Property pscomputername, displayname, startname

 

 

 

 

 

 

 

 

Labels:

Comments

Post a Comment

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

By
This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .
6 comments
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more

Backup and Restore AD LDS with DSDBUTIL.exe

By
Active Directory Lightweight Directory Services allow you to create a directory service that allows applications to have access to user accounts, groups, and authentication similar to Active Directory Domain Services.  The big advantage here is that the schema of the directory service will not be bound by the rules of an Active Directory database.  Exchange 2007/2010, for example, use an instance of AD LDS on the Edge Transport Server to provide for user authentication from the internet.  Because your Active Directory database is not exposed to the internet, this is more secure. Applications will handle most of the dirty work should they require AD LDS.  You may want to make sure the database is being backed up and also have a restore plan in place.  Should the database become corrupt, the application that uses that database will fail.  This document will walk you through backing up and restoring an instance of AD LDS using the dsdbutil.exe command. Fi...
6 comments
Read more