Shared Application: Deploying & running e/pop as a shared application
Technote: Q00010
Last Reviewed:
June 6, 2004
The information in this article applies to:
All e/pop clients including e/pop Professional, Basic, Remote and Alert
IT organizations that do not have electronic distribution utilities (sometimes called
"software push")
SUMMARY
The purpose of this article is to explain the fundamentals and the step-by-step process for deploying e/pop as a shared application on a network. Although WiredRed recommends local installs, a shared install is preferred if an organization does not have a software deployment utility to assist in the deployment process.
An important consideration for deploying e/pop within an organization is selecting a deployment method, and the method in which users run e/pop. The answer to these questions will determine the amount of time and tools needed to administer e/pop. Most programs require the program in question to be installed locally on the selected PC. This installation method is ideal for most applications but it increases the administrative overhead if the necessary tools are not present to assist in administering these programs.
e/pop is very flexible in that it offers administrators the option to install
the e/pop
client
application
as a locally
or shared install. In a local install, e/pop is installed and run from the C drive. In a shared install, e/pop system files are located in a shared folder and user personal files are store in a unique folder (home directory) for each user. The following diagram shows the concept of a shared and local install.
Setting e/pop to run as a shared program
There are several requirements needed to run e/pop as a shared program. The requirements are:
1. To achieve good performance, a server with sufficient RAM, hard disk space, a powerful I/O controller and CPU speed is required. A slow server PC is not recommended because the load placed on the CPU and I/O controller may be too much for the hardware. (see e/pop Requirements)
2. A shared folder to store the e/pop system files and sufficient user rights to access e/pop
3. A home directory on the file server for each user or a folder on the users C drive to store users personal files.
Step-by-step process for deploying e/pop as shared program
Step 1. Install Server. Run essetup.exe on the selected server PC
and complete the
installation wizard.
Step 2. Run the e/pop client setup on the selected server PC, and
make sure
the selected
install path
is a shared
folder.
After the
first phase
of the
installation,
complete the
questions in
the
connection
wizard.
Setup 3. Select the option
'Connecting
over a
network'.
Setup 4. Select Shared Installation
Setup 5. Specify
the IP
address of
the e/pop
server
Step 6.
After click
the
[Next]
button, the
e/pop wizard
will connect
to the e/pop
server at
the
specified IP
address.
If the
connection
is
successful,
the wizard
will display
the
congratulation
screen.
Click the
[Finish]
when
complete.
Step 7.
Navigate to
the folder
where the
e/pop client
was
installed
and double
click
epopcp.exe
to start the
e/pop
Control
Panel.
Step 8.
After the
e/pop
Control
Panel
starts,
click the
[Open]
button and
select
epop.exe
(e/pop pro),
epopb.exe
(e/pop
basic), or
epopa.exe
(e/pop
alert).
Step 9.
Select the
My Files
option on
the left and
enter the
directory on
the right.
Step 10.
Click on My
File
(continued)
on the left
and select
the first
option on
the right.
Step
11.
Click the
[Save]
button when
complete.
Step 12.
Configure
the PCs to
start e/pop
from the
shared for
folder
either from
a login
script or by
placing a
shortcut in
the Windows
Startup
folder.
|
