deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-13 13:57:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Merge pull request #10285 from chrisjlin/edit-release-mcc-ent

Browse Source 
Changes to Deploy and CLI pages
This commit is contained in:
Gary Moore 2024-10-07 15:46:02 -07:00 committed by GitHub
commit f98757a440
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
18 changed files with 227 additions and 528 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
.openpublishing.redirection.windows-deployment.json
View File

@ -125,6 +125,21 @@
"redirect_url": "/windows/deployment/do/waas-microsoft-connected-cache", "redirect_url": "/windows/deployment/do/waas-microsoft-connected-cache",
"redirect_document_id": false "redirect_document_id": false
}, },
{
"source_path": "windows/deployment/do/mcc-ent-configure-provision-linux.md",
"redirect_url": "/windows/deployment/do/mcc-ent-deploy-to-linux",
"redirect_document_id": false
},
{
"source_path": "windows/deployment/do/mcc-ent-configure-provision-windows.md",
"redirect_url": "/windows/deployment/do/mcc-ent-deploy-to-windows",
"redirect_document_id": false
},
{
"source_path": "windows/deployment/do/mcc-ent-update-cache.md",
"redirect_url": "/windows/deployment/do/mcc-ent-uninstall-cache-node",
"redirect_document_id": false
},
{ {
"source_path": "windows/deployment/planning/act-technical-reference.md", "source_path": "windows/deployment/planning/act-technical-reference.md",
"redirect_url": "/previous-versions/windows/it-pro/windows-10/deployment/compatibility/compatibility-administrator-users-guide", "redirect_url": "/previous-versions/windows/it-pro/windows-10/deployment/compatibility/compatibility-administrator-users-guide",

149
windows/deployment/do/mcc-ent-configure-provision-linux.md
View File

@ -1,149 +0,0 @@
---
title: MCC for Enterprise provision Linux cache node
description: Microsoft Connected Cache for Enterprise. Learn about how to provision Linux cache node.
ms.service: windows-client
ms.subservice: itpro-updates
ms.topic: how-to
manager: aaroncz
ms.author: nidos
author: doshnid
ms.reviewer: mstewart
ms.collection: tier3
appliesto:
- ✅ <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>
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise</a>
ms.date: 06/03/2024
---
<!--
Remove all the comments in this template before you sign-off or merge to the main branch.
This template provides the basic structure of a How-to article pattern. See the
[instructions - How-to](../level4/article-how-to-guide.md) in the pattern library.
You can provide feedback about this template at: https://aka.ms/patterns-feedback
How-to is a procedure-based article pattern that show the user how to complete a task in their own environment. A task is a work activity that has a definite beginning and ending, is observable, consist of two or more definite steps, and leads to a product, service, or decision.
-->
<!-- 1. H1 -----------------------------------------------------------------------------
Required: Use a "<verb> * <noun>" format for your H1. Pick an H1 that clearly conveys the task the user will complete.
For example: "Migrate data from regular tables to ledger tables" or "Create a new Azure SQL Database".
* Include only a single H1 in the article.
* Don't start with a gerund.
* Don't include "Tutorial" in the H1.
-->
# "<verb> * <noun>"
TODO: Add your heading
<!-- 2. Introductory paragraph ----------------------------------------------------------
Required: Lead with a light intro that describes, in customer-friendly language, what the customer will do. Answer the fundamental “why would I want to do this?” question. Keep it short.
Readers should have a clear idea of what they will do in this article after reading the introduction.
* Introduction immediately follows the H1 text.
* Introduction section should be between 1-3 paragraphs.
* Don't use a bulleted list of article H2 sections.
Example: In this article, you will migrate your user databases from IBM Db2 to SQL Server by using SQL Server Migration Assistant (SSMA) for Db2.
-->
TODO: Add your introductory paragraph
<!---Avoid notes, tips, and important boxes. Readers tend to skip over them. Better to put that info directly into the article text.
-->
<!-- 3. Prerequisites --------------------------------------------------------------------
Required: Make Prerequisites the first H2 after the H1.
* Provide a bulleted list of items that the user needs.
* Omit any preliminary text to the list.
* If there aren't any prerequisites, list "None" in plain text, not as a bulleted item.
-->
## Prerequisites
TODO: List the prerequisites
<!-- 4. Task H2s ------------------------------------------------------------------------------
Required: Multiple procedures should be organized in H2 level sections. A section contains a major grouping of steps that help users complete a task. Each section is represented as an H2 in the article.
For portal-based procedures, minimize bullets and numbering.
* Each H2 should be a major step in the task.
* Phrase each H2 title as "<verb> * <noun>" to describe what they'll do in the step.
* Don't start with a gerund.
* Don't number the H2s.
* Begin each H2 with a brief explanation for context.
* Provide a ordered list of procedural steps.
* Provide a code block, diagram, or screenshot if appropriate
* An image, code block, or other graphical element comes after numbered step it illustrates.
* If necessary, optional groups of steps can be added into a section.
* If necessary, alternative groups of steps can be added into a section.
-->
## "\<verb\> * \<noun\>"
TODO: Add introduction sentence(s)
[Include a sentence or two to explain only what is needed to complete the procedure.]
TODO: Add ordered list of procedure steps
1. Step 1
1. Step 2
1. Step 3
## "\<verb\> * \<noun\>"
TODO: Add introduction sentence(s)
[Include a sentence or two to explain only what is needed to complete the procedure.]
TODO: Add ordered list of procedure steps
1. Step 1
1. Step 2
1. Step 3
## "\<verb\> * \<noun\>"
TODO: Add introduction sentence(s)
[Include a sentence or two to explain only what is needed to complete the procedure.]
TODO: Add ordered list of procedure steps
1. Step 1
1. Step 2
1. Step 3
<!-- 5. Next step/Related content------------------------------------------------------------------------
Optional: You have two options for manually curated links in this pattern: Next step and Related content. You don't have to use either, but don't use both.
- For Next step, provide one link to the next step in a sequence. Use the blue box format
- For Related content provide 1-3 links. Include some context so the customer can determine why they would click the link. Add a context sentence for the following links.
-->
## Next step
TODO: Add your next step link(s)
> [!div class="nextstepaction"]
> [Write concepts](article-concept.md)
<!-- OR -->
## Related content
TODO: Add your next step link(s)
- [Write concepts](article-concept.md)
<!--
Remove all the comments in this template before you sign-off or merge to the main branch.
-->

149
windows/deployment/do/mcc-ent-configure-provision-windows.md
View File

@ -1,149 +0,0 @@
---
title: MCC for Enterprise provision Windows cache node
description: Microsoft Connected Cache for Enterprise. Learn about how to provision Windows cache node.
ms.service: windows-client
ms.subservice: itpro-updates
ms.topic: how-to
manager: aaroncz
ms.author: nidos
author: doshnid
ms.reviewer: mstewart
ms.collection: tier3
appliesto:
- ✅ <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>
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise</a>
ms.date: 06/03/2024
---
<!--
Remove all the comments in this template before you sign-off or merge to the main branch.
This template provides the basic structure of a How-to article pattern. See the
[instructions - How-to](../level4/article-how-to-guide.md) in the pattern library.
You can provide feedback about this template at: https://aka.ms/patterns-feedback
How-to is a procedure-based article pattern that show the user how to complete a task in their own environment. A task is a work activity that has a definite beginning and ending, is observable, consist of two or more definite steps, and leads to a product, service, or decision.
-->
<!-- 1. H1 -----------------------------------------------------------------------------
Required: Use a "<verb> * <noun>" format for your H1. Pick an H1 that clearly conveys the task the user will complete.
For example: "Migrate data from regular tables to ledger tables" or "Create a new Azure SQL Database".
* Include only a single H1 in the article.
* Don't start with a gerund.
* Don't include "Tutorial" in the H1.
-->
# "<verb> * <noun>"
TODO: Add your heading
<!-- 2. Introductory paragraph ----------------------------------------------------------
Required: Lead with a light intro that describes, in customer-friendly language, what the customer will do. Answer the fundamental “why would I want to do this?” question. Keep it short.
Readers should have a clear idea of what they will do in this article after reading the introduction.
* Introduction immediately follows the H1 text.
* Introduction section should be between 1-3 paragraphs.
* Don't use a bulleted list of article H2 sections.
Example: In this article, you will migrate your user databases from IBM Db2 to SQL Server by using SQL Server Migration Assistant (SSMA) for Db2.
-->
TODO: Add your introductory paragraph
<!---Avoid notes, tips, and important boxes. Readers tend to skip over them. Better to put that info directly into the article text.
-->
<!-- 3. Prerequisites --------------------------------------------------------------------
Required: Make Prerequisites the first H2 after the H1.
* Provide a bulleted list of items that the user needs.
* Omit any preliminary text to the list.
* If there aren't any prerequisites, list "None" in plain text, not as a bulleted item.
-->
## Prerequisites
TODO: List the prerequisites
<!-- 4. Task H2s ------------------------------------------------------------------------------
Required: Multiple procedures should be organized in H2 level sections. A section contains a major grouping of steps that help users complete a task. Each section is represented as an H2 in the article.
For portal-based procedures, minimize bullets and numbering.
* Each H2 should be a major step in the task.
* Phrase each H2 title as "<verb> * <noun>" to describe what they'll do in the step.
* Don't start with a gerund.
* Don't number the H2s.
* Begin each H2 with a brief explanation for context.
* Provide a ordered list of procedural steps.
* Provide a code block, diagram, or screenshot if appropriate
* An image, code block, or other graphical element comes after numbered step it illustrates.
* If necessary, optional groups of steps can be added into a section.
* If necessary, alternative groups of steps can be added into a section.
-->
## "\<verb\> * \<noun\>"
TODO: Add introduction sentence(s)
[Include a sentence or two to explain only what is needed to complete the procedure.]
TODO: Add ordered list of procedure steps
1. Step 1
1. Step 2
1. Step 3
## "\<verb\> * \<noun\>"
TODO: Add introduction sentence(s)
[Include a sentence or two to explain only what is needed to complete the procedure.]
TODO: Add ordered list of procedure steps
1. Step 1
1. Step 2
1. Step 3
## "\<verb\> * \<noun\>"
TODO: Add introduction sentence(s)
[Include a sentence or two to explain only what is needed to complete the procedure.]
TODO: Add ordered list of procedure steps
1. Step 1
1. Step 2
1. Step 3
<!-- 5. Next step/Related content------------------------------------------------------------------------
Optional: You have two options for manually curated links in this pattern: Next step and Related content. You don't have to use either, but don't use both.
- For Next step, provide one link to the next step in a sequence. Use the blue box format
- For Related content provide 1-3 links. Include some context so the customer can determine why they would click the link. Add a context sentence for the following links.
-->
## Next step
TODO: Add your next step link(s)
> [!div class="nextstepaction"]
> [Write concepts](article-concept.md)
<!-- OR -->
## Related content
TODO: Add your next step link(s)
- [Write concepts](article-concept.md)
<!--
Remove all the comments in this template before you sign-off or merge to the main branch.
-->

34
windows/deployment/do/mcc-ent-create-resource-and-cache.md
View File

@ -1,6 +1,6 @@
--- ---
title: Create and configure 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 (MCCE) 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.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: how-to ms.topic: how-to
@ -14,16 +14,16 @@ appliesto:
ms.date: 06/03/2024 ms.date: 06/03/2024
--- ---
# Create MCCE Azure resource and cache nodes # Create Microsoft Connected Cache Azure resource and cache nodes
This article outlines how to create and configure your Microsoft Connected Cache for Enterprise and Education (MCCE) 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. 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 ## 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/). 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. 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 MCCE](mcc-ent-prerequisites.md). For more information on sizing and OS requirements, see [the prerequisites for using MCC](mcc-ent-prerequisites.md).
## Create MCCE Azure resource ## Create MCC Azure resource
# [Azure portal](#tab/portal) # [Azure portal](#tab/portal)
@ -59,7 +59,7 @@ For more information on sizing and OS requirements, see [the prerequisites for u
* Resource group under which an MCC resource can be created. Use the [az group create](/cli/azure/group#az-group-create) command to create a new Resource group if you don't already have one. * Resource group under which an MCC resource can be created. Use the [az group create](/cli/azure/group#az-group-create) command to create a new Resource group if you don't already have one.
#### Create MCCE Azure resource #### Create MCC Azure resource
Replace the following placeholders with your own information: Replace the following placeholders with your own information:
* *\<resource-group>*: An existing resource group in your subscription. * *\<resource-group>*: An existing resource group in your subscription.
* *\<mcc-resource-name>*: A name for your Microsoft Connected Cache for Enterprise resource. * *\<mcc-resource-name>*: A name for your Microsoft Connected Cache for Enterprise resource.
@ -71,7 +71,7 @@ az mcc ent resource create --mcc-resource-name <mymccresource> --resource-group
--- ---
## Create MCCE cache node ## Create MCC cache node
# [Azure portal](#tab/portal) # [Azure portal](#tab/portal)
@ -121,7 +121,7 @@ az mcc ent node create --cache-node-name <mycachenode> --mcc-resource-name <mymc
--- ---
## Configure MCCE cache node ## Configure MCC cache node
# [Azure portal](#tab/portal) # [Azure portal](#tab/portal)
Enter required values to configure your cache node. To learn more about the definitions of each field, review the Configuration fields at the bottom of this article. Enter required values to configure your cache node. To learn more about the definitions of each field, review the Configuration fields at the bottom of this article.
@ -140,9 +140,9 @@ Replace the following placeholders with your own information:
* *\<size-in-gb>*: The size of cache drive. Must be at least 50 Gb. * *\<size-in-gb>*: The size of cache drive. Must be at least 50 Gb.
* *\<proxy>*: If proxy needs to be enabled or not.<br> * *\<proxy>*: If proxy needs to be enabled or not.<br>
Accepted values: enabled, disabled Accepted values: enabled, disabled
If proxy is set to enabled, you must provide proxy host and proxy port information 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 * *\<proxy-host>*: The proxy host name or ip address. Required if proxy is set to enabled.
* *\<proxy-port>*: Proxy port * *\<proxy-port>*: Proxy port number. Required if proxy is set to enabled.
* *\<auto-update-ring>*: Update ring the cache node should have.<br> * *\<auto-update-ring>*: Update ring the cache node should have.<br>
Accepted values: slow, fast. Accepted values: slow, fast.
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. 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.
@ -171,9 +171,9 @@ Replace the following placeholders with your own information:
* *\<size-in-gb>*: The size of cache drive. Must be at least 50 Gb. * *\<size-in-gb>*: The size of cache drive. Must be at least 50 Gb.
* *\<proxy>*: If proxy needs to be enabled or not.<br> * *\<proxy>*: If proxy needs to be enabled or not.<br>
Accepted values: enabled, disabled Accepted values: enabled, disabled
If proxy is set to enabled, you must provide proxy host and proxy port information 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 * *\<proxy-host>*: The proxy host name or ip address. Required if proxy is set to enabled.
* *\<proxy-port>*: Proxy port * *\<proxy-port>*: Proxy port number. Required if proxy is set to enabled.
* *\<auto-update-ring>*: Update ring the cache node should have.<br> * *\<auto-update-ring>*: Update ring the cache node should have.<br>
Accepted values: slow, fast. Accepted values: slow, fast.
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. 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.
@ -234,12 +234,12 @@ To deploy cache nodes using Azure CLI, see [Bulk management of cache nodes](mcc-
#### Proxy settings #### Proxy settings
<br> <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> <br>
>[!IMPORTANT] >[!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| | Field Name |Expected Value |Description|
|---|---|---| |---|---|---|

36
windows/deployment/do/mcc-ent-deploy-to-linux.md
View File

@ -1,6 +1,6 @@
--- ---
title: Deploy 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 (MCCE) 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 author: chrisjlin
ms.author: lichris ms.author: lichris
manager: naengler 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> - ✅ <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. 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. 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. 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. 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 ## Next step
> [!div class="nextstepaction"] > [!div class="nextstepaction"]
@ -35,4 +57,4 @@ Before deploying MCCE to a Linux host machine, ensure that the host machine meet
## Related content ## Related content
- [Deploy to a Windows host machine](mcc-ent-deploy-to-windows.md) - [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)

50
windows/deployment/do/mcc-ent-deploy-to-windows.md
View File

@ -1,6 +1,6 @@
--- ---
title: Deploy 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 (MCCE) 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 author: chrisjlin
ms.author: lichris ms.author: lichris
manager: naengler 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> - ✅ <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. 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. 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. 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"`. 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. 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 ## Next step
> [!div class="nextstepaction"] > [!div class="nextstepaction"]
> [Verify cache node functionality](mcc-ent-verify-cache-node.md) > [Verify cache node functionality](mcc-ent-verify-cache-node.md)
<!-- OR -->
## Related content ## Related content
- [Deploy to a Linux host machine](mcc-ent-deploy-to-linux.md) - [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)

4
windows/deployment/do/mcc-ent-edu-overview.md
View File

@ -1,6 +1,6 @@
--- ---
title: MCCE Overview title: MCC Overview
description: Overview, supported scenarios, and content types for Microsoft Connected Cache for Enterprise and Education (MCCE). description: Overview, supported scenarios, and content types for Microsoft Connected Cache for Enterprise and Education (MCC).
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: conceptual ms.topic: conceptual

6
windows/deployment/do/mcc-ent-faq.yml
View File

@ -1,7 +1,7 @@
### YamlMime:FAQ ### YamlMime:FAQ
metadata: metadata:
title: MCCE Frequently Asked Questions title: MCC Frequently Asked Questions
description: The following article is a list of frequently asked questions for Microsoft Connected Cache for Enterprise (MCCE). description: The following article is a list of frequently asked questions for Microsoft Connected Cache for Enterprise (MCC).
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: faq 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 11</a>
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a> - ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
ms.date: 06/03/2024 ms.date: 06/03/2024
title: Microsoft Connected Cache for Enteprise Frequently Asked Questions title: Microsoft Connected Cache for Enterprise Frequently Asked Questions
summary: | summary: |
Frequently asked questions about Microsoft Connected Cache for Enterprise Frequently asked questions about Microsoft Connected Cache for Enterprise

132
windows/deployment/do/mcc-ent-manage-cache-using-CLI.md
View File

@ -1,6 +1,6 @@
--- ---
title: Manage MCCE cache nodes using CLI title: Manage MCC cache nodes using CLI
description: Details on how to manage Microsoft Connected Cache for Enterprise (MCCE) cache nodes via Azure CLI commands. description: Details on how to manage Microsoft Connected Cache for Enterprise (MCC) cache nodes via Azure CLI commands.
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: how-to ms.topic: how-to
@ -20,7 +20,7 @@ ms.date: 06/03/2024
<br> <br>
This article outlines how to create, configure, and deploy Microsoft Connected Cache for Enterprise (MCCE) cache nodes using Azure CLI. This article outlines how to create, configure, and deploy Microsoft Connected Cache for Enterprise (MCC) cache nodes using Azure CLI.
## Prerequisites: ## Prerequisites:
@ -44,10 +44,10 @@ 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. Once the resource group is created, you'll need to create a Microsoft Connected Cache for Enterprise resource.
### 2. Create an MCCE Azure resource ### 2. Create an MCC Azure resource
An MCCE Azure resource is a top-level Azure resource under which cache nodes can be created. An MCC Azure resource is a top-level Azure resource under which cache nodes can be created.
To create an MCCE Azure resource, use `az mcc ent resource create` To create an MCC Azure resource, use `az mcc ent resource create`
```azurecli-interactive ```azurecli-interactive
az mcc ent resource create --mcc-resource-name mymccresource --resource-group myrg az mcc ent resource create --mcc-resource-name mymccresource --resource-group myrg
@ -136,79 +136,65 @@ 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. Save the resulting values for cacheNodeId, customerKey, mccResourceId, registrationKey. These GUIDs are needed to create the provisioning script.
### 7. Deploy cache node ### Example script:
<br> Below is a pseudocode example of how to script bulk creation and configuration of an MCC Azure resource and multiple MCC cache nodes.
#### Deploy cache node to Linux host machine <!--# [Bash](#tab/bash)
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)
Use the following link to download and extract the Linux-compatible MCCE provisioning package onto the host machine. :::code language="azurecli" source="~/azure_cli_scripts/azure-cli/create-azure-resources-at-scale/bash/create-azure-resources-at-scale.sh" id="step4":::
[Download MCCE provisioning package for Linux host machine](https://aka.ms/MCC-Ent-InstallScript-Linux) 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.
<br> # [PowerShell](#tab/powershell)
>[!IMPORTANT] :::code language="azurecli" source="~/azure_cli_scripts/azure-cli/create-azure-resources-at-scale/powershell/create-azure-resources-at-scale.ps1" id="step4":::
>Before you execute the provisioning command, make sure you change directory to the extracted provisioning package and set the script execution permissions by running the command below.
```azurepowershell-interactive -->
sudo chmod +x provisionmcc.sh
# [PowerShell](#tab/powershell)
```powershell
#Define variables
$mccResourceName = "myMCCResource"
$cacheNodeName = "demo-node"
$cacheNodeOperatingSystem = "Windows"
$resourceGroup = "myRG"
$resourceLocation = "westus"
$cacheNodesToCreate = 2
$proxyHost = "myProxy.com"
$proxyPort = "8080"
$waitTime = 3
#Create MCC Az resource
az mcc ent resource create --mcc-resource-name $mccResourceName --location $resourceLocation --resource-group $resourceGroup
#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
#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
}
``` ```
Replace the values in the following provisioning command before running it.<br>
```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="true" proxyurl=http://enter proxy hostname:enter port
```
<br>
>[!IMPORTANT]
>'shoulduseproxy' parameter is required, whether or not your network uses proxy to access internet.
#### Deploy cache node to Windows host machine
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)
Use the following link to download and extract the Windows-compatible MCCE provisioning package onto the host machine.
[Download MCCE provisioning package for Windows host machine](https://aka.ms/MCC-Ent-InstallScript-WSL)
<br>
>[!IMPORTANT]
>Before you execute the provisioning command, make sure you change directory to the extracted provisioning package and set the script execution permissions by running the command below.
```azurepowershell-interactive
Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process
```
If you're using a **Group Managed Service Account**, replace the values in the following provisioning command before running it.<br>
```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 $true -proxyurl " http://enter proxy host name:enter port" -mccRunTimeAccount $User
```
<br>
>[!IMPORTANT]
>'shoulduseproxy' parameter is required, whether or not your network uses proxy to access internet.
If you're using **Local User account** or **Domain User account**, replace the values in the following provisioning command before running it.<br>
```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 $true -proxyurl " http://enter proxy host name:enter port" -mccRunTimeAccount $User -mccLocalAccountCredential $myLocalAccountCredential
```
<br>
>[!IMPORTANT]
>'shoulduseproxy' parameter is required, whether or not your network uses proxy to access internet.
## Next step ## Next step
To verify cache node functionality, see [Verify cache node functionality](mcc-ent-verify-cache-node.md) > [!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)
<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.

12
windows/deployment/do/mcc-ent-monitoring.md
View File

@ -1,6 +1,6 @@
--- ---
title: Monitor usage of MCCE cache nodes title: Monitor usage of MCC cache nodes
description: Details on how to monitor the usage of Microsoft Connected Cache for Enterprise (MCCE) cache nodes. description: Details on how to monitor the usage of Microsoft Connected Cache for Enterprise (MCC) cache nodes.
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: how-to ms.topic: how-to
@ -14,9 +14,9 @@ appliesto:
ms.date: 09/04/2024 ms.date: 09/04/2024
--- ---
# Monitor MCCE cache node usage # Monitor Microsoft Connected Cache cache node usage
Tracking the status and performance of your MCCE cache node is essential to making sure that you're getting the most out of the service. 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.
<!-- Add standard metrics <!-- Add standard metrics
@ -28,7 +28,7 @@ The Cache Node Summary box on your Azure portal
| Metric | Description | | Metric | Description |
| --- | --- | | --- | --- |
| Healthy nodes | The MCCE service will periodically request heartbeat messages from your MCC node to determine if it's functioning as expected. | | Healthy nodes | The MCC service will periodically request heartbeat messages from your MCC node to determine if it's functioning as expected. |
| Unhealthy nodes | If the cache node doesn't respond, it is labeled as unhealthy. | | Unhealthy nodes | If the cache node doesn't respond, it is labeled as unhealthy. |
| Max in | The maximum egress (in Mb/sec.) that your node has pulled in at any given time. This statistic isn't dependent on the time filter near the charts. | | Max in | The maximum egress (in Mb/sec.) that your node has pulled in at any given time. This statistic isn't dependent on the time filter near the charts. |
| Max out | The minimum egress (in Mb/sec.) that your node has pushed out at any given time. | | Max out | The minimum egress (in Mb/sec.) that your node has pushed out at any given time. |
@ -49,7 +49,7 @@ The Cache Node Summary box on your Azure portal
### Volume by Content Type ### Volume by Content Type
- The volume of content that your MCCE cache node is distributing, broken down by the hostname used to download said content - The volume of content that your MCC cache node is distributing, broken down by the hostname used to download said content
## Additional metrics ## Additional metrics

12
windows/deployment/do/mcc-ent-prerequisites.md
View File

@ -1,6 +1,6 @@
--- ---
title: MCCE prerequisites title: MCC prerequisites
description: Details of prerequisites and recommendations for using Microsoft Connected Cache for Enterprise and Education (MCCE). description: Details of prerequisites and recommendations for using Microsoft Connected Cache for Enterprise and Education (MCC).
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: conceptual ms.topic: conceptual
@ -15,17 +15,17 @@ ms.date: 09/27/2024
# Microsoft Connected Cache for Enterprise and Education Requirements (Public Preview) # Microsoft Connected Cache for Enterprise and Education Requirements (Public Preview)
This article details the requirements and recommendations for using Microsoft Connected Cache for Enterprise and Education (MCCE). This article details the requirements and recommendations for using Microsoft Connected Cache for Enterprise and Education (MCC).
## Licensing requirements ## Licensing requirements
- **Valid Azure subscription**: To use the Microsoft Connected Cache for Enterprise and Education (MCCE) service, you'll need a valid Azure subscription that can be used to provision the necessary [Azure resources](/azure/cloud-adoption-framework/govern/resource-consistency/resource-access-management). - **Valid Azure subscription**: To use the Microsoft Connected Cache for Enterprise and Education (MCC) service, you'll need a valid Azure subscription that can be used to provision the necessary [Azure resources](/azure/cloud-adoption-framework/govern/resource-consistency/resource-access-management).
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/). 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 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) - Windows Education A3 or A5, included in [Microsoft 365 A3 or A5](https://www.microsoft.com/education/products/microsoft-365?msockid=32c407b43d5968050f2b13443c746916#Education-plans)

14
windows/deployment/do/mcc-ent-private-preview.md
View File

@ -1,6 +1,6 @@
--- ---
title: MCCE Private Preview title: MCC Private Preview
description: Details on Microsoft Connected Cache for Enterprise (MCCE) Private Preview description: Details on Microsoft Connected Cache for Enterprise (MCC) Private Preview
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: conceptual ms.topic: conceptual
@ -12,15 +12,15 @@ appliesto:
ms.date: 06/03/2024 ms.date: 06/03/2024
--- ---
# Microsoft Connected Cache for Enterprise and Education (MCCE) Private 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 MCCE, 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 MCCE 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 ## Next step
> [!div class="nextstepaction"] > [!div class="nextstepaction"]
> [View documentation for MCCE Public Preview](mcc-ent-edu-overview.md) > [View documentation for MCC Public Preview](mcc-ent-edu-overview.md)

12
windows/deployment/do/mcc-ent-release-notes.md
View File

@ -1,6 +1,6 @@
--- ---
title: MCCE Release Notes title: MCC Release Notes
description: Release Notes for Microsoft Connected Cache for Enterprise and Education (MCCE). description: Release Notes for Microsoft Connected Cache for Enterprise and Education (MCC).
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: conceptual ms.topic: conceptual
@ -14,9 +14,9 @@ appliesto:
ms.date: 09/27/2024 ms.date: 09/27/2024
--- ---
# Release Notes for Microsoft Connected Cache for Enterprise and Education (MCCE) # Release Notes for Microsoft Connected Cache for Enterprise and Education (MCC)
This article contains details about the latest releases of MCCE. Since MCCE is a Preview service, some releases may contain breaking changes that will be highlighted as such. This article contains details about the latest releases of MCC. Since MCC is a Preview service, some releases may contain breaking changes that will be highlighted as such.
## Release v0.1.0 (Public Preview launch) ## Release v0.1.0 (Public Preview launch)
@ -33,8 +33,8 @@ This article contains details about the latest releases of MCCE. Since MCCE is a
- Added support for creating both Windows-hosted and Linux-hosted cache nodes under the same MCC Azure resource - 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 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 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 ## Related content
- [Overview of MCCE](mcc-ent-edu-overview.md) - [Overview of MCC](mcc-ent-edu-overview.md)

8
windows/deployment/do/mcc-ent-support-and-troubleshooting.md
View File

@ -1,6 +1,6 @@
--- ---
title: MCCE support and troubleshooting title: MCC support and troubleshooting
description: Details on how to troubleshoot and seek support for Microsoft Connected Cache for Enterprise (MCCE). description: Details on how to troubleshoot and seek support for Microsoft Connected Cache for Enterprise (MCC).
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: how-to ms.topic: how-to
@ -38,7 +38,7 @@ For example: "Migrate data from regular tables to ledger tables" or "Create a ne
--> -->
# Troubleshoot Microsoft Connected Cache for Enterprise and Education (MCCE) # Troubleshoot Microsoft Connected Cache for Enterprise and Education (MCC)
<!-- 2. Introductory paragraph ---------------------------------------------------------- <!-- 2. Introductory paragraph ----------------------------------------------------------
@ -54,7 +54,7 @@ Example: In this article, you will migrate your user databases from IBM Db2 to S
--> -->
This article contains instructions on how to troubleshoot different issues you may encounter while using MCCE. 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). 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).
## Troubleshooting Azure resource creation ## Troubleshooting Azure resource creation

14
windows/deployment/do/mcc-ent-uninstall-cache-node.md
View File

@ -1,6 +1,6 @@
--- ---
title: Uninstall MCCE cache nodes title: Uninstall MCC cache nodes
description: Details on how to uninstall Microsoft Connected Cache for Enterprise and Education (MCCE) from a host machine. description: Details on how to uninstall Microsoft Connected Cache for Enterprise and Education (MCC) from a host machine.
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: how-to ms.topic: how-to
@ -14,18 +14,18 @@ appliesto:
ms.date: 09/27/2024 ms.date: 09/27/2024
--- ---
# Uninstall MCCE caching software from a host machine # Uninstall MCC caching software from a host machine
This article describes how to uninstall Microsoft Connected Cache for Enterprise and Education (MCCE) caching software from a host machine. These steps should be taken after deleting the cache node in the Azure portal. This article describes how to uninstall Microsoft Connected Cache for Enterprise and Education (MCC) caching software from a host machine. These steps should be taken after deleting the cache node in the Azure portal.
## Steps to uninstall MCCE from a Windows host machine ## Steps to uninstall MCC from a Windows host machine
1. Launch a PowerShell window *as administrator* and navigate to the MCC installation directory (C:\mcconwsl01 by default) 1. Launch a PowerShell window *as administrator* and navigate to the MCC installation directory (C:\mcconwsl01 by default)
1. Run the `uninstallmcconwsl.ps1` script 1. Run the `uninstallmcconwsl.ps1` script
## Steps to uninstall MCCE from a Linux host machine ## Steps to uninstall MCC from a Linux host machine
The `uninstallmcc.sh` script within the provisioning package uninstalls the MCCE caching software and all related components, including: The `uninstallmcc.sh` script within the provisioning package uninstalls the MCC caching software and all related components, including:
- IoT Edge - IoT Edge
- IoT Edge Agent - IoT Edge Agent

29
windows/deployment/do/mcc-ent-update-cache-node.md
View File

@ -1,6 +1,6 @@
--- ---
title: Update MCCE cache nodes title: Update MCC cache nodes
description: Details on how Microsoft Connected Cache for Enterprise and Education (MCCE) cache nodes are updated by Microsoft. description: Details on how Microsoft Connected Cache for Enterprise and Education (MCC) cache nodes are updated by Microsoft.
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: how-to 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> - ✅ <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 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 ## 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 ### 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 #### 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 #### 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 | | Setting | Description |
| --- | --- | | --- | --- |
@ -41,15 +44,15 @@ Configuring an MCCE cache node to update as part of the Slow ring provides users
## Update process ## 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 ## 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 | | 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 | | 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).

55
windows/deployment/do/mcc-ent-update-cache.md
View File

@ -1,55 +0,0 @@
---
title: Uninstall MCC for Enterprise and Education
description: Details on how to uninstall Microsoft Connected Cache (MCC) for Enterprise and Education for your environment.
ms.service: windows-client
ms.subservice: itpro-updates
ms.topic: how-to
ms.author: carmenf
author: cmknox
manager: aaroncz
ms.reviewer: mstewart
ms.collection:
- tier3
- must-keep
appliesto:
- ✅ <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>
- ✅ <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: 05/23/2024
---
<!-- Customers will no longer update the private preview and instead install public preview
# Update or uninstall Microsoft Connected Cache for Enterprise and Education
Throughout the preview phase, we'll send you security and feature updates for MCC. Follow these steps to perform the update.
## Update MCC
Run the following command with the **arguments** we provided in the email to update your MCC:
```powershell
# .\updatemcc.ps1 version="**\<VERSION\>**" tenantid="**\<TENANTID\>**" customerid="**\<CUSTOMERID\>**" cachenodeid="**\<CACHENODEID\>**" customerkey="**\<CUSTOMERKEY\>**"
```
For example:
```powershell
# .\updatemcc.ps1 version="msconnectedcacheprod.azurecr.io/mcc/linux/iot/mcc-ubuntu-iot-amd64:1.2.1.659" tenantid="799a999aa-99a1-99aa-99aa-9a9aa099db99" customerid="99a999aa-99a1-99aa-99aa-9aaa9aaa0saa" cachenodeid=" aa99aaaa-999a-9aas-99aa99daaa99 " customerkey="a99d999a-aaaa-aa99-0999aaaa99a"
```
-->
# Uninstall MCC
Contact the MCC Team before uninstalling to let us know if you're facing issues.
This script removes the following items:
1. EFLOW + Linux VM
1. IoT Edge
1. Edge Agent
1. Edge Hub
1. MCC
1. Moby CLI
1. Moby Engine
To delete MCC, go to Control Panel \> Uninstall a program \> Select Azure IoT
Edge LTS \> Uninstall

24
windows/deployment/do/mcc-ent-verify-cache-node.md
View File

@ -1,6 +1,6 @@
--- ---
title: Verify MCCE cache node functionality title: Verify MCC cache node functionality
description: Details on how to verify functionality of Microsoft Connected Cache for Enterprise and Education (MCCE) cache nodes. description: Details on how to verify functionality of Microsoft Connected Cache for Enterprise and Education (MCC) cache nodes.
author: chrisjlin author: chrisjlin
ms.author: lichris ms.author: lichris
manager: naengler manager: naengler
@ -9,20 +9,20 @@ ms.subservice: itpro-updates
ms.topic: how-to ms.topic: how-to
ms.date: 09/27/2024 ms.date: 09/27/2024
appliesto: appliesto:
- ✅ Windows-hosted MCCE cache nodes - ✅ Windows-hosted MCC cache nodes
- ✅ Linux-hosted MCCE 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> - ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>
--- ---
# Verify MCCE cache node functionality # Verify MCC cache node functionality
This article describes how to verify that a Microsoft Connected Cache for Enterprise and Education (MCCE) cache node is functioning correctly. 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 MCCE container on the host machine is running and reachable, run the following command from the host machine: 1. To verify that the MCC container on the host machine is running and reachable, run the following command from the host machine:
```powershell ```powershell
wget http://localhost/filestreamingservice/files/7bc846e0-af9c-49be-a03d-bb04428c9bb5/Microsoft.png?cacheHostOrigin=dl.delivery.mp.microsoft.com wget http://localhost/filestreamingservice/files/7bc846e0-af9c-49be-a03d-bb04428c9bb5/Microsoft.png?cacheHostOrigin=dl.delivery.mp.microsoft.com
@ -30,13 +30,13 @@ These steps should be taken after deploying MCCE caching software to a [Windows]
If successful, there should be an HTTP response with StatusCode 200. If successful, there should be an HTTP response with StatusCode 200.
1. To verify that Windows clients in your network can reach the MCCE cache node, visit the following address from a web browser on a Windows client device: 1. To verify that Windows clients in your network can reach the MCC cache node, visit the following address from a web browser on a Windows client device:
`http://[HostMachine-IP-address]/filestreamingservice/files/7bc846e0-af9c-49be-a03d-bb04428c9bb5/Microsoft.png?cacheHostOrigin=dl.delivery.mp.microsoft.com` `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 MCCE 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. 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.
You should see a donut chart titled Download Statistics. If the Windows client has pulled content from the cache node, you'll see a segment of the donut labeled "From Microsoft cache server". You should see a donut chart titled Download Statistics. If the Windows client has pulled content from the cache node, you'll see a segment of the donut labeled "From Microsoft cache server".