Merge pull request #10303 from doshnid/nidos-ent

wait to merge

windows/deployment/do/TOC.yml

@@ -50,7 +50,7 @@
           - name: Deploy MCC to Windows
             href: mcc-ent-deploy-to-windows.md
         - name: Using CLI to create and manage cache nodes
-          href: mcc-ent-manage-cache-using-CLI.md 
+          href: mcc-ent-manage-cache-using-cli.md 
         - name: Verify cache node functionality
           href: mcc-ent-verify-cache-node.md
         - name: Monitor cache node

windows/deployment/do/mcc-ent-create-resource-and-cache.md

@@ -36,9 +36,7 @@ For more information on sizing and OS requirements, see [the prerequisites for u
 -->
 
 1. Select the Microsoft Connected Cache for Enterprise resource. When prompted, choose the subscription, resource group, and location for the resource. Then enter a name for the resource and select Review + Create.
-<!--
+
-    :::image type="content" source="images/mcc-isp-provision-cache-node-numbered.png" alt-text="Screenshot of the Azure portal depicting the cache node configuration page of a cache node. This screenshot shows all of the fields you can choose to configure the cache node." lightbox="./images/mcc-isp-provision-cache-node-numbered.png":::  
--->
 1. After a few moments, you'll see a "Validation successful" message, indicating you can move onto the next step and select Create.
 
 1. The creation of the resource might take a few minutes. After a successful creation, you'll see a Deployment complete page as below. Select Go to resource to create cache nodes.
@@ -79,11 +77,9 @@ az mcc ent resource create --mcc-resource-name <mymccresource> --resource-group
 
 # [Azure portal](#tab/portal)
 
-  1. Open Azure portal and navigate to the Microsoft Connected Cache for Enterprise resource that you created.
+  1. Open Azure portal and navigate to the Microsoft Connected Cache for Enterprise resource that you created.<br>
-  1. Under Cache Node Management, select on Cache Nodes and then on + Create Cache Node.
+  1. Under Cache Node Management, select on Cache Nodes and then on + Create Cache Node.<br>
-  <!--
+  
-    :::image type="content" source="images/mcc-isp-provision-cache-node-numbered.png" alt-text="Screenshot of the Azure portal depicting the cache node configuration page of a cache node. This screenshot shows all of the fields you can choose to configure the cache node." lightbox="./images/mcc-isp-provision-cache-node-numbered.png":::  
-    -->
   1. Provide a name for your cache node and select the host OS you plan to deploy the cache node on and select create. Note, cache node names have to be unique under the Microsoft Connected Cache resource.
   <!--
     :::image type="content" source="images/mcc-isp-provision-cache-node-numbered.png" alt-text="Screenshot of the Azure portal depicting the cache node configuration page of a cache node. This screenshot shows all of the fields you can choose to configure the cache node." lightbox="./images/mcc-isp-provision-cache-node-numbered.png":::  
@@ -130,8 +126,7 @@ Don't forget to select save after adding configuration information.
 
 # [Azure CLI](#tab/cli)
 
-# [Linux host OS](#tab/cli/linux)
+### Configure Linux MCC
-
 Use the following command to configure cache node for deployment to a **Linux** host machine.
 
 Replace the following placeholders with your own information:
@@ -163,8 +158,7 @@ az mcc ent node update --cache-node-name <mycachenode> --mcc-resource-name <mymc
 <br>
 <br>
 
-# [Windows host OS](#tab/cli/windows)
+### Configure Windows MCC
-
 Use the following command to configure cache node for deployment to a **Windows** host machine.
 
 Replace the following placeholders with your own information:
@@ -199,12 +193,18 @@ az mcc ent node update --cache-node-name <mycachenode> --mcc-resource-name <mymc
 ## Next step
 
 ### [Azure portal](#tab/portal)
-To deploy the cache node to a **Windows** host machine, see [Deploy cache node to Windows](mcc-ent-deploy-to-windows.md)
+To deploy the cache node to a **Windows** host machine, see 
+>[!div class="nextstepaction"]
+>[Deploy cache node to Windows](mcc-ent-deploy-to-windows.md)
 
-To deploy the cache node to a **Linux** host machine, see [Deploy cache node to Linux](mcc-ent-deploy-to-linux.md)
+To deploy the cache node to a **Linux** host machine, see 
+>[!div class="nextstepaction"]
+>[Deploy cache node to Linux](mcc-ent-deploy-to-linux.md)
 
-### [Azure CLI](#tab/cli/)
+### [Azure CLI](#tab/cli)
-To deploy cache nodes using Azure CLI, see [Manage cache nodes using CLI](mcc-ent-manage-cache-using-CLI.md)
+To deploy cache nodes using Azure CLI, see 
+>[!div class="nextstepaction"]
+>[Manage cache nodes using CLI](mcc-ent-manage-cache-using-CLI.md)
 
 ---
 <br>

windows/deployment/do/mcc-ent-edu-overview.md

@@ -75,6 +75,11 @@ See [Host machine requirements](mcc-ent-prerequisites.md) for complete details.
 
 ## How it works
 
+The following diagram displays an overview of how MCC functions:<br>
+
+:::image type="content" source="./images/mcc_ent_publicpreview.png" alt-text="Diagram displaying the components of MCC." lightbox="./images/mcc_ent_publicpreview.png":::
+
+
 1. The Azure management portal for Microsoft Connected Cache or CLI are used to create cache nodes, configure deployments, including unauthenticated proxy settings.
 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.
@@ -83,7 +88,8 @@ See [Host machine requirements](mcc-ent-prerequisites.md) for complete details.
 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.
 Customers can view data regarding Microsoft Connected Cache downloads on management portal and Windows Update for Business reports
 
-The following diagram displays an overview of how MCC functions:
+
- <!--
+## Next step
-:::image type="content" source="./images/waas-mcc-diag-overview.png" alt-text="Diagram displaying the components of MCC." lightbox="./images/waas-mcc-diag-overview.png":::
+
- -->
+>[!div class="nextstepaction"]
+>[Create MCC Azure resources](mcc-ent-create-resource-and-cache.md)

windows/deployment/do/mcc-ent-faq.yml

@@ -25,3 +25,48 @@ sections:
     questions:
       - question: Is this product a free service?
         answer: Yes. Microsoft Connected Cache is a free service.  
+      - question: Is there a nondisclosure agreement to sign?
+        answer: No, a nondisclosure agreement isn't required.
+      - question: What are the prerequisites and hardware requirements?
+        answer:  | 
+         - [Azure pay-as-you-go subscription](https://azure.microsoft.com/offers/ms-azr-0003p/).
+         - [Hardware to host Microsoft Connected Cache](mcc-ent-edu-overview.md)
+         - [Host machine requirements](mcc-ent-prerequisites.md)
+      - question: What host OS do I need to deploy MCC?
+        answer: You can use Linux or Windows OS. Depending on the OS, the provisioning script and certain provisioning steps are different. 
+      - question: What content is cached by Microsoft Connected Cache?
+        answer: For more information about content cached, see [Delivery Optimization and Microsoft Connected Cache content endpoints](delivery-optimization-endpoints.md).
+      - question: Do I need to provide hardware BareMetal server or a virtual machine (VM)?
+        answer: Microsoft Connected Cache is a software-only caching solution and requires you to provide your own server to host the software.   
+      - question: Can we use hard drives instead of SSDs?
+        answer: We highly recommend using SSDs as Microsoft Connected Cache is a read intensive application. We also recommend using multiple drives to improve performance.
+      - question: Where should we install Microsoft Connected Cache?
+        answer: You are in control of your hardware and you can pick the location based on your traffic and end clients. You can choose the location where you have your routers or where you have dense traffic or any other parameters.   
+      - question: How can I set up a gMSA account?
+        answer: For more information about gMSA accounts, see [Learn how to provision a Group Managed Service Account on a Domain Controller](/windows-server/identity/ad-ds/manage/group-managed-service-accounts/group-managed-service-accounts/getting-started-with-group-managed-service-accounts#create-group-managed-service-accounts). Make sure that your gMSA has been granted permissions to "Log on as batch job" within the host machine's [local security policies](/previous-versions/windows/it-pro/windows-10/security/threat-protection/security-policy-settings/how-to-configure-security-policy-settings).
+      - question: How can I set up a local account?
+        answer: For more information, see [Learn how to provision a Local User Account](https://support.microsoft.com/topic/104dc19f-6430-4b49-6a2b-e4dbd1dcdf32). Make sure that your gMSA has been granted permissions to "Log on as batch job" within the host machine's [local security policies](/previous-versions/windows/it-pro/windows-10/security/threat-protection/security-policy-settings/how-to-configure-security-policy-settings).
+      - 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: Does Microsoft Connected Cache support Xbox or Microsoft Teams content?
+        answer: Currently, Microsoft Connected Cache doesn't support Xbox or Microsoft Teams content. However, supporting Xbox content is of high priority, and we expect this feature soon. We'll let you know as soon as it becomes available!
+      - 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.
+      - 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 will reside 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?
+        answer: No. It's important to keep the Microsoft Connected Cache software up to date, especially when it comes to security issues. Microsoft validates updates prior to releasing Enterprises Connected Cache updates and will only release updates when it's necessary to keep customers secure or to ensure the continued successful operation of Connected Cache nodes for customers.  
+      - question: How do I set up CLI?
+        answer: For more information, see [How to install the Azure CLI](/cli/azure/install-azure-cli).
+      - question: How do I install MCC extension?
+        answer: For more information, see [Install the Microsoft Connected Cache extension](mcc-ent-install-extension.md).
+      - question: What do I do if I have to set up or change existing proxy?
+        answer: You can enable proxy and provide proxy information on Azure portal or use the CLI. Don't forget to rerun the provisioning script after making any proxy changes. For more information, see [Set up or change existing proxy](mcc-ent-proxy.md).
+      - question: How do we set up Microsoft Connected Cache if we support multiple countries or regions?
+        answer: Microsoft Connected Cache isn't a service that has dependency on a specific Azure region, and there isn't personal or organizational identifiable information stored in the resource that necessitates data residency. The three regions that the Connected Cache resource can be deployed to are (Europe) North Europe, (Asia Pacific) Korea Central, and (US) West US.
+      - question: Should I use a gMSA, local user, or domain account to deploy Microsoft Connected Cache to Windows?
+        answer: There are pros and cons to the account options available to customers. We anticipate that security and manageability are top priories for customers. Microsoft provides guidance on both Active Directory and Microsoft Entra-based service accounts ([Introduction to Active Directory service accounts - Choose the right type of service account](/entra/architecture/service-accounts-on-premises#types-of-on-premises-service-accounts)) and user-based service accounts ([Secure user-based service accounts in Active Directory)](/entra/architecture/service-accounts-user-on-premises#assess-on-premises-user-account-security)).
+      - question: Does the user have to be logged using the account that installed Microsoft Connected Cache on Windows or Linux?
+        answer: No. As part of the installation on Windows a scheduled task is created using the account used to install Connected Cache. Regardless of which user is logged in or not logged in, the schedule task remains running. On Linux Connected Cache is installed by the user and remains running regardless of which user is logged in to the OS.
+      - question: What do I do if I need more support and have more questions even after reading this FAQ page?
+        answer: For further support for Microsoft Connected Cache, see [Troubleshooting issues for Microsoft Connected Cache for Enterprise and Education](mcc-ent-support-and-troubleshooting.md). If you still need more support, you can contact customer support.

windows/deployment/do/mcc-ent-manage-cache-using-cli.md

@@ -135,7 +135,10 @@ To get the relevant information for provisioning script, use `az mcc ent node ge
 az mcc ent node get-provisioning-details --cache-node-name mycachenode --mcc-resource-name mymccresource --resource-group myrg
 ```
 
-Save the resulting values for cacheNodeId, customerKey, mccResourceId, registrationKey. These GUIDs are needed to create the provisioning script.
+>[!IMPORTANT]
+>* Save the resulting values for cacheNodeId, customerKey, mccResourceId, registrationKey. These GUIDs are needed to create the provisioning script.
+>* In the output look for cacheNodeState. If **cacheNodeState = Not Provisioned**, you can continue with cache node provisioning.
+>* If **cacheNodeState = Not Configured**, then the cache node has not been configured. Please configure the cache node before provisioning.
 
 ### Example script:
 
@@ -197,6 +200,10 @@ for ($cacheNodeNumber = 1; $cacheNodeNumber -le $cacheNodesToCreate; $cacheNodeN
 
 ## Next step
 
+To deploy the cache node to a **Windows** host machine, see 
 >[!div class="nextstepaction"]
-> [Deploy cache node to Linux host machine](mcc-ent-deploy-to-Linux.md)
+>[Deploy cache node to Windows](mcc-ent-deploy-to-windows.md)
-> [Deploy cache node to Windows host machine](mcc-ent-deploy-to-Windows.md)
+
+To deploy the cache node to a **Linux** host machine, see 
+>[!div class="nextstepaction"]
+>[Deploy cache node to Linux](mcc-ent-deploy-to-linux.md)

windows/deployment/do/mcc-ent-private-preview.md

@@ -18,7 +18,7 @@ If you participated in the MCC early preview, thank you for your collaboration a
 
 To continue using MCC, we strongly recommend that you upgrade your existing cache nodes to the Public Preview release. Cache nodes created and deployed during early preview should still function but can no longer be managed or monitored remotely via the MCC Azure service.
 
-As such, we strongly recommend you [recreate your existing cache nodes in Azure](mcc-ent-create-resource-and-cache.md) and then [redeploy the MCC caching software to your host machines](mcc-ent-deploy-to-windows.md) using the latest OS-specific installer. You don't need to re-create your MCC Azure resource.
+As such, we strongly recommend you [recreate your existing resources in Azure](mcc-ent-create-resource-and-cache.md) and then [redeploy the MCC caching software to your host machines](mcc-ent-deploy-to-windows.md) using the latest OS-specific installer.
 
 ## Next step
 

windows/deployment/do/mcc-ent-support-and-troubleshooting.md

@@ -15,9 +15,6 @@ ms.date: 09/27/2024
 ---
 
 
-
-
-
 # Troubleshoot Microsoft Connected Cache for Enterprise and Education (MCC)
 
 This article contains instructions on how to troubleshoot different issues you may encounter while using MCC. These issues are categorized by the task in which they may be encountered. For example, this next section covers troubleshooting [MCC Azure resource creation](mcc-ent-create-resource-and-cache.md).
@@ -31,14 +28,10 @@ This article contains instructions on how to troubleshoot different issues you m
 
 MCC Azure resource creation can be initiated using either the Azure portal or the Azure CLI command set. If you're encountering an error during resource creation, check that you have the necessary RPaaS permissions and have filled out all required fields.
 
-## Troubleshooting cache node creation
+## Troubleshooting cache node issue
-TODO: Add introduction sentence(s)
+If you are facing issues with your cache node, it could be due to cache node being on the early preview version of MCC. Cache nodes belonging to early preview version will be under MCC resource that will have 'early preview' in its name. Please delete these cache nodes and associated MCC resource and create a new MCC resource on the new version.
-[Include a sentence or two to explain only what is needed to complete the procedure.]
+For detailed instructions on creating MCC resource, see [Create MCC Azure resources](mcc-ent-create-resource-and-cache.md)
-TODO: Add ordered list of procedure steps
 
-1. Step 1
-1. Step 2
-1. Step 3
 
 ## Troubleshooting cache node deployment
 TODO: Add introduction sentence(s)
@@ -66,6 +59,15 @@ Optional: You have two options for manually curated links in this pattern: Next
 
 -->
 
+## Diagnose and Solve
+
+If this article isn't resolving the issue you're facing with your cache node, you can use the **Diagnose and solve problems** functionality within your MCC resource to continue troubleshooting. **Diagnose and solve problems** contains solutions to most common problems that users might face as they onboard.
+
+You can find **Diagnose and solve problems** on the left pane within your MCC resource.
+
+Within **Diagnose and solve problems**, select **Troubleshoot** under the type of problem you're facing and follow the prompts that narrow down the solution to the issue.
+
+
 ## Filing a support request
 
 TODO: Add steps for filling out a CSS ticket.

windows/deployment/do/waas-microsoft-connected-cache.md

@@ -24,7 +24,7 @@ ms.date: 05/23/2024
 Microsoft Connected Cache is a software-only caching solution that delivers Microsoft content. Microsoft Connected Cache has two main offerings:
 
 - Microsoft Connected Cache for Internet Service Providers
-- Microsoft Connected Cache for Enterprise and Education (early preview)
+- Microsoft Connected Cache for Enterprise and Education (preview)
 
 Both products are created and managed in the cloud portal.
 
@@ -35,14 +35,14 @@ Both products are created and managed in the cloud portal.
 
 Microsoft Connected Cache (MCC) for Internet Service Providers is currently in preview. MCC can be deployed to as many bare-metal servers or VMs as needed and is managed from a cloud portal. When deployed, MCC can help to reduce your network bandwidth usage for Microsoft software content and updates. Cache nodes are created in the cloud portal and are configured to deliver traffic to customers by manual CIDR or BGP routing. Learn more at [Microsoft Connected Cache for ISPs Overview](mcc-isp-overview.md).
 
-## Microsoft Connected Cache for Enterprise and Education (early preview)
+## Microsoft Connected Cache for Enterprise and Education (preview)
 
 > [!NOTE]
-> As we near the release of public preview, we have paused onboarding. Please continue to submit the form to express interest so we can follow up with you once public preview of Microsoft Connected Cache for Enteprise and Education is available. To register your interest, fill out the form located at [https://aka.ms/MSConnectedCacheSignup](https://aka.ms/MSConnectedCacheSignup).
+> Microsoft Connected Cache (MCC) for Enterprise and Education is now in public preview. To get started, follow the instructions in the [Create Microsoft Connected Cache Azure resource and cache nodes](mcc-ent-create-resource-and-cache.md) article.
 
-Microsoft Connected Cache (MCC) for Enterprise and Education (early preview) is a software-only caching solution that delivers Microsoft content within Enterprise and Education networks. MCC can be deployed to as many Windows servers, bare-metal servers, or VMs as needed, and is managed from a cloud portal. Cache nodes are created in the cloud portal and are configured by applying the client policy using management tools such as Intune. Learn more at [Microsoft Connected Cache for Enterprise and Education Overview](mcc-ent-edu-overview.md).
+Microsoft Connected Cache (MCC) for Enterprise and Education is a software-only caching solution that delivers Microsoft content within Enterprise and Education networks. MCC can be deployed to as many Windows servers, bare-metal servers, or VMs as needed, and is managed from a cloud portal. Cache nodes are created in the cloud portal and are configured by applying the client policy using management tools such as Intune. Learn more at [Microsoft Connected Cache for Enterprise and Education Overview](mcc-ent-edu-overview.md).
 
-Microsoft Connected Cache (MCC) for Enterprise and Education (early preview) is a standalone cache for customers moving towards modern management and away from Configuration Manager distribution points. For Microsoft Connected Cache in Configuration Manager (generally available starting Configuration Manager version 2111), see [Microsoft Connected Cache in Configuration Manager](/mem/configmgr/core/plan-design/hierarchy/microsoft-connected-cache)
+Microsoft Connected Cache (MCC) for Enterprise and Education (preview) is a standalone cache for customers moving towards modern management and away from Configuration Manager distribution points. For Microsoft Connected Cache in Configuration Manager (generally available starting Configuration Manager version 2111), see [Microsoft Connected Cache in Configuration Manager](/mem/configmgr/core/plan-design/hierarchy/microsoft-connected-cache)
 
 ## Next steps