Konica Minolta IC-308 - Manual (Page 8)

8
5 Operating System Environment
5.1 Start-up Procedures
The operating system and Fiery system software are loaded
from the local HDD during startup.
The BIOS resident on the Fiery motherboard is read-only
and stores the information needed to boot up the operating
system. Changes to the BIOS (or removal of the BIOS)
prevent the Fiery server from functioning properly.
The Configuration Page lists the values specified during
set-up. Some information, such as FTP proxy information,
password information, and SNMP Community Names, are
not included on the Configuration Page.
5.2 Linux
Linux systems do not include a local interface that allows
access to the operating system.
5.2.1 Linux Anti-Virus Software
The Linux operating system used on integrated Fiery
servers is a dedicated OS for integrated Fiery servers only.
It has all OS components needed by a integrated Fiery
server, but not some OS components on some general
purpose Linux systems, such as Ubuntu. In addition to
having better performance, this dedicated OS is not subject
to the same virus vulnerability as a general purpose Linux
system and Microsoft OS. The anti-virus software designed
for general purpose Linux OS may not be able to run on
integrated Fiery servers.
5.3 Windows 7 Professional
The Windows-based Fiery server ships with a default
Windows 7 Administrator password. It is recommended for
the administrator to change the password upon installation.
It is also highly recommended to change the password
regularly to comply with the organization’s IT policy.
Administrator password gives a user full access to the
Fiery server locally and/or from a remote workstation.
That includes, but is not limited to, the file system, system
security policy, and registry entries. In addition, this user
can change the administrator password and to deny anyone
else access to the Fiery server.
5.3.1 Microsoft Security Patches
Microsoft regularly issues security patches to address
potential security holes in the Windows 7 operating system.
The default setting of Windows Updates is to notify users
of patches but don’t download. The Fiery Administrator can
change the default setting in Windows Update or install
manually the security patches.
5.3.2 SMS Tools
EFI has its own dedicated system update tool for its Windows-
based systems. This tool handles the retrieval of all applicable
MS security patches and Fiery software updates. The Fiery
server does not support any third-party SMS tools for retrieving
and pushing updates to the Fiery server.
5.3.3 Windows Anti-Virus Software
Administrators can install anti-virus software on Fiery
servers with FACI kits. A local GUI is required for proper
configuration of anti-virus software. Anti-virus software is
most useful in a local GUI configuration, where users have
the potential to infect the Fiery server with a virus through
standard Windows actions.
For Fiery servers without a FACI kit, it is still possible to
launch anti-virus software on a remote PC and scan a
shared Fiery hard drive. However, EFI suggests that the
Fiery administrator work directly with the anti-virus software
manufacturer for operational support.
EFI ensures Fiery servers’ compatibility with Anti-Virus
software by testing the latest releases of Norton’s Symantec
Endpoint Protection Small Business Edition, McAfee Virus
Scan Enterprise, Microsoft Security Essentials, and Trend
Micro Worry-Free Business Security Advanced software on
Fiery servers. While EFI does not provide anti-virus software
on Fiery servers, we recommend that administrators refer to
section 3.1 Network Ports in this document when configuring
an anti-virus solution so that legitimate network-based
services on Fiery servers can operate without interruption.
EFI supports the use of anti-virus solutions as long as they
are used in accordance with this specification. EFI does not
support or give any warranty regarding the efficacy of any
anti-virus software.
5.4 Email Viruses
Typically, viruses transmitted via e-mail require some type
of execution by the receiver. Attached files that are not PDL
files are discarded by the Fiery server. The Fiery server also
ignores e-mail in RTF or HTML or any included JavaScript.
Aside from an e-mail response to a specific user based on
a received command, all files received via e-mail are treated
as PDL jobs. Please see the details on Fiery e-mail printing
workflow in Section 6.4 in this document.