You can create a component template with a compliance rule that checks this.
1. Create a component template.
2. Add "Services" as a part
3. Create a compliance rule:
Service * Must Exist AND (Account Name = "NT AUTHORITY\LocalService")
4. Create and execute a discovery job against windows servers
5. Create and execute a compliance job against windows servers
thank you, it worked flawlessy
is it possible to execute the compliance job using as target some servers without first running the discovery job (which always returns true)?
and to complete our audit on username usage, how can we audit scheduled tasks user?
you must run the discovery job before the compliance job if there are new systems in the environment. if there is no 'component' on the target server, compliance will fail. the 'component' is created by running the discovery job against the server, using the 'component template'
you can make a batch job that runs the discovery job, then the complaince job if you like.
i believe for scheduled tasks you will have to use an extended object.
make an extended object for windows systems, remote execution and the csv grammar.
use the following command:
cmd /c "schtasks /query /FO CSV /NH"
this should return the scheduled tasks for a 2003 system (schtasks.exe is not available on windows 2000)
thank you, it works
but the command line should be
cmd /c "schtasks /query /FO CSV /NH /V"
or else the username won't be displayed