http://powershell.com/cs/blogs/tips/atom.aspxCommunity Server2010-02-23T08:00:00Z/cs/blogs/tips/archive/2010/03/15/export-csv-with-culture-specific-delimiter.aspx2010-03-15T13:00:00Z2010-03-15T13:00:00Z<p>Export-CSV used to only support the comma as separator, which caused problems on non-U.S.-systems. In PowerShell v.2, with -useCulture you can have Export-CSV use whatever delimiter is the right one, depending on your culture.</p> <p>There is only one caveat: You should never combine -useCulture with -Encoding Unicode. This seems to be a bug where the culture-specific delimiter is not inserted correctly, which causes importing applications, such as Export, to ignore it.</p> <p>You should use -Encoding UTF8 instead if you want to preserve special characters in your export:</p> <div class="pscode"><span class="verbnoun">Get-Process</span> | <span class="verbnoun">Select-Object</span> Name, Company | <br /> <span class="verbnoun">Export-CSV</span> <span class="modifier">-useCulture</span> <span class="modifier">-Encoding</span> UTF8 <span class="var">$home</span>\<span class="namespace">export.csv</span></div> <p><a href="http://twitter.com/home/?status=RT+%40PowerTip+Export+Culture-Specific+CSV+from+%23PowerShell+http%3A%2F%2Fbit.ly%2FaK8jvt" target="twitter"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a href="http://twitter.com/home/?status=RT+%40PowerTip+Export+Culture-Specific+CSV+from+%23PowerShell+http%3A%2F%2Fbit.ly%2FaK8jvt" target="twitter">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=4683" width="1" height="1">ps1http://powershell.com/cs/members/ps1/default.aspx/cs/blogs/tips/archive/2010/03/12/stopping-the-pipeline.aspx2010-03-12T14:00:00Z2010-03-12T14:00:00Z<p>Usually, once a pipeline runs, you cannot stop it prematurely, even if you already received the information you were seeking. Simply use this filter to stop a pipeline:</p> <div class="pscode"><span class="keyword">filter</span> <span class="verbnoun">Stop-Pipeline</span>([<span class="optional">scriptblock</span>]<span class="var">$condition</span> <span class="op">=</span> {<span class="var">$true</span>}) {<br /><span class="var">$_</span><br /><span class="keyword">if</span> (<span class="op">&amp;</span> <span class="var">$condition</span>) {<span class="keyword">continue</span>}<br />}</div> <p>Now, to stop a pipeline, use it like this:</p> <div class="pscode"><span class="verbnoun">Get-EventLog</span> Application | <span class="verbnoun">Stop-Pipeline</span> { <span class="var">$_</span>.<span class="method">InstanceID</span> <span class="op">-gt</span> 10000}</div> <p>This will get you all Application events until you find one with an InstanceID of greater than 10,000. The pipeline exists once it is found.</p> <p>If you&#39;d like to use this technique inside a script, you will need to make sure Stop-Pipeline does not stop your entire script. You can do that by embedding the pipeline inside a dummy loop:</p> <div class="pscode"><span class="var">$result</span> <span class="op">=</span> <span class="keyword">do</span> { <br /><span class="verbnoun">Get-EventLog</span> Application | <span class="verbnoun">Stop-Pipeline</span> { <span class="var">$_</span>.<span class="method">InstanceID</span> <span class="op">-gt</span> 10000} <br />} <span class="keyword">while</span> (<span class="var">$false</span>)</div> <p><a href="http://twitter.com/home/?status=RT+%40PowerTip+Stopping+the+%23PowerShell+Pipeline+http%3A%2F%2Fbit.ly%2F9dRKvB" target="twitter"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a href="http://twitter.com/home/?status=RT+%40PowerTip+Stopping+the+%23PowerShell+Pipeline+http%3A%2F%2Fbit.ly%2F9dRKvB" target="twitter">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=4682" width="1" height="1">ps1http://powershell.com/cs/members/ps1/default.aspx/cs/blogs/tips/archive/2010/03/11/creating-large-dummy-files-with-net.aspx2010-03-11T14:00:00Z2010-03-11T14:00:00Z<p>You can always resort to the underlying .NET framework whenever the functionality you need isn&#39;t available through a cmdlet. </p> <p>The following code is a very fast way to generate really large test files:</p> <div class="pscode"><span class="var">$path</span> <span class="op">=</span> <span class="string">&quot;$env:temp\testfile.txt&quot;</span><br /><span class="var">$file</span> <span class="op">=</span> [<span class="namespace">io.file</span>]::<span class="method">Create</span>(<span class="var">$path</span>)<br /><span class="var">$file</span>.<span class="method">SetLength</span>(1gb)<br /><span class="var">$file</span>.<span class="method">Close</span>()<br /><span class="verbnoun">Get-Item</span> <span class="var">$path</span></div> <p><a href="http://twitter.com/home/?status=RT+%40PowerTip+Large+Files+with+.NET+from+%23PowerShell+http%3A%2F%2Fbit.ly%2FbYmRZw" target="twitter"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a href="http://twitter.com/home/?status=RT+%40PowerTip+Large+Files+with+.NET+from+%23PowerShell+http%3A%2F%2Fbit.ly%2FbYmRZw" target="twitter">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=4681" width="1" height="1">ps1http://powershell.com/cs/members/ps1/default.aspx/cs/blogs/tips/archive/2010/03/10/creating-large-dummy-files.aspx2010-03-10T14:00:00Z2010-03-10T14:00:00Z<p>Sometimes, it is more efficient to use existing console tools rather than PowerShell cmdlets. For example here is a way to create a large file for load tests:</p> <div class="pscode">fsutil file createnew <span class="var">$env:temp</span>\<span class="namespace">dummy.bin</span> (1gb)</div> <p>However, you should note that fsutil requires admin privileges.</p> <p><a href="http://twitter.com/home/?status=RT+%40PowerTip+Large+Files+with+fsutil+from+%23PowerShell+http%3A%2F%2Fbit.ly%2F9NCO1L" target="twitter"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a href="http://twitter.com/home/?status=RT+%40PowerTip+Large+Files+with+fsutil+from+%23PowerShell+http%3A%2F%2Fbit.ly%2F9NCO1L" target="twitter">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=4680" width="1" height="1">ps1http://powershell.com/cs/members/ps1/default.aspx/cs/blogs/tips/archive/2010/03/09/running-powershell-scripts-as-scheduled-task.aspx2010-03-09T14:00:00Z2010-03-09T14:00:00Z<p>If you have jobs that need to execute regularly, you can manage them with a PowerShell script and make it a scheduled task:</p> <div class="pscode">schtasks <span class="op">/</span>CREATE <span class="op">/</span>TN CheckHealthScript <span class="op">/</span>TR <span class="string">&quot;powershell.exe `</span><br /><span class="string"> -noprofile -executionpolicy Unrestricted `</span><br /><span class="string"> -file %public%\checkhealth.ps1&quot;</span> <span class="op">/</span>IT <span class="op">/</span>RL HIGHEST <span class="op">/</span>SC DAILY</div> <p>To remove the scheduled task, specify the name you assigned:</p> <div class="pscode">schtasks <span class="op">/</span>DELETE <span class="op">/</span>TN CheckHealthScript</div> <p><a href="http://twitter.com/home/?status=RT+%40PowerTip+Running+%23PowerShell+Scripts+as+Scheduled+Task+http%3A%2F%2Fbit.ly%2F9jzFFi" target="twitter"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a href="http://twitter.com/home/?status=RT+%40PowerTip+Running+%23PowerShell+Scripts+as+Scheduled+Task+http%3A%2F%2Fbit.ly%2F9jzFFi" target="twitter">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=4679" width="1" height="1">ps1http://powershell.com/cs/members/ps1/default.aspx/cs/blogs/tips/archive/2010/03/08/launching-a-powershell-script-externally.aspx2010-03-08T14:00:00Z2010-03-08T14:00:00Z<p>To launch a PowerShell script outside of the PowerShell console (i.e. as scheduled task or as a link), prepend the script path with this:</p> <div class="pscode"><span class="namespace">Powershell.exe</span> <span class="modifier">-noprofile</span> <span class="modifier">-executionpolicy</span> Bypass c:\<span class="namespace">pathtoscript.ps1</span></div> <p>As you can see, in v.2 Microsoft added an -executionPolicy parameter, which allows you to override whatever execution policy is set by default. However, your call cannot override this setting if the execution policy was defined by a group policy.</p> <p><a href="http://twitter.com/home/?status=RT+%40PowerTip+Launching+a+%23PowerShell+Script+Externally+http%3A%2F%2Fbit.ly%2FafKTdl" target="twitter"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a href="http://twitter.com/home/?status=RT+%40PowerTip+Launching+a+%23PowerShell+Script+Externally+http%3A%2F%2Fbit.ly%2FafKTdl" target="twitter">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=4678" width="1" height="1">ps1http://powershell.com/cs/members/ps1/default.aspx/cs/blogs/tips/archive/2010/03/05/accessing-profile-scripts.aspx2010-03-05T14:00:00Z2010-03-05T14:00:00Z<p>Profile scripts are executed automatically when PowerShell starts. The paths to these scripts can be found in $profile:</p> <div class="pscode"><span class="var">$profile</span> | gm <span class="op">*</span>Host<span class="op">*</span> | <span class="op">%</span> { <span class="var">$_</span>.<span class="method">Name</span> } | <span class="op">%</span> {<br /> <span class="var">$rv</span> <span class="op">=</span> @{}; <span class="var">$rv</span>.<span class="method">Name</span> <span class="op">=</span> <span class="var">$_</span><br /> <span class="var">$rv</span>.<span class="method">Path</span> <span class="op">=</span> <span class="var">$profile</span>.<span class="var">$_</span><br /> <span class="var">$rv</span>.<span class="method">Exists</span><span class="op">=</span> (<span class="verbnoun">Test-Path</span> <span class="var">$profile</span>.<span class="var">$_</span>)<br /> <span class="verbnoun">New-Object</span> PSObject <span class="modifier">-Property</span> <span class="var">$rv</span> <br />} | <span class="verbnoun">Format-Table</span> <span class="modifier">-AutoSize</span></div> <div class="psoutput">Name Path Exists<br />---- ---- ------<br />AllUsersAllHosts C:\Windows\...ps1 True<br />AllUsersCurrentHosts C:\Windows\...ps1 False<br />CurrentUserAllHosts C:\Users\...ps1 True<br />CurrentUserCurrentHost C:\Users\...ps1 True</div> <p><a href="http://twitter.com/home/?status=RT+%40PowerTip+Accessing+%23PowerShell+Profile+Scripts+http%3A%2F%2Fbit.ly%2F9eZYgc" target="twitter"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a href="http://twitter.com/home/?status=RT+%40PowerTip+Accessing+%23PowerShell+Profile+Scripts+http%3A%2F%2Fbit.ly%2F9eZYgc" target="twitter">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=4677" width="1" height="1">ps1http://powershell.com/cs/members/ps1/default.aspx/cs/blogs/tips/archive/2010/03/04/listing-execution-policies.aspx2010-03-04T14:00:00Z2010-03-04T14:00:00Z<p>In PowerShell v.2, there are multiple execution policies. You should use this to view and check the settings:</p> <div class="pscode"><span class="verbnoun">Get-ExecutionPolicy</span> <span class="modifier">-List</span></div> <p><a href="http://twitter.com/home/?status=RT+%40PowerTip+Listing+%23PowerShell+Execution+Policies+http%3A%2F%2Fbit.ly%2FcFdbO2" target="twitter"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a href="http://twitter.com/home/?status=RT+%40PowerTip+Listing+%23PowerShell+Execution+Policies+http%3A%2F%2Fbit.ly%2FcFdbO2" target="twitter">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=4676" width="1" height="1">ps1http://powershell.com/cs/members/ps1/default.aspx/cs/blogs/tips/archive/2010/03/03/closing-a-program-gracefully.aspx2010-03-03T14:00:00Z2010-03-03T14:00:00Z<p>When you use Stop-Process to kill a program, it will stop instantaneously. The user will get no chance to save unsaved documents:</p> <div class="pscode"><span class="verbnoun">Get-Process</span> Notepad | <span class="verbnoun">Stop-Process</span></div> <p>Try a more graceful way by using an internal .NET method, which then acts as if someone closed the program window. If the content has not been saved, a dialog opens and asks for a choice:</p> <div class="pscode"><span class="verbnoun">Get-Process</span> Notepad | <br /> <span class="verbnoun">Foreach-Object</span> { <span class="var">$_</span>.<span class="method">CloseMainWindow</span>() | <span class="verbnoun">Out-Null</span> }</div> <p><a href="http://twitter.com/home/?status=RT+%40PowerTip+Closing+a+Program+Gracefully+from+%23PowerShell+http%3A%2F%2Fbit.ly%2FdbuAVr" target="twitter"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a href="http://twitter.com/home/?status=RT+%40PowerTip+Closing+a+Program+Gracefully+from+%23PowerShell+http%3A%2F%2Fbit.ly%2FdbuAVr" target="twitter">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=4675" width="1" height="1">ps1http://powershell.com/cs/members/ps1/default.aspx/cs/blogs/tips/archive/2010/03/02/stopping-a-program-whenever-you-feel-like-it.aspx2010-03-02T14:00:00Z2010-03-02T14:00:00Z<p>When you launch a program using Start-Process with -passThru, you will get back the process object representing the started program. You can then use this object later to kill the program whenever necessary.</p> <div class="pscode"><span class="var">$notepad</span> <span class="op">=</span> <span class="verbnoun">Start-Process</span> notepad <span class="modifier">-passthru</span><br /><span class="verbnoun">Start-Sleep</span> 2<br /><span class="verbnoun">Stop-Process</span> <span class="modifier">-inputObject</span> <span class="var">$notepad</span></div> <p><a href="http://twitter.com/home/?status=RT+%40PowerTip+" target="twitter"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a href="http://twitter.com/home/?status=RT+%40PowerTip+" target="twitter">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=4674" width="1" height="1">ps1http://powershell.com/cs/members/ps1/default.aspx/cs/blogs/tips/archive/2010/03/01/use-choice-to-prompt-for-input.aspx2010-03-01T14:00:00Z2010-03-01T14:00:00Z<p>PowerShell can run native console applications, which can be very helpful. For example, you should take a closer look at CHOICE.EXE, which will prompt you for information:</p> <div class="pscode">Choice <span class="op">/</span>N <span class="op">/</span>C:123 <span class="op">/</span>M <span class="string">&quot;Enter a number between 1 and 3!&quot;</span><br /><span class="string">&quot;Your choice: $LASTEXITCODE&quot;</span></div> <p>This will get you a simple Y/N prompt:</p> <div class="pscode">Choice <span class="op">/</span>N <span class="op">/</span>C:YN <span class="op">/</span>M <span class="string">&quot;Do you agree (Y/N)?&quot;</span><br /><span class="string">&quot;Your answer: $LASTEXITCODE&quot;</span></div> <p><a href="http://twitter.com/home/?status=RT+%40PowerTip+Use+CHOICE+to+Prompt+for+Input+in+%23PowerShell+http%3A%2F%2Fbit.ly%2FcBasGI" target="twitter"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a href="http://twitter.com/home/?status=RT+%40PowerTip+Use+CHOICE+to+Prompt+for+Input+in+%23PowerShell+http%3A%2F%2Fbit.ly%2FcBasGI" target="twitter">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=4673" width="1" height="1">ps1http://powershell.com/cs/members/ps1/default.aspx/cs/blogs/tips/archive/2010/02/26/launching-programs-maximized.aspx2010-02-26T14:00:00Z2010-02-26T14:00:00Z<p>Start-Process has a parameter called -WindowStyle. With it, you can control the window size of the application you launch. You should use this line to launch notepad maximized:</p> <div class="pscode"><span class="verbnoun">Start-Process</span> notepad <span class="modifier">-WindowStyle</span> Maximized</div> <p>Supported arguments are Maximized, Minimized, Normal, and Hidden. Be sure to watch out with Hidden! You should only use it for programs that do not require user interaction.</p> <p><a href="http://twitter.com/home/?status=RT+%40PowerTip+Launching%20Programs%20Maximized%20from%20#PowerShell%20http://bit.ly/9f9voL" target="twitter"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a href="http://twitter.com/home/?status=RT+%40PowerTip+Launching%20Programs%20Maximized%20from%20#PowerShell%20http://bit.ly/9f9voL" target="twitter">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=4672" width="1" height="1">ps1http://powershell.com/cs/members/ps1/default.aspx/cs/blogs/tips/archive/2010/02/25/wait-for-programs.aspx2010-02-25T14:00:00Z2010-02-25T14:00:00Z<p>PowerShell launches Windows applications asynchronously. It only waits for the console application so you should use -wait if you want to launch a Windows application and wait for it until it finishes:</p> <div class="pscode"><span class="verbnoun">Start-Process</span> notepad <span class="modifier">-wait</span></div> <p><a href="http://twitter.com/home/?status=RT+%40PowerTip+Wait+for+Programs+Launched+from+%23PowerShell+http%3A%2F%2Fbit.ly%2F9a7KfV" target="twitter"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a href="http://twitter.com/home/?status=RT+%40PowerTip+Wait+for+Programs+Launched+from+%23PowerShell+http%3A%2F%2Fbit.ly%2F9a7KfV" target="twitter">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=4671" width="1" height="1">ps1http://powershell.com/cs/members/ps1/default.aspx/cs/blogs/tips/archive/2010/02/24/open-current-folder-in-your-explorer.aspx2010-02-24T14:00:00Z2010-02-24T14:00:00Z<p>If you are stuck in the console and would like to move over to the Explorer GUI, the next line opens your current folder in an Explorer window:</p> <div class="pscode">explorer .</div> <p>Of course, this only works when the current folder is set to a folder in your file system.</p> <p><a href="http://twitter.com/home/?status=RT+%40PowerTip+Open+Current+Folder+in+Your+Explorer+from+%23PowerShell+http%3A%2F%2Fbit.ly%2FbVtCJ2" target="twitter"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a href="http://twitter.com/home/?status=RT+%40PowerTip+Open+Current+Folder+in+Your+Explorer+from+%23PowerShell+http%3A%2F%2Fbit.ly%2FbVtCJ2" target="twitter">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=4670" width="1" height="1">ps1http://powershell.com/cs/members/ps1/default.aspx/cs/blogs/tips/archive/2010/02/23/search-for-localized-keywords.aspx2010-02-23T14:00:00Z2010-02-23T14:00:00Z<p>Finding the appropriate command for a task is important. With a little trick, PowerShell can help you. Have a look:</p> <div class="pscode"><span class="keyword">function</span> ??(<span class="var">$keywords</span>) { <span class="verbnoun">Get-Help</span> <span class="op">*</span> | <br /> ? { <span class="var">$_</span>.<span class="method">description</span> <span class="op">-like</span> <span class="string">&quot;*$keywords*&quot;</span> } | <br /> <span class="verbnoun">Select-Object</span> Name, Synopsis }</div> <p>This function called &quot;??&quot; searches Help content for any keyword you specify. Since Help files are localized, you can happily use keywords in your own language (the language your window uses, to be exact). For example, on German systems, you could search for &quot;Drucker&quot; and get back everything related to &quot;printer&quot;:</p> <div class="pscode">?? drucker<br />?? zufall</div> <p><a href="http://twitter.com/home/?status=RT+%40PowerTip+Search+for+Localized+%23PowerShell+Keywords+http%3A%2F%2Fbit.ly%2FaPALnE" target="twitter"><img src="http://powershell.com/cs/Themes/powershell/images/ps/twitter_32x32.png" alt="Twitter This Tip!" style="vertical-align:middle;border:0px;" /></a> <a href="http://twitter.com/home/?status=RT+%40PowerTip+Search+for+Localized+%23PowerShell+Keywords+http%3A%2F%2Fbit.ly%2FaPALnE" target="twitter">ReTweet this Tip!</a></p><div style="clear:both;"></div><img src="http://powershell.com/cs/aggbug.aspx?PostID=4669" width="1" height="1">ps1http://powershell.com/cs/members/ps1/default.aspx