Microsoft Connected Cache for Enterprise and Education topics

Install failed at Attempting to get task info for MCC Install Scheduled Task

hoyty76 — Thu, 02 Apr 2026 20:04:04 GMT

Built a fresh Windows Server 2025 from March 2026 ISO and installed Hyper-V / WSL. After reboots I ran the script. It failed at the scheduled task step. Not sure how to troubleshoot this? Tried to re-run install script and errored out differently. I attached the logs. I renamed from .log to .docx to trick the attachment filter.

Large Intune Win32 apps don't seem to cache

AndrewMcN_SFRS — Sun, 01 Feb 2026 17:16:12 GMT

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.

v2.0.0.2119_e

marty5 — Mon, 22 Dec 2025 12:12:51 GMT

v2.0.0.2119_e was released on 17th November but none of my nodes have updated yet, they are all using 'Fast - Keep nodes updated immediately'. Any known issues?

Question regarding update requests on the MCC node

Makky — Tue, 09 Dec 2025 08:54:36 GMT

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

Makky — Wed, 03 Dec 2025 07:21:24 GMT

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

jjmehren — Sat, 22 Nov 2025 01:39:38 GMT

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?

Air-Gap System Deployment

myyodamail — Fri, 03 Oct 2025 18:37:06 GMT

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.

Cache server hostname source & LocalPolicyMerge setting

bindumadhava — Fri, 22 Aug 2025 14:51:19 GMT

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.

generateCsr.sh failing

eoirgjuhs — Mon, 18 Aug 2025 09:43:56 GMT

Hi,

I'm trying to run ./generateCsr.sh to generate a CSR, but it is failing with the following errors:

[2025-08-18 09:27:23] [GENERATE-CSR-BASH-SCRIPT] - Executing docker command: docker exec MCC bash -lc "source /tls/call-csr-endpoint.sh 'RSA' '2048' 'srv1_csr_20250818_092719' '<SUBJECT>' '<SAN>'" [2025-08-18 09:27:23] [GENERATE-CSR-BASH-SCRIPT] - bash: /root/.bash_profile: Permission denied <snip> [2025-08-18 09:27:25] [GENERATE-CSR-BASH-SCRIPT] - mkdir: cannot create directory '/keys': Permission denied [2025-08-18 09:27:25] [GENERATE-CSR-BASH-SCRIPT] - chmod: cannot access '/keys': No such file or directory [2025-08-18 09:27:25] [GENERATE-CSR-BASH-SCRIPT] - /tls/call-csr-endpoint.sh: line 159: netstat: command not found [2025-08-18 09:27:25] [GENERATE-CSR-BASH-SCRIPT] - CSR script completed successfully [2025-08-18 09:27:25] [GENERATE-CSR-BASH-SCRIPT] - windowsCerts directory does not exist, CSR generated directly in certs directory [2025-08-18 09:27:25] [GENERATE-CSR-BASH-SCRIPT] - ERROR: CSR file not found at expected location: /var/mcc/certs/certs/srv1_csr_20250818_092719.csr

MCC software version 2.0.0.2112_e

I've tried both Ubuntu 24.04 and Alma Linux 8. No CSR is generated

Any ideas?

MCC Phantom Install

jjmehren — Fri, 15 Aug 2025 13:49:08 GMT

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 **********************

MCC Install Failure - Code 13631746

marty5 — Fri, 15 Aug 2025 08:34:11 GMT

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 D00102

Win 2025 - MCC Install Failure

marty5 — Mon, 11 Aug 2025 11:03:09 GMT

WSL_Mcc_Install_Transcript

[08/11/2025 14:41:51] Completed configuration of port forwarding [08/11/2025 14:41:51] Setting WslMccUbuntuEthZeroIp [08/11/2025 14:41:51] Creating cache folder locations within Ubuntu image [08/11/2025 14:41:51] Successfully completed creating cache folder locations within Ubuntu image [08/11/2025 14:41:51] Running MCC install command line within WSL Ubuntu distro... [08/11/2025 14:45:27] MCC install command line has completed within WSL Ubuntu distro [08/11/2025 14:45:27] Validating MCC install to ensure it has completed successfully [08/11/2025 14:45:27] Failure: MCC failed to install during deployment, please check install from registered task install logs to diagnose issue and retry, Return Code: 13631746 [08/11/2025 14:45:27] System.Management.Automation.RuntimeException: ScriptHalted [08/11/2025 14:45:27] [2025-08-11] [02:45:27 PM] [08/11/2025 14:45:27] WSL MCC install failed (ReturnCode: 13633026) [08/11/2025 14:45:27] [2025-08-11] [02:45:27 PM] [08/11/2025 14:45:27] Setting InvocationExitCode [08/11/2025 14:45:27] Setting InvocationErrorMessage [08/11/2025 14:45:27] Setting LastCompletedInstallStep Unregistering. [08/11/2025 14:45:28] Unregistered base Ubuntu image version: Ubuntu-24.04-Mcc after successful install of MCC

WSL_Mcc_Install_FromRegisteredTask_Transcript

[✓] Certificate matches expected thumbprint! Geo certificate verification successful. Fetching Geo response... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 270 100 270 0 0 29 0 0:00:09 0:00:09 --:--:-- 62 Using default MCC KV host. [!] Only 1 cert(s) found. Server may not be sending full chain. MCCKV certificate verification failed. Exiting. [08/11/2025 14:45:26] MCC install has completed within WSL Ubuntu distro

Minor Improvement for v2

marty5 — Mon, 11 Aug 2025 06:13:29 GMT

You might receive the below error during installation

System.Management.Automation.RuntimeException: WSL MCC setup requires Hyper-V to be installed on this machine, please install Hyper-V and re-run installation : Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

The suggested fix only applies to Windows 11 installations. Windows server installs require the below command. All of this info is listed in the prerequisites but it might catch some people out.

Install-WindowsFeature -Name Hyper-V -IncludeManagementTools

Ubuntu 24.04 LTS Not found (404)

SamuelLangis — Thu, 07 Aug 2025 14:24:06 GMT

I installed 3 MCC this week, but today I see the error message on two different servers. Is something not available regarding this distribution? I also tried it directly and the same result.
Thanks!

Stuck on "MCC container detected as running, waiting for MCC to return ready status code"

Khuongy — Wed, 30 Jul 2025 07:18:10 GMT

Hi all,

We’ve followed Microsoft’s guide to set up Microsoft Connected Cache, but we’re hitting a roadblock.

When attempting to deploy the cache node, the process gets stuck at the following message:

"MCC container detected as running, waiting for MCC to return ready status code"

It doesn’t move past this point.

We haven’t been able to find any clear documentation or community guidance on what this specific status means or how to troubleshoot it.

Has anyone else run into this issue, and if so, how did you resolve it?

Thanks in advance for any help,

New shortcut file

bindumadhava — Thu, 05 Jun 2025 12:13:07 GMT

Anyone noted a new file that gets downloaded / created called shortcut.ico when we trigger the installation of connected cache. This was seen only from past 2 weeks. This file is not available in the installer download location so i assume this is getting downloaded during installation and goes inside the installer folder.

Double click or checking the path of this ico file doesnot showup anything useful to troubleshoot / check

Stuck on MCC container to be downloaded

HomanA — Wed, 04 Jun 2025 11:40:28 GMT

Hello everyone,

I'm new here and I'm wondering if someone could help me.

I'm trying to install MCC but it is "stuck" on Waiting for MCC container to be downloaded (could take up to 30 minutes) but it takes a few hours before I get this error message: "An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. (error code: 0x80072747)"

The VM where the WSL runs on is a Windows Server 2022, 16GB RAM, nested virtualization configured, 1 socket, 4 cores, 8 logical processors, 1TB free of space (HD). The server is only dedicated for this role.

I'm also in contact with the support team of Microsoft but we are still not able to figure this out.

Is there a way we can troubleshoot? Is the MCC that is not able to download (via NAT of the VM-host?), are there other things I can check/test?

Thank you in advance.

Cache Size Limit Ignored

marty5 — Fri, 25 Apr 2025 05:59:29 GMT

Using Windows cache node version 1.2.1.2076_E.

The cache drive size is set to the minimum of 50GB, it appears this limit is ignored as I have multiple servers with the C:\mccwsl01\ext4.vhdx file being over 100GB.

Verified that the install log states the following "Cache Drives: /var/mcc,50" and lines later on stating

"Verified a cache drive size greater than 50 was specified, sizeinGb : 50"
"Completed cache folder validation, final drive configuration string : /var/mcc`,50`,

MCC Deployment Large Enterprises

Viktor_Grzebyk — Thu, 27 Mar 2025 17:51:15 GMT

Hello everyone,

As dedicated fans of MCC, I’d like to share some challenges you might encounter when deploying MCC in conjunction with DHCP option 235. Below are key troubleshooting points and network considerations to help guide you through the process.

Preliminary Troubleshooting Steps

Before diving deeper, ensure you verify the following:

Network Proxy: Confirm if your network uses a proxy, adjust the rules.
TLS Inspection: Review and adjust TLS inspection rules by creating necessary exclusions.
Firewall Policies: If Firewall Local Policy Merge is disabled for all clients, Create appropriate inbound rules for Delivery Optimization (DO) and inspect the firewall’s inbound logs on the client.
Connectivity Test: Verify access to the MCC using a command, that is mentioned in the docs, from the client. For guidance, refer to Microsoft Documentation.
PowerShell Check: Run Get-DeliveryOptimizationStatus to confirm that P2P is operational and that the MCC is properly recognized.
Intune Policies: Double-check that your DO Intune policies are configured correctly.
Network Deep Dive: DHCP Communication

If the MCC server remains unreachable via DHCP Option 235 after the initial checks, it’s time to investigate further into your network setup.

Standard DHCP Process

Typically, DHCP communication occurs in four steps:

DHCP Discover
DHCP Offer
DHCP Request
DHCP ACK

The DHCP ACK packet is where the client normally receives DHCP Option 235.

Role of VLANs and DHCP Relay

In large networks with multiple VLANs, an IP helper-address is used to set up a DHCP relay. Since DHCP broadcasts are limited to the local LAN, a DHCP relay intercepts the broadcast, converts it into a unicast request to the DHCP server on a different LAN, and then relays the unicast response (including the necessary DHCP options) back to the client.

Introduction of DHCPINFORM

In these scenarios, a fifth packet—DHCPINFORM—comes into play. This packet is sent by clients to obtain additional network configuration details (like DHCP Option 235) without needing to lease a new IP address.

Identifying and Resolving Communication Breaks

A potential issue arises when the DHCPINFORM request is either not forwarded by the firewall or core switch (which handles the IP helper function) or when the corresponding DHCP ACK response is blocked. In such cases, the client successfully obtains its IP address and basic DHCP options, but fails to receive Option 235, which is crucial for starting content downloads.

So we where able to see the DHCPINFORM request but there was any response.

The resolution involved investigating the firewall responsible for handling the IP helper function. Although the DHCP server correctly sent a DHCP ACK in response to the DHCPINFORM request, the firewall treated this as a new session and blocked it. Adjusting the firewall rules allowed the DHCP ACK to reach the client successfully.

I hope these insights help you troubleshoot and achieve a seamless deployment of MCC with DHCP Option 235. If you have any questions or need further clarification, please feel free to reach out.

Waiting for MCC container to become available

scottu1615 — Thu, 27 Mar 2025 08:49:22 GMT

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