mcc-branding

This commit is contained in:
Meghan Stewart 2024-10-24 14:01:45 -07:00
parent 44d613f10c
commit e4ccb2a4c2
4 changed files with 8 additions and 8 deletions

View File

@ -164,7 +164,7 @@ One or more values can be added as either fully qualified domain names (FQDN) or
<!-- DOCacheHost-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
> [!NOTE]
> Clients don't talk to multiple Microsoft Connected Cache servers at the same time. If you configure a list of Connected Cache servers in this policy, the clients will round robin until they successfully connect to an Connected Cache server. The clients have no way to determine if the Connected Cache server has the content or not. If the Connected Cache server doesn't have the content, it caches the content as it is handing the content back to the client.
> Clients don't talk to multiple Microsoft Connected Cache servers at the same time. If you configure a list of Connected Cache servers in this policy, the clients will round robin until they successfully connect to a Connected Cache server. The clients have no way to determine if the Connected Cache server has the content or not. If the Connected Cache server doesn't have the content, it caches the content as it is handing the content back to the client.
<!-- DOCacheHost-Editable-End -->
<!-- DOCacheHost-DFProperties-Begin -->

View File

@ -33,7 +33,7 @@
items:
- name: What is Microsoft Connected Cache?
href: waas-microsoft-connected-cache.md
- name: Connected Cache for Enterprise and Education
- name: Microsoft Connected Cache for Enterprise and Education
items:
- name: Connected Cache for Enterprise and Education Overview
href: mcc-ent-edu-overview.md
@ -45,7 +45,7 @@
href: mcc-enterprise-update-uninstall.md
- name: Appendix
href: mcc-enterprise-appendix.md
- name: Connected Cache for ISPs
- name: Microsoft Connected Cache for ISPs
items:
- name: Connected Cache for ISPs Overview
href: mcc-isp-overview.md

View File

@ -82,7 +82,7 @@ communication operations. The runtime performs several functions:
For more information on Azure IoT Edge, see the [Azure IoT Edge documentation](/azure/iot-edge/about-iot-edge).
## Routing local Windows clients to an Connected Cache
## Routing local Windows clients to a Connected Cache
### Get the IP address of your Connected Cache using ifconfig

View File

@ -173,13 +173,13 @@ If you get the error message "Validation failed" in the Azure portal, it's likel
If you get the error message "Could not create marketplace item" in the Azure portal, use the following steps to troubleshoot:
- Make sure that you've selected **Microsoft Connected Cache** and not *Connected Cache resources* while trying to create an Connected Cache resource.
- Make sure that you've selected **Microsoft Connected Cache** and not *Connected Cache resources* while trying to create a Connected Cache resource.
- Make sure that you're using the same subscription that you provided to Microsoft and you have privileges to create an Azure resource.
- If the issue persists, clear your browser cache and start in a new window.
### Create an Connected Cache node in Azure
### Create a Connected Cache node in Azure
1. After you successfully create the resource, select **Go to resource**.
@ -347,7 +347,7 @@ Before you start, make sure that you have a data drive configured on your server
- If this process is for your *first Connected Cache deployment*, enter `n`.
- If you already have an Connected Cache deployment, you can use an existing IoT Hub from your previous installation. Select `Y` to see your existing IoT Hubs. You can copy and paste the resulting IoT Hub name to continue.
- If you already have a Connected Cache deployment, you can use an existing IoT Hub from your previous installation. Select `Y` to see your existing IoT Hubs. You can copy and paste the resulting IoT Hub name to continue.
:::image type="content" source="./images/mcc-isp-bash-iot-prompt.png" alt-text="Screenshot of the Bash script output with steps for existing IoT Hub." lightbox="./images/mcc-isp-bash-iot-prompt.png":::
@ -550,7 +550,7 @@ sudo ./updatemcc.sh version="msconnectedcacheprod.azurecr.io/mcc/linux/iot/mcc-u
<!-- ### Configure BGP on an Existing Connected Cache
If you have an Connected Cache that's already active and running, follow the steps below to configure BGP.
If you have a Connected Cache that's already active and running, follow the steps below to configure BGP.
1. Run the Update commands as described above.