deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-13 13:57:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

emoved e from mcce and other changes

Browse Source
This commit is contained in:
Nidhi Doshi 2024-10-03 12:20:33 -07:00
parent 4cd4f2429a
commit 5f7d994b35
5 changed files with 33 additions and 371 deletions
Show Stats 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.
-->

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

@ -21,7 +21,7 @@ This article outlines how to create and configure your Microsoft Connected Cache
## Prerequisites ## Prerequisites
1. **Azure Pay-As-You-Go subscription**: Microsoft Connected Cache is a free-of-charge service hosted in Azure. You'll need a pay-as-you-go Azure subscription in order to onboard to our service. To create a subscription, go to [pay-as-you-go subscription page](https://azure.microsoft.com/offers/ms-azr-0003p/). 1. **Azure Pay-As-You-Go subscription**: Microsoft Connected Cache is a free-of-charge service hosted in Azure. You'll need a pay-as-you-go Azure subscription in order to onboard to our service. To create a subscription, go to [pay-as-you-go subscription page](https://azure.microsoft.com/offers/ms-azr-0003p/).
2. **Hardware to host MCC**: The recommended configuration serves approximately 35,000 managed devices, downloading a 2-GB payload in 24-hour timeframe at a sustained rate of 6.5 Gbps. 2. **Hardware to host MCC**: The recommended configuration serves approximately 35,000 managed devices, downloading a 2-GB payload in 24-hour timeframe at a sustained rate of 6.5 Gbps.
For more information on sizing and OS requirements, see [the prerequisites for using MCCE](mcc-ent-prerequisites.md). For more information on sizing and OS requirements, see [the prerequisites for using MCC for Enterprise and Education](mcc-ent-prerequisites.md).
## Create MCC Azure resource ## Create MCC Azure resource
@ -60,6 +60,7 @@ For more information on sizing and OS requirements, see [the prerequisites for u
* Resource group under which an MCC resource can be created. Use the [az group create](/cli/azure/group#az-group-create) command to create a new Resource group if you don't already have one. * Resource group under which an MCC resource can be created. Use the [az group create](/cli/azure/group#az-group-create) command to create a new Resource group if you don't already have one.
#### Create MCC Azure resource #### Create MCC Azure resource
Replace the following placeholders with your own information: Replace the following placeholders with your own information:
* *\<resource-group>*: An existing resource group in your subscription. * *\<resource-group>*: An existing resource group in your subscription.
* *\<mcc-resource-name>*: A name for your Microsoft Connected Cache for Enterprise resource. * *\<mcc-resource-name>*: A name for your Microsoft Connected Cache for Enterprise resource.
@ -85,7 +86,8 @@ az mcc ent resource create --mcc-resource-name <mymccresource> --resource-group
:::image type="content" source="images/mcc-isp-provision-cache-node-numbered.png" alt-text="Screenshot of the Azure portal depicting the cache node configuration page of a cache node. This screenshot shows all of the fields you can choose to configure the cache node." lightbox="./images/mcc-isp-provision-cache-node-numbered.png"::: :::image type="content" source="images/mcc-isp-provision-cache-node-numbered.png" alt-text="Screenshot of the Azure portal depicting the cache node configuration page of a cache node. This screenshot shows all of the fields you can choose to configure the cache node." lightbox="./images/mcc-isp-provision-cache-node-numbered.png":::
--> -->
The creation of cache node might take a few minutes. Select Refresh to see your recently created cache node. The creation of cache node might take a few minutes. Select Refresh to see your recently created cache node.
Once the status changes to **Not Configured**, you can now configure your cache node. Once the cache node state changes to **Not Configured**, you can now configure your cache node.<br>
To know more about different cache node state, see [Cache node states](#cache-node-states).
# [Azure CLI](#tab/cli) # [Azure CLI](#tab/cli)
@ -112,10 +114,7 @@ az mcc ent node create --cache-node-name <mycachenode> --mcc-resource-name <mymc
>``` >```
>In the output look for cacheNodeState. If ***cacheNodeState = Not Configured***, you can continue with cache node configuration. >In the output look for cacheNodeState. If ***cacheNodeState = Not Configured***, you can continue with cache node configuration.
>If ***cacheNodeState = Registration in Progress***, then the cache node is still in process of being created. Please wait for a minute or two more and run the command again. >If ***cacheNodeState = Registration in Progress***, then the cache node is still in process of being created. Please wait for a minute or two more and run the command again.
>To know more about different cache node state, see [Cache node states](#cache-node-states).
<!-- `code blah blah`
-->
--- ---
@ -200,7 +199,7 @@ To deploy the cache node to a **Windows** host machine, see [Deploy cache node t
To deploy the cache node to a **Linux** host machine, see [Deploy cache node to Linux](mcc-ent-deploy-to-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/) ### [Azure CLI](#tab/cli/)
To deploy cache nodes using Azure CLI, see [Bulk management of cache nodes](mcc-ent-manage-cache-using-CLI.md) To deploy cache nodes using Azure CLI, see [Manage cache nodes using CLI](mcc-ent-manage-cache-using-CLI.md)
--- ---
<br> <br>
@ -247,3 +246,16 @@ You can choose to enable or disable proxy settings on your cache node.
|---|---|---| |---|---|---|
|**Proxy host name**| String or number| Proxy host name or address| |**Proxy host name**| String or number| Proxy host name or address|
|**Proxy port**| Integer| Proxy port |**Proxy port**| Integer| Proxy port
<br>
##### Cache node states
| Cache node state |Description|
|---|---|
|Creation in progress| Cache node is being created|
|Registration in progress| Cache node is being registered|
|Not configured| Cache node is ready to be configured|
|Not provisioned| Cache node is ready to be provisioned on host machine|
|Healthy| Cache node phoning home|
|Unhealthy| Cache node has stopped phoning home|
|Never phoned home| Cache node has provisioned but has never phoned home|

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

@ -20,7 +20,7 @@ ms.date: 06/03/2024
<br> <br>
This article outlines how to create, configure, and deploy Microsoft Connected Cache for Enterprise (MCCE) cache nodes using Azure CLI. This article outlines how to create, configure, and deploy Microsoft Connected Cache for Enterprise (MCC) cache nodes using Azure CLI.
## Prerequisites: ## Prerequisites:
@ -44,10 +44,10 @@ az group create --name myrg --location westus
Once the resource group is created, you'll 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 an MCCE Azure resource ### 2. Create an Azure resource
An MCCE Azure resource is a top-level Azure resource under which cache nodes can be created. An MCC Azure resource is a top-level Azure resource under which cache nodes can be created.
To create an MCCE Azure resource, use `az mcc ent resource create` To create an MCC Azure resource, use `az mcc ent resource create`
```azurecli-interactive ```azurecli-interactive
az mcc ent resource create --mcc-resource-name mymccresource --resource-group myrg az mcc ent resource create --mcc-resource-name mymccresource --resource-group myrg
@ -108,19 +108,9 @@ az mcc ent node update --cache-node-name <mycachenode> --mcc-resource-name <mymc
``` ```
>[!Note] >[!Note]
>For a cache node that is to be deployed on Windows host OS, the physical path of the cache drive must be **/var/mcc**. >* For a cache node that is to be deployed on Windows host OS, the physical path of the cache drive <u>must</u> be **/var/mcc**.<br>
<br> >* In the output, look for operationStatus. **operationStatus = Succeeded** indicates that our services have successfully updated the cache node. You will also see that cacheNodeState will show "Not Provisioned". <br>
>* Please save values for <u>physicalPath, sizeInGb, proxyPort, proxyHostName</u> as these values will be needed to construct the provisioning script.
>[!NOTE]
>Proxy info changes, required to provision cache node.
<br>
>[!IMPORTANT]
>In the output, look for operationStatus. **operationStatus = Succeeded** indicates that our services have successfully updated the cache node.
<br>
>[!IMPORTANT]
>Please save values for physicalPath, sizeInGb, proxyPort, proxyHostName as these values will be needed to create the provisioning script.
<br> <br>
@ -136,71 +126,35 @@ az mcc ent node get-provisioning-details --cache-node-name mycachenode --mcc-res
Save the resulting values for cacheNodeId, customerKey, mccResourceId, registrationKey. These GUIDs 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. Deploy cache node
<br> <br>
### 7. Deploy cache node
#### Deploy cache node to Linux host machine #### 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) 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 following link to download and extract the Linux-compatible MCCE provisioning package onto the host machine. Use the following link to download and extract the Linux-compatible MCCE provisioning package onto the host machine.
[Download MCCE provisioning package for Linux host machine](https://aka.ms/MCC-Ent-InstallScript-Linux) [Download MCC provisioning package for Linux host machine](https://aka.ms/MCC-Ent-InstallScript-Linux)
<br> <br>
>[!IMPORTANT] To deploy the cache node to a **Linux** host machine, see [Deploy cache node to Linux](mcc-ent-deploy-to-linux.md)
>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
```
Replace the values in the following provisioning command before running it.<br>
```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> <br>
>[!IMPORTANT]
>'shoulduseproxy' parameter is required, whether or not your network uses proxy to access internet.
#### Deploy cache node to Windows host machine #### 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) 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. 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) [Download MCC provisioning package for Windows host machine](https://aka.ms/MCC-Ent-InstallScript-WSL)
<br> <br>
>[!IMPORTANT] To deploy the cache node to a **Windows** host machine, see [Deploy cache node to Windows](mcc-ent-deploy-to-windows.md)
>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'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
```
<br> <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
```
<br>
>[!IMPORTANT]
>'shoulduseproxy' parameter is required, whether or not your network uses proxy to access internet.
## Next step ## Next step
To verify cache node functionality, see [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)

6
windows/deployment/do/mcc-ent-prerequisites.md
View File

@ -23,11 +23,6 @@ This article details the requirements and recommendations for using Microsoft Co
If you don't have an Azure subscription already, you can create an Azure [pay-as-you-go](https://azure.microsoft.com/offers/ms-azr-0003p/) account, which requires a credit card for verification purposes. For more information, see the [Azure Free Account FAQ](https://azure.microsoft.com/free/free-account-faq/). If you don't have an Azure subscription already, you can create an Azure [pay-as-you-go](https://azure.microsoft.com/offers/ms-azr-0003p/) account, which requires a credit card for verification purposes. For more information, see the [Azure Free Account FAQ](https://azure.microsoft.com/free/free-account-faq/).
<<<<<<< HEAD
The resources used for the preview and in the future when this product is ready for production will be free to you, like other caching solutions.
1. **Hardware to host MCC**: The recommended configuration serves approximately 35,000 managed devices, downloading a 2-GB payload in 24-hour timeframe at a sustained rate of 6.5 Gbps.
=======
The Azure resources used for MCCE will be free to you during this public preview. The Azure resources used for MCCE will be free to you during this public preview.
- **E3/E5 or A3/A5 license**: Your organization must have one of the following license subscriptions for each device that downloads content from an MCCE cache node. - **E3/E5 or A3/A5 license**: Your organization must have one of the following license subscriptions for each device that downloads content from an MCCE cache node.
@ -75,4 +70,3 @@ This article details the requirements and recommendations for using Microsoft Co
|Disk | SSD <br>1 drive <br>50 GB each |SSD <br>1 drive <br>200 GB each | |Disk | SSD <br>1 drive <br>50 GB each |SSD <br>1 drive <br>200 GB each |
|Memory | 4 GB | 8 GB | |Memory | 4 GB | 8 GB |
|Cores | 4 | 8 | |Cores | 4 | 8 |
>>>>>>> baff7906fe02b76b4a3649d7e6c3acdac9534e66