Server Administration
  Home arrow Server Administration arrow Page 2 - Spiceworks in the Enterprise
Codewalker Forums 
  Tutorials  
Database Articles  
Miscellaneous  
Navigation Usability  
PEAR Articles  
Programming Basics  
Server Administration  
XML Tutorials  
  Reviews  
Database Book Reviews  
Linux Book Reviews  
Miscellaneous Reviews  
PHP Book Reviews  
PHP Software Reviews  
Server Admin Reviews  
SQL Tool Reviews  
  Code Gallery  
Content Management Code  
Contest Code  
Counters Code  
Database Code  
Date Time Code  
Discussion Board Code  
Email Code  
File Manipulation Code  
GUI Code  
Link Farm Code  
Miscellaneous Code  
Search Code  
Site Navigation Code  
User Management Code  
Mobile Linux 
App Generation ROI 
IBM® developerWorks 
Download TestComplete 
Forums Sitemap 
Weekly Newsletter 
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
SERVER ADMINISTRATION

Spiceworks in the Enterprise
By: Luke Niland
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 5 stars5 stars5 stars5 stars5 stars / 2
    2008-12-10

    Table of Contents:
  • Spiceworks in the Enterprise
  • Spiceworks Features
  • Reports
  • Application Speed

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    Spiceworks in the Enterprise - Spiceworks Features


    (Page 2 of 4 )

    Hardware Inventory

    The hardware inventory is the heart of Spiceworks, and probably the place that most people will go first after doing the initial install.

    The first thing you’ll need to do is tell Spiceworks what subnets it can scan, and which user will do the scanning. You’ll need to pick a user that has access to all of the machines on your subnet, and (obviously) the subnet must be accessible from the server.

    To get the information pertaining to the clients you are scanning, Spiceworks uses WMI (Windows Management Instrumentation), so all of the clients need this service installed and running. Under normal installs this will be the case.

    The speed of the scan will depend on a few issues, such as the speed of the server, the speed of the network, the speed of the clients, and so on. Even so, a scan of about 100 clients should take about 40 minutes.

    The scan will have difficulties running if the firewall is active on the clients. Additionally, it does a reverse lookup into DNS. It’s a good idea to turn off the clients' firewalls (via group policy or registry change), and make sure your DNS is clean before running the scan. When the scan has finished, your inventory page will be full of discovered devices.





    Software inventory

    When the scan has completed, as well as the hardware, you will also have a list of all the software installed on your network. You can get a summary of the installed software from the software section on the Inventory page.

    One of the problems with many software auditing tools is sometimes they have problems working out what the software is, in relation to other software on the machine. For instance, sometimes it will find Word, Excel, and PowerPoint and instead of classing them as the Microsoft Office package, it thinks they are separate pieces of software.

    Spiceworks does quite a good job of this, but on some machines it still classes each part of Office as a separate piece of software.

    If you click on one of the software packages in the list, you can see more information on the software, but most importantly you can fill in how many licenses you have for each product. One thing that would be nice to have at this point is the ability to flag software that does not need a license. This way you could flag a service pack or piece of open source software. If you could do this, you won't have to go in and add another license when Spiceworks detects a new install. 



    More Server Administration Articles
    More By Luke Niland


     

    SERVER ADMINISTRATION ARTICLES

    - Processes in the UNIX Shell
    - Migrating from Windows to Wine
    - Wine: Not Another Emulator
    - Preventive Measures to Block SSH Attacks
    - Monitoring Temperatures with Cacti
    - Cacti: RRDTool-based Graphing Solution
    - Network Magic 5.0 Review
    - Netfilter and Iptables Overview
    - Installing and Configuring Squid
    - Clickfree PC Backup Systems Compared
    - Squid, the Caching Proxy
    - Regular Expressions in the Unix Shell
    - Source Code Version Control Solutions
    - OTRS: Open Source Ticket Request System
    - Clonezilla: Free Mass Disk-Cloning Utility





    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 4 Hosted by Hostway
    For more Enterprise Application Development news, visit eWeek