Signup for itopia and Google Cloud here
- Login to itopia and create a new deployment. Click All deployments from the main menu and click the green + sign
If you already created a deployment, select it from the "Deployments" menu on the top left. You will get the option to continue the deployment in the Dashboard. The system will resume your deployment at the same step where you left off.
Click the "Continue" button
2. Select Remote Desktop Services as the deployment type, then type the Name of your deployment. The deployment code will be generated automatically. If you prefer to define your own code, uncheck the "Autogenerate Code" box and Type your code (we allow from 3 to 8 characters). Click Create.
3. Select your deployment configuration
Select "New domain" option and provide Internal DNS name. It's a name for your Active Directory Domain, it cannot resolve to an existing domain (e.g. name.local)
Operating System: if you select 2012, users will get Windows 8 experience, with 2016 or newer you'll get Windows 10 end user experience
Secondary Domain Controller: Enabling the option will create Backup Domain Controller server that you can schedule to only turn on for 1 hour a day to synchronize the database with the primary domain controller.
Username suffix: is the username login identifier (the portion of the username after the @ sign) that will be used by end users when logging in to Cloud desktop. (i.e. username@sufix)
External DNS: A real domain or subdomain you own is needed here since you will input DNS entries with your registrar later.
We require the DNS to make the configuration of the RDP file easier. The system configures the RDP files for end users with a subdomain of your external domain so once the Deployment is launched to Cloud, you will create a DNS record for the subdomain pointing to the session host / gateway server IP so the preconfigured RDP files can work correctly (instructions to do the above are received via email).
Estimated No. of users: put the number of users that are expected to be created for this deployment so we can give you more accurate Google cost estimate in the last step. The number is also used later to configure RDS licensing.
Dedicated File Server: dedicated file server will be created. No end users sessions will be hosted in the server, it will host only data. A separate server will be created for end user sessions.
If the option is not selected, files will be hosted in session host server.
RD Gateway: provides you higher security for your Cloud connection. If enabled, you will get a task to input RD Gateway certificate (SSL) in .pfx format and a password after the provisioning. Make sure you request wildcard SSL cert or check with itopia support for the correct hostname for your certificate in case you are requesting a different SSL certificate type.
Redundant Gateway: Another server with the gateway role will be deployed and the system will configure Google Load Balancer
Dedicated RD Broker: Broker role will be configured in a dedicated server. If the option is not selected, the broker will be combined with the session host server
User Profile Disk: If enabled, user profile configuration will take advantage of user profile disk technology. If you prefer other configuration for user profiles, you can disable User Profile Disk option and manually setup a different configuration of your choice for user profiles.
Once all the above fields are populated, click Next.
4. Select your GCP settings
Authenticate with your GCP account. The system will ask you for your Google email address and password. Make sure to use the same one you used to sign up for Google Cloud.
Then select a project that will be associated with your deployment. It will appear in the drop-down list so you can select it.
Note: It's recommended to use a clean project for the deployment that doesn't contain other servers or custom configurations.
If you want to create a new project for your deployment, select "Create new project" option from the drop down.
5. Enable APIs
The APIs need to be enabled for the project. They allow itopia software to integrate and communicate with your Google infrastructure.
The system will try to enable the API's automatically. In case any of the API's stays disabled, click on the "Enable" or "Add" button next to it and you will be redirected to a new tab in Google Cloud Platform. In Google tab, click Enable button located in the top of the screen.
Once enabled, the button will change to "Disable"
The software is also checking the IP quota restriction. The system will confirm if your Google account is upgraded. Without upgrading the GCP account you would only have access to a limited number of static IPs that may not be enough for a basic deployment in itopia.
In https://console.cloud.google.com/ click on the UPGRADE button in the top right corner to upgrade your account. If you don't see such button in the IP quota tab, it means that your account was already upgraded.
After you enable the APIs in Google, you can click on the refresh buttons next to each API.
APIs will turn green to confirm they were enabled so you can continue to the Region selection below.
6. Select your GCP Region(s)
In case you're launching a deployment hosted in multiple regions. Add all of them in this step.
Companies with multiple sites located in different states, countries or continents can now be deployed under single domain with their environment created in Google datacenter that's close to their physical location.
Just select the region and add it clicking "ADD REGION" button.
On the bottom of the screen you can check the instances that will be created. You can add additional instances like app/ web/ database servers clicking on the green plus sign on the right.
If you need to edit resources (RAM/ CPU) on any other selected instance, just click the pencil icon:
At this step, hovering your mouse over the green + sign on the right, you can also import any existing app/ web/ database servers to your itopia deployment. They must be part of the GCP project that you selected in the previous steps. Learn how to import existing GCP servers here.
Once done, click Next and you'll get the summary of your settings
7. Check if your selected settings are correct and confirm the disclaimer.
Under the settings summary and just above the disclaimer message, you will see Google infrastructure cost estimate to give you an idea of the approximate Google cost for your selected settings after you spend your free credits. The estimate shows two scenarios, one if you leave your servers on 24/7 or just 14 hours from Monday to Friday.
Once confirmed, check the disclaimer in the bottom and click "DEPLOY" button in the bottom right lo launch the deployment to Cloud.
The Deployment Process
After the deployment is saved, you can see Provisioning Status in itopia CAS after clicking on your deployment dashboard and watch how Google servers are being automatically deployed and configured.
After the automatic server configuration is complete, you will receive an email with server admin credentials to be able to connect to your servers.
You can now go to itopia - Tasks section where you will see 2 provision tasks to be completed manually. After both tasks are marked complete, you will receive a link to download RDP file so users can connect to their cloud desktop.
IMPORTANT: Don't turn off your servers before the provisioning process has fully completed.
If you deploy your servers directly in Google, you will not be able to manage them from itopia.
- Importing SSL cert for RD Gateway (if RD Gateway was enabled)
- Add DNS record to configure your RDP file.
- Run the PC discovery tool or Network discovery to inventory data in the existing environment (optional)
Note: If you'd like to build your remote desktop deployment extending your existing AD rather than creating a new domain, look at this article.