Schedule time and frequency to sync information of previously scanned assets and scan new assets added to the network. ServiceDesk Plus allows you to configure different scanning schedules for IT assets with and without a UEM agent.
Role Required: SDAdmin
Go to Admin > Discovery > Schedule Scan.
Schedule agent-based UEM scan - Enable this option to schedule agent-based scanning of IT assets such as Windows, Linux, and Mac machines. Fill out the following fields.
|
Frequency |
Choose the frequency to schedule the scan. |
|
Start at* |
Set the scan start time. |
|
Time Zone |
Select the time zone of the domain/network. |
|
Perform this* |
Select the recurrence pattern. The available option may vary based on the frequency selected. |
* Mandatory fields
Agent-based Scan Process
During the agent scan, only the machines that are powered on and within the network will be scanned. For example, if there are 500 machines in your inventory, and only 400 are powered on and within the network during the scheduled time, then only those 400 machines will be scanned. Machines that are not powered on or outside the network will be scanned whenever they are powered on and come within the network.
The agent follows a 90-minute refresh cycle, pulling schedule information from the server during this period. Once the information is retrieved, the agent will scan the assets without any intervention from the server.
Schedule agentless scan - Enable this option to schedule scanning of IT assets such as Solaris, AIX, HP-UX, SNMP supported network device, VMware, and Cisco IP Phone.
Select a scan frequency from the following options and set the recurrence pattern.
|
Scan Once |
Set the date and time to scan the IT assets. |
|
Daily Scan |
Set the time (hours and minutes) to scan devices on a daily basis. Select a date to schedule the scan. |
|
Weekly Scan |
|
|
Monthly Scan |
|
|
Periodic Scan |
Enter a period to repeat the scan. By default, the value is 7. |
Agentless Scan Process
Agentless scan relies on DNS and connectivity to scan machines within the network. For an agentless scan, the machines must be powered on and must be within the network to be reachable. If a machine is not powered on/not within the network, it is marked as "Failed" during the scan process. The ports used for the scan must be reachable for the scan to be successful. Click here to know about the ports used during the scan. Machines must be pingable to ensure they are reachable during DNS resolution.
Scan History Clean up - Enable this option and specify the number of days after which the scanned information can be deleted.
Scan new devices added to the network - Enable this option and provide the recurrence pattern to re-scan the domain/network.
Click Save.

Click View History to view all activities performed to schedule scan, clean scan history, and re-scan domain/network.