• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 361
  • Last Modified:

Get-WMIObject Output issue

Hello All,

Banging my head against the wall with this one...

As part of a script I want to output to a text file the name of a server, the name of a service and the name of the user account that is used to run the service.  Input is obviously a csv or list of servers. just like this:
MyServerName,smstsmgr,LocalSystem

Open in new window


My issue is the output.  All I can get is too much information!  This is what I'm getting:

MyServerName,@{Name=smstsmgr; StartsAs=LocalSystem; DisplayName=ConfigMgr Task Sequence Agent}.name,@{Name=smstsmgr; StartsAs=LocalSystem; DisplayName=ConfigMgr Task Sequence Agent}.Displayname,.Startname
MyServerName,\\MyServerName\root\cimv2:Win32_Service.Name="smstsmgr".name,\\MyServerName\root\cimv2:Win32_Service.Name="smstsmgr".Displayname,\\MyServerName\root\cimv2:Win32_Service.Name="smstsmgr".Startname

Open in new window



This is on two lines in a text file.
This is my code:

function Get-AdminService

{
    [CmdletBinding()]

    Param()

    $Servers = Get-Content -Path $InputDir\RealServers.txt

    foreach ($Server in $Servers)
    {
        $SVC = Get-WMIObject -Class Win32_Service -Computername $Server -Filter "Name = 'smstsmgr'"

        foreach ($Service in $SVC)
        {
            Write-Verbose $Service.name 
            Add-Content -Path $OutputDir\ChgService.txt "$Server,$Service.name,$Service.Displayname,$Service.Startname"
        }
    }
}
Get-AdminService -Verbose

Open in new window


You can see where I'm writing verbose using just a single property and that works fine on the console. If I add multiple properties there it also doesn't work. If I wrap that part with "quotes" and just show a single property, I get a similar extended output to the file I'm generating:
VERBOSE: \\MyServerName\root\cimv2:Win32_Service.Name="smstsmgr".name

Open in new window


Please can anyone point out what I'm doing wrong and how I fix it?

Many thanks
0
Tommy_Cooper
Asked:
Tommy_Cooper
  • 3
  • 2
1 Solution
 
Dan CraciunIT ConsultantCommented:
I think you should try it like this:
Add-Content -Path $OutputDir\ChgService.txt ($Server + ", " + $Service.name + ", " + $Service.Displayname + ", " + $Service.Startname)

Open in new window


HTH,
Dan
0
 
Tommy_CooperAuthor Commented:
Dan,

You're a star!

Thank you.
0
 
Dan CraciunIT ConsultantCommented:
Nope, just banged my head against the same wall a while back :)

Glad I could help.
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 
footechCommented:
Solution has already been accepted, but here's an explanation of this behavior...
Inside a string, if you're displaying properties of an object you need to use subexpression notation "$($x.property)".  So you could do the following:
           Add-Content -Path $OutputDir\ChgService.txt "$Server,$($Service.name),$($Service.Displayname),$($Service.Startname)"

Open in new window

I have found a few times that this works better than concatenation (which is what Dan's example uses).
In a case where your objective is to output a .CSV file however, in most cases I would use the Select-Object command to choose what properties I want and pipe that to Export-CSV.
0
 
Tommy_CooperAuthor Commented:
Footech - That is excellent. Thank you. If I could give you some points now I would :)
0
 
Dan CraciunIT ConsultantCommented:
I'm not versed enough on PS, so I find the $($.) construct harder to read. That's why I prefer concatenation. Easier on my brain :)
0

Featured Post

What Security Threats Are We Predicting for 2018?

Cryptocurrency, IoT botnets, MFA, and more! Hackers are already planning their next big attacks for 2018. Learn what you might face, and how to defend against it with our 2018 security predictions.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now