mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 18:33:43 +00:00
Merge branch 'release-mcc-ent' of https://github.com/MicrosoftDocs/windows-docs-pr into edit-release-mcc-ent
This commit is contained in:
chrisjlin
149
windows/deployment/do/mcc-ent-configure-provision-linux.md
Normal file
149
windows/deployment/do/mcc-ent-configure-provision-linux.md
Normal file
@ -0,0 +1,149 @@
|
||||
---
|
||||
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
Normal file
149
windows/deployment/do/mcc-ent-configure-provision-windows.md
Normal file
@ -0,0 +1,149 @@
|
||||
---
|
||||
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.
|
||||
-->
|
||||
|
||||
@ -17,7 +17,7 @@ appliesto:
|
||||
|
||||
This article describes how to deploy Microsoft Connected Cache for Enterprise and Education (MCCE) caching software to a Windows host machine.
|
||||
|
||||
Deploying MCCE to a Windows host machine requires designating a [Group Managed Service Account (gMSA)](https://learn.microsoft.com/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 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.
|
||||
|
||||
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).
|
||||
|
||||
@ -30,7 +30,7 @@ Before deploying MCCE to a Windows host machine, ensure that the host machine me
|
||||
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](https://learn.microsoft.com/dotnet/api/system.management.automation.pscredential?view=powershellsdk-7.4.0&preserve-view=true) named `$myLocalAccountCredential`.
|
||||
- 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`.
|
||||
1. Run the provisioning command on the host machine.
|
||||
|
||||
# [Azure CLI](#tab/cli)
|
||||
|
||||
149
windows/deployment/do/mcc-ent-monitor-cache.md
Normal file
149
windows/deployment/do/mcc-ent-monitor-cache.md
Normal file
@ -0,0 +1,149 @@
|
||||
---
|
||||
title: MCC for Enterprise monitor cache nodes
|
||||
description: Microsoft Connected Cache for Enterprise. Learn about how to monitor 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: 09/04/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.
|
||||
-->
|
||||
|
||||
@ -27,7 +27,7 @@ This article details the requirements and recommendations for using Microsoft Co
|
||||
|
||||
- **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.
|
||||
|
||||
- [Windows Enterprise E3 or E5](https://learn.microsoft.com/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)
|
||||
|
||||
## Cache node host machine requirements
|
||||
@ -45,7 +45,7 @@ This article details the requirements and recommendations for using Microsoft Co
|
||||
- Windows 11 must have [OS Build 22631.3296](https://support.microsoft.com/topic/march-12-2024-kb5035853-os-builds-22621-3296-and-22631-3296-a69ac07f-e893-4d16-bbe1-554b7d9dd39b) or later
|
||||
- Windows Server 2022 must have [OS Build 20348.2227](https://support.microsoft.com/topic/january-9-2024-kb5034129-os-build-20348-2227-6958a36f-efaf-4ef5-a576-c5931072a89a) or later
|
||||
- The Windows host machine must support nested virtualization.
|
||||
- The Windows host machine must have [WSL2 installed](https://learn.microsoft.com/windows/wsl/install#install-wsl-command).
|
||||
- The Windows host machine must have [WSL2 installed](/windows/wsl/install#install-wsl-command).
|
||||
|
||||
### Additional requirements for Linux host machines
|
||||
|
||||
|
||||
@ -23,4 +23,4 @@ As such, we strongly recommend you [recreate your existing cache nodes in Azure]
|
||||
## Next step
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [View documentation for MCCE Public Preview](mcc-ent-edu-overview.md)
|
||||
> [View documentation for MCCE Public Preview](mcc-ent-edu-overview.md)
|
||||
|
||||
55
windows/deployment/do/mcc-ent-update-cache.md
Normal file
55
windows/deployment/do/mcc-ent-update-cache.md
Normal file
@ -0,0 +1,55 @@
|
||||
---
|
||||
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
|
||||
@ -36,11 +36,11 @@ These steps should be taken after deploying MCCE caching software to a [Windows]
|
||||
|
||||
If successful, the Windows client device should begin to download a small image file from the MCCE 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](https://learn.microsoft.com/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 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.
|
||||
|
||||
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".
|
||||
|
||||
## Related content
|
||||
|
||||
- [Monitor cache node usage](mcc-ent-monitoring.md)
|
||||
- [Troubleshoot cache node](mcc-ent-support-and-troubleshooting.md)
|
||||
- [Troubleshoot cache node](mcc-ent-support-and-troubleshooting.md)
|
||||
|
||||
@ -13,7 +13,7 @@ appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/mem/configmgr/ > Microsoft Configuration Manager</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows-server/administration/windows-server-update-services/get-started/windows-server-update-services-wsus > WSUS </a>
|
||||
ms.date: 04/22/2024
|
||||
ms.date: 10/01/2024
|
||||
---
|
||||
|
||||
# How to make Features on Demand and language packs available when you're using WSUS or Configuration Manager
|
||||
@ -31,11 +31,13 @@ Due to these changes, the **Specify settings for optional component installation
|
||||
|
||||
The introduction of the **Specify source service for specific classes of Windows Updates** ([SetPolicyDrivenUpdateSourceFor<UpdateClass\>](/windows/client-management/mdm/policy-csp-update#setpolicydrivenupdatesourceforfeatureupdates)) policy in Windows 10, version 2004 further complicated configuring settings for FoD and language pack content.
|
||||
|
||||
Starting in Windows 11, version 22H2, on-premises Unified Update Platform (UUP) updates were introduced. FoDs and language packs are available from WSUS again. It's no longer necessary to use the **Specify settings for optional component installation and component repair** policy for FoD and language pack content.
|
||||
Starting in Windows 11, version 22H2, on-premises Unified Update Platform (UUP) updates were introduced. FoDs and language packs are available from WSUS again. It's no longer necessary to use the **Specify settings for optional component installation and component repair** policy for FoD and language pack content. This policy was modified starting in Windows 11, version 24H2 and the following options were removed:<!--8914508-->
|
||||
- Never attempt to download payload from Windows Update
|
||||
- Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS)
|
||||
|
||||
## Version specific information for Features on Demand and language packs
|
||||
|
||||
Windows 11, version 22H2, and later clients use on-premises Unified Update Platform (UUP) updates with WSUS and Microsoft Configuration Manager. These clients don't need to use **Specify settings for optional component installation and component repair** for FoDs and language packs since the content is available in WSUS due to on-premises UUP.
|
||||
Windows 11, version 22H2, and later clients use on-premises Unified Update Platform (UUP) updates with WSUS and Microsoft Configuration Manager. These clients don't need to use **Specify settings for optional component installation and component repair** for FoDs and language packs since the content is available in WSUS due to on-premises UUP. The policy was modified starting in Windows 11, version 24H2 to remove the unneeded options.<!--8914508-->
|
||||
|
||||
For Windows 10, version 2004 through Windows 11, version 21H2, clients can't download FoDs or language packs when **Specify settings for optional component installation and component repair** is set to Windows Update and **Specify source service for specific classes of Windows Updates** ([SetPolicyDrivenUpdateSourceFor<FeatureUpdates/QualityUpdates>](/windows/client-management/mdm/policy-csp-update#setpolicydrivenupdatesourceforfeatureupdates)) for either feature or quality updates is set to WSUS. If you need this content, you can set **Specify settings for optional component installation and component repair** to Windows Update and then either:
|
||||
- Change the source selection for feature and quality updates to Windows Update
|
||||
|
||||
@ -105,7 +105,6 @@ For more information about implementing Credential Guard, see the following reso
|
||||
- [Security considerations for Original Equipment Manufacturers](/windows-hardware/design/device-experiences/oem-security-considerations)
|
||||
- [Device Guard and Credential Guard hardware readiness tool](https://www.microsoft.com/download/details.aspx?id=53337)
|
||||
|
||||
|
||||
### AppLocker management
|
||||
|
||||
AppLocker in Windows Enterprise can be managed by using Group Policy. Group Policy requires having AD DS and that the Windows Enterprise devices are joined to an AD DS domain. AppLocker rules can be created by using Group Policy. The AppLocker rules can then be targeted to the appropriate devices.
|
||||
|
||||
Reference in New Issue
Block a user