Ask the Community
Groups
Discovering Windows services that are set to Manual or are currently Stopped - Connect IT Community | Kaseya
<main> <article class="userContent"> <p><strong>QUESTION</strong></p> <p>How to discover tests for Windows Services that are not set to startup automatically?</p> <p> </p> <p><strong>RESOLUTION</strong></p> <p>By default, Traverse will only discover Windows services that are running at the time of test discovery and the service Startup Type is Auto. Occasionally though, you may want to discover/provision Windows services that are running but the Startup Type is manual. Or, the service may be stopped at the time the discovery is running.</p> <p>The attached files, to be put under <TRAVERSE_HOME>\plugin\monitors on the BVE will enable you to discover/provision such services as described here <a href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fkaseya.zendesk.com%2Fentries%2F85588076-Deploying-a-new-device-or-application-signature">https://kaseya.zendesk.com/entries/85588076-Deploying-a-new-device-or-application-signature</a></p> <p>Bear in mind though that you may have a large number of services now that are discovered - but are always Critical because they are either not running, or, they were running at the time of discovery - but since they are Manual - on a server reboot they may have stopped running. If possible, deploy these signatures when discovering tests on specific Windows servers and remove the files from <TRAVERSE_HOME>\plugin\monitors when done.</p> <p> </p> <p><strong>APPLIES TO </strong></p> <p>All versions of Traverse.</p> <p> </p> <p><strong>REFERENCE</strong></p> <p>None.</p> </article> </main>