Forum Widgets
Latest Discussions
Large Intune Win32 apps don't seem to cache
I was hoping to see one of our MCC's cache some large Intune Win32 app packages. One is around 28GB and a couple of others are around 18GB. This is within Intune's Win32 app size limit. It's for a self-deploying Autopilot build and these are large sets of maps and documents. All packages deploy accurately given the download time needed. We have 700 to build. The Internet service available at build sites is not really sufficient. An MCC seemed like the perfect solution. Unfortunately, there is apparent evidence that the packages are not being cached. Not only do they not appear to register in the metrics, each device takes all day to build. Obviously, the more we try to do at once, the worse it gets. Here is a screenshot of the metrics for the last 30 days: This cache is dedicated to our PC Build Room's VLAN subnet. As you can see, Intune content only seems to account for 1.99GB when it should be much more than this. The MCC is 300GB in size. Being able to diagnose why the MCC is not caching these Win32 app packages would be extremely useful. Is it our infrastructure or something else? I have an open support case and also posted about it in the MCCP. Microsoft reps advised that MCC should be able to support these packages.
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 Scott
