IDLE-PC The power to manage

waisttherapeuticΛογισμικό & κατασκευή λογ/κού

4 Νοε 2013 (πριν από 3 χρόνια και 9 μήνες)

78 εμφανίσεις

Idle
-
PC documentation


1



1. What is
IDLE
-
PC
and what does it
d
o?


IDLE
-
PC

is a proprietary, licensed software tool that gathers information on the usage
of computer workstations in educational environments.


The information gathered by the IDLE
-
PC software is placed in files a
s
Comma
Sepa
rated Variables

(CSV files)
.
This structured data can be imported into a wide
variety of database produ
cts for storage and reporting
.


IDLE
-
PC clients are installed on computer workstations and an IDLE
-
PC server is
nominated to receive reports
on
workstation
usage several times per minute.



The

information provided by an IDLE
-
PC client to the
IDLE
-
PC server includes
:
-

a)

the IP address of the reporting workstation

b)

the status of the reporting workstation, either used or unused, Windows
MAC
or Linux

session.

c)

the identification of the current user and the start and end time of the login
session.

d)

T
he Active Directory domain, the workstation MAC number(s) and the
SystemName.

e)

the program name for the active Windows

or iMAC

application

f)

a list of all Windo
ws programs being run by the current user.


Diagram 1

illustrates the rep
orting of workstation usage by

IDLE
-
PC clients to the
IDLE
-
PC server.


Appendix 1

contains a detailed explanation of the fields in the CSV files.


The IDLE
-
PC s
oftware produces three
different
outputs as CSV files :
-


a)

real
-
time information about current usage

b)

daily audit files

of user

sessions

at workstations

c)

daily audit files

of Windows
programs run at workstations


IDLE
-
PC outputs
(by permission of the University of Ulster)

can be vi
ewed at :
-


real
-
time information about current usage


http://
idlepc.ulster.ac.uk
/realtime.txt




IDLE
-
PC


The power to manage






Idle
-
PC documentation


2

C:
\
c3idlepcdocumentation
\
diagram01.doc






Diagram 1 illustrates the reporting of workstation usage by IDLE
-
PC clients to the ID
LE
-
PC server.

IDLE
-
PC
Server

Usage Report at 16.53

User = Paul, Login Time =

16.40

Active Windows Application is MS Word

Also using Internet Explorer and Powerpoint

Usage Report at 16.53

User = Robert, Login Time = 12.35

Active Windows Application is MS Excel

Also using Visual Basic

Usage Report at 16.53

User = Lynne, Login Tim
e = 13.54

Active Windows Application is FileZilla

Also using Visual Basic and Visual Studio

Usage Report at 16.53

User = Gavin, Login Time = 9.05

Active Windows Application is MS Excel

Also using Firefox and Adobe Reader

IDLE
-
PC

client

IDLE
-
PC

client

I
DLE
-
PC

client

IDLE
-
PC

client

16.53,
Paul,16.40,MSWord,IE,Powerpoint

16.53,Robert,12.35,MSExcel,VB

16.53,Lynne,13.54,FileZilla,VB,Visual Studio

16.53,Gavin,9.05,MSExcel,Firefox,Adobe Reader

place information in CSV file


Idle
-
PC documentation


3

2.
What can
IDLE
-
PC
customers
do with information in the CSV files?


IDLE
-
PC
customers
can take
the information in the
output
CSV files

and import it

into a database of choice.
Once in a database, management information can be
extracted usin
g a scripting language.
Choice
of database and scripting language
would
be informed by existing products and expertise within an educational institution.


The CSV output files from the IDLE
-
PC software can
, for example,

be inserted into a
MySQL database wi
th management information extracted and displayed as HTML
pages using the popular PHP scripting language.


The authors of the IDLE
-
PC software tool
can
provide worked examples

of PHP or C
routines to upload the data to a database
.
Such example scripts are

free, the source
code is provided.


This use of an intermediate data format allows the data to be integrated into any
institutional database or management syste
m
.

Other database products and reporting lan
guages can be used by customers

of the
IDLE
-
PC soft
ware.


Here are some examples of extracting

IDLE
-
PC information from a MySQL database
using the PHP scripting language

(by permission of the University of Ulster)

:
-



a summary of available
computer
workstations

in an educational establishment


http://faccompeng.ulster.ac.uk/pchart/labuse.php


a ma
p of real
-
time usage of computer

wo
rkstations in an educational establi
shment


a

report on the usage of computer
workstations during a semester


from


http://idlepc.ulster.ac.uk
/idlepc.php
















Idle
-
PC documentation


4


3. What technical environments will IDLE
-
PC operate in?


Idle
-
PC clients communicate with the server over any TCP/IP network. The custom
protocol is lightweight and will be a minimal network load
ing


The IDLE
-
PC server gathers a variety of information from the client, any one of
which could be used to

identify

the computer workstations that report

to it.


Statically assigned IP addresses


Where IP numbers

are statically assigned
,
a list of IP addr
esses can be
supplied to the
IDLE
-
PC server by an administrator.
The list of statically assigned IP addresses is
used by the IDLE
-
PC server to populate an internal table. The IDLE
-
PC software will
always accept usage reports from the identified IP addresse
s and, optionally, the
IDLE
-
PC server can be set to ping client addresses that do not return usage reports.



The
file containing the
list of statically assigned IP addresses is identified in the
IDLE
-
PC server configuration file i.e.


IPTABLEFILE=c:
\
stati
cip.txt


Dynamically assigned IP addresses


Where IP addresses are dynamically assigned, the IDLE
-
PC server will populate its
internal table with all IDLE
-
PC clients that communicate with it.

Thereafter the
IDLE
-
PC software will always accept usage reports

from the identified IP addresses.


Network MAC address or system name


The client software always returns the system name and the MAC addresses of any
network adapters in the client system


4. What operating system is required for the IDLE
-
PC server?


The

IDLE
-
PC server is run on a Windows

operating system.

Server versions are available for Windows XP
(obsolete)

and Windows 7.

The
Windows

7 version has been

implemented on Server 2003 and Server 2008 64bit.


5. Which

operating systems

are IDLE
-
PC clients av
ailable for?


IDLE
-
PC clients are currently availa
ble for the following operating systems:
-


Linux ( test
ed on Redhat Fedora 6/7/8
/9
, SUSE 10
, OpenSuse
)



Windows XP/Vista
/7

with an Active Dir
ectory authentication


iMAC Leopard / Snow Leopard
/ Lion/Mount
ain Lion


Note that Lion/Mountain Lion uses a different client


Idle
-
PC documentation


5

6. Configuring and running an IDLE
-
PC server



The IDLE
-
PC softw
are is distributed via the following
URL
:
-


http://
idlepc.ulster.ac.uk/IDLEPC
-
distribution/


The IDLE
-
PC server
is called idlepc.exe.


Contact
J.Hanna@ulster.ac.uk

or
M.Crozier@ulster.ac.uk

to get a copy of the idlep
c
server software.


The IDLE
-
PC server is
invoked at

the DOS prompt on a Windows

operating system.



idlepc


debug

runs the server within a console window. This is useful for initial setup and testing.
However it requires a user session to be ope
n on the host PC.


Once the system is working then

i
dlepc



install

will install the software as a Windows Service, this starts automatically when the host
boots.


The IDLE
-
PC server require
s a confi
guration file. This


config
uration file, named
idlep
c
.gid
,

must be

in the same folder as the IDLE
-
PC serv
er. A licence file idlepc.lic
is also required

in the same folder
. Each licence file is specific
to a particular server
IP address.


Diagram 2

shows the IDLE
-
PC server being started and reading paramet
ers from the
idlepc
.gid file.


Copy the IDLE
-
PC server file and the configuration file to
the same directory and
then start the
IDLE
-
PC
server as
above.




A
ppendix 2

has a

detailed explanation o
f each parameter in idlepc
.gid
file.


Idle
-
PC documentation


6

C:
\
c3idlepcdocumentati
on
\
diagram02.doc






Diagram 2 illustrates the IDLE
-
PC server being run and readin
g parameters from a idlepc
.gid file

Hardware
platform
running
Window
s XP
operating
system


DOS prompt

c:
\
idlepc
\
i
dlepc.exe


IDLE
-
PC server running

idlepc
.gid

# a comment line

#the server IP

SERVERIP=193.61.148.209

#server port

SERVERPORT=110


take parameters from

Idle
-
PC documentation


7

7
. Restarting the IDLE
-
PC server




Note. Once installed as a Windows service the normal service administrat
ion
utilities can be used to restart

and manage
the Idle
-
PC server.
Idle
-
PC documentation


8


8
. I
DLE
-
PC Client Installations


The IDLE
-
PC software has a number of

different IDLE
-
PC clients. The choice of
client
used on a
computer workstation
depends on the operating system
and th
e t
ype
of authentication.

The

workstation configurations on which an IDLE
-
PC client will
run are :
-


a Windows Vis
ta/
Windows XP
/Windows 7

workstation with authentication to
Microsoft Active Directory


a
Windows Vista/
Windows XP
/Windows 7

works
tation with

authentication to
Novell
Netware

(No longer supported)


a

Linux workstation


an iMAC system (
Leopard /
Snow Leopard

/ Lion /Mountain Lion
)


Note that Lion/Mountain Lion uses a different client


The Active Directory

client

cons
ist
s

of two files called c
onserv
.exe and conserv2.exe

plus a third utility file
idlepcmon.exe



If a user is logged in to Active Directory or Novell Netw
are, the IDLE
-
PC client
conserv
.exe calls a secondary program called conserv2.exe that reports on the
Windows applications that
are currently being run on that workstation.


Diagram 4

illustrates the interaction within the IDLE
-
PC client reporting on the
user/workstation
as well as on active Windows applications.




Idle
-
PC documentation


9

C:
\
c3idlepcdocumentation
\
diagram04.doc






Diagram 4 illustrates the interaction within the IDLE
-
PC client reporting on the user/workstation as well as on active Windows applications.

IDLE
-
PC
Server

IDLE
-
PC client


c潮獥r瘮vxe


牵渠r猠
p奓呅䴠獥Y癩捥

牥灯牴楮g渠畳 爬rIP a摤牥獳⁡湤⁍sC⁡摤de獳⁴漠IDib
-
PC⁳ 牶rr


a湤⁦n牴桥爠re瑡楬猠晲潭⁣潮獥牶㈮rxe

c潮獥牶㈮rxe


牵渠a猠桩摤d渠啓䕒⁰牯 e獳

牥灯牴楮g渠 c瑩癥⁗楮i潷猠灲潧牡浳⁴漠IDib
-
PC⁣汩e湴⁵獩湧
楮ie爠灲潣e獳sc潭o畮楣u瑩潮
IPC)

IDLE
-
PC

Client

Idle
-
PC documentation


10

9. IDLE
-
PC client installation on
a
Windows Vista
\
7
\
Windows XP workstation
with authentication to Microsoft

Active Directory


On a Windows Vista
/7

workstation, begin by switching off the User Account Control
(UAC) feature.


Ensuring the UAC is off :
-


Go to

Control Panel


User Accounts


Select the User who is carrying out the installation.

Select Change Secu
rity Settings


If UAC is running
,
at this point you will be asked to confirm that you wish to continue
Click Continue


Make sure the

“Use User Account Control to help protect ..” box is unchecked


Click OK


If you have disabled UAC then the system must
be restarted for the change to take
effect.


Installing the Active Directory IDLE
-
PC client o
n both a Windows Vista
/7

workstation and a Windows XP workstation :
-


Copy the

IDLE
-
PC client
files to an approp
riate location on the hard disk of the
computer wor
kstation :
-


C:
\
Windows
\
Conserv
\
conserv.exe

C:
\
Windows
\
Conserv
\
conserv2.exe

C:
\
Windows
\
Conserv
\
idlepcmon.exe



Open a command prompt window.


Start


All programs


Accessories


Command prompt


Change to the installation folder where conserv.exe

and cons
erv2.exe
is located


Install the service
s


i
dlepcmon


-
install


conserv

install 193.61.130.221:110:1


The
conserve
program takes one parameter which has three parts.


193.61.130.221:110:1

Idle
-
PC documentation


11


First
,

there is the IP address of the IDLE
-
PC server


Second, t
he port number the server listens on


Third, the interval at which the
IDLE
-
PC client reports to
the
IDLE
-
PC
server (in 10
second increments)


The three parts are s
eparated by colon(:) characters. There are n
o spaces.


The program now installs itself as a
background service and inserts appropriate

details
in the system registry of the computer workstation.


On Windows Vista
/7

workstations re
-
enable UAC if required.


On both Windows Vista
/7

and Windows XP workstations,
r
eboot so that the
IDLE
-
PC c
lient will
start automatically
as a Windows service.


The IDLE
-
PC
client

will now report to the IDLE
-
PC
server at appropriate intervals.


Depending on th
e customer environment it may be

necessary to explicitly allocate
permissions to the conserv2.exe file.

The comman
d which has to be executed to give appropriate permissions

(assuming
the client is in c:
\
windows
\
conserv folder)

is



CACLS c:
\
windows
\
conserv
\
conserv2.exe /e /g "Domain Users":R





The r
eason

for this is that conserv.exe

run
s

as a system service to extra
ct user
information, however

conserv2.exe is

then

invoked as the current user to query
the
current user

s
foreground application

so all domain users mu
st have read access to the
file.



10
.
Removing the
IDLE
-
PC client installation on
a
Windows Vista
\
7
\
Wind
ows
XP workstation with authentication to Microsoft Active Directory



On a Windows Vista
/7

workstation, t
urn off
the
UAC as above.


Open a command prompt window.


Start


All programs


Accessories


Command prompt



Chang
e to the installation directory


idlepcmon
-
remove


conserv

remove


Idle
-
PC documentation


12

will remove the service entries from the register.


Reboot the workstation, the workstation will start without the IDLE
-
PC
client as a
service


The
idlepcmon.exe,
conserv.exe
and conserv2.exe
file
s

can now be deleted
.



13
. IDLE
-
PC client installation on
a Linux workstation


The
IDLE
-
PC client
file
is
linux_idlepc
and
is a Linux COFF executable.


It reports

user information to the IDLE
-
PC server at 10 second intervals so that the
usage statistics and real
-
time data are m
aintained no matter which OS has been booted
on a dual
-
boot system


Where there are multiple userids on a workstation they are displayed as user1+user2


To distinguish Linux workstations the local workstation userid, normally the local
Windows login, is sh
own as LINUX_USER and the context is shown as
LINUX_CONTEXT


Assuming that the executable resides in directory /var/idlepc then to start the daemon
when the Linux OS is booted put the line


/var/idlepc/
linux
_
idlep
c

193.61.130.221 110 &



replacing 193.61
.130.221 with the server IP address and 110 with the server port


in the file /etc/rc.d/rc.local




For OpenSUSE


The /etc/rc.d/rc.local file does not exist


The

Linux client

software can be started by putting the above command in the file



/etc/
init.d/boot.local



Idle
-
PC documentation


13

14
. IDLE
-
PC client installation on
an iMAC workstation


For Leopard/Snow Leopard


The software consists of a number of files (five off plus documentation)


MOST OF THESE MUST BE LOCATED IN THE FOLDER /idlepc (no capitals)


Copy the f
ollowing files to /idlepc (the idlepc folder must be at the top level in the
Macintosh HD folder)


idlemac (the application file)

idlemac.gid (the application parameters)

imfindname (other application parts)

imscript


and


idlemac.plist



Edit the idlem
ac.gid file if required. The first line is the IP address

of the IDLE
-
PC server, the second line is the port the IDLE
-
PC server

listens on.


Copy the idlemac.plist file to /Library/LaunchDaemons


using the following in a terminal window (you will find th
e terminal application in
Applications
-

Utilities)


sudo cp /idlepc/idlemac.plist /Library/LaunchDaemons/idlemac.plist

(you will be prompted for a password)


Restarting the system will then start the idlepc daemon.


For L
ion/Mountain Lion
(a different cli
ent from Leopard/Snow Leopard)












The software consists of a number of files (
three

off plus documentation)


MOST OF THESE MUST BE LOCATED IN THE FOLDER /idlepc (no capitals)


Copy the following files to /idlepc (the idlepc folder must be at the t
op level in the
Macintosh HD folder)


idlemac (the application file)

idlemac.gid (the application parameters)



and


idlemac.plist

Idle
-
PC documentation


14



Edit the idlemac.gid file if required. The first line is the IP address

of the IDLE
-
PC server, the second line is the p
ort the IDLE
-
PC server

listens on.


Copy the idlemac.plist file to /Library/LaunchDaemons


using the following in a terminal window (you will find the terminal application in
Applications
-

Utilities)


sudo cp /idlepc/idlemac.plist /Library/LaunchDaemons/i
dlemac.plist

(you will be prompted for a password)


Restarting the system will then start the idlepc daemon.




Note. If an iMAC is used dual
-
boot to run both Windows and OSX, then a standard
Windows client should also be installed on the Windows image.












Idle
-
PC documentation


15

Appendix 1.


Explanation of the fields in the IDLE
-
PC output CSV files


The real
-
time file


The IDLE
-
PC server writes the real
-
time output file to a folder specified in the
REALTIMEFILE parameter in
idlepc
.gid


26/05/2007 00:52:35 ;1180137155
;Real Time data from IDLE
-
PC
-

DO NOT EDIT this file manually

193.61.148.209,2,00
-
E0
-
00
-
AE
-
CE
-
EE ,czhk23,E7010,E7010
,26/05/2007 00:52:27,26/05/2007
00:50:02,1180137147,1180137002
,cmd.exe,C3:AD

193.61.148.210
,2,00
-
E0
-
00
-
AE
-
CE
-
EE ,czhk23,E7010,E7010,26/05/20
07 00:52:27,26/05/2007
00:50:02,1180137147,1180137002
,autocad.exe,C3N

193.61.148.209,2,00
-
E0
-
00
-
AE
-
CE
-
EE ,czhk23,E7010,E7010,26/05/2007 00:52:27,26/05/2007 00:50:02,1180137147,1180137002
,,


First line in the real
-
time file


The first line is a date/time en
try showing when the file was produced.

When the IDLE
-
PC server restarts it checks for the presence of a real
-
time file at the location specified in its parameter file. If the date/time is
less than 60 second (default time), the data is treated as current

and is reloaded into the IDLE
-
PC server internal table. In this way reports from
IDLE
-
PC clients are preserved over an IDLE
-
PC server restart.

Subsequent lines in the real
-
time file


Date/
time fields


Date/time fields in the files are presented in two

formats to facilitate customer processing. The first format is a human readable form

with day/month/year time
26/05/2007 00:52:35
, the second format is a C time_t numeric e.g.
1180137155

the number of seconds from 1 Jan
1970.

Idle
-
PC documentation


16

IDLE
-
PC c
lient
report
lines


193.61.148.209,2,00
-
E0
-
00
-
AE
-
CE
-
EE ,czhk23,E7010,E7010,26/05/2007 00:52:27,26/05/2007
00:50:02,1180137147,1180137002
,cmd.exe,C3:AD


Explanation of IDLE
-
PC client report lines


IP

address

,
Workstation status, MAC address(es) , userid
, context/domain,

systemname ,whenpolled

time,

start

time
,

whenpolled(time
_
t)
,

starttime(time
_
t)
, current active process, IDLE
-
PC client version number


Explanation of workstation status values


status value


meaning

1

The IDLE
-
PC client is reporting as a Windows
/iMAC

wo
rkstation but with no userid logged in. System values such as
IP address, MAC address(es) and Systemname are reported.

2

The IDLE
-
PC c
lien
t is reporting as a Windows/iMA
C
workstation with a logged in userid. User values such as
userid, context/domain are
reported along with System values such as IP address, MAC address(es) and
Systemname.

The active program is reported.

5

The IDLE
-
PC client is reporting as a LINUX workstation but with no userid logged in. MAC address(es) are
reported.


6

The IDLE
-
PC clie
nt is reporting as a LINUX workstation with a logged in userid that may have multiple
entries. MAC address(es) are reported.

8

NO IDLEPC client is reporting but when polled by the IDLE
-
PC server, the workstation does respond to ping.

Using the
idlepc
.gid
file, the IDLE
-
PC server can be set to poll workstations using the IPTABLEFILE
parameter and the PINGIFNOTRESPONDING parameter.

9

The IDLE
-
PC client is not reporting. Neither is the workstation responding to a ping from the IDLE
-
PC server
within the perio
d in seconds specified by the CONSIDERDEA
DAFTER parameter in idlepc
.gid


Idle
-
PC documentation


17


Older pre version C3 clients do not return process information, the IDLE
-
PC server is backwards compatible. Clients which do not return
information appear as at line three above.



Daily
login
audit files


Daily audit files of user sessions at workstations are created by the IDLE
-
PC server. These daily audit files have the naming convention of
YYYYMMMDD.log to facilitate sorting by date. The IDLE
-
PC server writes the daily audit fi
les in a folder specified by the AUDIT
FOLDER
parameter in idlepc
.gid


2007MAY12.log

is an example of a daily audit file for the 12
th

May 2007.


lines in the daily audit file


193.61.148.209
,00
-
E0
-
00
-
AE
-
CE
-
EE ,czhk23,E7010,E7010,26/05/2007 00:52:27,26/05/20
07 00:50:02,1180137147,1180137002


Expla
nation of lines in daily audit file


IP address ,

MAC

address
(
es) , userid
, contex
t/domain, systemname , end time,

start

time
,

end time
(time
_
t)
,

start

time(time
_
t)


A user session is recorded in the daily audit
file corresponding to the date of logout. For example, the audit record for a user logging in at 11.50
p.m. on Monday 28 May 2007 and logging out at 12.30 a.m. on Tuesday 29 May 2007 will appear in the 2007MAY29.log audit file.

Only one
audit record is ge
nerated for each session.






Idle
-
PC documentation


18


Daily audit files

of process lists


Daily audit files of process lists are created by the IDLE
-
PC server. These daily audit files have the naming convention of YYYYMMMDD.plg
to facilitate sorting by date. The IDLE
-
PC server

writes the daily audit files of process lists in a folder specified by the
PROCESSLISTFOLDER

parameter in idlepc
.gid


2007MAY12.
plg

is an example of a daily audit file for the 12
th

May 2007.


lines in the daily audit files of process lists


12345678
,
193.
61.148.209
,
00
-
E0
-
00
-
AE
-
CE
-
EE

,
czhk23
,E7010,
ultraedit.exe
,iexplorer.exe, winword.exe,


Expla
nation of lines in the daily audit files of process lists


Time

audit record created in time_t format
,
IP

address,

MAC

address
(
e
s)

,
user
id
,

systemname
,
current

active process
, a list of running
processes owned by user


MAC address(es), userid and SystemName are optional. Reporting is determined b
y parameters in the idlepc
.gid file i.e.


PLIncludeUser=Yes

PLIncludeMAC=Yes

PLIncludeSysName=Yes



The first entry

i
n the process list is the current active process. This may not be owned by the current logged in user.

The active process is the

program name for the
activ
e Window

screen at time of the report from the IDLE
-
PC client.

Idle
-
PC documentation


19

For example, if

the user has an Inter
net Explorer window
as the active Window

at the time the IDLE
-
PC client reports, then the value
iexplorer.exe

is returned.


Lines in the daily audit files of process lists can be long. The following is one line extracted from a daily audit file. Th
e activ
e Windows
application in this case is MSDEV.EXE (Visual Studio)


1183992308, 193.61.130.207,00
-
14
-
22
-
3F
-
21
-
8F ,czhk23,TP2
-
JUL06,MSDEV.EXE,explorer.exe,smax4pnp.exe,StatusClient.exe,mpm.exe,nwtray.exe,shstat.exe,UpdaterUI.exe,TBMon.exe,fpdisp4.exe,
fppdi
s1.e
xe,FileZilla Server
Interface.exe,eraser.exe,MFIndexer.exe,ApacheMonitor.exe,wuauclt.exe,mmc.exe,taskmgr.exe,capture.exe,restart2.exe,realsched.e
xe,IEXPLOR
E.EXE,cmd.exe,MSDEV.EXE,UEDIT32.EXE,idlepc.exe

















Idle
-
PC documentation


20

Appendix 2


Detailed explanation of

t
he entries in the idlepc
.gid file


# a comment line

#the
IDLE
-
PC
server IP

address

SERVERIP
=193.61.148.209

The IP
address of the

IDLE
-
PC server is

specified

here. On a hardware platform

with multiple network interface cards this ties the IDLE
-
PC server to

one network
interface card.


#server port

SERVERPORT
=110

The port number on which

the

IDLE
-
PC server listens.



#a restart password

RESTARTPASSWORD
=1234567

A Windows application called restart2.exe is supplied for restarting the IDLE
-
PC
server either on t
he server hardware platform or from a remote workstation. The
restart program prompts for the following parameters
-

the
IP

address of the IDLE
-
PC server, port and remote password.



#

WRITELOG
=Yes

LOGFILE
=c:
\
restartlog.txt

on restart the
IDLE
-
PC
server
can be

asked to copy its internal table to a logfile. As
well as the contents of the internal table,
normal error messages will scro
ll on the
console screen and be copied

to this logfile



#audit files folder

AUDITFOLDER
=c:
\
audit

The folder where the dai
ly audit files will be written by the IDLE
-
PC server.


#real
-
time file name

REALTIMEFILE
=c:
\
realtime.csv

The folder where the real
-
time file will be written by the IDLE
-
PC server.


When the IDLE
-
PC server restarts it checks for the presence of a re
al
-
time

file at the
location specified in the

parameter file

called idlepc
.gid I
f the date/time is less than
PRESERVEINFOFOR

seconds old
,

it considers the data as still current and
reloads it back into the
IDLE
-
PC server. Reported

information can thus be
pre
served over an IDLE
-
PC software restart or
, with a longer time gap,

a hardware
restart


#
PRESERVEINFOFOR
=

default = 60 seconds if not specified


EXECAFTERREALTIME
=Yes

Idle
-
PC documentation


21


DATAREADYFILE
=c:
\
idlepc
\
upload.exe

The
IDLE
-
PC
server can run an ex
ternal program a
t the same time as it updates
the

real
-
time file.
Such external p
rog
rams are run in the background and
the IDLE
-
PC
server does not check for or report the outcome
. The external programs
are not
logged.

The command string may include parameters, max
imum

t
otal length

is 255
characters.

For

a long filename that contains a space, use quoted strings to indicate where the
filename ends and the arguments begin
.

e
.
g
.


"c:
\
program files
\
database upload
\
mysqlclient.exe" c:
\
realtime.csv

The external program will be
hidden if a Windows application.

The external progr
am will run as a new console if of

Console/DOS type

The IDLE
-
PC server does not process messages from the external application th
at is
generated by the IDLE
-
PC customer.
.

For reliability and resilience,
the IDLE
-
PC server invokes the external application as
a separate entity.


BLOGRUNDELAY
=20

The time between updates of the real
-
time file in increments of 500

m
illiseconds

i
.
e
.

20 = 10 seconds


#ping parameters

PINGIFNOTRESPONDING
=YES

Statically assigned I
P addresses

loaded from the IPTABLEFILE= parameter can be

pinged if IDLE
-
PC clients are not reporting to the IDLE
-
PC server.


I
PTABLEFILE
= c:
\
staticip.txt

a list of statically assigned IP addresses in the form

193.61.130.211

193.62.34.45

no wildcards allow
ed

entries in this file will always appear in the output real
-
ti
me

file


#

CONSIDERDEADAFTER
=180

the t
ime
(in seconds)
after which a non
-
reporting

IDLE
-
PC
client will be considered
to be switched off for audit purposes

#


#show a line for each reporting cl
ient

on the console

SHOWCONNECTIONS
=Yes

the
IDLE
-
PC
server can print a short diagnostic line for each
IDLE
-
PC
client
connection on its console screen

(if running in debug mode
, when running as a
service the only record of connections is the realtime file)





Idle
-
PC documentation


22

SHOWCONNECTIONSFULL
=No

The

IDLE
-
PC

server will show all the returned information from the

IDLE
-
PC

client


#ignore any usernames which have these

IGNOREPART
=abc123

IGNOREEXACT
=JHanna


Novell Netware using Zenworks

The IDLE
-
PC client on a Windows Vista/
W
indows
XP workstation with Novell
authentication reports a context/domain of “[Public]”
when
ever there is no user
logged in.


If

Zenworks is used

on a Windows Vista/
Windows
XP workstation with Novell
authentication

and the user is not logged in, the IDLE
-
PC client

reports a
context/domain of the form :
-


Station identifier.Zenworks container information


An example of this might be

WOL
-
9620.WORKSTATIONS.ZEN


The Station identifie
r (WOL
-
9620) is unique for a
workstation


Zenworks is an NDS container specif
ied at installation time for the Novell Netware
server.


To allow the IDLE
-
PC serve
r to identify

workstations

that are not logged in,

a list of
any Zen containers is required.


Multiple
IGNOREPART
=
or IGNOREEXACT
= lines may be specified in
the
parameter
file . IDLE
-
PC client reports

to the
IDLE
-
PC
server which include
any
IGNOREPART
= string as

part of the returned userid

are treated as being vacant
.
IDLE
-
PC client reports

to the
IDLE
-
PC
server which include
any IGNOREEXACT
=
string as an exact match f
or the returned user name are treated as being vacant
.


# Logging program usage variables

IDLE
-
PC clients* return two types

of program utiliz
ation data to the IDLE
-
PC server


T
ype 1. Every IDLE
-
PC client reports

the program name which owns the


act
ive

Windows screen at the time of the report. For example,
if the user has an
Internet Explorer window with the focus
1
at report
-
time then the

IDLE
-
PC

client
returns iexplorer.exe




Type 2. At each IDLE
-
PC client report

specified by the


PROCESSLISTINTER
VAL

parameter
, the

IDLE
-
PC client also reports

a longer
list of all the running program names which are owned by the user.


This list is placed in daily audit

files

of process lists

in the folder specified


by the
PROCESSLISTFOLDER

parameter






Idle
-
PC documentation


23

#For th
e daily
audit files of process lists

# Below =6 returns process list every minute if

IDLE
-
PC
clients are set to

# report

at 10 second intervals, =0 means no process list information

#is reported

PROCESSLISTINTERVAL
=6


PROCESSLISTFOLDER
=c:
\
processlists

The

folder where the daily audit file of process lists will be written by the IDLE
-
PC
server.


Dailyprocess list files have the naming convention

yearmonday.plg eg 2007JAN12.plg

and are placed in the above folder. If the folder does not exist then no

process
logs will be written


PLIncludeUse
r=Yes


PLIncludeMAC
=Yes


PLIncludeSysName
=Yes