Forum Widgets
Latest Discussions
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
Stuck on MCC container to be downloaded
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.
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 **********************New shortcut file
hi 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
Error installation MCC on Server 2022
I installed a couple of MCC for customers. But for 1, I still get this error : This is the end of my text file : Restarting WSL to apply new configuration file, please wait while WSL is restarted...... [12/11/2024 13:05:01] . . . . . . . . . . . . . . . [12/11/2024 13:05:15] Completed WSL restart [12/11/2024 13:05:15] Completed restart and successfully applied new configuration file [12/11/2024 13:05:15] Setting LastCompletedInstallStep [12/11/2024 13:05:15] Registering the MCC Monitoring scheduled task [12/11/2024 13:05:15] Register scheduled task MCC_Monitor_Task (mccscheduletask.ps1) [12/11/2024 13:05:15] Registering scheduled task as local account [12/11/2024 13:05:16] Completed registering scheduled task for MCC monitoring [12/11/2024 13:05:16] Completed registering task to monitor MCC and ensure it is running [12/11/2024 13:05:16] Registering the MCC Uninstall scheduled task [12/11/2024 13:05:16] RegisterScheduledTask_UninstallWsl (uninstallwsl.ps1) [12/11/2024 13:05:16] Registering scheduled task as local account [12/11/2024 13:05:16] Completed registering scheduled task for MCC uninstall [12/11/2024 13:05:16] Completed registering task to uninstall MCC manually, if needed in the future [12/11/2024 13:05:16] Setting LastCompletedInstallStep [12/11/2024 13:05:16] Registering MCC install task and waiting for compleition [12/11/2024 13:05:16] RegisterScheduledTask_InstallMccOnWsl (InstallMccOnWsl.ps1) [12/11/2024 13:05:16] Registering scheduled task as local account [12/11/2024 13:05:16] Completed registering scheduled task for MCC Install [12/11/2024 13:05:16] Setting LastCompletedInstallStep [12/11/2024 13:05:16] Successfully registered MCC Install Scheduled task [12/11/2024 13:05:17] System.Management.Automation.RuntimeException: Impossible d’appeler une méthode dans une expression Null. à System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception) à System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame) à System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) à System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) [12/11/2024 13:05:17] [2024-12-11] [01:05:17 ] [12/11/2024 13:05:17] WSL MCC install failed (ReturnCode: ) [12/11/2024 13:05:17] [2024-12-11] [01:05:17 ] PS>Erreur de terminaison (SetDWordRegistryValue) : « Impossible de lier l'argument au paramètre « Value », car il s'agit d'une chaîne vide. » [12/11/2024 13:05:17] Setting InvocationEndTime [12/11/2024 13:05:17] Setting InvocationState [12/11/2024 13:05:17] Installer return code 0 ********************** Fin de la transcription Windows PowerShell Heure de fin : 20241211130517 **********************generateCsr.sh failing
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?
