Not applicable to SBC SWe Edge.
Purpose
This document identifies common use cases for deploying a non-
When an unsupported third-party application is installed, the ASM generally operates in Server mode. As a result,
Repurposing the ASM (SBA or CCE) for unsupported third-party applications and places the ASM in Server mode occurs when either one of the following conditions is true:
- The unsupported third-party application is not installed onto a VM, but is rather installed on the host OS.
- A supported third-party application is not installed on the ASM according to Unable to show "metadata-from": No such page "_space_variables"instructions.
Background - Third Party software deployment on the ASM
Third-Party Software installed on the ASM Host Operating System
Third-party software for the
- Supported. Third-party applications supported on the ASM host operating system are listed here: Approved Partner Solutions for ASM. For these approved applications, the ASM runs in Appliance Mode (SBA default offering).
- Unsupported. Third-party applications installed directly on the ASM that are not supported by Unable to show "metadata-from": No such page "_space_variables". When these applications are installed and deployed by customers, the ASM runs in Server Mode.
The information in this page explains the deployment of unsupported third party software directly onto the ASM host operating system, resulting in server mode of operation and support.
Third-Party Software installed via VM
- Deployment via Hyper-V VM. Unsupported third-party applications can be installed using a VM. For these applications, the ASM runs in Appliance mode. Unable to show "metadata-from": No such page "_space_variables"is not responsible for the performance or support of third party applications installed onto the VMs. See Installing Unsupported Third-Party Applications on the ASM via VM. Refer to the respective VM supplier's documentation for deployment instructions.
For additional details on the ASM in Appliance or Server Mode, see Managing the ASM.
For installing supported third party applications onto the ASM, see Installing an ASM Package.
Common Use Cases for Repurposing the ASM (SBA or CCE) for Third Party Applications and Server Mode
When an unsupported third-party application is installed and running on the ASM host (for SBA or CCE), the ASM operates in Server Mode. Common use cases for running in Server mode include:
- Installing non-Unable to show "metadata-from": No such page "_space_variables"approved security and update processes for the ASM's Windows Server® OS, Skype for Business SBA or CCE applications.
- Deploying a firewall or antivirus solution not approved by Unable to show "metadata-from": No such page "_space_variables".
- Deploying a third-party application (i.e., Call Recording, Auto Attendant, or IP PBX) that is not approved for use with the ASM. This includes common open source IP PBX applications such as those offered by Asterisk®.
Returning to Ribbon Cloud Link Usage
These instructions return an ASM originally shipped with the CCE application back to its original state.
If you need to revert back to the
- Remove all third-party party applications from the system.
- Re-initialize the ASM using the Cloud Connector Edition (CCE) image found on the hard drive. See Re-initializing the ASM.
From the ASM image type drop down, select Cloud Connector Edition.
After re-initialization, the
Returning to SBA Usage
These instructions return an ASM originally shipped with the SBA application back to its original state.
If you need to revert back to the
- Remove all third-party party applications from the system.
- Re-initialize the ASM using the SBA image found on the hard drive. See Re-initializing the ASM.
From the ASM image type drop down, select the SBA image.
After re-initialization, the