diff --git a/windows/deployment/do/images/mcc_ent_publicpreview.png b/windows/deployment/do/images/mcc_ent_publicpreview.png new file mode 100644 index 0000000000..6f6f292d58 Binary files /dev/null and b/windows/deployment/do/images/mcc_ent_publicpreview.png differ diff --git a/windows/deployment/do/mcc-ent-create-resource-and-cache.md b/windows/deployment/do/mcc-ent-create-resource-and-cache.md index 1e356fa5e9..2004d65f59 100644 --- a/windows/deployment/do/mcc-ent-create-resource-and-cache.md +++ b/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. - + 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 --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. - + 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.
+ 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. + +## Next step + +>[!div class="nextstepaction"] +>[Create MCC Azure resources](mcc-ent-create-resource-and-cache.md) \ No newline at end of file diff --git a/windows/deployment/do/mcc-ent-manage-cache-using-CLI.md b/windows/deployment/do/mcc-ent-manage-cache-using-CLI.md index 6316cd5ee0..c48dd5e04b 100644 --- a/windows/deployment/do/mcc-ent-manage-cache-using-CLI.md +++ b/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) diff --git a/windows/deployment/do/mcc-ent-private-preview.md b/windows/deployment/do/mcc-ent-private-preview.md index bf1846c8a2..03c549f395 100644 --- a/windows/deployment/do/mcc-ent-private-preview.md +++ b/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 diff --git a/windows/deployment/do/mcc-ent-support-and-troubleshooting.md b/windows/deployment/do/mcc-ent-support-and-troubleshooting.md index c9e642b42f..4199588658 100644 --- a/windows/deployment/do/mcc-ent-support-and-troubleshooting.md +++ b/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.