;NOTE: A few entries below are only supported in the coming v4.0 or newer ; ;The following shows the values that you can override, and the default values that ;are used if you don't override it (ie if you simply remove the line, or keep the ;line unchanged, the value shown is what will be used ; ;The lines beginning with ; are comments and can be completely removed (if you don't ;want to give your customers these same hints) ; ;This file needs to be in the same directory as the Console.exe program ; ;Most of these parameters REQUIRE a value. Only a few (they are mentioned) can ;be set to a blank value [Settings] APPNAME=PA Server Monitor ;The following two entries are how the application shows up in the Windows Service Control Manager ;To be safe, don't use any 'special' characters (ie stick to letters, numbers and space) ;To make these settings 'take', you need to re-register the service. To do this, stop the service and ;run "servermonsvc.exe -i". ;The ServiceName parameter will also be the name of the Event Source for any events written to the event log ServiceName=PA Server Monitor ServiceDescription=PA Server Monitor is a configurable service that can watch for many server health events and actively alert you or run actions to fix problems that are detected. ;The AlertFooter is shown at the bottom of most alerts (email, message boxes, etc) that go out. ;You can include the standard expansion variables. An example is show below ;AlertFooter=Would you like help with this issue? Call us at 800-HELP-ME. Version=$ProdVer$ AlertFooter=\r\n\r\n\r\nAlert created with PA Server Monitor $PRODWEB$ ;DefaultSettingsUrl is now obsolete and ignored. If it DOES exist, update checks will NOT happen just ;to make sure your customers don't receive an update message from us ;UpdateCheckURL is called as follows: ;?VER=&D=&S=&DS= where: ; = the version installed (ie 3.5.0.120) - this helps you determine whether an update exists or not ;The following three values are for aggregate statistical purposes ; = 1 if running on an demo (trial) license, 0 if using a non-demo license ; = number of servers/devices being monitored ; = number of days until next check (defaults to 30) ;Note that the above is useful for aggregated stats, but does not expose any information about the customer, their license or anything else that ;would compromise their privacy. ;The response should contain text inside of MSG tags (ie There is an update available. Please contact us...) ;It should also contain an UPDATE value of U, N, or M (ie N). ;U = update available, send MSG value to any email accounts configured to receive update notifications ;N = no updates available, do NOT send MSG value (MSG value could be empty in this case) ;M = no updates available, but send MSG anyway (maybe for a version-specific message, or a global message for everyone) ;So some possible responses: ;No updates availableN ;Version 3.6 has been released. Please ... U ;We are looking for users with over 100 servers for a survey...M ;To disable automatic update checks, set UpdateCheckURL to blank, ie: UpdateCheckURL= UpdateCheckURL=http://www.poweradmin.com/servermonitor/updatecheck.aspx ;The Settings dialog has a link next to the UpdateCheck that explains what information is passed in an update check and how privacy is maintained ;You can override where that link goes: UpdateCheckPrivacyPage=http://www.poweradmin.com/help/updateCheckPrivacy.aspx ;Customer visible in various areas of the product DefaultProductUrl=http://www.poweradmin.com/servermonitor ;Customer visible in the About Box SocialLink1=Twitter: http://twitter.com/poweradmn SocialLink2=Google+: http://goo.gl/PYVj2 SocialLink3= ;Customer visible in the AboutBox DefaultFeedbackURL=http://www.poweradmin.com/contact.aspx ;URL used from the Licensing screen to purchase more licenses OrderURL=http://www.poweradmin.com/order.aspx ;Help button or pressing F1 opens this URL HelpURL=http://www.poweradmin.com/help/SM_3_7 ;Hints in the reports that fail to get WMI data will link to this URL if not disabled in Settings->Report Settings EnableWMIURL=http://www.poweradmin.com/Help/EnableWMI.aspx ;Hint for using self-signed certificates SSLHintURL=http://www.poweradmin.com/help/SSLHints/ ;Hint page for setting up SMS alerts SMSHintURL=http://www.poweradmin.com/help/SMSHints.aspx ;Hint for entering server credentials DefaultServerCredsDocURL=http://www.poweradmin.com/Help/SM_3_7/config_adding_computers.aspx ;These show up in error messages and in the About Box DefaultCustomerSupportEmail=support@poweradmin.com DefaultCustomerSupportPhone= DefaultCustomerSupportWebSite=http://www.poweradmin.com/servermonitor/index.aspx ;URL that is linked to when adding computers DefaultRemoteMonitoringHintURL=http://www.poweradmin.com/help/remotemonitoringhints.aspx ;Default title of alerts DefaultActionSubject=Alert from $Machine$ ;The branding graphic needs to be a Windows .bmp file that is 36 pixels high and 1700 pixels ;wide (to handle WIDE screens). The file needs to be in the same directory as the Console.exe program ;For example: BrandingGraphic=mycompanybrand.bmp BrandingGraphic=ExampleBrandingBitmap.bmp ;Reports are brandable by changing the templates they are built from. The templates are in ;C:\Program Files\PA Server Monitor\Reports\Shared and are named PA_Report....html ;If the file is missing, it will be replaced. If the file is modified in anyway, it will be left alone