There’s definitely a trick to creating reports with Windows PowerShell. Windows PowerShell isn’t at its best when it’s forced to work with text; objects are where it excels. This blog, based on Chapter 33 from PowerShell in Depth<\/a>, focuses on a technique that can produce a nicely formatted HTML report, suitable for emailing to a boss or colleague.<\/b><\/p>\n Assembling the final page simply involves adding our two existing fragments, although we are also going to embed a style sheet. Using cascading style sheet (CSS) language is a bit beyond the scope of this blog, but this example will give you a basic idea of what it can do. This embedded style sheet lets us control the formatting of the HTML page, so that it looks a little nicer. If you would like a good tutorial and reference to CSS, check out this CSS Tutorial<\/a> on the w3schools.com site.<\/p>\n $head = @’<\/p>\n <style><\/p>\n body { background-color:#dddddd;<\/p>\n font-family:Tahoma;<\/p>\n font-size:12pt; }<\/p>\n td, th { border:1px solid black;<\/p>\n border-collapse:collapse; }<\/p>\n th { color:white;<\/p>\n background-color:black; }<\/p>\n table, tr, td, th { padding: 2px; margin: 0px }<\/p>\n table { margin-left:50px; }<\/p>\n <\/style><\/p>\n ‘@<\/p>\n <\/p>\n ConvertTo-HTML -head $head -PostContent $frag1,$frag2 `<\/p>\n -PreContent “<h1>Hardware Inventory for SERVER2<\/h1>”<\/p>\n We have put that style sheet into the $head<\/b> variable by using a here string to type out the entire CSS syntax that we wanted. That gets passed to the Head<\/i> parameter, our HTML fragments to the PostContent<\/i> parameter, and we couldn’t resist adding a header for the whole page, where we’ve again hardcoded a computer name (SERVER2).<\/p>\n We saved the entire script as C:\\Good.ps1, and ran it like this:<\/p>\n .\/good > Report.htm<\/p>\n That directs the output HTML to Report.htm. This HTML report consists of multiple HTML fragments, which is incredibly beautiful as shown here:<\/p>\n Okay, maybe it is no work of art, but it is highly functional, and frankly, it looks better than the on-screen-only report we started with in yesterday’s blog. List 2 shows the completed script, where we’ve swapped out the hard-coded computer name for a script-wide parameter that defaults to the local host. Notice too that we’ve included the [CmdletBinding()] <\/b>declaration at the top of the script, which enables the Verbose<\/i> parameter. We have used Write-Verbose<\/b> to document what each step of the script is doing.<\/p>\n List 2: An HTML inventory report script<\/b><\/p>\n <#<\/p>\n .DESCRIPTION<\/p>\n Retrieves inventory information and produces HTML<\/p>\n .EXAMPLE<\/p>\n .\/Good > Report.htm<\/p>\n .PARAMETER<\/p>\n The name of a computer to query. The default is the local computer.<\/p>\n #><\/p>\n <\/p>\n [CmdletBinding()]<\/p>\n param([string]$computername=$env:computername)<\/p>\n <\/p>\n # function to get computer system info<\/p>\n function Get-CSInfo {<\/p>\n param($computername)<\/p>\n $os = Get-WmiObject -Class Win32_OperatingSystem -ComputerName $computername<\/p>\n $cs = Get-WmiObject -Class Win32_ComputerSystem -ComputerName $computername<\/p>\n $bios = Get-WmiObject -Class Win32_BIOS -ComputerName $computername<\/p>\n $props = @{‘ComputerName’=$computername<\/p>\n ‘OS Version’=$os.version<\/p>\n ‘OS Build’=$os.buildnumber<\/p>\n ‘Service Pack’=$os.sevicepackmajorversion<\/p>\n ‘RAM’=$cs.totalphysicalmemory<\/p>\n ‘Processors’=$cs.numberofprocessors<\/p>\n ‘BIOS Serial’=$bios.serialnumber}<\/p>\n <\/p>\n $obj = New-Object -TypeName PSObject -Property $props<\/p>\n Write-Output $obj<\/p>\n }<\/p>\n <\/p>\n Write-Verbose ‘Producing computer system info fragment’<\/p>\n $frag1 = Get-CSInfo -computername $computername |<\/p>\n ConvertTo-Html -As LIST -Fragment -PreContent ‘<h2>Computer Info<\/h2>’ |<\/p>\n Out-String<\/p>\n <\/p>\n Write-Verbose ‘Producing disk info fragment’<\/p>\n $frag2 = Get-WmiObject -Class Win32_LogicalDisk -Filter ‘DriveType=3’ `<\/p>\n -ComputerName $computername |<\/p>\n Select-Object @{name=’Drive’;expression={$_.DeviceID}},<\/p>\n @{name=’Size(GB)’;expression={$_.Size \/ 1GB -as [int]}},<\/p>\n @{name=’FreeSpace(GB)’;expression={$_.freespace \/ 1GB -as [int]}} |<\/p>\n ConvertTo-Html -Fragment -PreContent ‘<h2>Disk Info<\/h2>’ |<\/p>\n Out-String<\/p>\n <\/p>\n Write-Verbose ‘Defining CSS’<\/p>\n $head = @’<\/p>\n <style><\/p>\n body { background-color:#dddddd;<\/p>\n font-family:Tahoma;<\/p>\n font-size:12pt; }<\/p>\n td, th { border:1px solid black;<\/p>\n border-collapse:collapse; }<\/p>\n th { color:white;<\/p>\n background-color:black; }<\/p>\n table, tr, td, th { padding: 2px; margin: 0px }<\/p>\n table { margin-left:50px; }<\/p>\n <\/style><\/p>\n ‘@<\/p>\n <\/p>\n Write-Verbose ‘Producing final HTML’<\/p>\n Write-Verbose ‘Pipe this output to a file to save it’<\/p>\n ConvertTo-HTML -head $head -PostContent $frag1,$frag2 `<\/p>\n -PreContent “<h1>Hardware Inventory for $ComputerName<\/h1>”<\/p>\n <\/p>\n Now that’s a script you can build upon! Using the script is very easy.<\/p>\n <\/p>\n PS C:\\> $computer = SERVER01<\/p>\n PS C:\\> C:\\Scripts\\good.ps1 -computername $computer |<\/p>\n >> Out-File “$computer.html”<\/p>\n >> <\/p>\n PS C:\\> Invoke-Item “$computer.html”<\/p>\n The script runs, produces an output file for future reference, and displays the report. Keep in mind that our work to build the Get-CSInfo<\/b> function is reusable. Because that function outputs an object, not only pure text, you could repurpose it in a variety of places where you might need the same information.<\/p>\n To add to this report, you would:<\/p>\n Yes, this report is text. Ultimately, every report will be because text is what humans read. The point of this one is that everything stays as Windows PowerShell-friendly objects until the last possible instance. We let Windows PowerShell, rather than our own fingers, format everything for us. The actual working bits of this script, which retrieve the information we need, could easily be copied and pasted and used elsewhere for other purposes. That was not as easy to do with our original pure-text report because the actual working code was embedded with all of that formatted text.<\/p>\n Building reports is certainly a common need for administrators, and Windows PowerShell is well suited to the task. The trick, we feel, is to produce reports in a way that makes the reports’ functional code (the bits that retrieve information and so forth) somewhat distinct from the formatting- and the output-creation code. In fact, Windows PowerShell is generally capable of delivering great formatting with very little work on your part, as long as you work it the way it needs you to.<\/p>\n ~Don, Richard, and Jeffery<\/p>\n Thank you Candace, Don, Richard, and Jeffery.<\/p>\n I invite you to follow me on Twitter<\/a> and Facebook<\/a>. If you have any questions, send email to me at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n Ed Wilson, Microsoft Scripting Guy<\/b><\/p>\n","protected":false},"excerpt":{"rendered":" Summary: In today’s blog, we continue our excerpt from the upcoming book by Don Jones, Richard Siddaway, and Jeffery Hicks. Microsoft Scripting Guy, Ed Wilson, is here. Yesterday, we posted PowerShell in Depth: Part 1, an excerpt provided by Candace Gillhoolley from Manning Publications. The book, PowerShell in Depth, is written by Don Jones, Richard […]<\/p>\n","protected":false},"author":596,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[64,56,65,189,3,45],"class_list":["post-9211","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-don-jones","tag-guest-blogger","tag-jeffery-hicks","tag-richard-siddaway","tag-scripting-guy","tag-windows-powershell"],"acf":[],"blog_post_summary":" Summary: In today’s blog, we continue our excerpt from the upcoming book by Don Jones, Richard Siddaway, and Jeffery Hicks. Microsoft Scripting Guy, Ed Wilson, is here. Yesterday, we posted PowerShell in Depth: Part 1, an excerpt provided by Candace Gillhoolley from Manning Publications. The book, PowerShell in Depth, is written by Don Jones, Richard […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/9211","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/596"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=9211"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/9211\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=9211"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=9211"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=9211"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/7506.hsg-6-5-12-1.jpg\" "\\"Image")
<\/a><\/p>\nAssembling the final HTML page<\/h2>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/5078.hsg-6-5-12-2.png\" "\\"Image")
<\/a><\/p>\n\n