Changes since Beta1 Build b191282

 

 

General Functionality:

 

•A universal, all-disks capture Payload is now pre-created upon LSM installation, allowing the User to start capturing Machine Snapshots out of the box

 

•Machine default actions upon Payload success and Payload failure are streamlined, with the added ability to pause before a user-designated reboot or power-off, allowing the LSM user to SSH into any Machine being serviced for remote diagnostics, troubleshooting and other remote SSH actions

oConfigure and Machine Settings GUI pages have revised Payload success and failure dropdowns and a new Pause on Completion dropdown

 

•Machine Profile (hardware discovery) augmented with Baseboard (motherboard) and BIOS discovery (manufacturer, product name, version number...)

 

•User Scripts:

oStreamlined User Scripts directory structure allowing the User to build desired directory hierarchies for Machine OS (Windows, Linux...) file content

oMachine OS (Windows and Linux) Script working examples are now provided, illustrating how the User's LSM RAM Agent scripts can mount the Machine OS file system(s) and copy files including first-boot scripts to the Windows or Linux Machine being serviced

 

•"In Use" elements (Payloads, Payload Stages) can now be edited if not in active pre-use or use by Machines, providing enhanced Payload design flexibility

 

Security and Integrity:

 

•User Management is enhanced allowing authorized LSM LSM users remote access from multiple, pre-specified IP addresses for SSH and HTTP access

oLogin error messages are now streamlined and can be reviewed by authorized LSM root users

 

•LSM Installer

oFirewall and SELinux activated at RHEL/CentOS installation time will be disabled upon LSM installation

▪LSM root user can authorize secure user access

▪User may set up Firewall and SELinux with the provided port numbers needed by LSM

 

•If altered by the User, system scripts and files are re-created to be "as delivered" upon Machine servicing events

 

•Remote command line access to Machines being serviced has been restricted to authorized LSM users only

oOnly authorized LSM Users may enable local command line usage of a remote Machine being serviced

▪Performed by adding a root access script as a Payload Stage

oAccidental alteration of LSM product directories and files by authorized LSM users accessing a Machine being serviced is prevented

 

Known issues as of Build b191282

 

•Only Machines with BIOS are supported (not UEFI) either to run LSM or to be serviced by LSM