Skip to content

Commit

Permalink
Merging latest updates into Live (#1908)
Browse files Browse the repository at this point in the history
* Update the example of `Where-Object -IsNot` (#1841)

* Update Example 5 in Group-Object.md (#1845)

* removing @{Text=} tags

* fixing UTF8 characters

* removed empty H3

* added H3 for input and output types

* removed mangled UTF8 character

* updating Out-* commands with -NoNewLine per Issue 1739

* Fix the example of `Format-Table -DisplayError` (#1848)

The example is a `-DisplayError` parameter example. But it uses `-ShowError` parameter.

* Fix the example of `Format-Wide -DisplayError` (#1850)

* Fix the example of `Format-Custom -DisplayError` (#1849)

The example is a -DisplayError parameter example. But it uses -ShowError parameter.

* updating set-acl docs per PR#901

* using semantic link breaks

* Fix the example of `Format-Wide -ShowError` (#1851)

* Fixed Test-ScriptFileInfo example (#1852)

* fixing issue 1768

* Formatting, example fix for Body parameter (#1847)

1. Replaced variable names with PascalCase convention and for consistency
2. Removed directory information [c:\] in the examples
3. Put powershell keyword for formatting examples
4. Replaced Invoke-RestMethod with Invoke-WebRequest in the Body example, added method Post
5. Removed InformationAction and InformationVariable parameters, which were mistakenly a copy of Body, included already in CommonVariables part

* fixing style consistency across articles

* Fix example numbers in Resume-Job.md (#1857)

Example 4 is duplicated.

* Fixes typo $WebSiteName in separatingEnvData.md (#1856)

- Adds the website name to common node property inside configuration data.
- Also, it is now referenced (e.g. $Node.WebSiteName) in the DSC configuration document in MyWebApp.ps1.

* Updates configurations.md (#1855)

Two set of changes made.
- Example scripts e.g. MyDscConfiguration.ps1 define the configuration inside them and call the configuration at the end line. Removed the call to the configuration at the end. Since the article demonstrates dot-sourcing the file and calling the configuration explicitly.
- Fixed typo in the file name (TEST-PC1.mof  to localhost.mof ), since the ComputerName was not specified it should default to using 'localhost' as the default argument for it.

P.S. - There is a comment on the web-page regarding the fixes made

* Fix typo in comment (#1854)

* Updating the help content for v6. (#1853)

* Updating the help content for v6.

* Address code review comments

* Fix broken links

* Fix example numbers in about_Transactions.md (#1859)

Example number '7' is duplicated.

* Update Alias-Provider.md (#1831)

1. Removed statement that an alias is to an executable, the definition cotnains the path. It may - but does not need to be. For example:
Try Set-Alias np Notepad then look at the definition.
2. Clarified that an alias can also be to a powershell script (ps1 file).
3. Tidied up the language removing multiple 'And,' clauses to improve readability.

* Add documentation of new -AsHashtable switch for ConvertFrom-Json introduced by PR #5043 (#1858)

* add documentation of new -AsHashTable switch for ConvertFrom-Json and also document the behaviour in case of duplicate strings.

* correct casing of -AsHashtable switch.

* Address PR comments about -AsHashtable switch for ConvertFrom-Json.md

* Accept pipeline input: False for -AsHashtable switch in ConvertFrom-Json.md

* Revert "Accept pipeline input: False for -AsHashtable switch in ConvertFrom-Json.md"
Accidentally change the wrong field.
This reverts commit 6e76191.

* Accept pipeline input: False for -AsHashtable switch in ConvertFrom-Json.md

* Fix example numbers in Invoke-WebRequest.md (#1862)

Example number '4' is duplicated.

* reformatting and integrating changes from PR#1831 (#1860)

* Fix example numbers in Get-Help.md (#1869)

Example number 12 and 13 are missing.

* Fix example numbers in Import-Module.md (#1868)

Example number '10' is duplicated.

* Fix example number in ConvertTo-Html.html (#1867)

Example number '10' is duplicated.

* Update dscCiCd.md (#1865)

Missing a period on line 378. Should be `$(Build.ArtifactStagingDirectory)\` not `$(BuildArtifactStagingDirectory)\`.

* Web Cmdlets 6.0.0 Documentation Refresh (#1870)

* Web Cmdlets 6.0.0 Documentation Refresh

* Address PR Feedback

* Merge Example 4 and 5 in Get-Member.md (#1874)

Example 4 and 5 in Get-Member.md v3.0 and v4.0 are almost the same. They should be merged as with v5.0.

* Remove hash algorithms unsupported in v6.0 (#1873)

MACTripleDES and RIPEMD160 are no longer supported in v6.0.

* Update outputs of Get-Verb (#1872)

Since v6.0, `Get-Verb` returns  not MemberDefinition but VerbInfo that has Verb and Group properties.

* Fix typo in ConvertTo-Html.md (UTF-x) (#1879)

* Fix "Accept wildcard characters" in Get-Service.md v6 (#1878)

* Fixed "False" -> "True" (`DisplayName`, `Exclude`, `Include`, and `Name`)
* Removed `InformationAction` and `InformationVariable`

* Fixed Get-WindowsFeature cmdlet HyperLink (#1877)

* Fixed Get-WindowsFeature cmdlet HyperLink

Minor edit.  Update Get-WindowsFeature cmdlet HyperLink to https://technet.microsoft.com/library/jj205469(v=wps.630).aspx

* Changed URL to new docs.microsoft.com location

The TechNet URL did not work. TechNet and MSDN are being retired.

* Update Get-WinEvent.md (#1876)

Removed future tense in a couple of places to improve readability. Minor edit.

* Update Example 8 in Get-Process.md (find the owner of a process) (#1875)

* Update Example 8 in Get-Process.md (Find the owner of a process)

* Update to attempt to avoid build errors

It seems that the build system does not accept multiple script blocks per one Example header.

* updated localmachine\Root to LocalMachine\My (#1880)

The example where we import the PFX on the target node should import the cert into Personal store and not root.

* Update Group property example in Get-Verb.md (#1881)

* adding missing space (#1885)

* removing stray character (#1886)

* Update Example 9 in Get-Process.md (#1888)

* powershell -> pwsh (only v6.0)
* Windows PowerShell -> PowerShell

* Remove "About ISE" files of v6.0 (#1891)

* Remove "About ISE" files of v6.0

ISE is no longer bundled with PowerShell 6.0.

* Remove links for "About ISE" files of v6.0

* Update Get-Process.md (#1890)

Fixed name parameter details to show it accepts wildcards in the name

* Update productincompat.md (#1892)

The list of compatible systems should include Skype For Business Server 2015 and Lync Server 2013.

* Update unapproved verbs examples in Get-Verb.md (#1896)

* Updated Example 4
* Removed Example 5

* Removing extra space in the Example 5A script (#1894)

It was highlighting as string in the documentation, I was trying to remove all the extra space.

* fixing merge conflict

* updates to style and contrib

* tweak format

* tweak format 2

* fix typo

* fix number list example

* adding review feedback

* fix broken links

* incorporating feedback from zach

* reformatting About_* for 80 columns - part 1

* reformat about_*

* reformatting About_* topics - Part 2

* fixing broken links

* fixing more broken links

* more broken links fixed

* Fix parameter's position in Get-Random.md (#1901)

* Fix parameter's position in Measure-Command.md (#1905)

* Fix parameter's position in Trace-Command.md (#1904)

* Actually call the configuration in the example (#1906)

On line 74, it says...

"The last line of the example containing only the name of the configuration, calls the configuration."

This change actually makes that call.

* reformatting About_* for 80 columns - part 3 (#1902)

* reformatting About_*

* reformatting About_* part 3

* fixing broken links

* fixing more broken links

* one more time with the links
  • Loading branch information
Sean Wheeler committed Dec 1, 2017
1 parent 93c647a commit 7bb75bf
Show file tree
Hide file tree
Showing 56 changed files with 4,738 additions and 4,474 deletions.
4 changes: 3 additions & 1 deletion dsc/configurations.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,8 @@ Configuration MyDscConfiguration {
Name = "Bitlocker"
}
}
}
}
MyDscConfiguration
```

Expand Down Expand Up @@ -60,6 +61,7 @@ Configuration MyDscConfiguration {
}
}
}
MyDscConfiguration
```

Expand Down
Original file line number Diff line number Diff line change
@@ -1,19 +1,16 @@
---
ms.date: 2017-06-09
ms.date: 2017-11-28
schema: 2.0.0
locale: en-us
keywords: powershell,cmdlet
title: about_Functions_CmdletBindingAttribute
---

# About Functions CmdletBindingAttribute
## about_Functions_CmdletBindingAttribute


# SHORT DESCRIPTION

Describes the attribute that makes a function work like a
compiled cmdlet.
Describes the attribute that makes a function work like a compiled cmdlet.

# LONG DESCRIPTION

Expand Down Expand Up @@ -124,13 +121,15 @@ to an advanced function.
function Get-Numbers {
[CmdletBinding(SupportsPaging = $true)]
param()
$FirstNumber = [Math]::Min($PSCmdlet.PagingParameters.Skip, 100)
$LastNumber = [Math]::Min($PSCmdlet.PagingParameters.First + $FirstNumber - 1, 100)
$LastNumber = [Math]::Min($PSCmdlet.PagingParameters.First +
$FirstNumber - 1, 100)
if ($PSCmdlet.PagingParameters.IncludeTotalCount) {
$TotalCountAccuracy = 1.0
$TotalCount = $PSCmdlet.PagingParameters.NewTotalCount(100, $TotalCountAccuracy)
$TotalCount = $PSCmdlet.PagingParameters.NewTotalCount(100,
$TotalCountAccuracy)
Write-Output $TotalCount
}
$FirstNumber .. $LastNumber | Write-Output
Expand Down Expand Up @@ -173,8 +172,7 @@ must be included when the parameter is used in a function.
The Position argument of the Parameter attribute takes precedence over the
PositionalBinding default value. You can use the Position argument to specify
a position value for a parameter. For more information about the Position
argument, see about_Functions_Advanced_Parameters
(http://go.microsoft.com/fwlink/?LinkID=135173).
argument, see [about_Functions_Advanced_Parameters](about_Functions_Advanced_Parameters.md).

# NOTES

Expand Down
Original file line number Diff line number Diff line change
@@ -1,43 +1,45 @@
---
ms.date: 2017-06-09
ms.date: 2017-11-28
schema: 2.0.0
locale: en-us
keywords: powershell,cmdlet
title: about_Group_Policy_Settings
---

# About Group Policy Settings
## about_Group_Policy_Settings


# SHORT DESCRIPTION

Describes the Group Policy settings for Windows PowerShell

# LONG DESCRIPTION


Windows PowerShell includes Group Policy settings to help you define
consistent option values for servers in an enterprise environment.

The Windows PowerShell Group Policy settings are in the following
Group Policy paths:

Computer Configuration\Administrative Templates\Windows Components\Windows PowerShell
User Configuration\Administrative Templates\Windows Components\Windows PowerShell
Computer Configuration\
Administrative Templates\
Windows Components\
Windows PowerShell

User Configuration\
Administrative Templates\
Windows Components\
Windows PowerShell

Group policy settings in the User Configuration path take precedence
over Group Policy settings in the Computer Configuration path.

The policies are as follows:

Turn on Script Execution: Sets the Windows PowerShell execution
policy.
Turn on Module Logging: Sets the LogPipelineExecutionDetails
property of modules.
Set the default source path for Update-Help:
Sets the source for UpdatableHelp to
a directory, not the Internet.
- Turn on Script Execution: Sets the Windows PowerShell execution policy.
- Turn on Module Logging: Sets the LogPipelineExecutionDetails property of
modules.
- Set the default source path for Update-Help: Sets the source for
UpdatableHelp to a directory, not the Internet.

To download spreadsheets that list all of the Group Policy settings for
each version of Windows, see "Group Policy Settings Reference for Windows
Expand All @@ -53,28 +55,27 @@ run.
If you enable the policy setting, you can select from among the following
policy settings.

-- "Allow only signed scripts" allows scripts to execute only if they
are signed by a trusted publisher. This policy setting is equivalent
to the AllSigned execution policy.
- "Allow only signed scripts" allows scripts to execute only if they are
signed by a trusted publisher. This policy setting is equivalent to the
AllSigned execution policy.

-- "Allow local scripts and remote signed scripts" allows all local
scripts to run. Scripts that originate from the Internet must be
signed by a trusted publisher. This policy setting is equivalent
to the RemoteSigned execution policy.
- "Allow local scripts and remote signed scripts" allows all local scripts to
run. Scripts that originate from the Internet must be signed by a trusted
publisher. This policy setting is equivalent to the RemoteSigned execution
policy.

-- "Allow all scripts" allows all scripts to run. This policy
setting is equivalent to the Unrestricted execution policy.
- "Allow all scripts" allows all scripts to run. This policy setting is
equivalent to the Unrestricted execution policy.

If you disable this policy setting, no scripts are allowed to run.
This policy setting is equivalent to the Restricted execution policy.
If you disable this policy setting, no scripts are allowed to run. This policy
setting is equivalent to the Restricted execution policy.

If you disable or do not configure this policy setting, the execution
policy that is set for the computer or user by the Set-ExecutionPolicy
cmdlet determines whether scripts are permitted to run. The default
value is Restricted.
If you disable or do not configure this policy setting, the execution policy
that is set for the computer or user by the Set-ExecutionPolicy cmdlet
determines whether scripts are permitted to run. The default value is
Restricted.

For more information, see about_Execution_Policies
(http://go.microsoft.com/fwlink/?LinkID=135170).
For more information, see [about_Execution_Policies](about_Execution_Policies.md).

# TURN ON MODULE LOGGING

Expand All @@ -99,56 +100,54 @@ To turn on module logging for a module, use the following command format.
The module must be imported into the session and the setting is effective
only in the current session.

```powershell
PS C:> Import-Module <Module-Name>
PS C:> (Get-Module <Module-Name>).LogPipelineExecutionDetails = $true
```

To turn on module logging for all sessions on a particular computer,
add the previous commands to the all-users Windows PowerShell profile
($Profile.AllUsers.AllHosts).

For more information about module logging, see about_Modules
(http://go.microsoft.com/fwlink/?LinkID=144311).
For more information about module logging, see [about_Modules](about_Modules.md).

# SET THE DEFAULT SOURCE PATH FOR UPDATE-HELP

The "Set the Default Source Path for Update-Help" policy setting sets a
default value for the SourcePath parameter of the Update-Help cmdlet.
This setting prevents users from using the Update-Help cmdlet to download
help files from the Internet.
default value for the SourcePath parameter of the Update-Help cmdlet. This
setting prevents users from using the Update-Help cmdlet to download help
files from the Internet.

NOTE: The "Set the default source path for Update-Help" Group
Policy setting appears under Computer Configuration and
User Configuration. However, only the Group Policy setting
under Computer Configuration is effective. The Group Policy
setting under User Configuration is ignored.
NOTE: The "Set the default source path for Update-Help" Group Policy setting
appears under Computer Configuration and User Configuration. However, only the
Group Policy setting under Computer Configuration is effective. The Group
Policy setting under User Configuration is ignored.

The Update-Help cmdlet downloads and installs the newest help files for
Windows PowerShell modules and installs them on the computer. By default,
Update-Help downloads new help files from an Internet location specified
by the module.
Update-Help downloads new help files from an Internet location specified by
the module.

However, you can use the Save-Help cmdlet to download the newest help
files to a file system location, such as a network share, and then use
the Update-Help cmdlet to get the help files from the file system
location and install them on the computer. The SourcePath parameter of
the Update-Help cmdlet specifies the file system location.
However, you can use the Save-Help cmdlet to download the newest help files to
a file system location, such as a network share, and then use the Update-Help
cmdlet to get the help files from the file system location and install them on
the computer. The SourcePath parameter of the Update-Help cmdlet specifies the
file system location.

By providing a default value for the SourcePath parameter, this Group
Policy setting implicitly adds the SourcePath parameter to all Update-Help
commands. Users can override the particular file system location specified
as the default value by entering a different file system location. But they
cannot remove the SourcePath parameter from the Update-Help command.
By providing a default value for the SourcePath parameter, this Group Policy
setting implicitly adds the SourcePath parameter to all Update-Help commands.
Users can override the particular file system location specified as the
default value by entering a different file system location. But they cannot
remove the SourcePath parameter from the Update-Help command.

If you enable this policy setting, you can specify a default value for the
SourcePath parameter. Enter a file system location.

If this policy setting is disabled or not configured, there is no
default value for the SourcePath parameter of the Update-Help cmdlet.
Users can download help from the Internet or from any file system
location.
If this policy setting is disabled or not configured, there is no default
value for the SourcePath parameter of the `Update-Help` cmdlet. Users can
download help from the Internet or from any file system location.

For more information, see about_Updatable_Help
(http://go.microsoft.com/fwlink/?LinkID=235801).
For more information, see [about_Updatable_Help](about_Updatable_Help.md).

# KEYWORDS

Expand All @@ -163,13 +162,12 @@ about_GroupPolicy

[about_Updatable_Help](about_Updatable_Help.md)

Get-ExecutionPolicy

Set-ExecutionPolicy
[Get-ExecutionPolicy](../../Microsoft.PowerShell.Security/Get-ExecutionPolicy.md)

Get-Module
[Set-ExecutionPolicy](../../Microsoft.PowerShell.Security/Set-ExecutionPolicy.md)

Update-Help
[Get-Module](../Get-Module.md)

Save-Help
[Update-Help](../Update-Help.md)

[Save-Help](../Save-Help.md)
Loading

0 comments on commit 7bb75bf

Please sign in to comment.