{"id":16501,"date":"2010-11-15T00:01:00","date_gmt":"2010-11-15T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2010\/11\/15\/use-powershell-cmdlets-to-administer-windows-remotely\/"},"modified":"2010-11-15T00:01:00","modified_gmt":"2010-11-15T00:01:00","slug":"use-powershell-cmdlets-to-administer-windows-remotely","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/use-powershell-cmdlets-to-administer-windows-remotely\/","title":{"rendered":"Use PowerShell Cmdlets to Administer Windows Remotely"},"content":{"rendered":"


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

Summary:<\/span><\/b> Microsoft Scripting Guy Ed Wilson shows how to use Windows PowerShell cmdlets to administer remote computers.<\/span><\/p>\n

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

\"Hey,Hey, Scripting Guy! I need to be able to work with remote computers. Is there a good way to do this with Windows PowerShell?<\/span><\/p>\n

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

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

\"Hey,Hello DN, Microsoft Scripting Guy Ed Wilson here. I was recently reading Shakespeare’s The Tragedy of Hamlet, Prince of Denmark<\/span><\/i><\/a>  <\/span>again when I ran across his famous soliloquy. One reason for reading Shakespeare, for me, is to try to expand my horizons beyond geekdom; unfortunately, it is not working. I am a geek at heart. As my eyes scanned across the pages of Bevington<\/span><\/a> drawing me deeper and deeper into the world of intrigue, revenge, and scandal, I still could not still my inner geek. I could not help myself; I began to translate Hamlet into Windows PowerShell. Here is the tragic Hamlet’s soliloquy. <\/span><\/p>\n

PS C:\\> $2b = “hamlet”
PS C:\\> $question = ($2b -OR !($2b))
PS C:\\> $question
True
PS C:\\><\/span><\/span><\/p>\n

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

One thing to be aware of, the parentheses around the question are not required. In addition to using parentheses for grouping, I also like to use them to make code easier to read. Easier to read, is of course, sometimes a matter of personal preference. The question, without parentheses appears here.<\/span><\/p>\n

$question = $2b -OR !$2b<\/span><\/span><\/p>\n

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

Speaking of Denmark, the following figure is a picture I took of the Copenhagen Opera House<\/span><\/a>. I was able to attend the ballet there one night while I was in Copenhagen, Denmark<\/span><\/a> teaching a Windows PowerShell class. <\/span><\/p>\n

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

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

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

The cool thing about the Copenhagen Opera House is that it is on an island, and I had to take a water taxi to access it. The Royal Danish Theatre is in the central part of Copenhagen. The new opera house is more remote.<\/span><\/p>\n

Speaking of remote, DN, Windows PowerShell 2.0<\/span><\/a> incorporates a strong remoting<\/span><\/a> solution that lets you work remotely. The problem is that remoting will not work with the default configuration of Windows. There are basically two kinds of remoting included with Windows PowerShell 2.0.<\/span><\/p>\n

The first kind of remoting, uses the computername<\/i> parameter. In Windows PowerShell 1.0 only one cmdlet contained a computername <\/i>parameter; that cmdlet was the Get-WmiObject<\/span><\/a><\/b> cmdlet. The remoting capability that is exposed with the Get-WmiObject<\/b> cmdlet is the same remoting capability that is native in Windows Management Instrumentation (WMI<\/span><\/a>). It relies on DCOM, and in order to use it, you have to open ports in the Windows Firewall<\/span><\/a>. In addition, you must be a member of the Local Administrators<\/b> group on the remote computer (although it is possible to change the security permissions for WMI to enable a non-admin access). <\/span><\/p>\n

To find the Windows PowerShell cmdlets that natively support remoting I only have to use the Get-Help<\/b> cmdlet<\/span><\/span><\/a>. By specifying a value of computername<\/i> for the parameter <\/i>parameter of the Get-Help<\/b> Windows PowerShell cmdlet I can find all the cmdlets that have a parameter named computername<\/i>. The command and associated output is here.<\/span><\/p>\n

PS C:\\> Get-Help * -Parameter computername | Format-Table name, synopsis -AutoSize -Wrap<\/span><\/span><\/p>\n

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

Name                 <\/span>Synopsis<\/span><\/span><\/p>\n

—-                 <\/span>——–<\/span><\/span><\/p>\n

Get-WinEvent   <\/span>      <\/span>Gets events from event logs and event tracing log files on loca<\/span><\/span><\/p>\n

                     <\/span>l and remote computers.<\/span><\/span><\/p>\n

Get-Counter          <\/span>Gets performance counter data from local and remote computers.<\/span><\/span><\/p>\n

Test-WSMan           <\/span>Tests whether the WinRM service is running on a local or remote<\/span><\/span><\/p>\n

                      <\/span>computer.<\/span><\/span><\/p>\n

Invoke-WSManAction   <\/span>Invokes an action on the object that is specified by the Resour<\/span><\/span><\/p>\n

                     <\/span>ce URI and by the selectors.<\/span><\/span><\/p>\n

Connect-WSMan        <\/span>Connects to the WinRM service on a remote computer.<\/span><\/span><\/p>\n

Disconnect-WSMan     <\/span>Disconnects the client from the WinRM service on a remote compu<\/span><\/span><\/p>\n

                     <\/span>ter.<\/span><\/span><\/p>\n

Get-WSManInstance    <\/span>Displays management information for a resource instance specifi<\/span><\/span><\/p>\n

                     <\/span>ed by a Resource URI.<\/span><\/span><\/p>\n

Set-WSManInstance    <\/span>Modifies the management information that is related to a resour<\/span><\/span><\/p>\n

                     <\/span>ce.<\/span><\/span><\/p>\n

Remove-WSManInstance Deletes a management resource instance.<\/span><\/span><\/p>\n

New-WSManInstance    <\/span>Creates a new instance of a management resource.<\/span><\/span><\/p>\n

Invoke-Command       <\/span>Runs commands on local and remote computers.<\/span><\/span><\/p>\n

New-PSSession        <\/span>Creates a persistent connection to a local or remote computer.<\/span><\/span><\/p>\n

Get-PSSession        <\/span>Gets the Windows PowerShell sessions (PSSessions) in the curren<\/span><\/span><\/p>\n

                     <\/span>t session.<\/span><\/span><\/p>\n

Remove-PSSession     <\/span>Closes one or more Windows PowerShell sessions (PSSessions).<\/span><\/span><\/p>\n

Receive-Job          <\/span>Gets the results of the Windows PowerShell background jobs in t<\/span><\/span><\/p>\n

                     <\/span>he current session.<\/span><\/span><\/p>\n

Enter-PSSession      <\/span>Starts an interactive session with a remote computer.<\/span><\/span><\/p>\n

Get-EventLog         <\/span>Gets the events in an event log, or a list of the event logs, o<\/span><\/span><\/p>\n

                     <\/span>n the local or remote computers.<\/span><\/span><\/p>\n

Clear-EventLog       <\/span>Deletes all entries from specified event logs on the local or r<\/span><\/span><\/p>\n

                     <\/span>emote computers.<\/span><\/span><\/p>\n

Write-EventLog       <\/span>Writes an event to an event log.<\/span><\/span><\/p>\n

Limit-EventLog       <\/span>Sets the event log properties that limit the size of the event<\/span><\/span><\/p>\n

                     <\/span>log and the age of its entries.<\/span><\/span><\/p>\n

Show-EventLog        <\/span>Displays the event logs of the local or a remote computer in Ev<\/span><\/span><\/p>\n

                     <\/span>ent Viewer.<\/span><\/span><\/p>\n

New-EventLog         <\/span>Creates a new event log and a new event source on a local or re<\/span><\/span><\/p>\n

                     <\/span>mote computer.<\/span><\/span><\/p>\n

Remove-EventLog      <\/span>Deletes an event log or unregisters an event source.<\/span><\/span><\/p>\n

Get-WmiObject        <\/span>Gets instances of Windows Management Instrumentation (WMI) clas<\/span><\/span><\/p>\n

                     <\/span>ses or information about the available classes.<\/span><\/span><\/p>\n

Invoke-WmiMethod     <\/span>Calls Windows Management Instrumentation (WMI) methods.<\/span><\/span><\/p>\n

Get-Process          <\/span>Gets the processes that are running on the local computer or a<\/span><\/span><\/p>\n

                     <\/span>remote computer.<\/span><\/span><\/p>\n

Remove-WmiObject     <\/span>Deletes an instance of an existing Windows Management Instrumen<\/span><\/span><\/p>\n

               <\/span>      <\/span>tation (WMI) class.<\/span><\/span><\/p>\n

Register-WmiEvent    <\/span>Subscribes to a Windows Management Instrumentation (WMI) event.<\/span><\/span><\/p>\n

Get-Service          <\/span>Gets the services on a local or remote computer.<\/span><\/span><\/p>\n

Set-Service          <\/span>Starts, stops, and suspends a service, and changes its properti<\/span><\/span><\/p>\n

                     <\/span>es.<\/span><\/span><\/p>\n

Set-WmiInstance      <\/span>Creates or updates an instance of an existing Windows Managemen<\/span><\/span><\/p>\n

                     <\/span>t Instrumentation (WMI) class.<\/span><\/span><\/p>\n

Get-HotFix           <\/span>Gets the hotfixes that have been applied to the local and remot<\/span><\/span><\/p>\n

                     <\/span>e computers.<\/span><\/span><\/p>\n

Test-Connection      <\/span>Sends ICMP echo request packets (“pings”) to one or more comput<\/span><\/span><\/p>\n

                     <\/span>ers.<\/span><\/span><\/p>\n

Restart-Computer     <\/span>Restarts (“reboots”) the operating system on local and remote c<\/span><\/span><\/p>\n

                     <\/span>omputers.<\/span><\/span><\/p>\n

Stop-Computer        <\/span>Stops (shuts down) local and remote computers.<\/span><\/span><\/p>\n

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

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

PS C:\\><\/span><\/span><\/p>\n

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

As you can see, many of the Windows PowerShell cmdlets that have a computername<\/i> parameter are related to either wsman<\/b>, or to working with Windows PowerShell sessions. If I remove those cmdlets from the output, a more streamlined list results. The command I used to do this is shown here where I used the question mark alias (?) for the Where-Object<\/b> cmdlet.<\/span><\/p>\n

PS C:\\> Get-Help * -Parameter computername | ? { $_.name -notmatch “WSMan” -AND $_.Na
me -notmatch “PSSession”}<\/p>\n

Name                              <\/span>Category  <\/span>Synopsis
—-                              <\/span>——–  <\/span>——–
Get-WinEvent                      <\/span>Cmdlet    <\/span>Gets events from event logs and event…
Get-Counter                       <\/span>Cmdlet    <\/span>Gets performance counter data from lo…
Invoke-Command                    <\/span>Cmdlet    <\/span>Runs commands on local and remote com…
Receive-Job                       <\/span>Cmdlet    <\/span>Gets the results of the Windows Power…
Get-EventLog                      <\/span>Cmdlet    <\/span>Gets the events in an event log, or a…
Clear-EventLog                    <\/span>Cmdlet    <\/span>Deletes all entries from specified ev…
Write-EventLog                    <\/span>Cmdlet    <\/span>Writes an event to an event log.
Limit-EventLog                    <\/span>Cmdlet    <\/span>Sets the event log properties that li…
Show-EventLog                     <\/span>Cmdlet    <\/span>Displays the event logs of the local …
New-EventLog                      <\/span>Cmdlet    <\/span>Creates a new event log and a new eve…
Remove-EventLog                   <\/span>Cmdlet    <\/span>Deletes an event log or unregisters a…
Get-WmiObject                     <\/span>Cmdlet    <\/span>Gets instances of Windows Management …
Invoke-WmiMethod                  <\/span>Cmdlet    <\/span>Calls Windows Management Instrumentat…
Get-Process                       <\/span>Cmdlet    <\/span>Gets the processes that are running o…
Remove-WmiObject                  <\/span>Cmdlet    <\/span>Deletes an instance of an existing Wi…
Register-WmiEvent                 <\/span>Cmdlet    <\/span>Subscribes to a Windows Management In…
Get-Service                       <\/span>Cmdlet    <\/span>Gets the services on a local or remot…
Set-Service                       <\/span>Cmdlet    <\/span>Starts, stops, and suspends a service…
Set-WmiInstance                   <\/span>Cmdlet    <\/span>Creates or updates an instance of an …
Get-HotFix                        <\/span>Cmdlet    <\/span>Gets the hotfixes that have been appl…
Test-Connection                   <\/span>Cmdlet    <\/span>Sends ICMP echo request packets (“pin…
Restart-Computer                  <\/span>Cmdlet    <\/span>Restarts (“reboots”) the operating sy…
Stop-Computer                     <\/span>Cmdlet    <\/span>Stops (shuts down) local and remote c…<\/p>\n

PS C:\\><\/span><\/span><\/p>\n

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

Some cmdlets let you specify credentials. This enables you to use a different user account than the one that is currently logged on. This is seen here.<\/span><\/p>\n

PS C:\\> Get-WinEvent -LogName application -MaxEvents 1 -ComputerName ex1 -Credential<\/span><\/span><\/p>\n

nwtraders\\administrator<\/span><\/span><\/p>\n

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

TimeCreated           <\/span>ProviderName                           <\/span>Id Message<\/span><\/span><\/p>\n

———–           <\/span>————          <\/span>                 <\/span>— ——-<\/span><\/span><\/p>\n

11\/9\/2010 11:54:14 AM MSExchange ADAccess                  <\/span>2080 Process MAD.EXE (…<\/span><\/span><\/p>\n

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

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

PS C:\\><\/span><\/span><\/p>\n

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

When the command runs, a dialog box is displayed to enable me to type the credentials. The dialog box is seen in the following figure.<\/span><\/p>\n

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

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

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

Other cmdlets, such as Get-Service<\/b> or Get-Process<\/b> do not have a credential<\/i> parameter. Therefore, the command impersonates the user who is logged on. This is illustrated here.<\/span><\/p>\n

PS C:\\> Get-Service -ComputerName hyperv -Name bits<\/span><\/span><\/p>\n

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

Status   <\/span>Name               <\/span>DisplayName<\/span><\/span><\/p>\n

——   <\/span>—-               <\/span>———–<\/span><\/span><\/p>\n

Running  <\/span>bits               <\/span>Background Intelligent Transfer Ser…<\/span><\/span><\/p>\n

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

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

PS C:\\><\/span><\/span><\/p>\n

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

However, by holding down the Shift Key<\/b> and right-clicking on the Windows PowerShell icon<\/b>, I bring up an action menu that enables me to run the program as a different user. This menu is seen in the following figure.<\/span><\/p>\n

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

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

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

The credential dialog box, as seen in the following figure, appears.<\/span><\/p>\n

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

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

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

By using the Run As Different User<\/b> dialog box, alternative credentials can be used for Windows PowerShell cmdlets that do not support the credential<\/i> parameter. <\/p>\n

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

DN, that is all there is to using the Windows PowerShell cmdlets that support remoting. Remoting week will continue tomorrow when I will talk about how to use Windows PowerShell remoting. <\/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> <\/span><\/p>\n

 <\/p><\/p>\n","protected":false},"excerpt":{"rendered":"

Summary: Microsoft Scripting Guy Ed Wilson shows how to use Windows PowerShell cmdlets to administer remote computers.   Hey, Scripting Guy! I need to be able to work with remote computers. Is there a good way to do this with Windows PowerShell? — DN   Hello DN, Microsoft Scripting Guy Ed Wilson here. I was […]<\/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,57,3,4,45],"class_list":["post-16501","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-getting-started","tag-remoting","tag-scripting-guy","tag-scripting-techniques","tag-windows-powershell"],"acf":[],"blog_post_summary":"

Summary: Microsoft Scripting Guy Ed Wilson shows how to use Windows PowerShell cmdlets to administer remote computers.   Hey, Scripting Guy! I need to be able to work with remote computers. Is there a good way to do this with Windows PowerShell? — DN   Hello DN, Microsoft Scripting Guy Ed Wilson here. I was […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/16501","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=16501"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/16501\/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=16501"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=16501"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=16501"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}