{"id":51673,"date":"2009-12-31T00:01:00","date_gmt":"2009-12-31T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2009\/12\/31\/hey-scripting-guy-how-can-i-create-a-disk-space-report-in-a-word-document\/"},"modified":"2009-12-31T00:01:00","modified_gmt":"2009-12-31T00:01:00","slug":"hey-scripting-guy-how-can-i-create-a-disk-space-report-in-a-word-document","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/hey-scripting-guy-how-can-i-create-a-disk-space-report-in-a-word-document\/","title":{"rendered":"Hey, Scripting Guy! How Can I Create a Disk Space Report in a Word Document?"},"content":{"rendered":"

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

 <\/p>\n

\"Hey,<\/font><\/p>\n

Hey, Scripting Guy! We are having problems with several of our servers at work. Several of them were upgraded from Windows NT 4, and as a result, we are constantly running into disk space issues on the C: drive. I would rather manage the problem than take the servers down and rebuild them because we already have budget to replace them next quarter. Therefore, in the meantime, I have to baby-sit 30 servers. <\/p>\n

This whole thing came to a head last week when one server blue-screened because of no disk space on the C: drive when the page file was unable to grow. Now the pointy-headed boss wants a daily disk space report for the 30 servers. I wrote a quick Windows PowerShell script that will report the disk space for the 30 servers, and gave him the script (hoping in vain that he would run it). But he wants an actual Microsoft Word document report. I found your How Can I Create a Microsoft Word Document from WMI Information?<\/font><\/a> article, but it does not really do what I need to accomplish. I would appreciate it if you would help me out. <\/p>\n

— CA<\/p>\n

\n

 <\/p>\n<\/p>\n

\"Hey,Hello CA, <\/p>\n

Microsoft Scripting Guy Ed Wilson here. I am listening to UFO<\/a> on my Zune HD, and sipping a nice cup of Earl Grey tea with a cinnamon stick and a splash of milk in it. I am also munching on one of my carefully guarded ANZAC biscuits. Probably because of the cold weather, I have been reviewing some of the pictures I took during my last dive trip to Key Largo, Florida, with my scuba club. The following picture makes me want to grab my gear and dive in.<\/p>\n

\"Image<\/p>\n

\n

 <\/p>\n<\/p>\n

CA, writing WMI information to a Microsoft Word document by using a Windows PowerShell script is easier than stepping off a dive boat and swimming with sharks.<\/p>\n

The first thing we do in the WriteDiskSpaceToWord.ps1 script is assign a few strings to some variables. The Win32_Volume<\/b> WMI class is used to obtain the free disk space from the C: drive. The Win32_Volume<\/b> WMI class was first introduced in Windows Server 2003, and if you have to query Windows XP or earlier computers, you will need to use the Win32_LogicalDisk<\/b> WMI class. The $path<\/b> variable holds the location that will store the complete disk space report. You will need to edit the script to point to a location that is available to your computer, and you can name the report file anything that makes sense to you. The $computers<\/b> variable stores an array of computer names and will need to be modified for your specific network. If you have more than ten computers, you will probably want to store your computer names in a text file and use the Get-Content<\/b> cmdlet to read the file. You could still store the results in the $comptuers<\/b> variable, as seen here:<\/p>\n

$computers = Get-Content –path c:fsocomputerlist.txt<\/p>\n

<\/font><\/span><\/p>\n

The complete variable initialization section of the WriteDiskSpaceToWord.ps1 script is seen here:<\/p>\n

$class = “Win32_Volume”<\/p>\n

<\/font><\/span><\/p>\n

$path = “C:fsoVolume.docx”<\/p>\n

<\/font><\/span><\/p>\n

$computers = “Win7-pc”,”MrEd1″,”HyperV”<\/p>\n

<\/font><\/span><\/p>\n

To save the Microsoft Word document, use an instance of the wdSaveFormat enumeration<\/font><\/a>. The wdSaveFormat<\/b> enumeration is documented on MSDN and is used to determine the type of document that will be saved. <\/p>\n

I used the wdSaveFormat<\/b> enumeration to allow me to convert a folder full of Microsoft Word documents into PDF files in a recent Hey, Scripting Guy! post<\/font><\/a>. <\/p>\n

After the WdSaveFormat<\/b> enumeration is created, it is saved in the $SaveFormat<\/b> reference variable. This is seen here. <\/p>\n

 <\/span>[ref]$SaveFormat = “microsoft.office.interop.word.WdSaveFormat” -as [type]<\/p>\n

<\/font><\/span><\/p>\n

For more information about using the [ref]<\/b> type, refer to<\/span> this Hey, Scripting Guy! post<\/font><\/a>. To create the new Microsoft Word document, you will need to first create the Word.Application<\/b> object. To do this, use the New-Object<\/b> cmdlet and specify the –ComObject<\/b> parameter while using the word.application<\/b> program ID. Store the resulting application object in the $word<\/b> variable, as seen here. If you want to see the Word document while the WMI query is writing to it, you can set the visible<\/b> property of the application object to $true<\/b>. After you have the script working on your network, you will probably want to change this value to $false<\/b>. <\/p>\n

<\/span><\/p>\n

$word = New-Object -ComObject word.application<\/p>\n

<\/font><\/span><\/p>\n

$word.visible = $true<\/p>\n

<\/font><\/span><\/p>\n

It is time create a new Microsoft Word document. To do this, use the add<\/b> method from the documents<\/b> collection. Store the resulting document object in the $doc<\/b> variable. You also need to create a selection<\/b> object by using the selection<\/b> property from the application<\/b> object. Store the resultant selection<\/b> object in the $selection<\/b> variable. This section of the script is seen here:<\/p>\n

$doc = $word.documents.add()<\/p>\n

<\/font><\/span><\/p>\n

$selection = $word.selection<\/p>\n

<\/font><\/span><\/p>\n

To walk through the array of computer names that is stored in the $computers<\/b> variable, use the Foreach<\/b> statement:<\/p>\n

Foreach($computer in $Computers)<\/p>\n

<\/font><\/span><\/p>\n

{<\/p>\n

<\/font><\/span><\/p>\n

Use the TypeText<\/b> method from the selection<\/b> object to write the heading for each computer report. Each computer name is stored in the $computer<\/b> variable. The `r`n<\/b> special character sequence generates a carriage return and a line feed in the Microsoft Word document. The `t<\/b> will tab over the line of text by one tab. This section of the script is seen here:<\/p>\n

 <\/span>$selection.typeText(“Disk Space Report for $Computer `r`n `tDisk C gigabytes: “)<\/p>\n

<\/font><\/span><\/p>\n

Use the Get-WmiObject<\/b> cmdlet to query the Win32_Volume<\/b> WMI class. The .NET format specifier<\/font><\/a> command causes the resulting free disk space to be returned to two decimal places. The GB<\/b> is an administrative constant that converts numbers to gigabytes. The resulting WMI object is piped to the Out-String<\/b> cmdlet so that the results can be displayed as text. This command is seen here:<\/p>\n

 <\/span>“{0:n2}” -f ((Get-WmiObject -Class Win32_Volume -ComputerName $computer `<\/p>\n

<\/font><\/span><\/p>\n

  <\/span>-Filter “DriveLetter = ‘c:'”).FreeSpace\/1GB) | <\/p>\n

<\/font><\/span><\/p>\n

 <\/span>Out-String |<\/p>\n

<\/font><\/span><\/p>\n

To use a command in the middle of a pipeline, use the ForEach-Object<\/b> cmdlet. This requirement exists even if there is only one item on the pipeline. The typeText<\/b> method is used to write the current information on the pipeline. The typeParagraph method from the selection object<\/font><\/a> writes a blank paragraph. This is seen here:<\/p>\n

 <\/span>ForEach-Object { $selection.typeText($_)}<\/p>\n

<\/font><\/span><\/p>\n

 <\/span>$selection.TypeParagraph()<\/p>\n

<\/font><\/span><\/p>\n

}<\/p>\n

<\/font><\/span><\/p>\n

The saveas<\/b> method from the document<\/b> object needs the path to the file and a wdSaveFormat<\/b> enumeration value. In this example, the wdFormatDocument<\/b> enumeration value is used, which will save to the default word format. For Microsoft Word 2007, this is a DOCX format file. When you are done, make sure you call the quit<\/b> method from the application<\/b> object to release the word application object from memory:<\/p>\n

$doc.saveas($path, $saveFormat::wdFormatDocument)<\/p>\n

<\/font><\/span><\/p>\n

$word.quit()<\/p>\n

<\/font><\/span><\/p>\n

When the WriteDiskSpaceToWord.ps1 script runs, the Microsoft Word document shown in the following image is created. <\/p>\n

\"Image<\/p>\n

\n

 <\/p>\n<\/p>\n

CA, that is all there is to using Microsoft Word to store information you gathered from WMI. This concludes our Microsoft Word Week articles. Join us tomorrow for Quick-Hits Friday.  <\/span><\/p>\n

If you want to know exactly what we will be covering tomorrow, follow us on Twitter<\/a> or Facebook<\/a>. If you have any questions, send e-mail to us at scripter@microsoft.com<\/font><\/a> or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n

\n

 <\/p>\n<\/p>\n

Ed Wilson and Craig Liebendorfer, Scripting Guys<\/p>\n

<\/span><\/b><\/p>\n

 <\/p><\/p>\n","protected":false},"excerpt":{"rendered":"

    Hey, Scripting Guy! We are having problems with several of our servers at work. Several of them were upgraded from Windows NT 4, and as a result, we are constantly running into disk space issues on the C: drive. I would rather manage the problem than take the servers down and rebuild them […]<\/p>\n","protected":false},"author":595,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[216,84,49,3,4,12,45,6],"class_list":["post-51673","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-disk-drives-and-volumes","tag-microsoft-word","tag-office","tag-scripting-guy","tag-scripting-techniques","tag-storage","tag-windows-powershell","tag-wmi"],"acf":[],"blog_post_summary":"

    Hey, Scripting Guy! We are having problems with several of our servers at work. Several of them were upgraded from Windows NT 4, and as a result, we are constantly running into disk space issues on the C: drive. I would rather manage the problem than take the servers down and rebuild them […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/51673","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\/595"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=51673"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/51673\/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=51673"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=51673"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=51673"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}