{"id":5789,"date":"2017-11-21T14:12:03","date_gmt":"2017-11-21T19:12:03","guid":{"rendered":"https:\/\/jdhitsolutions.com\/blog\/?p=5789"},"modified":"2017-11-21T14:15:09","modified_gmt":"2017-11-21T19:15:09","slug":"who_is_running","status":"publish","type":"post","link":"https:\/\/jdhitsolutions.com\/blog\/powershell\/5789\/who_is_running\/","title":{"rendered":"Who is Running Your PowerShell Script?"},"content":{"rendered":"

I've often talked about the benefit of including Verbose output in your PowerShell scripts and functions from the very beginning. This is especially helpful when someone else is running your command but encounters a problem. You can have them start a transcript, run your command with \u2013Verbose, close the transcript and send it to you. if you've written informative Verbose messaging you should be able to figure out the problem. Part of the information might include metadata about the person running the command and their environment. To simply things, I've created an easy to use function called Get-PSWho.<\/p>\n

<\/p>\n

The function writes a custom object to the pipeline with information about the user, their computer and their PowerShell environment. One of the things that might be helpful is knowing where the command is being run as not all PowerShell hosts may support your code.<\/p>\n

\"image\"<\/a><\/p>\n

 <\/p>\n

\"image\"<\/a><\/p>\n

\"image\"<\/a><\/p>\n

The other design decision I made was to deviate slightly from the recommended practice of only writing one type of object to the pipeline and not re-inventing the wheel. One of the reasons I wrote this was to make it easy to incorporate into your functions and scripts. You can either embed the function or make sure it is distributed with your commands so that you can include the output in a Write-Verbose<\/a> line. But, you have to make turn the output into a string.<\/p>\n

Write-Verbose \"User Metadata\"\r\nWrite-Verbose (Get-PSWho | Out-String)\r\n<\/pre>\n
Since you might need a string anyway, I decided to include it as an option.<\/p>\n
Write-Verbose \"User Metadata\"\r\nGet-PSWho -AsString | Write-Verbose\r\n<\/pre>\n
\"image\"<\/a><\/p>\n
Or you could just as easily pipe the string version to Write-Host<\/a>. The point is that I thought about how this command might be used and added what I thought would be a useful parameter. Again, I am a bit torn on whether this is the right design decision, but you may simple opt to take my code and paste it into your function directly.<\/p>\n
You can find the code on GitHub.<\/p>\n