|
There are several Settings and Components that need to be updated or installed on
every Workstation on which an EJS OnSite program is supposed to be used. When installing or updating a
workstation or when updating to the latest version of EJS OnSite, the EJS OnSite Install program will also
automatically update the workstation components on the computer that runs the update.
In addition, every EJS OnSite application (besides the Install program) will do an automatic test at startup, to determine
if all the components that are required for that application are setup and installed. If anything is missing, the same
Workstation Component Installation dialog that is used by the Install program will automatically be displayed.
Because the Installation of most of the Settings and Components requires Windows
Administrator rights, it is possible to disable the automatic popup dialog at program startup, so that Limited Access
Windows users aren't bothered by it, everytime the program starts.
This update dialog (shown below) can also be manually accessed at any time from the Main Menu of any EJS OnSite application
under: "Utility" → "Updates / Installations" →
"Install Workstation Components", to check the current status of the workstation and to
complete the installation, if necessary.
The check box on the bottom right, which is labeled "Don't ask to Install on this Workstation again."
can be used to suppress this popup dialog at startup for this workstation.
Any workstation Setting or Component that is missing or needs to be updated or installed
will be automatically highlighted in red and checked for installation, as
can be seen in the picture below. The items that are already installed and updated aren't highlighted and can't be selected,
while the items shown in light gray aren't applicable to the current Operating System or EJS OnSite application. If the mouse
pointer is moved over any of the items listed on the left, an explanation of the purpose of the Component or Setting is shown
in the text box on the top right, while the text box on the bottom right will show the current status of the feature: if it is
missing, already installed or not required.
Pressing the "Cancel" button or the "ESC" key will close the
Workstation Component Installation dialog without attempting to install any of the possibly selected or required features,
which is the recommended choice for users without Windows Administrator rights on that workstation.
To install or update the required components just press the "Start" button or the
"Page Down" key. After each component is installed or updated, a small dialog will show if the
update was successful or not.
The PDF Creator Printer Driver installation requires some user input but is relatively straightforward.
Click here to get step-by-step instructions on how to do that installation. In principal,
you can just follow the prompts and click through, using the default settings, with one exception: Un-select the Installation
of the "Yahoo Search Bar for Internet Explorer" add-on in two of the dialogs, as you don't need
(and probably don't want) that browser plug-in to be installed on your computer!
NOTE: Some of the components will be installed by running dedicated Installation programs, like
the PDF Creator, while others must be registered with the Operating System. In some cases, specifically on
Windows Vista, Windows 7, and Windows Server 2008, some of those programs
might start minimized, and will only show up as a usually blinking push
button on the Windows Taskbar (which is normally located) on the bottom of the Windows Desktop, as shown in the red box at
the bottom of the following picture:

The Installation Process can't continue, until you click on that button to view the minimized program's dialog and confirm
the displayed message, as shown in the next picture:

There are several reasons why the Installation of some or all of the Workstation Components might be unsuccessful. The most
common problems and possible workarounds are listed here:
If UAC (User Access Control) is enabled on Windows Vista, the program might not be
able to install or update some of the components even if the user has Windows Administrator rights,
because of missing file-access rights in the "C:\Program Files\" directory. This is usually
the case if a message like the following is displayed when trying to install a component:

This can only be resolved by temporarily disabling UAC to allow the program to create that directory
(if it is missing) and copy the required files into it. A similar message is also displayed when the user doesn't have
Windows Administrator rights on most Windows operating systems.
If an older version of the PDF Creator printer driver is already installed, it must be un-installed,
before the newer version can be installed. It is recommended to do this (through the Windows Control Panel)
if a message like the following is displayed while trying to install this component:

If an EJS OnSite program is run with the credentials of a different user (using the "Run as ..."
or "Run as Administrator" options) it is necessary that both users have the same drive letter
mapped to the location where the EJS OnSite application is installed. If this isn't the case, the program might not start
and will instead show one of several possible Operating System error messages. The most common ones are the following three:
If the Drive Letter specified in the Workstation's "UserParm" database doesn't exist for
the user running the program, the following error might occurr:

If the Drive specified in the Workstation's "UserParm" database isn't ready, most likely
because it points to a Drive that contains removable media, like a Floppy Disk, or CD / DVD Drive, the following error
might occurr:

If the specified path is a UNC (Uniform Naming Convention) Path (in the form of
"\\ComputerName\SharedFolder\Resource" rather than a Drive Letter like
"F:\", usually because no drive letter was mapped to the location from where the program
was started, the following error might occurr:

Other Operating System Errors are also possible, but virtually all of them are caused by an incorrect or missing Drive
Letter mapping.
|
|