mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-14 14:27:22 +00:00
add doc changes for the private preview
This commit is contained in:
parent
9b0507a9a7
commit
2c722dbbdd
@ -157,9 +157,7 @@ Installing MCC on your Windows device is a simple process. A PowerShell script p
|
||||
>
|
||||
> Don't use PowerShell ISE, PowerShell 6.x, or PowerShell 7.x. Only Windows PowerShell version 5.x is supported.
|
||||
|
||||
#### If you're installing MCC on a local virtual machine
|
||||
|
||||
1. Turn the virtual machine **off** while you enable nested virtualization and MAC spoofing.
|
||||
1. **If you're installing MCC on a local virtual machine**, turn the virtual machine **off** while you enable nested virtualization and MAC spoofing.
|
||||
1. Enable nested virtualization:
|
||||
|
||||
```powershell
|
||||
@ -229,7 +227,7 @@ Installing MCC on your Windows device is a simple process. A PowerShell script p
|
||||
|
||||
1. Your MCC deployment is now complete.
|
||||
|
||||
1. If you don't see any errors, continue to the next section to validate your MCC deployment.
|
||||
1. If you don't see any errors, continue to the next section to validate your MCC deployment. Your VM will not appear in Hyper-V Manager as it is an EFLOW VM.
|
||||
1. After validating your MCC is properly functional, review your management solution documentation, such as [Intune](/mem/intune/configuration/delivery-optimization-windows), to set the cache host policy to the IP address of your MCC.
|
||||
1. If you had errors during your deployment, see the [Common Issues](#common-issues) section in this article.
|
||||
|
||||
|
@ -98,6 +98,8 @@ There are five IDs that the device provisioning script takes as input in order t
|
||||
| Customer key | The unique alphanumeric ID that provides secure authentication of the cache node to Delivery Optimization services. |
|
||||
| Registration key | Single use device registration key used by Microsoft Delivery Optimization services. |
|
||||
|
||||
#### Provision your server
|
||||
|
||||
:::image type="content" source="images/mcc-isp-deploy-cache-node-numbered.png" alt-text="Screenshot of the server provisioning tab within cache node configuration in Azure portal.":::
|
||||
|
||||
1. After completing cache node provisioning, navigate to the **Server provisioning** tab. Select **Download provisioning package** to download the installation package to your server.
|
||||
|
@ -61,7 +61,9 @@ The following steps describe how MCC is provisioned and used:
|
||||
|
||||
## ISP requirements for MCC
|
||||
|
||||
### Azure subscription
|
||||
Microsoft Connected Cache for Internet Service Providers is now in Public Preview! To get started, visit [Azure portal](https://www.portal.azure.com) to sign up for Microsoft Connected Cache for Internet Service Providers. Please see [Operator sign up and service onboarding for Microsoft Connected Cache](mcc-isp-signup.md) for more information on the requirements for sign up and onboarding.
|
||||
|
||||
<!-- ### Azure subscription
|
||||
|
||||
The MCC management portal is hosted within Azure. It's used to create the Connected Cache Azure resource and IoT Hub resource. Both are *free* services.
|
||||
|
||||
@ -98,9 +100,9 @@ The MCC module is optimized for Ubuntu 20.04 LTS. Install Ubuntu 20.04 LTS on a
|
||||
| NIC | 10 Gbps| at least 10 Gbps |
|
||||
| Disk | SSD </br>1 drive </br>2 TB each |SSD </br>2-4 drives </br>at least 2 TB each |
|
||||
| Memory | 8 GB | 32 GB or greater |
|
||||
| Cores | 4 | 8 or more |
|
||||
| Cores | 4 | 8 or more | -->
|
||||
|
||||
## Steps to deploy MCC
|
||||
<!-- ## Steps to deploy MCC
|
||||
|
||||
To deploy MCC:
|
||||
|
||||
@ -258,9 +260,9 @@ To modify the configuration for existing MCC nodes in the portal, select the cac
|
||||
|
||||
:::image type="content" source="./images/mcc-isp-node-configuration.png" alt-text="Screenshot of the Cache Node Configuration page, highlighting editable fields.":::
|
||||
|
||||
To delete a cache node, select it in the cache nodes list, and then select **Delete** in the toolbar. If you delete a cache node, there's no way to recover it or any of the information related to the cache node.
|
||||
To delete a cache node, select it in the cache nodes list, and then select **Delete** in the toolbar. If you delete a cache node, there's no way to recover it or any of the information related to the cache node. -->
|
||||
|
||||
## Install MCC
|
||||
<!-- ## Install MCC
|
||||
|
||||
To install MCC on your physical server or VM, you use a Bash script installer, which runs the following tasks:
|
||||
|
||||
@ -393,7 +395,7 @@ Before you start, make sure that you have a data drive configured on your server
|
||||
|
||||
- Inspect the installer logs, which are in the following path: `/etc/mccresourcecreation/`
|
||||
|
||||
- For more information, see [Troubleshoot your IoT Edge device](/azure/iot-edge/troubleshoot).
|
||||
- For more information, see [Troubleshoot your IoT Edge device](/azure/iot-edge/troubleshoot). -->
|
||||
|
||||
## Verify properly functioning MCC server
|
||||
|
||||
@ -523,7 +525,7 @@ To run the script:
|
||||
|
||||
1. [Email the MCC team](mailto:msconnectedcache@microsoft.com?subject=Debugging%20Support%20Request%20for%20MCC) and attach this tar file, asking for debugging support. Screenshots of the error along with any other warnings you saw will be helpful during the debugging process. -->
|
||||
|
||||
## Updating your MCC
|
||||
<!-- ## Updating your MCC
|
||||
|
||||
Throughout the early preview phase, Microsoft will release security and feature updates for MCC. Follow these steps to update your MCC.
|
||||
|
||||
@ -539,7 +541,7 @@ For example:
|
||||
|
||||
```bash
|
||||
sudo ./updatemcc.sh version="msconnectedcacheprod.azurecr.io/mcc/linux/iot/mcc-ubuntu-iot-amd64:1.2.1.981" tenantid="799a999aa-99a1-99aa-99aa-9a9aa099db99" customerid="99a999aa-99a1-99aa-99aa-9aaa9aaa0saa" cachenodeid=" aa99aaaa-999a-9aas-99aa99daaa99 " customerkey="a99d999a-aaaa-aa99-0999aaaa99aa"
|
||||
```
|
||||
``` -->
|
||||
|
||||
### Configure BGP on an Existing MCC
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user