Information regarding new version of pcAnywhere ThinHost included in Backup Exec System Recovery (BESR) and Symantec System Recovery (SSR).

Article:TECH192751  |  Created: 2012-07-11  |  Updated: 2014-05-15  |  Article URL http://www.symantec.com/docs/TECH192751
Article Type
Technical Solution


Issue



With the release of Backup Exec System Recovery 2010 SP5 (9.0.5) and Symantec System Recovery (SSR) 2011 SP3 (10.0.3), a new version of the pcAnywhere (pcA) ThinHost is included on the Symantec Recovery Disk (SRD). This article explains some of the changes that have been made in this new version of the pcAnywhere ThinHost.

  1. In the BESR 9.0.5 & SSR 10.0.3 SRD, the ThinHost is replaced with version 12.5sp4 (12.5.5.1086). (Earlier ThinHost version was 12.1 (12.1.0.448)).
  2. The following are known limitations with the 12.5.5.1086 version:
  • No backward compatibility with previous versions of pcA.
  • The pcA 12.5sp4 version will only connect to itself and any version higher than itself.
  • So to connect with new thin host in SRD, the Host must be 12.5sp4 or higher.
  • In new version of pcA has removed support for following languages:

Simplified Chinese,Russian, Portuguese
For these languages, English version ThinHost will be used. (i.e. text and messages will appear in English in Thin host application dialogs.)

  1. Working of new PCA (default options changed e.g. SSL, encryption etc.):
  • In standard SRD, default Encryption is changed to AES256 (Symmetric). In earlier versions default was “None”. So while connecting to thin host  in standard SRD user needs to select Encryption level “AES256” in Quick Connect Wizard.
  • In Custom SRD wizard, user can configure the Encryption level to “None /  pcAnywhere / Symmetric”
  • In Custom SRD wizard, nothing has changed from UI perspective. User can configure the PcAnywhere options same as previous releases.
  1. The only part of BESR & SSR that has changed is the SRD.
  2. Additional information:
  • Each pcAnywhere Host and ThinHost will generate a self-signed unique certificate and key to be used throughout it's life:

thost.crt for ThinHost

thost.key for ThinHost

  • Additionally, passwords are now being hashed inside the encryption for additional protection.

Solution



This article is provided for information only.




Article URL http://www.symantec.com/docs/TECH192751


Terms of use for this information are found in Legal Notices