Freigeben über

PowerShell Script to Create a Sysinternals Suite INF File Installer

  • Artikel

A few months ago I created a script for the Elevation PowerToys blog that I thought might be of interest to readers of this blog.

More than a few of our customers have included the Sysinternals tools in their Windows Server builds.  My current customer is one.  So to automate the installation of the Sysinternals tools in their MDT task sequence, I used an INF file that I had created to install the Sysinternals Suite as part of a download for a TechNet Magazine article of mine.  I had manually updated it several times as the contents of the Sysinternals Suite was updated.

Since updating this manually could be tedious, I decided to script the whole process of downloading, unzipping, and creating the INF file.  You can read about and download the script here.

To use the resulting folder of files as an MDT application source, In the Deployment Workbench create a new Application using the folder containing the Sysinternals Suite expanded files and the INF file (the Extracted subfolder of the Updated date folder) as the source.  Use an install command line like the following:

For Windows Vista and higher:

"%SystemRoot%\System32\InfDefaultInstall.exe" "<app folder path>\Install_SysinternalsSuite.inf"

For Windows XP/Server 2003:

    "%SystemRoot%\System32\rundll32.exe" setupapi,InstallHinfSection DefaultInstall 132 "<app folder path>\Install_SysinternalsSuite.inf"

This Sysinternals Suite installation can be uninstalled using the entry in the Add/Remove Programs control panel (called Programs and Features on Windows Vista and higher).

 

Disclaimer: The information on this site is provided "AS IS" with no warranties, confers no rights, and is not supported by the authors or Microsoft Corporation. Use of included script samples are subject to the terms specified in the Terms of Use .

This post was contributed by Michael Murgolo, a Senior Consultant with Microsoft Services - U.S. East Region

Comments

  • Anonymous
    October 26, 2015
    It seems the site was changed in a way that breaks the script. The URL starts with HTTPS now instead of HTTP