Easy as pie.
The standard installation package that we ship contains three separate Setup routines that can be run separately or together. One setup routine is used to install the Sentry Administration GUI which is used to administer NTSMF data collection. You can install as many copies of the Sentry Administration program as necessary to administer NTSMF across your network. (It is often helpful to run separate copies of Sentry Administration in front of and behind your firewall, for example.
The second setup routine is for the Performance Sentry Collection Service. You can run this setup routine right from the distribution or copy it to disk and run it separately. There is even a silent mode setup option so that you can install the collection agent unattended. Finally, the User Manual shows how to create a simple installation script that you can use to roll out NTSMF across your network of Windows machines. A scripted installation of the collection service has the advantage of being able to assign a Data Collection set (DCS) of your own during installation and also allows you to assign a User Account to be impersonated during Cycle End processingThe User Manual also provides a sample script to use to distribute the NTSMF collection agent using SMS.
For those customers who develop their own distribution and installation procedures, the required set of files needed to install the current version of the collection service is documented on page 17 of the User Manual.
Download the full User Manual (pdf)
Unable to copy the PSSMsg.dll file during installation. Running an installation script to upgrade the collection service, you are likely to find that the PSSMsg.dll file is in use and cannot be replaced. The PSSMsg.dll file is an application Event log message dll that is loaded and used by the Event Log service. Any other utility programs that you run that access the Event log are likely also to have opened the PSSMsg.dll file. In order to copy the latest PSSMsg.dll file, you may have to shut down the Event Log service and any other service that accesses Event Log message dlls. Make sure you restart these services after you complete the file copy successfully.
Please do not agonize over the fact that your script cannot replace the PSSMsg.dll file because it is in use. It is not the end of the world to run the most current collection service with a slightly out-of-date Event Log Message dll.
Optional runtime files. Diagnostic symbols are no longer included in the program’s binary executables like DMPerfss.exe and DTSFnd.dll due to Microsoft compiler changes. Diagnostic symbols are now found in filenames ending with a .pdb suffix. Installing these debug symbol files is optional, but highly recommended so that we can maintain the high quality of the collection service code.
Installing the enclosed version of PKZIP25.exe is also optional.
The runtime files can be found in the Program FilesNTSMF31 folder following the installation of the collection service following setup, or in the folder Program FilesPerformance SentryCollection Sevice Files following the installation of Performance Sentry Administration component.
The third setup routine is for Performance Sentry Portal and Performance Database. The Performance Database is a Microsoft SQL Server based database and the Performance Sentry Portal is an ASP.NET graphical interface to the database.