Skip to main content

How to access remote computers with PowerShell?

Windows PowerShell V2 allows you to access remote computers and execute PowerShell commands on those remote clients. The following steps illustrate how to create a session with a single client.

For every client that we will be remotely accessing, we need to run the command:

  • Winrm quickconfig
  • Press Y at all prompts.

This will open the ports on the firewall that we need open for remote management.

Now, on the copmuter that will be making the remote connection, type:

  • Enter-PSSession –computerName ComputerName

In my case, the ComputerName parameter is MCT-1. Once the session is established, your prompt will look like this:

[MCT-1]: PS C:\Users\Administrator\Documentss>

Go ahead and type Get-Service. You should notice that what is returned is the services from the remote client.

Type Exit to return to your local client.

Now what about multiple sessions?

Once you have run WinRM QuickConfig on multiple clients, you can set up multiple sessions.

My current setup has me on a computer named MCT-Win7-1 I want to set up a session to two other clients, MCT-1 and MCT-Win7-2. I type in this command:

New-PSSession MCT1, MCT-Win7-2

What comes back are the session numbers. With this method, you can only have on session open at a time. To access one one of the sessions, type Enter-PSSession –ID and then the session number.

Once you have comleted your work with that client, type Exit.

You can get a list of all open sessions by typing Get-PSSession.

So how do you run a command in all sessions? First lets save the current sessions in a variable.

$PSList = Get-PSSession

Now, we are going to use the Invoke-Command commandlet.

Invoke-Command –session $PSList –scriptblock {Get-Service}

From here you will receive a list of the data returned.

You can close the sessions in one of two ways.

Remove-PSSession – ID SessionNumber

Or

Remove-PSSession –session $PSList

Comments

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.