{"id":16371,"date":"2010-11-29T00:01:00","date_gmt":"2010-11-29T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2010\/11\/29\/learn-when-to-write-powershell-scripts-and-when-not-to\/"},"modified":"2010-11-29T00:01:00","modified_gmt":"2010-11-29T00:01:00","slug":"learn-when-to-write-powershell-scripts-and-when-not-to","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/learn-when-to-write-powershell-scripts-and-when-not-to\/","title":{"rendered":"Learn When to Write PowerShell Scripts and When Not To"},"content":{"rendered":"

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

Summary:<\/span><\/b> Microsoft Scripting Guy Ed Wilson discusses when to write a Windows PowerShell script and when not to write a script.<\/span><\/p>\n

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

\"Hey,<\/span>Hey, Scripting Guy! I am wondering why everyone is talking about Windows PowerShell. To me it seems to simply be another scripting language, and I do not know why I should worry about it. I already know VBScript, and my friends use Perl. So what is the big deal?<\/span><\/p>\n

— BW<\/span><\/p>\n

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

\"Hey,<\/span>Hello BW, Microsoft Scripting Guy Ed Wilson here. If Windows PowerShell were simply a new scripting language I would not be as excited as I am about the product. The truth of the matter is that Windows PowerShell is both an interactive command shell in addition to a scripting language. <\/span><\/p>\n

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

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

Portions of today’s Hey, Scripting Guy! Blog post are adapted from material in my book Windows PowerShell 2.0 Best Practices<\/span><\/i><\/a>, published by Microsoft Press in December 2009. <\/span><\/p>\n

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

Not everything in Windows PowerShell 2.0 has to be scripted. This was true in Windows PowerShell 1.0 and it is very true in Windows PowerShell 2.0. People coming from a VBScript background or a Perl background frequently feel they must write a script. But a tremendous amount of work can be done from the command line, without the need for writing a script. <\/span><\/p>\n

One of the more powerful things that can be done with Windows PowerShell is the ability to use language statements from the command line. The for<\/i><\/b> statement lets you control looping operations that would have required creating a script in other languages. To facilitate work from the command line, Windows PowerShell will let you create incomplete commands on one line, and to continue them to the next line. When you are finished, you press the enter key a second time. The command seen here sends a ping command to each IP address in the range of 192.168.2.1 through 192.168.2.10. <\/span><\/p>\n

PS C:\\> for($i = 1 ; $i -le 10 ; $i++)
>> { Test-Connection -Destination 192.168.2.$i -Count 1 -ErrorAction Silentlycontinue |
>> Format-Table –property Address, statusCode, ResponseTime -AutoSize }
>><\/p>\n

Address     <\/span>statusCode ResponseTime
——-     <\/span>———- ————
192.168.2.1          <\/span>0            <\/span>1
Address     <\/span>statusCode ResponseTime
——-     <\/span>———- ————
192.168.2.3          <\/span>0            <\/span>2
Address     <\/span>statusCode ResponseTime
——-     <\/span>———- ————
192.168.2.5          <\/span>0            <\/span>0
Address      <\/span>statusCode ResponseTime
——-      <\/span>———- ————
192.168.2.10          <\/span>0           <\/span>10<\/span><\/span><\/p>\n

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

The command above could have been much shorter by taking advantage of several economies provided by the Windows PowerShell syntax such as using aliases, partial parameters and positional arguments. <\/span><\/p>\n

When talking about Windows PowerShell scripts, the first thing to realize is that in its most basic form a Windows PowerShell script is a collection of PowerShell commands stored in a file with a specific extension. If you do not want to do that, you can have a text file with a collection of commands, and store them as a text file as seen in the following figure.<\/span><\/p>\n

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

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

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

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

By using Windows PowerShell, you can easily read the commands.txt text file, and execute the commands. To do this, you use the Get-Content<\/b> cmdlet to retrieve the commands in the text file. The default parameter for the Get-Content<\/b> cmdlet is the path<\/i> parameter, and when you are working from the command line, you do not have to supply it if you do not want to do so. The path can be a local path or even a Universal Naming Convention (UNC) path as long as you have rights to read the text file. The best way to use this technique is to pipeline the results to the Invoke-Expression<\/b> cmdlet. Each command that streams across the pipeline from the Get-Content<\/b> cmdlet will be executed in turn as it arrives to the Invoke-Expression<\/b> cmdlet. This is seen here:<\/span><\/p>\n

Get-Content -Path C:\\fso\\Commands.txt | Invoke-Expression<\/span><\/span><\/p>\n

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

The results are seen in the following figure.<\/span><\/p>\n

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

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

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

When you are using the Windows PowerShell remoting features against an untrusted domain, it is rather easy to become confused when you use cmdlets such as Get-Content<\/b>. The path<\/i> parameter that is used refers to a path that is local to the target computer, not a path that is local to the launching computer. In the example that follows the path c:\\fso\\commands.txt<\/i> points to a text file that is named commands.tx<\/i>t that must reside in the fso<\/i> folder on the C:\\<\/i> drive of a computer named Sydney<\/i> in the Woodbridgebank<\/i>.com<\/i> domain. If the commands.txt file is not found in that location, the error seen here will be emitted. <\/span><\/p>\n

PS C:\\> invoke-command -ComputerName sydney.woodbridgebank.com -Credential admin
istrator@woodbridgebank.com -ScriptBlock {get-content -Path C:\\fso\\Commands.txt
| Invoke-Expression}
Invoke-Command : Cannot find path ‘C:\\fso\\Commands.txt’ because it does not exi
st.
At line:1 char:15
+ invoke-command <<<<  <\/span>-ComputerName sydney.woodbridgebank.com -Credential admi
nistrator@woodbridgebank.com -ScriptBlock {get-content -Path C:\\fso\\Commands.tx
t | Invoke-Expression}
    <\/span>+ CategoryInfo          <\/span>: ObjectNotFound: (C:\\fso\\Commands.txt:String) [Ge
   <\/span>t-Content], ItemNotFoundException
    <\/span>+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetCo
   <\/span>ntentCommand<\/span><\/span><\/p>\n

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

You might think that you could use an UNC path and point to the commands.txt file on the launching computer. Because the remote domain is un-trusted, there is no security context that enables the remote command to access the file system of the local computer. When the command that is expressed in the ScriptBlock<\/i> parameter is evaluated, it is evaluated in the context of the target computer which in this case is the <\/span>Sydney.WoodBridgeBank.Com<\/i> computer. The local computer which is the launching point for the command is <\/span>Vista.NWTraders.com<\/i> and as there is no trust relationship between the two domains, there are no credentials that can be supplied to enable the command to run. The results of trying to run the command are seen here. <\/span><\/span><\/p>\n

PS C:\\> invoke-command -ComputerName sydney.woodbridgebank.com -Credential admin
istrator@woodbridgebank.com -ScriptBlock {get-content -Path ‘\\\\vista\\fso\\Command
s.txt’ | Invoke-Expression}
Invoke-Command : Cannot find path ‘\\\\vista\\fso\\Commands.txt’ because it does no
t exist.
At line:1 char:15
+ invoke-command <<<<  <\/span>-ComputerName sydney.woodbridgebank.com -Credential admi
nistrator@woodbridgebank.com -ScriptBlock {get-content -Path ‘\\\\vista\\fso\\Comma
nds.txt’ | Invoke-Expression}
    <\/span>+ CategoryInfo          <\/span>: ObjectNotFound: (\\\\vista\\fso\\Commands.txt:String
   <\/span>) [Get-Content], ItemNotFoundException
    <\/span>+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetCo
   <\/span>ntentCommand<\/span><\/span><\/p>\n

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

The part that can seem to be confusing is that the Get-Content<\/b> command works just fine when it is run alone. In working on a computer named Vista<\/i> that has a folder named fso<\/i> that contains a text file that is named Commands.txt<\/i> the command completes successfully when it is ensconced with single quotes. This is seen here. <\/span><\/p>\n

PS C:\\> Get-Content -Path ‘\\\\vista\\fso\\Commands.txt’
Get-Service -Name bits -ComputerName vista
Get-Process -Name explorer -ComputerName berlin
Get-EventLog -LogName application -Newest 1 -ComputerName berlin,vista
Invoke-Command -ComputerName Berlin { Get-Date }
Get-Date<\/span><\/span><\/p>\n

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

But this is to be expected as the logged on user has rights to the folder, and can therefore use the Get-Content<\/b> cmdlet to read a UNC path to the command.txt<\/i> file. <\/span><\/p>\n

You could map a drive on the remote domain, and copy the file from your local computer to the appropriate folder on the remote server. You would, of course, be required to open additional ports in the Windows Firewall which, depending on your network configuration, may or may not be an acceptable solution. If you decide to use this route, you could use Windows PowerShell to perform the configuration changes as shown here. <\/span><\/p>\n

PS C:\\> Invoke-Command -ComputerName Sydney.WoodBridgeBank.Com -Credential Admin
istrator@WoodbridgeBank.com -ScriptBlock { netsh advfirewall firewall set rule g
roup=”File and Printer Sharing” new enable=Yes }<\/p>\n

Updated 28 rule(s).
Ok.<\/span><\/span><\/p>\n

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

After you have enabled the firewall exception, you can then map a drive using the GUI or the Net Use<\/b> command from within Windows PowerShell, or any of the other programmatic methods. After you have mapped the drive, you could then copy the commands.txt<\/i> file to the remote server by using the Copy-Item<\/b> cmdlet as seen here. <\/span><\/p>\n

When you use Copy-Item<\/b> to copy an item to a mapped drive, you have to consider the structure of the mapped drive. It is quite common to map a drive to a share on a remote computer. The remote share is almost invariably a share of a folder, and not a complete drive. Because your remote drive is a map point of a single folder, it will change the destination. The z:<\/i> drive in the command which follows is a share of the fso<\/i> folder on the remote server. The destination parameter is to the root of the mapped drive, and not to z:\\fso<\/i>. <\/span><\/p>\n

Copy-Item -Path C:\\fso\\Commands.txt -Destination z:<\/span><\/span><\/p>\n

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

You could now use the commands.txt<\/i> directly in the Windows PowerShell command as seen here. <\/span><\/p>\n

PS C:\\> invoke-command -ComputerName Sydney.WoodbridgeBank.com -Credential admin
istrator@WoodBridgeBank.com -ScriptBlock { Get-Content -Path C:\\fso\\Commands.txt
 <\/span>| Invoke-Expression }<\/span><\/span><\/p>\n

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

One solution to the dilemma of mapping drives is to use Remote Desktop. Remote Desktop will enable you to access local resources if you decide to make them available in your session. By selecting Remote Desktop \/ Options \/ Local Resources<\/b>, <\/b>you can choose to enable printer connections, clip board access, and local drives to be available within the Remote Desktop Protocol (RDP) session. You can access Remote Desktop by going to Start \/ All Programs \/ Accessories<\/b> and selecting Remote Desktop Connection<\/b>. There is a problem with using remote desktop. It must first be enabled. If it has not been previously enabled, you will be greeted with the friendly access denied message seen in the following figure. <\/span><\/p>\n

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

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

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

To enable Remote Desktop access, on Windows 2008 and Windows 2008 R2, select Configure Remote Desktop<\/b> from Server Manager<\/b>. If you are running Windows Vista or Windows 7 you select Remote Settings<\/b> from Control Panel \/ System<\/b>. In any case, the System Properties<\/b> dialog appears, and you have to select the Remote<\/b> tab which is shown in the following figure. The Remote Desktop options are seen in the bottom half of the screen and present three choices. By default Remote Desktop connections are not allowed to the computer. The safest choice is to enable connections only from computers that are running Remote Desktop with Network Level Authentication. You are also able to specify which users will be allowed to make the connection. By default, members of the Domain Administrators group will be permitted to make connections. <\/span><\/p>\n

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

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

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

After you have enabled Remote Desktop an exception is automatically created to allow for RDP traffic through the Windows Firewall. It is still a good idea to double-check to make sure the exception was permitted.<\/span> <\/span><\/p>\n

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

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

BW, that is all there is to working interactively with Windows PowerShell. To Script or Not to Script week will continue tomorrow when I will talk about how to work with command history. <\/span><\/p>\n

I invite you to follow me on Twitter<\/span><\/a> or Facebook<\/span><\/a>. If you have any questions, send email to me at scripter@microsoft.com<\/span><\/a> or post them on the Official Scripting Guys Forum<\/span><\/a>. See you tomorrow. Until then, peace.<\/span><\/p>\n

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

Ed Wilson, Microsoft Scripting Guy<\/span><\/b><\/p>\n","protected":false},"excerpt":{"rendered":"

   Summary: Microsoft Scripting Guy Ed Wilson discusses when to write a Windows PowerShell script and when not to write a script.   Hey, Scripting Guy! I am wondering why everyone is talking about Windows PowerShell. To me it seems to simply be another scripting language, and I do not know why I should worry […]<\/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":[51,3,4,45],"class_list":["post-16371","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-getting-started","tag-scripting-guy","tag-scripting-techniques","tag-windows-powershell"],"acf":[],"blog_post_summary":"

   Summary: Microsoft Scripting Guy Ed Wilson discusses when to write a Windows PowerShell script and when not to write a script.   Hey, Scripting Guy! I am wondering why everyone is talking about Windows PowerShell. To me it seems to simply be another scripting language, and I do not know why I should worry […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/16371","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=16371"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/16371\/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=16371"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=16371"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=16371"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}