Merge branch 'staging' of https://github.com/MicrosoftDocs/PowerShell-Docs into staging

Author: sdwheeler

reference/7/Microsoft.PowerShell.Management/New-Service.md

@@ -17,8 +17,8 @@ Creates a new Windows service.
 
 ```
 New-Service [-Name] <String> [-BinaryPathName] <String> [-DisplayName <String>] [-Description <String>]
- [-StartupType <ServiceStartupType>] [-Credential <PSCredential>] [-DependsOn <String[]>] [-WhatIf] [-Confirm]
- [<CommonParameters>]
+ [-SecurityDescriptorSddl <String>] [-StartupType <ServiceStartupType>] [-Credential <PSCredential>]
+ [-DependsOn <String[]>] [-WhatIf] [-Confirm] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
@@ -62,6 +62,18 @@ Status    : OK
 This command uses **Get-WmiObject** to get the **Win32_Service** object for the new service.
 This object includes the start mode and the service description.
 
+### Example 4: Set the SecurityDescriptor of a service when creating.
+
+This example adds the **SecurityDescriptor** of the service being created.
+
+```powershell
+$SDDLToSet = "D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;SU)"
+New-Service -Name "TestService" -BinaryPathName "C:\WINDOWS\System32\svchost.exe -k netsvcs" -DependsOn NetLogon -DisplayName "Test Service" -StartupType Manual -Description "This is a test service." -SecurityDescriptorSddl $SDDLToSet
+```
+
+The **SecurityDescriptor** is stored in the `$SDDLToSet` variable. The **SecurityDescriptorSddl** parameter uses
+`$SDDLToSet` to set the **SecurityDescriptor** of the new service.
+
 ## PARAMETERS
 
 ### -BinaryPathName
@@ -194,6 +206,22 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -SecurityDescriptorSddl
+
+Specifies the **SecurityDescriptor** for the service in **Sddl** format.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -Confirm
 
 Prompts you for confirmation before running the cmdlet.
@@ -264,5 +292,3 @@ This cmdlet returns an object that represents the new service.
 [Suspend-Service](Suspend-Service.md)
 
 [Remove-Service](Remove-Service.md)
-
-

reference/docs-conceptual/dsc/overview/decisionMaker.md

@@ -1,57 +1,70 @@
 ---
-ms.date:  06/12/2017
+ms.date:  10/11/2019
 keywords:  dsc,powershell,configuration,setup
 title:  Desired State Configuration Overview for Decision Makers
 ---
 
-# Desired State Configuration Overview for Decision Makers
+# Desired State Configuration overview for decision makers
 
-This document describes the business benefits of using Windows PowerShell Desired State Configuration (DSC). It is not a technical guide.
+This document describes the business benefits of using PowerShell Desired State Configuration (DSC),
+and isn't a technical guide.
 
-## What Is Desired State Configuration?
+## What Is DSC?
 
-PowerShell Desired State Configuration is a configuration management platform built into Windows that is based on open standards. DSC is flexible enough to function reliably and consistently in each stage of the deployment lifecycle (development, test, pre-production, production), as well as during scale-out.
+PowerShell DSC is a configuration management platform built into Windows that is based on open
+standards. DSC is flexible enough to function reliably and consistently in each stage of the
+deployment lifecycle (development, test, pre-production, production), and during scale-out.
 
-DSC centers around [configurations](../configurations/configurations.md).
-A configuration is an easy-to-read document that describes an environment made up of computers ("nodes") with specific characteristics.
-These characteristics can be as simple as ensuring a specific Windows feature is enabled or as complex as deploying SharePoint.
+DSC centers around [configurations](../configurations/configurations.md). A configuration is
+PowerShell script that describes an environment made up of computers, or nodes, with specific
+characteristics. These characteristics can be as simple as ensuring a specific Windows feature is
+enabled or as complex as deploying SharePoint.
 
-DSC also has monitoring and reporting built in.
-If a system is no longer compliant, DSC can raise an alert and act to correct the system.
+DSC has monitoring and reporting built-in. If a system is no longer compliant, DSC can raise an
+alert and act to correct the system.
 
-## Benefits of Using Desired State Configuration
+## Benefits of using DSC
 
-Configurations are designed to be easily read, stored, and updated.
-Configurations declare the state target devices should be in, instead of writing instructions for how to put them in that state.
-This makes it much less costly to learn, adopt, implement, and maintain configuration through DSC.
+The configuration's design simplifies how they're read, stored, and updated. Configurations declare
+the state of target devices, rather than writing instructions for how to place devices in that
+state. These factors reduce the costs to learn, adopt, implement, and maintain configuration through
+DSC.
 
-Creating configurations means that complex deployment steps are captured as a "single source of truth" in a single location.
-This makes repeated deployments of a specific set of machines much less error-prone.
-In turn, making deployments faster and more reliable which enables a quick turnaround on complex deployments.
+Creating configurations means that complex deployment steps are captured as a **single source of
+truth** in a single location. Configurations make repeated deployments of a specific set of machines
+less error-prone. And, deployments are faster and more reliable, which enables a quick turnaround on
+complex deployments.
 
-Configurations are also shareable via the [PowerShell Gallery](https://powershellgallery.com) meaning common scenarios and best practices might already exist for the work that needs to be done.
+Configurations are shareable via the [PowerShell Gallery](https://powershellgallery.com). It's
+possible that common scenarios and best practices might already exist for the work you need to do.
 
+## DSC and DevOps
 
-## Desired State Configuration and DevOps
+DSC was designed with
+[DevOps](http://blogs.technet.com/b/ashleymcglone/archive/2015/11/20/devops-for-n00bs-ie-windows-people.aspx)
+in mind. A combination of people, processes, and tools that allow for rapid deployment and iteration
+focused on delivering value to end users whether internal or external. A single configuration that
+defines an environment means that developers can encode their requirements into a configuration and
+check that configuration into source control. Operations teams can then deploy code without going
+through error-prone manual processes.
 
-DSC was designed with [DevOps](http://blogs.technet.com/b/ashleymcglone/archive/2015/11/20/devops-for-n00bs-ie-windows-people.aspx) in mind, a combination of people, processes, and tools that allow for rapid deployment and iteration focused on delivering value to end users whether internal or external.
-Having a single configuration define an environment means that developers can encode their requirements into a configuration,
-check that configuration into source control, and operation teams can easily deploy code without having to go through error-prone manual processes.
+Configurations are [data-driven](../configurations/configData.md). The defined data makes it easier
+for operations to identify and change environments without developer intervention.
 
-Configurations are also [data-driven](../configurations/configData.md),
-which makes it easier for ops to identify and change environments without developer intervention.
+## DSC on-premises and off-premises
 
-## Desired State Configuration On-Premises and Off-Premises
-DSC can be used to manage both on-premise and off-premise deployments.
-For on-premise solutions, DSC has a [pull server](../pull-server/pullServer.md)
-that can be used to centralize management of machines and report on their status.
-For cloud solutions, DSC is usable wherever Windows is usable.
-There are also specific offerings from Azure built on Desired State Configuration,
-such as [Azure Automation](https://azure.microsoft.com/en-us/documentation/services/automation/), which centralizes reporting of DSC.
+DSC can manage on-premises and off-premises deployments. For on-premises solutions, DSC has a
+[Pull Server](../pull-server/pullServer.md) that's used to centralize management of machines and
+report on their status. For off-premises cloud solutions, DSC is usable any place Windows is usable.
+There are specific offerings from Azure built on DSC, such as
+[Azure Automation](https://azure.microsoft.com/en-us/documentation/services/automation/), that
+centralizes DSC reporting.
 
-## DSC and Compatibility
+## DSC and compatibility
 
-Although DSC was introduced in Windows Server 2012 R2, it is available for down-level operating systems via the Windows Management Framework (WMF) package.
-More information about the WMF can be found on the [PowerShell homepage](/powershell/).
+DSC was introduced in Windows Server 2012 R2, but it's available for down-level operating systems
+via the Windows Management Framework (WMF). For more information about WMF, see
+[Windows Management Framework](/powershell/scripting/wmf/overview).
 
-DSC can also be used to manage Linux. For more information, see [Getting Started with DSC for Linux](../getting-started/lnxGettingStarted.md).
+DSC can be used to manage Linux. For more information, see
+[Getting Started with DSC for Linux](../getting-started/lnxGettingStarted.md).