Contacting WinMagic
WinMagic
5600A Cancross Court
Mississauga, Ontario, L5R 3E9
Toll free: 1-888-879-5879
Phone: (905) 502-7000
Fax: (905) 502-7001
Sales: |
sales@winmagic.com |
Who Should Read this Document
This document explains how to use SecureDoc in an enterprise environment and is intended for either end users or administrators. It describes features available in all SecureDoc Cloud Lite editions, with edition-specific features clearly labelled. Note that some features may not be available in some environments, or to some users.
This document assumes a basic working knowledge of MacOS-based computer systems. It explains only SecureDoc-specific procedures.
New Features and Enhancements
SD-21870 |
SD Linux: Reducing drivers dependency on kernel patch versions Issues: When SD Linux released a major or minor version we are looking for a way to support installation and resolve current heavy dependency of patch versions of Linux with our product.
List of supported Linux versions and kernels:
|
SD-21892 |
SD Linux Client: Supports Ubuntu v16.04 with the new kernel v4.8 Issue: SDLinux Client supports Ubuntu V16.04.02 with the new kernel 4.8. Alternatively, SDLinux Client should support Ubuntu V16.04.02 with kernel 4.4. |
SD-22478 |
SD Linux Client: Sends recovery information to SES while recover data from encrypted system New Feature: SDLinux now has the capability to send recovery information back to SES, in order to recover data from an encrypted/encrypting or non-bootable VM. The recovery information can be properly exported and SDLinux can successfully recover. Limitation: LVM-based system recovery is a limitation in v7.28. |
SD-22656 |
SD Linux Client: Supports static IP (limited to RHEL 7.3 only) New Feature: CloudVM Linus client supports static IP at pre-boot. When the administrator configures the package to sue static IP instead of getting an IP from DHCP it will retrieve the static information from the client and apply it at pre-boot for PBConnex. |
SD-22657 |
SD Linux Client: Supports LVM resizing on an encrypted volume Improvement: CloudVM now supports an encrypted VM with LVM configuration, and is able to extend the LVM volume for more space without any disruption. Solution: The changing LVM volume size after installation, PBA was unable to match the volume correctly at boot time, by removing the extra check for size when the volume name matches the volume type is LVM (this doesn’t change the name). |
Limitations – Windows
SD-23189 |
Client machine is unable to begin decryption with the “Decrypt All” option in SecureDoc Control Center Issue: Windows client machine is unable to start decryption when using "Decrypt All" in SecureDoc Control Center (SDCC). SecureDoc progress bar does not open and decryption does not start when using "Decrypt All" function in SDCC. |
SD-23604 |
Manufacturer info registration not updated properly for Scale Environment CloudVM’s Enhancement: The manufacturer info registration for Scale Environment CloudVM's are currently the manufacturers info during device registration for Scale VM's are registered as "Red Hat". The Manufacturer info should be displayed/Identified depending on Scale VM's or Environment. |
SD-23625 |
Newly supported regions has not been added to Azure GEO location policies list Enhancement: The newly announced Regions for Africa and Asia Pacific should be added into Azure GEO location policies list. The list in Prevent Azure from Auto-Booting if found in the following Region(s) is missing 2 regions of Africa and 2 regions of Asia Pacific: |
SD-23720 |
Error 500 when creating Emergency Disk (EMG) Issue: Error 500 displayed when creating Emergency Disk while client installing BootLogon. The issue occurs in Windows client while BootLogon is being installed and creating an Emergency Disk in SES Web at the same time. |
SecureDoc CloudVM does not support moving of parent folders between two different Organizational Units (OU’s) in the Active Directory If any parent folder is moved from one OU to a different OU, then duplicate OU names are created in the SecureDoc Enterprise Sever (SES). |
|
|
The deployed installation packages (which contains the profile options) created using the SESWeb cannot be modified |
Child Virtual Machines fails at registration if the parent machine is permanently deleted from SES |
|
|
Self-Help warning messages, such as “Self-Help questions must be answered before continuing” and “Self-Help recover is not available for this user |
|
Installation packages cannot be created and prepared in an environment where SES Console and SDConnex are installed on physically separate instances (VM’s or real hardware) |
SecureDoc CloudVM extends limited support for Azure Classic VM’s |
|
SecureDoc CloudVM does not support Generation 2 (UEFI) Virtual Machines on Hyper-V environment and vSphere UEFI virtual machine |
|
When the “Prevent KF from being saved locally on the machine at deployment” option in the SESWeb installation package settings is set to Yes
Recommendation: It is strongly recommended not to enable this option. If you want to push a key file to a device, manually push them by assigning user to a device. |
|
Encryption progress bar is NOT displayed on some Azure RM Virtual Machines with Standard A1 & A0 size |
|
|
The remote command “Lock Device” does NOT work |
New clones cannot be created from the crypto-erased parent machines |
|
SESWeb will NOT support partition encryption and excluding partitions |
|
|
Microsoft Azure Classic VMs are not removed to Recycle Bin upon termination from Azure |
Auto-Scaled up and down cloud instances are not moved to Recycle Bin |
Limitations – Linux
SD-20964 |
Contact Technical Support error occurs when sending cryptoerase device to SDLinux devices Issue: SES Console is sending cryptoerase device to SDLinux device shows error '781a contact technical support'. In the SES console, sending Crypto-erase command to Linux client still works properly but got a pop-up error. |
||||||||||||||
SD-23307,
SD-23588 |
Issue: [AWS] Fails to deploy default package on Ubuntu 16.04 LTS (HVM) kernel 4-4.0-1020 (New Kernel). No driver file was found for new kernel version 4.4.0-1020 when deploying package on Ubuntu. This kernel is the special version for AWS: https://launchpad.net/ubuntu/+source/linux-aws/4.4.0-1020.29 Issue: Ubuntu 16.10 kernel 4.8.0-46-generic: Online fast conversion skipped root volume:adjustSectorBlockToConvert failed 0x7f2bb79c. The volume sda1 (root volume) was skipped while other data/swap volumes encrypting/encrypted after deployed package. And this only happens on 16.10 with kernel 4.8.0-46-generic. Work-around: N/A. |
||||||||||||||
CloudVM Linux runs on the following flavors of Linux along with these Kernel versions
Please note that SecureDoc pre-boot requires a separate volume in which is created during the installation process. Otherwise, the installation process will fail if we are unable to create this special volume. Recommendation: Please confirm if the kernel version of the VM device to be deployed is currently supported with SecureDoc’s supported list included above. |
|||||||||||||||
For conversion, please see the recommendation listed here:
|
|||||||||||||||
Concerning current public Cloud market place images |
|||||||||||||||
Client’s info is not all sent back to SES database after deploying and encrypting |
|||||||||||||||
On rare occasions the device does not start after installing Linux on the machine with redhat7.2 client on Azure Please note that this is an issue with Azure infrastructure and not an issue with SES. Recommendation: Shutdown and Reboot the VM in question. |
|||||||||||||||
Installation of multi volume encryption is haled on reboot for a system with more than 16 volumes Recommendation: Please ensure that (including root + SWAP) that the environment does not have in excess of 16 volumes. |
|||||||||||||||
Encryption does not start when creating multi volume Linux VM environment specifically where there are volumes after the given range of sectors used or SWAP Recommendation: This issue mainly manifests in LVM type devices used in private cloud instances and custom public cloud images. Please do not create any data volumes after creating SWAP space. Create all required data volumes prior to defining the space which would be used for SWAP. |
|||||||||||||||
In Microsoft Azure, SDLinux solutions cannot be deployed on either CentOS or Ubuntu related flavors SDLinux requires the boot - encryption does not start with Linux installation package for SES web for offline conversion of boot disk. This is a result of both Ubuntu and CentOS requiring the boot drive to be the primary drive. Work-around: We recommend using a custom VM Image (environment) created with either available SWAP or Free Space for the SDSpace volume to be created on the root Drive. |
|||||||||||||||
SecureDoc Linux AWS-RHEL7.3 does not support Amazon EFS instance storage types Please find more information from the following link: https://aws.amazon.com/efs/details/. SecureDoc does not currently support Dynamically allocated\deallocated storage space. Recommendation: Please use AWS’s EBS storage solutions. |
|||||||||||||||
An SDLinux package, created with the encryption type “Encrypt All Disks", "Data Only Fast Encryption" will switch to Through encryption when faced with a volume with an un-recognized file system Recommendation: As SecureDoc supports Most modern file systems, this issue is only randomly visible. It is however by design as it provides the maximum protection for such volumes. Feature can be readily visible when encrypting SWAP Space. |