Skip to content

Release bobbytreed b005 #2385

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 18 commits into from
May 2, 2018
Merged

Release bobbytreed b005 #2385

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
18 commits
Select commit Hold shift + click to select a range
b16728d
Fixing issue with faulty links from issue (2322)
bobbytreed Apr 25, 2018
c6ea429
Trying smaller pull requests to test Script Automation
bobbytreed Apr 25, 2018
e7d088d
Testing script automation with a smaller batch of files (#2359)
bobbytreed Apr 25, 2018
8080e1c
Bringing even with staging.
v-alje Apr 25, 2018
d48ac48
Merge branch 'release-bobbytreed' of github.com:PowerShell/PowerShell…
bobbytreed Apr 26, 2018
47dae5b
Bringing even with staging.
v-alje Apr 26, 2018
4cddb37
Bringing even with staging.
v-alje Apr 27, 2018
6021994
Merge branch 'release-bobbytreed' of github.com:PowerShell/PowerShell…
bobbytreed Apr 27, 2018
fd084c8
Merge pull request #2369 from bobbytreed/release-bobbytreed
Apr 27, 2018
745108f
Git Batch testing 15 files (#2371)
bobbytreed Apr 27, 2018
5ab8971
Batch automation: Formatting fixes (#2372)
bobbytreed Apr 27, 2018
09d07f9
Bringing even with staging.
v-alje Apr 27, 2018
b450b4d
Batch automation: Formatting fixes (#2377)
bobbytreed Apr 30, 2018
6cb4714
Merge branch 'staging' into release-bobbytreed
Apr 30, 2018
8800e06
Bringing even with staging.
v-alje Apr 30, 2018
d531bba
Bringing even with staging.
v-alje May 1, 2018
7761f57
Batch automation: Formatting fixes
bobbytreed May 2, 2018
5be9e6d
fixing small formatting error
bobbytreed May 2, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions reference/3.0/Microsoft.PowerShell.Core/About/about_Remote.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,10 @@
---
---
ms.date: 01/03/2018
schema: 2.0.0
locale: en-us
keywords: powershell,cmdlet
title: about_Remote
---

# About Remote

## SHORT DESCRIPTION
Expand Down
79 changes: 38 additions & 41 deletions ...rence/3.0/Microsoft.PowerShell.Core/About/about_Remote_Disconnected_Sessions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,10 @@
---
---
ms.date: 12/01/2017
schema: 2.0.0
locale: en-us
keywords: powershell,cmdlet
title: about_Remote_Disconnected_Sessions
---

# About Remote Disconnected Sessions

## Short Description
Expand Down Expand Up @@ -44,12 +43,12 @@ location.

The following cmdlets support the Disconnected Sessions feature:

* `Connect-PSSession`: Connects to a disconnected PSSession
* `Disconnect-PSSession`: Disconnects a PSSession
* `Get-PSSession`: Gets PSSessions on the local computer or on remote computers
* `Receive-PSSession`: Gets the results of commands that ran in disconnected
- `Connect-PSSession`: Connects to a disconnected PSSession
- `Disconnect-PSSession`: Disconnects a PSSession
- `Get-PSSession`: Gets PSSessions on the local computer or on remote computers
- `Receive-PSSession`: Gets the results of commands that ran in disconnected
sessions
* `Invoke-Command`: **InDisconnectedSession** parameter creates a PSSession and
- `Invoke-Command`: **InDisconnectedSession** parameter creates a PSSession and
disconnects immediately

## How the Disconnected Sessions Feature Works
Expand Down Expand Up @@ -113,7 +112,7 @@ The first command creates a session to the Server01 computer. The session
resides on the Server01 computer.

```powershell
PS C:\> New-PSSession -ComputerName Server01
PS> New-PSSession -ComputerName Server01

Id Name ComputerName State ConfigurationName Availability
-- ---- ------------ ----- ----------------- ------------
Expand All @@ -124,7 +123,7 @@ To get the session, use the **ComputerName** parameter of `Get-PSSession`
with a value of Server01.

```powershell
PS C:\> Get-PSSession -ComputerName Server01
PS> Get-PSSession -ComputerName Server01

Id Name ComputerName State ConfigurationName Availability
-- ---- ------------ ----- ----------------- ------------
Expand All @@ -137,16 +136,16 @@ maintained on the local computer. It does not get PSSessions on the Server01
computer, even if they were started on the local computer.

```powershell
PS C:\> Get-PSSession -ComputerName localhost
PS C:\>
PS> Get-PSSession -ComputerName localhost
PS>
```

To get sessions that were created in the current session, use the
`Get-PSSession` cmdlet without parameters. This command gets the PSSession
that was created in the current session and connects to the Server01 computer.

```powershell
PS C:\> Get-PSSession
PS> Get-PSSession

Id Name ComputerName State ConfigurationName Availability
-- ---- ------------ ----- ----------------- ------------
Expand All @@ -164,7 +163,7 @@ Notice that the value of the State property is Disconnected and the
Availability is None.

```powershell
PS C:\> Get-PSSession -ComputerName Server01 | Disconnect-PSSession
PS> Get-PSSession -ComputerName Server01 | Disconnect-PSSession

Id Name ComputerName State ConfigurationName Availability
-- ---- ------------ ----- ----------------- ------------
Expand All @@ -179,7 +178,7 @@ The following command runs a `Get-WinEvent` command in a disconnected session
on the Server02 remote computer.

```powershell
PS C:\> Invoke-Command -ComputerName Server02 -InDisconnectedSession `
PS> Invoke-Command -ComputerName Server02 -InDisconnectedSession `
-ScriptBlock { Get-WinEvent -LogName "Windows PowerShell" }

Id Name ComputerName State ConfigurationName Availability
Expand Down Expand Up @@ -207,7 +206,7 @@ The following command gets the sessions on the Server02 computer. The output
includes two disconnected sessions, both of which are available.

```powershell
PS C:\> Get-PSSession -ComputerName Server02
PS> Get-PSSession -ComputerName Server02

Id Name ComputerName State ConfigurationName Availability
-- ---- ------------ ----- ----------------- ------------
Expand All @@ -219,7 +218,7 @@ The following command connects to Session2. The PSSession is now open and
available.

```powershell
PS C:\> Connect-PSSession -ComputerName Server02 -Name Session2
PS> Connect-PSSession -ComputerName Server02 -Name Session2

Id Name ComputerName State ConfigurationName Availability
-- ---- ------------ ----- ----------------- ------------
Expand Down Expand Up @@ -250,7 +249,7 @@ command that ran in the Session3 session. The command uses the **OutTarget**
parameter to get the results in a job.

```powershell
PS C:\> Receive-PSSession -ComputerName Server02 -Name Session3 `
PS> Receive-PSSession -ComputerName Server02 -Name Session3 `
-OutTarget Job

Id Name PSJobTypeName State HasMoreData Location
Expand All @@ -261,7 +260,7 @@ Id Name PSJobTypeName State HasMoreData Location
To get the results of the job, use the `Receive-Job` cmdlet.

```powershell
PS C:\> Get-Job | Receive-Job -Keep
PS> Get-Job | Receive-Job -Keep

ProviderName: PowerShell

Expand Down Expand Up @@ -299,43 +298,41 @@ reconnected.

```powershell
# Session 1
PS C:\> New-PSSession -ComputerName Server30 -Name Test
PS> New-PSSession -ComputerName Server30 -Name Test

Id Name ComputerName State ConfigurationName Availability
-- ---- ------------ ----- ----------------- ------------
1 Test Server30 Opened Microsoft.PowerShell Available

# Session 2
PS C:\> Get-PSSession -ComputerName Server30 -Name Test
PS> Get-PSSession -ComputerName Server30 -Name Test

Id Name ComputerName State ConfigurationName Availability
-- ---- ------------ ----- ----------------- ------------
1 Test Server30 Disconnected Microsoft.PowerShell Busy

# Session 1
PS C:\> Get-PSSession -ComputerName Server30 -Name Test |
PS> Get-PSSession -ComputerName Server30 -Name Test |
>> Disconnect-PSSession

Id Name ComputerName State ConfigurationName Availability
-- ---- ------------ ----- ----------------- ------------
1 Test Server30 Disconnected Microsoft.PowerShell None

# Session 2
PS C:\> Get-PSSession -ComputerName Server30
PS> Get-PSSession -ComputerName Server30

Id Name ComputerName State ConfigurationName Availability
-- ---- ------------ ----- ----------------- ------------
1 Test Server30 Disconnected Microsoft.PowerShell None

# Session 2
PS C:\> Connect-PSSession -ComputerName Server01 -Name Test
PS> Connect-PSSession -ComputerName Server01 -Name Test

Id Name ComputerName State ConfigurationName Availability
-- ---- ------------ ----- ----------------- ------------
3 Test Server30 Opened Microsoft.PowerShell Available

# Session 1
PS C:\> Get-PSSession -ComputerName Server30
3 Test Server30 Opened Microsoft.PowerShell Available# Session 1
PS> Get-PSSession -ComputerName Server30

Id Name ComputerName State ConfigurationName Availability
-- ---- ------------ ----- ----------------- ------------
Expand Down Expand Up @@ -398,7 +395,7 @@ in SessionOption object and the IdleTimeout value in the $PSSessionOption
preference variable do not change the value of the IdleTimeout of the
PSSession in a `Connect-PSSession` or `Receive-PSSession` command.

* To create a PSSession with a particular idle timeout value, create
- To create a PSSession with a particular idle timeout value, create
a $PSSessionOption preference variable. Set the value of the
IdleTimeout property to the desired value (in milliseconds).

Expand All @@ -411,7 +408,7 @@ PSSession in a `Connect-PSSession` or `Receive-PSSession` command.
$PSSessionOption = New-PSSessionOption -IdleTimeoutMSec 172800000
```

* To create a PSSession with a particular idle timeout value, use
- To create a PSSession with a particular idle timeout value, use
the **IdleTimeoutMSec** parameter of the `New-PSSessionOption` cmdlet.
Then, use the session option in the value of the **SessionOption**
parameter of the `New-PSSession` or `Invoke-Command` cmdlets.
Expand All @@ -427,7 +424,7 @@ $o = New-PSSessionOption -IdleTimeoutMSec 172800000
New-PSSession -SessionOption $o
```

* To change a the idle timeout of a PSSession when disconnecting,
- To change a the idle timeout of a PSSession when disconnecting,
use the **IdleTimeoutSec** parameter of the `Disconnect-PSSession`
cmdlet.

Expand All @@ -437,7 +434,7 @@ New-PSSession -SessionOption $o
Disconnect-PSSession -IdleTimeoutSec 172800
```

* To create a session configuration with a particular idle timeout
- To create a session configuration with a particular idle timeout
and maximum idle timeout, use the **IdleTimeoutSec** and **MaxIdleTimeoutSec**
parameters of the `New-PSTransportOption` cmdlet. Then, use the
transport option in the value of the **TransportOption** parameter
Expand All @@ -450,7 +447,7 @@ $o = New-PSTransportOption -IdleTimeoutSec 172800 -MaxIdleTimeoutSec 259200
Register-PSSessionConfiguration -Name Test -TransportOption $o
```

* To change the default idle timeout and maximum idle timeout of
- To change the default idle timeout and maximum idle timeout of
a session configuration, use the **IdleTimeoutSec** and **MaxIdleTimeoutSec**
parameters of the `New-PSTransportOption` cmdlet. Then, use the
transport option in the value of the **TransportOption** parameter
Expand All @@ -473,12 +470,12 @@ whether the command continues to run while the session is disconnected.

Valid values:

* Block
- Block

When the output buffer is full, execution is suspended until the buffer is
clear.

* Drop
- Drop

When the output buffer is full, execution continues. As new output is
generated, the oldest output is discarded.
Expand Down Expand Up @@ -513,7 +510,7 @@ If you are a member of the Administrators group on the remote computer, you
can also create and change the output buffering mode of session
configurations.

* To create a PSSession with an output buffering mode of Drop, create
- To create a PSSession with an output buffering mode of Drop, create
a $PSSessionOption preference variable in which the value of the
OutputBufferingMode property is Drop.

Expand All @@ -526,7 +523,7 @@ configurations.
$PSSessionOption = New-PSSessionOption -OutputBufferingMode Drop
```

* To create a PSSession with an output buffering mode of Drop, use
- To create a PSSession with an output buffering mode of Drop, use
the **OutputBufferingMode** parameter of the `New-PSSessionOption`
cmdlet to create a session option with a value of Drop. Then, use
the session option in the value of the **SessionOption** parameter of
Expand All @@ -543,7 +540,7 @@ $o = New-PSSessionOption -OutputBufferingMode Drop
New-PSSession -SessionOption $o
```

* To change a the output buffering mode of a PSSession when
- To change a the output buffering mode of a PSSession when
disconnecting, use the **OutputBufferingMode** parameter of the
`Disconnect-PSSession` cmdlet.

Expand All @@ -553,7 +550,7 @@ New-PSSession -SessionOption $o
Disconnect-PSSession -OutputBufferingMode Drop
```

* To change a the output buffering mode of a PSSession when
- To change a the output buffering mode of a PSSession when
reconnecting, use the **OutputBufferingMode** parameter of the
`New-PSSessionOption` cmdlet to create a session option with
a value of Drop. Then, use the session option in the value of the
Expand All @@ -563,10 +560,10 @@ Disconnect-PSSession -OutputBufferingMode Drop

```powershell
$o = New-PSSessionOption -OutputBufferingMode Drop
Connect-PSSession -Cn Server01 -Name Test -SessionOption $o
Connect-PSSession -ComputerName Server01 -Name Test -SessionOption $o
```

* To create a session configuration with a default output buffering
- To create a session configuration with a default output buffering
mode of Drop, use the **OutputBufferingMode** parameter of the
`New-PSTransportOption` cmdlet to create a transport option object
with a value of Drop. Then, use the transport option in the value of
Expand All @@ -579,7 +576,7 @@ $o = New-PSTransportOption -OutputBufferingMode Drop
Register-PSSessionConfiguration -Name Test -TransportOption $o
```

* To change the default output buffering mode of a session
- To change the default output buffering mode of a session
configuration, use the **OutputBufferingMode** parameter of the
`New-PSTransportOption` cmdlet to create a transport option with a
value of Drop. Then, use the Transport option in the value of the
Expand Down
8 changes: 4 additions & 4 deletions reference/3.0/Microsoft.PowerShell.Core/About/about_Remote_FAQ.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,10 @@
---
---
ms.date: 12/01/2017
schema: 2.0.0
locale: en-us
keywords: powershell,cmdlet
title: about_Remote_FAQ
---

# About Remote FAQ

## SHORT DESCRIPTION
Expand Down Expand Up @@ -53,7 +52,7 @@ session on the local computer.

To transmit the commands and receive the output, Windows PowerShell uses the
WS-Management protocol. For information about the WS-Management protocol, see
[WS-Management Protocol](http://go.microsoft.com\/fwlink/?LinkId=144634) in
[WS-Management Protocol](http://go.microsoft.com/fwlink/?LinkId=144634) in
the MSDN library.

Beginning in Windows PowerShell 3.0, remote sessions are stored on the remote
Expand Down Expand Up @@ -468,7 +467,8 @@ changes.

You can use the following Windows PowerShell command to add this entry:

```powershell

```powershell
$parameters = @{
Path='HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System'
Name='LocalAccountTokenFilterPolicy'
Expand Down
Loading