mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-07 10:07:21 +00:00
edits
This commit is contained in:
Meghan Stewart
parent
9ef04f6ec6
commit
35293bae63
@ -65,7 +65,7 @@
|
||||
href: mcc-ent-faq.yml
|
||||
- name: Troubleshooting
|
||||
href: mcc-ent-troubleshooting.md
|
||||
- name: Microsoft Connected Cache for Enterprise and Education Early Preview
|
||||
- name: Microsoft Connected Cache for Enterprise and Education early preview
|
||||
href: mcc-ent-early-preview.md
|
||||
- name: Release notes
|
||||
href: mcc-ent-release-notes.md
|
||||
|
||||
@ -67,10 +67,12 @@ landingContent:
|
||||
linkLists:
|
||||
- linkListType: deploy
|
||||
links:
|
||||
- text: Connected Cache for Enterprise and Education (early preview)
|
||||
url: waas-microsoft-connected-cache.md
|
||||
- text: Sign up
|
||||
url: https://aka.ms/MSConnectedCacheSignup
|
||||
- text: Connected Cache for Enterprise and Education overview
|
||||
url: mcc-ent-edu-overview.md
|
||||
- text: Connected Cache for Enterprise and Education requirements
|
||||
url: mcc-ent-edu-mcc-ent-prerequisites.md
|
||||
- text: Create the Microsoft Connected Cache Azure resource and cache nodes
|
||||
url: mcc-ent-create-resource-and-cache.md
|
||||
|
||||
# Card
|
||||
- title: Microsoft Connected Cache for Internet Service Providers (ISPs)
|
||||
@ -79,8 +81,6 @@ landingContent:
|
||||
links:
|
||||
- text: Connected Cache for ISPs (public preview)
|
||||
url: mcc-isp-signup.md
|
||||
- text: Sign up
|
||||
url: https://aka.ms/MCCForISPSurvey
|
||||
- text: Connected Cache for ISPs (early preview)
|
||||
url: mcc-isp.md
|
||||
|
||||
|
||||
@ -279,7 +279,7 @@ az mcc ent resource list --resource-group <myrg>
|
||||
### List all cache nodes
|
||||
|
||||
# [Azure portal](#tab/portal)
|
||||
On the left pane, click on 'Cache Nodes' under 'Cache Node Management' to see all the cache nodes under the Connected Cache resource.
|
||||
On the left pane, select **Cache Nodes** under **Cache Node Management** to see all the cache nodes under the Connected Cache resource.
|
||||
|
||||
|
||||
# [Azure CLI](#tab/cli)
|
||||
@ -299,7 +299,7 @@ az mcc ent node list --mcc-resource-name <mymccresource> --resource-group <myrg>
|
||||
### Delete Connected Cache resource
|
||||
|
||||
# [Azure portal](#tab/portal)
|
||||
Navigate to the Connected Cache resource to delete and click on the delete button on top.
|
||||
Navigate to the Connected Cache resource to delete, then select the **Delete** button on top.
|
||||
|
||||
|
||||
# [Azure CLI](#tab/cli)
|
||||
@ -319,7 +319,7 @@ az mcc ent node delete --cache-node-name <mycachenode> --mcc-resource-name <mymc
|
||||
### Delete cache node
|
||||
|
||||
# [Azure portal](#tab/portal)
|
||||
On the left pane, click on 'Cache Nodes' under 'Cache Node Management' to see all the cache nodes under the Connected Cache resource. Select the cache node you wish to delete and click delete button on top of the page.
|
||||
On the left pane, select **Cache Nodes** under **Cache Node Management** to see all the cache nodes under the Connected Cache resource. Select the cache node you wish to delete and select the **Delete** button on top of the page.
|
||||
|
||||
|
||||
# [Azure CLI](#tab/cli)
|
||||
|
||||
@ -23,7 +23,7 @@ Before deploying Connected Cache to a Linux host machine, ensure that the host m
|
||||
|
||||
# [Azure portal](#tab/portal)
|
||||
|
||||
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.
|
||||
@ -46,7 +46,7 @@ To deploy a cache node programmatically, you'll need to use Azure CLI to get the
|
||||
1. Replace the values in the following provisioning command before running it on the host machine.
|
||||
|
||||
```azurepowershell-interactive
|
||||
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
|
||||
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
|
||||
|
||||
@ -25,10 +25,10 @@ Before deploying Connected Cache to a Windows host machine, ensure that the host
|
||||
|
||||
# [Azure portal](#tab/portal)
|
||||
|
||||
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. **Note**: The installer should be in a folder that isn't synced to OneDrive, as this will interfere with the installation process.
|
||||
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. 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 Connected Cache runtime account.
|
||||
|
||||
For gMSAs, the value should be formatted as `"Domain\Username$"`. For Local User accounts, `$User` should be formatted as `"LocalMachineName\Username"`.
|
||||
@ -50,7 +50,7 @@ To deploy a cache node programmatically, you'll need to use Azure CLI to get the
|
||||
1. Save the resulting output. These values will be passed as parameters within the provisioning command.
|
||||
1. Download and extract the [Connected Cache provisioning package for Windows](https://aka.ms/MCC-Ent-InstallScript-WSL) to your host machine. **Note**: The installer should be in a folder that isn't synced to OneDrive, as this will interfere with the installation process.
|
||||
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. 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 Connected Cache runtime account.
|
||||
|
||||
For gMSAs, the value should be formatted as `"Domain\Username$"`. For Local User accounts, `$User` should be formatted as `"LocalMachineName\Username"`.
|
||||
|
||||
@ -57,7 +57,7 @@ sections:
|
||||
- question: Where can I monitor cache node usage?
|
||||
answer: You can monitor your cache node usage on Azure portal. For more information, see [Monitor cache node usage Info on Reporting Capabilities](mcc-ent-monitoring.md).
|
||||
- question: How does Microsoft Connected Cache populate its content? Can I precache content?
|
||||
answer: Microsoft Connected Cache is a cold cache warmed by client requests at the byte range level so your clients only request the content they need. The client requests content and that is what fills the cache which means there's no cache fill necessary. "Preseeding" can be achieved but use of update rings. A test ring or early adopter ring can be used to fill the cache and all subsequent requests by other clients will come from cache.
|
||||
answer: Microsoft Connected Cache is a cold cache warmed by client requests at the byte range level so your clients only request the content they need. The client requests content and that is what fills the cache which means there's no cache fill necessary. "Preseeding" can be achieved by use of update rings. A test ring or early adopter ring can be used to fill the cache and all subsequent requests by other clients will come from cache.
|
||||
- question: How long would a piece of content live within the Microsoft Connected Cache? Is content purged from the cache?
|
||||
answer: Once a request for said content is made, NGINX looks at the cache control headers from the original acquisition. If that content is expired, NGINX continues to serve the stale content while it's downloading the new content. We cache the content for 30 days. The content is in the hot cache path (open handles and such) for 24 hrs, but resides on disk for 30 days. The drive fills up and nginx starts to delete content based on its own algorithm, probably some combination of least recently used.
|
||||
- question: Is it possible to not update the Microsoft Connected Cache software or delay update longer than the timeline provided in the updates configuration?
|
||||
|
||||
@ -119,7 +119,7 @@ az mcc ent node update --cache-node-name <mycachenode> --mcc-resource-name <mymc
|
||||
|
||||
>[!Note]
|
||||
>* For a cache node that is to be deployed on Windows host OS, the physical path of the cache drive <u>must</u> be **/var/mcc**.<br>
|
||||
>* In the output, look for operationStatus. **operationStatus = Succeeded** indicates that our services have successfully updated the cache node. You will also see that cacheNodeState will show "Not Provisioned". <br>
|
||||
>* In the output, look for operationStatus. **operationStatus = Succeeded** indicates that our services have successfully updated the cache node. You will also see that cacheNodeState will show *Not Provisioned*. <br>
|
||||
>* Please save values for <u>physicalPath, sizeInGb, proxyPort, proxyHostName</u> as these values will be needed to construct the provisioning script.
|
||||
|
||||
|
||||
@ -170,7 +170,7 @@ $proxyHost = "myProxy.com"
|
||||
$proxyPort = "8080"
|
||||
$waitTime = 3
|
||||
|
||||
#Create MCC Az resource
|
||||
# Create Microsoft Connected Cache Azure resource
|
||||
az mcc ent resource create --mcc-resource-name $mccResourceName --location $resourceLocation --resource-group $resourceGroup
|
||||
|
||||
#Loop through $cacheNodesToCreate iterations
|
||||
|
||||
@ -18,9 +18,9 @@ ms.date: 09/04/2024
|
||||
|
||||
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'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 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'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.
|
||||
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'll be able to gather essential insights into the health, performance, and efficiency of your Connected Cache nodes.
|
||||
|
||||
@ -28,7 +28,7 @@ Between the two monitoring sections, you'll be able to gather essential insights
|
||||
|
||||
### Cache node summary
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
|
||||
|
||||
@ -67,7 +67,7 @@ The content types displayed in the chart each have a distinct color and are sort
|
||||
|
||||
## 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 metrics you can access in this section:
|
||||
|
||||
|
||||
@ -31,12 +31,12 @@ These changes affect Linux and Windows host machines.
|
||||
|
||||
### Feature updates
|
||||
|
||||
- **Metrics and charts in Azure portal**: You can now visualize "Outbound egress" and "Volume by Content type" charts for your cache node on Azure portal. You can also create custom monitoring charts for your cache nodes. This capability is under the **Metrics** tab on Azure portal.
|
||||
- **Metrics and charts in Azure portal**: You can now visualize *Outbound egress* and *Volume by Content type* charts for your cache node on Azure portal. You can also create custom monitoring charts for your cache nodes. This capability is under the **Metrics** tab on Azure portal.
|
||||
- **Cache nodes for Windows or Linux host machines**: Cache nodes can now be created and deployed to Windows host machine or Linux host machines by simply choosing the OS when creating cache nodes.
|
||||
- **Ubuntu 22.04 LTS**: Cache nodes can now be deployed on Ubuntu 22.04 LTS.
|
||||
- **Azure CLI support**: Cache nodes can now be created and managed via Azure CLI.
|
||||
- **Proxy**: We added support for unauthenticated proxy and cloud proxy integration.
|
||||
- **Updates**: Your cache nodes are now updated automatically and we also added the capability to set each cache node's update ring to govern the cadence of Micoroft Connected Cache container updates.
|
||||
- **Updates**: Your cache nodes are now updated automatically and we also added the capability to set each cache node's update ring to govern the cadence of Microsoft Connected Cache container updates.
|
||||
|
||||
### Fixes
|
||||
- We fixed various bugs to achieve smoother install experience.
|
||||
|
||||
@ -36,7 +36,7 @@ If you're encountering an error during resource creation, check that you have th
|
||||
|
||||
If you're encountering a validation error, check that you have filled out all required configuration fields.
|
||||
|
||||
If your configuration doesn't appear to be taking effect, check that you have clicked the "Save" button at the top of the configuration page in the Azure portal user interface.
|
||||
If your configuration doesn't appear to be taking effect, check that you have selected the **Save** option at the top of the configuration page in the Azure portal user interface.
|
||||
|
||||
If you have changed the proxy configuration, you will need to re-provision the Connected Cache software on the host machine for the proxy configuration to take effect.
|
||||
|
||||
@ -83,9 +83,9 @@ Once the Connected Cache container is running, a scheduled task is periodically
|
||||
You can use Task Scheduler on the host machine to check the status of this scheduled task.
|
||||
|
||||
1. Open Task Scheduler on the host machine
|
||||
1. Navigate to the Active Tasks section and double-click on "MCC_Monitor_Task"
|
||||
1. Select the scheduled task "MCC_Monitor_Task"
|
||||
1. Select the "Triggers" tab and confirm that the Status is "Enabled"
|
||||
1. Navigate to the Active Tasks section and double-click on **MCC_Monitor_Task**
|
||||
1. Select the scheduled task **MCC_Monitor_Task**
|
||||
1. Select the **Triggers** tab and confirm that the Status is **Enabled**
|
||||
|
||||
## Troubleshooting cache node deployment to Linux host machine
|
||||
|
||||
|
||||
@ -38,7 +38,7 @@ These steps should be taken after deploying Connected Cache software to a [Windo
|
||||
|
||||
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 downloaded 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
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user