--- title: "Linux-Desktop-Agent 1.2.1-Installation on GCP-Cloud" slug: "linux-desktop-agent-121-installation-on-gcp-cloud" updated: 2024-07-16T10:11:02Z published: 2024-07-16T10:11:02Z --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.workspot.com/llms.txt > Use this file to discover all available pages before exploring further. # Linux-Desktop-Agent 1.2.1-Installation on GCP-Cloud **Prerequisites:** - Make sure template VM is having unmanaged disk. - The same name of the VM cannot be use for template registration. - Tags should be added to VM, if tags are not added template cannot be register in Workspot control. - Only Ubuntu 20.04, Debian 10, Red hat 7.9 and CentOS 7.9 are supported for now. **Creation of Linux VM:** - Under VM instance page, click on create Instance option. - Enter Instance name with small letters and choose desired region/zone. - Choose Machine configuration based on your requirements. ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/1dd64fd4-9db2-4a0e-8651-ee135371f1ac.png) - Choose Image based on your requirements. We support Ubuntu 20.04 LTS, Debian 10 Bluster, CentOS 7.9 and RedHat 7.9. ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/be0d713d-b76e-4222-97fe-3898d22bc6d5.png) - Choose Networking settings based on your requirements. ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/3708c728-b7fa-43be-a6e8-bedff5432a07.png) - After all, select your choice of settings and click on the create button. - Meanwhile Open the PuTTY Gen application and follow the below steps - ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/0b4fc9f5-25f2-402c-af3b-4bba83e0e1cc.png) - Click on the Generate button. - Move the mouse to generate the key fast. ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/fe06058b-34d3-4521-af27-13b9b9108855.png) - Rename the key comment – to a name that you remember (This key will be used to login to the VM) and Click on the Save private key button. - Make sure we understand that the Key comment is going to be the username needed to log on to the desktop via SSH. - Ignore the warning message ‘are you sure you want to save this key without a passphrase to protect it’ and just save the file to a location, the file save creates a .ppk file. ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/08b19c9d-9a1f-4603-b342-b6d77fccf873.png) - Copy the whole Pubic key ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/d0da56d2-fbba-4612-92c2-f1e87b3c08b5.png) - By now VM instance in GCP might create successfully. Go to that instance. In top we have edit option click on that. ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/a17a194d-7206-49ab-bcbe-03fc33fff784.png) - Once VM is in edit mode, Go to SSH keys and click on Show and edit link ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/e9a17ca3-56ed-4a92-94ee-e48b5a2f82c0.png) - We can see empty SSH keys ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/5e7c97e2-7af3-4bb8-899e-a198c7e65d8b.png) - Paste public key which we copied from PuTTYgen. ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/faf099b4-dcdb-4f1e-a837-e7a01128027a.png) - The final step is, Save the changes. **Installation of Linux agent in VM:** - RDP windows and install putty software. ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/153aada9-19a2-4578-9f0a-32e15ec511f3.png) - Login to Linux VM from Putty ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/185433e0-7196-49ed-9ad3-2b1a7e0cb5f7.png) - Copy the private key generated before (under Create VM in GCP) to the RDP Windows machine. After giving Private IP in putty. Go to SSH > Auth > Browse ppk file location. Then Click on the Open button. ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/950875b3-b378-4dc7-a6ec-cab6cfb7ca31.png) - Give Username as Login in the terminal. - After login to Linux VM terminal, Change the root password to default password we use for admin using command – “sudo passwd root” and enter new/confirm password. ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/e6d227a4-a2bc-4fa9-a386-4b285ecdf235.png) - Below is the confirmation that the password is updated. ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/972540a6-9c39-4dd7-aefd-244ff4471f05.png) - Download installer script from URL using below command based on Linux distributor, - For Ubuntu: “curl -O https://workspotbuilds.blob.core.windows.net/product/focal/workspot_installer.sh” - For Debian: “curl -O https://workspotbuilds.blob.core.windows.net/debian/dev/workspot_installer.sh” - For CentOS/RHEL: “curl -O https://workspotbuilds.blob.core.windows.net/product/el7/workspot_installer.sh” - Once downloaded check the script is available or not. ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/51908d09-076a-4f5b-a645-88f4ca90e673.png) - Give executable permission to script **Command –**chmod +x workspot_installer.sh ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/e656e4ca-8cf1-468c-b2a4-a4e86cf38d8a.png) - Run the script using the command below. **Command -** “sudo ./workspot_installer.sh” or “sudo bash workspot_installer.sh” ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/246cd2c3-4716-4170-b1a7-389dc7c78a26.png) - Enter DNS IP if you have any - We can add multiple DNS IP addresses by separating with commas. ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/8962deb5-7d70-4937-aaa2-e7302697c1c4.png) - Choose Domain Join “Yes or No” in this screen ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/018fec35-a477-4edf-88c6-efabb66ee204.png) - After installing some dependencies, we can see Registration screen ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/7c914c83-9ded-407d-8521-3193a3313510.png) - You can choose any method of registration. - Credential Based - - Enter Control account. ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/07a04eee-1e4c-44f3-a393-d437ee609928.png) - Enter Password ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/945aaf2c-98b1-4636-b207-1d676af940a9.png) - If you choose Token Based - - Enter Token ID which we can get from Control > Setup > Configuration tab ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/df098af3-1910-4cab-8dc0-0a5c67f10200.png) - You can see registration status in terminal based on registration type. - For Credential based ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/6d517517-e861-4387-bdab-68b40ad29955.png) - For Token based ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/061770db-2c4d-43ae-9acb-fe6b52759906.png) - If Domain Join option selected as “Yes”, the below screen prompt to enter domain details - Enter domain name – like indevqa.com ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/7c87ea34-60bb-4a00-a501-5c4544c8bf76.png) - Enter OU details of domain. <> ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/893a6a8c-bbab-40e3-b000-118eac489695.png) - Enter Domain admin account. ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/14b90191-c3af-4b78-a92f-049ca4813384.png) - Enter Domain admin account password. ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/e9b9834d-59c2-45f5-b48c-9c1135ab8c5e.png) - After entering domain details, we can see below lines in terminal ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/6f515ed8-b58a-436b-9ce1-bd4c4fece652.png) - Finally, installer script will complete execution and end with the below message “system restart required”. ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/3a999f3a-05a7-4d5f-8a81-21962f2516fa.png) - As this is template VM, Stop the VM directly from GCP portal. **Image creation** - Create an image under the images tab in GCP portal using respective VM instance disk. - Select source disk of VM instance where we installed Linux agent. ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/1ef396e6-fbfa-40d3-ac7b-6e464fb26e61.png) - Go to instance template and click on Create Instance Template. Give same name as VM instance. Same machine configuration like VM instance ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/0b0b75ae-795d-4441-976e-dd4308eb1cff.png) ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/0a5fd66a-5d1d-4f36-b869-8eb590f1f39b.png) - Under Boot disk, choose Custom image which we created in above Step ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/3615f032-dff0-41b5-891f-8d52ac6837f9.png) - Same network configuration like VM instance ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/a4874e84-4b37-40c4-bdd7-eb4078b8d24d.png) - Create Instance Template. - Go to Control > Setup > Cloud > Azure Cloud and click on Register template. Choose respective resource group and give respective VM name, click on Search button. - Select the Template VM and Click on Save button. - GCP Linux Template should successfully be added to the Workspot Control.