deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-18 03:43:39 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Update feature-update-maintenance-window.md

Browse Source 
Added PowerShell as language identifier to the code section. 
Put the Disclaimer section in the PowerShell code as comment. 
Removed surplus spaces on several line endings.
This commit is contained in:
Baard Hermansen
2021-06-04 02:03:37 +02:00
committed by GitHub
parent 2f714a60b3
commit 4cc511c578
1 changed files with 111 additions and 108 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
windows/deployment/update/feature-update-maintenance-window.md
View File

@ -62,7 +62,7 @@ Priority=Normal
You can use the new [Run Scripts](/sccm/apps/deploy-use/create-deploy-scripts) feature to run a PowerShell script like the sample below to create the SetupConfig.ini on target devices.
```
```powershell
#Parameters
Param(
[string] $PriorityValue = "Normal"
@ -91,6 +91,7 @@ foreach ($k in $iniSetupConfigKeyValuePair.Keys)
#Write content to file
New-Item $iniFilePath -ItemType File -Value $iniSetupConfigContent -Force
<#
Disclaimer
Sample scripts are not supported under any Microsoft standard support program or service. The sample scripts is
provided AS IS without warranty of any kind. Microsoft further disclaims all implied warranties including, without
@ -100,6 +101,7 @@ Microsoft, its authors, or anyone else involved in the creation, production, or
for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption,
loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample script
or documentation, even if Microsoft has been advised of the possibility of such damages.
#>
```
> [!NOTE]
@ -131,7 +133,7 @@ Before you deploy the feature updates, you can download the content as a separat
**Create a new deployment package**: Select this setting to create a new deployment package for the software updates that are in the deployment. Configure the following settings:
- **Name**: Specifies the name of the deployment package. The package must have a unique name that briefly describes the package content. It is limited to 50 characters.
- **Description**: Specifies the description of the deployment package. The package description provides information about the package contents and is limited to 127 characters.
- **Package source**: Specifies the location of the feature update source files. Type a network path for the source location, for example, \\server\sharename\path, or click **Browse** to find the network location. You must create the shared folder for the deployment package source files before you proceed to the next page.
- **Package source**: Specifies the location of the feature update source files. Type a network path for the source location, for example, \\\server\sharename\path, or click **Browse** to find the network location. You must create the shared folder for the deployment package source files before you proceed to the next page.
> [!NOTE]
> The deployment package source location that you specify cannot be used by another software deployment package.
@ -254,6 +256,7 @@ After you determine which feature updates you intend to deploy, you can manually
11. Click **Next** to deploy the feature update(s).
### Step 4: Monitor the deployment status
After you deploy the feature update(s), you can monitor the deployment status. Use the following procedure to monitor the deployment status:
1. In the Configuration Manager console, navigate to **Monitoring > Overview > Deployments**.