This document discusses ways to optimize performance in Spiceworks by choosing fast hardware, adjusting scanning schedules and intervals, enabling extensions and plugins, and checking logs to ensure scans are occurring as expected. It provides examples of hardware configurations that can support 180 devices and 3000 tickets as well as the types of logs to search and what information they contain such as scanning times and actions.

1. Going The Extra Mile
With Spiceworks
Presented By
Greg & Tabrez
October 21 , 2010

2. Going The Extra Mile
• Performance
• Scanning
• Checking for Scanning Errors
• Spiceworks Extensions
• Microsoft License Manager
• Intel Power Manager
• Intel Maintenance Manager
• Windows Performance Monitor
• Intel KVM
• Device Uptime

3. Going The Extra Mile
• Performance
– Choose a fast browser
– Machine -> Dual Core or better; 4 Gig memory
– Help Desk Email polling interval
– AV setup…
– Widgets on Dashboard(s)
– Plugins
• Scanning
– Primary Scan -> long schedule = network + device data + software + alerts
– Health Check -> short schedule = network data + exchange data
– Widgets & App -> realtime = network data + widget data
• Credentials (Scanning & Network Backup)
• Network Data & Backup -> SSH, Telnet, Enable
• Windows -> WMI & SNMP
• LINUX/OS-X -> SSH, SNMP
• Printers -> SNMP & JetDirect

4. • Page load time for
• Dashboard
• People View
• Purchasing View
• Help Desk
• 180 devices + 3000 tickets
• Windows XP SP3, AMD Athlon 64X2 Dual, 2.19 GHz, 1.75 GB RAM
Details

5. • Spiceworks Logging
– Production.log -> General Application Log
– Finder_child.log -> Scheduled Scanning Log
– Finder_re.log -> Rescan Specific Device Log
– Finder _watch.log -> Health check.log
Sample: search finder_child.log for “rb:”
Check time vs action
1
2
Check AV blocking; Firewall blocking

6. • Spiceworks Logging
– Production.log -> General Application Log
– Finder_child.log -> Scheduled Scanning Log
– Finder_re.log -> Rescan Specific Device Log
– Finder _watch.log -> Health check.log
Sample: search finder_child.log for “rb:”
Check time vs action
1
2
Check AV blocking; Firewall blocking