Asset Scan

Asset Scan

Asset Scan 

Scanning allows you to fetch asset information, including hardware and software details. Below is the list of supported devices and the corresponding asset data fetched during a scan.

Supported Devices  
Attributes  
Workstations/Server:  
Windows, Linux, Mac, AIX, Solaris
Windows (HyperV)
Asset Details: Name, Model, Service Tag, Operating system, Last Logged In User, Domain, Manufacturer Name, Discovered Serial Number, and Vendor.
Computer System: Name, Model, ServiceTag, Manufacturer, BIOS Date, BIOS Version, and Total Slot.
Operating System: Operating System, Version, Build Number, Service Pack, and Product ID.
Memory: Physical Memory and Virtual Memory.
Processor: Serial Number, Processor, CPU Stepping, Manufacturer, Number of Cores, and Clock Speed.
Installed Memory Modules: Serial Number, Socket, Capacity, Module Tag, and Bank Label.
Network Details: Serial Number, IP Address, MAC Address, NIC, DHCP, and DHCP Server.
Disk and Drives: Serial Number, Model, Serial Number, Manufacturer, and Capacity.
Logical Drives: Serial Number, Drive, Drive Type, File Type, Capacity, Free Space, and Drive Usage.
Physical Drives: Serial Number, Drive Name, Drive Type, Manufacturer, Drive Version, and Drive Provider.
Printer Details: Serial Number, Name, Server, Model, Type, and Location.
Keyboard: Keyboard Type
Mouse: Mouse Type, Mouse Manufacturer, and Mouse Buttons.
Monitor: Monitor Type, Serial Number, and Manufacturer.
Sound Card Details: Sound Card Name.
Video Card: Chipset, Video Card Memory, and Video Card.
Ports: Serial Number, Port Name, and Port Status.
USB Controller: Serial Number and Name.
Only For HyperV
Virtual Machine: Name, Guest OS, Memory Reservation, Memory Limit, Memory Share, Memory Shares Level, CPU Reservation, and CPU Limit.
Virtual Host  
VMware [ESX, ESXi]
Asset Details: Name, Model, Operating system, Model Manufacturer, VM Platform, and Vendor.
Computer System: Name, Model, Manufacturer, and Total Slot.
Operating System: Operating System, Version, Build Number, and Product ID.                                          
Processor: Serial Number, Processor, CPU Stepping, Manufacturer, Number of Cores, and Clock Speed.                    
Logical Drives: Serial Number, Drive, Drive Type, File Type, Capacity, Free Space, and Drive Usage.                            
Virtual Machine: Name, Guest OS, Memory Reservation, Memory Limit, Memory Share, Memory Shares Level, CPU Reservation, and CPU Limit.
SNMP devices:  
Printer, Router, and Switch.
Printer:  
  1. Asset Details: Name, Discovered Serial Number, and Serial Number.
  2. Printer Input Subunits: Serial Number, Input Unit Name, and Input type.
  3. Printer Output Subunits: Serial Number, Output Unit Name, and Output type.
  4. Printer Marker Subunits: Serial Number, Marker Type, Marker Life Count.
    Printer Marker Supply Subunits: Serial Number, Marker Supply Type, Marker Supply Description, Marker Supply Max Capacity, Marker Supply Level, and Marker Supply Usages.

Router:  
  1. Asset Details: Name, Product Name, State, OS Type, DRAM Size, Flash Size, CPU Revision, NVRAM Size, and Config Register.
  2. Switch Interface: Serial Number, Interface name, IP Address, and Speed.

Switch:
  1. Asset Details: Name, Discovered Serial Number, Product, OS version, NVRAM size, DRAM size, and Flash size.
  2. Switch Ports: Serial Number (index number), port name, Operational state, admin state, and speed,

Discovered Serial Number will be fetched only for Cisco Switch/Cisco Router. 
 
 The Deep Discovery option will be available only for SNMP devices like printers, routers, and switches. Other SNMP devices will be categorized based on the corresponding product type if unknown OID is configured. 

Prerequisites for Asset Scan 

ServiceDesk Plus MSP Cloud uses probes to fetch asset-related information. Only the devices that are associated with a probe can be scanned.
Probes are applications installed on a network to fetch the details of the devices present in that network. For the probes to scan devices successfully, make sure that the target devices meet the below requirements:

Windows Machines

Remote Registry Service must be running in the target machines. [ Click here for instructions to check ]
Port 139 (File Sharing) must be open on the target machines. [ Click here for instructions to check ]
Admin$ share ( \\TargetMachine\admin$ share ) of the target machine must be accessible from probe. [ Click here for instructions to check ]

Linux Machines

SSH port 22 must be open [ Click here for instructions to check ]
Printers, Routers, and Switches
SNMP (v1 / v2c / v3) must be enabled and the corresponding credentials must be configured for the network scan.
To know how a probe works, click here.

Scan Assets  

You can initiate a scan from the assets list view and asset details page.
To initiate from assets list view,
  1. Go to Assets and click the required product type on the left pane accordion.
  2. Choose a customer from the drop-down in the application header.
  3. Select the required assets from the list by using the corresponding checkboxes.
  4. Click the Actions drop-down on the toolbar and click Scan Now.
For assets with no probes, you will be redirected to associate a probe and create/update the credentials. After you associate, click Save and Scan now to initiate asset scanning.

To initiate a scan from the asset details page,
  1. Go to the required product type list view.
  2. To view customer-specific assets, choose the required customer from the drop-down in the header. Use filters to narrow down specific assets.
  3. Click the required asset in the list to open its details page.
  4. Click Scan Now on the toolbar.

Scan Failures 

To view devices whose scans are failed and the reasons for scan failures,
  1. Go to Assets.
  2. On the left pane, click Scan Failures.
  3. To view customer-specific scan failures, choose the required customer from the drop-down in the header.
  4. On the list view, you will find a list of devices whose scans failed, along with key details such as failure error message, associated site, and last scanned period. Use the column chooser icon on the toolbar to view other details, such as error reason, audit details, and user details.
Error Message
Reason
Unknown UserName or Bad Password
Verify the credentials given in the Credentials Library or in the Domain Scan.
If Credential Library is used, make sure the user name is given in DomainName\UserName format for Windows.
Unable to connect to admin$ share
Remote registry service might not be running in the target machine. Go to Administrative tools > Windows Services in the target machine and start the remote registry service.
Go to the target system and open Computer management > Shared folder > ADMIN$. Right click and start sharing if it is not shared.
Check whether any antivirus, firewall, or Endpoint security software is preventing access to admin$ share.
None of the credentials configured in the network scan succeeded
This error occurs when none of the credentials configured in the network scan succeeded during the scan.
Local Asset credential not succeeded
The credentials selected under Workstations > Change Credentials pop-up did not succeed due to an unknown user name or bad password.
Unable to create or start remote service
Check whether the given credentials have admin privileges. Also, make sure the above mentioned conditions for Windows machines are satisfied.
 
Port [139/22] not open
For a target Windows machine, make sure that port 139 is open and accessible from the probe.
For a target Linux machine, make sure that port 22 is open and accessible from the probe.
To know how to check if ports are accessible, refer to this section
No Windows credential configured
In the network scan configuration, check if you have selected a Windows credential in the credential library for scanning Windows machines.
No SSH credential configured
In the network scan configuration, check if you have selected a SSH credential in the credential library for scanning Linux/Mac machines.
 
Any other error message
Make sure that you provided username in the DomainName/UserName format for Windows machines in Credential Library.
 

List View Actions 

  1. Actions: Select the required devices in the list by using the check boxes and use the Actions drop-down for the following:
  2. Scan Now: Initiate a scan for the selected devices.
  3. Update Credentials: Update authentication details for the selected devices and then initiate a scan. You can enable software scan, if needed.
  4. Filter: By using the relevant drop-downs on the top-right, you can filter scan failures based on product type and last scanned on period.
  5. Search: Use the search icon   to perform a column-based search on the scan failure list.
  6. Export: Use the export icon on the top-right to export scan failure records in the CSV format. You can export the first 10,000 records or set export criteria for specific records.
  7. Table Settings: Use the table settings icon for the following:
  8. Records Per Page: Limit the number of asset records to be displayed on a page.
  9. Sort By Column: Sort and view the asset records based on the criteria listed in the drop-down. You can also click the column name on the list view page to sort the asset records.

How does a Probe performs a network or domain scan  

  1. During a network or domain scan, the probe will look for the list of alive hosts.
  2. For each alive host, the probe will determine whether to perform a Windows, Linux, or SNMP scan.
  3. Based on the credentials and open ports, the probe will determine whether the target machine is a Windows, Linux, or SNMP device.
  4. If the target machine is Windows, the probe will copy scan-related files to admin$ share of the target machine and execute the files.
  5. For a Linux target machine, the probe will copy the shell script file and execute the script.
  6. For SNMP devices, predefined OIDs are queried.
  7. The scan results are then logged in ServiceDesk Plus MSP Cloud.

How to check whether Remote Registry Service is running in a target workstation    

  1. Go to the target workstation.
  2. Open the Windows Services console and check the status of Remote Registry Service.
  3. The Service status must be Runn​ing.


How to check whether admin$ share is accessible    

Admin$ share of target workstations must be accessible from probe for scan to be successful.
Try the following net command and see if the admin$ share is accessible:
  1. Go to the probe machine.
  2. Open the command prompt.
  3. Run the command: net use \\<TargetHost>\admin$ /user:domain\administrator
  4. Provide the password. Use the same credentials you have configured in ServiceDesk Plus MSP Cloud for the domain scan or the network scan.
  5. The command will complete successfully.
Also, try the following and see if admin$ is accessible:
  1. Go to the probe machine.
  2. Open the command prompt and type \\<TargetHost>\Admin$.
  3. Provide the same credentials you have configured in ServiceDesk Plus MSP Cloud for the domain scan or the network scan.
  4. The connection will now be established, and the target workstation's files will be shown in the Windows explorer.

How to troubleshoot if the port 139 is not open and admin$ share is not accessible 

  1. Go to the target workstation.
  2. Open the Windows firewall and check the status.
  3. If the firewall is running, then allow access to TCP port 139.
  4. Check for any other antivirus, security, or endpoint software blocking access to port 139.
Try the suggestions in the following discussions:
  1. https://social.technet.microsoft.com/Forums/windows/en-US/2ff997ca-bb0d-4ea5-87c0-6264433fc4be/unable-to-access-administrative-shares-on-a-windows-7?forum=w7itpronetworking
  2. https://social.technet.microsoft.com/Forums/en-US/9f375a5d-9194-45e8-bcb6-4656bf05f180/problems-accessing-administrative-shares-remotely-on-windows-2012-cannot-access?forum=winserver8gen
  3. https://social.technet.microsoft.com/Forums/windows/en-US/4efab32e-3f9c-458a-835c-5ba0ce9a49cc/domain-machine-cant-access-administrative-shares-c-admin-on-windows-7-x64-network-path-was-not?forum=w7itpronetworking
  4. https://social.technet.microsoft.com/Forums/en-US/8ecac154-b871-46c0-8529-fd7fb7ffe943/windows-10-v1803-cant-access-admin-share-c-in-a-domain?forum=win10itpronetworking

Things to Check in Probe Logs   

Check for Latest Scan Log 

Go to the probe-installed machine and refer to the probe log. Latest scan log will be available in the file ProbeMain0.log  (C:\ManageEngine\SDPODProbe\logs)

Check if the Host is Alive 

During a network or domain scan, the probe uses NMap to find the list of alive hosts. Only if a host falls under the Alive Hosts List does the probe proceed to scan that host.  Check whether the host name or IP is available in the alive hosts list. Please also check for any Windows error codes.

Alternate way of scanning 

You can run a self scan script in each of the workstations, either through GPO or task scheduler. Refer here for more details.
 

    • Related Articles

    • Network Scan

      Network scan allows you to discover networks that are part of your organization and scan them periodically to retrieve asset information. Using network scan, you can scan Windows, Linux, MAC, Solaris, AIX workstations, SNMP devices, VMware ...

    • Asset Details

      Asset Details View all details of an asset, including the financial and contractual data and historical records. Technicians with edit permission to the asset can spot-edit field values in the details page. To view details of an asset, Go to Assets. ...

    • Asset Loan

      Asset Loan Loan assets in the organization to end users and technicians for a defined period. Asset Loan enables you to add multiple assets to a single loan, adjust an ongoing loan by adding new assets, extend or pre-close loans, return specific ...

    • Asset FAQs

      Asset Management License Consumption and Asset States Will an asset be included in license consumption if it is moved to a disposed or expired state? No, Disposed or Expired assets do not consume license. How to create an asset state similar to ...

    • Introduction to Asset Audit

      Introduction to Asset Audit Asset audit is the process of verifying the existence, location, and condition of an organization's assets. It is a crucial aspect of asset management that helps ensure accurate and up-to-date asset records. With ...