mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 02:13:43 +00:00
Merge branch 'release-mcc-ent' into nidos-mcc
This commit is contained in:
Vinay Pamnani
GitHub
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Create and configure MCCE cache nodes
|
||||
description: Details on how to create and configure Microsoft Connected Cache for Enterprise and Education (MCCE) cache nodes.
|
||||
title: Create and configure MCC cache nodes
|
||||
description: Details on how to create and configure Microsoft Connected Cache for Enterprise and Education (MCC) cache nodes.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: how-to
|
||||
@ -19,9 +19,12 @@ ms.date: 06/03/2024
|
||||
This article outlines how to create and configure your Microsoft Connected Cache for Enterprise and Education (MCC) cache nodes. The creation and configuration of your cache node takes place in Azure. The deployment of your cache node requires downloading and running an OS-specific provisioning package on your host machine.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
1. **Azure Pay-As-You-Go subscription**: Microsoft Connected Cache is a free-of-charge service hosted in Azure. You'll need a pay-as-you-go Azure subscription in order to onboard to our service. To create a subscription, go to [pay-as-you-go subscription page](https://azure.microsoft.com/offers/ms-azr-0003p/).
|
||||
2. **Hardware to host MCC**: The recommended configuration serves approximately 35,000 managed devices, downloading a 2-GB payload in 24-hour timeframe at a sustained rate of 6.5 Gbps.
|
||||
For more information on sizing and OS requirements, see [the prerequisites for using MCC for Enterprise and Education](mcc-ent-prerequisites.md).
|
||||
|
||||
For more information on sizing and OS requirements, see [the prerequisites for using MCC](mcc-ent-prerequisites.md).
|
||||
|
||||
|
||||
## Create MCC Azure resource
|
||||
|
||||
@ -72,7 +75,7 @@ az mcc ent resource create --mcc-resource-name <mymccresource> --resource-group
|
||||
|
||||
---
|
||||
|
||||
## Create cache node
|
||||
## Create MCC cache node
|
||||
|
||||
# [Azure portal](#tab/portal)
|
||||
|
||||
@ -118,7 +121,7 @@ az mcc ent node create --cache-node-name <mycachenode> --mcc-resource-name <mymc
|
||||
|
||||
---
|
||||
|
||||
## Configure cache node
|
||||
## Configure MCC cache node
|
||||
|
||||
# [Azure portal](#tab/portal)
|
||||
Enter required values to configure your cache node. To learn more about the definitions of each field, review the [Configuration](#general-configuration-fields) fields at the bottom of this article.
|
||||
@ -132,16 +135,17 @@ Don't forget to select save after adding configuration information.
|
||||
Use the following command to configure cache node for deployment to a **Linux** host machine.
|
||||
|
||||
Replace the following placeholders with your own information:
|
||||
|
||||
* *\<resource-group>*: An existing resource group in your subscription.
|
||||
* *\<mcc-resource-name>*: A name for your Microsoft Connected Cache for Enterprise resource.
|
||||
* *\<cache-node-name>*: The Azure region where your Microsoft Connected Cache will be located.
|
||||
* *\<physical-path>*: The cache drive path. You can add upto nine cache drives.
|
||||
* *\<size-in-gb>*: The size of cache drive. Must be at least 50 Gb.
|
||||
* *\<proxy>*: If proxy needs to be enabled or not.<br>
|
||||
Accepted values: enabled, disabled.<br>
|
||||
If proxy is set to enabled, you must provide proxy host and proxy port information
|
||||
* *\<proxy-host>*: The proxy host name or ip address
|
||||
* *\<proxy-port>*: Proxy port
|
||||
Accepted values: enabled, disabled<br>
|
||||
Proxy should be set to enabled if the cache node will need to pass through a network proxy to download content. The provided proxy will also be used during deployment of the MCC cache node to your host machine.
|
||||
* *\<proxy-host>*: The proxy host name or ip address. Required if proxy is set to enabled.
|
||||
* *\<proxy-port>*: Proxy port number. Required if proxy is set to enabled.
|
||||
* *\<auto-update-ring>*: Update ring the cache node should have.<br>
|
||||
Accepted values: slow, fast.<br>
|
||||
If update ring is set to slow, you must provide the day of week, time of day and week of month the cache node should be updated.
|
||||
@ -164,6 +168,7 @@ az mcc ent node update --cache-node-name <mycachenode> --mcc-resource-name <mymc
|
||||
Use the following command to configure cache node for deployment to a **Windows** host machine.
|
||||
|
||||
Replace the following placeholders with your own information:
|
||||
|
||||
* *\<resource-group>*: An existing resource group in your subscription.
|
||||
* *\<mcc-resource-name>*: A name for your Microsoft Connected Cache for Enterprise resource.
|
||||
* *\<cache-node-name>*: The Azure region where your Microsoft Connected Cache will be located.
|
||||
@ -171,10 +176,10 @@ Replace the following placeholders with your own information:
|
||||
Accepted value: /var/mcc
|
||||
* *\<size-in-gb>*: The size of cache drive. Must be at least 50 Gb.
|
||||
* *\<proxy>*: If proxy needs to be enabled or not.<br>
|
||||
Accepted values: enabled, disabled.<br>
|
||||
If proxy is set to enabled, you must provide proxy host and proxy port information
|
||||
* *\<proxy-host>*: The proxy host name or ip address
|
||||
* *\<proxy-port>*: Proxy port
|
||||
Accepted values: enabled, disabled<br>
|
||||
Proxy should be set to enabled if the cache node will need to pass through a network proxy to download content. The provided proxy will also be used during deployment of the MCC cache node to your host machine.
|
||||
* *\<proxy-host>*: The proxy host name or ip address. Required if proxy is set to enabled.
|
||||
* *\<proxy-port>*: Proxy port number. Required if proxy is set to enabled.
|
||||
* *\<auto-update-ring>*: Update ring the cache node should have.<br>
|
||||
Accepted values: slow, fast.<br>
|
||||
If update ring is set to slow, you must provide the day of week, time of day and week of month the cache node should be updated.
|
||||
@ -235,12 +240,12 @@ To deploy cache nodes using Azure CLI, see [Manage cache nodes using CLI](mcc-en
|
||||
|
||||
#### Proxy settings
|
||||
<br>
|
||||
You can choose to enable or disable proxy settings on your cache node.
|
||||
You can choose to enable or disable proxy settings on your cache node. Proxy should be set to enabled if the cache node will need to pass through a network proxy to download content. The provided proxy will also be used during deployment of the MCC cache node to your host machine.
|
||||
|
||||
<br>
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Enabling or disabling the proxy settings after your cache node has been deployed will require running the provisioning script again. This will ensure that proxy changes are in effect on the cache node.
|
||||
>Enabling or disabling the proxy settings after your cache node has been deployed will require running the provisioning script on the host machine again. This will ensure that proxy changes are in effect on the cache node.
|
||||
|
||||
| Field Name |Expected Value |Description|
|
||||
|---|---|---|
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Deploy MCCE cache software to a Linux host machine
|
||||
description: Details on how to deploy Microsoft Connected Cache for Enterprise and Education (MCCE) cache software to a Linux host machine.
|
||||
title: Deploy MCC cache software to a Linux host machine
|
||||
description: Details on how to deploy Microsoft Connected Cache for Enterprise and Education (MCC) cache software to a Linux host machine.
|
||||
author: chrisjlin
|
||||
ms.author: lichris
|
||||
manager: naengler
|
||||
@ -13,13 +13,15 @@ appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>
|
||||
---
|
||||
|
||||
# Deploy MCCE cache node to a Linux host machine
|
||||
# Deploy Microsoft Connected Cache caching software to a Linux host machine
|
||||
|
||||
This article describes how to deploy Microsoft Connected Cache for Enterprise and Education (MCCE) caching software to a Linux host machine.
|
||||
This article describes how to deploy Microsoft Connected Cache for Enterprise and Education (MCC) caching software to a Linux host machine.
|
||||
|
||||
Before deploying MCCE to a Linux host machine, ensure that the host machine meets all [requirements](mcc-ent-prerequisites.md), and that you have [created and configured your MCC Azure resource](https://aka.ms/mccent-create-resources).
|
||||
Before deploying MCC to a Linux host machine, ensure that the host machine meets all [requirements](mcc-ent-prerequisites.md), and that you have [created and configured your MCC Azure resource and cache node](mcc-ent-create-resource-and-cache.md).
|
||||
|
||||
## Steps to deploy MCCE cache node to Linux
|
||||
## Steps to deploy MCC cache node to Linux
|
||||
|
||||
# [Azure portal](#tab/portal)
|
||||
|
||||
1. Within the Azure portal, navigate to the "Provisioning" tab of your cache node and copy the provisioning command.
|
||||
1. Download the provisioning package using the button at the top of the Cache Node Configuration page and extract the package onto the host machine.
|
||||
@ -27,6 +29,26 @@ Before deploying MCCE to a Linux host machine, ensure that the host machine meet
|
||||
1. Set access permissions to allow the `provisionmcc.sh` script within the provisioning package directory to execute.
|
||||
1. Run the provisioning command on the host machine.
|
||||
|
||||
# [Azure CLI](#tab/cli)
|
||||
|
||||
To deploy a cache node programmatically, you'll need to use Azure CLI to get the cache node's provisioning details and then run the provisioning command on the host machine.
|
||||
|
||||
1. To get the cache node's provisioning details, use `az mcc ent node get-provisioning-details`
|
||||
|
||||
```azurecli-interactive
|
||||
az mcc ent node get-provisioning-details --cache-node-name mycachenode --mcc-resource-name mymccresource --resource-group myrg
|
||||
```
|
||||
|
||||
1. Save the resulting output. These values will be passed as parameters within the provisioning command.
|
||||
1. Download and extract the [MCC provisioning package for Linux](https://aka.ms/MCC-Ent-InstallScript-Linux) to your host machine.
|
||||
1. Open a command line window *as administrator* on the host machine, then change directory to the extracted provisioning package.
|
||||
1. Set access permissions to allow the `provisionmcc.sh` script within the provisioning package directory to execute.
|
||||
1. Replace the values in the following provisioning command before running it on the host machine.
|
||||
|
||||
```azurepowershell-interactive
|
||||
sudo ./provisionmcc.sh customerid="enter mccResourceId here" cachenodeid=" enter cacheNodeId here " customerkey=" enter customerKey here " registrationkey="enter registrationKey here" drivepathandsizeingb="enter physicalPath value,enter sizeInGb value here" shoulduseproxy="enter true if present, enter false if not" proxyurl=http://enter proxy hostname:enter port
|
||||
```
|
||||
|
||||
## Next step
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
@ -35,4 +57,4 @@ Before deploying MCCE to a Linux host machine, ensure that the host machine meet
|
||||
## Related content
|
||||
|
||||
- [Deploy to a Windows host machine](mcc-ent-deploy-to-windows.md)
|
||||
- [Uninstall MCCE](mcc-ent-uninstall-cache-node.md)
|
||||
- [Uninstall MCC](mcc-ent-uninstall-cache-node.md)
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Deploy MCCE cache software to a Windows host machine
|
||||
description: Details on how to deploy Microsoft Connected Cache for Enterprise and Education (MCCE) cache software to a Windows host machine.
|
||||
title: Deploy MCC cache software to a Windows host machine
|
||||
description: Details on how to deploy Microsoft Connected Cache for Enterprise and Education (MCC) cache software to a Windows host machine.
|
||||
author: chrisjlin
|
||||
ms.author: lichris
|
||||
manager: naengler
|
||||
@ -13,32 +13,58 @@ appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>
|
||||
---
|
||||
|
||||
# Deploy MCCE cache node to a Windows host machine
|
||||
# Deploy Microsoft Connected Cache caching software to a Windows host machine
|
||||
|
||||
This article describes how to deploy Microsoft Connected Cache for Enterprise and Education (MCCE) caching software to a Windows host machine.
|
||||
This article describes how to deploy Microsoft Connected Cache for Enterprise and Education (MCC) caching software to a Windows host machine.
|
||||
|
||||
Deploying MCCE to a Windows host machine requires designating a [Group Managed Service Account (gMSA)](/windows-server/security/group-managed-service-accounts/getting-started-with-group-managed-service-accounts) or a [Local User Account](https://support.microsoft.com/windows/create-a-local-user-or-administrator-account-in-windows-20de74e0-ac7f-3502-a866-32915af2a34d) as the MCCE runtime account. This prevents tampering with the MCC container and the cached content on the host machine.
|
||||
Deploying MCC to a Windows host machine requires designating a [Group Managed Service Account (gMSA)](/windows-server/security/group-managed-service-accounts/getting-started-with-group-managed-service-accounts) or a [Local User Account](https://support.microsoft.com/windows/create-a-local-user-or-administrator-account-in-windows-20de74e0-ac7f-3502-a866-32915af2a34d) as the MCC runtime account. This prevents tampering with the MCC container and the cached content on the host machine.
|
||||
|
||||
Before deploying MCCE to a Windows host machine, ensure that the host machine meets all [requirements](mcc-ent-prerequisites.md), and that you have [created and configured your MCC Azure resource](https://aka.ms/mccent-create-resources).
|
||||
Before deploying MCC to a Windows host machine, ensure that the host machine meets all [requirements](mcc-ent-prerequisites.md), and that you have [created and configured your MCC Azure resource](mcc-ent-create-resource-and-cache.md).
|
||||
|
||||
## Steps to deploy MCCE cache node to Windows
|
||||
## Steps to deploy MCC cache node to Windows
|
||||
|
||||
# [Azure portal](#tab/portal)
|
||||
|
||||
1. Within the Azure portal, navigate to the "Provisioning" tab of your cache node and copy the provisioning command.
|
||||
1. Download the provisioning package using the button at the top of the Cache Node Configuration page and extract the package onto the host machine.
|
||||
1. Open a PowerShell windows *as administrator* on the host machine, then change directory to the extracted provisioning package.
|
||||
1. Open a PowerShell window *as administrator* on the host machine, then change directory to the extracted provisioning package.
|
||||
1. Set the Execution Policy to "Unrestricted" to allow the provisioning scripts to run.
|
||||
1. Create a `$User` environment variable containing the username of the account you intend to designate as the MCC runtime account. For gMSAs, the value should be formatted as `"Domain\Username$"`. For Local User accounts, `$User` should be formatted as `"LocalMachineName\Username"`.
|
||||
- If you're using a Local User account as the MCCE runtime account, you'll also need to create a [PSCredential Object](/dotnet/api/system.management.automation.pscredential) named `$myLocalAccountCredential`.
|
||||
|
||||
If you're using a Local User account as the MCC runtime account, you'll also need to create a [PSCredential Object](/dotnet/api/system.management.automation.pscredential) named `$myLocalAccountCredential`.
|
||||
|
||||
1. Run the provisioning command on the host machine.
|
||||
|
||||
# [Azure CLI](#tab/cli)
|
||||
|
||||
To deploy a cache node programmatically, you'll need to use Azure CLI to get the cache node's provisioning details and then run the provisioning command on the host machine.
|
||||
|
||||
1. To get the cache node's provisioning details, use `az mcc ent node get-provisioning-details`.
|
||||
|
||||
```azurecli-interactive
|
||||
az mcc ent node get-provisioning-details --cache-node-name mycachenode --mcc-resource-name mymccresource --resource-group myrg
|
||||
```
|
||||
|
||||
1. Save the resulting output. These values will be passed as parameters within the provisioning command.
|
||||
1. Download and extract the [MCC provisioning package for Windows](https://aka.ms/MCC-Ent-InstallScript-WSL) to your host machine.
|
||||
1. Open a PowerShell window *as administrator* on the host machine, then change directory to the extracted provisioning package.
|
||||
1. Set the Execution Policy to "Unrestricted" to allow the provisioning scripts to run.
|
||||
1. Create a `$User` environment variable containing the username of the account you intend to designate as the MCC runtime account. For gMSAs, the value should be formatted as `"Domain\Username$"`. For Local User accounts, `$User` should be formatted as `"LocalMachineName\Username"`.
|
||||
|
||||
If you're using a Local User account as the MCC runtime account, you'll also need to create a [PSCredential Object](/dotnet/api/system.management.automation.pscredential) named `$myLocalAccountCredential`.
|
||||
|
||||
1. Replace the values in the following provisioning command before running it on the host machine. Note that `-mccLocalAccountCredential $myLocalAccountCredential` is only needed if you are using a Local User account as the MCC runtime account.
|
||||
|
||||
```powershell-interactive
|
||||
./provisionmcconwsl.ps1 -installationFolder c:\mccwsl01 -customerid [enter mccResourceId here] -cachenodeid [enter cacheNodeId here] -customerkey [enter customerKey here] -registrationkey [enter registration key] -cacheDrives "/var/mcc,enter drive size" -shouldUseProxy [enter true if present, enter false if not] -proxyurl "http://[enter proxy host name]:[enter port]" -mccRunTimeAccount $User -mccLocalAccountCredential $myLocalAccountCredential
|
||||
```
|
||||
|
||||
## Next step
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [Verify cache node functionality](mcc-ent-verify-cache-node.md)
|
||||
|
||||
<!-- OR -->
|
||||
|
||||
## Related content
|
||||
|
||||
- [Deploy to a Linux host machine](mcc-ent-deploy-to-linux.md)
|
||||
- [Uninstall MCCE](mcc-ent-uninstall-cache-node.md)
|
||||
- [Uninstall MCC](mcc-ent-uninstall-cache-node.md)
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: MCCE Overview
|
||||
description: Overview, supported scenarios, and content types for Microsoft Connected Cache for Enterprise and Education (MCCE).
|
||||
title: MCC Overview
|
||||
description: Overview, supported scenarios, and content types for Microsoft Connected Cache for Enterprise and Education (MCC).
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
### YamlMime:FAQ
|
||||
metadata:
|
||||
title: MCCE Frequently Asked Questions
|
||||
description: The following article is a list of frequently asked questions for Microsoft Connected Cache for Enterprise (MCCE).
|
||||
title: MCC Frequently Asked Questions
|
||||
description: The following article is a list of frequently asked questions for Microsoft Connected Cache for Enterprise (MCC).
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: faq
|
||||
@ -16,7 +16,7 @@ metadata:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
ms.date: 06/03/2024
|
||||
title: Microsoft Connected Cache for Enteprise Frequently Asked Questions
|
||||
title: Microsoft Connected Cache for Enterprise Frequently Asked Questions
|
||||
summary: |
|
||||
Frequently asked questions about Microsoft Connected Cache for Enterprise
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Manage MCCE cache nodes using CLI
|
||||
description: Details on how to manage Microsoft Connected Cache for Enterprise (MCCE) cache nodes via Azure CLI commands.
|
||||
title: Manage MCC cache nodes using CLI
|
||||
description: Details on how to manage Microsoft Connected Cache for Enterprise (MCC) cache nodes via Azure CLI commands.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: how-to
|
||||
@ -37,6 +37,7 @@ To learn more about installting extensions, visit [Install the MCC extension.](/
|
||||
<br>
|
||||
|
||||
### 1. Create a Resource group
|
||||
|
||||
The first step is to create a resource group if you don't already have one.
|
||||
An Azure resource group is a logical container into which Azure resources are deployed and managed.
|
||||
|
||||
@ -49,8 +50,8 @@ az group create --name myrg --location westus
|
||||
|
||||
Once the resource group is created, you'll need to create a Microsoft Connected Cache for Enterprise resource.
|
||||
|
||||
### 2. Create an MCC Azure resource
|
||||
|
||||
### 2. Create an Azure resource
|
||||
An MCC Azure resource is a top-level Azure resource under which cache nodes can be created.
|
||||
|
||||
To create an MCC Azure resource, use `az mcc ent resource create`
|
||||
@ -70,6 +71,7 @@ The next step is to create a cache node under this resource.
|
||||
|
||||
|
||||
### 3. Create a cache node
|
||||
|
||||
To create a cache node, use `az mcc ent node create`
|
||||
|
||||
```azurecli-interactive
|
||||
@ -84,6 +86,7 @@ az mcc ent node create --cache-node-name mycachenode --mcc-resource-name mymccre
|
||||
<br>
|
||||
|
||||
### 4. Confirm cache node creation
|
||||
|
||||
Before you can start configuring your cache node, you need to confirm that the cache node was successfully created.
|
||||
|
||||
To confirm cache node creation, use `az mcc ent node show`
|
||||
@ -104,6 +107,7 @@ Once successful cache node creation is confirmed, you can proceed to configure t
|
||||
|
||||
|
||||
### 5. Configure cache node
|
||||
|
||||
To configure your cache node, use `az mcc ent node update`
|
||||
|
||||
The below example configures a Linux cache node with proxy enabled:
|
||||
@ -122,6 +126,7 @@ az mcc ent node update --cache-node-name <mycachenode> --mcc-resource-name <mymc
|
||||
<br>
|
||||
|
||||
### 6. Get provisioning details for the cache node
|
||||
|
||||
After successfully configuring the cache node, the next step is to deploy the cache node to a host machine. To deploy the cache node, you'll need to create a provisioning script with relevant information.
|
||||
|
||||
To get the relevant information for provisioning script, use `az mcc ent node get-provisioning-details`
|
||||
@ -132,43 +137,66 @@ az mcc ent node get-provisioning-details --cache-node-name mycachenode --mcc-res
|
||||
|
||||
Save the resulting values for cacheNodeId, customerKey, mccResourceId, registrationKey. These GUIDs are needed to create the provisioning script.
|
||||
|
||||
<br>
|
||||
### Example script:
|
||||
|
||||
### 7. Deploy cache node
|
||||
Below is a pseudocode example of how to script bulk creation and configuration of an MCC Azure resource and multiple MCC cache nodes.
|
||||
|
||||
<!--# [Bash](#tab/bash)
|
||||
|
||||
#### Deploy cache node to Linux host machine
|
||||
Before you deploy your cache node to a Linux host machine, make sure you have met the prerequisites listed here: [Host machine requirements](mcc-ent-prerequisites.md)
|
||||
:::code language="azurecli" source="~/azure_cli_scripts/azure-cli/create-azure-resources-at-scale/bash/create-azure-resources-at-scale.sh" id="step4":::
|
||||
|
||||
Use the following link to download and extract the Linux-compatible MCCE provisioning package onto the host machine.
|
||||
In your console output, are you missing the last row in your CSV file? This can be caused by a missing line continuation character after the last line. Add a blank line at the end of your CSV file to fix the issue.
|
||||
|
||||
[Download MCC provisioning package for Linux host machine](https://aka.ms/MCC-Ent-InstallScript-Linux)
|
||||
# [PowerShell](#tab/powershell)
|
||||
|
||||
<br>
|
||||
:::code language="azurecli" source="~/azure_cli_scripts/azure-cli/create-azure-resources-at-scale/powershell/create-azure-resources-at-scale.ps1" id="step4":::
|
||||
|
||||
To deploy the cache node to a **Linux** host machine, see [Deploy cache node to Linux](mcc-ent-deploy-to-linux.md)
|
||||
<br>
|
||||
-->
|
||||
|
||||
#### Deploy cache node to Windows host machine
|
||||
# [PowerShell](#tab/powershell)
|
||||
|
||||
Before you deploy your cache node to a Windows host machine, make sure you have met the prerequisites listed here: [Host machine requirements](mcc-ent-prerequisites.md)
|
||||
```powershell
|
||||
#Define variables
|
||||
$mccResourceName = "myMCCResource"
|
||||
$cacheNodeName = "demo-node"
|
||||
$cacheNodeOperatingSystem = "Windows"
|
||||
$resourceGroup = "myRG"
|
||||
$resourceLocation = "westus"
|
||||
$cacheNodesToCreate = 2
|
||||
$proxyHost = "myProxy.com"
|
||||
$proxyPort = "8080"
|
||||
$waitTime = 3
|
||||
|
||||
Use the following link to download and extract the Windows-compatible MCCE provisioning package onto the host machine.
|
||||
[Download MCC provisioning package for Windows host machine](https://aka.ms/MCC-Ent-InstallScript-WSL)
|
||||
<br>
|
||||
#Create MCC Az resource
|
||||
az mcc ent resource create --mcc-resource-name $mccResourceName --location $resourceLocation --resource-group $resourceGroup
|
||||
|
||||
To deploy the cache node to a **Windows** host machine, see [Deploy cache node to Windows](mcc-ent-deploy-to-windows.md)
|
||||
#Loop through $cacheNodesToCreate iterations
|
||||
for ($cacheNodeNumber = 1; $cacheNodeNumber -le $cacheNodesToCreate; $cacheNodeNumber++) {
|
||||
$iteratedCacheNodeName = $cacheNodeName + "-" + $cacheNodeNumber
|
||||
|
||||
#Create cache node
|
||||
az mcc ent node create --cache-node-name $iteratedCacheNodeName --mcc-resource-name $mccResourceName --host-os $cacheNodeOperatingSystem --resource-group $resourceGroup
|
||||
|
||||
<br>
|
||||
#Get cache node state
|
||||
$cacheNodeState = $(az mcc ent node show --cache-node-name $iteratedCacheNodeName --mcc-resource-name $mccResourceName --resource-group $resourceGroup --query "cacheNodeState") | ConvertFrom-Json
|
||||
|
||||
$howLong = 0
|
||||
#Wait until cache node state returns "Not Configured"
|
||||
while ($cacheNodeState -ne "Not Configured") {
|
||||
Write-Output "Waiting for cache node creation to complete...$howLong seconds"
|
||||
Start-Sleep -Seconds $waitTime
|
||||
$howLong += $waitTime
|
||||
|
||||
$cacheNodeState = $(az mcc ent node show --cache-node-name $iteratedCacheNodeName --mcc-resource-name $mccResourceName --resource-group $resourceGroup --query "cacheNodeState") | ConvertFrom-Json
|
||||
}
|
||||
|
||||
#Configure cache node
|
||||
az mcc ent node update --cache-node-name $iteratedCacheNodeName --mcc-resource-name $mccResourceName --resource-group $resourceGroup --cache-drive "[{physical-path:/var/mcc,size-in-gb:50}]" --proxy enabled --proxy-host $proxyHost --proxy-port $proxyPort
|
||||
}
|
||||
```
|
||||
|
||||
## Next step
|
||||
|
||||
To verify cache node functionality, see [Verify cache node functionality](mcc-ent-verify-cache-node.md)
|
||||
|
||||
|
||||
<br>
|
||||
<br>
|
||||
|
||||
### Sample script:
|
||||
Below is a pseudo code that shows how the above can be scripted for bulk creation and configuration of cache node.
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [Deploy cache node to Linux host machine](mcc-ent-deploy-to-Linux.md)
|
||||
> [Deploy cache node to Windows host machine](mcc-ent-deploy-to-Windows.md)
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Monitor usage of MCCE cache nodes
|
||||
description: Details on how to monitor the usage of Microsoft Connected Cache for Enterprise (MCCE) cache nodes.
|
||||
title: Monitor usage of MCC cache nodes
|
||||
description: Details on how to monitor the usage of Microsoft Connected Cache for Enterprise (MCC) cache nodes.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: how-to
|
||||
@ -14,7 +14,7 @@ appliesto:
|
||||
ms.date: 09/04/2024
|
||||
---
|
||||
|
||||
# Monitor MCC cache node usage
|
||||
# Monitor Microsoft Connected Cache cache node usage
|
||||
|
||||
Tracking the status and performance of your MCC cache node is essential to making sure that you're getting the most out of the service.
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: MCCE prerequisites
|
||||
description: Details of prerequisites and recommendations for using Microsoft Connected Cache for Enterprise and Education (MCCE).
|
||||
title: MCC prerequisites
|
||||
description: Details of prerequisites and recommendations for using Microsoft Connected Cache for Enterprise and Education (MCC).
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
@ -23,9 +23,9 @@ This article details the requirements and recommendations for using Microsoft Co
|
||||
|
||||
If you don't have an Azure subscription already, you can create an Azure [pay-as-you-go](https://azure.microsoft.com/offers/ms-azr-0003p/) account, which requires a credit card for verification purposes. For more information, see the [Azure Free Account FAQ](https://azure.microsoft.com/free/free-account-faq/).
|
||||
|
||||
The Azure resources used for MCCE will be free to you during this public preview.
|
||||
The Azure resources used for MCC will be free to you during this public preview.
|
||||
|
||||
- **E3/E5 or A3/A5 license**: Your organization must have one of the following license subscriptions for each device that downloads content from an MCCE cache node.
|
||||
- **E3/E5 or A3/A5 license**: Your organization must have one of the following license subscriptions for each device that downloads content from an MCC cache node.
|
||||
|
||||
- [Windows Enterprise E3 or E5](/windows/whats-new/windows-licensing#windows-11-enterprise), included in [Microsoft 365 F3, E3, or E5](https://www.microsoft.com/microsoft-365/enterprise/microsoft365-plans-and-pricing?msockid=32c407b43d5968050f2b13443c746916)
|
||||
- Windows Education A3 or A5, included in [Microsoft 365 A3 or A5](https://www.microsoft.com/education/products/microsoft-365?msockid=32c407b43d5968050f2b13443c746916#Education-plans)
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: MCCE Private Preview
|
||||
description: Details on Microsoft Connected Cache for Enterprise (MCCE) Private Preview
|
||||
title: MCC Private Preview
|
||||
description: Details on Microsoft Connected Cache for Enterprise (MCC) Private Preview
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
@ -12,13 +12,13 @@ appliesto:
|
||||
ms.date: 06/03/2024
|
||||
---
|
||||
|
||||
# Microsoft Connected Cache for Enterprise and Education (early preview)
|
||||
# Microsoft Connected Cache for Enterprise and Education (MCC) Private Preview
|
||||
|
||||
If you participated in the MCCE early preview, thank you for your collaboration and feedback.
|
||||
If you participated in the MCC early preview, thank you for your collaboration and feedback.
|
||||
|
||||
To continue using Microsoft Connected Cache for Enterprise and Education (MCC), we strongly recommend that you upgrade your existing cache nodes to the new release. Cache nodes created and deployed during early preview should still function but can no longer be managed or monitored remotely via the MCC Azure service.
|
||||
To continue using MCC, we strongly recommend that you upgrade your existing cache nodes to the Public Preview release. Cache nodes created and deployed during early preview should still function but can no longer be managed or monitored remotely via the MCC Azure service.
|
||||
|
||||
As such, we strongly recommend you [recreate your existing cache nodes in Azure](mcc-ent-create-resource-and-cache.md) and then [redeploy the MCCE caching software to your host machines](mcc-ent-deploy-to-windows.md) using the latest OS-specific installer. You don't need to re-create your MCC Azure resource.
|
||||
As such, we strongly recommend you [recreate your existing cache nodes in Azure](mcc-ent-create-resource-and-cache.md) and then [redeploy the MCC caching software to your host machines](mcc-ent-deploy-to-windows.md) using the latest OS-specific installer. You don't need to re-create your MCC Azure resource.
|
||||
|
||||
## Next step
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: MCCE Release Notes
|
||||
description: Release Notes for Microsoft Connected Cache for Enterprise and Education (MCCE).
|
||||
title: MCC Release Notes
|
||||
description: Release Notes for Microsoft Connected Cache for Enterprise and Education (MCC).
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
@ -33,7 +33,7 @@ This article contains details about the latest releases of MCC. Since MCC is a P
|
||||
- Added support for creating both Windows-hosted and Linux-hosted cache nodes under the same MCC Azure resource
|
||||
- Added Azure CLI support for programmatic creation and management of MCC Azure resources and cache nodes
|
||||
- Added support for unauthenticated proxy and cloud proxy integration
|
||||
- Added ability to set each cache node's Update Ring to govern cadence of MCCE container updates
|
||||
- Added ability to set each cache node's Update Ring to govern cadence of MCC container updates
|
||||
|
||||
## Related content
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: MCCE support and troubleshooting
|
||||
description: Details on how to troubleshoot and seek support for Microsoft Connected Cache for Enterprise (MCCE).
|
||||
title: MCC support and troubleshooting
|
||||
description: Details on how to troubleshoot and seek support for Microsoft Connected Cache for Enterprise (MCC).
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: how-to
|
||||
@ -22,13 +22,11 @@ ms.date: 09/27/2024
|
||||
|
||||
This article contains instructions on how to troubleshoot different issues you may encounter while using MCC. These issues are categorized by the task in which they may be encountered. For example, this next section covers troubleshooting [MCC Azure resource creation](mcc-ent-create-resource-and-cache.md).
|
||||
|
||||
|
||||
## Steps to obtain an Azure subscription ID
|
||||
|
||||
<!--Using include file, get-azure-subscription.md, do/mcc-isp.md for shared content-->
|
||||
[!INCLUDE [Get Azure subscription](includes/get-azure-subscription.md)]
|
||||
|
||||
|
||||
## Troubleshooting Azure resource creation
|
||||
|
||||
MCC Azure resource creation can be initiated using either the Azure portal or the Azure CLI command set. If you're encountering an error during resource creation, check that you have the necessary RPaaS permissions and have filled out all required fields.
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Uninstall MCCE cache nodes
|
||||
description: Details on how to uninstall Microsoft Connected Cache for Enterprise and Education (MCCE) from a host machine.
|
||||
title: Uninstall MCC cache nodes
|
||||
description: Details on how to uninstall Microsoft Connected Cache for Enterprise and Education (MCC) from a host machine.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: how-to
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Update MCCE cache nodes
|
||||
description: Details on how Microsoft Connected Cache for Enterprise and Education (MCCE) cache nodes are updated by Microsoft.
|
||||
title: Update MCC cache nodes
|
||||
description: Details on how Microsoft Connected Cache for Enterprise and Education (MCC) cache nodes are updated by Microsoft.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: how-to
|
||||
@ -13,25 +13,28 @@ appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>
|
||||
ms.date: 09/27/2024
|
||||
---
|
||||
# Configure container update frequency for Microsoft Connected Cache for Enterprise and Education (MCCE)
|
||||
# Configure container update frequency for Microsoft Connected Cache for Enterprise and Education (MCC)
|
||||
|
||||
Microsoft Connected Cache for Enterprise and Education (MCCE) caching software is deployed to host machines as a container. The container OS and any software component within the container will need to be updated for security vulnerabilities or quality issues, or performance improvements required to successfully operate the caching software. These Microsoft-published container updates are called "MCCE updates" in this article.
|
||||
Microsoft Connected Cache for Enterprise and Education (MCC) caching software is deployed to host machines as a container. The container OS and any software component within the container need to be updated to address security vulnerabilities and improve quality and performance. These Microsoft-published container updates are referred to as "MCC updates" in this article.
|
||||
|
||||
Microsoft silently deploys MCCE updates to your cache nodes based on the Update Ring setting you configure for each cache node.
|
||||
Microsoft silently deploys MCC updates to your cache nodes based on the Update Ring setting you configure for each cache node.
|
||||
|
||||
## Update rings
|
||||
|
||||
MCCE cache nodes can be configured to either the "Fast" or "Slow" update ring. If configured to update as part of the Fast ring, the cache node will be silently updated by Microsoft soon after the update is made available. If configured to update as part of the Slow ring, the cache node is silently updated by Microsoft within five weeks of the update becoming available.
|
||||
MCC cache nodes can be configured to either the "Fast" or "Slow" update ring. If configured to update as part of the Fast ring, the cache node will be silently updated by Microsoft soon after the update is made available. If configured to update as part of the Slow ring, the cache node is silently updated by Microsoft within five weeks of the update becoming available.
|
||||
|
||||
In other words, configuring cache nodes to update as part of the Slow ring provides users with the option to delay the update process until they have validated that the latest MCCE update works within their environment. For example, a user could configure a test cache node to update as part of the Fast ring and validate that clients can successfully interact with the test cache node after the latest MCCE update has been applied. This builds confidence that service won't be interrupted when the production cache nodes are updated as part of the Slow ring.
|
||||
In other words, configuring cache nodes to update as part of the Slow ring provides users with the option to delay the update process until they have validated that the latest MCC update works within their environment. For example, a user could configure a test cache node to update as part of the Fast ring and validate that clients can successfully interact with the test cache node after the latest MCC update has been applied. This builds confidence that service won't be interrupted when the production cache nodes are updated as part of the Slow ring.
|
||||
|
||||
### Update ring options
|
||||
|
||||
>[!IMPORTANT]
|
||||
>In the event of a critical security patch, Microsoft may elect to initiate an MCC update to your cache node as soon as possible (even if the cache node has been set to the Slow Ring). Visit the [Release notes](mcc-ent-release-notes.md) page for a detailed changelog of each MCC update.
|
||||
|
||||
#### Fast Ring
|
||||
All MCCE cache nodes are configured to update as part of the Fast ring by default. MCCE cache nodes in the Fast ring will be updated soon after an update is made available. Microsoft will silently update cache nodes at a time of day when update traffic is likely to be minimal, such as 3:00 AM (local time) on Saturday.
|
||||
All MCC cache nodes are configured to update as part of the Fast ring by default. MCC cache nodes in the Fast ring will be updated soon after an update is made available. Microsoft will silently update cache nodes at a time of day when update traffic is likely to be minimal, such as 3:00 AM (local time) on Saturday.
|
||||
|
||||
#### Slow Ring
|
||||
Configuring an MCCE cache node to update as part of the Slow ring provides users with the option to delay MCCE software updates until the update can be validated. There are three settings that control when MCCE updates will be applied to MCCE cache nodes. All update ring settings can be managed from the Azure portal or through Azure CLI.
|
||||
Configuring an MCC cache node to update as part of the Slow ring provides users with the option to delay MCC software updates until the update can be validated. There are three settings that control when MCC updates will be applied to MCC cache nodes. All update ring settings can be managed from the Azure portal or through Azure CLI.
|
||||
|
||||
| Setting | Description |
|
||||
| --- | --- |
|
||||
@ -41,15 +44,15 @@ Configuring an MCCE cache node to update as part of the Slow ring provides users
|
||||
|
||||
## Update process
|
||||
|
||||
When Microsoft publishes an MCCE update, the MCCE service attempts to update all MCCE cache nodes based on their Update Ring membership. If a cache node can't complete the silent MCCE update within 6 hours of starting, an error message is surfaced in the Azure portal.
|
||||
When Microsoft publishes an MCC update, the MCC service attempts to update all MCC cache nodes based on their Update Ring membership. If a cache node can't complete the silent MCC update within 6 hours of starting, an error message is surfaced in the Azure portal.
|
||||
|
||||
## Update terminology, criteria, and SLA
|
||||
|
||||
MCCE updates will be released based on need instead of on a set cadence.
|
||||
MCC updates will be released based on need instead of on a set cadence.
|
||||
|
||||
| Update type | Criteria and SLA |
|
||||
| --- | --- |
|
||||
| Security | Security updates are the highest priority and will be released based on the severity rating of the vulnerability. [Critical and High](https://nvd.nist.gov/vuln-metrics/cvss) vulnerabilities will be released by Microsoft within 60 days of discovery. [Medium and Low](https://nvd.nist.gov/vuln-metrics/cvss) vulnerabilities will be released by Microsoft within 120 days |
|
||||
| Quality | Quality updates fix a specific problem and addresses a noncritical, non-security-related bug. Quality updates could include performance fixes for a specific problem or changes related to cache efficiency or maximum egress for example. Quality updates will be released along with security updates or when necessary to ensure proper functioning of the Microsoft Connected Cache software. |
|
||||
| Quality | Quality updates fix a specific problem and addresses a noncritical, non-security-related bug. Quality updates could include performance fixes for a specific problem or changes related to cache efficiency or maximum egress for example. Quality updates are released along with security updates or when necessary to ensure proper functioning of the Microsoft Connected Cache software. |
|
||||
|
||||
For information on all released Microsoft Connected Cache updates see the [MCCE release notes](mcc-ent-release-notes.md).
|
||||
For information on all released Microsoft Connected Cache updates, see the [MCC release notes](mcc-ent-release-notes.md).
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Verify MCCE cache node functionality
|
||||
description: Details on how to verify functionality of Microsoft Connected Cache for Enterprise and Education (MCCE) cache nodes.
|
||||
title: Verify MCC cache node functionality
|
||||
description: Details on how to verify functionality of Microsoft Connected Cache for Enterprise and Education (MCC) cache nodes.
|
||||
author: chrisjlin
|
||||
ms.author: lichris
|
||||
manager: naengler
|
||||
@ -9,8 +9,8 @@ ms.subservice: itpro-updates
|
||||
ms.topic: how-to
|
||||
ms.date: 09/27/2024
|
||||
appliesto:
|
||||
- ✅ Windows-hosted MCCE cache nodes
|
||||
- ✅ Linux-hosted MCCE cache nodes
|
||||
- ✅ Windows-hosted MCC cache nodes
|
||||
- ✅ Linux-hosted MCC cache nodes
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>
|
||||
---
|
||||
|
||||
@ -18,9 +18,9 @@ appliesto:
|
||||
|
||||
This article describes how to verify that a Microsoft Connected Cache for Enterprise and Education (MCC) cache node is functioning correctly.
|
||||
|
||||
These steps should be taken after deploying MCCE caching software to a [Windows](mcc-ent-deploy-to-windows.md) or [Linux](mcc-ent-deploy-to-linux.md) host machine.
|
||||
These steps should be taken after deploying MCC caching software to a [Windows](mcc-ent-deploy-to-windows.md) or [Linux](mcc-ent-deploy-to-linux.md) host machine.
|
||||
|
||||
## Steps to verify functionality of MCCE cache node
|
||||
## Steps to verify functionality of MCC cache node
|
||||
|
||||
1. To verify that the MCC container on the host machine is running and reachable, run the following command from the host machine:
|
||||
|
||||
@ -34,7 +34,7 @@ These steps should be taken after deploying MCCE caching software to a [Windows]
|
||||
|
||||
`http://[HostMachine-IP-address]/filestreamingservice/files/7bc846e0-af9c-49be-a03d-bb04428c9bb5/Microsoft.png?cacheHostOrigin=dl.delivery.mp.microsoft.com`
|
||||
|
||||
If successful, the Windows client device should begin to download a small image file from the MCCE cache node.
|
||||
If successful, the Windows client device should begin to download a small image file from the MCC cache node.
|
||||
|
||||
1. To check how much content an individual Windows client has pulled from an MCC cache node, open the [Delivery Optimization activity monitor](/microsoft-365-apps/updates/delivery-optimization#viewing-data-about-the-use-of-delivery-optimization) on the Windows client device.
|
||||
|
||||
|
||||
@ -66,8 +66,8 @@ These variables can be used within sections in the **.xml** files with `context=
|
||||
|*CSIDL_DEFAULT_TEMPLATES*|Refers to the Templates folder inside `%DEFAULTUSERPROFILE%`.|
|
||||
|*CSIDL_DEFAULT_QUICKLAUNCH*|Refers to the Quick Launch folder inside `%DEFAULTUSERPROFILE%`.|
|
||||
|*CSIDL_FONTS*|A virtual folder containing fonts. A typical path is `C:\Windows\Fonts`.|
|
||||
|*CSIDL_PROGRAM_FILESX86*|The Program Files folder on 64-bit systems. A typical path is `C:\Program Files(86)`.|
|
||||
|*CSIDL_PROGRAM_FILES_COMMONX86*|A folder for components that are shared across applications on 64-bit systems. A typical path is `C:\Program Files(86)\Common`.|
|
||||
|*CSIDL_PROGRAM_FILESX86*|The Program Files folder on 64-bit systems. A typical path is `C:\Program Files (x86)`.|
|
||||
|*CSIDL_PROGRAM_FILES_COMMONX86*|A folder for components that are shared across applications on 64-bit systems. A typical path is `C:\Program Files (x86)\Common`.|
|
||||
|*CSIDL_PROGRAM_FILES*|The Program Files folder. A typical path is `C:\Program Files`.|
|
||||
|*CSIDL_PROGRAM_FILES_COMMON*|A folder for components that are shared across applications. A typical path is `C:\Program Files\Common`.|
|
||||
|*CSIDL_RESOURCES*|The file-system directory that contains resource data. A typical path is `C:\Windows\Resources`.|
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Windows quality update end user experience
|
||||
description: This article explains the Windows quality update end user experience
|
||||
ms.date: 09/16/2024
|
||||
ms.date: 10/07/2024
|
||||
ms.service: windows-client
|
||||
ms.subservice: autopatch
|
||||
ms.topic: conceptual
|
||||
@ -32,9 +32,7 @@ In this section we review what an end user would see in the following three scen
|
||||
|
||||
### Typical update experience
|
||||
|
||||
The Windows quality update is published and devices in the Broad ring have a deferral period of nine days. Devices wait nine days before downloading the latest quality update.
|
||||
|
||||
In the following example, the user:
|
||||
In the following example, the Windows quality update is published and devices in the Broad ring have a deferral period of seven days. Devices wait seven days before downloading the latest quality update.
|
||||
|
||||
| Day | Description |
|
||||
| --- | --- |
|
||||
@ -46,7 +44,7 @@ In the following example, the user:
|
||||
|
||||
### Quality update deadline forces an update
|
||||
|
||||
In the following example, the user:
|
||||
In the following example:
|
||||
|
||||
| Day | Description |
|
||||
| --- | --- |
|
||||
@ -58,7 +56,7 @@ In the following example, the user:
|
||||
|
||||
### Quality update grace period
|
||||
|
||||
In the following example, the user:
|
||||
In the following example:
|
||||
|
||||
| Day | Description |
|
||||
| --- | --- |
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: What's new 2023
|
||||
description: This article lists the 2023 feature releases and any corresponding Message center post numbers.
|
||||
ms.date: 12/14/2023
|
||||
ms.date: 10/07/2024
|
||||
ms.service: windows-client
|
||||
ms.subservice: autopatch
|
||||
ms.topic: whats-new
|
||||
|
||||
Reference in New Issue
Block a user