deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-15 18:33:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

more content to faqs

Browse Source
This commit is contained in:
Nidhi Doshi
2024-10-10 14:36:35 -07:00
parent a1fc2766cf
commit 8842ede9a2
1 changed files with 13 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
windows/deployment/do/mcc-ent-faq.yml
View File

@ -50,8 +50,10 @@ sections:
answer: You can monitor your cache node usage on Azure portal. For more information see [Monitor cache node usage Info on Reporting Capabilities](mcc-ent-monitoring.md).
- question: Does Microsoft Connected Cache support Xbox or Teams content?
answer: Currently, Microsoft Connected Cache doesn't support Xbox or Teams content. However, supporting Xbox content is of high priority, and we expect this feature soon. We'll let you know as soon as it becomes available!
- question: How does Microsoft Connected Cache populate its content?
answer: Microsoft Connected Cache is a cold cache warmed by client requests. The client requests content and that is what fills up the cache. There's no off-peak cache fill necessary. Microsoft Connected Cache will reach out to different CDN providers just like a client device would. The traffic flow from Microsoft Connected Cache will vary depending on how you currently transit to each of these CDN providers. The content can come from third party CDNs or from AFD.
- question: How does Microsoft Connected Cache populate its content? Can I pre-cache content?
answer: Microsoft Connected Cache is a cold cache warmed by client requests at the byte range level so your clients only request the content they need. The client requests content and that is what fills the cache which means there is no cache fill necessary. "Pre-seeding" can be achieved but use of update rings. A test ring or early adopter ring can be used to fill the cache and all subsequent requests by other clients will come from cache.
- question: How long would a piece of content live within the Microsoft Connected Cache? Is content purged from the cache?
answer: Once a request for said content is made, NGINX looks at the cache control headers from the original acquisition. If that content is expired, NGINX continues to serve the stale content while it's downloading the new content. We cache the content for 30 days. The content will be in the hot cache path (open handles and such) for 24 hrs, but will reside on disk for 30 days. The drive fills up and nginx will start to delete content based on its own algorithm, probably some combination of least recently used.
- question: Is it possible to not update the Microsoft Connected Cache software or delay update longer than the timeline provided in the updates configuration?
answer: No. It is important to keep the Microsoft Connected Cache software up to date, especially when it comes to security issues. Microsoft has validated updates prior to releasing Microsoft releasing to Enterprises Connected Cache updates and will only release updates when it is necessary to keep customers secure or to ensure the continued successful operation of Connected Cache nodes for customers.
- question: How do I set up CLI?
@ -59,4 +61,12 @@ sections:
- question: How do I install MCC extension?
answer: Please see [Install the Microsoft Connected Cache extension](mcc-ent-install-extension.md).
- question: What do I do if I have to set up or change existing proxy?
answer: You can enable proxy and provide proxy information on Azure portal or use CLI. Don’t forget to re-run the provisioning script after making any proxy changes. Please see [Set up or change existing proxy](mcc-ent-proxy.md).
answer: You can enable proxy and provide proxy information on Azure portal or use CLI. Don’t forget to re-run the provisioning script after making any proxy changes. Please see [Set up or change existing proxy](mcc-ent-proxy.md).
- question: How do we set up Microsoft Connected Cache if we support multiple countries or regions?
answer: Microsoft Connected Cache is not a service that has dependency on a specific Azure region, and there is not personal or organizational identifiable information stored in the resource that necessitates data residency. The three regions that the Connected Cache resource can be deployed to are (Europe) North Europe, (Asia Pacific) Korea Central, and (US) West US.
- question: Should I use a gMSA, local user, or domain account to deploy Microsoft Connected Cache to Windows?
answer: There are pros and cons to the account options available to customers. We anticipate that security and manageability will be top priories for customers. Microsoft has provided guidance on both Active Directory/Entra-based service accounts ([Introduction to Active Directory service accounts - Choose the right type of service account](/entra/architecture/service-accounts-on-premises#types-of-on-premises-service-accounts)) and user-based service accounts ([Secure user-based service accounts in Active Directory - Microsoft Entra | Microsoft Learn)](/entra/architecture/service-accounts-user-on-premises#assess-on-premises-user-account-security).
- question: Does the user have to be logged using the account that installed Microsoft Connected Cache on Windows or Linux?
answer: No. As part of the installation on Windows a scheduled task is created using the account used to install Connected Cache. Regardless of which user is logged in or not logged in, the schedule task will remain running. On Linux Connected Cache is installed by the user and remains running regardless of which user is logged in to the OS..
- question: What do I do if I need more support and have more questions even after reading this FAQ page?
answer: For further support for Microsoft Connected Cache, visit [Troubleshooting issues for Microsoft Connected Cache for Enterprise and Education](mcc-ent-support-and-troubleshooting.md). If you still need more support, you can contact customer support.