Skip to content
Rimo36 Feb 20232 min read

Arkansas

Flexible resource naming & Azure Marketplace offering 

The resource names of most Rimo3 resources created in the customer Azure subscription can now be customized via a new Marketplace offering.  The marketplace offering allows customers to: 

  • Choose an existing, empty resource group or create a new one 
  • Create a new storage account 
  • Choose an existing virtual network or create a new one 
  • Manage the subnets of an existing virtual network or create a new subnet 
  • Name the Gateway virtual machine, disk and network card resources 

Marketplace-Images

Existing customers can take advantage of flexible resource naming by migrating Rimo3 resources that are using prescribed resource names to a new custom named resource group. 

 

Upload/Download improvements 

Improvements have been made to how packages are uploaded to the Rimo3 platform.  Packages can be uploaded from the local machine or imported from a shared location such as Azure Blob storage, OneDrive or Google Drive.  Packages are uploaded/imported directly to Azure storage and are now scanned for malware as part of the import sequence.  The time to upload and import packages is now notably quicker, uploads are more reliable, and the upload size is no longer limited to 4GB when importing from a shared location. 

upload-anti-malware-scan

Modernized applications are now automatically stored in blob storage ready for download which significantly improves the download time of MSIX and App Volumes packages.  Packages modernized before this release will automatically be copied to blob storage the next time they are downloaded. 

ready-to-download-notification

 

Rimo3 Public API 

The Rimo3 Public API has been updated in line with the changes to how packages are uploaded and downloaded.  Details of the changes can be found in the new Swagger documentation, there is now also a Postman collection for the Rimo3 Public API, both of which can be accessed via the Integrations page. 

API Gif

 

Windows 10 2004 Support 

As Windows 10 2004 and Windows 10 2004 multi-session is no longer available in the Azure marketplace as a vanilla image it has been removed from the Onboarding and Change OS questionnaires.  If you have Windows 10 2004 currently selected as a current or target OS you will be prompted to change it next time you login.  Custom Images that use Windows 10 2004 or Windows 10 2004 multi-session are not affected. 

 

Other improvements & fixes 

  • Prompt for expired password now occurs before selecting a tenant and entering MFA token. 
  • Orphaned task runners are now automatically removed by the Gateway on a schedule. 
  • Fixed bug in Rimo.launcher that affected shortcuts after re-signing MSIX packages. 
  • Fixed bug when fetching Azure extensions log for some custom images. 
  • It is now possible to rediscover and rebase MSIX packages. 
  • Improvements to how environment variables are expanded in install/uninstall commands. 
  • The upload load option is disabled if the storage account connection string is not set. 
  • Running and queued Sequences can now be bulk canceled.
 

Similar Posts

Image for Fraser

Fraser

Image for Xanadu

Xanadu

Image for El Paso

El Paso