deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-15 02:13:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Acrolinx fixes

Browse Source
This commit is contained in:
chrisjlin
2024-10-24 19:39:33 -07:00
parent 53de6a1d48
commit a3418e7c6b
11 changed files with 65 additions and 66 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -49,9 +49,9 @@ 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 Connnected Cache node
## Steps to point Windows client devices at Connected Cache node
Once you have successfully deployed Connected Cache to your Linux host machine, you will need to configure your Windows client device(s) to request Microsoft content from the 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.
You can do this by setting the [DOCacheHost or DOCacheHostSource policies via Intune](./waas-delivery-optimization-reference.md#cache-server-hostname).

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

@ -53,15 +53,15 @@ To deploy a cache node programmatically, you'll need to use Azure CLI to get the
If you're using a Local User account as the Connected Cache 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 Connected Cache runtime account.
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're using a Local User account as the Connected Cache 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
```
## Steps to point Windows client devices at Connnected Cache node
## Steps to point Windows client devices at Connected Cache node
Once you have successfully deployed Connected Cache to your Windows host machine, you will need to configure your Windows client device(s) to request Microsoft content from the 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.
You can do this by setting the [DOCacheHost or DOCacheHostSource policies via Intune](./waas-delivery-optimization-reference.md#cache-server-hostname).

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

@ -4,9 +4,9 @@ description: Overview, supported scenarios, and content types for Microsoft Conn
ms.service: windows-client
ms.subservice: itpro-updates
ms.topic: conceptual
ms.author: carmenf
author: cmknox
manager: aaroncz
ms.author: andyriv
author: chrisjlin
manager: naengler
ms.reviewer: mstewart
ms.collection: tier3
appliesto:
@ -35,27 +35,27 @@ Microsoft Connected Cache for Enterprise and Education (preview) is intended to
- Co-managed clients that get monthly updates and Win32 apps from Microsoft Intune
- Cloud-only managed devices, such as Intune-enrolled devices without the Configuration Manager client, that get monthly updates and Win32 apps from Microsoft Intune
Microsoft Connected Cache is built for flexible deployments to support a number of enterprise configurations:
Microsoft Connected Cache is built for flexible deployments to support several different enterprise configurations:
### Branch office
Customers may have globally dispersed offices that meet the following parameters:
Customers may have globally dispersed offices that meet some or all of the following parameters:
- 10 – 50 Windows Clients
- No dedicated server hardware
- Internet bandwidth is great to limited (satellite internet)
- Possibly intermittent connectivity
- Have 10 – 50 Windows devices on-site
- Don't have dedicated server hardware
- 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.
### Large Enterprise
Customers may have office spaces, data centers, or Azure deployments that meet the following parameters:
Customers may have office spaces, data centers, or Azure deployments that meet some or all of the following parameters:
- 100's or 1,000's of Windows devices (client or server).
- Existing hardware – Decommissioned DP, file server, cloud print server
- Azure VMs and Azure Virtual Desktop
- Internet bandwidth is great to limited (T1)
- 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)
To support the large enterprise scenario, customers can deploy a Connected Cache node to a server running Windows Server 2022 or Ubuntu 22.04.
@ -88,8 +88,8 @@ The following diagram displays an overview of how Connected Cache functions:
1. Prepare Windows or Linux devices. If deploying to Windows devices, prepare accounts - gMSA, local user account, domain account. Deploy to Windows or Linux devices using scripts.
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 fallback 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.
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
## Next steps

4
windows/deployment/do/mcc-ent-manage-using-cli.md
View File

@ -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 installting extensions, visit [Install the Connected Cache extension.](/cli/azure/azure-cli-extensions-overview#how-to-install-extensions)
To learn more about installing extensions, visit [Install the Connected Cache extension.](/cli/azure/azure-cli-extensions-overview#how-to-install-extensions)
<br>
<br>
@ -54,7 +54,7 @@ Once the resource group is created, you'll need to create a Microsoft Connected
A Connected Cache Azure resource is a top-level Azure resource under which cache nodes can be created.
To create an Connected Cache Azure resource, use `az mcc ent resource create`
To create a Connected Cache Azure resource, use `az mcc ent resource create`
```azurecli-interactive
az mcc ent resource create --mcc-resource-name mymccresource --resource-group myrg

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

@ -16,77 +16,76 @@ ms.date: 09/04/2024
# Monitor cache node usage
Tracking the status of your Connected Cache node is essential to making sure you are getting the most out of the service.
Tracking the status and performance of your Connected Cache node is essential to making sure you're getting the most out of the service.
For basic monitoring, navigate to the "Overview" tab. Here you will be able to view a cache node summary dashboard and charts for key metrics. No additional work is necessary, all the monitoring in this section will function right after your Connected Cache node has been installed.
For basic monitoring, navigate to the "Overview" tab. Here you'll be able to view a collection of predefined metrics and charts. All the monitoring in this section will function right after your Connected Cache node has been deployed.
For advanced monitoring, navigate to the "Metrics" section under the "Monitoring" tab. Here you will be able to access more sampled metrics (hits, misses, inbound traffic) and specify different aggregations (count, avg, min, max, sum). You can then use this data to create customized dashboards and configure alerts. Overall, this section is designed to cater to your specific monitoring needs and preferences.
For advanced monitoring, navigate to the "Metrics" section under the "Monitoring" tab. Here you'll be able to access more sampled metrics (hits, misses, inbound traffic) and specify different aggregations (count, avg, min, max, sum). You can then use this data to create customized charts and configure alerts.
Between the two monitoring sections, you will be able to gather essential insights into the health, performance, and efficiency of your Connected Cache nodes.
Between the two monitoring sections, you'll be able to gather essential insights into the health, performance, and efficiency of your Connected Cache nodes.
## Basic Monitoring
### Cache node summary
The preset monitoring data for Connected Cache is displayed on the Overview page in the Azure portal. Below are the metrics you will find in the "Cache Node Summary" dashboard, along with their descriptions. Please take note that this dashboard only reflects data from all cache nodes the last 24 hours. The filters that are displayed below the dashboard only affect the data shown in the "Key Metrics" charts.
Below are the metrics you'll find in the "Cache Node Summary" dashboard, along with their descriptions. This dashboard only reflects data received from cache nodes in the last 24 hours.
<!-- Add Cache node summary picture here -->
![Screenshot of cache node summary in the Azure portal interface.](../images/mcc-ent-cache-node-summary.png)
| Metric | Description |
| --- | --- |
| Healthy nodes | Your Connected Cache node will frequently send heartbeat messages to our backend. If your node has responded in the last 24 hours, it will be labeled as healthy. |
| Unhealthy nodes | If your node has not sent a heartbeat message in the last 24 hours, it will be labeled as unhealthy. |
| Max in | The maximum ingress in Mbps (Megabits per second) that your node has pulled from CDN in the last 24 hours. |
| Max out | The minimum egress in Mbps that your node has pushed out to devices in your network over the last 24 hours. |
| Average in | The average ingress in Mbps that your node has pulled from CDN in the last 24 hours. |
| Average out | The average egress in Mbps that your node has pushed out to devices in your network over the last 24 hours. |
| Cache efficiency | The percentage of all content requests your Connected Cache node receives that are ultimately delivered by your Connected Cache node. An well-performing node should have an efficiency > 90%. |
| Healthy nodes | Your Connected Cache node will periodically send heartbeat messages to the Connected Cache service. If the Connected Cache service has received a heartbeat message from your Connected Cache node in the last 24 hours, the node will be labeled as healthy. |
| Unhealthy nodes | If the Connected Cache service hasn't received a heartbeat message from your Connected Cache node in the last 24 hours, the node will be labeled as unhealthy. |
| Max in | The maximum ingress in Megabits per second (Mbps) that your node has pulled from CDN endpoints in the last 24 hours. |
| Max out | The minimum egress in Mbps that your node has sent to Windows devices in its network over the last 24 hours. |
| Average in | The average ingress in Mbps that your node has pulled from CDN endpoints in the last 24 hours. |
| Average out | The average egress in Mbps that your node has sent to Windows devices in its network over the last 24 hours. |
| Cache efficiency | The percentage of all content requests your Connected Cache node receives that can be fulfilled using your node's cached content. A well-performing node should have an efficiency > 90%. |
### Key Metrics
### Key metric charts
The two monitoring charts on the Overview page more visually represent the usage of your Connected Cache node, as well as the types cached content delivered by your node over various time intervals.
The two predefined charts on the Overview page visually represent the egress and types of content served by your Connected Cache node. The filters that are displayed below the cache node summary dashboard only affect the data shown in the key metric charts.
<!-- Add Charts picture here -->
![Screenshot of key metric charts in the Azure portal interface.](../images/mcc-ent-key-metric-charts.png)
#### Filters
Both filters displayed will only impact the data shown in the 2 charts below.
There are two filter controls that can be used to configure the key metric charts.
- By time: View data from the last 1 hour to 30 days
- By cache node: View data from individual cache nodes or the sum of all your active Connected Cache nodes.
- Timespan: Select how far back the chart should display
- Cache nodes: Select which Connected Cache nodes the chart should display data for
#### Outbound Traffic Chart
This chart displays the egress in Mbps that your Connected Cache node was delivering at specific timestamps. The value in the chart's key represents the average egress over the specified time period.
This chart displays the average egress in bits per second (b/s) that your selected Connected Cache nodes delivered over the specified timespan.
#### Volume by Content Type
This chart displays the amount (in GB) of each supported content type that your Connected Cache node is delivering at specific timestamps. You can find the complete list of supported content types here: [Microsoft Connected Cache content and services endpoints | Microsoft Learn](https://learn.microsoft.com/en-us/windows/deployment/do/delivery-optimization-endpoints)
This chart displays the volume of each supported content type in bytes (B) that your selected Connected Cache nodes delivered over the specified timespan. See [Microsoft Connected Cache content and services endpoints](delivery-optimization-endpoints.md) for a complete list of supported content types.
The content types in the key are sorted from highest to lowest volume an each have a distinct color. The bar chart is stacked such that you can visually compare total volume being delivered at different timestamps
The content types displayed in the chart each have a distinct color and are sorted in descending order of volume. The bar chart is stacked such that you can visually compare total volume being delivered at different points in time.
## Advanced Monitoring
To expand upon the metrics shown in the Overview tab, navigate to the "Metrics" tab in the left side toolbar of Azure Portal.
To expand upon the metrics shown in the Overview tab, navigate to the "Metrics" tab in the left side toolbar of Azure portal.
Listed below are the additional metrics you can access in this section:
Listed below are the metrics you can access in this section:
| Metric | Description |
| --- | --- |
| Inbound | The number of content requests your Connected Cache node receives over a specified period of time. |
| Hits | The number of times your Connected Cache node fulfills a content request by pulling from its cache. |
| Misses | The number of times your Connected Cache node is not able to fulfill a content request by pulling from its cache |
| Misses | The number of times your Connected Cache node isn't able to fulfill a content request by pulling from its cache |
### Customizable Dashboards
Once you select the charts you would like to track, you can save them over to a personalized dashboard. This dashboard enables you to configure the chart title, filters, range, legend, and more. You can also use this personalized dashboard to set up alerts that will notify you if your Connected Cache node dips in performance.
Once you select the charts you would like to track, you can save them to a personalized dashboard. You can configure the chart title, filters, range, legend, and more. You can also use this personalized dashboard to set up alerts that will notify you if your Connected Cache node dips in performance.
Some scenarios where you would want to set up these alerts:
• My Connected Cache node is being shown as unhealthy and I want to know exactly when it stopped egressing last.
A new Xbox update just released last night and I want to know if my Connected Cache node is helping deliver this content to my client machines.
Some example scenarios where you would want to set up a custom alert:
- My Connected Cache node is being shown as unhealthy and I want to know exactly when it stopped egressing last
- A new Microsoft Word update was released last night and I want to know if my Connected Cache node is helping deliver this content to my Windows devices
## Additional Metrics
Once the content has left the Connected Cache node, the node cannot track whether the content has successfully been delivered to the requesting Windows client. To access client-side data, you can refer to this page: [Monitor Delivery Optimization | Microsoft Learn](https://learn.microsoft.com/en-us/windows/deployment/do/waas-delivery-optimization-monitor)
Your Connected Cache node can keep track of how much content has been sent to requesting Windows devices, but the node can't track whether the content was successfully received by the device. For more information on accessing client-side data from your Windows devices, see [Monitor Delivery Optimization](waas-delivery-optimization-monitor.md).

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

@ -25,7 +25,7 @@ This article details the requirements and recommended specifications for using M
The Azure resources used for Connected Cache 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 Connected 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 a Connected 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 Education A3 or A5, included in [Microsoft 365 A3 or A5](https://www.microsoft.com/education/products/microsoft-365?msockid=32c407b43d5968050f2b13443c746916#Education-plans)
@ -63,11 +63,11 @@ This article details the requirements and recommended specifications for using M
### Recommended host machine hardware specifications
Based on your [enterprise configuration](mcc-ent-edu-overview.md), it is recommended to deploy your Connected Cache nodes to host machines that meet the following recommended hardware specifications.
Based on your [enterprise configuration](mcc-ent-edu-overview.md), it's recommended to deploy your Connected Cache nodes to host machines that meet the following recommended hardware specifications.
| | Branch Office | Small Enterprise | Large Enterprise |
| --- | --- | --- | --- |
| CPU cores | 4 | 8 | 16 |
| Memory | 8 GB, 4GB free | 16 GB, 4GB free | 32 GB, 4GB free |
| Memory | 8 GB, 4 GB free | 16 GB, 4 GB free | 32 GB, 4 GB free |
| Disk storage | 100 GB free | 500 GB free | 2x 200-500 GB free |
| NIC | 1 Gbps | 5 Gbps | 10 Gbps |

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

@ -26,7 +26,7 @@ This article contains details about the latest releases of Connected Cache. Sinc
- Contains client changes
- Affects Linux, Windows host machines
### Changenotes
### Change notes
- Added new "Outbound egress" and "Volume by Content type" monitoring charts to Azure portal user interface
- Added ability to create custom monitoring charts under the Metrics tab in the Azure portal user interface

2
windows/deployment/do/mcc-ent-troubleshooting.md
View File

@ -30,7 +30,7 @@ Connected Cache Azure resource creation can be initiated using either the Azure
## Troubleshooting cache node issue
If you are facing issues with your cache node, it could be due to cache node being on the early preview version of Connected Cache. Cache nodes belonging to early preview version will be under Connected Cache resource that will have 'early preview' in its name. Please delete these cache nodes and associated Connected Cache resource and create a new Connected Cache resource on the new version.
If you're facing issues with your cache node, it could be due to cache node being on the early preview version of Connected Cache. Cache nodes belonging to early preview version will be under Connected Cache resource that will have 'early preview' in its name. Please delete these cache nodes and associated Connected Cache resource and create a new Connected Cache resource on the new version.
For detailed instructions on creating Connected Cache resource, see [Create Connected Cache Azure resources](mcc-ent-create-resource-and-cache.md)
## Troubleshooting cache node deployment

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

@ -14,7 +14,7 @@ appliesto:
ms.date: 09/27/2024
---
# Uninstall Connected Cache caching software from a host machine
# Uninstall Connected Cache software from a host machine
This article describes how to uninstall Microsoft Connected Cache for Enterprise and Education caching software from a host machine. These steps should be taken after deleting the cache node in the Azure portal.

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

@ -36,25 +36,25 @@ All Connected Cache nodes are configured to update as part of the Fast ring by d
#### Slow Ring
Configuring an Connected Cache node to update as part of the Slow ring provides users with the option to delay Connected Cache software updates until the update can be validated. There are three settings that control when Connected Cache updates will be applied to Connected Cache nodes. All update ring settings can be managed from the Azure portal or through Azure CLI.
Configuring a Connected Cache node to update as part of the Slow ring provides users with the option to delay Connected Cache software updates until the update can be validated. There are three settings that control when Connected Cache updates will be applied to Connected Cache nodes. All update ring settings can be managed from the Azure portal or through Azure CLI.
| Setting | Description |
| --- | --- |
| Week of the month | 1st to 4th week can be selected. There are three to four months in a year that could have a 5th week. If there's a 5th week, the update could be applied during that 5th week if the day of the week falls near the last day of the month.|
| Week of the month | 1st to 4th week can be selected. There are three to four months in a year that could have a fifth week. If there's a fifth week, the update could be applied during that fifth week if the day of the week falls near the last day of the month.|
| Day of the week | Monday through Sunday can be selected. |
| Time of day | Time of day is based on UTC and a 24 hour clock. |
## Update process
When Microsoft publishes an Connected Cache update, the Connected Cache service attempts to update all Connected Cache nodes based on their Update Ring membership. If a cache node can't complete the silent Connected Cache update within 6 hours of starting, an error message is surfaced in the Azure portal.
When Microsoft publishes a Connected Cache update, the Connected Cache service attempts to update all Connected Cache nodes based on their Update Ring membership. If a cache node can't complete the silent Connected Cache update within 6 hours of starting, an error message is surfaced in the Azure portal.
## Update terminology, criteria, and SLA
Connected Cache updates will be released based on need instead of on a set cadence.
Connected Cache updates are released based on need instead of on a set cadence.
| 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 are released based on the severity rating of the vulnerability. Patches for [Critical and High](https://nvd.nist.gov/vuln-metrics/cvss) vulnerabilities are released by Microsoft within 60 days of discovery. Patches for [Medium and Low](https://nvd.nist.gov/vuln-metrics/cvss) vulnerabilities are 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 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 [Connected Cache release notes](mcc-ent-release-notes.md).

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

@ -36,9 +36,9 @@ These steps should be taken after deploying Connected Cache software to a [Windo
If successful, the Windows client device should begin to download a small image file from the Connected Cache node.
1. To check how much content an individual Windows client has pulled from an Connected 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 downloaded from a Connected 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 downloaded content from the cache node, you'll see a segment of the donut labeled "From Microsoft cache server".
## Related content