Merging latest changes into Live

.openpublishing.redirection.json

@@ -15,6 +15,21 @@
       "redirect_url": "/powershell/wmf/readme",
       "redirect_document_id": "False"
     },
+    {
+      "source_path": "reference/docs-conceptual/core-powershell/console-guide.md",
+      "redirect_url": "/powershell/scripting/core-powershell/console/powershell.exe-command-line-help",
+      "redirect_document_id": "False"
+    },
+    {
+      "source_path": "reference/docs-conceptual/core-powershell/ise-guide.md",
+      "redirect_url": "/powershell/scripting/core-powershell/ise/introducing-the-windows-powershell-ise",
+      "redirect_document_id": "False"
+    },
+    {
+      "source_path": "reference/docs-conceptual/getting-started/understanding-concepts-reference.md",
+      "redirect_url": "/powershell/scripting/getting-started/fundamental/about-windows-powershell",
+      "redirect_document_id": "False"
+    },
     {
       "source_path": "reference/virtual-directory/index.md",
       "redirect_url": "/powershell/scripting/powershell-scripting",

dsc/DSCAutomationHostEnabled.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  DSCAutomationHostEnabled registry key

dsc/DscForEngineers.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-10-13
-author:  eslesar;mgreenegit
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  Desired State Configuration Overview for Decision Makers
@@ -112,15 +111,15 @@ Configuration Sample_Share
       # implement the logic of "how" to execute a task
       xSmbShare MySMBShare
       {
-          Ensure      = "Present" 
+          Ensure      = "Present"
           Name        = "MyShare"
-          Path        = "C:\Demo\Temp"  
+          Path        = "C:\Demo\Temp"
           ReadAccess  = "Alice"
           FullAccess  = "Bob"
           Description = "This is an updated description for this share"
       }
    }
-} 
+}
 #Run the function to compile the configuration
 Sample_Share
 #Pass the configuration to the nodes we defined and configure them

dsc/PackageManagementDscResource.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  DSC PackageManagement Resource

dsc/PackageManagementSourceDscResource.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  DSC PackageManagementSource Resource

dsc/archiveResource.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  DSC Archive Resource
@@ -12,7 +11,7 @@ title:  DSC Archive Resource
 
 The Archive resource in Windows PowerShell Desired State Configuration (DSC) provides a mechanism to unpack archive (.zip) files at a specific path.
 
-## Syntax 
+## Syntax
 ```MOF
 Archive [string] #ResourceName
 {
@@ -28,15 +27,15 @@ Archive [string] #ResourceName
 
 ## Properties
 
-|  Property  |  Description   | 
-|---|---| 
-| Destination| Specifies the location where you want to ensure the archive contents are extracted.| 
-| Path| Specifies the source path of the archive file.| 
-| __Checksum__| Defines the type to use when determining whether two files are the same. If __Checksum__ is not specified, only the file or directory name is used for comparison. Valid values include: SHA-1, SHA-256, SHA-512, createdDate, modifiedDate, none (default). If you specify __Checksum__ without __Validate__, the configuration will fail.| 
-| Ensure| Determines whether to check if the content of the archive exists at the __Destination__. Set this property to __Present__ to ensure the contents exist. Set it to __Absent__ to ensure they do not exist. The default value is __Present__.| 
-| DependsOn | Indicates that the configuration of another resource must run before this resource is configured. For example, if the ID of the resource configuration script block that you want to run first is ResourceName and its type is __ResourceType__, the syntax for using this property is `DependsOn = "[ResourceType]ResourceName"`.| 
-| Validate| Uses the Checksum property to determine if the archive matches the signature. If you specify Checksum without Validate, the configuration will fail. If you specify Validate without Checksum, a SHA-256 checksum is used by default.| 
-| Force| Certain file operations (such as overwriting a file or deleting a directory that is not empty) will result in an error. Using the Force property overrides such errors. The default value is False.| 
+|  Property  |  Description   |
+|---|---|
+| Destination| Specifies the location where you want to ensure the archive contents are extracted.|
+| Path| Specifies the source path of the archive file.|
+| __Checksum__| Defines the type to use when determining whether two files are the same. If __Checksum__ is not specified, only the file or directory name is used for comparison. Valid values include: SHA-1, SHA-256, SHA-512, createdDate, modifiedDate, none (default). If you specify __Checksum__ without __Validate__, the configuration will fail.|
+| Ensure| Determines whether to check if the content of the archive exists at the __Destination__. Set this property to __Present__ to ensure the contents exist. Set it to __Absent__ to ensure they do not exist. The default value is __Present__.|
+| DependsOn | Indicates that the configuration of another resource must run before this resource is configured. For example, if the ID of the resource configuration script block that you want to run first is ResourceName and its type is __ResourceType__, the syntax for using this property is `DependsOn = "[ResourceType]ResourceName"`.|
+| Validate| Uses the Checksum property to determine if the archive matches the signature. If you specify Checksum without Validate, the configuration will fail. If you specify Validate without Checksum, a SHA-256 checksum is used by default.|
+| Force| Certain file operations (such as overwriting a file or deleting a directory that is not empty) will result in an error. Using the Force property overrides such errors. The default value is False.|
 
 ## Example
 
@@ -47,6 +46,6 @@ Archive ArchiveExample {
     Ensure = "Present"  # You can also set Ensure to "Absent"
     Path = "C:\Users\Public\Documents\Test.zip"
     Destination = "C:\Users\Public\Documents\ExtractionPath"
-} 
+}
 ```
 

dsc/authoringResource.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  Build Custom Windows PowerShell Desired State Configuration Resources
@@ -16,9 +15,9 @@ Windows PowerShell Desired State Configuration (DSC) has built-in resources that
 
 A DSC resource is a Windows PowerShell module. The module contains both the schema (the definition of the configurable properties) and the implementation (the code that does the actual work specified by a configuration) for the resource. A DSC resource schema can be defined in a MOF file, and the implementation is performed by a script module. Beginning with the support of PowerShell classes in version 5, the schema and implementation can both be defined in a class. The following topics describe in more detail how to create DSC resources.
 
-* [Writing a custom DSC resource with MOF](authoringResourceMOF.md) 
-* [Implementing a DSC resource in C#](authoringResourceMofCS.md) 
-* [Writing a custom DSC resource with PowerShell classes](authoringResourceClass.md) 
-* [Composite resources: Using a DSC configuration as a resource](authoringResourceComposite.md) 
-* [Using the Resource Designer tool](authoringResourceMofDesigner.md) 
+* [Writing a custom DSC resource with MOF](authoringResourceMOF.md)
+* [Implementing a DSC resource in C#](authoringResourceMofCS.md)
+* [Writing a custom DSC resource with PowerShell classes](authoringResourceClass.md)
+* [Composite resources: Using a DSC configuration as a resource](authoringResourceComposite.md)
+* [Using the Resource Designer tool](authoringResourceMofDesigner.md)
 

dsc/authoringResourceClass.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  Writing a custom DSC resource with PowerShell classes

dsc/authoringResourceComposite.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  Composite resources--Using a DSC configuration as a resource

dsc/authoringResourceMOF.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  Writing a custom DSC resource with MOF

dsc/authoringResourceMofCS.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  Authoring a DSC resource in C#

dsc/authoringResourceMofDesigner.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  Using the Resource Designer tool

dsc/azureDsc.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  Using DSC on Microsoft Azure

dsc/bootstrapDsc.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  Configure a virtual machines at initial boot-up by using DSC

dsc/builtInResource.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  Built-In Windows PowerShell Desired State Configuration Resources

dsc/compositeConfigs.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  Nesting configurations

dsc/configData.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  Using configuration data

dsc/configDataCredentials.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  Credentials Options in Configuration Data
@@ -18,7 +17,10 @@ To suppress these error and warning messages use the DSC configuration data keyw
 * **PsDscAllowPlainTextPassword**
 * **PsDscAllowDomainUser**
 
->**Notes:** <p>Storing/transmitting plaintext passwords unencrypted is generally not secure. Securing credentials by using the techniques covered later in this topic is recommended.</p> <p>The Azure Automation DSC service allows you to centrally manage credentials to be compiled in configurations and stored securely.  For information, see: [Compiling DSC Configurations / Credential Assets](https://docs.microsoft.com/en-in/azure/automation/automation-dsc-compile#credential-assets)</p>
+> [!NOTE]
+> Storing/transmitting plaintext passwords unencrypted is generally not secure. Securing credentials by using the techniques covered later in this topic is recommended.
+> The Azure Automation DSC service allows you to centrally manage credentials to be compiled in configurations and stored securely.
+> For information, see: [Compiling DSC Configurations / Credential Assets](/azure/automation/automation-dsc-compile#credential-assets)
 
 The following is an example of passing plain text credentials:
 
@@ -133,7 +135,8 @@ see [Running DSC with user credentials](runAsUser.md).
 Newer resources and custom resources can use this automatic property
 instead of creating their own property for credentials.
 
->**Note:** the design of some resources are to use multiple credentials for a specific reason, and they will have their own credential properties.
+> [!NOTE]
+> The design of some resources are to use multiple credentials for a specific reason, and they will have their own credential properties.
 
 To find the available credential properties on a resource
 use either `Get-DscResource -Name ResourceName -Syntax`
@@ -228,8 +231,8 @@ for node 'localhost'.
 ```
 
 This example has two issues:
-1.  An error explains that plain text passwords are not recommended
-2.  A warning advises against using a domain credential
+1. An error explains that plain text passwords are not recommended
+2. A warning advises against using a domain credential
 
 ## PsDscAllowPlainTextPassword
 
@@ -276,10 +279,11 @@ $cred = Get-Credential -UserName contoso\genericuser -Message "Password please"
 DomainCredentialExample -DomainCredential $cred -ConfigurationData $cd
 ```
 
->**Note:** `NodeName` cannot equal asterisk, a specific node name is mandatory.
+> [!NOTE]
+> `NodeName` cannot equal asterisk, a specific node name is mandatory.
+
+**Microsoft advises to avoid plain text passwords due to the significant security risk.**
 
-**Microsoft advises to avoid plain text passwords
-due to the significant security risk.**
 An exception would be when using the Azure Automation DSC service,
 only because the data is always stored encrypted
 (in transit, at rest in the service, and at rest on the node).
@@ -291,8 +295,7 @@ still generates the warning that using a domain account for a credential is not
 Using a local account eliminates potential exposure of domain credentials
 that could be used on other servers.
 
-**When using credentials with DSC resources,
-prefer a local account over a domain account when possible.**
+**When using credentials with DSC resources, prefer a local account over a domain account when possible.**
 
 If there is a '\' or '@' in the `Username` property of the credential,
 then DSC will treat it as a domain account.

dsc/configHelp.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  Writing help for DSC configurations

dsc/configurations.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  DSC Configurations

dsc/crossNodeDependencies.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  Specifying cross-node dependencies

dsc/debugResource.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  Debugging DSC resources

dsc/decisionMaker.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  Desired State Configuration Overview for Decision Makers

dsc/directCallResource.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  Calling DSC resource methods directly

dsc/docfx.json

@@ -13,7 +13,6 @@
             "breadcrumb_path":"bread/toc.json",
             "uhfHeaderId": "MSDocsHeader-Powershell",
             "layout": "conceptual",
-            "ms.locale": "en-us",
             "ROBOTS": "INDEX, FOLLOW",
             "ms.prod": "powershell",
             "ms.technology": "dsc",

dsc/dscCiCd.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  Building a Continuous Integration and Continuous Deployment pipeline with DSC

dsc/dscExamples.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  DSC Examples

dsc/enactingConfigurations.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-10-16
-author:  eslesar;mgreenegit
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  Enacting configurations
@@ -27,7 +26,7 @@ For example, if the configuration MOF is located at `C:\DSC\Configurations\local
 you would apply it to the local machine with the following command:
 `Start-DscConfiguration -Path 'C:\DSC\Configurations'`
 
-> __Note__: By default, DSC runs a configuration as a background job. To run the configuration interactively, call the 
+> __Note__: By default, DSC runs a configuration as a background job. To run the configuration interactively, call the
 >[Start-DscConfiguration](https://technet.microsoft.com/library/dn521623.aspx) with the __-Wait__ parameter.
 
 ## Pull mode

dsc/environmentResource.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  DSC Environment Resource

dsc/fileResource.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  DSC File Resource

dsc/gettingStarted.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  Getting Started with PowerShell Desired State Configuration

dsc/groupSetResource.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 description:  Provides a mechanism to manage local groups on the target node.

dsc/lnxArchiveResource.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  DSC for Linux nxArchive Resource

dsc/lnxBuiltInResources.md

@@ -1,6 +1,5 @@
 ---
 ms.date:  2017-06-12
-author:  eslesar
 ms.topic:  conceptual
 keywords:  dsc,powershell,configuration,setup
 title:  Built-In Desired State Configuration Resources for Linux