Network Asset Manager is light weight application which the network administrators can install on their desktops. Once installed, Network Asset Manager can remotely scan all the desktops and servers that are available on the network remotely without any client or agent installation. During the asset discovery process, Network Asset Manager collects all the software and hardware asset information from networked machines. The asset information is collected and then stored in a database on the administrator's machine.
Hardware Asset Tracking
Network asset manager can track lot of different hardware components of system.
- Processor Processor type, number, speed etc.
- OS Operating system name, service pack, last boot etc.
- Bios Manufacturer, version etc.
- Motherboard Manufacturer, model, product etc.
- Disk Size, Interface, Model etc.
- Memory Capacity, speed, from factor etc.
- Logical drives Name, size, free-space etc.
- CD ROM Name, media type, manufacturer etc.
- Video Resolution, memory, name etc.
- Multimedia Name, manufacturer
- Monitor Screen dimension, manufacturer etc.
Software Asset Tracking
Network asset manager can track lot of different components of system.
- Computer System boot state, model, domain etc.
- Share Name, caption, path etc.
- Printer Name, port, status etc.
- Hot fixes ID, description, install by etc.
- Startup Name, command, location etc
- Software Name, version, install date etc.
- Processes Name, Private bytes, command line etc
- Services Name, state, start mode etc.
- IP routes Name, destination, protocol etc.
- Environment variables Name, status, value etc.
- User groups Name, users, domain etc.
Advanced Report generation
Network asset manager has an advanced super easy to use reporting engine build into it. IT managers can generate reports on multiple filtering criteria. The reports can be generated as an html file for easy publication on intranet portals or can even be generated as a XML file for easy import in any third party system.
Following are some of the frequently asked questions when deploying Network Asset Manager.
Why am I not get information from remote computers?
Network Asset Manager uses WMI (Windows Management Instrumentation). The account attempting remote access should be an administrator on the target computer. Other than that please check the following services on the problem PC:
- COM+ Event system
- Remote Procedure Call (RPC)
- Remote Procedure Call (RPC) Locator
On what platforms is WMI available?
WMI is available in all recent versions of Windows. WMI is available on Windows Me, Windows 2000, Windows XP and Windows Server 2003. For operating systems like Windows 98 and Windows NT 4.0, WMI is available as add on service and can be downloaded from http://www.microsoft.com/downloads.
In the download section search for “Windows Management Instrumentation (WMI) CORE 1.5 (Windows 95/98/NT 4.0). Please note that Windows NT 4.0 requires Service Pack 4 or later before you can install and run WMI.
Some additional software are also required for WMI they are :
- Microsoft® Internet Explorer version 5.0 or later.
- Windows Script Host (WSH).
WSH ships with Windows 2000, Windows XP, Windows Server 2003, and Windows Me, but not with Windows NT4 or Windows 98. WSH can be downloaded from http://www.microsoft.com/downloads.
Why is Network Asset Manager not collecting data from a Windows XP SP2 machine?
For remote administration of Windows XP SP2 machine using WMI, you may need to configure the Windows built-in firewall. If the Windows firewall is enabled and not configured to accept a remote WMI connections, Network Asset Manager will not be able to connect to the system. Network Asset Manager will shows "The RPC Server is unavailable" error in such cases.
To configure Windows XP firewall, you need to enable the "Allow remote administration exception" group policy entry. This setting can either be configured on the local group policy of a machine or globally by configuring the global Group Policy settings of an Active Directory domain.
For more details check the following link
Why am I not getting information from remote computer with Windows 2003?
In Windows 2003, WMI subsystem is an optional component and might now be installed with the default Windows 2003 installation. To manually install the WMI, please follow the steps
- Open the Control Panel Add/Remove Programs
- Click Add/Remove Windows Components
- Select the Management and Monitoring Tools check box, then click Details
- Select the WMI Windows Installer Provider check box, and click OK.
If none of the above FAQs solves your problem please log a support request in the support forums. To add a support request click here
Why am I not getting information from remote computer with Windows Vista, windows 7 and Windows 2008?
Starting with Windows Vista, under User Account Control (UAC) access-token filtering can affect which operations are allowed in WMI namespaces or what data is returned. Under UAC, all accounts in the local Administrators group run with a standard user access token, also known as UAC access-token filtering. An administrator account can run a script with an elevated privilege—"Run as Administrator".
When you are not connecting to the built-in Administrator account, UAC affects connections to a remote computer differently depending on whether the two computers are in a domain or a workgroup. For more details check the following link