diff --git a/windows/deployment/do/TOC.yml b/windows/deployment/do/TOC.yml index a86ca6bef1..b9d7757f89 100644 --- a/windows/deployment/do/TOC.yml +++ b/windows/deployment/do/TOC.yml @@ -35,7 +35,7 @@ href: waas-microsoft-connected-cache.md - name: Microsoft Connected Cache for Enterprise and Education items: - - name: Connected Cache for Enterprise and Education Overview + - name: Connected Cache for Enterprise and Education overview href: mcc-ent-edu-overview.md - name: Requirements href: mcc-ent-prerequisites.md diff --git a/windows/deployment/do/mcc-ent-create-resource-and-cache.md b/windows/deployment/do/mcc-ent-create-resource-and-cache.md index 3f022ca166..bae29c6ffa 100644 --- a/windows/deployment/do/mcc-ent-create-resource-and-cache.md +++ b/windows/deployment/do/mcc-ent-create-resource-and-cache.md @@ -30,16 +30,16 @@ For more information on sizing and OS requirements, see [the prerequisites for u # [Azure portal](#tab/portal) -1. In the [Azure portal](https://portal.azure.com), select **Create a Resource** and search for "Microsoft Connected Cache for Enterprise and Education". +1. In the [Azure portal](https://portal.azure.com), select **Create a Resource** and search for `Microsoft Connected Cache for Enterprise and Education`. -1. Select the Microsoft Connected Cache for Enterprise resource. When prompted, choose the subscription, resource group, and location for the resource. Then enter a name for the resource and select Review + Create. +1. Select the Microsoft Connected Cache for Enterprise resource. When prompted, choose the subscription, resource group, and location for the resource. Then enter a name for the resource, then select Review + Create. 1. After a few moments, you'll see a "Validation successful" message, indicating you can move onto the next step and select Create. -1. The creation of the resource might take a few minutes. After a successful creation, you'll see a Deployment complete page as below. Select Go to resource to create cache nodes. +1. The creation of the resource might take a few minutes. After a successful creation, you'll see a page stating the deployment is complete. Select **Go to resource** to create cache nodes. # [Azure CLI](#tab/cli) @@ -78,15 +78,15 @@ az mcc ent resource create --mcc-resource-name --resource-group # [Azure portal](#tab/portal) 1. Open Azure portal and navigate to the Microsoft Connected Cache for Enterprise resource that you created.
- 1. Under Cache Node Management, select on Cache Nodes and then on + Create Cache Node.
+ 1. Under Cache Node Management, select **Cache Nodes** then **Create Cache Node**.
- 1. Provide a name for your cache node and select the host OS you plan to deploy the cache node on and select create. Note, cache node names have to be unique under the Microsoft Connected Cache resource. + 1. Provide a name for your cache node and select the host OS you plan to deploy the cache node on, then select **Create**. Note, cache node names have to be unique under the Microsoft Connected Cache resource. - The creation of cache node might take a few minutes. Select Refresh to see your recently created cache node. + The creation of the cache node might take a few minutes. Select **Refresh** to see your recently created cache node. Once the cache node state changes to **Not Configured**, you can now configure your cache node.
-To know more about different cache node state, see [Cache node states](#cache-node-states). +For more information about different cache node states, see [Cache node states](#cache-node-states). # [Azure CLI](#tab/cli) @@ -98,7 +98,7 @@ Replace the following placeholders with your own information: * *\*: Name of the Microsoft Connected Cache for Enterprise resource. * *\*: A name for your Microsoft Connected Cache node. * *\*: The OS on which cache node will be provisioned. - Accepted values: windows, linux + Accepted values: `windows`, `linux` ```azurecli-interactive az mcc ent node create --cache-node-name --mcc-resource-name --resource-group --host-os @@ -107,12 +107,12 @@ az mcc ent node create --cache-node-name --mcc-resource-name >[!NOTE] ->To ensure cache node has been created successfully, please run the following command before continuing with cache node configuration. +>To ensure cache node has been created successfully, run the following command before continuing with cache node configuration. >```azurecli-interactive >az mcc ent node show --cache-node-name --mcc-resource-name --resource-group >``` ->In the output look for cacheNodeState. If ***cacheNodeState = Not Configured***, you can continue with cache node configuration. ->If ***cacheNodeState = Registration in Progress***, then the cache node is still in process of being created. Please wait for a minute or two more and run the command again. +>In the output look for **cacheNodeState**. If ***cacheNodeState = Not Configured***, you can continue with cache node configuration. +>If ***cacheNodeState = Registration in Progress***, then the cache node is still in process of being created. Wait a couple of minutes and run the command again. >To know more about different cache node state, see [Cache node states](#cache-node-states). --- @@ -120,7 +120,7 @@ az mcc ent node create --cache-node-name --mcc-resource-name *: Name of the resource group in your subscription. * *\*: Name of your Microsoft Connected Cache for Enterprise resource. * *\*: Name for your Microsoft Connected Cache node. -* *\*: The cache drive path. You can add upto nine cache drives. +* *\*: The cache drive path. You can add up to nine cache drives. * *\*: The size of cache drive. Must be at least 50 Gb. * *\*: If proxy needs to be enabled or not.
- Accepted values: enabled, disabled
+ Accepted values: `enabled`, `disabled`
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 Connected Cache cache node to your host machine. * *\*: The proxy host name or ip address. Required if proxy is set to enabled. * *\*: Proxy port number. Required if proxy is set to enabled. * *\*: Update ring the cache node should have.
- 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. * *\*: The day of the week cache node should be updated. Week starts from Monday.
Accepted values: 1,2,3,4,5,6,7 @@ -170,12 +170,12 @@ Replace the following placeholders with your own information: Accepted value: /var/mcc * *\*: The size of cache drive. Must be at least 50 Gb. * *\*: If proxy needs to be enabled or not.
- Accepted values: enabled, disabled
+ Accepted values: `enabled`, `disabled`
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 Connected Cache cache node to your host machine. * *\*: The proxy host name or ip address. Required if proxy is set to enabled. * *\*: Proxy port number. Required if proxy is set to enabled. * *\*: Update ring the cache node should have.
- 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. * *\*: The day of the week cache node should be updated. Week starts from Monday.
Accepted values: 1,2,3,4,5,6,7 diff --git a/windows/deployment/do/mcc-ent-deploy-to-linux.md b/windows/deployment/do/mcc-ent-deploy-to-linux.md index b7cfb00596..0fc31cdf23 100644 --- a/windows/deployment/do/mcc-ent-deploy-to-linux.md +++ b/windows/deployment/do/mcc-ent-deploy-to-linux.md @@ -49,6 +49,8 @@ To deploy a cache node programmatically, you'll need to use Azure CLI to get the 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 ``` +--- + ## Steps to point Windows client devices at Connected Cache node Once you have successfully deployed Connected Cache to your Linux host machine, you'll need to configure your Windows client devices to request Microsoft content from the Connected Cache node. diff --git a/windows/deployment/do/mcc-ent-deploy-to-windows.md b/windows/deployment/do/mcc-ent-deploy-to-windows.md index d5180ee2f1..ba27a5f82f 100644 --- a/windows/deployment/do/mcc-ent-deploy-to-windows.md +++ b/windows/deployment/do/mcc-ent-deploy-to-windows.md @@ -63,6 +63,8 @@ To deploy a cache node programmatically, you'll need to use Azure CLI to get the ./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 ``` +--- + ## Steps to point Windows client devices at Connected Cache node Once you have successfully deployed Connected Cache to your Windows host machine, you'll need to configure your Windows client devices to request Microsoft content from the Connected Cache node. diff --git a/windows/deployment/do/mcc-ent-edu-overview.md b/windows/deployment/do/mcc-ent-edu-overview.md index e96d65af39..70acb8886c 100644 --- a/windows/deployment/do/mcc-ent-edu-overview.md +++ b/windows/deployment/do/mcc-ent-edu-overview.md @@ -21,11 +21,11 @@ ms.date: 10/30/2024 > [!IMPORTANT] > Microsoft Connected Cache is currently a preview feature. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). -Microsoft Connected Cache for Enterprise and Education (preview) is a software-only caching solution that delivers Microsoft content within Enterprise and Education networks. Connected Cache can be managed from an Azure portal or through Azure CLI and can be deployed to as many Windows devices, Linux devices, or VMs as needed. Managed Windows devices can be configured to download cloud content from a Connected Cache server by applying the client policy using management tools such as Intune. +Microsoft Connected Cache for Enterprise and Education (preview) is a software-only caching solution that delivers Microsoft content within enterprise and education networks. Connected Cache can be managed from the Azure portal or through Azure CLI. It can be deployed to as many Windows devices, Linux devices, or VMs as needed. Managed Windows devices can be configured to download cloud content from a Connected Cache server by applying the client policy using management tools such as Microsoft Intune. -For information about Microsoft Connected Cache in Configuration Manager (generally available, starting Configuration Manager version 2111), see [Microsoft Connected Cache in Configuration Manager](/configmgr/core/plan-design/hierarchy/microsoft-connected-cache). +For information about Microsoft Connected Cache in Configuration Manager, see [Microsoft Connected Cache in Configuration Manager](/configmgr/core/plan-design/hierarchy/microsoft-connected-cache). -Microsoft Connected Cache deployed directly to Windows relies on [Windows Subsystem for Linux](/windows/wsl/about) and either a [Group Managed Service Account](/windows-server/identity/ad-ds/manage/group-managed-service-accounts/group-managed-service-accounts/getting-started-with-group-managed-service-accounts), local user account, or domain user account are required to run WSL. WSL needs to run in a user context and any user, even if the currently logged-in user, could be used to run WSL and Microsoft Connected Cache. +Microsoft Connected Cache deployed directly to Windows relies on [Windows Subsystem for Linux (WSL](/windows/wsl/about) and either a [Group Managed Service Account](/windows-server/identity/ad-ds/manage/group-managed-service-accounts/group-managed-service-accounts/getting-started-with-group-managed-service-accounts), local user account, or domain user account are required to run WSL. WSL needs to run in a user context and any user, even if the currently logged-in user, could be used to run WSL and Microsoft Connected Cache. ## Supported scenarios and configurations @@ -41,10 +41,10 @@ Microsoft Connected Cache is built for flexible deployments to support several d Customers may have globally dispersed offices that meet some or all of the following parameters: -- Have 10 – 50 Windows devices on-site +- Have 10 to 50 Windows devices on-site - Don't have dedicated server hardware -- Have Internet bandwidth that is limited (satellite internet) -- Have intermittent Internet connectivity +- Have internet bandwidth that is limited (satellite internet) +- Have intermittent internet connectivity To support the branch office scenario, customers can deploy a Connected Cache node to a Windows 11 client device. @@ -55,7 +55,7 @@ Customers may have office spaces, data centers, or Azure deployments that meet s - Have 100s or 1,000s of Windows devices (desktop or server) - Have some existing server hardware (Decommissioned Distribution Point, file server, cloud print server) - Have Azure VMs and/or Azure Virtual Desktop deployed -- Have Internet bandwidth that is mediocre (T1 or T3 lines) +- Have limited internet bandwidth (T1 or T3 lines) To support the large enterprise scenario, customers can deploy a Connected Cache node to a server running Windows Server 2022 or Ubuntu 22.04. @@ -63,9 +63,9 @@ See [Connected Cache node host machine requirements](mcc-ent-prerequisites.md) f | Enterprise configuration | Download speed range | Download speeds and approximate content volume delivered in 8 Hours | |---|---|---| -|Branch Office|< 1 Gbps Peak| 500 Mbps => 1,800 GB

250 Mbps => 900 GB

100 Mbps => 360 GB

50 Mbps => 180 GB| -|Small to Medium Enterprises/Autopilot Provisioning Center (50 - 500 devices in a single location) |1 - 5 Gbps| 5 Gbps => 18,000 GB

3 Gbps => 10,800 GB

1 Gbps => 3,600 GB| -|Medium to Large Enterprises/Autopilot Provisioning Center (500 - 5,000 devices in a single location) |5 - 101 Gbps Peak| 9 Gbps => 32,400 GB

5 Gbps => 18,000 GB

3 Gbps => 10,800 GB| +|Branch office|< 1 Gbps Peak| 500 Mbps => 1,800 GB

250 Mbps => 900 GB

100 Mbps => 360 GB

50 Mbps => 180 GB| +|Small to medium enterprises/Autopilot provisioning center (50 - 500 devices in a single location) |1 - 5 Gbps| 5 Gbps => 18,000 GB

3 Gbps => 10,800 GB

1 Gbps => 3,600 GB| +|Medium to large enterprises/Autopilot provisioning center (500 - 5,000 devices in a single location) |5 - 101 Gbps Peak| 9 Gbps => 32,400 GB

5 Gbps => 18,000 GB

3 Gbps => 10,800 GB| ## Supported content types @@ -89,8 +89,8 @@ The following diagram displays an overview of how Connected Cache functions: 1. The Microsoft Connected Cache container is deployed to the device using Azure IoT Edge container management services and the cache server begins reporting status and metrics to Delivery Optimization services. 1. The DOCacheHost setting is configured using Intune or other MDM, DHCP custom option, or registry key. 1. Devices request content from the cache server, the cache server forwards the requests to the CDN and fills the cache, the cache server delivers the content requested to the devices, and uses Peer to Peer (depending on DO Download mode settings) for all DO content. -1. Devices can fall back to CDN if cache server is unavailable for any reason or use Delivery Optimization delay fallback to http (CDN) settings to prefer the local cache server. -Customers can view data regarding Microsoft Connected Cache downloads on management portal and Windows Update for Business reports +1. Devices can fall back to CDN if the cache server is unavailable for any reason or use Delivery Optimization delay fallback to http (CDN) settings to prefer the local cache server. +You can view data about Microsoft Connected Cache downloads on management portal and Windows Update for Business reports. ## Next steps diff --git a/windows/deployment/do/mcc-ent-manage-using-cli.md b/windows/deployment/do/mcc-ent-manage-using-cli.md index 2b6393ee4e..ffb7e198d8 100644 --- a/windows/deployment/do/mcc-ent-manage-using-cli.md +++ b/windows/deployment/do/mcc-ent-manage-using-cli.md @@ -31,7 +31,7 @@ This article outlines how to create, configure, and deploy Microsoft Connected C az extension add --name mcc ``` -To learn more about installing extensions, visit [Install the Connected Cache extension.](/cli/azure/azure-cli-extensions-overview#how-to-install-extensions) +To learn more about installing extensions, see [Install the Connected Cache extension.](/cli/azure/azure-cli-extensions-overview#how-to-install-extensions)

@@ -138,11 +138,11 @@ az mcc ent node get-provisioning-details --cache-node-name mycachenode --mcc-res >[!IMPORTANT] >* Save the resulting values for cacheNodeId, customerKey, mccResourceId, registrationKey. These GUIDs are needed to create the provisioning script. >* In the output look for cacheNodeState. If **cacheNodeState = Not Provisioned**, you can continue with cache node provisioning. ->* If **cacheNodeState = Not Configured**, then the cache node has not been configured. Please configure the cache node before provisioning. +>* If **cacheNodeState = Not Configured**, then the cache node has not been configured. Configure the cache node before provisioning. ### Example script: -Below is a pseudocode example of how to script bulk creation and configuration of a Connected Cache Azure resource and multiple Connected Cache cache nodes. +Below is a pseudocode example of how to script bulk creation and configuration of a Connected Cache Azure resource and multiple Connected Cache cache nodes: