mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
cleanup files, remove images and ver history
This commit is contained in:
Meghan Stewart
parent
920e692c21
commit
cff22a6801
@ -35,7 +35,7 @@
|
||||
href: mcc-enterprise-prerequisites.md
|
||||
- name: Deploy Microsoft Connected Cache
|
||||
href: mcc-enterprise-deploy.md
|
||||
- name: Update and uninstall cache node
|
||||
- name: Update or uninstall MCC
|
||||
href: mcc-enterprise-update-uninstall.md
|
||||
- name: Appendix
|
||||
href: mcc-enterprise-appendix.md
|
||||
@ -59,8 +59,6 @@
|
||||
href: mcc-isp-vm-performance.md
|
||||
- name: Support and troubleshooting
|
||||
href: mcc-isp-support.md
|
||||
- name: Version history
|
||||
href: mcc-version-history.md
|
||||
- name: MCC for ISPs (Early Preview)
|
||||
href: mcc-isp.md
|
||||
- name: Content endpoints for Delivery Optimization and Microsoft Connected Cache
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 208 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 242 KiB |
@ -115,7 +115,3 @@ To verify that the Delivery Optimization client can download content using MCC,
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-delivery-optimization-activity.png" alt-text="Screenshot of the Delivery Optimization Activity Monitor.":::
|
||||
|
||||
## More information
|
||||
|
||||
[Microsoft Connected Cache for ISPs](mcc-isp.md)</br>
|
||||
[Introducing Microsoft Connected Cache](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/introducing-microsoft-connected-cache-microsoft-s-cloud-managed/ba-p/963898)
|
||||
|
||||
@ -16,6 +16,7 @@ ms.topic: article
|
||||
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
## Enterprise requirements for MCC
|
||||
|
||||
1. **Azure subscription**: MCC management portal is hosted within Azure and is used to create the Connected Cache [Azure resource](/azure/cloud-adoption-framework/govern/resource-consistency/resource-access-management) and IoT Hub resource. Both are free services.
|
||||
|
||||
@ -31,12 +31,8 @@ This article outlines how to create, provision, and deploy your Microsoft Connec
|
||||
|
||||
1. Navigate to **Settings** > **Cache nodes** and select **Create Cache Node**.
|
||||
|
||||
:::image type="content" source="images/mcc-isp-create-cache-node.png" alt-text="Screenshot of the cache node page in the Azure portal":::
|
||||
|
||||
1. Provide a name for your cache node and select **Create** to create your cache node.
|
||||
|
||||
:::image type="content" source="images/mcc-isp-cache-node-name.png" alt-text="Screenshot of the create cache node page in the Azure portal, with the cache node name input field.":::
|
||||
|
||||
## Configure cache node
|
||||
|
||||
During the configuration of your cache node, there are many fields for you to configure your cache node. To learn more about the definitions of each field, review the [Configuration fields](#general-configuration-fields) at the bottom of this article.
|
||||
@ -118,7 +114,7 @@ There are five IDs that the device provisioning script takes as input in order t
|
||||
|
||||
1. Run the deployment script that is shown for your cache node in Azure portal by copying and pasting the script in your terminal. The script may take a few minutes to run. If there were no errors, you have set up your cache node successfully. To verify the server is set up correctly, follow the [verification steps](mcc-isp-verify-cache-node.md).
|
||||
|
||||
## General configuration fields
|
||||
### General configuration fields
|
||||
|
||||
| Field Name | Expected Value| Description |
|
||||
|---|---|---|
|
||||
|
||||
@ -40,18 +40,16 @@ This article details the process of signing up for Microsoft Connected Cache for
|
||||
|
||||
> [!NOTE]
|
||||
> Verification codes expire in 24 hours. You will need to generate a new code if it expires.
|
||||
|
||||
:::image type="content" source="images/mcc-isp-operator-verification.png" alt-text="Screenshot of the sign up verification page on Azure portal for Microsoft Connected Cache.":::
|
||||
|
||||
1. Once verified, follow the instructions in [Create, provision, and deploy cache node](mcc-isp-create-provision-deploy.md) to create your cache node.
|
||||
|
||||
## Traffic estimation
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This traffic estimation feature is coming soon! Stay tuned.
|
||||
<!--## Traffic estimation
|
||||
|
||||
During the sign-up process, Microsoft will provide you with a traffic estimation based on your ASN(s). We make estimations based on our predictions on historical data about Microsoft content download volume. We'll use these estimations to recommend hardware or VM configurations. You can review these recommendations within the Azure portal.
|
||||
|
||||
We make these estimations based on the Microsoft content types that Microsoft Connected Cache serves. To learn more about the types of content that are supported, see [Delivery Optimization and Microsoft Connected Cache content type endpoints](delivery-optimization-endpoints.md).
|
||||
We make these estimations based on the Microsoft content types that Microsoft Connected Cache serves. To learn more about the types of content that are supported, see [Delivery Optimization and Microsoft Connected Cache content type endpoints](delivery-optimization-endpoints.md). -->
|
||||
|
||||
### Cache performance
|
||||
|
||||
@ -74,7 +72,7 @@ RAID disk configurations are discouraged as cache performance will be impacted.
|
||||
|
||||
### Hardware configuration example
|
||||
|
||||
There are many hardware configurations that suit Microsoft Connected Cache. As an example, a customer has deployed the following hardware configuration and is able achieve a peak egress of about 35 Gbps:
|
||||
There are many hardware configurations that suit Microsoft Connected Cache. As an example, a customer has deployed the following hardware configuration and is able to achieve a peak egress of about 35 Gbps:
|
||||
|
||||
**Dell PowerEdge R330**
|
||||
|
||||
|
||||
@ -23,8 +23,6 @@ Microsoft will release updates for Microsoft Connected Cache periodically to imp
|
||||
|
||||
To view which version your cache nodes are currently on, navigate to the **Cache nodes** tab to view the versions in the list view.
|
||||
|
||||
To view update release notes, visit [Version history](mcc-version-history.md).
|
||||
|
||||
## Uninstall cache node
|
||||
|
||||
There are two main steps required to uninstall your cache node:
|
||||
|
||||
@ -41,8 +41,6 @@ Saving to: 'wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com'
|
||||
wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com 100%[========================]
|
||||
```
|
||||
|
||||
:::image type="content" source="images/mcc-isp-wget.png" alt-text="Terminal output of successful test result with wget command to validate a Microsoft Connected Cache node." lightbox="./images/mcc-isp-wget.png":::
|
||||
|
||||
Similarly, enter the following URL into a web browser on any device on the network:
|
||||
|
||||
```http
|
||||
|
||||
@ -1,25 +0,0 @@
|
||||
---
|
||||
title: Version history
|
||||
manager: aaroncz
|
||||
description: This page tracks the version history of Microsoft Connected Cache
|
||||
keywords: updates, downloads, network, bandwidth
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
audience: itpro
|
||||
author: amyzhou
|
||||
ms.localizationpriority: medium
|
||||
ms.author: amyzhou
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Version History
|
||||
Microsoft periodically releases software updates for your cache nodes to improve performance, caching efficiency, and other bug fixes. These updates will be performed automatically at low-traffic hours.
|
||||
|
||||
## Current Version
|
||||
#### Version 1332
|
||||
Released September 15, 2022
|
||||
|
||||
Version notes:
|
||||
- Fix for caching TLU (Time Limited URLs) - There was a problem and some files that were accessed via TLUs were returning 403 errors
|
||||
- Core Caching Engine optimizations that will dynamically configure caching settings based on the available system resources.
|
||||
Loading…
x
Reference in New Issue
Block a user