added support content and other changes

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. Under Cache Node Management, select on Cache Nodes and then on + Create Cache Node.
-  <!--
-    :::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. 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.<br>
+  
   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":::  
@@ -199,12 +195,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/)
-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:
- <!--
-:::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":::
- -->
+
+## Next step
+
+>[!div class="nextstepaction"]
+>[Create MCC Azure resources](mcc-ent-create-resource-and-cache.md)

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
 
-> [!div class="nextstepaction"]
-> [Deploy cache node to Linux host machine](mcc-ent-deploy-to-Linux.md)
-> [Deploy cache node to Windows host machine](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 
+>[!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
-TODO: Add introduction sentence(s)
-[Include a sentence or two to explain only what is needed to complete the procedure.]
-TODO: Add ordered list of procedure steps
+## Troubleshooting cache node issue
+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.
+For detailed instructions on creating MCC resource, see [Create MCC Azure resources](mcc-ent-create-resource-and-cache.md)
 
-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.