Frequently asked questions about Rimo3
What formats are you able to import from ConfiMgr (MSI, App-V, Scripts, Exe-files etc)? Are Packages and Applications supported?
Rimo3 supports Applications (and Deployment types)
The following formats are supported:
Currently, Rimo3 does not support Packages (and Programs)
Is the performance data saved so it can be compared between versions?
Yes, the Performance data can be exported via the Public API and processed for comparison in a tool of your choice.
Do you see use cases for smoke testing groups of apps at once, as opposed to single apps?
Yes, this is already available in the Enterprise platform, and we are reviewing the possibility of including this feature in the Cloud platform.
Are the MSIX packages signed?
Yes, MSIX packages are signed and timestamped with a certificate issued by a Trusted Root CA and therefore will work on any version of Windows.
Does Rimo3 support task sequences?
No, we currently do not support importing task sequences themselves, but we are still able to import the applications that make up the task sequence and the install order can be recreated using dependencies in the Rimo3 Platform.
Can you replace the logic if you have an update? I have app A, B and C with dependencies to each other from ConfigMgr. Then a little later app B updates, can you replace B and do a new test and packaging within the console?
Yes, you can import the updated package for app B and use it in the dependency chain with apps A and C.
Can a single Rimo3 tenant support multiple instances of Microsoft Intune to test and export applications?
Yes, Rimo3 provides the ability to configure multiple instances of Intune in a single tenant of Rimo3.
Can Rimo3 install applications that do not have a silent switch?
No, if there is any interaction required during the install then this will cause the install to eventually timeout.
What is the Rimo3 + Nerdio integration path?
MSIX packages can be exported from Rimo3 to Nerdio Manager where they will be converted to an App Attach image automatically via the integration.
How does the technology integrate with in-house applications?
Rimo3 can support in-house developed apps if the applications meet the Rimo3 prerequisites. (Silent install)
What if we have multiple OS’s (like most large enterprises?)
Applications can be tested and retested against different vanilla and custom OS’s as needed.
If an app needs java, will it automatically download and install?
Rimo3 provides the ability to add dependencies if they are not included in the source package.
How can I onboard application packages to Rimo3 Cloud?
Application packages can be imported from Config Manager, uploaded in zip files, or manually added.
What is a silent install?
A silent install, or unattended install, is when an application’s installer is configured to run without displaying an interface such as an installation wizard or error messages which allows applications to be deployed via deployment solutions such as Endpoint Manager Config Manager (SCCM), Intune or GPO. The installer’s interface would typically be suppressed by using command line switches, a response file (also known as an answer file) or a combination of the two.
- Command line switches to invoke a silent install typically include, but are not limited to, /q or -q (for quite), /s or -s (for silent) or /passive, though the latter may result in errors messages being displayed for some installers. Unattended installs typically install a default set of features, but response files also have the advantage of allowing you to preconfigure how an application installs.
- For Windows Installer (MSI) packages the silent install switches are /q & /qn; other switches are available, but in some situations, these can still lead to error messages being displayed and as a result the install is not truly unattended. Windows Installer packages use a special file known as a Transform file, to pre-configure the application. As important as ensuring the installation is silent the removal, or uninstall, of applications also needs to be silent, this is typically achieved with the same silent switches for installation with the addition of a /u or -u (for uninstall) or /r or -r (for remove) switch.
Some package format such as MSIX, AppV, and App Volumes inherently install silently. Vendors typically provide documentation on how to silently install their products but if you can’t find such information there are many sites and forums you can review such as https://silentinstallhq.com/.
What is Discovery?
Discovery in Rimo3 Cloud is how we determine whether an application can be tested or not and if so, what components are available to test. The process automatically installs an imported application and identifies the executables and shortcuts that were installed. The shortcuts will be automatically selected for testing, if desired you can select any additional executables that were Discovered to be tested as well.
What is a Baseline smoke test?
The Baseline smoke Test, or Baseline IST, is a test carried out to ensure that the components identified in Discovery behave as expected in a “known good” environment. The Baseline smoke test is carried on against the current OS where the application is expected to install and launch without error. Application packages need to pass the Baseline smoke test before any other activities will be carried out.
Can I use custom builds for testing?
Yes, you can configure your tenant to use Managed Images or images from a Shared Image gallery when provisioning Task Runners.
What is the Gateway?
The Gateway is a device running the Rimo3 Gateway agent; it acts as a reverse proxy to secure communication between Task Runners and the Rimo3 Web Host as well as orchestrating activities on the Task Runners.
What is a Task Runner?
A Task Runner is a device running the Rimo3 Task Runner Agent that is used to carry out automated tests and other Rimo3 activities such as importing application packages, Discovery and conversion.
What is Modernization?
Modernization is the term Rimo3 uses for not only converting legacy application package formats to modern package formats, but also testing them to ensure they work on a modern operating system too.