Secure. Doc v. 6. Release Notes. Note: If you do not use FFE currently, skip this advisory.
IF you are planning to upgrade your existing SES implementation to V6. AND your organization uses FFE to protect data on the Network or Locally on user computers, read the following prior to attempting the SES upgrade.
Background: Files that are encrypted using FFE in 6. Secure. Doc clients using FFE v. SR1 or earlier. However, v.
FFE clients are able to view fine FFE encrypted files from earlier versions, i. SR1 and earlier. This one- way limitation is due to improvements in the V6. Please review the following KB article to understand the upgrade considerations relating to use of FFE and upgrading to V6.
FFE. This article will instruct you in how to remove existing FFE policies and transition existing FFE- protected data to the new FFE protection schema in preparation to implement the V6. Please note that Win. Magic is deprecating Secure. Doc V4 Pre- Boot Authentication (PBA) support for SEDs in favor of the fuller function, more capable, V5 Pre- Boot Linux (PBL). The existing V4 support for SEDs will remain in the product for the time being but will not be maintained or enhanced.
Vpn Program Fail Sfera
We recommend that customers migrate to V5 PBL over the course of the next year. System requirements and supported devices, including tokens and Smart. Cards, for Secure. Doc v. 6. 5 are listed here. Note: It is strongly recommended to initially install Full- Text Indexing feature (Full- Text Search) into the Database Engine, before performing an SES installation. More information can be found here: http: //msdn.
Service.exe configure file located in Program Files. How to Get to Safe Mode in Windows XP/Vista/7. Best Paid VPN Service. Get This Top-Rated Backup & Recovery Program Free Through.
Vpn Program Fail Sfers
ASPXDuring the installation of SES, if Full- Text Indexing has not been installed, a message will appear indicating the absence of the Full- Text Indexing. This message will not allow the user to stop the installation of SES which will require retrofitting Full- Text Indexing into an existing SQL Server.
Note: Use of the SES Console will require the user to have at least local admin rights on the server or client device (e. Admin desktop) on which it runs, in order for the console to function properly. Note: Win. Magic is deprecating Secure. Doc V4 Pre- Boot Authentication (PBA) support for SEDs in favor of the fuller function, more capable, V5 Pre- Boot Linux (PBL). The existing V4 support for SEDs will remain in the product for the time being but will not be maintained or enhanced. We recommend that customers migrate to V5 PBL over the course of the next year.
Reference. Description. SD- 2. 22. 1Secure. Doc Cloud Lite (SDCL) – a new tool to synchronize encrypted data to Cloud Service providers.
A new set of tools,Secure. Doc Cloud Lite (SDCL), is now available to synchronize encrypted data to Cloud Service providers, as well as providing the ability for end users to access and decrypt such files on Windows and IOS devices using a new set of decryption tools collectively called Secure. Doc File. Viewer. This same reader technology, Secure. Doc File. Viewer, can also be used to decrypt files that can be sent securely as email attachments, on USB media, CD/DVD, or through any other transfer method.
SFE: A fast-acting low voltage glass body cartridge fuse. UL's Component Recognition Program allows the testing of components (including fuses and holders). Anonymous, Private, Secure, and Free. SafeIP can be used completely free for unlimited use, without advertisements and never expires. Pkgbuild-sfe-commits — svn commit notifications for the. Advertising Programmes Business Solutions +Google About Google Google.com . Search; Images; Maps; Play; YouTube; News; Gmail; Drive; More.
To learn more about this exciting new offering, refer to the SDCL and File. Viewer user manuals. SD- 5. 14. 2Change from password protection to token protection at Windows and Pre- boot, based on certificates in AD SES Administrators can automate the mass- transition from password protection to the use of smart card or token- protection at Windows and pre- boot by adding the following clause in the ADSync Settings section in the Win. Magic. Secure. Doc. ADSync. Service. exe configure file located in Program Files\Win.
Magic\SDDT- NT\SDConnex. Once this switch is performed, the users must use the token to log in. The clause to be added is: Apply. Smart. Card. Logon. From. User. Account. Control= . For details on how to change from password protection to token protection, refer to Changing from password protection to token protection at Windows and Pre- boot section in SES User manual. SD- 7. 71. 0Ability to configure proxy settings in SES console in order to connect client devices to SDConnex.
Secure. Doc Enterprise Server now offers a means through which the SES Administrator can define that Client Devices can connect to SDConnex (and thereby the SES Server) through network data communication proxy servers. SD- 8. 63. 2Ability to disrupt / degrade normal service to enforce licensing compliance for endpoints. Secure. Doc Enterprise Server now offers a new account- in- good- standing compliance feature for those customers offering Secure. Doc management as a hosted service. When activated, this permits the Secure.
Doc client itself to present reminder messages and a countdown before the device can be accessed to users whose service payments are delinquent, prompting them to pay and make their accounts current. SD- 8. 85. 0SD- 9. SD- 9. 63. 0New Compliance Reporting Management Tool (CRMT) to report accurate drive list back to SES Console. SES now offers a new Compliance Reporting Management Tool (CRMT) through which both devices protected by Secure.
Doc, as well as other devices imported from Active Directory can be included into reports for purposes of tracking and analyzing organizational compliance. SD- 8. 95. 8SD- 9. SD- 7. 08. 8SD- 1. SD- 1. 00. 84. New broadened support for Smart Cards and Tokens, offering generalized support for Smart Cards that will work with Open SC as well as a new “Generic Card Type” that uses Microsoft CSPSecure. Doc now supports even more Token and Smart Card types. Where there is no specific driver for the card type to be used, Administrators can now select . The SES administrators can enable this option while defining Profiles in SES console.
SD- 9. 91. 6SD- 8. Ability to define a customized pre- boot background for client users in Pre- Boot for UEFI (PBU) The SES Administrator can now apply a customized pre- boot background image on all Windows platforms. The SES functionality that permits an Administrator to define a customized background image at pre- boot had not been working for devices using UEFI under Windows 8.
This has been corrected and a means of defining and correctly scaling such an image has been developed for use in the Secure. Doc pre- boot environment for UEFI devices. Also, it offers the ability to incorporate additional drivers.
These benefits had not been a possibility under the limitations inherent in the native UEFI boot platform. SD- 9. 67. 9SD- 4. A new command line tool “SDRecovery. Cmd” is now available to script decryption of endpoint devices. A new Command- line tool is now available that can be used to script decryption of endpoint devices. For more information on how to use this command- line tool, refer to “SDRecovery.
Cmd” section in the SES User Manual. SD- 6. 37. 3A new tool allows for the automatic collection of logs on Secure. Doc Client A file Client. Support. Info. bat in folder C: \Program Files\Win. Magic\Secure. Doc- NT\Support has been created through which end- users can (upon SES Administrator request) automatically aggregate device- level detail logs.
These logs may be required by Win. Magic Support to troubleshoot issues on that device. Refer to the “Collecting Support Information and Logs” section in Secure. Doc User Manual for detailed information. SD- 8. 96. 1When decrypting media, always use fast decryption. In order to improve user experience when needing to decrypt media, Secure.
Doc now uses the . This will substantially shorten the time required to decrypt sparsely used media by not requiring the decryption of sectors that do not contain . For partition- encrypted disks, the user must decrypt such partitions a partition at a time (i. After individually decrypting all the encrypted partitions, you can decrypt any full- disk encryption using the “Decrypt All Disks” functionality. SD- 9. 49. 8Automatic collection of required logs from Mac FV2 client A new command can be run on Secure. Doc- protected Mac computers that will aggregate Secure.
Doc logs stored locally on the Mac device into a single zip file, suitable for attaching to an email to Win. Magic support, where required. This is equivalent to a feature available for Secure. Doc- protected Windows devices, and now available for Secure. Doc- protected Apple Mac devices. To use this option, run a new command script named collect- sd- logs, located in the /Applications/Win. Magic/Secure. Doc folder).
This script will create an archive named . This option has been added to the Profile Boot Configuration screen.
This new option permits the disabling of the drive binding implementation, allowing the Secure. Doc implementation to work on non- compliant hardware. Note: This option is disabled by default. Refer to the “Boot Configuration Advanced Options” section in SES User Manual for detailed information. SD- 1. 01. 02. SES validated to work with any version of Microsoft SQL 2. Secure. Doc Enterprise Server has been tested and verified against all versions of Microsoft SQL Server 2. SD- 9. 98. 7SD- 1.
A new feature now enables Smartcard- based Single Sign- on (SSO) into endpoint devices. This is defined in the Secure. Doc Profile in SES, as well as offering extended SES/SDCC Credential Provider options. Secure. Doc Enterprise Server adds functionality to permit and manage Single Sign- on (SSO) when using Smart- Cards or Tokens. Having authenticated with a Smart Card or Token, the user's underlying credentials will be accessed and utilized to complete the single sign- on process, transitioning the user into the Windows desktop directly without requiring further authentication. SD- 7. 47. 7SD- 9.
SD- 9. 62. 1A warning message will be displayed when configuring ADSync service without selecting a Master Keyfile A new warning message will appear if an SES Administrator configures the ADSync service but has selected a Keyfile that does not contain the AES key. Note: The AES key protects the SES Database (as its primary key).