HP MFP Digital Sending Software five.0 Upgrading From DSS 4.0 Through four.20 C04022690

User Manual: HP HP MFP Digital Sending Software 5.0 - Upgrading from DSS 4.0 through 4.20

Open the PDF directly: View PDF PDF.
Folio Count: 3

white paper  HP Digital Sending Software v.0 – Upgrading from DSS four.0 through 4.20  Appointment Written: December 6th, 2013 Date Updated: May 28, 2014  Introduction HP Digital Sending Software 5.0 is the latest in a series of DSS versions to have shipped over the past 10 years. Previous versions of DSS accept fallen into 3 broad groups. The oldest are the versions 4.0 through 4.20 The four.91.xx versions The four.25.twenty version This white paper will talk over upgrading or migrating from DSS versions 4.0 through 4.20. Please see the other upgrade white papers for data on upgrades from 4.91.20 or 4.25.twenty versions of DSS.  Definitions Same Server Upgrade: This is when DSS 5.0 is installed on a server that already has an older version of DSS installed Migration: This is when the settings from an older version of DSS are captured from one server and moved to another server that has DSS five.0 already installed DSS 5 Supported Operating Systems: DSS 5 supports the post-obit operating systems. Windows 7 (32 and 64 bit) Windows 2008 (32 and 64 bit) Windows 2008 R2 Windows 2012          : The default install path for DSS on 64 bit systems is: c:\Program Files (x86)\HewlettPackard\HP Digital Sending Software 5.0. On 32 fleck systems the "Program Files (x86)" is replaced by "Program Files". Also, the person installing DSS tin instruct the install program to employ a custom install path. In this document                          will bespeak the install folder that the install program used for DSS file storage.  Page 1 of 3  white newspaper  Same Server Upgrades Same server upgrades are not supported for DSS versions 4.0 through 4.20. DSS versions four.0 through 4.20 just supported the Windows XP and Windows Server 2003 operating systems. Since DSS five does not back up either of those operating systems aforementioned server upgrades are not permitted.  Migrations DSS iv.0 -> 4.12 DSS 5 does not support a direct migration of settings from versions 4.0 through 4.12 of DSS. If you have i of these older versions the procedure is to get-go upgrade the server to DSS iv.20, and and so follow the instructions below for migrating setting from DSS 4.20 to DSS v. DSS four.13->4.xx To migrate DSS settings from a server running DSS iv.thirteen through four.xx to a server running DSS v follow these instructions. 1. The server running DSS iv.13 through 4.20 must have two Microsoft components loaded on it for the migration tool to run. If these components are not loaded on the DSS server please load them earlier starting. a. .NET 3.five SP1. b. Microsoft Visual C++ 2010 Redistributable Package. This bundle can be downloaded from: http://world wide web.microsoft.com/en-u.s.a./download/details.aspx?id=5555 2. Install DSS 5 on a new server 3. Copy the contents of the following folder from the DSS 5 server to the server running DSS 4.xiii through four.20:              \scripts\LegacyDssConfigurationBackup. 4. Register the hpcscp.dll a. Starting time a command prompt and navigate to the binder where the files were copied to in step 3 above b. Run the control: "regsvr32 hpcscp.dll" i. If this step fails with a message that says "LoadLibrary("HPCSCP.dll") Failed" run Windows update on the server and try again. 5. Run the LegacyDSSConfigurationBackup.exe utility from a control prompt. LegacyDssConfigurationBackup.exe –key                                  -path                                      -assistance  Where: –key is an optional parameter used to specify the encryption key for the output file. Note: If no encryption key is specified the output file will be unencrypted and no passwords will exist saved in the fill-in file. If the file is non encrypted so the organization administrator volition have to manually re-enter passwords subsequently the file is restored. (There are many places in DSS where passwords may have been entered including: credentials for SMTP servers, credentials for hallmark servers, credentials for shared folder access, etc.) -path is an optional parameter that specifies the path for the output file. The default path is the same folder from which the utility is run -aid is an optional parameter which will output aid for this executable  Page 2 of 3  white paper  6. Copy the output file created by the utility to a place where it can be read by the DSS 5 server. The settings output file will have a file name in the format: DssBackup_YYYYMMDD_HHMMSS.dss. vii. Restore the settings gathered from the older version of DSS using the standard restore capability built into DSS 5. The restore process can be accessed from the General tab within the DSS Configuration Utility.  A notation on the DSS v Restore Functionality The DSS v restore operation allows for the restore of all settings in the settings file or just some of the settings. For instance, all the settings other than the device list can be restored. Also, for settings that are lists such as folders, templates, and workflows, the restored settings tin either supervene upon the current settings or be merged with the current settings in the list. See the System Administrators Guide for more than detail.  Page 3 of three  white newspaper                                                                              

Source Exif Data:

File Blazon                       : PDF File Type Extension             : pdf MIME Blazon                       : application/pdf PDF Version                     : 1.6 Linearized                      : Yes Author                          : David Lerman Create Date                     : 2014:05:28 07:50:40-07:00 Modify Date                     : 2014:05:28 11:xviii:37-06:00 Has XFA                         : No Linguistic communication                        : en-US Tagged PDF                      : Aye XMP Toolkit                     : Adobe XMP Core 5.four-c005 78.147326, 2012/08/23-xiii:03:03 Format                          : application/pdf Creator                         : David Lerman Creator Tool                    : Microsoft® Word 2013 Metadata Date                   : 2014:05:28 11:eighteen:37-06:00 Producer                        : Microsoft® Word 2013 Document ID                     : uuid:d2949ae7-33fb-4652-92c8-b8a865fe8f71 Instance ID                     : uuid:48e62758-0ee4-43a2-97be-4525530b200d Page Count                      : iii        

EXIF Metadata provided past EXIF.tools