question

MichelLeclerc-0874 avatar image
0 Votes"
MichelLeclerc-0874 asked saldana-msft edited

Clients not using Microsoft Connected cache (Doinc)

Hello, I'm trying to configure MECM (2010) to work with connected cache. DOINC is enabled on DP Clients registry is configured with DOCacheHost and download mode is 2 (Group) GroupID is also configured. When I try to download an update content is retrieved from office CDN and never from the MCC. Cache server is used for store download. So, it's an issue specific to MECM. Did I missed something ?

mem-cm-generalmem-cm-updates
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

GaryBlok avatar image
0 Votes"
GaryBlok answered

I was unaware M365 updates came through Connected Cache. We're pulling them in to CM, and clients pull from DPs, similar to other updates.
We're also working on Split tunneling, so that MS Updates would all come directly from MS when on VPN.


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

SunnyNiu-MSFT avatar image
0 Votes"
SunnyNiu-MSFT answered MichelLeclerc-0874 commented

@MichelLeclerc-0874
1)If the Connected Cache server isn't installed correctly, or the Connected Cache server is unavailable, client will not download the content from the MCC.
When we select Enable the distribution point to be used as Microsoft Connected Cache server(Distribution point<Properties<Site Role<Distribution point Properties<General), this distribution point will be enabled as a Microsoft Connected Cache server and will trigger the installation of the Connected Cache server.
We may get more detailed message about the installation process of cache server by checking distmgr.log and DoincSetup.log on the machine where the DP is located.

2)If the client isn't configured correctly, or the content isn't yet cached, client will not download the content from the MCC.
Firstly we may verify if the client is configured correctly. We could Open PowerShell and run the following command: Get-DeliveryOptimizationStatus
If the BytesFromCacheServer attribute is not zero, it indicates that the client configuration is correct and the content can be cached from the Connected Cache server. Like below screenshot:
71531-22.png


If the response is helpful, please click "Accept Answer"and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.



22.png (34.1 KiB)
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

71564-image.png



MCC is working fine for store apps but not for MECM updates

I've also found this uservoice:

https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/40348321-allow-delivery-optimization-connected-cache-doi

So, is MECM able to use connected cache for update content ?



0 Votes 0 ·
image.png (12.6 KiB)
SunnyNiu-MSFT avatar image
0 Votes"
SunnyNiu-MSFT answered SunnyNiu-MSFT edited

@MichelLeclerc-0874
In order for us to solve this problem faster, we want to confirm if we have meet these prerequisites and limitations when we enable Microsoft Connected Cache in Configuration Manager: https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/hierarchy/microsoft-connected-cache#prerequisites-and-limitations

At the same time, we may need some time to try to do experiment in my lab to see if the same phenomenon occurs.


If the response is helpful, please click "Accept Answer"and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

MichelLeclerc-0874 avatar image
0 Votes"
MichelLeclerc-0874 answered

Hello,

We finally got MCC working. My issue was that the URL officecdn.microsoft.com.edgesuite.net was not allowed by the proxy.
Now setup.exe use content from the MCC to install MS Apps but MCC is not used if Office is COM enabled.

Delivery Optimization can't be used for Microsoft 365 Apps client updates if Office COM is enabled. Office COM is used by Configuration Manager to manage updates for Microsoft 365 Apps clients. You can deregister Office COM to allow the use of Delivery Optimization for Microsoft 365 Apps updates. When Office COM is disabled, software updates for Microsoft 365 Apps are managed by the default Office Automatic Updates 2.0 scheduled task. This means that Configuration Manager doesn't dictate or monitor the installation process for Microsoft 365 Apps updates. Configuration Manager will continue to collect information from hardware inventory to populate Office 365 Client Management Dashboard in the console.

I hope that MS will remove this limitation, so that we will no more have to care about content for MS Apps when managed by SCCM.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

MichelLeclerc-0874 avatar image
0 Votes"
MichelLeclerc-0874 answered MichelLeclerc-0874 published

Hello,

We finally got MCC working. My issue was that the URL officecdn.microsoft.com.edgesuite.net was not allowed by the proxy.
Now setup.exe use content from the MCC to install MS Apps but MCC is not used if Office is COM enabled.

Delivery Optimization can't be used for Microsoft 365 Apps client updates if Office COM is enabled. Office COM is used by Configuration Manager to manage updates for Microsoft 365 Apps clients. You can deregister Office COM to allow the use of Delivery Optimization for Microsoft 365 Apps updates. When Office COM is disabled, software updates for Microsoft 365 Apps are managed by the default Office Automatic Updates 2.0 scheduled task. This means that Configuration Manager doesn't dictate or monitor the installation process for Microsoft 365 Apps updates. Configuration Manager will continue to collect information from hardware inventory to populate Office 365 Client Management Dashboard in the console.

I hope that MS will remove this limitation, so that we will no more have to care about content for MS Apps when managed by SCCM.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

SunnyNiu-MSFT avatar image
0 Votes"
SunnyNiu-MSFT answered

@MichelLeclerc-0874
Thank you very much for the update and we're glad the problem is solved now.
We will try our best to feed back the information to the product team, hoping that MS will remove this limitation so that SCCM could be used better. After receiving the reply, we will reply to you as soon as possible. Thank you for your understanding.


If the response is helpful, please click "Accept Answer"and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

anjillan avatar image
0 Votes"
anjillan answered Jason-MSFT commented

I have the very same issue, MCC configuration checks all the boxes and yet M365 apps install payload still gets downloaded from CDN instead of MCC. When the installer / setup.exe starts it does try to connect to DOCacheHost and throws a few header files onto the DOINC share but then it connects to internet and downloads the rest from there. My office 365 app is being pushed via SCCM, and it doesn't make any sense to disable OfficeCOM in this scenario should I still have to do so if I have to make this work?

· 5
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

and it doesn't make any sense to disable OfficeCOM in this scenario

Why not? Using the OfficeCOM setting is explicitly for enabling ConfigMgr to handle the update process which includes downloading content by the Office c2r client during initial installation and future updates and bypassing the c2r process completely so not following why disabling it doesn't make sense?

0 Votes 0 ·

I thought without OfficeCOM enabled in the configmgr client settings we can't send out m365 apps updates via configmgr. Oh well, my understanding about this is wrong then. I will disable the setting and try it out and see if the MCC will work as expected.

Thank you Jason.

0 Votes 0 ·

That is correct. The point though is that if you are using ConfigMgr, why do you need MCC for content?

0 Votes 0 ·
Show more comments