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

Update mcc-isp-create-provision-deploy.md

Browse Source 
Minor update to the script run instructions to make it clearer.
This commit is contained in:
Andy Rivas
2022-11-11 10:00:54 -08:00
committed by GitHub
parent 0102682712
commit 93b418f8af
1 changed files with 8 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
windows/deployment/do/mcc-isp-create-provision-deploy.md
View File

@ -106,13 +106,18 @@ There are five IDs that the device provisioning script takes as input in order t
1. After completing cache node provisioning, navigate to the **Server provisioning** tab. Select **Download provisioning package** to download the installation package to your server.
1. Open a terminal window in the directory where you would like to deploy your cache node and run the following command to change the access permission to the Bash script:
2. Open a terminal window in the directory where you would like to deploy your cache node and run the following command to change the access permission to the Bash script:
```bash
sudo chmod +x installmcc.sh
sudo chmod +x provisionmcc.sh
```
1. Run the deployment script that is shown for your cache node in Azure portal by copying and pasting the script in your terminal. The script may take a few minutes to run. If there were no errors, you have set up your cache node successfully. To verify the server is set up correctly, follow the [verification steps](mcc-isp-verify-cache-node.md).
3. Copy and paste the script command line shown in the Azure portal.
5. Run the script in your server terminal for your cache node by . The script may take a few minutes to run. If there were no errors, you have set up your cache node successfully. To verify the server is set up correctly, follow the [verification steps](mcc-isp-verify-cache-node.md).
> [!NOTE]
> The same script can be used to provision multiple cache nodes, but the command line is unique per cache node. Additionally, if you need to reprovision your server or provision a new server or VM for the cache node, you must copy the command line from the Azure portal again as the "registrationkey" value is unique for each successful execution of the provisioning script.
### General configuration fields