Recovery keys from a hard drive that won’t boot

I need a solution

I need assistance. This is my first exposure to Symantec Encryption Desktop. My client has a laptop that can no longer boot to the Windows 7 OS due to physical damage and corruption on the hard drive. Numerous attempts were made to repair the Windows 7 OS, but they all failed. I am able to remove the hard drive from the laptop and insert it into a external USB dock connected to another computer. I am also able to see and access the uncorrupted files and data on this hard drive.

My client is asking if it is possible to retrieve the encryption keys stored this hard drive. My client has older documents that were encrypted using this laptop that she can no longer decrypt. According to online lresources, if I had been able to boot into the operating system, then I could export and import the keys. Is it possible to retrieve the keys from this unbootable hard drive and import these key into another copy of Symantec Encryption Desktop? 

Symantec Encryption Desktop 10.3.2 is the version installed on this hard drive.

Thank you,

Will Z.. 




  • No Related Posts

7023121: SUSE Manager database schema fails with ERROR: syntax error at or near “on”

This document (7023121) is provided subject to the disclaimer at the end of this document.


SUSE Manager 3

SUSE Manager 3.1

SUSE Manager 3.2


After upgrade from SUSE Manager 3.0* to 3.1 or 3.2 the database spacewalk schema upgrade fails:

psql:<stdin>:46: ERROR: syntax error at or near "on"

LINE 27: on conflict do nothing;

Another indicator is following log message in /var/log/boot:

Apr 11 10:55:26 xxdevmon postgresql-init[1701]: Your database files were created by PostgreSQL version 9.4.

Apr 11 10:55:26 xxdevmon postgresql-init[1701]: Using the executables in /usr/lib/postgresql94/bin.


PostgreSQL database needs to be upgraded as outlined within the release notes:


This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.


  • No Related Posts

EMC SourceOne Email Management File Restore Activity fails with “Permission Error (0x86044710).”

Article Number: 483073 Article Version: 2 Article Type: Break Fix

SourceOne for File Systems

When trying to restore the files previously shortcut, using File restore activity, the following file permission-related error shows:

Unable to verify that the user has required file system permissions to restore the file. Try restoring to an alternate location. (0x86044710)

Function: CExFileSystem::iWriteFileProperties

Error encountered checking permissions (0x80070423)

Function: CoExFileProvider::StoreDoc

Failed to restore file to original location

(000000002FA2F179A9A64B3E18708A1301F6951BEA98F76600). (0x86044701) The specified property FSC_TargetLocation does not exist


The issue was related with Windows File permissions not being applied properly to the files needed to be restored. Although Windows NTFS file/folder permissions stated that a particular end user and SourceOne account had full permission on those files, somehow Windows was not applying it.

Also, when running a File Restore Activity, the following NTFS security file/folder permissions need to be configured for the SourceOne service account :

–>Local Administrators group has the following rights:

–> Backup files and directories

–> Manage auditing and security log

–> Restore files and directories

–>Take ownership of files or other objects

  1. Remove and re-add the file permissions, disabling the option “Include inheritable permissions from this object’s parent” when managing NTFS permission on the problem file server foldername.
  2. Re-add any other identified users in this manner that lost file/folder permissions


  • No Related Posts

> 16 unix groups – server_param maxgroups – what are example valid OS ?

Some operating systems allow sending more than 16 groups.

VNX has a parameter called: maxgroups – which allows support for more than 16 groups (up to 128) but reboot is required.

[nasadmin@localhost ~]$ server_param server_2 -facility security -info maxgroups -v

server_2 : name = maxgroups

facility_name = security

default_value = 16

current_value = 16

configured_value = 16

user_action = reboot DataMover

change_effective = reboot DataMover range = (16,128)

description = Define the max number of extra group in Unix credential

[nasadmin@localhost ~]$ server_param server_2 -facility security -modify maxgroups -value 64

server_2 : done Warning 17716815750: server_2 : You must reboot server_2 for maxgroups changes to take effect.


does anyone have an example of OS ?


  • No Related Posts

A Hitchhiker’s Guide to Deploying Hyperledger Fabric on Kubernetes

Deploying a multi-component system like Hyperledger Fabric to production is challenging. Join us Wednesday, September 26, 2018 9:00 a.m. Pacific for an introductory webinar, presented by Alejandro (Sasha) Vicente Grabovetsky and Nicola Paoli of AID:Tech.

Why should you care?

Hyperledger Fabric is rather awesome, but deploying a distributed network has been known to give headaches and even migraines. In this talk, we will not be providing you with a guillotine that forever gets rid of these headaches, but instead we will talk you through some tools that can help you deploy a functioning, production-ready Hyperledger Fabric network on a Kubernetes cluster.

Who should attend?

Ideally, you are a Dev, an Ops or a DevOps interested in learning more about how to deploy Hyperledger Fabric to Kubernetes.

You might know a little bit about Hyperledger Fabric and about Docker containers and Kubernetes. We assume limited knowledge and will do our best to as possible and explain and demystify all the components along the way.

Read more at The Linux Foundation


  • No Related Posts

7023182: Linux Replication Fails with Error “TCPSocket::Bind(): Address already in use”

This document (7023182) is provided subject to the disclaimer at the end of this document.


PlateSpin Migrate 12.0 and up

PlateSpin Forge 11.1 and up

PlateSpin Protect 11.0 and up


A Linux replication fails with the message ERROR: “TCPSocket::Bind(): Address already in use” at the step sending files stage.


There is an existing connection using port 3725 on the source.
On the source run netstat -nlp to find out what connection using data transfer port exists and what its PID is. By default, the data transfer port is 3725.
If the process using the connection over the data transfer port is the ofx controller process, end the process. If another process is using that connection, consider when would be an appropriate time to run the replication or consider changing the data transfer port to a port number that won’t be used.


This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.


  • No Related Posts

Virtual Desktops Appear as “Not Registered” in the Console

To resolve the issue, grant the logon right, Access this computer from the network to the Delivery Controller machine account(s).

This can be modified directly on the VDA (recommended for testing):

  1. To edit the policy directly on the VDA, use Local Computer Policy editor (MMC, then add the Snap-In Local Computer Policy.)
  2. The policy is located in Computer Configuration –>Windows Settings –>Security Settings –>Local Policies –>User Rights Assignment
  3. Locate “Access this computer from the network”
  4. Click ‘Add User or Group’. Change the Object Types to include “Computers”.
  5. Type the names of the Delivery Controller(s). Click ‘Check Names’. Click OK to save the change. There will be several warnings.

Once this is determined to resolve the OU-based registration issue, policy can be applied to all the VDA’s by completing one of the following tasks:

  • Apply a group policy from the domain controller either to the domain as a whole or to an Organizational Unit containing the Virtual Desktops for the XenDesktop farm.

User-added image


  • No Related Posts

Case Study – Web Browser Displays “401 – Unauthorized: Access is denied due to invalid credentials”

Problem Definition

A customer was attempting to configure ICA Proxy mode on Citrix Access Gateway Enterprise Edition with XenApp 5.0 and Web Interface. The customer reported that when configuring the same, the 401 – Unauthorized Access is denied due to invalid credentials error message is displayed on the Web browser after a successful authentication to the Citrix Access Gateway Enterprise Edition Login page, as shown in the following screenshot:

User-added image


The customer had installed the following hardware and software components on the network:

  • Windows Server 2008
  • Internet Information Server 7
  • NetScaler appliance
  • Web Interface 5.0
  • XenApp 5.0

Troubleshooting Methodology

To troubleshoot this issue, the Technical Support Engineers investigated the Windows event logs of the XenApp Server and observed an error message in the Citrix Web Interface event log, as shown in the following screenshot:

User-added image

This prompted the engineers to shift the focus of the investigation towards the XenApp Server. The engineers recorded network packet traces on the XenApp server during a login attempt. Each time, the engineers killed the Access Gateway Enterprise Edition session to ensure that a new session starts. The Web Interface makes the outbound https request to the Access Gateway Enterprise appliance to retrieve the SmartAccess settings, such as VServer and Session Policy Name.

When analyzing the packet traces, the engineers observed that when the XenApp Server communicates to the URL in the preceding screenshot, /CitrixAuthService/AuthService.asmx, the XenApp Server sends a FIN-ACK packet during the Secure Socket Layer (SSL) handshake negotiation, as shown in the following screenshot:

User-added image

When attempting to open the /Citrix/XenApp1/auth/agesso.aspx URL, the Web Interface sends the 401 response code because the XenApp server could not complete the SSL handshake.

After further investigating the event logs, the engineers noticed that there was an issue with the SSL certificates.


  • No Related Posts