Policy Manager Two Multi-User/Network Installation Instructions Table of Contents

loyalsockvillemobΔίκτυα και Επικοινωνίες

27 Οκτ 2013 (πριν από 3 χρόνια και 9 μήνες)

84 εμφανίσεις



Policy Manager Two


Multi
-
User/Network Installation Instructions


Table of Contents


Multi u
ser (Network) setup

................................
................................
................................
.

2

1) Guidelines and choosing the server computer

................................
................................

2

2) Installing the server
................................
................................
................................
.........

3

3) Configuring the server

................................
................................
................................
....

4

4) Client Configuration

................................
................................
................................
.......

8

Installing the client (or not)
................................
................................
.............................

8

Running
Policy Manager Two

Clients for the first time
................................
...................

11

Setting up Multi User Serial Numbers (sn.ini)

................................
................................
.

11

Setting up Automatic server/database connection (server.ini)

................................
.........

12

How to Open Databases in Policy Manager Two

................................
.............................

14

Network Protocol

................................
................................
................................
..............

15

Server Name
................................
................................
................................
......................

15

Verify Server
................................
................................
................................
.....................

15

Server status

................................
................................
................................
......................

15

Database Name

................................
................................
................................
.................

16




2

Multi user (Network) setup


Follow these instructions to set up Policy Manager Two on a network with many people
sharing the same data.


We'll walk you through the following s
ections:





1) Guidelines and choosing the server computer




2) Installing the server




3) Configuring the server




4) Client Configuration


Setting up a Policy Manager Two server is quite simple you'll see. You don't need to be a
computer expert, but you

will need to be familiar with your local network setup.


If you already have a Policy Manager Two server on your network and you just want to
add a computer to access the server, you can go to Client Configuration



1) Guidelines and choosing the ser
ver computer


Policy Manager Two user a separate program that runs on one computer we call the
"server". You install and run the server application on one computer. Other computers
running Policy Manager Two connect the server computer to access data (th
e "clients").


After a few setup steps, you will be running a true client
-
server database, in a setup
similar to Oracle or MS SQL Server. Having a separate server program helps ensure data
integrity.


Ideally, the server is a separate computer than the on
es people use at their desktops to run
the Policy Manager Two client program. It does not need to be a super powerful
computer for a small network of 5 or so users at a time. We suggest at least a Pentium III
and 64MB of RAM. More power for more users.


The server should also be running Windows 2000 or Windows XP. It will work fine on
Windows 98 or Windows ME, but these operating systems tend to be unstable, needing
frequent reboots and you don't want this for your database server. You don't necessaril
y
need the 'Server" versions of Windows 2000 or XP. Policy Manager Two clients will get
data only through the server and will not use up what Microsoft calls Client Access
Licenses (CALs).


If you don't have a computer to dedicate to being the server, you

can also run the server
on anyone's desktop pc. It doesn't consume much in the way of resources when not in
use.



3

You also want the Policy Manager Two server program to run on the computer that has
the disk drives local. In other words, if you run the s
erver application on one computer,
but the data files are on a network (remote) drive, you create double the network traffic
and it will be slower.


Wherever you decide to run the server, be sure to have good backup procedures in place
for the Policy Manag
er Two data. We have found the server to be quite reliable and have
not experienced any data corruption, but computers and hard drives do fail.



2) Installing the server


Insert your Policy Manager Two installation CD. If it does not start by itself, ru
n
Setup.exe in the root directory of the CD.


When you purchased Policy Manager Two, Network version, you should receive a Multi
User Server Serial Number to enter at the start of the installation. The server serial
numbers start with "NS". Contact us i
f you don't have a serial number or have other
questions. Call Jim Masters at 510
-
339
-
3803 or e
-
mail
jmasters@cencomfut.com
.


Wherever you choose to install the server program, the Data directory will be at t
he same
location & should be a local drive with at least a few hundred megabytes free. You can
also change the Data location later.


After running the installation, you'll have directories like:




In the Server directory, ffserv32.exe
is the program you'll run on the server.


The Data directory is where all of the Policy Manager Two data gets installed. You'll
need to know the path to this Data directory in a step ahead, so you may want to make a
note of it.


All the other directories,
Bin, Reports, and Help are for the Policy Manager Two client
program (..
\
Bin
\
PolicyManager2.exe). You may run the client program on ("while sitting
at") the server if needed. With these directories on the server, clients can run Policy

4

Manager Two direct
ly from these server directories
-

you don't need to run an install on
every client.



3) Configuring the server


In this section, we'll start the server and set a few things to get it configured. We like it to
start itself up minimized to be sure it is a
lways on for users to connect to.


Go to the server computer (the one that will run a server program that other users will
connect to). This should be the computer you ran the installation with the server serial
number.


When the server is running, you'll

see the TurboPower FlashFiler icon in your task tray
(usually in the lower right of your screen). Like:




If you see the FlashFiler icon in your tray (the server is already running), double click the
icon to open it.


Otherwise, start

the server by clicking the Windows Start Menu, Programs, Policy
Manager Two, Policy Manager Two Server.


You'll get a window that looks like the one below.




5

First, we'll set the Server Name. Click the Server menu and choose Name...




You can name the server whatever you want. You can name it the same as the computer
or make up a name. For example, "FFServer". When clients connect, they specify the
server name and the address of the computer, so be sure to rememb
er or write down what
your server name is.





Now, from the Config menu, choose General configuration...





On this first tab, we suggest you check both of the boxes under Startup Options (like
below). This will sta
rt up the server automatically & minimize it, which is easiest to
manage once it is set up and running.



6



Next, click the Network tab. Select the Default Protocol for the network you are using.
This depends on your local network. If
you have "IP Addresses" you should choose
TCP/IP like below. Also, choose the network (card) under Biddings TCP/IP or <ALL
INTERFACES> to make the server visible over all the networks this server sees.




Press OK to save these settings
.




7

One more step & we'll be ready to start the server. We need to add an "Alias". This is
giving a database name to the data directory you chose during the installation. From the
Config menu, choose Alaises...




Make up a name for t
he database like "PM2Data" and type it in the first (Alias) column.
When users connect to this server, they will see this name and choose it in a list. In the
Path column, type the full path to the directory where you installed Policy Manager Two
+ "
\
Dat
a". For example, "C:
\
Program Files
\
PolicyManager2
\
Data" (don't type in the
quotes).




Click OK to save your new Alias and close the window.



Now, back on the main screen, you are ready to start up the server. Click the red up
arrow

button to start the server.






8

Note that if you wanted to stop the server, you click the down arrow button on this
screen. This screen also displays the number of clients currently connected. If there are
active connections, it is a
good idea to ask them to exit before you bring the server down
on them.


Now you can minimize the server & it will stay running & be ready for client
connections.


At any time you can double click the FlashFiler icon in the task tray to check the status of

the server, see if anyone is connected, etc.



4) Client Configuration


These sections describe how to set up and run Policy Manager Two to access shared data
over your network.


We'll walk you through:




Installing the client (or not)




Running Policy Mana
ger Two Clients for the first time




Setting up Multi User Serial Numbers (sn.ini)




Setting up Automatic server/database connection (server.ini)


Installing the client (or not)


You can run PolicyManager2.exe, the client program:


1) from a
shared serve
r folder

directly


or

2) from a
locally

installed or copied PolicyManager2.exe


Regardless of which of the two setups you use (or mix of them), the PolicyManager2.exe
program file is "dependency free", which means it doesn't rely on any external .dll f
iles
on the local computer. You can move it around without worry and it won't break due to
some other errant installation. We expect this will make your life easier as
administrators!


1)
shared server folder
is often easier since you don't have to run t
he installation on each
client. Recall, when we installed Policy Manager Two on the server, it also installed the
directories and files the clients need to run Policy Manager Two.


The clients only need to access a few directories, so generally clients sh
ould not be able
to see, read, or write to most of the directories on the server (keep it secure). You don't
want the clients to have "file system" level or any permissions on, for example, the Data
directory. Client access to those files is handled by t
he server program.


9


Clients set up to run PolicyManager2.exe directly from the server will need READ access
to the ..
\
PolicyManager2
\
Bin directory on the server.


Also give the clients READ access to the ..
\
PolicyManager2
\
Help and
..
\
PolicyManager2
\
Repor
ts. If you want this or any of the clients to be able to modify
reports or add new ones, they will need WRITE access to the ..
\
PolicyManager2
\
Reports
directory as well.


Now you can configure any of the clients to run Policy Manager Two by simply making a

shortcut to ..
\
PolicyManager2
\
Bin
\
PolicyManager2.exe on the shared server folder. For
example, go to the client desktop, and browse to the
\
\
servername
\
..
\
PolicyManager2
\
Bin
directory in Windows Explorer. Select the PolicyManager2.exe file, and drag it
to the
client desktop... being careful to hold down the Ctrl + Shift keys so you make a shortcut
(and not a copy).


In this setup, all clients are using the same, shared, sn.ini file. This file keeps your Policy
Manager Two Multi User Client Serial Numb
ers, which we will get back to in a bit.


This setup makes updating the one copy of PolicyManager2.exe very easy (don't have to
update each client).


One drawback of this setup that may or may not apply to you is, because we are using
"file shares" to run
the exe, we will use up Windows Client Access Licencse(s) (CALs)
which may become a limit if you are not running the "Server" versions of Windows 2000
or XP. The next setup, 2), does not require any file shares on the server or use up CALs.


2)
locally

c
an work better for some clients. Some advantages of running a local copy of
PolicyManager2.exe include:




Faster startup



"dedicated" Serial Number(s)



Local copy of Reports


The simplest way to set up a local (client) copy of Policy Manager Two is to run th
e
Policy Manager Two installation, entering the Multi User Client Serial Number during
the install. You can run the Setup.exe installation program from the Policy Manager Two
CD, or, you can copy Setup.exe to a shared network folder and tell people to ins
tall it
from there.


When the Multi User Client is installed, choose a local directory for the location when
prompted during the install. You will get local ..
\
PolicyManager2
\
Bin, Help and Reports
directories. Note that there is no local Data directory c
reated
-

you will log into the
server from the client.



10

If what your user wanted was really their own local copy of the data, then they should use
the Single User version of Policy Manager Two. You could create a separate Alias (Data
directory) and let
the client(s) use a different database, but they will still need to log into
a server.


A shortcut will be added to the Windows Start menu and Policy Manager Two should be
ready to go. When it is run for the first time on a particular computer, you will g
et
prompted at startup for the server login stuff. See Open Database Window for more about
this window and logging into a server.



11

Running
Policy Manager Two

Clients for the first time


If you are setting up a new network and/or running Policy Manager fo
r the first time, you
may be prompted with an Open Database window. In this window, you can specify the
server and database names. If you are not the person that set these up, these names
should be provided to you (see Configuring the server).


If you se
t the clients up with a server.ini file, they will never have to see the Open
Database window and you won't have to give them instructions with the server/database
names. We'll get to server.ini in another section, but for now, just know you can run the
i
nstallation on the clients, enter a serial number, then copy a server.ini file to the local
Bin directory for a hassle free startup.



Setting up Multi User Serial Numbers (sn.ini)


The number of people that can access the Policy Manager Two data at the sa
me time
depends on the number of client licenses you have purchased.


You can choose to make any of your licenses (serial numbers) shared among many
people or dedicated to individual(s). In other words, you have the flexibility to make
licenses "floating"
, where it is first come, first serve until the licenses are used up.


Some or all of the Policy Manager Two clients can also have a "dedicated" or "node
-
locked" license by running the installation on the client with their "own" Multi User
Client Serial
Number.


Hang in there, it is really simple in the end, which will help you administer licenses
(Serial Numbers) easily. When PolicyManager2.exe starts up, it looks in that same
directory for a file named "sn.ini". In there is a list of serial numbers
, like:




All that really matters to the client are the "[NC..." entries, which it will use to log into
the server. If all of the numbers are already in use by other users, then they will need to
login later, etc.



12

Now, as you set up y
our network clients, if you have them all starting
PolicyManager2.exe from the same network share, you'll keep all of your serial numbers
in that one (server) "..
\
PolicyManager2
\
Bin
\
sn.ini" file.


You can edit sn.ini manually in a text editor or by using t
he Help|About... box in Policy
Manager Two to add new Serial Numbers.


For those clients that installed Policy Manager Two (Multi User Client) to a local
directory, you can leave them with the one serial number they entered, which will already
be in their
local sn.ini. Alternatively, you can combine/add serial numbers into one sn.ini
file and copy the same, "shared", set of serial numbers to the clients' local
"..
\
PolicyManager2
\
Bin
\
sn.ini" file.



Setting up Automatic server/database connection (server.in
i)


One more thing that will save you time in setting up client computers is the server.ini file.
When PolicyManager2.exe starts, it will look in that same directory for a file named
"server.ini". Inside that file are the parameters the user would otherw
ise have to choose
in the Open Database window (Network Protocol, Server Name/address, and Database
Name).


Having the server.ini file ready to go for your users saves them (and you) from having to
specify the Server and Database stuff.


If all your users
are running from the same shared (network) "..
\
PolicyManager2
\
Bin"
directory, then you just need to login once the first time you try/test it and all future users
will log in to the same database by default.


You may need to give yourself WRITE permissions

to this file and/or directory so that
server.ini can be updated. Then you can make it read only again
-

users will normally
read server.ini, but don't need to write to it.


If you have clients running local "..
\
PolicyManager2
\
Bin" directories, copy anot
her
server.ini file into their local Bin directory after running the Policy Manager Two
installation. In other words, get logged in on one computer, which will create a server.ini
with your network login stuff saved. Copy this server.ini to other compute
rs (other
"..
\
PolicyManager2
\
Bin" dirs) before they start PolicyManager2.exe and they won't need
to know the login details.



13

Here is an example of a server.ini file:





Note it is not obvious that the Protocol is "Winsock TCP/IP Protoc
ol". It is usually easier
to log in using Open Database... in Policy Manager Two and let it update server.ini than
to edit server.ini manually.


14

How to Open Databases in Policy Manager Two


To check the version of Policy Manager you are using or to en
ter your serial number,
choose About... on the Help menu.


This window allows you to connect to other computers that are running a Policy Manager
Two database server. Typically information such as the database and server name are
given to you by whoever i
s setting up your network or hosting your data.




To log into a server:


1. Select the Network Protocol for your local network.


2. Enter the Server Name. Or, choose it from the list if you have been there before.


3. Click the Veri
fy Server button to test the server name and make sure we can connect.
This can take some time before it gives up.


4. If you get a 'Server verified' message under the Server Name, you should have some
items in the Database Name: list below.


5. Selec
t the database you want to open in the Database Name list and click OK.


If you don't see any Database Names listed or cannot connect to the server, ensure that
the server is running and has at least one Alias created for you (Configuring the server).




15

N
etwork Protocol


Select the option for your network (or ask your network administrator which one to use).


TCP/IP
-

Commonly used for local networks. Always used for Internet connections.


IPX/SPX
-

Used for Novel Netware networks.


NetBIOS
-

Used for som
e (usually smaller) Windows networks.




Server Name


Enter the name of the database server you wish to connect to. This information is often
given to you by a database, network, or systems administrator. The format of the server
name will depend on the
Network Protocol used for your network.


For TCP/IP protocol, ServerName must be of the form servername@iii.iii.iii.iii where
servername is exactly the name of the server and the iii.iii.iii.iii is the IP address of the
server. The server shows this infor
mation on its main screen.


For IPX/SPX protocol, ServerName must be of the form servername@xx
-
xx
-
xx
-
xx
-
xx
-
xx where servername is exactly the name of the server and the xx
-
xx
-
xx
-
xx
-
xx
-
xx is the
IPX address (the adapter address) of the server. The server sh
ows this information on its
main screen.


For NetBIOS protocol, ServerName must be the name the server is known by and it is
case
-
sensitive.



Verify Server


Check that the server name entered is valid and currently available. Also get the list of
databas
es on this server.



Server status


Shows the status of the currently selected server and the results of pressing the Verify
Server button.



16

Database Name


The name of the existing database you wish to open. Each server can have several
databases. Ask

your database administrator or the person in charge of your Policy
Manager Two data which one you should choose if there is more than one choice.


See the Policy Manager Two Network Installation Guide for more information about
servers and creating databa
ses.