From bcf9e0a97559001a9e47e414aad4ed3b202826ca Mon Sep 17 00:00:00 2001 From: Vinay Pamnani <37223378+vinaypamnani-msft@users.noreply.github.com> Date: Mon, 28 Oct 2024 10:14:10 -0600 Subject: [PATCH 1/5] Implement public PRs for App Control --- .../app-control-for-business/appcontrol.md | 4 ++-- .../deployment/deploy-appcontrol-policies-with-script.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/security/application-security/application-control/app-control-for-business/appcontrol.md b/windows/security/application-security/application-control/app-control-for-business/appcontrol.md index 6c4ee67b41..51665939c7 100644 --- a/windows/security/application-security/application-control/app-control-for-business/appcontrol.md +++ b/windows/security/application-security/application-control/app-control-for-business/appcontrol.md @@ -4,7 +4,7 @@ description: Application Control restricts which applications users are allowed ms.localizationpriority: medium ms.collection: - tier3 -ms.date: 09/11/2024 +ms.date: 10/25/2024 ms.topic: overview --- @@ -32,7 +32,7 @@ Windows 10 and Windows 11 include two technologies that can be used for applicat Starting in Windows 11 version 22H2, [Smart App Control](https://support.microsoft.com/topic/what-is-smart-app-control-285ea03d-fa88-4d56-882e-6698afdb7003) provides application control for consumers. Smart App Control is based on App Control. App control enables enterprise customers to create a policy that offers the same security and compatibility as Smart App Control with the capability to customize policeis to run line-of-business (LOB) apps. To make it easier to implement policy, an [example policy](design/example-appcontrol-base-policies.md) is provided. The example policy includes **Enabled:Conditional Windows Lockdown Policy** option that isn't supported for App Control enterprise policies. This rule must be removed before you use the example policy. To use this example policy as a starting point for creating your own policy, see [Create a custom base policy using an example App Control base policy](design/create-appcontrol-policy-for-lightly-managed-devices.md#create-a-custom-base-policy-using-an-example-app-control-base-policy). -Smart App Control is only available on clean installation of Windows 11 version 22H2 or later, and starts in evaluation mode. Smart App Control is automatically turned off for enterprise managed devices unless the user has turned it on first. To turn off Smart App Control across your organization's endpoints, you can set the **VerifiedAndReputablePolicyState** (DWORD) registry value under `HKLM\SYSTEM\CurrentControlSet\Control\CI\Policy` as shown in the following table. After you change the registry value, you must either restart the device or use [CiTool.exe -r](operations/citool-commands.md#refresh-the-app-control-policies-on-the-system) for the change to take effect. +Smart App Control is only available on clean installation of Windows 11 version 22H2 or later, and starts in evaluation mode. Smart App Control is automatically turned off for enterprise managed devices unless the user has turned it on first. To turn off Smart App Control across your organization's endpoints, you can set the **VerifiedAndReputablePolicyState** (DWORD) registry value under `HKLM\SYSTEM\CurrentControlSet\Control\CI\Policy` as shown in the following table. After you change the registry value, you must use [CiTool.exe -r](operations/citool-commands.md#refresh-the-app-control-policies-on-the-system) for the change to take effect. | Value | Description | |-------|-------------| diff --git a/windows/security/application-security/application-control/app-control-for-business/deployment/deploy-appcontrol-policies-with-script.md b/windows/security/application-security/application-control/app-control-for-business/deployment/deploy-appcontrol-policies-with-script.md index 8de7b6d981..2d47be74a6 100644 --- a/windows/security/application-security/application-control/app-control-for-business/deployment/deploy-appcontrol-policies-with-script.md +++ b/windows/security/application-security/application-control/app-control-for-business/deployment/deploy-appcontrol-policies-with-script.md @@ -22,7 +22,7 @@ You should now have one or more App Control policies converted into binary form. ## Deploying policies for Windows 11 22H2 and above, and Windows Server 2025 and above -You can use the inbox [CiTool](../operations/citool-commands.md) to deploy signed and unsigned policies on Windows 11 22H2 and Windows Server 2025 with the following commands. Be sure to replace **<Path to policy binary file to deploy>** in the following example with the actual path to your App Control policy binary file. +You can use the inbox [CiTool](../operations/citool-commands.md) to deploy signed and unsigned policies on Windows 11 22H2 and Windows Server 2025 with the following commands. Be sure to replace `` in the following example with the actual path to your App Control policy binary file. ```powershell # Policy binary files should be named as {GUID}.cip for multiple policy format files (where {GUID} = from the Policy XML) @@ -82,7 +82,7 @@ Use WMI to deploy policies on all other versions of Windows and Windows Server. ## Deploying signed policies -If you're using [signed App Control policies](use-signed-policies-to-protect-appcontrol-against-tampering.md), the policies must be deployed into your device's EFI partition in addition to the locations outlined in the earlier sections. Unsigned App Control policies don't need to be present in the EFI partition. +If you're using [signed App Control policies](use-signed-policies-to-protect-appcontrol-against-tampering.md), the policies must be deployed into your device's EFI partition. 1. Mount the EFI volume and make the directory, if it doesn't exist, in an elevated PowerShell prompt: From dfe48a4970a168d1931ebed07af48ea2e1c6d488 Mon Sep 17 00:00:00 2001 From: Padma Jayaraman Date: Mon, 28 Oct 2024 23:42:13 +0530 Subject: [PATCH 2/5] Pencil edits --- .../application-control/app-control-for-business/appcontrol.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/application-security/application-control/app-control-for-business/appcontrol.md b/windows/security/application-security/application-control/app-control-for-business/appcontrol.md index 51665939c7..8d6749004f 100644 --- a/windows/security/application-security/application-control/app-control-for-business/appcontrol.md +++ b/windows/security/application-security/application-control/app-control-for-business/appcontrol.md @@ -30,7 +30,7 @@ Windows 10 and Windows 11 include two technologies that can be used for applicat ## App Control and Smart App Control -Starting in Windows 11 version 22H2, [Smart App Control](https://support.microsoft.com/topic/what-is-smart-app-control-285ea03d-fa88-4d56-882e-6698afdb7003) provides application control for consumers. Smart App Control is based on App Control. App control enables enterprise customers to create a policy that offers the same security and compatibility as Smart App Control with the capability to customize policeis to run line-of-business (LOB) apps. To make it easier to implement policy, an [example policy](design/example-appcontrol-base-policies.md) is provided. The example policy includes **Enabled:Conditional Windows Lockdown Policy** option that isn't supported for App Control enterprise policies. This rule must be removed before you use the example policy. To use this example policy as a starting point for creating your own policy, see [Create a custom base policy using an example App Control base policy](design/create-appcontrol-policy-for-lightly-managed-devices.md#create-a-custom-base-policy-using-an-example-app-control-base-policy). +Starting in Windows 11 version 22H2, [Smart App Control](https://support.microsoft.com/topic/what-is-smart-app-control-285ea03d-fa88-4d56-882e-6698afdb7003) provides application control for consumers. Smart App Control is based on App Control. App control enables enterprise customers to create a policy that offers the same security and compatibility as Smart App Control with the capability to customize policies to run line-of-business (LOB) apps. To make it easier to implement policy, an [example policy](design/example-appcontrol-base-policies.md) is provided. The example policy includes **Enabled:Conditional Windows Lockdown Policy** option that isn't supported for App Control enterprise policies. This rule must be removed before you use the example policy. To use this example policy as a starting point for creating your own policy, see [Create a custom base policy using an example App Control base policy](design/create-appcontrol-policy-for-lightly-managed-devices.md#create-a-custom-base-policy-using-an-example-app-control-base-policy). Smart App Control is only available on clean installation of Windows 11 version 22H2 or later, and starts in evaluation mode. Smart App Control is automatically turned off for enterprise managed devices unless the user has turned it on first. To turn off Smart App Control across your organization's endpoints, you can set the **VerifiedAndReputablePolicyState** (DWORD) registry value under `HKLM\SYSTEM\CurrentControlSet\Control\CI\Policy` as shown in the following table. After you change the registry value, you must use [CiTool.exe -r](operations/citool-commands.md#refresh-the-app-control-policies-on-the-system) for the change to take effect. From 9ef04f6ec6bd9cccd46862792436fec305284b08 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Mon, 28 Oct 2024 13:11:31 -0700 Subject: [PATCH 3/5] release updates for mcc --- windows/deployment/do/TOC.yml | 2 +- ...cc-ent-private-preview.md => mcc-ent-early-preview.md} | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) rename windows/deployment/do/{mcc-ent-private-preview.md => mcc-ent-early-preview.md} (79%) diff --git a/windows/deployment/do/TOC.yml b/windows/deployment/do/TOC.yml index 749468bbbf..8b3994852b 100644 --- a/windows/deployment/do/TOC.yml +++ b/windows/deployment/do/TOC.yml @@ -66,7 +66,7 @@ - name: Troubleshooting href: mcc-ent-troubleshooting.md - name: Microsoft Connected Cache for Enterprise and Education Early Preview - href: mcc-ent-private-preview.md + href: mcc-ent-early-preview.md - name: Release notes href: mcc-ent-release-notes.md - name: Microsoft Connected Cache for ISPs diff --git a/windows/deployment/do/mcc-ent-private-preview.md b/windows/deployment/do/mcc-ent-early-preview.md similarity index 79% rename from windows/deployment/do/mcc-ent-private-preview.md rename to windows/deployment/do/mcc-ent-early-preview.md index d80c08f02f..20d6403fa2 100644 --- a/windows/deployment/do/mcc-ent-private-preview.md +++ b/windows/deployment/do/mcc-ent-early-preview.md @@ -1,6 +1,6 @@ --- -title: Microsoft Connected Cache for Enterprise and Education Private Preview -description: Details on Microsoft Connected Cache for Enterprise Private Preview +title: Microsoft Connected Cache for Enterprise and Education early preview +description: Details on Microsoft Connected Cache for Enterprise early preview ms.service: windows-client ms.subservice: itpro-updates ms.topic: conceptual @@ -19,10 +19,10 @@ If you participated in the early preview program, thank you for your collaborati To continue using supported version of Microsoft Connected Cache, we strongly recommend that you upgrade your existing cache nodes to the new release. Cache nodes created and deployed during early preview should still function but can no longer be managed or monitored remotely via the Microsoft Connected Cache Azure service. -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. +We strongly recommend you [recreate your existing resources in Azure](mcc-ent-create-resource-and-cache.md) and then [redeploy the caching software to your host machines](mcc-ent-deploy-to-windows.md) using the latest OS-specific installer. ## Next step > [!div class="nextstepaction"] -> [View documentation for Connected Cache Public Preview](mcc-ent-edu-overview.md) +> [View documentation for Connected Cache public preview](mcc-ent-edu-overview.md) From 35293bae63f1a711b30ef961d61051c848818c45 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Mon, 28 Oct 2024 13:43:11 -0700 Subject: [PATCH 4/5] edits --- windows/deployment/do/TOC.yml | 2 +- windows/deployment/do/index.yml | 12 ++++++------ .../do/mcc-ent-create-resource-and-cache.md | 6 +++--- windows/deployment/do/mcc-ent-deploy-to-linux.md | 4 ++-- windows/deployment/do/mcc-ent-deploy-to-windows.md | 6 +++--- windows/deployment/do/mcc-ent-faq.yml | 2 +- windows/deployment/do/mcc-ent-manage-using-cli.md | 4 ++-- windows/deployment/do/mcc-ent-monitoring.md | 8 ++++---- windows/deployment/do/mcc-ent-release-notes.md | 4 ++-- windows/deployment/do/mcc-ent-troubleshooting.md | 8 ++++---- windows/deployment/do/mcc-ent-verify-cache-node.md | 2 +- 11 files changed, 29 insertions(+), 29 deletions(-) diff --git a/windows/deployment/do/TOC.yml b/windows/deployment/do/TOC.yml index 8b3994852b..a86ca6bef1 100644 --- a/windows/deployment/do/TOC.yml +++ b/windows/deployment/do/TOC.yml @@ -65,7 +65,7 @@ href: mcc-ent-faq.yml - name: Troubleshooting href: mcc-ent-troubleshooting.md - - name: Microsoft Connected Cache for Enterprise and Education Early Preview + - name: Microsoft Connected Cache for Enterprise and Education early preview href: mcc-ent-early-preview.md - name: Release notes href: mcc-ent-release-notes.md diff --git a/windows/deployment/do/index.yml b/windows/deployment/do/index.yml index 42eddd71c7..1de435c050 100644 --- a/windows/deployment/do/index.yml +++ b/windows/deployment/do/index.yml @@ -67,10 +67,12 @@ landingContent: linkLists: - linkListType: deploy links: - - text: Connected Cache for Enterprise and Education (early preview) - url: waas-microsoft-connected-cache.md - - text: Sign up - url: https://aka.ms/MSConnectedCacheSignup + - text: Connected Cache for Enterprise and Education overview + url: mcc-ent-edu-overview.md + - text: Connected Cache for Enterprise and Education requirements + url: mcc-ent-edu-mcc-ent-prerequisites.md + - text: Create the Microsoft Connected Cache Azure resource and cache nodes + url: mcc-ent-create-resource-and-cache.md # Card - title: Microsoft Connected Cache for Internet Service Providers (ISPs) @@ -79,8 +81,6 @@ landingContent: links: - text: Connected Cache for ISPs (public preview) url: mcc-isp-signup.md - - text: Sign up - url: https://aka.ms/MCCForISPSurvey - text: Connected Cache for ISPs (early preview) url: mcc-isp.md 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 1450c17321..0a71a896ae 100644 --- a/windows/deployment/do/mcc-ent-create-resource-and-cache.md +++ b/windows/deployment/do/mcc-ent-create-resource-and-cache.md @@ -279,7 +279,7 @@ az mcc ent resource list --resource-group ### List all cache nodes # [Azure portal](#tab/portal) -On the left pane, click on 'Cache Nodes' under 'Cache Node Management' to see all the cache nodes under the Connected Cache resource. +On the left pane, select **Cache Nodes** under **Cache Node Management** to see all the cache nodes under the Connected Cache resource. # [Azure CLI](#tab/cli) @@ -299,7 +299,7 @@ az mcc ent node list --mcc-resource-name --resource-group ### Delete Connected Cache resource # [Azure portal](#tab/portal) -Navigate to the Connected Cache resource to delete and click on the delete button on top. +Navigate to the Connected Cache resource to delete, then select the **Delete** button on top. # [Azure CLI](#tab/cli) @@ -319,7 +319,7 @@ az mcc ent node delete --cache-node-name --mcc-resource-name --mcc-resource-name [!Note] >* For a cache node that is to be deployed on Windows host OS, the physical path of the cache drive must be **/var/mcc**.
->* In the output, look for operationStatus. **operationStatus = Succeeded** indicates that our services have successfully updated the cache node. You will also see that cacheNodeState will show "Not Provisioned".
+>* In the output, look for operationStatus. **operationStatus = Succeeded** indicates that our services have successfully updated the cache node. You will also see that cacheNodeState will show *Not Provisioned*.
>* Please save values for physicalPath, sizeInGb, proxyPort, proxyHostName as these values will be needed to construct the provisioning script. @@ -170,7 +170,7 @@ $proxyHost = "myProxy.com" $proxyPort = "8080" $waitTime = 3 -#Create MCC Az resource +# Create Microsoft Connected Cache Azure resource az mcc ent resource create --mcc-resource-name $mccResourceName --location $resourceLocation --resource-group $resourceGroup #Loop through $cacheNodesToCreate iterations diff --git a/windows/deployment/do/mcc-ent-monitoring.md b/windows/deployment/do/mcc-ent-monitoring.md index 060afcf66f..fd26c86983 100644 --- a/windows/deployment/do/mcc-ent-monitoring.md +++ b/windows/deployment/do/mcc-ent-monitoring.md @@ -18,9 +18,9 @@ ms.date: 09/04/2024 Tracking the status and performance of your Connected Cache node is essential to making sure you're getting the most out of the service. -For basic monitoring, navigate to the "Overview" tab. Here you'll be able to view a collection of predefined metrics and charts. All the monitoring in this section will function right after your Connected Cache node has been deployed. +For basic monitoring, navigate to the **Overview** tab. Here you'll be able to view a collection of predefined metrics and charts. All the monitoring in this section will function right after your Connected Cache node has been deployed. -For advanced monitoring, navigate to the "Metrics" section under the "Monitoring" tab. Here you'll be able to access more sampled metrics (hits, misses, inbound traffic) and specify different aggregations (count, avg, min, max, sum). You can then use this data to create customized charts and configure alerts. +For advanced monitoring, navigate to the **Metrics** section under the **Monitoring** tab. Here you'll be able to access more sampled metrics (hits, misses, inbound traffic) and specify different aggregations (count, avg, min, max, sum). You can then use this data to create customized charts and configure alerts. Between the two monitoring sections, you'll be able to gather essential insights into the health, performance, and efficiency of your Connected Cache nodes. @@ -28,7 +28,7 @@ Between the two monitoring sections, you'll be able to gather essential insights ### Cache node summary -Below are the metrics you'll find in the "Cache Node Summary" dashboard, along with their descriptions. This dashboard only reflects data received from cache nodes in the last 24 hours. +Below are the metrics you'll find in the **Cache Node Summary** dashboard, along with their descriptions. This dashboard only reflects data received from cache nodes in the last 24 hours. ![Screenshot of cache node summary in the Azure portal interface.](../images/mcc-ent-cache-node-summary.png) @@ -67,7 +67,7 @@ The content types displayed in the chart each have a distinct color and are sort ## Advanced Monitoring -To expand upon the metrics shown in the Overview tab, navigate to the "Metrics" tab in the left side toolbar of Azure portal. +To expand upon the metrics shown in the Overview tab, navigate to the **Metrics** tab in the left side toolbar of Azure portal. Listed below are the metrics you can access in this section: diff --git a/windows/deployment/do/mcc-ent-release-notes.md b/windows/deployment/do/mcc-ent-release-notes.md index bbd76a511d..673884ecbe 100644 --- a/windows/deployment/do/mcc-ent-release-notes.md +++ b/windows/deployment/do/mcc-ent-release-notes.md @@ -31,12 +31,12 @@ These changes affect Linux and Windows host machines. ### Feature updates -- **Metrics and charts in Azure portal**: You can now visualize "Outbound egress" and "Volume by Content type" charts for your cache node on Azure portal. You can also create custom monitoring charts for your cache nodes. This capability is under the **Metrics** tab on Azure portal. +- **Metrics and charts in Azure portal**: You can now visualize *Outbound egress* and *Volume by Content type* charts for your cache node on Azure portal. You can also create custom monitoring charts for your cache nodes. This capability is under the **Metrics** tab on Azure portal. - **Cache nodes for Windows or Linux host machines**: Cache nodes can now be created and deployed to Windows host machine or Linux host machines by simply choosing the OS when creating cache nodes. - **Ubuntu 22.04 LTS**: Cache nodes can now be deployed on Ubuntu 22.04 LTS. - **Azure CLI support**: Cache nodes can now be created and managed via Azure CLI. - **Proxy**: We added support for unauthenticated proxy and cloud proxy integration. -- **Updates**: Your cache nodes are now updated automatically and we also added the capability to set each cache node's update ring to govern the cadence of Micoroft Connected Cache container updates. +- **Updates**: Your cache nodes are now updated automatically and we also added the capability to set each cache node's update ring to govern the cadence of Microsoft Connected Cache container updates. ### Fixes - We fixed various bugs to achieve smoother install experience. diff --git a/windows/deployment/do/mcc-ent-troubleshooting.md b/windows/deployment/do/mcc-ent-troubleshooting.md index b7566354ba..ddc3003a7a 100644 --- a/windows/deployment/do/mcc-ent-troubleshooting.md +++ b/windows/deployment/do/mcc-ent-troubleshooting.md @@ -36,7 +36,7 @@ If you're encountering an error during resource creation, check that you have th If you're encountering a validation error, check that you have filled out all required configuration fields. -If your configuration doesn't appear to be taking effect, check that you have clicked the "Save" button at the top of the configuration page in the Azure portal user interface. +If your configuration doesn't appear to be taking effect, check that you have selected the **Save** option at the top of the configuration page in the Azure portal user interface. If you have changed the proxy configuration, you will need to re-provision the Connected Cache software on the host machine for the proxy configuration to take effect. @@ -83,9 +83,9 @@ Once the Connected Cache container is running, a scheduled task is periodically You can use Task Scheduler on the host machine to check the status of this scheduled task. 1. Open Task Scheduler on the host machine -1. Navigate to the Active Tasks section and double-click on "MCC_Monitor_Task" -1. Select the scheduled task "MCC_Monitor_Task" -1. Select the "Triggers" tab and confirm that the Status is "Enabled" +1. Navigate to the Active Tasks section and double-click on **MCC_Monitor_Task** +1. Select the scheduled task **MCC_Monitor_Task** +1. Select the **Triggers** tab and confirm that the Status is **Enabled** ## Troubleshooting cache node deployment to Linux host machine diff --git a/windows/deployment/do/mcc-ent-verify-cache-node.md b/windows/deployment/do/mcc-ent-verify-cache-node.md index 2c63db2453..0398eaa61f 100644 --- a/windows/deployment/do/mcc-ent-verify-cache-node.md +++ b/windows/deployment/do/mcc-ent-verify-cache-node.md @@ -38,7 +38,7 @@ These steps should be taken after deploying Connected Cache software to a [Windo 1. To check how much content an individual Windows client has downloaded from a Connected Cache node, open the [Delivery Optimization activity monitor](/microsoft-365-apps/updates/delivery-optimization#viewing-data-about-the-use-of-delivery-optimization) on the Windows client device. - You should see a donut chart titled Download Statistics. If the Windows client has downloaded content from the cache node, you'll see a segment of the donut labeled "From Microsoft cache server". + You should see a donut chart titled **Download Statistics**. If the Windows client has downloaded content from the cache node, you'll see a segment of the donut labeled **From Microsoft cache server**. ## Related content From 1f15e6980c861bfeb7aa6ad4ffcca2f80c67d9d9 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Mon, 28 Oct 2024 13:51:55 -0700 Subject: [PATCH 5/5] edits --- ...ishing.redirection.windows-deployment.json | 20 +++++++++++++++++++ windows/deployment/do/index.yml | 2 +- .../deployment/do/mcc-ent-troubleshooting.md | 2 +- 3 files changed, 22 insertions(+), 2 deletions(-) diff --git a/.openpublishing.redirection.windows-deployment.json b/.openpublishing.redirection.windows-deployment.json index a563d3fa34..367dbbf186 100644 --- a/.openpublishing.redirection.windows-deployment.json +++ b/.openpublishing.redirection.windows-deployment.json @@ -1675,6 +1675,26 @@ "redirect_url": "/previous-versions/windows/it-pro/windows-10/deployment/planning/windows-10-enterprise-faq-itpro", "redirect_document_id": false }, + { + "source_path": "windows/deployment/do/mcc-enterprise-appendix.md", + "redirect_url": "/windows/deployment/do/mcc-ent-early-preview", + "redirect_document_id": false + }, + { + "source_path": "windows/deployment/do/mcc-enterprise-deploy.md", + "redirect_url": "/windows/deployment/do/mcc-ent-early-preview", + "redirect_document_id": false + }, + { + "source_path": "windows/deployment/do/mcc-enterprise-prerequisites.md", + "redirect_url": "/windows/deployment/do/mcc-ent-early-preview", + "redirect_document_id": false + }, + { + "source_path": "windows/deployment/do/mcc-enterprise-update-uninstall.md", + "redirect_url": "/windows/deployment/do/mcc-ent-early-preview", + "redirect_document_id": false + }, { "source_path": "windows/deployment/planning/windows-10-deployment-considerations.md", "redirect_url": "/previous-versions/windows/it-pro/windows-10/deployment/planning/windows-10-deployment-considerations", diff --git a/windows/deployment/do/index.yml b/windows/deployment/do/index.yml index 1de435c050..b9d6852bd4 100644 --- a/windows/deployment/do/index.yml +++ b/windows/deployment/do/index.yml @@ -70,7 +70,7 @@ landingContent: - text: Connected Cache for Enterprise and Education overview url: mcc-ent-edu-overview.md - text: Connected Cache for Enterprise and Education requirements - url: mcc-ent-edu-mcc-ent-prerequisites.md + url: mcc-ent-prerequisites.md - text: Create the Microsoft Connected Cache Azure resource and cache nodes url: mcc-ent-create-resource-and-cache.md diff --git a/windows/deployment/do/mcc-ent-troubleshooting.md b/windows/deployment/do/mcc-ent-troubleshooting.md index ddc3003a7a..240962f055 100644 --- a/windows/deployment/do/mcc-ent-troubleshooting.md +++ b/windows/deployment/do/mcc-ent-troubleshooting.md @@ -42,7 +42,7 @@ If you have changed the proxy configuration, you will need to re-provision the C ## Troubleshooting cache nodes created during early preview -Cache nodes created and deployed during the [Microsoft Connected Cache for Enterprise and Education early preview](mcc-ent-private-preview.md) should continue to function but can no longer be managed or monitored remotely via the Connected Cache Azure service. +Cache nodes created and deployed during the [Microsoft Connected Cache for Enterprise and Education early preview](mcc-ent-early-preview.md) should continue to function but can no longer be managed or monitored remotely via the Connected Cache Azure service. As such, we strongly recommend you [recreate your existing resources in Azure](mcc-ent-create-resource-and-cache.md) and then [redeploy the Connected Cache software to your host machines](mcc-ent-deploy-to-windows.md) using the latest OS-specific installer.