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

Acrolinx improvements

Browse Source
This commit is contained in:
chrisjlin 2024-09-27 13:51:56 -07:00
parent d226b8e8ba
commit c5c1082cca
5 changed files with 23 additions and 23 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
windows/deployment/do/mcc-enterprise-deploy-linux.md
View File

@ -17,11 +17,11 @@ appliesto:
This article describes how to deploy Microsoft Connected Cache for Enterprise and Education (MCCE) caching software to a Linux host machine.
Before deploying MCCE to a Linux host machine, ensure that the host machine meets all [requirements](mcc-enterprise-prerequisites.md) and you have [created and configured your MCC Azure resource](https://aka.ms/mccent-create-resources).
Before deploying MCCE to a Linux host machine, ensure that the host machine meets all [requirements](mcc-enterprise-prerequisites.md), and that you have [created and configured your MCC Azure resource](https://aka.ms/mccent-create-resources).
## Steps to deploy MCCE to Linux
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. 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.

10
windows/deployment/do/mcc-enterprise-deploy-windows.md
View File

@ -17,18 +17,18 @@ 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 relies on [Windows Subsystem for Linux (WSL)](https://learn.microsoft.com/en-us/windows/wsl/about) being installed under a [Group Managed Service Account (gMSA)](https://learn.microsoft.com/en-us/windows-server/security/group-managed-service-accounts/getting-started-with-group-managed-service-accounts) or [Local User Account](https://support.microsoft.com/en-us/windows/create-a-local-user-or-administrator-account-in-windows-20de74e0-ac7f-3502-a866-32915af2a34d) to isolate execution of the WSL-Microsoft Connected Cache distribution from the other users on the machine. This helps prevent tampering with both the WSL-MCC process and the cached content that is hosted on the disk.
Deploying MCCE to a Windows host machine requires designating a [Group Managed Service Account (gMSA)](https://learn.microsoft.com/en-us/windows-server/security/group-managed-service-accounts/getting-started-with-group-managed-service-accounts) or a [Local User Account](https://support.microsoft.com/en-us/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-enterprise-prerequisites.md) and you have [created and configured your MCC Azure resource](https://aka.ms/mccent-create-resources).
Before deploying MCCE to a Windows host machine, ensure that the host machine meets all [requirements](mcc-enterprise-prerequisites.md), and that you have [created and configured your MCC Azure resource](https://aka.ms/mccent-create-resources).
## Steps to deploy MCCE to Windows
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. Open a PowerShell windows *as administrator* on the host machine, then change directory to the extracted provisioning package.
1. Set the Execution Policy to "Unrestricted" to allow the provisoning 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"`.
- If you are using a Local User account as the MCCE runtime account, you will also need to create a [PS Credential Object](https://learn.microsoft.com/en-us/dotnet/api/system.management.automation.pscredential?view=powershellsdk-7.4.0) named `$myLocalAccountCredential`.
- 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/en-us/dotnet/api/system.management.automation.pscredential?view=powershellsdk-7.4.0) named `$myLocalAccountCredential`.
1. Run the provisioning command on the host machine.
## Next step

16
windows/deployment/do/mcc-enterprise-prerequisites.md
View File

@ -19,13 +19,13 @@ This article details the requirements and recommendations for using Microsoft Co
## Licensing requirements
- **Valid Azure subscription**: To use the Microsoft Connected Cache for Enterprise and Education (MCCE) service, you will 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 (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).
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 resources used for the public preview and in the future when this product is ready for production will be free to you, like other caching solutions.
The Azure resources used for MCCE 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 a 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 MCCE cache node.
- [Windows Enterprise E3 or E5](https://learn.microsoft.com/en-us/windows/whats-new/windows-licensing#windows-11-enterprise), included in [Microsoft 365 F3, E3, or E5](https://www.microsoft.com/en-us/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/en-us/education/products/microsoft-365?msockid=32c407b43d5968050f2b13443c746916#Education-plans)
@ -37,10 +37,10 @@ This article details the requirements and recommendations for using Microsoft Co
### General requirements
- Any previous installations of MCC must be [uninstalled](mcc-enterprise-update-uninstall.md) prior to installing the latest version of MCC.
- Any previous installations of MCC must be [uninstalled](mcc-enterprise-update-uninstall.md) before installing the latest version of MCC.
- [These listed endpoints](delivery-optimization-endpoints.md) must be reachable by the host machine.
- There must be no other services / applications utilizing port 80 on the host machine (e.g. ConfigManager, Distribution Point)
- There must be at least 4 GB of free memory on the host machine.
- The host machine must have no other services / applications utilizing port 80 (for example, ConfigManager or Distribution Point).
- The host machine must have at least 4 GB of free memory.
### Additional requirements for Windows host machines
@ -55,14 +55,14 @@ This article details the requirements and recommendations for using Microsoft Co
- The Linux host machine must be using one of the following Operating Systems:
- Ubuntu 20.04
- Red Hat Enterprise Linux 8.* or 9.*
- Red Hat Enterprise Linux (RHEL) 8.* or 9.*
- If using RHEL, the default container engine (Podman) must be replaced with [Moby](https://github.com/moby/moby#readme)
### Networking recommendations for host machines
- Multiple network interface cards (NICs) on a single MCC instance aren't supported.
- 1 Gbps NIC is the minimum speed recommended but any NIC is supported.
- For best performance, NIC and BIOS should support SR-IOV.
- The NIC and BIOS should support SR-IOV for best performance.
### Host machine sizing recommendations

10
windows/deployment/do/mcc-enterprise-uninstall.md
View File

@ -16,7 +16,7 @@ ms.date: 09/27/2024
# Uninstall MCCE 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. This should be done after deleting the cache node in the Azure Portal.
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.
## Steps to uninstall MCCE from a Windows host machine
@ -25,11 +25,11 @@ This article describes how to uninstall Microsoft Connected Cache for Enterprise
## Steps to uninstall MCCE from a Linux host machine
The `uninstallmcc.sh` script within the provisioning package will uninstall the MCCE caching software and all related components, including:
The `uninstallmcc.sh` script within the provisioning package uninstalls the MCCE caching software and all related components, including:
- IoT Edge
- Edge Agent
- Edge Hub
- IoT Edge Agent
- IoT Edge Hub
- MCC
- Moby CLI
- Moby engine
- Moby engine

6
windows/deployment/do/mcc-enterprise-verify-functionality.md
View File

@ -18,7 +18,7 @@ appliesto:
This article describes how to verify that a Microsoft Connected Cache for Enterprise and Education (MCCE) cache node is functioning correctly.
This should be done after deploying MCCE caching software to a [Windows](mcc-enterprise-deploy-windows.md) or [Linux](mcc-enterprise-deploy-linux.md) host machine.
These steps should be taken after deploying MCCE caching software to a [Windows](mcc-enterprise-deploy-windows.md) or [Linux](mcc-enterprise-deploy-linux.md) host machine.
## Steps to verify functionality of MCCE cache node
@ -30,13 +30,13 @@ This should be done after deploying MCCE caching software to a [Windows](mcc-ent
If successful, there should be an HTTP response with StatusCode 200.
1. To verify that the MCCE cache node can be reached by Windows clients in your network, 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 MCCE 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`
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 a MCCE cache node, open the [Delivery Optimization activity monitor](https://learn.microsoft.com/en-us/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](https://learn.microsoft.com/en-us/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".