Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>From what I can tell...</p> <p>The PSSessions you created live on "MyServerName" and, for the duration of the session you first created them, will also be returned by Get-PSSession (with no arguments, in the PowerShell window on the box you're remoting FROM). When you close the session they are created in, the sessions are no longer on your computer. This is why Get-PSSession doesn't return anything when you close and open a new PowerShell window. They never "lived" on your computer, they are remote sessions, however, they were <em>in scope</em> in your original PowerShell window because that is the local scope you created them in. </p> <p>If your sessions are still on MyServerName, as it seems they are due to the error you mention about max sessions, then typing the following command should list them:</p> <pre><code>Get-PSSession -ComputerName MyServerName </code></pre> <p>If you wanted to reconnect them all in your existing session/window, you could do:</p> <pre><code>Get-PSSession -ComputerName MyServerName | Connect-PSSession </code></pre> <p>To remove them all, enabling you to create new PSSessions to MyServerName </p> <pre><code>Get-PSSession -ComputerName MyServerName | Remove-PSSession </code></pre> <p>Looking a bit further in the docs, all sessions do not live indefinitely when you close your PowerShell window. See:</p> <blockquote> <p><code>Get-Help about_Remote_Disconnected_Sessions -ShowWindow</code></p> <p>partial excerpt (with emphasis mine):</p> <p>If you close (exit) the session in which a PSSession was created while commands are running in the PSSession, Windows PowerShell maintains the PSSession in the Disconnected state on the remote computer. <strong>If you close (exit) the session in which a PSSession was created, but no commands are running in the PSSession, Windows PowerShell does not attempt to maintain the PSSession.</strong></p> </blockquote> <p>From what I can see, sessions that aren't a) disconnected, or b) busy running a command, are discarded when you close the PowerShell window you started the PSSessions from. Additionally, the documentation does seem to mention there are also timeouts (which probably depend on PSSessionConfigurations on the server, but I don't know anything about those yet myself (other than they exist).</p> <p>This was a good excuse for me to sift through some of the PowerShell Remoting documentation, also look at:</p> <pre><code>Get-Help *PSSession* Get-Help *remote* </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POGetting all open PS Sessions on a remote server (from new console window)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJoshua McKinnon
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POGetting all open PS Sessions on a remote server (from new console window)
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COYes, I agree that I _should_ be able to use this to get open sessions on a remote computer (from a new console): Get-PSSession -ComputerName MyServerName.
      singulars
      1. PO
      1. USLocal Needs
    2. COThe fact that you could not made me greatly suspect 2.0 ...glad we answered that part
      singulars
      1. PO
      1. USJoshua McKinnon
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload