<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Command-Line on Anything About IT</title><link>https://www.verboon.info/tags/command-line/</link><description>Recent content in Command-Line on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 24 Mar 2013 14:48:33 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/command-line/index.xml" rel="self" type="application/rss+xml"/><item><title>How to install System Center 2012 Endpoint Protection on a standalone client</title><link>https://www.verboon.info/2013/03/how-to-install-system-center-2012-endpoint-protection-on-a-standalone-client/</link><pubDate>Sun, 24 Mar 2013 14:48:33 +0000</pubDate><guid>https://www.verboon.info/2013/03/how-to-install-system-center-2012-endpoint-protection-on-a-standalone-client/</guid><description>&lt;p&gt;Suppose you have a need to deploy System Center 2012 Endpoint Protection to a number of clients that later run in standalone mode, meaning that they are not joined to a domain, can’t be managed by SCCM and operate in a network that is not connected to your corporate network.&lt;/p&gt;
&lt;p&gt;The installation source &lt;strong&gt;scepinstall.exe&lt;/strong&gt; for the System Center Endpoint Protection agent is stored within the SCCM 2012 client installation folder on the SCCM 2012 SP1 server under C:\Program Files\Microsoft Configuration Manager\Client. Within that same directory we also find the endpoint protection default policy settings stored as &lt;strong&gt;ep_defaultpolicy.xml&lt;/strong&gt;, but we won’t use this , as we are going to prepare our own policy that meets our requirements for a standalone unmanaged client.&lt;/p&gt;</description></item><item><title>Script for finding Executables that are command-line programs</title><link>https://www.verboon.info/2012/05/script-for-finding-executables-that-are-command-line-programs/</link><pubDate>Wed, 02 May 2012 22:11:57 +0000</pubDate><guid>https://www.verboon.info/2012/05/script-for-finding-executables-that-are-command-line-programs/</guid><description>&lt;p&gt;I recently came across a FREE utility called &lt;a href="http://helgeklein.com/free-tools/iscommandlineapp/"&gt;IsCommandLineApp&lt;/a&gt; from &lt;a href="http://helgeklein.com/"&gt;Helge Klein&lt;/a&gt;,  a little command-line tool that can be used to determine whether a specific executable is a command-line program. To run this against multiple executables manually is a kind of a pain, so I decided to write a PowerShell script that runs IsCommandLineapp against a defined Folder and all it’s subfolders.&lt;/p&gt;
&lt;p&gt;
 &lt;img src="images/image_thumb.png" alt="image"&gt;

&lt;/p&gt;
&lt;p&gt;To run the script, first download the IsCommandLineApp from &lt;a href="http://helgeklein.com/free-tools/iscommandlineapp/%22"&gt;here&lt;/a&gt;) and then edit the variable &lt;strong&gt;$IsCommandLineApp&lt;/strong&gt; so that it points to the location where you have stored the tool. If you want to search through another folder than C:\Windows change the variable &lt;strong&gt;$StartPath&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Copying command-line tools from Windows into WinPE, don&amp;rsquo;t forget the localization files</title><link>https://www.verboon.info/2012/04/copying-command-line-tools-from-windows-into-winpe-dont-forget-the-localization-files/</link><pubDate>Thu, 12 Apr 2012 20:43:07 +0000</pubDate><guid>https://www.verboon.info/2012/04/copying-command-line-tools-from-windows-into-winpe-dont-forget-the-localization-files/</guid><description>&lt;p&gt;To keep the footprint of WinPE as small as possible many services or tools usually found within a full Windows installation are not available within WinPE. So if you need a command-line tool from Windows such as icacls.exe you just copy the executable into your WinPE sources and you’re done.&lt;/p&gt;
&lt;p&gt;But hey, when booting into WinPE and executing icacls.exe, nothing is displayed, the command itself however works.&lt;/p&gt;
&lt;p&gt;
 &lt;img src="images/image_thumb3.png" alt="image"&gt;

&lt;/p&gt;
&lt;p&gt;Unfortunately just copying the the executable alone isn’t enough since it is language neutral, you must also copy the corresponding localization file. These can be found under C;\Windows\System32&amp;lt;locale&amp;gt; so for English C;\Windows\System32\en-US. For icacls.exe we would copy the file ICacls.exe.mui into the WinPE’s \Windows\System32\en-US folder.&lt;/p&gt;</description></item><item><title>ToolTip: Boxcutter &amp;ndash; A Command line screenshot utility</title><link>https://www.verboon.info/2011/11/tooltip-boxcutter-a-command-line-screenshot-utility/</link><pubDate>Tue, 08 Nov 2011 22:57:10 +0000</pubDate><guid>https://www.verboon.info/2011/11/tooltip-boxcutter-a-command-line-screenshot-utility/</guid><description>&lt;p&gt;Boxcutter is a simple command line-driven screenshot program for Microsoft Windows. Below you find a short script I wrote that will take a screenshot of the full screen every 20 seconds until 100 screenshots are saved.&lt;/p&gt;
&lt;p&gt;One usage scenario (I plan to use) is where you are running an OS installation within a Virtual Machine and want to take screenshots of the various stages of the installation without having to manually take a screenshot. You would just let the script run, it will probably produce more screenshots as needed, but these then can be deleted manually afterwards.&lt;/p&gt;</description></item><item><title>Cannot start Microsoft Outlook. Cannot open the Outlook window</title><link>https://www.verboon.info/2009/11/cannot-start-microsoft-outlook-cannot-open-the-outlook-window/</link><pubDate>Fri, 20 Nov 2009 18:33:24 +0000</pubDate><guid>https://www.verboon.info/2009/11/cannot-start-microsoft-outlook-cannot-open-the-outlook-window/</guid><description>&lt;p&gt;…….That’s the message i got yesterday when I wanted to start Outlook 2007. I solved the problem after having found the solution on &lt;a href="http://www.msoutlook.info/question/268"&gt;MSOutlook.info&lt;/a&gt; Running the following command fixed the issue.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;outlook.exe /resetnavpane&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;A complete reference of all the Microsoft Outlook 2007 command-line switches can be found &lt;a href="http://office.microsoft.com/en-us/outlook/HP012185891033.aspx?pid=CH100788811033"&gt;here&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>