first round of changes

windows/deployment/do/mcc-isp-monitor.md

@@ -0,0 +1,23 @@
+# Monitor cache node health and performance
+
+## Metrics 
+Within Azure portal, there are a number of metrics that are available to monitor cache node health and performance.
+
+### Available Metrics
+    - **Cache Efficiency**: Cache efficiency is defined as the total cache hit bytes divided by all bytes requested. The higher this value (0 - 100%), the more efficient the cache node is. 
+
+    - **Healthy nodes**: The number of cache nodes that are reporting as healthy
+    - **Unhealthy nodes**: The number of cache nodes that are reporting as unhealthy
+    - **Maximum in**: The maximum egress (in Gbps) of inbound traffic
+    - **Maximum out**: The maximum egress (in Gbps) of outbound traffic
+    - **Average in**: The average egress (in Gbps) of inbound traffic
+    - **Average out**: The average egress (in Gbps) of outbound traffic
+
+### Viewing your metrics
+To view the metrics associated with your cache nodes, navigate to the **Overview** tab within Azure portal.
+
+[[ include screenshot of an example view]]
+
+You can choose to monitor the health and performance of all cache nodes or one by one 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 are unable to view metrics for your cache node, it may be that your cache node is unhealthy, inactive, or hasn't been fully configured. 

windows/deployment/do/mcc-isp-uninstall.md

@@ -0,0 +1,32 @@
+# Uninstall your cache node
+
+There are two main steps required to uninstall your cache node:
+1. Delete your cache node from the Azure portal
+1. Run the uninstall script to cleanly remove MCC from your server
+
+
+## Delete your cache node from the Azure portal
+Navigate to your Overview page. On the top bar, click on **Delete**.
+
+
+## Run the uninstall script to cleanly remove MCC from your server
+In the installer zip file, you'll find the file **uninstallmcc.sh**. This script uninstalls MCC and all the related components. Before you run this script, contact the MCC team. Only run it if you're facing issues with MCC installation.
+
+> [!WARNING]
+> Be cautious before running this script. It will also erase existing IoT workflows in this VM.
+
+The **uninstallmcc.sh** script removes the following components:
+
+- IoT Edge
+- Edge Agent
+- Edge Hub
+- MCC
+- Moby CLI
+- Moby engine
+
+To run the script, use the following commands:
+
+```bash
+sudo chmod +x uninstallmcc.sh
+sudo ./uninstallmcc.sh
+```

windows/deployment/do/mcc-isp-update.md

@@ -0,0 +1,7 @@
+# Update your cache node
+
+Microsoft will release updates for MCC periodically to improve performance, functionality, and security. Updates will not require any action from the customer. Instead, when an update is available, your cache node will automatically update during low traffic hours with minimal to no impact to your end customers. 
+
+To view which version your cache nodes are currently on, [[*********]].
+
+To view update release notes, visit our Tech Community page.

windows/deployment/do/mcc-isp-verify-cache-node.md

@@ -0,0 +1,49 @@
+# Verify cache node functionality
+
+### Verify client side
+
+Sign in to the Connected Cache server or use SSH. Run the following command from a terminal to see the running modules (containers):
+
+```bash
+sudo iotedge list
+```
+
+If the cache server is running properly, you will see the containers **edgeAgent**, **edgeHub**, and **[Your Cache Node name]** listed, all with the status **running**.
+
+If it lists the **edgeAgent** and **edgeHub** containers, but doesn't include **MCC**, view the status of the IoT Edge security manager using the command:
+
+```bash
+sudo journalctl -u iotedge -f
+```
+
+This command provides the current status of the starting and stopping of a container or the container pull and start.
+
+### Verify server side
+
+It can take a few minutes for the container to deploy.
+
+To validate a properly functioning MCC, run the following command in the terminal of the cache server or any device in the network. Replace `<CacheServerIP>` with the IP address of the cache server.
+
+```bash
+wget http://<CacheServerIP>/mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com
+```
+
+If successful, you will see a terminal output similar to the following:
+
+```bash
+HTTP request sent, awaiting response... 200 OK
+Length: 969710 (947K) [image/gif]
+Saving to: 'wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com'
+
+wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com   100%[========================]
+```
+
+:::image type="content" source="images/imcc28.png" alt-text="Terminal output of successful test result with wget command to validate a MCC.":::
+
+Similarly, enter the following URL into a web browser on any device on the network:
+
+```http
+http://<CacheServerIP>/mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com
+```
+
+If the test fails, for more information, see the [common issues](#common-issues) section.

windows/deployment/do/mcc-isp-vm-performance.md

@@ -0,0 +1,13 @@
+# Enhancing VM Performance
+
+In virtual environments, the cache server egress peaks at around 1.1 Gbps. If you want to maximize the egress in virtual environments, it's critical to change the following two settings:
+
+1. Enable **SR-IOV** in the following three locations:
+
+    - The BIOS of the MCC VM
+    - The MCC VM's network card properties
+    - The hypervisor for the MCC VM
+
+    Microsoft has found these settings to double egress when using a Microsoft Hyper-V deployment.
+
+2. Enable "high performance" in the BIOS instead of energy savings. Microsoft has found this setting to also nearly double egress in a Microsoft Hyper-V deployment.