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.
Air-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.
Minor Improvement for v2
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 -IncludeManagementToolsCertificate installation request during WSL setup
Hi We use Beyond Trust privilege management to open elevated PowerShell. This elevated powershell is used to run the WSL installation. The installation starts and during the completion of WSL installation we get an additional pop-up for Local Admin account. This pop-up is for installation of certificate requesting for local admin creds. The certificate is for Windows hardware driver verification. Any of you using elevated powershell do get this popup to install certificate, trying to rule out if this is generic or specific to my infra. We are using Win11 23H2. Thank you.Welcome to the Connected Cache for Enterprise and Education Discussion Forum!
Hello All! Welcome to the new discussion board for Microsoft Connected Cache for Enterprise and Education! Here you can engage in conversations with your peers around configuration and deployment of cache nodes, Connected Cache CLI, reporting and monitoring, troubleshooting issues, post questions for our product team or other users of the product. We will have a separate "Ideas Board" where you can share ideas for the future of Connected Cache for Enterprise and Education. So look for this announcement coming soon. Thanks for being a part of our community!
