EMC Client Installation Guide
EMC Client Installation Guide
When configuring report printers for remote networked printers, one must use the full network path enclosed within quotation marks. This step ensures that the system can locate the printer on the network and differentiate it from local printers .
EMC Client offers comprehensive functionality by incorporating the Configurator, Control Panel, Audit Trail, and Credit Card utilities, which allows for database maintenance without accessing the server directly . In contrast, the RMC Client is primarily used for Report Writer and Autosequencer functions and is not as integrated with server-side maintenance utilities .
Renaming and configuring PrintPortrait.txt and PrintLandscape.txt ensures that the printer location and specific printer names are properly recognized by the system. Failing to do so can lead to configuration errors where printers might not appear for selection or errors in print jobs being sent to incorrect printers due to misconfigured names, especially for networked printers which require precise naming conventions .
The installation involves opening the relevant directory, copying and renaming the configuration files to match printer locations, editing the printer names in the files, and repeating the process for multiple printers. Each step ensures printers are correctly recognized and accessible through RMC Client, aligning configuration with physical setup .
The reboot after EMC Client installation ensures that all configuration settings and system changes are properly applied and active. Skipping the reboot could result in incomplete installation where certain functions or connections might not work as intended .
Quotation marks are necessary around printer names in the configuration files when the printer's name contains spaces (e.g., “HP Laser Jet 4”). This ensures that the system interprets the entire string as a single printer name instead of distinct commands or parameters separated by spaces .
Supporting both SQL and Oracle databases increases organizational flexibility, allowing businesses to integrate with existing systems without the need for significant backend changes. This compatibility broadens application use and enhances the adaptability of the EMC Client across diverse database environments .
Both EMC and RMC Clients run on Windows 2003 Server, Windows XP, and Windows 2000 systems. However, RMC also supports Windows NT, whereas EMC does not. This difference implies that older setups running NT can only install the RMC Client, limiting the use of full EMC capabilities without upgrading the operating systems .
Applying the same service packs to both the 9700 server and the client PCs ensures compatibility and proper functioning of the RMC Client. Inconsistent service pack updates can lead to software mismatch errors or functionality issues .
The installation of EMC Client begins with accessing a web address through Internet Explorer and involves selecting database type and rebooting the system after completion . In contrast, RMC Client installation involves starting from a CD, selecting specific components, and may require applying additional Service Packs post-installation .