This document applies to LANDesk Management Suite 9.0 SP3
Description
Previous to LDMS 9.0 SP3 the software distribution status was sent from the client to the core by way of PostCGI.exe which wrote the status to the LDMain\SDStatus.
Problem
PostCGI.exe was not scaleable like other web processes such as WSVulnerabilitycore.asmx.
WSVulnerabilitycore uses the LDAppVulnerability application pool. As an application pool, additional worker processes can be added which increases the amount of requests the service can handle.
Change Made in LDMS 9.0 SP3
In Service Pack 3 the software distribution status coming from the client will be processed by WSVulnerability.
Possible Action Required
Monitor the IIS log. If wsvulnerabilitycore.asmx requests are recieving 503 errors, increase the number of work processes assigned to the LDAppVulnerability applicaiton pool.
Entries for vulcore.asmx with a 50x error like the 503 below indicates that the app pool is being overworked and increasing the worker processes may be benificial.
2011-12-13 23:57:48 192.168.0.5 POST /WSVulnerabilityCore/VulCore.asmx - 80 - 192.168.0.24 Microsoft-ATL-Native/9.00 503 0 0 3388
To increase the worker processes in IIS7 (Windows 2008 R2 cores)
Open IIS Manager
Expand server
Click on Application Pool
Right-click LDAppVulnerability
Click Advance Settings
Change the Maximum Worker Process.
Recommended Max number of worker processes is the number of processor cores on the server minus 1.
If you think you need to increase the number of worker processes, start with 2 to 4. Usually that is enough.