Limitations
The following limitations apply to SPS when you deploy it from the Microsoft Azure
Marketplace.
CAUTION:
Do not export or import configuration between a physical SPS deployment
and a virtual one. Because of the differences and limitations between
physical and virtual appliances, configure the virtual appliance from
scratch to ensure proper functionality. When you migrate a virtual SPS to
another one, you can export and import the configuration.
l
Root login is not available on the console.
l
SSH access is only available after you have completed the Welcome Wizard.
l
Currently, the data that is entered during the provisioning phase (for example,
the username and the IP address) of creating the virtual machine in Azure is
not transferred to SPS. Therefore, only the data entered in the Welcome Wizard
will be used.
l
By default, you can only use Physical interface 1 (eth0) of SPS, with a single IP
address. Aside from changing the IP address of SPS, do not modify other interface-
related settings (additional logical interfaces, IP forwarding, and so on) on the
Basic
Settings > Network
page of SPS.
The number of interfaces you can use depends on the size of your Azure VM. If your
VM allows you to use multiple interfaces, you can configure multiple interfaces in
SPS. For details, see
l
The
Seal the box
functionality is not available.
l
The High Availability support of SPS was designed to work between two physical SPS
appliances. This feature is not available in Azure environments. For further details,
see the
High Availability and redundancy in Microsoft Azure
l
Due to Azure requirements, an additional 5-minute delay has been added to the boot
process. This ensures that the root device appears in the system.
l
The size of the hard disk in Azure is 100 Gb. You cannot extend this virtual disk size
later, nor can you write to Samba or other disks. In case you run out of disk space,
either configure a
Backup policy
and an
Archive policy
if you have a server for
this purpose, or configure a
Cleanup policy
that deletes the audit trails at certain
time intervals. For details, see
"Data and configuration backups" in the
"Archiving and cleanup" in the Administration Guide
l
SPS currently cannot receive its IP address using DHCP. Make sure that:
l
The IP address you have configured in Azure and the IP address that you
configure for SPS for the
Physical interface 1
on the Networking settings
part of the Welcome Wizard are the same. Otherwise, you will not be able to
access SPS.
l
You set the internal IP static on the Network Interfaces tab of the Virtual
SPS 6.0 Installation Guide
Deploying One Identity Safeguard for Privileged Sessions from the Azure
Marketplace
31
