| EzGet Advantages |
| Asset Management |
| Software Inventory |
| Hardware Inventory |
| Resource Management |
| Application Control |
| Screenshots |
| Diagram |
| Pre Requisite |
| Console |
| Agent |
| Interceptor |
| Database |
| Alert Management |
| Statistics |
| Document Managemet |
|
 |
EzGet technology uses an agent installed on each workstation to
automatically track all activities and events, whether the workstation is
connected to the network or not, whether the user is log in or not.
The collected information
builds an accurate profile of the use of your resources
(Diagram).
The principal tasks of this agent are to constantly collect hardware and
software data for the inventory, track the software usage and any
modifications made to the hardware.
|
Features
|
• |
Compatible with
all 32 bits Windows®
version (95, 98, ME, NT, 2000, XP, 2003, ...) |
|
• |
Do Inventories when the workstation is idle for user comfort |
|
• |
Works in total transparency for the user and cannot be detected |
|
• |
Automatically purges file logs |
|
• |
Report compression
(rate of 60%) |
|
• |
Detect any hardware and software changes |
|
• |
Easy Remote
installation and settings |
|
• |
Internet usage
monitoring for every user and workstation |
|
• |
Software and
license usage tracking |
|
• |
Hardware,
Software, Operating System, Service Pack and Patches Inventories |
|
• |
Detect Pocket
PC, Handset, Printers, USB drives, Fax, Modem, etc... |
|
• |
Do not use any
catalog or reference file |
|
• |
Prevents Illicit programs
execution, Interceptor
function included (see more) |
|
• |
 Lock all CD, DVD and burners drive on laptops, workstations or servers |
| |
|
|
|
|
|
Benefits
|
|
• |
Deploys
quickly with the Ezget Console |
|
• |
Small
compressed reports, doesn’t tax your network’s bandwidth. |
|
• |
Required
a small disk space, EzGet agent file size is
only 860 Kb |
|
• |
Data is sent to the EzGet database when the workstation is idle. |
|
• |
Do
not need .NET Framework |
|
• |
Do not need user logon or
connected network |
|
|
|
|
|
EzGet Agent Data Transmission |
|
| |
|
The
EzGet agent can use two different supports to transmit its report
file.
EzGet agent uses the FTP protocol to transfers inventories and report
files.
By default on a LAN network (can be changed with the agent setup) the
FTP port will be 8174.
The agent accepts two different settings to transmit data, a primary
setting can be done for a LAN connection on port 8174 and a secondary
one can be made for an Internet connection on port 21 with user and
password.
This
means that an installed agent on a laptop can send reports through the
LAN or Web server.
|
|
Scenario on R.A.S Connection |
|
|
|
|
When
a RAS connection is established by the user, EzGet agent detects the
EzGet server or service. EzGet agent will wait for computer and
network inactivity.
If the last sent report is older than 10 days or the computer is idle
for more than 3 minutes, then EzGet agent opens TCP port 8174,
connects to server on the TCP port 8174, sends the report file to the
server and closes the TCP port 8174.
(A daily report file is a 10kb file size)
The EzGet service will uncompress files and dispatch data into the
database.
|
|
Scenario sending file on slow Internet connection |
|
|
|
|
When
an Internet connection is established by the user, EzGet agent detects
the Web network.
If the last sent report is older than 10 days or the computer is idle
for more than 3 minutes, then EzGet agent opens TCP port 21,
establishes a secured (with user and password) FTP connection to Web
server on the TCP port 21, sends the report file to the server and
closes the TCP port 21.
The EzGet service will uncompress files and dispatch data into the
database.
|
|
Scenario sending file on VPN connection |
|
|
|
|
When
a VPN Internet connection is established by the user, EzGet agent
detects the LAN network.
If the last send report is older than 10 days or the computer is idle
for more than 3 minutes, then EzGet agent opens TCP port 8174,
connects to EzGet server on the TCP port 8174, sends the report file
to the server and closes the TCP port 8174.
The EzGet service will uncompress files and dispatch data into the
database.
|
|
Scenario
sending file on LAN connection |
|
|
|
 |
When a LAN connection is established, EzGet agent detects the LAN
network.
If the last sent report is older than 10 days or the computer is idle
for more than 3 minutes, then EzGet agent opens TCP port 8174,
connects to EzGet server on the TCP port 8174, sends the report file
to the server and closes the TCP port 8174.
Otherwise the agent will wait for a 50 minute idle delay before
sending the report file.
The EzGet service will uncompress files and dispatch data into the
database.
|
|
|
EzGet Agent Multi-Site organization |
|
| |
|
Remote
site without EzGet server or gateway |
|
|
In this case any remote workstations on
Domain A- will send reports
directly to the master Domain.
Advantage:
- No
server needed on Domain –A-
|
|
|
|
Remote
site with EzGet server database |
|
|
For the
Domain -B- an EzGet data replication will be done between
EzGet servers.
EzGet Data relay service must be
installed on Domain –B-, this relay service will synchronize data, by
pushing method from Domain –B- to the Master Domain Database.
Advantages:
-
Domain
–B-
administrators can use the EzGet Console.
-
Domain –B-
server can use a MSDE database.
-
Domain –B-
administrator can see only Domain –B- EzGet information.
All
information (Domain –B- and Master Domain) can be visible from the Master
Domain with EzGet Console.
|
|
|
|
Remote
site with EzGet Gateway |
|
|
In this case, all inventories and reports are stored in one server and the
transfer to the master domain server is done at scheduled time by the EzGet
Relay Service.
EzGet Relay Service must be installed on a server or workstation on Domain
–C-
Advantage:
|
|
 |
|
|
|
Network resources required |
|
|
TCPIP
Note: EzGet data transfers are done asynchronously, this mean that EzGet
doesn’t need Network or user login to works. Typically for laptop users,
EzGet works also when laptop users are not connected on the network, all
the usage and software tracking are still working and in this case EzGet
agent will wait for the next network connection to transfers its data.
|
|
|
less than 70KB of data transfer per week. To be sure to not disturbing the
corporate networks the EzGet
agent carries out differential inventories.
I.e. that only the positive or negative differences are transmitted on the
network. Moreover transmitted information is compressed at an average rate
of 60%. That’s why a complete inventory makes on average less than 70KB.
|
|
|
- OS:
Windows
95,98,ME,NT4,2000,2003,XP and later
(WMI must be installed on Windows 95, 98 and NT)
-
Processor: Pentium I (90mhz)
- Memory
: 64 Mb
- Disk
Space : 20 Mb
|
|
What devices
are discoverable and which aren’t
|
|
|
- Discoverable:
All Microsoft platforms and supported devices.
All Pocket PC and Mobiles computers
Printers and Printers distribution
Fax, Modem, Uninterruptible Power Supply
- Not
Discoverable:
Routers, switches
Unix and Linux Computers (will be available for the beginning of 2006)
|
|
What
hardware and software information is inventoried
|
|
|
A 50 pages
document with all inventoried hardware and software information is
available on WareMon web site.
http://www.waremon.com/Commun/Technical%20Sheet%20Inventory%20EzGet%20Agent.pdf
|
|
How long
will the initial audit take
|
|
|
The fist and
initial complete audit takes 1 to 5 minutes and it is done when the user
is not using the computer. After installing the agent, the agent program
will wait for a idle state of the workstation.
When the idle state of the workstation is detected, the agent will wait 30
minutes before performing the inventories. If any key or mouse activity is
detected during the inventories, the agent will stop and wait for another
idle period of 30 minutes to continue all inventories.
|
|
Deploying
the client for hardware/software inventory |
|
|
|
We have 4 methods for deploying EzGet agent.
Centralized Method:
With the console
you can easily deploy EzGet Agent on your network.
You can also, easily stop and start the agent or modify all agent
parameters.
With the console you decide which computer has to get the EzGet agent and
simply do the remote installation.
Manual method: Installation with the EzGet Setup installation
CD computer by computer.
Image method:
You can include EzGet agent into your software corporate images and deploy
EzGet on computer installation.
Login Script method: You have the possibility to deploy EzGet
agent with the login script or batch file.
When user logon and if the agent is not installed, the logon script will
install EzGet program without any user prompt or message.
|
|
Providing historical
information |
|
|
When a new hardware or software is detected a new entry
form is generated to give you the option to enter all the data relating to
this new resource such as name, copyright, price, attribution, dates,
rental, supplier, etc. EzGet
maintains a history of all the changes which can occur at a workstation
and alerts you instantly when something is removed, modified, added or at
the end of a rental period.
The
alert screen
permanently informs of any modifications made to the hardware and software
configurations. Alerts are classified by type (hardware, software, hiring)
and by level (information, average, critical). Alerts can be exported into
Microsoft®
Excel or sent by e-mail.
A clear and detailed
description of each modification informs the administrator to help him to
act according to the importance of the alert. An automated email can be
generated on request for each alert so that the implicated services can be
quickly informed.
|
|
|
|
|
|
|
| |
