The purpose of this document is to outline the process to provision a Rimo3 tenant via the Azure Marketplace.
Prerequisites
- An identity that has Owner level rights on the Azure Subscription or the Resource Group.
Please see this article for the full list of prerequisites.
When you first sign up for Rimo3 we will provision your Workspace360 tenant for you. As part of this process we will require your Azure subscription ID so we can assign it to our Azure Marketplace Offer.
Workspace360 Deployment
Prefer to watch rather than read? See the video below for a step-by-step guide on deploying Workspace360.
Head over to Rimo3 website to login to Rimo3 Workspace360:
Sign in with your Rimo3 credentials - if you don't have these, please get in touch with us.
Please note, you will likely want to change your password via the Rimo3 portal before entering it in the Rimo3 Cloud Registration.
You will then be presented with the Workplace360 deployment screen. To start the deployment - click on Deploy.
You will be presented with the Rimo3 Cloud (preview) listing, as per Figure 1: Rimo3 Cloud (preview) Azure Marketplace.
Click on Create.
On the Basics tab, select your Azure Subscription and Create a new Resource Group or you may use an existing Resource Group.
When using an existing Resource Group, be aware that there is a script that runs that will delete any VMs that are not associated to Rimo3.
Select your preferred Azure Region.
Rimo3 provides default values for the Virtual Network, however you can create or use your own if preferred.
When creating your own Virtual Network, please work with Rimo3 to ensure there will be sufficient IP addresses available for the required Virtual Machines.
Also, if using an existing Virtual Network there may be challenges if there are Security Policies that are being applied. Please work with Rimo3 to ensure we have awareness and to overcome potential challenges.
You will need to create a new Storage account and provide a unique name.
If you are planning on domain joining the Rimo3 resources, you will also need to consider if the new or existing subnet needs to be added to an Active Directory Site.
A local admin account must be created for the Gateway Virtual Machine.
Resource names must be provided for the Gateway Virtual Machine, Disk and Network Card. Remove the <tenant> and replace with your provided Rimo3 Workspace360 tenant name.
The next step is to provide the credentials being used to access the Rimo3 portal.
Rimo3 provided the name of the Rimo3 tenant and the credentials when your Rimo3 tenant was provisioned.
Input your Rimo3 tenant name and credentials.
Review and confirm all the details that have been provided and click on Create when ready to provision the Rimo3 resources.
You will then be presented with the Resource deployment progress page.
To confirm the Rimo3 resources are provisioned correctly, you can head back to the Rimo3 console.
Once all three boxes are green, click on Next question.
On the next screen you can add any Custom Images from your Azure Compute Gallery, Domain Join the Gateway VM, or connect to SCCM.
All of these items can be configured later.
When ready click on Next question.
Finally configure the environment.
Select an image for the following:
- Current OS - used for Discovery and Baseline.
- Target OS - used for Windows Readiness.
- AVD OS - used for AVD Readiness.
- Modernize OS - used for MSIX Conversion.
Once selected, click on Next question.
The final screen provides a summary of your selections and some additional information and tips.
Click on Submit to head to your Workspace360 tenant.
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 Discover360 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 Package360 Modernize dashboard.
This now completes the onboarding process of:
- Connecting your Azure environment to Rimo3.
- Building the Rimo3 Workspace360 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.