Some solutions still have debug-mode compiling enabled in their related web.config files. Debug-mode compiling can cause performance problems for any ASP.NET application. In particular, the following debug-mode behaviors impact Notification Server performance:
Additional information about debug mode is available at ScottGu's Blog
Note: The Altiris Notification Server 6.x utilizes ASP.NET 1.1. If you're using Notification Server 7.x, you can configure this for all applications in a single config by changing the the machine.config to use the following setting. A tool for 7.x is also attached to this article.
Make the following modification to each web.config file that is part of the Altiris installation (\Program Files\Altiris). The change will be implemented as soon as another request to the related page occurs. In most cases, this will involve a visit to the related configuration or task Notification Server console page.
From a command line, execute the attached utility (DisableWebDebug.exe). It must be copied to the local file system on the Notification Server to meet .NET security requirements. All output will be sent to the console window, and important items will also be sent to the Notification Server log. Any modified web.config file will first be duplicated as "config.original" in the same folder. The utility offers two modes.
To perform a check to see which web.config files will be modified, use the following command:
To update the web.config files, use the following command:
By default, the utility will check the registry for the primary Notification Server installation directory, such as C:\Program Files\Altiris. If necessary, a second parameter can be used to specify an alternate search path as depicted below:
DisableWebDebug -fix "H:\Altiris2"
It is not necessary to restart any services, automatic recompilation will occur upon the next related Web page request.
For some other specific applications of this, see article 25655.