![\"Hey,](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/q-for-powertip.jpg\" "\\"Hey,")
<\/h2>\n <\/h2>\nHey Scripting Guy! I would like to be able to use Windows PowerShell<\/a> to obtain some information from WMI and then write that same information to a Microsoft Word document. I know that I can use Out-File<\/strong> to create a text file, but text files are boring. I want to get the information into Word where I can later add colors, borders, and pictures if I wish. Help me? I’m beggin’ you here.<\/p>\n – GS<\/p>\n Hi GS,<\/p>\n Boring text files? Dude, I love<\/strong> text files. They use almost no disk space, consume nearly no memory, and are portable across platforms. Personally, I think that Notepad.exe is the best program that Microsoft ever wrote. Hey, it was feature complete nearly 20 years ago, and it has never really<\/a> had a bug<\/a> in it. I do, however, agree that colors, borders, and pictures do make a document more interesting. <\/p>\n The coral picture just below, taken by Ed while scuba diving in the Cayman Islands a couple of weeks ago, has nothing to do with this article. But as you can see, it does make the article more interesting. This is particularly true because the water in Little Cayman was 84 degrees, and it is 29 degrees with frost on the ground this morning in Charlotte, NC, USA). Or the water there was 28.89 and it is now -1.69 Celsius here (by using the temperature conversion HTA<\/a>). <\/p>\n <\/p>\n GS, despite my strong affinity for Notepad.exe (also known as the Microsoft script editor), I am going to help you because I love WMI (I [Ed] actually wrote the best-selling book on the subject<\/a>), and I love scripting Microsoft Word. Okay, enough playing around, here is the WriteBiosInfoToWord.ps1<\/strong> script. If you would like to see a VBScript that writes WMI information to a Word document, there is one in the Script Repository<\/a>. That script, however, does not save the data; it just displays the data in a Word document. To see a VBScript example of saving a Word document, follow me<\/a>. <\/p>\n WriteBiosInfoToWord.ps1<\/strong><\/p>\n The first thing we do in the WriteBiosInfoToWord.ps1<\/strong> script is create two variables and assign values to them. The first variable is $class<\/strong> (in Windows PowerShell all variables begin with a dollar sign), and it holds the name of the WMI class we wish to query. In this script we are using the Win32_Bios WMI class, but there are many other WMI classes that could be used. They are all detailed in the MSDN WMI documentation<\/a>. The second variable we use is the $path<\/strong>, which holds the drive, folder, and name of the document we wish to create. Note that it does not contain the file extension. We will use Word to generate the appropriate file extension for us when we save the file. Here are these two variables: <\/p>\n We now use the -as<\/strong> operator to turn the string “Microsoft.Office.Interop.Word.WdSaveFormat” into a type. We use [ref]<\/strong> so that we can pass this type by reference, which is a requirement of the Word saveas method<\/a>. By creating the WdSaveFormat<\/strong> type we gain access WdSaveFormat enumerations<\/a>, which makes our script easier to write, easier to maintain, and easier to read. This line of code is seen here: <\/p>\n When we want to work with Word, we need to create an instance of the Word.Application<\/strong> object. The methods and properties (members) of the Word.Application<\/strong> object are documented in MSDN at this location<\/a>. To create the Word.Application<\/strong> object, we use the New-Object<\/strong> cmdlet and the -comobject<\/strong> parameter. We give it the program ID of Word.Application<\/strong>, and store the resulting object in the $word<\/strong> variable. Now we want to see what we are doing, so we set the Word applications visible<\/strong> property to $true<\/strong>. This code starts Word and makes it visible, but does not add any documents to it: <\/p>\n Once we have made the Word application visible, we are presented with an empty Word application. This is something that is seldom seen because when you start Word normally, it opens a blank document. Gaze upon this rare event: <\/p>\n <\/p>\n Now we need to add a document to Word. To do this, we use the documents object<\/a> and call the add<\/strong> method. What is interesting with this is that we obtain the documents<\/strong> object (which is a collection) by querying the documents property<\/a> from the application<\/strong> object. When we have the documents object, we can call the add<\/strong> method. We could easily write this code in two lines as shown here: <\/p>\n![\"Spacer\"](\"https:\/\/devblogs.microsoft.com\/scripting\/wp-content\/uploads\/sites\/29\/2019\/05\/spacer.gif\")
![\"Hey,](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/a-for-powertip.jpg\" "\\"Hey,")
<\/p>\n![\"Image](\"http:\/\/img.microsoft.com\/library\/media\/1033\/technet\/images\/scriptcenter\/qanda\/hsg\/hey1111\/hsg_wordwmi1.jpg\")
<\/p>\n$class = \"Win32_Bios\"\n$path = \"C:\\fso\\bios\"\n\n[ref]$SaveFormat = \"microsoft.office.interop.word.WdSaveFormat\" -as [type]\n$word = New-Object -ComObject word.application\n$word.visible = $true\n$doc = $word.documents.add()\n$selection = $word.selection\n$selection.typeText(\"This is the bios information\")\n$selection.TypeParagraph()\nGet-WmiObject -class $class | \nOut-String |\nForEach-Object { $selection.typeText($_) }\n$doc.saveas([ref] $path, [ref]$saveFormat::wdFormatDocument)\n$word.quit()<\/pre>\n$class = \"Win32_Bios\"\n$path = \"C:\\fso\\bios\"<\/pre>\n
[ref]$SaveFormat = \"microsoft.office.interop.word.WdSaveFormat\" -as [type]<\/pre>\n
$word = New-Object -ComObject word.application\n$word.visible = $true<\/pre>\n
![\"Image](\"http:\/\/img.microsoft.com\/library\/media\/1033\/technet\/images\/scriptcenter\/qanda\/hsg\/hey1111\/hsg_wordwmi2.jpg\")
<\/p>\n$collectionDocuments = $word.documents\n$doc = $collectionDocuments.add()<\/pre>\n
![\"Image](\"http:\/\/img.microsoft.com\/library\/media\/1033\/technet\/images\/scriptcenter\/qanda\/hsg\/hey1111\/hsg_wordwmi3.jpg\")
<\/p>\n