Forum Widgets
Latest Discussions
Question regarding update requests on the MCC node
So, as I have understood it, the MCC requires an update request to be requested 3 times by different devices before it actually starts to download it to cache it. 1. How many downloads does the MCC node download at the same time? 2. Does the MCC node keep a que list? 3. Does an update request ever "time out" on the MCC node or is it kept forever until reaching 3? What we have seen on the lab with 10 laptops, it is struggling to get more than 20% updates distributed from the MCC node. We re-install the laptops with the same USB installer multiple times when Windows reports it to be updated, so all of them are installed on the same build level every time. 4. How many times do we need to "re-install" windows until all updates are cached?Check cache status on MCC node
Is it posssible to check/monitor the amount of data the MCC node has cached? Since the MCC downloads updates only when requested 3x by the clients, it would be good to know how much % of an update is actually cached. This would give the most value when troubleshooting the MCC and the distribution of updates. We have configured a MCC in our LAB with 10 connected clients, and the amount of data shared varies too much for each client.
MCC Container missing mount points - unable to get CSR
MCC for Enterprise installed on Server 2022 I have around 20 nearly identical servers set up with MS Connected Cache, but two of them refuse to deploy the container in a fully operational state. Everything works perfectly fine over port 80. However, when I run the generateCSR.ps1 script, it fails. After digging around for quite a while, I found that the mount point inside the container is missing. This means that although the CSR is being generated, it can't send it back to Ubuntu and then to Windows. Running the 'docker inspect MCC' command yields this result: But, it's supposed to look like this: Apparently, you can't just add a mount point to the container. It has to be removed and redeployed with the mount point specified. However, I'm not able to figure out any way of doing that since the script seems to be deploying the container in a way that it generates the configuration file when running the deployment script instead of me being able to modify it for the deployment. I'm at a bit of a loss as to how to fix this or why it's even happening. I've already tried ripping everything out, including WSL and Hyper-V, and redeploying, with no success. Thoughts?Cache node successfully deployed but not serving requests
Hello All, I have successfully deployed Cache node on a Windows 11 Entra ID joined PCs in two locations. Both Cache nodes are showing healthy, and Intune policy with DOCacheHost was successful. However Cache node is not serving client requests. I have checked all troubleshooting steps that MS mentioned in the below article. Everything looks normal. https://learn.microsoft.com/en-us/windows/deployment/do/mcc-ent-troubleshooting 1. I ran "DeliveryOptimizationTroubleshooter" It is showing below unable to make WebRequest using MCC link over port 80 under "MCC DEVICE SETUP" 2. As per the troubleshooting document, I do not see any errors on port forwarding rules: 3. In both locations its the same behaviour, no FW between MCC Cache node to the Client PC, both are in same network. I have tried disabling windows FW on both ends. no luck. 4. Also command "netsh -a" results on MCC shows it is listening to port 80 I know it is something to tweak about networks, but not sure what i am missing as there is no NW FW/Windows FW, but why Client is failing on http://:80 and any idea?MCC Install Failure - Code 13631746
WSL_Mcc_Install_FromRegisteredTask log doesn't contain any useful information as to the failure unfortunately. ======================= Starting aziot-tpmd.socket...Started! Starting aziot-edged.service...Started! Done. Successfully applied configurations Successfully completed MCC device registration Starting cron job to update host every 4 hours Successfully added cron job to update host every 4 hours You have successfully deployed your server and cache node installation process will begin. It could take up to 30 minutes for the cache node software to download and begin caching. [08/15/2025 12:11:15] MCC install has completed within WSL Ubuntu distro [08/15/2025 12:11:15] Validating MCC install to ensure it has completed successfully [08/15/2025 12:11:15] Retrieved MCC install log, and it is not null or empty [08/15/2025 12:11:15] Validating that there are no common errors being reported in the install logs [08/15/2025 12:11:15] Failure: MCC failed to install during deployment, please check install from registered task install logs to diagnose issue and retry, Return Code: 13631746 [08/15/2025 12:11:15] System.Management.Automation.RuntimeException: Failure: MCC failed to install during deployment, please check install from registered task install logs to diagnose issue and retry, Return Code: 13631746 [08/15/2025 12:11:15] [2025-08-15] [12:11:15 PM] [08/15/2025 12:11:15] WSL MCC install failed (ReturnCode: 13631746) [08/15/2025 12:11:15] [2025-08-15] [12:11:15 PM] [08/15/2025 12:11:15] Installer return code D00102Air-Gap System Deployment
Everything I've read indicated that MCC must be deployed on an Internet connected system. However, Microsoft Copolite said it can be deployed on an air-gap (i.e. closed, non-Internet facing) system and to use the pre-seeding tool to download contents. My main interest is to use MCC to assist with future Windows OS upgrade and (secondary) patching on my closed network. I currently pull-down patches via a connected WSUS and then sneakernet them over to the WSUS servers on our closed networks. Has anyone successfully deployed MCC in an air-gap environment and operating as intended? Any lessons learned? Thanks in advance.
Waiting for MCC container to become available
Hi, Trying to setup Intune Connected Cache and getting stuck on MCC Install Waiting for MCC container to become available. running on Server 2022 VM with nested virtulization turned on and using a groupMSA account. I have set this up fine on one of our other domains\tenancy. Any ideas? Tried starting from scratch several times and not sure whats stopping it. Thanks ScottCache server hostname source & LocalPolicyMerge setting
hi In our organization we have the LocalPolicyMerge setting set to false thus blocking all standard or custom locally created inbound MDE firewall rule. Outbound does not have any such restriction. We do see that the clients does not receive OptionID235 value from DHCP server. We did see a note in the Microsoft documentation [Delivery Optimization reference] been called out for this, but with less information on what is the configuration or setting that gets blocked. If the LocalPolicyMerge setting is configured, such as part of security baselines, it can impact DHCP client and prevent it from retrieving this DHCP option, especially in Autopilot scenarios. Does anyone have the same issue and what are the rules that were created to have this working? Thank you.MCC Phantom Install
Installing on Windows 2022. WSL and WSL kernel are fully updated. MCC claims it installed successfully, but there is no distro installed. wsl --list says none exist. The wslip.txt file just shows: System.Object[] COMPLETED Starting MCC installation from scheduled task [07/30/2025 17:03:04] Verifying VHDX file exists and is accessible: c:\mccwsl02\Ubuntu-24.04-Mcc-Converted.vhdx [07/30/2025 17:03:04] VHDX file verified: Size 132074438656 bytes, accessible for import [07/30/2025 17:03:04] Importing MCC Ubuntu image from c:\mccwsl02\Ubuntu-24.04-Mcc-Converted.vhdx to WSL [07/30/2025 17:03:04] Completed imported MCC Ubuntu image from c:\mccwsl02\Ubuntu-24.04-Mcc-Converted.vhdx to WSL [07/30/2025 17:03:04] Validating that import was successful [07/30/2025 17:03:17] WSL Ubuntu Image detected running on IP : System.Object[], configuring port proxy [07/30/2025 17:03:18] Completed configuration of port forwarding [07/30/2025 17:03:18] Setting WslMccUbuntuEthZeroIp [07/30/2025 17:03:18] Successfully validated that WSL Imported MCC Ubuntu Image, WSLStatusText : Installed [07/30/2025 17:03:19] Creating cache folder locations within Ubuntu image [07/30/2025 17:03:19] Successfully completed creating cache folder locations within Ubuntu image [07/30/2025 17:03:19] Running MCC install command line within WSL Ubuntu distro... [07/30/2025 17:04:28] MCC install command line has completed within WSL Ubuntu distro [07/30/2025 17:04:28] Validating MCC install to ensure it has completed successfully [07/30/2025 17:04:28] Successfully verified that MCC has been installed on Ubuntu WSL instance [07/30/2025 17:04:30] Waiting for MCC container to become available... [07/30/2025 17:04:35] Waiting for MCC container to be downloaded (could take up to 30 minutes)... [07/30/2025 17:06:15] Jul 30 17:05:11 ***Removed for Privacy*** aziot-edged[4186]: 2025-07-30T21:05:11Z [INFO] - Pulling image via tag msconnectedcacheprod1.azurecr.io/mcc/linux/iot/mcc-ubuntu-iot-amd64:2.0.0.2112_e... [07/30/2025 17:06:15] Jul 30 17:06:14 ***Removed for Privacy*** aziot-edged[4186]: 2025-07-30T21:06:14Z [INFO] - Successfully pulled image msconnectedcacheprod1.azurecr.io/mcc/linux/iot/mcc-ubuntu-iot-amd64:2.0.0.2112_e [07/30/2025 17:06:20] MCC container detected as running, waiting for MCC to return ready status code [07/30/2025 17:06:34] Successfully validated MCC install, returned 200 for content request [07/30/2025 17:06:34] Setting LastCompletedInstallStepw2 [07/30/2025 17:06:34] MCC Install Task has returned success [07/30/2025 17:06:34] Final validation, ensuring that MCC is up and responding to requests [07/30/2025 17:06:34] Checking for netsh interface portproxy forwarding rules [07/30/2025 17:06:34] Successfully verified that MCC public port :80 has been forwarded to WSL [07/30/2025 17:06:34] Verifying symlink created: Ubuntu-24.04-Mcc [07/30/2025 17:06:34] Current execution context - User: ***Removed for Privacy***, Path: C:\Program Files\WindowsApps\Microsoft.DeliveryOptimization_1.0.24.0_neutral__8wekyb3d8bbwe\deliveryoptimization-cli [07/30/2025 17:06:34] MCC Runtime Account: ***Removed for Privacy*** [07/30/2025 17:06:34] Validating WSL distribution using gMSA account [07/30/2025 17:06:34] Current execution context - User: ***Removed for Privacy*** [07/30/2025 17:06:34] Checking for WSL distribution: Ubuntu-24.04-Mcc as runtime account: ***Removed for Privacy*** [07/30/2025 17:06:34] Created temporary task directory: c:\mccwsl02\TempWslCheck_a0d047e2-1dc9-45ce-be9b-a145ecbb5f3d [07/30/2025 17:06:34] Starting WSL distribution check task 'WSLDistroCheck_1654293464' [07/30/2025 17:06:35] Waiting for WSL distribution check task 'WSLDistroCheck_1654293464' to complete (max 30 seconds)... [07/30/2025 17:06:37] Task 'WSLDistroCheck_1654293464' finished. State: Ready, LastResult: [07/30/2025 17:06:37] Reading WSL distribution check result from file: c:\mccwsl02\TempWslCheck_a0d047e2-1dc9-45ce-be9b-a145ecbb5f3d\wsl_distro_check_result.txt [07/30/2025 17:06:37] Check result: U b u n t u - 2 4 . 0 4 - M c c - B a s e U b u n t u - 2 4 . 0 4 - M c c [07/30/2025 17:06:37] WSL distribution 'Ubuntu-24.04-Mcc' found for runtime account: ***Removed for Privacy*** [07/30/2025 17:06:37] Setting up certificate directories and WSL symlinks for gMSA account via scheduled task approach [07/30/2025 17:06:37] Creating Certificates directory: c:\mccwsl02\Certificates [07/30/2025 17:06:37] Certificates directory created successfully [07/30/2025 17:06:37] Creating certs subdirectory: c:\mccwsl02\Certificates\certs [07/30/2025 17:06:37] Certs subdirectory created successfully [07/30/2025 17:06:37] Creating logs subdirectory: c:\mccwsl02\Certificates\logs [07/30/2025 17:06:37] Logs subdirectory created successfully [07/30/2025 17:06:37] Creating WSL symlinks and config using scheduled task approach for gMSA account [07/30/2025 17:06:37] Registering WSL symlink setup task 'WSLSymlinkSetup_1872124169' using gMSA account for ***Removed for Privacy*** [07/30/2025 17:06:37] Starting WSL symlink setup task 'WSLSymlinkSetup_1872124169' [07/30/2025 17:06:37] Waiting for WSL symlink setup task 'WSLSymlinkSetup_1872124169' to complete (max 45 seconds)... [07/30/2025 17:06:43] Task 'WSLSymlinkSetup_1872124169' finished. State: Ready, LastResult: [07/30/2025 17:06:43] WSL Setup Results: Directory setup: Symlink creation: Subdirectories: Config file: Symlink verification: lrwxrwxrwx 1 root root 28 Jul 30 17:06 windowsCerts -> /mnt/c/mccwsl02/Certificates Config verification: Config file exists SUCCESS: WSL setup completed Directory setup: Symlink creation: Subdirectories: Config file: Symlink verification: lrwxrwxrwx 1 root root 28 Jul 30 17:06 windowsCerts -> /mnt/c/mccwsl02/Certificates Config verification: Config file exists SUCCESS: WSL setup completed [07/30/2025 17:06:43] WSL symlink and config creation completed successfully via scheduled task [07/30/2025 17:06:43] Successfully created WSL symlink for gMSA account using scheduled task approach [07/30/2025 17:06:43] Successfully created config file for gMSA account using scheduled task approach [07/30/2025 17:06:43] Cleaning up temporary task directory: c:\mccwsl02\TempWslCheck_a0d047e2-1dc9-45ce-be9b-a145ecbb5f3d [07/30/2025 17:06:43] ============================================================== [07/30/2025 17:06:43] TLS INFRASTRUCTURE SETUP RESULT DETAILS: [07/30/2025 17:06:43] ============================================================== [07/30/2025 17:06:43] WSLDistroFound: True [07/30/2025 17:06:43] CertificatesDirectoryCreated: True [07/30/2025 17:06:43] WSLSymlinkCreated: True [07/30/2025 17:06:43] ConfigFileCreated: True [07/30/2025 17:06:43] HasLocalAccountCredential: False [07/30/2025 17:06:43] ErrorMessage: [07/30/2025 17:06:43] ErrorDetails: None [07/30/2025 17:06:43] SUCCESS CALCULATION BREAKDOWN: [07/30/2025 17:06:44] [07/30/2025 17:06:44] Has Local Credentials = False [07/30/2025 17:06:44] WSLDistroFound = True [07/30/2025 17:06:44] CertificatesDirectoryCreated = True [07/30/2025 17:06:44] WSLSymlinkCreated = True [07/30/2025 17:06:44] ConfigFileCreated = True [07/30/2025 17:06:44] FINAL SUCCESS RESULT: True [07/30/2025 17:06:44] ============================================================== [07/30/2025 17:06:44] [07/30/2025 17:06:44] TLS infrastructure setup completed successfully [07/30/2025 17:06:44] [07/30/2025 17:06:44] Successfully received response from MCC content server, status description: OK, System.Net.HttpWebRequest.URL, System.Net.HttpWebRequest.StatusCode [07/30/2025 17:06:44] Successfully verified MCC is installed, running and responding to requests! [07/30/2025 17:06:44] Setting LastCompletedInstallStep [07/30/2025 17:06:44] Setting InvocationExitCode [07/30/2025 17:06:44] Unregistered base Ubuntu image version: Ubuntu-24.04-Mcc after successful install of MCC [07/30/2025 17:06:44] Setting InvocationEndTime [07/30/2025 17:06:44] Setting InvocationState [07/30/2025 17:06:44] Installer return code 0 ********************** Windows PowerShell transcript end End time: 20250730170644 **********************
