Service center > Checklist

Architecture and interfaces

  1. Is the software based on a recognized and independent de facto standard or best-practice approach such as ITIL?
  2. Which architectural features of the software ensure a high level of scalability, and which ensure high-performance software distribution and inventory management?
  3. Are standard interfaces such as XML supported?
  4. Which ITIL processes does the tool support?

Operating systems

  1. Which widely used operating systems does the software support (Windows, Linux, Solaris, AIX, HP-UX)?
  2. Are unattended setup and cloning supported for the installation of operating systems?
  3. Can RAID controllers be configured?
  4. Is there a local crash recovery function?

System management in practice

  1. What measures are in place to protect the system against manipulation?
  2. Is the software able to manage systems at remote locations?
  3. Are software configuration and installation performed in the background, thus not affecting system operation?
  4. How does the product make optimum use of the available bandwidth (speed versus network load)? Does it offer dynamic bandwidth management? If so, how is this implemented?
  5. Is the entire data stream between the distribution server and end device encrypted? What method is used for this? What key lengths are used?
  6. How is it possible to prevent all systems from transferring their results at the same time and instead ensure that distribution is optimized within a definable period?
  7. Is there a specific technology that facilitates efficient data transfer?
  8. Which ports are required in order to supply software to systems behind a firewall?
  9. How are offline clients included?
  10. How is the progress of a distribution operation followed? How does the software support postprocessing if installation is unsuccessful?
  11. Is it possible to have different user groups with different permissions?
  12. What are the requirements of the client components on the systems managed (hard disk space, RAM, etc.)?
  13. Can installation instructions be adapted quickly to suit specific requirements?
  14. How is it ensured that only the files of the currently installed version are installed on the target system and that files belonging to older versions that are no longer required are deleted?
  15. How are dependencies between different software packages represented? Where are these defined? What kinds of dependencies are supported? Are transitive dependencies supported?
  16. What specific functions are used to prevent systems affected by the interruption of software distribution (because of a network problem or system shutdown) from continuing in operation?
  17. Is automatic conflict checking offered? What criteria are used for the checks? Where is the data stored?
  18. How are installation packages parameterized, and where are the values of these parameters stored? Can the values of these parameters be taken from the database of a configuration management system?
  19. What package formats does the system management software support (MSI, RPM, PKG, DEB)? 
  20. How is version management implemented for the software to be distributed?
  21. Does the system offer a set of proven standard reports? Can freely definable reports be added to these?
  22. How many people are required to operate the system management software for 5,000 devices?

Project management and support

  1. Are projects run by certified project managers?
  2. Is the documentation and support available in German?
  3. What influence do you, the customer, have on software development? Is the vendor based in Germany?