Uninstall securedoc

Right click the taskbar on the bottom and then click Task Manager. Input "msconfig" in the Open: field and click OK. Click the Boot tab in System Configuration window. Tick the checkbox "Safe boot" and click OK. Click Restart in the pop-up dialog to boot into Safe Mode. Uncheck the Safe boot option to exit Safe Mode. To avoid overweight registry and disordered system , you should continue with next two steps: 1. Sign in to leave feedback. Blank Blank.

Blank Details. Please review the macOS client documentation for a deeper explanation of the changes to the User Interface. WinMagic has received requests from customers to provide a new standard report on Crypto-erased devices.

SD A new option has been added into the Device Profile to enable the Device Compatibility testing report mode functionality. A new option has been added to Device Compatibility testing that permits testing to stop after Pre-Boot Compatibility testing has completed, at which point the device will produce a report of the test results. If chosen, this option will block the SecureDoc Client installer from completing installation and encryption of the device.

This was implemented to provide additional compatibility for systems that are using disk controllers or modes that prevent PBLU from accessing the disk directly. For example, systems configured to use the intel software RAID functionality in the bios. Therefore, this new feature is disabled by default, and is accessible through a new Profile option, adjacent to the existing SUSAM option. It is strongly recommended to test this feature on devices before widespread deployment.

After successful customer validation, this option may become a default in a future version of SecureDoc. The old way of creating a Device Profile has been removed and made more consistent across all Profile types.

Customers have indicated that there are certain scenarios where it may be necessary to have a different IP configuration in windows vs in Pre-Boot authentication. In this scenario, even setting the option in the profile to use Static IP is not sufficient.

Therefore, an improvement was made to provide a way to manually set a static IP for Pre-Boot authentication on a device. A KB article will be added with more details on how to configure this mode. For details, please reach out to WinMagic Technical Support. As part of the multi-domain improvements made in SecureDoc 8.

NOTE: In order for this to take effect, new keyfiles must be generated that include the new information. If there is a requirement to force immediate update of users keyfiles, please reach out to technical support for instructions.

Work-Around: For those customers that still rely upon this functionality, the same effect can be achieved by opening and editing the PackageSettings. In previous versions of the SecureDoc Windows Client, there was no warning or protection provided if an attempt was made to install an older version of the windows client over a newer version. Instead, the upgrade would proceed and result in a corrupted installation.

Starting with SecureDoc 8. Additionally, it is strongly recommended to use the Full Sync option by clicking the corresponding Full Sync button before starting the ADSync service. After upgrading SES to V8. SD Port Control short-term override and automated device discovery has been improved. This permits kiosk, ATM and other similar special-purpose devices to accept only those HID devices they are deployed with down to the Serial number , and Port Control will prevent attachment of any other devices.

To coincide with the maintenance of a special-purpose device e. It was determined through investigation that there was a possibility of a drive failure being triggered by frequent communication from SecureDoc causing the drive firmware to stop responding. The affected drive found in testing was the Samsung PMa.

It is recommended to check with the vendor of the drive or OEM system for a firmware update. When the above disk becomes activated as an eDrive, it was longer possible to perform a PSID-revert action with previous versions of the SDRecovery tool.

The only work-around had been to use 3rd-party tools to revert the disk if the customer did not want to use eDrive management or Software Encryption. Solution: SecureDoc 8.

The functionality is also included in the command line version of SDRecovery. SD An issue has been corrected, wherein customers who have Cisco Duo installed were encountering a conflict between SecureDoc and Duo relating to Password Synchronization. Issue: SecureDoc Password Synchronization was failing randomly where client devices also has DUO installed; It was determined that Windows will sometimes create an encrypted version of credentials passwords when they are passed to authentication APIs, which results in the same encrypted passwords being passed to the SecureDoc Password Synch process.

Solution: SecureDoc is now able to synchronize with this form of credential, and this correction is now integrated into V8. SD, SD Devices that originally did not have a shared device certificate for Background: Many organizations are looking more closely at applying WinMagic has long supported PEAP authentication as certificate-based authentication was not available to pre-boot unless the private key was made available for every device certificate.

This presented an issue for organizations that prefer to use certificates to authenticate. This allows an organization to use a fixed user account that is protected by certificate, not password, for EAP-TLS Issue: It was discovered that for devices that originally did not have a certificate assigned via a profile with the appropriate network configuration, that once the new profile was assigned, the certificate would not reliably propagate.

This was determined to be an issue with device communication logic, and it was found that the certificate was not being requested on communication with the SES server. Solution: SES V8. In addition, if the certificate is changed Eg: to replace an expired certificate the new certificate will propagate successfully. This issue comprised multiple root causes and resolutions: 1 It was found that an issue existed which involved Case Sensitivity when creating the personal Key File for a user.

In the rare case where a user would have an upper case user id, the client would create the personal key using a lower case userid. This would cause an issue where the client incorrectly invalidated the userID due to the case sensitivity mismatch. The underlying result was that the cached credential could then become duplicated in SDSpace, thus preventing password sync from working as designed. This would result in the user not being able to login offline at Pre-boot.

The default is 40 boot slots. The issue that was found, was that as new users logon to the system, the expected design was that new users would replace the oldest users in the boot slots, thus enabling the new users to authenticate at pre-boot. This design was not functioning, and new users were not getting cached on the system.

If the user took some time to connect to the VPN, the user would not get cached. This issue has been resolved and the system will continue to check for a connection to the SES server in order to cache the user.

Solution: All issues have been resolved and a HF was made available on request for 8. This release note is to notify that this fix has also been fully incorporated into Version 8. SD An issue was identified that prevented a device from rebooting via remote command if automatic reboots were disabled during the initial installation.

Issue: Where an installation package has the setting: "Wait for the distribution software to reboot the system" had been selected, the intended behavior was that this setting would prevent the automatic restart of the computer during various parts of the SecureDoc Installation process. If the Administrator sends a command to reboot the device, once the device has communicated with the SES Server, the SES command's status will show as "executed", but the device will NOT be restarted in response to that command.

Solution: This issue has been resolved, and the client will now correctly respond to remote reboot commands after the initial installation process is completed. Solution: This issue has been corrected in V8. Customers using such devices should upgrade to V8.

In SecureDoc 8. However, for customers who already removed these verbs at the server level, due to propagation removing at the site level would cause a failure to start the website. This issue has been resolved and SES Web config has been adapted to no longer conflict with the server rules.

While not impacting functionality, it was found to be annoying. Solution: This has been resolved in this release. The systems will no longer emit a beep noise when shutting down or restarting from the Pre-Boot Linux environment.

This issue had been a limitation in SecureDoc 8. Solution: Please transition to a different token that is compatible with bit Pre-Boot. Work-Around: Until a more robust solution has been found, please:.

WinMagic will continue to pursue a solution to these limitations, which may require a kernel update for PBLU in a future SecureDoc version. WinMagic is working to improve this in a future version. WinMagic is looking to provide a resolution to this issue in a future version. SD Rapid insertion and removal of USB Media during the second countdown to system shutdown can result in a system halt on systems configured to use Port Control.

Solution: It is recommended to manually enter the UPN. This should not pose a substantial problem over the life of the device installaiton, as the UPN form of the user name will be made available via ADSync. SD : When encrypting or decrypting Linux devices using offline encryption, the device's encryption status is not updated in the SES Console as regularly as applies where the device is encrypting online. Issue: When encrypting or decrypting Linux devices using offline encryption, the device's encryption status is updated only after each volume completes encryption or decryption.

At this stage, this limitation is not avoidable, since the device does not utilize an ongoing communication model back to the SES Server. WinMagic is researching options to improve on this. This functionality is relatively rarely used.

WinMagic will be seeking an alternate way to handle importing a list into SES Web, which will be announced in a future version.

Where customers have translated certain messages, those messages will not appear correctly in the Compatibility Report. WinMagic is seeking a solution to this issue. SES 8. Note that, in general, upgrading existing client devices to handle these alternative logon methods will not necessarily mean that the users can immediately use these new login formats at the SecureDoc Control Center.

Underlying Cause: For the new logon methods to work, existing on-device key files must be updated to have the relevant attributes.

There is at present no means of automatically sending updated key files to client devices. The key files will get updated as passwords are synchronized or as users logon to windows with alternate formats. WinMagic is investigating ways to potentially script an update to all key-files.

If this is needed in your environment, please contact WinMagic Technical Support. WinMagic is working to find a solution for this issue. Issue: 2 options: "Hide wireless configuration at pre-boot" and "Do not reveal passwords at pre-boot" are missing from the SES Web User interface. WinMagic plans to have a correction to this issue in a future version. SD : Configuration of ADSync domain parameters wherein the User ID mapping is either different from the default, or includes a modification to append the domain name to SAM account will limit the user's ability to enter alternative logon names for authentication via PBConnex.

In particular, use of SAM-name only is not supported for such a scenario. From this point onward, the Administrator can then modify the profile. Issue: Once the profile is modified, SESWeb does not re-check for parameter contradictions in the package, nor does it regenerate the package to reflect the new profile parameter values. This is a limitation in SES V8. Work-Arounds: Create a new Installation Package from the same now changed Device Profile and duplicate the Package settings used in the original Installation package.

For ease of tracking, either change the original package description to indicate it was obsoleted by the new Package or delete the original installation package. Thanks for sharing that, def some nice troubleshooting there. Always encouraging to hear positive stories from the field and getting to feel like an IT rock star!

I was trying desperately to find a way to remove the encryption on a Samsung gb SSD. After scouring the net for days I was told there was no way to save it because Samsung did not provide a PSID Revert tool for their drives. Thanks again for all your work on this.

Take Care, Rick. Take Care, Rick Awesome. Glad it helped someone! Recovering a disk with SecureDoc encryption 5 posts. Rekcin wrote:. Posted: Fri Apr 15, pm.