<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Extract on Anything About IT</title><link>https://www.verboon.info/tags/extract/</link><description>Recent content in Extract on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 09 Sep 2019 18:18:44 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/extract/index.xml" rel="self" type="application/rss+xml"/><item><title>Extract ConfigMgr Script Status Results with PowerShell</title><link>https://www.verboon.info/2019/09/extract-configmgr-script-status-results-with-powershell/</link><pubDate>Mon, 09 Sep 2019 18:18:44 +0000</pubDate><guid>https://www.verboon.info/2019/09/extract-configmgr-script-status-results-with-powershell/</guid><description>&lt;p&gt;
 &lt;img src="images/wlEmoticon-smile.png" alt="Smile"&gt;

&lt;/p&gt;
&lt;p&gt;During a recent customer engagement I had to collect the size of user profiles across a large number of devices. I was first thinking of using a script that would collect the information we need, store it into a custom WMI table and then collect the data using ConfigMgr hardware inventory, but since we only needed a one time snapshot of this information I decided against that idea. The next option would be to go old school and run the script through Group Policy processing and store the results in a central location, but hey it’s 2019, no more logon scripts please And then the idea came up to run the script on the target clients via ConfigMgr.&lt;/p&gt;</description></item><item><title>Tip: How to extract Office 2010 Customization file content (MSP)</title><link>https://www.verboon.info/2011/11/tip-how-to-extract-office-2010-customization-file-content-msp/</link><pubDate>Tue, 01 Nov 2011 22:33:56 +0000</pubDate><guid>https://www.verboon.info/2011/11/tip-how-to-extract-office-2010-customization-file-content-msp/</guid><description>&lt;p&gt;If you have an Office 2010 installation that is customized by use of the Office customization tool the customizations are stored within an MSP file that uses Extensible Markup Language (XML) format.&lt;/p&gt;
&lt;p&gt;To extract the content you can use a vbscript that Microsoft has published on TechNet - &lt;a href="http://technet.microsoft.com/en-us/library/cc179027.aspx"&gt;View Office Customization Tool output in Office 2010&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Simply copy paste the code provided within the article into a file called ExtractOctXml.vbs and then run the following command to extract the content:&lt;/p&gt;</description></item><item><title>ToolTip: Updated version of lessmsi (View extract MSI content)</title><link>https://www.verboon.info/2011/10/tooltip-updated-version-of-lessmsi-view-extract-msi-content/</link><pubDate>Sat, 29 Oct 2011 15:15:20 +0000</pubDate><guid>https://www.verboon.info/2011/10/tooltip-updated-version-of-lessmsi-view-extract-msi-content/</guid><description>&lt;p&gt;There is an updated version of the less misérables utility a utility with a graphical user interface and a command line interface that can be used to view and extract the contents of an MSI file.&lt;/p&gt;
&lt;p&gt;
 &lt;img src="images/2011-10-29-17h12_30_thumb.png" alt="2011-10-29 17h12_30"&gt;

&lt;/p&gt;
&lt;p&gt;The updated version now has explorer integration, that can be easily enabled / disabled via the preference menu setting.&lt;/p&gt;
&lt;p&gt;
 &lt;img src="images/2011-10-29-17h11_58_thumb.png" alt="2011-10-29 17h11_58"&gt;

&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Download lessmsi from [here](http://code.google.com/p/lessmsi/).
&lt;/code&gt;&lt;/pre&gt;</description></item><item><title>Extracting CAB files from Microsoft Update Standalone Package (MSU)</title><link>https://www.verboon.info/2010/09/extracting-cab-files-from-microsoft-update-standalone-package-msu/</link><pubDate>Sat, 04 Sep 2010 13:08:01 +0000</pubDate><guid>https://www.verboon.info/2010/09/extracting-cab-files-from-microsoft-update-standalone-package-msu/</guid><description>&lt;p&gt;When manually downloading a Microsoft Security Update or hotfix for Windows 7 (Vista) you typically get a file with an MSU file extension. A file with an MSU extension is a Microsoft Update Standalone package.&lt;/p&gt;
&lt;p&gt;Microsoft Update Standalone Packages are installed through the Windows Update Standalone Installer WUSA.EXE which is located in the  C:\Windows\system32 folder. If you need to install many updates you could create a script like the one below.&lt;/p&gt;</description></item><item><title>ToolTip &amp;ndash; less mis&amp;eacute;rables (MSI file extractor)</title><link>https://www.verboon.info/2009/04/tooltip-less-misrables-msi-file-extractor/</link><pubDate>Fri, 03 Apr 2009 17:59:53 +0000</pubDate><guid>https://www.verboon.info/2009/04/tooltip-less-misrables-msi-file-extractor/</guid><description>&lt;p&gt;Today I found a nice utility that allows you to easily extract individual files from an MSI package. The tool is called “&lt;a href="http://blogs.pingpoet.com/overflow/archive/2005/06/02/2449.aspx"&gt;less miséreables&lt;/a&gt;”. it’s a kind of a funny name, but it does the job.&lt;/p&gt;
&lt;p&gt;To extract a file, simply launch the utility, select the file(s) you want to extract and click on the extract button.&lt;/p&gt;
&lt;p&gt;
 &lt;img src="images/image-thumb2.png" alt="image"&gt;

&lt;/p&gt;
&lt;p&gt;Of course the same can be done by using the MSIEXEC command from the command line as shown below, but that does extract all files.&lt;/p&gt;</description></item></channel></rss>