|
 |
The Inventory |
 |
|
|
Move the mouse cursor onto the item of Inventory on the menu will bring a pull-down menu to you. Click any item you prefer to see.
|
|
|
 |
|
|
|
 |
 |
OS Information |
 |
|
|
This inventory shows the following entries: OS Product Name, OS Version, OS Service Pack, OS Build Number, OS Type, and Kernel Version (The Linux platform only).
 Fig. The OS Information |
|
|
|
 |
|
|
|
 |
 |
FRU Information |
 |
|
|
The inventory of FRU (Field Replaceable Unit) information is the identities of components that were stored in the non-volatile memory. The service personnel of ASUSTeK usually examine this information while they are going to replace any defeated parts. Note that not all model of systems support these information. Typical FRU information has several groups such as Motherboard, Backplane, or Power Panel.
 Fig. The FRU Infomation of MB |
 Fig. The FRU Information of Backplane |
 Fig. The FRU Infomation of Power Panel |
|
|
|
|
 |
|
|
|
 |
 |
Software Information |
 |
|
|
The inventory of software information can be categorized into five groups: Service, Driver, Application, Process and System Variable.
- Service: The programs, which run in the background after the system is started up, are usually referred to service. To express this term by a jargon in the UNIX world, it is called daemon. The information panel here is not only informative but also manageable. You can stop a starting service and start a stopped service. Note that if there were some other services depending on the service that you are trying to start up, they would be started as well. Do not casually start or stop any service if you are not certain to understand the function of that service.
- Driver: Some programs are controlling the hardware or fundamentals of OS in your system and these are called as drivers. In the terms of the UNIX world, it can be "kernel modules". This information is similar to Service that a driver can be started or stopped. Again, do not carelessly start or stop any driver if you have no idea about what it is doing.
- Application: In a Windows platform, any extra installed software package will be listed here. In a Red Hat Linux platform, all installed RPM package are listed here.
- Process: All running processes or tasks are listed here. In the term of the UNIX world, it's done by "ps" command. In a Windows platform, it comes from the task manager. It also lists the CPU time and working set that a process consumed.
- System Variable: it lists the global environment variables that each users of that system will have. Each user may override your own variables by yourself.
 Fig. The Software Infomation of Service |
 Fig. The Software Infomation of Driver |
 Fig. The Software Infomation of Application |
 Fig. The Software Infomation of Process |
 Fig. The Software Infomation of System Variable |
|
|
|
|
 |
|
|
|
 |
 |
System Devices |
 |
|
|
It provides you with a graphical view of the hardware that is installed on your computer. You can determine whether the hardware on your computer is working properly. Any of four computer components that control how the devices on the computer work. These four resources are interrupt request (IRQ) lines, direct memory access (DMA) channels, input/output (I/O) ports, and memory address. Navigate this graphical tree by expanding or collapsing the class nodes to see the belonging of device entries. Click any of the device entries to see how these resources are allocated by each of devices.
There is another separated view of System Devices called PCI Devices. It is similar to Overall except it only enumerates PCI Devices.
 Fig. The Overall Devices |
 Fig. A device information is expanded |
 Fig. The PCI Devices |
|
|
|
|
 |
|
|
|
 |
 |
Network Cards |
 |
|
|
This inventory divides into sections of single Network Group and one or more Network Cards. The section of Network Group contains the information of Host Name, Domain Name, DNS Servers and Total of Network Cards.
Each section of Network Card includes Product Name, Manufacturer, MAC Address, Bus, Device, Function, Enable DHCP (Dynamic Host Configuration Protocol), IP Address, Subnet Mask, Gateway, WINS Server, DHCP Server, Driver Date, and Driver Version.
 Fig. The Information of Network Card |
|
|
|
 |
|
|
|
 |
 |
Event Logs |
 |
|
|
By using the viewer, you can gather the information about hardware, software, and system problems and watch over any security event.
- Application: It contains events logged by applications or programs. For example, a database program might record a file error in the application log. The developer of that application decides which events to record.
- System: It contains events logged by the system components. For example, the failure of a driver or other system component to load during startup is recorded in the system log. The event types logged by system components are predetermined.
- Security: It can record security events such as valid and invalid logon attempts, as well as events related to resource use, such as creating, opening, or deleting files. An administrator can specify what events are recorded in the security log. For example, if you have enabled logon auditing, attempts to log on to the system are recorded in the security log.
- ASWM: It records all events that are issued by ASWM's agent or web page. All activities of ASWM will be logged here for you to examine later.
- SEL: System Event Log is a log that is done by the IPMI firmware. IPMI (Intelligent Platform Management Interface) is a specification that promoters are Intel, HP, NEC and Dell. When your system is IPMI-enabled, all your hardware sensors in your system will be monitored even if the OS is not existed or crashed. Moreover, it still works when your system is powered off but a 5V stand-by voltage is still remained for IPMI adapter's operation. IPMI logs any abnormal events of hardware sensors into your system's size-limited but non-volatile memory. It can be downloaded and saved in a permanent storage (e.g., hard disk) by ASWM agent when ASWM agent is started up.
 Fig. The Event Log of Application |
 Fig. The Event Log of System |
 Fig. The Event Log of Security |
 Fig. The Event Log of ASWM |
|
|
|
 |
|
|
|
 |
|