Professional Documents
Culture Documents
24/05/2013
EasyVista 2013
Summary
A. Description ........................................................................................ 6
A.1. Objectives .......................................................................................................... 6
A.2. Prerequisites ..................................................................................................... 6
B. EasyVista Architecture..................................................................... 6
B.1. Three Tier Architecture..................................................................................... 6
B.1.1. Objectives ..................................................................................................................................... 6
B.1.2. A gradual way of scaling ............................................................................................................... 6
B.1.3. Licensed users vs Concurrent users ............................................................................................. 6
B.1.4. Scale-up vs Scale-out of the servers ............................................................................................ 7
24/05/2013
EasyVista 2013
24/05/2013
EasyVista 2013
24/05/2013
EasyVista 2013
24/05/2013
EasyVista 2013
A. Description
A.1. Objectives
The goal of this document is to help you to understand how the EasyVista platform will be integrated
into your environment.
A.2. Prerequisites
This document is for information purposes only.
Each project will have its own unique specifications that will need to be analysed during the pre-sales
process and pre-installation preparation.
B. EasyVista Architecture
B.1. Three Tier Architecture
B.1.1. Objectives
EasyVista is based on a three tier architecture, meaning that the interface layer (WEB), the application
layer and the database layer can be installed on different machines and sized depending on the
project.
According to the number of concurrent users and the security policy of your company, you must define
how the EasyVista platform will be structured.
Thats why you can choose to use a simplified architecture if you calculate that the average number of
simultaneous transactions is less than the number of licensed users.
24/05/2013
EasyVista 2013
We do not apply these rules to the database layer, because it can only support scale-up according to
the current feature of SQL Server.
24/05/2013
EasyVista 2013
EASYVISTA SERVER
APACHE + PHP
EASYVISTA Application
ACTIVE
DIRECTORY
SQL SERVER
Corporate
mail server
24/05/2013
EasyVista 2013
24/05/2013
EasyVista 2013
Value
OS
Apache
Directory Easyvista
<Directory "Repertoire_pages_Easyvista">
Options Indexes FollowSymLinks
AllowOverride All
Order allow,deny
Allow from all
</Directory>
10
24/05/2013
EasyVista 2013
Security
ServerSignature Off
Do not allow that folders could be browsed
EnableSendFile On
Performance
LogLevel warn
HostnameLookups Off
LogFormat %a %l %u %t \%r\ %>s %b common
DirectoryIndex index.php
Server-Status + ExtendedStatus
-> Desactivate if
not necessary
Activate Keep-Alive with a short timeout like 4s
Scalability
MaxClients
-> Depends of your configuration
MaxRequestPerChild -> 0 for Windows, 100 000 for
Linux
MinSpareServers, MaxSpareServers -> Depends of
your configuration
ThreadPerChild = 50 -> For Windows only
11
24/05/2013
EasyVista 2013
Curl
iconv
Json
so
sockets
Xcache
libXML
zlib
If you compile PHP yourself you must include the socket, GD,
XML and Apache modules and the following directives :
'./configure' '--prefix=/usr/local/apache2.4.2/php-5.4.11' '-with-curl' '--with-iconv' '--enable-sockets' '--withapxs2=/usr/local/apache2.4.2/bin/apxs' '--enable-json' -enable-module=so -sysconfdir=/usr/local/apache2.4.2/php-5.4.11 '--disablembstring' '--disable-pdo' '--disable-pdo_sqlite' '--disablephar' '--without-sqlite3' '--disable-tokenizer' '--withoutpcre' '--with-openssl' '--with-zlib'
Configure PHP.INI:
12
24/05/2013
EasyVista 2013
zend.ze1_compatibility_mode = On
zend.enable_gc = On
short_open_tag = Off
y2k_compliance = On
allow_call_time_pass_reference = Off
memory_limit = 192M
display_errors =off
log_errors = On
log_errors_max_len = 1024
track_errors = on
error_reporting = E_ALL & ~E_NOTICE
error_log = ( paramtrer)
register_globals = Off
register_long_arrays = Off
precision = 14
auto_globals_jit = On
post_max_size = 96M
session.save_handler = files
session.save_path = "/repertoire_temporaire_session_php/"
session.auto_start = Off/0
13
24/05/2013
EasyVista 2013
session.cookie_lifetime = Off/0
session.gc_maxlifetime = 18000
session.gc_divisor = 1000
session.gc_probability = 1
session.cache_expire = 180
session.bug_compat_warn = 1
session.use_trans_sid = 0
session.use_cookies = 0
session.hash_function = 0
session.hash_bits_per_character = 5
session.name = PHPSESSID
session.serialize_handler = php
session.bug_compat_42 = On
session.cache_limiter = nocache
Expose_php = off
variables_order=GPCS
request_order = "GP"
default_socket_timeout = 60
magic_quotes_gpc = Off
safe_mode = Off
max_execution_time = 300
max_input_time = 300
file_uploads = On
upload_max_filesize = 30M
max_file_uploads = 20
default_charset = "UTF-8"
14
24/05/2013
EasyVista 2013
Others
http://www.php.net/downloads.php
REDHAT/ CENTOS : http://iuscommunity.org/packages/
DEBIAN : http://www.dotdeb.org/
Value
OS
PROCESSOR
DATABASE client
ANTIVIRUS
15
24/05/2013
EasyVista 2013
Value
OS
SQL Server
SQL Server 2008 SP1 and next SPs, SQL Server 2008 R2 (we
highly recommend that you use SQL SERVER 2008 R2), SQL
SERVER 2012
SQL SERVER 2005 is no longer supported due to UNICODE
features of EasyVista 2012
SQL Server tools available (Database manager, configuration
tools, BCP, Alias configuration, )
Sort order: CASE INSENSITIVE ACCENT SENSITIVE / SQL Latin
1 general
Value
Version
16
24/05/2013
EasyVista 2013
Configuration
JavaScript allowed
Automatically refresh the pages
Local cache for temporary files must be large enough (>10MB)
If you use SSL, check that the cache for secure pages is allowed.
For Internet Explorer >= 7 :
Security option / Downloads must allow AUTOMATIC
PROMPTING FOR FILE DOWNLOADS.
Pop-ups must be allowed
For Firefox, Pop-ups must be allowed for the EasyVista web site.
Antivirus
On the customer PC, the local antivirus should not systematically check
each .JS (JavaScript) file to avoid performance problem during the
display of the page.
Others
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
MaxUserPort -> 60000
17
24/05/2013
EasyVista 2013
TcpTimedWaitDelay -> 30
Group
Information
SQL Server
Administrative
database
80 MB
Config database
100 MB
Data Database
600 MB
Assets.......................................... 38400
Employees ................................... 8750
Orders ......................................... 500
Requests ..................................... 24200
LAN
Mono server XEON double core, 4GB RAM, Windows 2008 32 or 64-bit, 2HD RAID 1
(70GB) and 3 HD RAID 5 (70GB)
Or
Mono server 2x XEON Processor, 8GB RAM, Windows 2003/2008 64-bit, 2HD RAID 1
(70GB) and 3 HD RAID 5 (146GB)
Or
18
24/05/2013
EasyVista 2013
Virtualized platform administrators prefer to size the resources based on the real usage while
the project is growing, instead of reserving too much resources at the beginning. Thats how
they can guarantee an optimal usage of the physical resources of the virtual server among all
the virtual machines
Using more than 4 vCPUs on a virtual machine should be considered with precaution because
that such configuration can create contention on physical CPUS (vmware CPU Ready
indicator).
19
24/05/2013
Connected
users
20
EasyVista 2013
Physical architecture
Virtual architecture
WEB server:
WEB server:
2 to 4 vCPUS, 4GB to 6 GB RAM, HD 40GB,
XEON QUAD CORE 4GB RAM 2 HD RAID Linux.
1 (70GB) , Linux.
(more virtual servers can be added if
necessary)
Application server:
XEON QUAD CORE 4GB RAM 2 HD RAID Application server:
1 (70 GB), Windows 2008 32 or 64 bits.
2 to 4 vCPUS, 4GB RAM, HD 40GB, Windows
20
24/05/2013
EasyVista 2013
2008 32 or 64 bits.
(more virtual servers can be added if
necessary)
Database server:
WEB server:
BI XEON QUAD CORE 8GB RAM, 2 HD
RAID 1 (70GB), Linux.
Depending of what the final users are doing
and of the forecast charge, it could be
necessary to double the web server when
you have more than 100 users.
Application server:
BI XEON QUAD CORE 8GB RAM 2 HD
RAID 1, Windows 2008 32 or 64 bits.
Depending of what the final users are doing
and of the forecast charge, it could be
necessary to double the Application server
when you have more than 100 users.
Database server:
SQL Server instance must have 8GB of
RAM allocated and six to height cores. The
instance must be dedicated to EasyVista.
Bigger
architecture
s
The architecture will be defined with your teams and our experts.
21
24/05/2013
EasyVista 2013
Discovery data integration (Discovery, Usage, SNMP, Citrix) can be very resource intensive. A
single PC needs 10 seconds to be integrated in the EasyVista database because of all the rules
applied during the integration process (merges, movement history, etc). Huge imports can potentially
slow down the performance for end users.
In this case, it is necessary to either import data outside of working hours (e.g. night shift), or use a
dedicated back office server to import data: MONO XEON DUAL CORE, 4GB RAM, 2 HD 70GB RAID
1, Windows 2003).
22
24/05/2013
EasyVista 2013
You can either use HYPER-V or VMware ESX / VSPHERE (or following).
Warning: EasyVista performance on virtualized platform is tightly linked to the performance of the
physical infrastructure hosting the virtualization OS.
C.7.1. Would you like to test response times and workload increase with
these platforms?
If the answer is YES, then these platforms must be identical to the production platform. Keep in mind
that this will cost the same price as the production platform, for a platform that will not be used very
often.
If the answer is NO, then these platforms will only be used to test new versions, develop specific
interfaces, etc. You can use smaller architectures, and even virtual server environments.
C.7.2. Would you like to validate on these platforms the whole integration
context and needs (LDAP, SSO)?
If the answer is YES, then these platforms should be the same as the production database in terms of
OS, and location in the network.
If the answer is NO, then these platforms will only be used to test new versions, develop specific
interfaces, etc. You can use smaller architectures, and even virtual server environments.
23
24/05/2013
EasyVista 2013
ADMINISTRATIVE Part
Account
Database
EVO_BACKOFFICE
EZV_ADMIN
EVO_REFERENCE
EVO_ADMIN
DATA Part
DATA
24
24/05/2013
EasyVista 2013
25
24/05/2013
EasyVista 2013
26
24/05/2013
EasyVista 2013
LDAP
Directory
Subtree
allowed for
EASYVISTA
account
3
User
+
Properties
29
13
27
24/05/2013
EasyVista 2013
Domains
Domain = Limit the data the user can see
Domain ALL THE COMPANY
Domain 1
Domain 3
Domain 2
Asset type
criteria
(AM)
Localisation
criteria
(Discovery+AM)
Department
criteria
(AM)
28
24/05/2013
EasyVista 2013
F.2. Profiles
Profiles limit the actions that a specific user can do (Add, Update, Delete), the administration level they
have to manage filters and reports, the screens they access, etc.
Profiles
Profile = Limit what the user can do
Menu
Theme
(Discovery,
Administration,
)
Screens accessible
Module
Menu
(Help-Desk,
Discovery,)
Theme
Filters
Rights
Reports
29
24/05/2013
EasyVista 2013
F.3. Users
A user is defined by:
Users
User = Account allowed to access Easyvista
Domain 1
Limit the data it can see
Domain N
Profile
30
24/05/2013
EasyVista 2013
Site 3 Manager,
all departments
Dept 2.1
Dept 3
Site 1
Dept 2.1
Region manager,
All sites and all department
Dept 2.1
Site 2
Dept 1
31
24/05/2013
EasyVista 2013
Department 3 manager
Dept 2.1
Dept 3
Department 2 manager
Site 1
Dept 2.2
Dept 2.2
Site 2
Dept 1
Department 1 manager
32
24/05/2013
EasyVista 2013
Dept 3
Site 3
Dept 2.1
Dept 3
Site 1
Dept 2.2
Dept 2.2
Site 2
Dept 1
10
33
24/05/2013
EasyVista 2013
All
the sites
R1
Dept 3
Site 3
Site 1
S1
S2
Dept 2.2
All
the departments
Dept 2
Dept 2.2
Site 2
Dept 1
2.1
2.2
Dept 3
Dept 1
11
With Discovery Manager, an automatic inventory tool that will discover assets connected to
the local network and inventory the ones that can be reached
With the company login script
With a local agent installed on the asset
Each method has its own advantages. You should use each one depending of the result you are
expecting.
Analyze
34
24/05/2013
Discovery Manager
EasyVista 2013
Pros:
User friendly interface to configure the collection point and run an
automatic discovery
Quick discovery of the connected and reachable assets
Cons:
Only the up and running assets at the very moment of the discovery
process can be found
Well designed for:
First discovery process to collect data
Scheduled inventory for SNMP assets
Login Script
Pros:
Each machine connected to the network will be inventoried each time a
user connects
The inventory will be completed one PC after the other, each that a user
connects
Cons:
The login script must be changed (1 or two lines to add)
Users must connect to have the PC inventoried
Well designed for:
Regular inventory of the assets
Local installation
Pros:
Useful for PC that never use the login script
Cons:
A local agent must be installed, either manually or automatically with a
deployment tool if you have one
Well designed for:
Inventory of servers, notebooks, etc
35
24/05/2013
EasyVista 2013
36
24/05/2013
EasyVista 2013
37
24/05/2013
EasyVista 2013
Inventory overview
Enterprise
equipment
Login Script
Service
Serveur
Windows
Others inventories :
SNMP,
USAGE,
CITRIX
Collection
Point
Service
Send DATA
Nomad
equipment
Remote
50
If you just have one local network, you should consider having just one collection point
If you have a more complex network with several sites, you should define one collection point
for each site.
Even if they are physically connected, and if users can access a shared folder on the
corporate LAN, our advice is to create one collection point per site instead of a single central
one, in order to avoid heavy traffic on the WAN network and to automatically define the
location of collected PCs.
For each collection point created, you can define an automatic default location (and/or department)
which will be automatically attached to each newly discovered PC. Consequently, the PCs will be
available to view for all users belonging to this domain based on these geographical criteria.
38
24/05/2013
EasyVista 2013
NECE
SSAR
Y
Collection Point 1
SI Department 1
SI Department 2
POP3
How are remote collections points
installed?
FTP
Collection Point 4
FOLDER
51
SMTP / SMTPS: data are sent to an e-mail account dedicated to EasyVista (e.g.
easyvista@yourcompany.com). The main platform will access this mailbox to get the collected
files. Once imported, e-mails are automatically deleted from the mailbox: you dont need to
delete them manually.
FTP / FTPS / SFTP : data are sent using an ftp web site accessible to the collect points. Once
imported you dont need to delete them manually, files are automatically deleted from the FTP
site.
SHARED FOLDER: If you have just one collection point on a single site architecture, you can
use a shared folder to send data because most of the time, the server hosting the collect point
and EasyVista server will be the same: in this case, thats the simplest way to send data.
HTTP / HTTPS
Depending on your network architecture and security rules, you can choose to use SMTP or FTP, or
both.
39
24/05/2013
EasyVista 2013
See Annex 1 for more details on the information collected by the agent.
40
24/05/2013
EasyVista 2013
SNMP INVENTORY
Collect
Point
Easyvista SNMP
Send
LA N
LA N
INTERNET
INTERNET
Printers
Servers / Workstations
Others
The SNMP inventory module automatically collects information from the assets using the SNMP
protocol.
You can define as many IP subnets and communities as needed.
You can extend the EasyVista Management Information Base (MIB) extract rules with specific rules for
your SNMP assets.
Discovery Manager can be used to:
41
24/05/2013
EasyVista 2013
Prerequisites:
42
24/05/2013
EasyVista 2013
Field
DATE
COMPUTER_NAME
PC_EUID
PATH
EXE_NAME
VERSION
PUBLISHER
LANGUAGE
NB_RUN
FOUND_IN_MEMORY
AGENT_VERSION
Description
Date of the capture
Computer name of the PC captured
EasyVista unique identifier of the PC (EUID)
Path of the exe in memory
Executable file name in memory
Version of the exe in memory
Publisher of the exe in memory
Language of the exe in memory
Number of time the software has been launched during the period
Duration of the software in memory (in seconds)
Version of the usage agent that captured the data
Field
DATE
COMPUTER_NAME
PC_EUID
TYPE_MEMORY
TYPE_HARDWARE
VALUE_1
VALUE_2
NB_START
RUNNING_TIME
AGENT_VERSION
Description
Date of the capture
Computer name of the PC captured
EasyVista unique identifier of the PC (EUID)
MEMORY_Usage for the total memory used lines
VIRTUAL_MEMORY_Usage for the total of the virtual memory used lines
HARDWARE_Usage for the hardware usage lines
If the TYPE_MEMORY column is MEMORY_Usage or VIRTUAL_MEMORY_Usage,
this column represents the minimum of memory used by the PC during the capture.
If the TYPE_MEMORY column is MEMORY_Usage or VIRTUAL_MEMORY_Usage,
this column represents the maximum of memory used by the PC during the capture.
If the TYPE_MEMORY column is MEMORY_Usage or VIRTUAL_MEMORY_Usage,
this column represents the average of memory used by the PC during the capture.
For the HARDWARE_Usage lines only, represents the number of time the PC has been
started during the day of the capture
For the HARDWARE_Usage lines only, represents the time the PC has been used
during the day of the capture (in seconds)
Version of the usage agent that captured the data
Software name
Software editor
Short version or marketing version if it exists (e.g. Excel 2007)
43
24/05/2013
EasyVista 2013
Long version
Installation folder
By default, software is detected based on the presence of shortcuts or information in the registry. This
method guarantees an optimal detection, in terms of speed and quality. Analyzing the whole local
hard disks would take too much time, and use too many resources.
If needed, if specific software were not automatically detected, it is possible to configure specific
searches based on part of file names or folder names.
Operating system
Office suite if available
Some software installed is missing (the ones installed without Windows installation process)
Some software already unisntalled are still present if the uninstallation process failed
Editor names and software names are not unified and not easily analyzed
Most of the time, no software version number
44
24/05/2013
EasyVista 2013
Antivirus
Information
VirusScan
Version
Date of virus base
Version of virus base
Kaspersky
Version
Date of virus base
ETrust
Version
Date of virus base
Panda
Version
Date of virus base
FProt
Version
Date of virus base
Norton AntiVirus
Version
Date of virus base
Version of virus base
45
24/05/2013
EasyVista 2013
Viguard
Version
NOD32
Version
Version
Date of virus base
Version of virus base
Remark: specific historization can be done, either by configuration, or by specific development for
more sophisticated needs.
Data
Technical
characteristic
Event
Changes in one of the following values :
Connected Device
BIOS
RAM Size
Login Name
OS Language
OS Serial Number
Default Printer
User Time zone
OS Registered user
OS Registered company
Comment
User language
Screen Resolution
Domain name
Computer name
Add or remove a connected device
Network card
Component
Component added
Component deleted
Software
Software installed
Software uninstalled
46
24/05/2013
EasyVista 2013
Its necessary to create a unique identifier, because theres no natural identifier on an asset:
COMPUTER NAME: can change and may be duplicate on complex company networks
IP ADDRESS / MAC ADDRESS: can change during life cycle of the computer
UUID: many duplicates exist because constructor do not guarantee that this field supposed to
be unique, is really uniquely filled for each machine
SERIAL NUMBER: many duplicates, event for the same constructor, and often not correctly
defined (To be filled, 12345, etc)
ASSET TAG: based on a human action, and not surely unique on a complex estate
On highly secured PCs where users are not allowed to write information in these places, it is
recommended to do a first inventory using an administrator account. This inventory will generate the
EasyVista tattoo at the right place and users will be granted to access to it in read only.
During the integration of the collected data for this asset, the integration process will try to merge the
old and the new tatoo to avoid creating duplicates in the database.
To do that, it will compare the following information of both collected data:
1. Asset Tag
2. Computer Name / Maker / Model / Serial Number / UUID
47
24/05/2013
EasyVista 2013
The pre-process system uses the speed and power of the SQL language to prepare the data (convert,
delete, merge).
Three steps:
1. From the different sources of data you have, copy the data in temporary tables, on your
EasyVista data server.
The pre-import process can work on data coming from LDAP servers, SQL Server, Oracle,
and any ADO/ODBC connector.
2. Once imported, the data can now be selected, converted, purged into a single result table
ready to integrate to EasyVista.
Example :
LDAP data separates FIRST NAMES and LAST NAMES: you can use the pre-import
process to merge them, and use a template to have the name in capitals for example.
LDAP data is often full of unwanted information (test accounts, distribution
accounts). You can use the pre-import process to delete the data you do not need
to avoid importing them into EasyVista
3. Integrate the data into EasyVista using the Integration tools
48
24/05/2013
EasyVista 2013
EasyVista will allow you to define an automatic process regardless of data complexity, quality, variety
and sources you need to integrate.
2
Data post process
Table
Table
Table
SQL Queries
Table
Model
Table
Table
Executing queries on
Local tables:
Delete , Insert, merge,
Table
Easyvista
database
Extract
Table
Table
LDAP directory
10
49
24/05/2013
EasyVista 2013
Specific access to your Active Directory is required to check what information can be used to map
users between Active Directory and EasyVista.
Concepts
1 Identification
2 - Authentication
3 - Habilitation
2 - Authentication
3 - Habilitation
| Copyright Staff&Line |
Automatically create new meetings in Exchange calendars for actions defined in EasyVista for
consultants
50
24/05/2013
EasyVista 2013
The calendar of each consultant defined in EasyVista must be shared and accessible to the MAPI
account defined on the application servers.
EasyVista is compliant with EXCHANGE 2003, 2007 and 2010.
51
24/05/2013
EasyVista 2013
MSI
EAN8
EAN13
CODABAR
CODE39
I2OF5
CODE128
RPC / ENCODED
RPC / LITERAL
DOCUMENT / LITERAL
The text and subject of the e-mail are used to define the new requests. Attachments are saved and
linked to the new request in the attached documents screen.
52
24/05/2013
EasyVista 2013
New request
Request number
Creation date
Requestor
Subject
Status
Origin
Localisation
Details
Account 1
SMO Server
POP3 Server
Account N
(RFC_NUMBER)
(SUBMIT_DATE)
(REQUESTOR_ID)
(SD_CATALOG_ID)
(STATUS_ID)
(REQUEST_ORIGIN_ID)
(LOCATION_ID)
(COMMENT)
Directory www/resources/..
Document 1
Document 2
17
Characteristic
Inventory
Fields
Inventory Agent version
Inventory date
Path of the collection point
Collection point name
Machine
Manufacturer
Model
53
24/05/2013
EasyVista 2013
Serial Number
UUID
Identification
Computer name
Asset tag (if available)
EasyVista unique Identifier
BIOS
Date
Name
Version
Memory
DOS Memory
Extended
Total
Logical disks
Speed
Memory type (DIMM, etc)
Size or NOT INSTALLED
For each logical disk :
Physical disks
Disk number
Name
Serial number
Type (IDE, etc)
Number of partitions
Network
Disk vendor
Serial number
Firmware
Smart Disk information available (current value, threshold value,
reference)
IP address
54
24/05/2013
EasyVista 2013
Network adapter
DHCP Active Yes / No
DHCP Server
Subnet Mask
Default Gateway
WinsPrimary
WinsSecondary
DNS Servers
Mac Address
Network cards
Printers
Name
Speed
HALF DUPLEX or FULL DUPLEX
Printer number
Local or network resource linked to this printer
Port
Printer name
Full printer name
Network server providing the resource
Name
Vertical frequency
Horizontal frequency
Model description
Serial number
Vendor ID
Model ID
Manufacture date
Peripherals tree
Internet
Device number
Name
Default browser
55
24/05/2013
EasyVista 2013
Default mail
Internet Explorer
Default page
Proxy enable Yes/No
Security level
Cookies status
Active script authorization
Java Parameters
Instant messenger
ICQ Yes / No
MSN Messenger Yes / No
Yahoo Messenger Yes / No
Screen saver
Active Yes / No
Is secure Yes / No
Timeout value
Screen saver name
Boot
USB Devices
Reference
Partition name
Number of USB ports available
Main board
Port number
Product name
Manufacturer
Vendor ID
Product ID
Manufacturer
Product name
Serial number
CPU
Frequency
Vendor string
56
24/05/2013
EasyVista 2013
Vendor
TFMS
Brand ID
Number of processors
Number of used, active and free sockets on mother board
Fields
NETWORK or LOCAL software
Exe name
Path to exe name
Software editor
Name
Long version
Short version
Language
Path to shortcut
Windows
Windows version
Product ID
System root folder
Registered organization
Registered owner
Temp folder
Workgroup or Domain
Comment
Screen resolution
Default printer
User ID
57
24/05/2013
EasyVista 2013
Time zone
Country
System language
User language
Auto logon Yes / No
Windows update configuration
Windows firewall configuration
License numbers
Product name
License number
Lotus notes
Version
Outlook
Server used
Connection string
LDAP / AD
Server used
Connection string
Antivirus
Software executed
at windows startup
For each antivirus detected (see list of detected antivirus in this document):
Antivirus name
Virus def
For each software configured to run at windows startup:
Services
Hotfix
Installed software
For each windows log (application, system, security, etc), list the last ten
errors:
58
24/05/2013
Environment
variables
ODBC Drivers
EasyVista 2013
Driver name
Version
Recycler
Name
Driver
For each recycler defined on the machine :
DMI
Size
Folder used
Present Yes / No
Process in memory
Process ID
EXE and path to exe
Editor
Name
Version
Language
TCP or UPD
Port number
IP of the connected machine
Profiles
Administrator
accounts
Computer
name
Linux
Solaris
HP-UX
AIX
Yes
Yes
Yes
Yes
59
24/05/2013
EasyVista 2013
No
Depends of the
machine
Yes
No
HP
IBM
Machine Type
Yes
Yes
BIOS name
and version
No
No
No
Main board
manufacturer
No
HP
IBM
Main board
serial number
No
No
No
UUID
N/A
N/A
Serial number
Yes if available in
the BIOS
Vendor
Model
Mac address
Yes
Yes
No
Yes
IP Address
Yes
Yes
Yes
Yes
DNS server
No
Name
Yes
Yes
Subnet mask
Yes
Yes
Yes
Yes
CPU
Frequency
Yes
Yes
Yes
Yes
CPU Vendor
Yes
No
Yes
Yes
CPU Name
Yes
Yes
Yes
Yes
CPU Count
Yes
No
Yes
Yes
No
No
No
Monitor serial
number
No
No
No
Monitor
Vendor
No
No
No
Monitor Model
Depends of the
monitor
Memory Total
Yes
Yes
Yes
Yes
Membanks
Yes
Yes
No
No
Logical
partitions
Name, Physical
storage, size, free
space, type
Name, Physical
storage, size, free
space
Name, Physical
storage, size, free
space
Name, Physical
storage, size, free
space
User ID
Name
Name
Name
Name
Installed
software
OS Information
Linux
Solaris
HP-UX
AIX
Based on RPMs or
packages installed
Based on packages
installed
Based on packages
installed
Based on packages
installed
Vendor, version
Vendor, version
Vendor, version
Vendor, version
60
24/05/2013
EasyVista 2013
61