From b35d59760cc1cc0c73fccf6a60c12d7f17ad22c2 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Thu, 24 Aug 2023 14:52:40 -0700 Subject: [PATCH 1/3] pull-8762-mainchange --- windows/deployment/do/TOC.yml | 4 +--- windows/deployment/do/mcc-enterprise-deploy.md | 6 +++--- 2 files changed, 4 insertions(+), 6 deletions(-) diff --git a/windows/deployment/do/TOC.yml b/windows/deployment/do/TOC.yml index 1697bfc141..136f9e7998 100644 --- a/windows/deployment/do/TOC.yml +++ b/windows/deployment/do/TOC.yml @@ -38,13 +38,11 @@ - name: Requirements href: mcc-enterprise-prerequisites.md - name: Deploy Microsoft Connected Cache - href: mcc-enterprise-portal-deploy.md + href: mcc-enterprise-deploy.md - name: Update or uninstall MCC href: mcc-enterprise-update-uninstall.md - name: Appendix href: mcc-enterprise-appendix.md - - name: MCC for Enterprise and Education (early preview) - href: mcc-enterprise-deploy.md - name: MCC for ISPs items: - name: MCC for ISPs Overview diff --git a/windows/deployment/do/mcc-enterprise-deploy.md b/windows/deployment/do/mcc-enterprise-deploy.md index cdcf5c1b5d..53d2940cc1 100644 --- a/windows/deployment/do/mcc-enterprise-deploy.md +++ b/windows/deployment/do/mcc-enterprise-deploy.md @@ -1,5 +1,5 @@ --- -title: MCC for Enterprise and Education (early preview) +title: Deploying your cache node manager: aaroncz description: How to deploy a Microsoft Connected Cache (MCC) for Enterprise and Education cache node ms.prod: windows-client @@ -12,7 +12,7 @@ ms.technology: itpro-updates ms.collection: tier3 --- -# Deploying your enterprise cache node +# Deploying your cache node **Applies to** @@ -130,7 +130,7 @@ Installing MCC on your Windows device is a simple process. A PowerShell script p - Downloads, installs, and deploys EFLOW - Enables Microsoft Update so EFLOW can stay up to date - Creates a virtual machine -- Enables the firewall and opens ports 80 for inbound and outbound traffic. Port 80 is used by MCC. +- Enables the firewall and opens ports 80 and 22 for inbound and outbound traffic. Port 80 is used by MCC, and port 22 is used for SSH communications. - Configures Connected Cache tuning settings. - Creates the necessary *FREE* Azure resource - IoT Hub/IoT Edge. - Deploys the MCC container to server. From a9b6ef6df8465e13db4ca0ad33a5fc9e81fb954e Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Thu, 24 Aug 2023 14:57:08 -0700 Subject: [PATCH 2/3] delete cmm-enterprise-portal-deploy --- .../do/mcc-enterprise-portal-deploy.md | 145 ------------------ 1 file changed, 145 deletions(-) delete mode 100644 windows/deployment/do/mcc-enterprise-portal-deploy.md diff --git a/windows/deployment/do/mcc-enterprise-portal-deploy.md b/windows/deployment/do/mcc-enterprise-portal-deploy.md deleted file mode 100644 index eea23e3bad..0000000000 --- a/windows/deployment/do/mcc-enterprise-portal-deploy.md +++ /dev/null @@ -1,145 +0,0 @@ ---- -title: Deploying your cache node -manager: aaroncz -description: How to deploy Microsoft Connected Cache (MCC) for Enterprise and Education cache node -ms.prod: windows-client -ms.author: carmenf -author: cmknox -ms.reviewer: mstewart -ms.topic: article -ms.date: 12/31/2017 -ms.technology: itpro-updates -ms.collection: tier3 ---- - -# Deploying your cache node - -**Applies to** - -- Windows 10 -- Windows 11 - -## Create the Microsoft Connected Cache resource - -1. Navigate to Azure portal by using the [following link](https://aka.ms/mcc-enterprise-preview): - > [!IMPORTANT] - > You must access Azure portal using this link (https://aka.ms/mcc-enterprise-preview) in order to find the correct Microsoft Connected Cache resource. - - ![Screenshot of Azure portal "Create a resource" page, where you search for the Microsoft Connected Cache resource](images/ent-mcc-portal-create.png) - -1. In the search bar by **Get Started**, search for `Microsoft Connected Cache for Enterprise`. - ![Screenshot of Azure portal after searching for the Microsoft Connected Cache resource](images/ent-mcc-portal-resource.png) -1. Select **Create** to create your Microsoft Connected Cache resource. When prompted, choose the subscription, resource group, and location of your cache node. Also, enter a name for your cache node. -1. The creation of the cache node may take a few minutes. After a successful creation, you'll see a “Deployment complete” page as below. Select **Go to resource**. -![Screenshot of Azure portal after the deployment is complete](images/ent-mcc-deployment-complete.png) - -## Create, provision, and deploy the cache node in Azure portal - -To create, provision, and deploy the cache node in Azure portal, follow these steps: -1. Open Azure portal and navigate to the Microsoft Connected Cache for Enterprise (preview) resource. -1. Navigate to **Settings** > **Cache nodes** and select **Create Cache Node**. -1. Provide a name for your cache node and select **Create** to create your cache node. -1. You may need to refresh to see the cache node. Select the cache node to configure it. -1. Fill out the Basics and Storage fields. Enter the cache drive size in GB - this has a minimum size of 50 GB. - - ![Screenshot of Azure portal on the Provisioning page, where the user can configure their cache node.](images/ent-mcc-provisioning.png) -Once complete, select **Save** at the top of the page and select **Provision server**. -1. To deploy your cache node, download the installer by selecting **Download provisioning package**. -1. Run the provided provisioning script - note that this is unique to each cache node. - -## Verify proper functioning MCC server - -#### Verify client side - -Connect to the EFLOW VM and check if MCC is properly running: - -1. Open PowerShell as an Administrator. -2. Enter the following commands: - - ```powershell - Connect-EflowVm - sudo -s - iotedge list - ``` - - :::image type="content" source="./images/ent-mcc-connect-eflowvm.png" alt-text="Screenshot of running connect-EflowVm, sudo -s, and iotedge list from PowerShell." lightbox="./images/ent-mcc-connect-eflowvm.png"::: - -You should see MCC, edgeAgent, and edgeHub running. If you see edgeAgent or edgeHub but not MCC, try this command in a few minutes. The MCC container can take a few minutes to deploy. - -#### Verify server side - -For a validation of properly functioning MCC, execute the following command in the EFLOW VM or any device in the network. Replace with the IP address of the cache server. - -```powershell -wget [http:///mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com] -``` - -A successful test result will display a status code of 200 along with additional information. - -:::image type="content" source="./images/ent-mcc-verify-server-ssh.png" alt-text="Screenshot of a successful wget with an SSH client." lightbox="./images/ent-mcc-verify-server-ssh.png"::: - - :::image type="content" source="./images/ent-mcc-verify-server-powershell.png" alt-text="Screenshot of a successful wget using PowerShell." lightbox="./images/ent-mcc-verify-server-powershell.png"::: - -Similarly, enter the following URL from a browser in the network: - -`http:///mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com` - -If the test fails, see the [common issues](#common-issues) section for more information. - -### Monitoring your metrics - -To view the metrics associated with your cache nodes, navigate to the **Overview** > **Monitoring** tab within the Azure portal. - -:::image type="content" source="./images/mcc-isp-metrics.png" alt-text="Screenshot of the Azure portal displaying the metrics view in the Overview tab."::: - -You can choose to monitor the health and performance of all cache nodes or one at a time by using the dropdown menu. The **Egress bits per second** graph shows your inbound and outbound traffic of your cache nodes over time. You can change the time range (1 hour, 12 hours, 1 day, 7 days, 14 days, and 30 days) by selecting the time range of choice on the top bar. - -If you're unable to view metrics for your cache node, it may be that your cache node is unhealthy, inactive, or hasn't been fully configured. - - -### Intune (or other management software) configuration for MCC - -For an [Intune](/mem/intune/) deployment, create a **Configuration Profile** and include the Cache Host eFlow IP Address or FQDN: - -:::image type="content" source="./images/ent-mcc-intune-do.png" alt-text="Screenshot of Intune showing the Delivery Optimization cache server host names."::: - -## Common Issues - -#### PowerShell issues - -If you're seeing errors similar to this error: `The term Get- isn't recognized as the name of a cmdlet, function, script file, or operable program.` - -1. Ensure you're running Windows PowerShell version 5.x. - -1. Run \$PSVersionTable and ensure you're running version 5.x and *not version 6 or 7*. - -1. Ensure you have Hyper-V enabled: - - **Windows 10:** [Enable Hyper-V on Windows 10](/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v) - - **Windows Server:** [Install the Hyper-V role on Windows Server](/windows-server/virtualization/hyper-v/get-started/install-the-hyper-v-role-on-windows-server) - -#### Verify Running MCC Container - -Connect to the Connected Cache server and check the list of running IoT Edge modules using the following commands: - -```bash -Connect-EflowVm -sudo iotedge list -``` - -:::image type="content" source="./images/ent-mcc-iotedge-list.png" alt-text="Screenshot of the iotedge list command." lightbox="./images/ent-mcc-iotedge-list.png"::: - -If edgeAgent and edgeHub containers are listed, but not "MCC", you may view the status of the IoT Edge security manager by using the command: - -```bash -sudo journalctl -u iotedge -f -``` - -This command will provide the current status of the starting, stopping of a container, or the container pull and start. - -:::image type="content" source="./images/ent-mcc-journalctl.png" alt-text="Screenshot of the output from journalctl -u iotedge -f." lightbox="./images/ent-mcc-journalctl.png"::: - - -> [!NOTE] -> You should consult the IoT Edge troubleshooting guide ([Common issues and resolutions for Azure IoT Edge](/azure/iot-edge/troubleshoot)) for any issues you may encounter configuring IoT Edge, but we've listed a few issues that we encountered during our internal validation. From 0138693df014279798d904b7921be742dcfe2118 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Thu, 24 Aug 2023 15:00:03 -0700 Subject: [PATCH 3/3] temp redir of mcc-enterprise-portal-deploy to mcc-enterprise-deploy --- .openpublishing.redirection.windows-deployment.json | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.openpublishing.redirection.windows-deployment.json b/.openpublishing.redirection.windows-deployment.json index 49fd3e464e..06fc754819 100644 --- a/.openpublishing.redirection.windows-deployment.json +++ b/.openpublishing.redirection.windows-deployment.json @@ -750,6 +750,11 @@ "redirect_url": "/windows/deployment/windows-10-subscription-activation", "redirect_document_id": false }, + { + "source_path": "windows/deployment/do/mcc-enterprise-portal-deploy.md", + "redirect_url": "/windows/deployment/do/mcc-enterprise-deploy", + "redirect_document_id": false + }, { "source_path": "windows/deployment/windows-autopatch/deploy/index.md", "redirect_url": "/windows/deployment/windows-autopatch/deploy/windows-autopatch-admin-contacts",