HP DSS 5 User Manual

							3 Installation and configuration
This chapter contains the following topics:
●
Planning the DSS deployment
●
Installation
●
Configuration
ENWW23 
						

							Planning the DSS deployment
This section contains the following topics:
●
System and environment requirements
●
System security requirements for using DSS
System and environment requirements
This section contains the following topics:
●
Software requirements
●
Temporary jobs folder
●
Hardware requirements
●
Device firmware requirements
●
Multiple DSS servers
●
Port requirements
Software requirements
The following table shows the server software requirements.
Table 3-1  DSS software requirements
Area Requirements
Operating systems
●Microsoft Windows 7, 32 and 64–bit
●Microsoft Windows Server 2008, including R2, 32 and 64–bit
●Microsoft Windows Server 2012
NOTE:64-bit operating systems are supported, but DSS runs in 32-bit mode
Virtual servers
●VMware ESX 3.5 and later
●Microsoft HyperV
24 Chapter 3   Installation and configuration ENWW 
						

							Table 3-1  DSS software requirements (continued)
Area Requirements
External database Compatible databases which can be used if you choose not to install the default DSS
database:
●Microsoft SQL Server 2005 (full or express versions)
●Microsoft SQL Server 2008 (full or express versions)
●Microsoft SQL Server 2012 (full or express versions)
Miscellaneous .NET Framework 3.5 and 4.0
NOTE:If the .NET Framework 4.0 is not present on the system where DSS is being
installed, the installer will install .the .NET Framework 4.0 during the installation process.
If the .NET Framework 3.5 is not installed on Windows 7 or Windows Server 2008
systems where DSS is being installed, the installer will install the .NET Framework 3.5
during the installation process.
For Windows Server 2012 systems where DSS is being installed, the .NET Framework
3.5 must either be installed 
before running the DSS installer, or the DSS installer must
be able to access the internet to download the .NET Framework 3.5 for installation.
Temporary jobs folder
DSS 5.0 temporarily stores job files on disk while processing jobs. All job files are deleted after the
job has finished processing. By default, this jobs folder for temporary storage is located within the
installation folder sub-folders. Some customers might choose to change the location of this jobs
folder. In DSS 5.0, this change is made by editing a configuration file.
Changing the location of the Jobs Folder
The file that controls the location of the temporary jobs folder is:
●\filesystems\core\bin\xp-x86
elease
vram.csv
Within the nvram.csv file find the line that reads:
●FE966859-E2D0-48e6-8467-BF6F5A417643,CustomerDataPartition,str,..\..\..
\..\CustomerData\Dss
To change the location where temporary job files are stored, replace the part of the line that reads “..
\..\..\..\CustomerData\DSS” with the path of the folder where you want the temporary files to be
stored.
For example, to store the files on the d: drive in a folder named dsstemp, change the line to the
following:
●FE966859-E2D0-48e6-8467-BF6F5A417643,CustomerDataPartition,str,d:
\dsstemp.
After editing the file and saving the changes, the DSS service must be stopped and restarted for the
change to take effect.
ENWW Planning the DSS deployment 25 
						

							Hardware requirements
DSS hardware requirements vary with the load put upon the system. The primary load is due to
processing of jobs that come in from devices.
It is strongly recommended that DSS run on its own server with no other server applications running.
If other applications do run, they will also use system resources, and the resources used for those
applications must be added to the consideration for resource usage by DSS when deciding what
hardware is needed by the DSS server.
The primary factors that affect load are:
●Peak job requests per unit time
●Size of the job being transferred from devices
●Server based operations such as OCR and LAN fax with Notification support
Jobs that are not configured to be processed by the DSS OCR engine are created in the devices in
their final format and transferred to DSS for routing to their destinations. Jobs that are to use the DSS
OCR engine are sent to DSS as 300 dpi color JPEG images. There are many factors that affect the
size of jobs that are created in the devices including, but not limited to:
●Number of pages
●File format
●Resolution
●Compression
●File content
There are so many factors that affect the load on the DSS server that not all variations can be tested.
Below are tables of three different load scenarios and the recommended hardware for each load. But
given the variables, it is highly recommended that administrators use tools, such as Microsoft
Performance Monitor, to monitor their DSS servers’ critical resources of processor bandwidth,
memory usage, free disk space, and network bandwidth for any usage or performance bottlenecks.
The load scenarios tested are below. An equal percentage of e-mail, folder and workflow jobs were
used during the testing.
Table 3-2  Load scenarios
Load Scenario Job frequency (peak) Average Job Size % OCR
Minimum 
						

							Table 3-3  Recommended hardware configurations for load scenario (continued)
Load scenario ProcessorMemory Free disk space
for InstallationFree disk space
for temporary job
filesNetwork
bandwidth
Medium 2 core x2 GHz 2 GB 1 GB 100 MB 100 Mb/s
High 4 core x2 GHz 2 GB 1 GB 100 MB 100 Mb/s
ENWW Planning the DSS deployment 27 
						

							Device firmware requirements
To support DSS features, some devices require a minimum revision of firmware. Over time, as new
features become available in DSS, it may be required to update the device firmware for compatibility.
These changes will be documented in detail in the DSS release notes.
Table 3-4  Device firmware requirements
  Model number Minimum firmware
revisionFirmware
dateFirmware version
pre-FutureSmart devices
MFPs HP LaserJet 4345MFP 09.220.7 12/8/2010 N/A
HP LaserJet 4730MFP 46.300.3 11/24/2010 N/A
HP LaserJet 9040MFP 08.210.5 11/27/2010 N/A
HP LaserJet 9050MFP 08.210.5 11/27/2010 N/A
HP LaserJet 9500MFP 08.210.6 11/29/2010 N/A
HP LaserJet M3035MFP 48.171.5 11/29/2010 N/A
HP LaserJet CM3530MFP 53.101.5 12/6/2010 N/A
HP LaserJet M4345MFP 48.171.5 11/29/2010 N/A
HP LaserJet CM4730MFP 50.151.0 12/6/2010 N/A
HP LaserJet M5035 48.171.5 11/29/2010 N/A
HP LaserJet CM6030MFP 52.121.2 12/6/2010 N/A
HP LaserJet CM6040MFP 52.121.2 12/6/2010 N/A
HP LaserJet M9040MFP 51.121.2 12/6/2010 N/A
HP LaserJet M9050MFP 51.121.2 12/6/2010 N/A
Digital senders HP 9200C 09.220.1 11/13/2010 N/A
HP 9250C 48.160.3 11/18/2010 N/A
FutureSmart Devices
MFPs HP Color LaserJet Enterprise CM4540
MFP2200643_228337 6/23/2012 FutureSmart 2 SP1
HP LaserJet Enterprise M4555 MFP 2200643_228339 6/23/2012 FutureSmart 2 SP1
HP LaserJet Enterprise 500 MFP M525 2200643_228344 6/23/2012 FutureSmart 2 SP1
HP LaserJet Enterprise flow MFP M525 Any Any Any
HP LaserJet 500 Enterprise color MFP
M5752200643_228345 6/23/2012 FutureSmart 2 SP1
HP LaserJet Enterprise color flow MFP
M575Any Any Any
HP LaserJet 700 Enterprise color MFP
M775Any Any Any
Scanjet Enterprise HP ScanJet Enterprise 7000n 2200643_228343 6/23/2012 FutureSmart 2 SP1
HP ScanJet Enterprise 8500 2200643_228339 6/23/2012 FutureSmart 2 SP1
28 Chapter 3   Installation and configuration ENWW 
						

							Multiple DSS servers
There are several reasons for considering using multiple DSS servers:
●If there are more than 1000 products to be managed, then more than one server is necessary.
●If the load on any one server is too great for its hardware capability. This can happen if many
devices are regularly sending very large jobs, if OCR is used frequently, or if network bandwidth
is limited.
●For highly distributed systems of devices (depending on the available network infrastructure),
multiple, distributed DSS servers help to ensure network reliability and bandwidth between the
DSS servers and the products they manage.
DSS servers function independently of any other DSS server and do not, by themselves, form any
type of clustering for enhanced functionality. This means that DSS servers will not share licenses.
Each server must have the appropriate number of license seats to support its attached devices.
Separate DSS servers also do not share address books or job logs.
DSS servers can be installed into a Microsoft Windows Server 2008 cluster for enhanced failover
functionality. For detailed instructions on how to install DSS into an MS Server 2008 clustered
environment, please see the white paper on this subject that is available at 
www.hp.com/support/dss.
ENWW Planning the DSS deployment 29 
						

							Port requirements
DSS 5.0 uses a number of industry standard network protocols and their corresponding TCP and
UDP ports in order to facilitate its Digital Sending functionality, such as Send to E‑mail, Send To
Folder, Authentication, and LDAP Replication. This section gives an overview of which ports are used
in different configurations.
In its most basic configuration, DSS 5.0 requires ports 1783, 5213, 7627, and 161 to function.
Administrators can refer to the table in this section to determine which ports are required for their
specific configuration of DSS 5.0.
Ports used
DSS uses the TCP/IP protocol to communicate on the network. Which TCP or UDP ports are used
depends on which features are enabled in DSS 5.0 and which underlying protocols facilitate these
features. Also, note that for each protocol DSS acts as a server or client, or both. The following table
provides an overview. Administrators should ensure that the required ports are open at appropriate
points in the network, for example, desktop firewall, switches, and routers.
Table 3-5  Ports used by DSS 5.0
Feature Type Protocol Port Role of DSS Can it be
changed?
Device
communication
with pre-
FutureSmart
devicesRequired DSMP
(HP Proprietary)1783 (TCP) Server & client No
WS-* (WS-STAR),
used for device
communication
with FutureSmart
devices and for
communication
between DSS and
the Configuration
UtilityRequired HTTPS 7627 (TCP) Server & client No
DSS Address
Book access for
FutureSmart
devicesRequired Secure SQL 5213 Server No
Device data
collection 
3Optional SNMP 161 (UDP) Client No
E‑mail
notifications,
e‑mail via serviceOptional
1SMTP 25 (TCP) Client Yes
Send to Folder
(Network UNC
path)
2
Optional CIFS / SMB 445 (TCP) Client No
Send to FTP Optional FTP 21 (TCP) Client No
LDAP Replication
& Authentication,
simple bindOptional LDAP 389 (TCP) Client Yes
30 Chapter 3   Installation and configuration ENWW 
						

							Table 3-5  Ports used by DSS 5.0 (continued)
Feature Type Protocol Port Role of DSS Can it be
changed?
LDAP Replication
& Authentication,
simple over SSL
bindOptional LDAP 636 (TCP) Client Yes
LDAP Replication
& Authentication
SPNEGOOptional Kerberos 88 (TCP) Client No
LDAP Replication
& Authentication,
Global CatalogOptional LDAP 3268 (TCP) Client Yes
DNS hostname
resolutionOptional DNS 53 (TCP) Client No
WINS hostname
resolutionOptional NetBIOS/WINS 137,138,139 Client No
SMTP and LDAP
server discovery –
when an MFP
sends out a
broadcast packet
looking for SMTP
or LDAP servers
DSS will respond
with any servers it
knows aboutOptional Broadcast 22986 Server No
SMTP and LDAP
server discovery –
DSS will
broadcast this
packet when
asked to search
for LDAP or SMTP
serversOptional Broadcast 22986 Client No
1If a mail gateway is not required, enter a dummy address (0.0.0.0) in the Configuration Utility.2Does not apply to local folders, for example. c:\myfolder.3SNMP is only required to get and set paper sizes in pre-FutureSmart devices and to get the firmware version from pre-
FutureSmart devices for use in LanFax job logs. We are working to remove these last uses of SNMP in future versions of
DSS
DSS Address Book access for FutureSmart devices
HP’s FutureSmart devices now access the DSS Address Book by connecting directly to the SQL
database on port 5213. Therefore, port 5213 must be open between FutureSmart devices and the
SQL database server. The database server is the DSS server by default, but can optionally be
configured to be a database on a different server.
Pre-FutureSmart devices continue to make address book requests of the DSS service, not directly to
the SQL database, via port 1783. The DSS service accesses the database and returns address
information to the device, also via port 1783.
ENWW Planning the DSS deployment 31 
						

							Summary
In its most basic configuration, DSS 5.0 requires ports 1783, 7627, and 5213 to function. At
installation, DSS will register itself with the desktop firewall to ensure connections are allowed on
these ports. Administrators can refer to the matrix in this document to determine which ports are
required for their specific configuration of DSS 5.0.
System security requirements for using DSS
Security to start the Configuration Utility
The DSS Configuration Utility uses Windows security to determine which users are allowed to start
and run the Configuration Utility. When the Configuration Utility is first started, the user is prompted to
enter the address of the server on which the DSS service is running that they want to control with this
Configuration Utility session. Users are allowed to run the Configuration Utility under any of the
following conditions:
●The user is a member of the local or global administrators group on the server running the DSS
service
●The user is a member of a group on the server running the DSS service that has been
configured to allow Configuration Utility access. By default, DSS is configured to use a group
named "DSSAdmins" for this purpose. If you want to use a group by that name you must create
it on the system. The name of the group can be configured, or multiple groups configured, to
allow DSS access. This configuration is contained in the file “\FileSystems\Product
\DSS\Configuration\HP.Dss.App.Service.Config.xml.”
●If a user attempts to run the Configuration Utility without being a member of the administrators
group or the configured group, they will be prompted for the credentials of a user that is a
member of one of those groups.
When changing the configuration of the group(s) that allow non-administrators to access the
Configuration Utility, the DSS service should be stopped, the configuration file edited, and then the
DSS service restarted.
Permissions needed to run DSS with full functionality
Administrators have all the permissions necessary to run DSS. But if the DSS server has Windows
User Account Control (UAC) enabled, the administrator might have to use the “Run as Administrator”
command to have the necessary permissions.
Non-administrators can start the Configuration Utility if they are members of the proper Windows
group, but this does not give them the necessary OS permissions to execute the tasks the
Configuration Utility performs. In order for proper Configuration Utility operation, the user must have
the following OS permissions on both the remote server (if they are running the Configuration Utility
from one system to control the DSS service on another server) and the sever which is running the
DSS service.
●Read/write access to the following area of the file system:
◦ \Hewlett-Packard\HP Digital Sending Software 5.00
●Read/write access to the following areas of the registry:
32 Chapter 3   Installation and configuration ENWW