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

additional edits, acrolinx

Browse Source
This commit is contained in:
chrisjlin
2024-09-27 15:36:51 -07:00
parent 581ff2d30c
commit 6747a66585
6 changed files with 56 additions and 356 deletions
Download Patch File Download Diff File Expand all files Collapse all files

149
windows/deployment/do/mcc-ent-configure-provision-linux.md
View File

@ -1,149 +0,0 @@
---
title: MCC for Enterprise provision Linux cache node
description: Microsoft Connected Cache for Enterprise. Learn about how to provision Linux cache node.
ms.service: windows-client
ms.subservice: itpro-updates
ms.topic: how-to
manager: aaroncz
ms.author: nidos
author: doshnid
ms.reviewer: mstewart
ms.collection: tier3
appliesto:
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise</a>
ms.date: 06/03/2024
---
<!--
Remove all the comments in this template before you sign-off or merge to the main branch.
This template provides the basic structure of a How-to article pattern. See the
[instructions - How-to](../level4/article-how-to-guide.md) in the pattern library.
You can provide feedback about this template at: https://aka.ms/patterns-feedback
How-to is a procedure-based article pattern that show the user how to complete a task in their own environment. A task is a work activity that has a definite beginning and ending, is observable, consist of two or more definite steps, and leads to a product, service, or decision.
-->
<!-- 1. H1 -----------------------------------------------------------------------------
Required: Use a "<verb> * <noun>" format for your H1. Pick an H1 that clearly conveys the task the user will complete.
For example: "Migrate data from regular tables to ledger tables" or "Create a new Azure SQL Database".
* Include only a single H1 in the article.
* Don't start with a gerund.
* Don't include "Tutorial" in the H1.
-->
# "<verb> * <noun>"
TODO: Add your heading
<!-- 2. Introductory paragraph ----------------------------------------------------------
Required: Lead with a light intro that describes, in customer-friendly language, what the customer will do. Answer the fundamental “why would I want to do this?” question. Keep it short.
Readers should have a clear idea of what they will do in this article after reading the introduction.
* Introduction immediately follows the H1 text.
* Introduction section should be between 1-3 paragraphs.
* Don't use a bulleted list of article H2 sections.
Example: In this article, you will migrate your user databases from IBM Db2 to SQL Server by using SQL Server Migration Assistant (SSMA) for Db2.
-->
TODO: Add your introductory paragraph
<!---Avoid notes, tips, and important boxes. Readers tend to skip over them. Better to put that info directly into the article text.
-->
<!-- 3. Prerequisites --------------------------------------------------------------------
Required: Make Prerequisites the first H2 after the H1.
* Provide a bulleted list of items that the user needs.
* Omit any preliminary text to the list.
* If there aren't any prerequisites, list "None" in plain text, not as a bulleted item.
-->
## Prerequisites
TODO: List the prerequisites
<!-- 4. Task H2s ------------------------------------------------------------------------------
Required: Multiple procedures should be organized in H2 level sections. A section contains a major grouping of steps that help users complete a task. Each section is represented as an H2 in the article.
For portal-based procedures, minimize bullets and numbering.
* Each H2 should be a major step in the task.
* Phrase each H2 title as "<verb> * <noun>" to describe what they'll do in the step.
* Don't start with a gerund.
* Don't number the H2s.
* Begin each H2 with a brief explanation for context.
* Provide a ordered list of procedural steps.
* Provide a code block, diagram, or screenshot if appropriate
* An image, code block, or other graphical element comes after numbered step it illustrates.
* If necessary, optional groups of steps can be added into a section.
* If necessary, alternative groups of steps can be added into a section.
-->
## "\<verb\> * \<noun\>"
TODO: Add introduction sentence(s)
[Include a sentence or two to explain only what is needed to complete the procedure.]
TODO: Add ordered list of procedure steps
1. Step 1
1. Step 2
1. Step 3
## "\<verb\> * \<noun\>"
TODO: Add introduction sentence(s)
[Include a sentence or two to explain only what is needed to complete the procedure.]
TODO: Add ordered list of procedure steps
1. Step 1
1. Step 2
1. Step 3
## "\<verb\> * \<noun\>"
TODO: Add introduction sentence(s)
[Include a sentence or two to explain only what is needed to complete the procedure.]
TODO: Add ordered list of procedure steps
1. Step 1
1. Step 2
1. Step 3
<!-- 5. Next step/Related content------------------------------------------------------------------------
Optional: You have two options for manually curated links in this pattern: Next step and Related content. You don't have to use either, but don't use both.
- For Next step, provide one link to the next step in a sequence. Use the blue box format
- For Related content provide 1-3 links. Include some context so the customer can determine why they would click the link. Add a context sentence for the following links.
-->
## Next step
TODO: Add your next step link(s)
> [!div class="nextstepaction"]
> [Write concepts](article-concept.md)
<!-- OR -->
## Related content
TODO: Add your next step link(s)
- [Write concepts](article-concept.md)
<!--
Remove all the comments in this template before you sign-off or merge to the main branch.
-->

149
windows/deployment/do/mcc-ent-configure-provision-windows.md
View File

@ -1,149 +0,0 @@
---
title: MCC for Enterprise provision Windows cache node
description: Microsoft Connected Cache for Enterprise. Learn about how to provision Windows cache node.
ms.service: windows-client
ms.subservice: itpro-updates
ms.topic: how-to
manager: aaroncz
ms.author: nidos
author: doshnid
ms.reviewer: mstewart
ms.collection: tier3
appliesto:
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise</a>
ms.date: 06/03/2024
---
<!--
Remove all the comments in this template before you sign-off or merge to the main branch.
This template provides the basic structure of a How-to article pattern. See the
[instructions - How-to](../level4/article-how-to-guide.md) in the pattern library.
You can provide feedback about this template at: https://aka.ms/patterns-feedback
How-to is a procedure-based article pattern that show the user how to complete a task in their own environment. A task is a work activity that has a definite beginning and ending, is observable, consist of two or more definite steps, and leads to a product, service, or decision.
-->
<!-- 1. H1 -----------------------------------------------------------------------------
Required: Use a "<verb> * <noun>" format for your H1. Pick an H1 that clearly conveys the task the user will complete.
For example: "Migrate data from regular tables to ledger tables" or "Create a new Azure SQL Database".
* Include only a single H1 in the article.
* Don't start with a gerund.
* Don't include "Tutorial" in the H1.
-->
# "<verb> * <noun>"
TODO: Add your heading
<!-- 2. Introductory paragraph ----------------------------------------------------------
Required: Lead with a light intro that describes, in customer-friendly language, what the customer will do. Answer the fundamental “why would I want to do this?” question. Keep it short.
Readers should have a clear idea of what they will do in this article after reading the introduction.
* Introduction immediately follows the H1 text.
* Introduction section should be between 1-3 paragraphs.
* Don't use a bulleted list of article H2 sections.
Example: In this article, you will migrate your user databases from IBM Db2 to SQL Server by using SQL Server Migration Assistant (SSMA) for Db2.
-->
TODO: Add your introductory paragraph
<!---Avoid notes, tips, and important boxes. Readers tend to skip over them. Better to put that info directly into the article text.
-->
<!-- 3. Prerequisites --------------------------------------------------------------------
Required: Make Prerequisites the first H2 after the H1.
* Provide a bulleted list of items that the user needs.
* Omit any preliminary text to the list.
* If there aren't any prerequisites, list "None" in plain text, not as a bulleted item.
-->
## Prerequisites
TODO: List the prerequisites
<!-- 4. Task H2s ------------------------------------------------------------------------------
Required: Multiple procedures should be organized in H2 level sections. A section contains a major grouping of steps that help users complete a task. Each section is represented as an H2 in the article.
For portal-based procedures, minimize bullets and numbering.
* Each H2 should be a major step in the task.
* Phrase each H2 title as "<verb> * <noun>" to describe what they'll do in the step.
* Don't start with a gerund.
* Don't number the H2s.
* Begin each H2 with a brief explanation for context.
* Provide a ordered list of procedural steps.
* Provide a code block, diagram, or screenshot if appropriate
* An image, code block, or other graphical element comes after numbered step it illustrates.
* If necessary, optional groups of steps can be added into a section.
* If necessary, alternative groups of steps can be added into a section.
-->
## "\<verb\> * \<noun\>"
TODO: Add introduction sentence(s)
[Include a sentence or two to explain only what is needed to complete the procedure.]
TODO: Add ordered list of procedure steps
1. Step 1
1. Step 2
1. Step 3
## "\<verb\> * \<noun\>"
TODO: Add introduction sentence(s)
[Include a sentence or two to explain only what is needed to complete the procedure.]
TODO: Add ordered list of procedure steps
1. Step 1
1. Step 2
1. Step 3
## "\<verb\> * \<noun\>"
TODO: Add introduction sentence(s)
[Include a sentence or two to explain only what is needed to complete the procedure.]
TODO: Add ordered list of procedure steps
1. Step 1
1. Step 2
1. Step 3
<!-- 5. Next step/Related content------------------------------------------------------------------------
Optional: You have two options for manually curated links in this pattern: Next step and Related content. You don't have to use either, but don't use both.
- For Next step, provide one link to the next step in a sequence. Use the blue box format
- For Related content provide 1-3 links. Include some context so the customer can determine why they would click the link. Add a context sentence for the following links.
-->
## Next step
TODO: Add your next step link(s)
> [!div class="nextstepaction"]
> [Write concepts](article-concept.md)
<!-- OR -->
## Related content
TODO: Add your next step link(s)
- [Write concepts](article-concept.md)
<!--
Remove all the comments in this template before you sign-off or merge to the main branch.
-->

8
windows/deployment/do/mcc-ent-create-resource-and-cache.md
View File

@ -195,17 +195,17 @@ az mcc ent node update --cache-node-name <mycachenode> --mcc-resource-name <mymc
---
## Next step
The next step is to provision the cache node on the server.
The next step is to deploy the cache node to the host machine.
# [Azure portal](#tab/portal)
To provision MCC on **Windows** host machine, see [Provision Windows cache node](mcc-ent-configure-provision-windows.md)
To deploy the cache node to a **Windows** host machine, see [Deploy cache node to Windows](mcc-ent-deploy-to-windows.md)
<br>
To provision MCC on **Linux** host machine, see [Provision Linux cache node](mcc-ent-configure-provision-linux.md)
To deploy the cache node to a **Linux** host machine, see [Deploy cache node to Linux](mcc-ent-deploy-to-linux.md)
# [Azure CLI](#tab/cli/)
To provision cache node using Azure CLI, see [Bulk management of cache nodes](mcc-ent-manage-cache-using-CLI.md)
To deploy cache nodes using Azure CLI, see [Bulk management of cache nodes](mcc-ent-manage-cache-using-CLI.md)
---
<br>

4
windows/deployment/do/mcc-ent-deploy-linux.md → windows/deployment/do/mcc-ent-deploy-to-linux.md
View File

@ -13,13 +13,13 @@ appliesto:
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>
---
# Deploy your Connected Cache to a Linux host machine
# Deploy MCCE cache node to a Linux host machine
This article describes how to deploy Microsoft Connected Cache for Enterprise and Education (MCCE) caching software to a Linux host machine.
Before deploying MCCE to a Linux host machine, ensure that the host machine meets all [requirements](mcc-enterprise-prerequisites.md), and that you have [created and configured your MCC Azure resource](https://aka.ms/mccent-create-resources).
## Steps to deploy MCCE to Linux
## Steps to deploy MCCE cache node to Linux
1. Within the Azure portal, navigate to the "Provisioning" tab of your cache node and copy the provisioning command.
1. Download the provisioning package using the button at the top of the Cache Node Configuration page and extract the package onto the host machine.

4
windows/deployment/do/mcc-ent-deploy-windows.md → windows/deployment/do/mcc-ent-deploy-to-windows.md
View File

@ -13,7 +13,7 @@ appliesto:
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>
---
# Deploy your Connected Cache to a Windows host machine
# Deploy MCCE cache node to a Windows host machine
This article describes how to deploy Microsoft Connected Cache for Enterprise and Education (MCCE) caching software to a Windows host machine.
@ -21,7 +21,7 @@ Deploying MCCE to a Windows host machine requires designating a [Group Managed S
Before deploying MCCE to a Windows host machine, ensure that the host machine meets all [requirements](mcc-enterprise-prerequisites.md), and that you have [created and configured your MCC Azure resource](https://aka.ms/mccent-create-resources).
## Steps to deploy MCCE to Windows
## Steps to deploy MCCE cache node to Windows
1. Within the Azure portal, navigate to the "Provisioning" tab of your cache node and copy the provisioning command.
1. Download the provisioning package using the button at the top of the Cache Node Configuration page and extract the package onto the host machine.

98
windows/deployment/do/mcc-ent-manage-cache-using-CLI.md
View File

@ -20,7 +20,7 @@ ms.date: 06/03/2024
<br>
This article outlines how to create, configure and provision your Microsoft Connected Cache for Enterprise cache nodes using Azure CLI.
This article outlines how to create, configure, and deploy Microsoft Connected Cache for Enterprise (MCCE) cache nodes using Azure CLI.
## Prerequisites:
@ -34,20 +34,20 @@ This article outlines how to create, configure and provision your Microsoft Conn
The first step is to create a resource group if you don't already have one.
An Azure resource group is a logical container into which Azure resources are deployed and managed.
To create a resource group, use [az group create](/cli/azure/group#az-group-create).
To create a resource group, use `az group create`. You can find more details on this CLI command [here](/cli/azure/group#az-group-create).
<br>
```azurecli-interactive
az group create --name myrg --location westus
```
Once the resource group is created, you will need to create a Microsoft Connected Cache for Enterprise resource.
Once the resource group is created, you'll need to create a Microsoft Connected Cache for Enterprise resource.
### 2. Create a MCC resource
A MCC resource is a resource under which cache nodes can be created.
### 2. Create an MCCE Azure resource
An MCCE Azure resource is a top-level Azure resource under which cache nodes can be created.
To create a mcc resource, use az mcc ent resource create
To create an MCCE Azure resource, use `az mcc ent resource create`
```azurecli-interactive
az mcc ent resource create --mcc-resource-name mymccresource --resource-group myrg
@ -64,7 +64,7 @@ The next step is to create a cache node under this resource.
### 3. Create a cache node
To create a cache node, use az mcc ent node create
To create a cache node, use `az mcc ent node create`
```azurecli-interactive
az mcc ent node create --cache-node-name mycachenode --mcc-resource-name mymccresource --resource-group myrg --host-os linux
@ -78,8 +78,9 @@ az mcc ent node create --cache-node-name mycachenode --mcc-resource-name mymccre
<br>
### 4. Confirm cache node creation
Before you can start configuring your cache node, you need to confirm that cache node creation has been successful.
To confirm cache node creation, use az mcc ent node show
Before you can start configuring your cache node, you need to confirm that the cache node was successfully created.
To confirm cache node creation, use `az mcc ent node show`
<br>
@ -93,11 +94,11 @@ az mcc ent node show --cache-node-name mycachenode --mcc-resource-name mymccreso
<br>
Once the cache node has been created successfully, you can now configure the cache node.
Once successful cache node creation is confirmed, you can proceed to configure the cache node.
### 5. Configure cache node
To configure your cache node, use az mcc ent node update
To configure your cache node, use `az mcc ent node update`
The below example configures a Linux cache node with proxy enabled:
@ -125,68 +126,59 @@ az mcc ent node update --cache-node-name <mycachenode> --mcc-resource-name <mymc
<br>
### 6. Get provisioning details for the cache node
Now that you have configured the cache node, the next step is to provision the cache node on the server. To provision the cache node, you will need to create a provisioning script with relevant information.
To get the relevant information for provisioning script, use az mcc ent node get-provisioning-details
After successfully configuring the cache node, the next step is to deploy the cache node to a host machine. To deploy the cache node, you'll need to create a provisioning script with relevant information.
To get the relevant information for provisioning script, use `az mcc ent node get-provisioning-details`
```azurecli-interactive
az mcc ent node get-provisioning-details --cache-node-name mycachenode --mcc-resource-name mymccresource --resource-group myrg
```
In the output, please save the values for cacheNodeId, customerKey, mccResourceId, registrationKey. These values are needed to create the provisioning script.
Save the resulting values for cacheNodeId, customerKey, mccResourceId, registrationKey. These GUIDs are needed to create the provisioning script.
### 7. Provisioning cache node
### 7. Deploy cache node
<br>
#### Provisioning cache node on Linux host OS:
Before you provision your cache node on Linux machine, please make sure you have completed the requisites listed here: Host machine requirements
#### Deploy cache node to Linux host machine
Before you deploy your cache node to a Linux host machine, make sure you have met the prerequisites listed here: [Host machine requirements](mcc-ent-prerequisites.md)
Use the link below to download and unzip the provisioning package on the server and run the below script to provision your cache node.
Use the following link to download and extract the Linux-compatible MCCE provisioning package onto the host machine.
[Download MCC package for Linux host OS](https://aka.ms/MCC-Ent-InstallScript-Linux)
[Download MCCE provisioning package for Linux host machine](https://aka.ms/MCC-Ent-InstallScript-Linux)
<br>
>[!IMPORTANT]
>Note: before you execute the script, please make sure you change access permissions by running the command below <br>
>```azurepowershell-interactive
>sudo chmod +x provisionmcc.sh
>```
>Before you execute the provisioning command, make sure you change directory to the extracted provisioning package and set the script execution permissions by running the command below.
```azurepowershell-interactive
sudo chmod +x provisionmcc.sh
```
<br>
Replace the values in the following provisioning command before running it.<br>
>[!NOTE]
>Please replace the sample values in the script below with the values that you saved in the step 5 and 6.
<br>
>[!IMPORTANT]
>'shoulduseproxy' parameter is required, whether or not your network uses proxy to access internet.
<br>
Provisioning script:<br>
`powershell-interactive
```azurepowershell-interactive
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="true" proxyurl=http://enter proxy hostname:enter port
`
```
<br>
#### Provisioning cache node on Windows host OS:
Before you provision your cache node on Windows, make sure you have completed the requisites listed here: [Host machine requirements](mcc-ent-prerequisites.md)
Please download and unzip the provisioning package on the server and run the below script to provision your cache node.
Note: Please replace the sample values with the values that you saved in the above steps.
>[!IMPORTANT]
>'shoulduseproxy' parameter is required, whether or not your network uses proxy to access internet.
#### Deploy cache node to Windows host machine
Before you deploy your cache node to a Windows host machine, make sure you have met the prerequisites listed here: [Host machine requirements](mcc-ent-prerequisites.md)
Use the following link to download and extract the Windows-compatible MCCE provisioning package onto the host machine.
[Download MCCE provisioning package for Windows host machine](https://aka.ms/MCC-Ent-InstallScript-WSL)
<br>
[Download MCC package for Windows host OS](https://aka.ms/MCC-Ent-InstallScript-WSL)
<br>
>[!IMPORTANT]
>Before you execute the provisioning command, make sure you change directory to the extracted provisioning package and set the script execution permissions by running the command below.
```azurepowershell-interactive
Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process
```
If you are using a **gmsa** account:<br>
If you're using a **Group Managed Service Account**, replace the values in the following provisioning command before running it.<br>
```powershell-interactive
./provisionmcconwsl.ps1 -installationFolder c:\mccwsl01 -customerid enter mccResourceId here -cachenodeid enter cacheNodeId here -customerkey enter customerKey here -registrationkey enter registration key -cacheDrives "/var/mcc,enter drive size" -shouldUseProxy $true -proxyurl " http://enter proxy host name:enter port" -mccRunTimeAccount $User
@ -194,7 +186,10 @@ If you are using a **gmsa** account:<br>
<br>
If you are using **local user account** or **domain user account**:<br>
>[!IMPORTANT]
>'shoulduseproxy' parameter is required, whether or not your network uses proxy to access internet.
If you're using **Local User account** or **Domain User account**, replace the values in the following provisioning command before running it.<br>
```powershell-interactive
./provisionmcconwsl.ps1 -installationFolder c:\mccwsl01 -customerid enter mccResourceId here -cachenodeid enter cacheNodeId here -customerkey enter customerKey here -registrationkey enter registration key -cacheDrives "/var/mcc,enter drive size" -shouldUseProxy $true -proxyurl " http://enter proxy host name:enter port" -mccRunTimeAccount $User -mccLocalAccountCredential $myLocalAccountCredential
@ -202,10 +197,13 @@ If you are using **local user account** or **domain user account**:<br>
<br>
>[!IMPORTANT]
>'shoulduseproxy' parameter is required, whether or not your network uses proxy to access internet.
## Next step
To verify cache node functionality, visit, [Verify cache node functionality](mcc-ent-verify-cache-node.md)
To verify cache node functionality, see [Verify cache node functionality](mcc-ent-verify-cache-node.md)
<br>