Win32 Service Application

From WeAreOnWiki

Jump to: navigation, search


Download and Installation

The latest release of the Win32 Service client can always be obtained from the Download page.

The installation program must be executed in a system running Windows NT 4, 2000, XP, 2003 or Vista by a user with administrative privileges. By default, the installation wizard allows the user to create shortcuts to the WeAreON Control Panel (see below) and configure it to run automatically when Windows starts.

If an older version of the software is already installed, the setup program will upgrade the installation. It is not necessary to uninstall the previous version; the wizard will stop the current program and upgrade it automatically.

Once installed, the client will start its periodical connections to the WeAreON hosts, and a new entry for the system will be generated in the Systems List. Users that claim ownership over the data generated by their machines can manage them at the Own Systems area.

Client Service

The WeAreON Win32 Service client runs without any interaction with the users of the system. As a Windows service, it works in the background, independently of user sessions. Every few minutes, it generates an XML status report with the following information:

  • Version of the WeAreON client
  • Local time, last boot and time zone
  • System BIOS
  • CPU architecture and frequency
  • Graphics adapter chipset, resolution, RAM and refresh rates
  • Disk drive file system, capacity and free space
  • Free and physical RAM / Virtual memory
  • Network adapters, IP addresses, network masks, DNS servers and DHCP settings
  • Operating system version and service pack

This information is compressed and uploaded to the WeAreON hosts using the HTTPS protocol. Our servers parse these fields and store the XML files. The data is aggregated and presented in our website

The service application is configured by default to start automatically when Windows starts up. This behaviour can be modified using the standard Windows service management console (services.msc), part of the system Administrative Tools. The service name is "WeAreON Client".

Automatic Software Updates

Since the release of version 0.9.4 Beta, the WeAreON client has been capable of updating itself as instructed by the hosts. This process is performed automatically, and it is controlled by the WeAreON developers.

Soon, the users will be able to configure the degree of automation of software updates:

  • Automatic download and installation
  • Automatic download, manual installation triggered by the user
  • Manual download and installation

In addition to this, the WeAreON website will very soon feature a detailed interface to control automatic updates. Using this feature, owners of data records will be able to schedule the download and installation of newer versions in the machines they control.

User Interface

The graphical user interface to the Win32 Service client is the WeAreON Control Panel. Any user can execute this program, but the Identification tab (see below) is available only to system administrators.

Tray Icon

The Control Panel receives notifications about the service status and displays them at the system tray icon:

  • Service start and stop
  • Software updates
  • Program errors

Tray icon notification

Information Tab

This tab allows all users to do the following:

  • View the unique WeAreON ID assigned to the machine
  • Verify that the WeAreON Client service is running
  • View the date, time and result of the client's latest connection to the WeAreON hosts
  • View the full contents of the latest XML report uploaded by the client

In addition to these features, administrators can start and stop the service, as a limited alternative to the Windows service management console mentioned above.

Control Panel Information tab running in an administrative account

Identification Tab

Users with administrative privileges can enter their user name and password from the WeAreON home page to gain ownership of their data record. They are validated in the next connection to the hosts (which might take a few minutes!) and stored using strong cryptographic techniques. Once a user has claimed ownership over her/his data, they can grant access to private data to other users in the Own Systems area, as described in our Security Model page.

Additionally, the user can set the system's description, which is visible in the Systems List.

Identification tab before setting the user name and password

Identification tab once the user name and password are set and validated

Personal tools