The purpose of this document is to outline the process to provision a Rimo3 tenant via the Azure Marketplace.
Overview
Deploying Rimo3 resources into you Azure subscription consists of 4 stages:
- Deploy Azure Resources - In this stage, you will generate a Registration Key and complete the Rimo3 Marketplace Offering (MPO).
- Deploy Rimo3 Agents - This fully automated stage tracks the deployment progress based on the MPO options, typically including a dedicated resource group, virtual network, subnet, storage account, key vault, and virtual machine, where the Rimo3 Agents will also be installed and registered as part of this stage.
- Rimo3 Health Check - Once the Rimo3 resources are successfully deployed, the Rimo3 Requirements Checker will automatically initiate a comprehensive health check to identify and report any potential issues that may need your attention.
- Configure Rimo3 - In the final stage, you will have the opportunity to add custom images and select the operating systems that will be utilized for automated testing in your new workspace.
Prerequisites
- An identity that has Owner level rights on
- The Azure Subscription, if you are creating a new resource group.
- Or an existing Resource Group that will contain the deployed resources..
Please see this article for the full list of prerequisites.
When you first sign up for Rimo3 we will provision your Workspace for you. As part of this process we will require your Azure subscription ID so we can assign it to our Azure Marketplace Offer. Deployment
Prefer to watch rather than read? See the video below for a step-by-step guide on deploying a Workspace.
Head over to Rimo3 website to login to Rimo3.
Sign in with your Rimo3 credentials - if you don't have these, please get in touch with us.
In Basecamp select the waffle menu and click on Tenant Health
You will then be presented with the Rimo3 deployment screen. To start the deployment - click on Lets go! →.
In step 2 click "1. Copy Registration Key 🔑" to save you unique registration key to the clipboard.
Please be aware that the Registration Key is valid for only 4 hours but don't worry, you will use soon after to complete the marketplace offering (MPO). If it happens to expire before you can use it, you can easily return to this step to generate a new key and start the MPO again.
Once you have generated a Registration key the "2. Take me to Azure! 🔗" button will be enabled, click on it and complete the next step in the Azure Portal which will open in a new browser tab or window.
After you have completed the MPO and Azure starts to deploy your resources comeback to the above screen and the button to proceed will automagically appear after the registration key has been validated.
In the Azure Portal tab you will be presented with the Rimo3 Cloud (preview) listing, if applicable ensure the correct subscription has been selected. Click on Create.
On the Basics tab, select your Azure Subscription, if necessary, and Create a new Resource Group. Alternately, you may use an existing Resource Group.
When utilizing an existing Resource Group, it's important to note that a service in the deployed solution periodically runs to remove orphaned resources. While this process is not expected to impact resources unrelated to Rimo3, it is advisable to avoid placing any non-Rimo3 resources within the Rimo3 resource group to prevent unintended deletions.
Select your preferred Azure Region, then click Next
On the Registration tab paste the Registration Key copied earlier and click Next.
Don't worry if you forgot to save the registration key somewhere have copied something else in the meantime, just use Windows Key + V to access your clipboard history. Alternately, swap back to the you workspace and copy a new registration key.
On the Networking tab you can:
- Use the pre-filled virtual network and subnet without changes
- Customize the pre-filled resource configuration as needed
- Select an existing virtual network and subnet
If you plan on peering the Rimo3 virtual network for Domain Join and SCCM import make sure the virtual network and subnet configuration do not conflict with any existing network configurations
When customizing the pre-filled resources or utilizing an existing virtual network, it is crucial to verify that there are sufficient available IP addresses within the subnet range for the Rimo3 resources. During peak usage, a typical deployment may require at least 14 virtual machines, including the Gateway VM, to be provisioned simultaneously, so ensure the subnet can accommodate this demand.
Click on Next when you are ready to proceed.
On the Storage tab create a new
You will not be able to select an existing storage account, if you encounter issues creating the storage account please take a look at our troubleshooting guides or reach out to our Support Team.
On the KeyVault tab enter the name for a new key vault and click Next.
You will not be able to select an existing ley vault, if you encounter issues creating the key vault please take a look at our troubleshooting guides or reach out to our Support Team.
On the Gateway settings tab, enter the username and password for the local admin account that will be set up on the Gateway virtual machine. Additionally, specify the resource names for the virtual machine, disk, and network card.
The local admin password must comply with Azure password requirements, and therefore must contain at least 12 characters, with at least 1 uppercase letter, 1 lowercase letter and 1 number.
Click on Next
On the Review + create tab review the configuration and when you are ready click on Create.
If you encounter Azure policies that prevent the creation or configuration of certain resources, there are a couple of options available. You can either:
- Create the required resources in advance and then adjust the Marketplace Offering (MPO) to utilize them.
- Pre-create the resource group and temporarily disable the policies for that group to facilitate the deployment. Once the deployment is complete, you can configure the affected resources to align with the policies and subsequently re-enable the policies for the resource group.
You will then be presented with the Resource deployment progress page. At this point you can switch back to the Deployment Wizard tab and wait for the Continue Ascent! → button to be enabled so you can continue your journey.
The Ascend button will be enabled shortly after the validateRegistrationKey Deployment Script completes
When the Continue Ascent! → button appears click on it to proceed
On the Resource and Agent deployment screen you can monitor the progress of each stage of the deployment. When all three stages are complete click on Continue Ascent! →
If you notice that any stage is taking longer than anticipated, feel free to return to the Azure Deployment screen to check for any reported issues with the deployment steps. Should you encounter any problems, we recommend consulting the deployment troubleshooting guide for further assistance.
On the Important Safety Checks screen you can review the result from the Rimo3 Requirements Checker and address any issue that may prevent the deployment from completing successfully.
The Gateway and Persistent Task Runner statuses may briefly go on and offline before the Requirements Checker runs. If the Requirements Checker does not appear to have started automatically click on Run Checks to start it manually.
Some issues do not need to be resolved immediately, but will need to be addressed before the Rimo3 service is fully up and running:
- ✅ Check has passed, no action required
- ⚠️ Check has failed, this won't prevent the deployment from proceeding but the issue should still be be addressed.
- ❌ Check has failed, the issue should be resolved before the deployment can proceed. Expand the rule to review the details of the failure, and the associated troubleshooting guide for more information.
After making changes you can re-run the Requirements checker from this screen to update the rules and validate that any changes have resolved the issue(s).
If all check have passed, or only failed with a warning, you can click on Continue Ascent! → to proceed.
On the Configure Rimo3 page you will have the opportunity to add custom OS images to you workspace and select which Operating System to use for the different Rimo3 test environments. If you are happy with the default selection click on Save to confirm the configuration.
When you are ready click on Continue Ascent! →
Congratulations! You made it to the Summit!
You have successfully completed the deployment and configuration of Rimo3 resources into you Azure Subscription.
Click on the Return to Basecamp button to continue exploring you workspace and the features of the Rimo3 platform.
You can navigate to the Main Menu -> Status to confirm that the Gateway Virtual Machine is visible.
Once the Gateway provision is active we can now test the provision of the Task Runner Virtual Machines by uploading our first app.
We recommend downloading a simple MSI file, e.g. Download (7-zip.org).
Compress the MSI file into a Zip file.
Proceed to onboard this Zip file to the Rimo3 platform.
Run the app through the full pipeline to ensure the Task Runner VMs are provisioned.
Click on next and then add your zip file.
This process will trigger the application upload process.
Once uploaded the application will go through the Rimo3 Onboarding pipeline, where it will be Discovered and go through a Baseline Smoke Test against your current Operating System.
After onboarding is completed, it will show as Onboarded - Yes.
From here we can view the Discovery information by clicking on the application name. We can view the Discovery Process details by clicking on the Green Passed icon, and the same for viewing the details of the Baseline Smoke Test.
Finally, we can test Modernizing the application.
From the Discovery dashboard, click on Modernize and select 7-zip and MSIX to test the process.
This will then trigger the application conversion process. The application will be converted to MSIX and will go through a post conversion smoke test.
You can see the results on the Modernization dashboard.
This now completes the onboarding process of:
- Connecting your Azure environment to Rimo3.
- Building the Rimo3 resources in your Azure Subscription.
- Building the Gateway server and confirming provisioned successfully.
- Provisioning the Task Runner Virtual Machines that are built with your current Operating System and target Operating System.
- Tested manually uploading an application and onboarding.
- Tested modernizing an onboarded application.