Deploy Microsoft Connected Cache caching software to a Linux host machine

• Koskee seuraavia::

  ✅ Supported Linux distributions, ✅ Microsoft Connected Cache for Enterprise and Education

This article describes how to deploy Microsoft Connected Cache for Enterprise and Education caching software to a Linux host machine.

Before deploying Connected Cache to a Linux host machine, ensure that the host machine meets all requirements, and that you have created and configured your Connected Cache Azure resource and cache node.

Steps to deploy Connected Cache cache node to Linux

Azure portal

1. Within the Azure portal, navigate to the Provisioning tab of your cache node and copy the provisioning command.

2. Download the provisioning package using the option at the top of the Cache Node Configuration page and extract the package onto the host machine.

3. Open a command line window as administrator on the host machine, then change directory to the extracted provisioning package.

   Note

   • If you are deploying your cache node to a Linux host machine that uses a TLS-inspecting proxy (e.g. ZScaler), ensure that you've configured the proxy settings for your cache node, then place the proxy certificate file (.pem) in the extracted provisioning package directory and add proxyTlsCertificatePath="/path/to/pem/file" to the provisioning command.

4. Set access permissions to allow the provisionmcc.sh script within the provisioning package directory to execute.

5. Run the provisioning command on the host machine.

Azure CLI

To deploy a cache node programmatically, you'll need to use Azure CLI to get the cache node's provisioning details and then run the provisioning command on the host machine.

1. To get the cache node's provisioning details, use az mcc ent node get-provisioning-details

   az mcc ent node get-provisioning-details --cache-node-name mycachenode --mcc-resource-name mymccresource --resource-group myrg
   

2. Save the resulting output. These values will be passed as parameters within the provisioning command.

3. Download and extract the Connected Cache provisioning package for Linux to your host machine.

4. Open a command line window as administrator on the host machine, then change directory to the extracted provisioning package.

   Note

   • If you are deploying your cache node to a host machine that uses a TLS-inspecting proxy (e.g. ZScaler), ensure that you've configured the proxy settings for your cache node, then place the proxy certificate file (.pem) in the extracted provisioning package directory and add proxyTlsCertificatePath="/path/to/pem/file" to the provisioning command.

5. Set access permissions to allow the provisionmcc.sh script within the provisioning package directory to execute.

6. Replace the values in the following provisioning command before running it on the host machine.

   sudo ./provisionmcc.sh customerid="enter mccResourceId here" cachenodeid="enter cacheNodeId here" customerkey=" enter customerKey here " registrationkey="enter registrationKey here" drivepathandsizeingb="enter physicalPath value,enter sizeInGb value here" shoulduseproxy="enter true if present, enter false if not" proxyurl=http://enter proxy hostname:enter port
   

Steps to point Windows client devices at Connected Cache node

Once you have successfully deployed Connected Cache to your Linux host machine, you'll need to configure your Windows client devices to request Microsoft content from the Connected Cache node.

You can do this by setting the DOCacheHost or DOCacheHostSource policies via Intune.

Next step

Verify cache node functionality

Related content

• Deploy to a Windows host machine
• Uninstall Connected Cache node