K
Kenji Yamamoto [Security]
Hi. As I have checked the stuff and noticed that it would
be great if the future release has enhancements concerning
event logging.
1. Event logging in general: Provide more ways to handle.
Currently it is difficult for us sysadmins to even check
the log generated with this tool, in a centralized manner.
a. Write to event log (application, system, or security
log)
This is a must thing when we deploy in business
environments.
It is difficult for us sysadmins to check each node via
console.
If an event entry is written to Eventlogs, we can control
as we like, as we can use various and many implementations
like WMI, LogParser, eventtrigger, and so on which are
either implemented within the base OS or retrieve via web.
b. Write to some text logs
It would also be cool to have text logs under %systemroot%
\system32\LogFiles\ in a fixed and standard format, say,
W3C, CSV, TSV, and so on.
This way too, we can handle things with what we have.
2. Centralized deployment: Provide MSI binary.
Please provide MSI binary for us sysadmins to deploy in
several ways. For example:
A. Advertize in Active Directory
B. Unattend installation during OS installation before the
initial reboot
3. Group policy template, COM objects, and command line:
Give us ways to centrally control
This means that we want ways to centrally manage, or if it
is not just possible, ways to automate the config and
manage tasks.
4. Central management console
This is either Group policy, or centralized web-based
console like CiscoWorks.
This way we admins can manage things in a detailed and yet
centralized manner.
5. Add the tool itself or the category "Anti-Spyware" in
Security Center applet.
This way we can manage our own PC's security in more
unified manner.
Anyone? Comment? Pls let me see what we users feel, like,
dislike.
Regards,
Kenji Yamamoto [Japanese MVP]
be great if the future release has enhancements concerning
event logging.
1. Event logging in general: Provide more ways to handle.
Currently it is difficult for us sysadmins to even check
the log generated with this tool, in a centralized manner.
a. Write to event log (application, system, or security
log)
This is a must thing when we deploy in business
environments.
It is difficult for us sysadmins to check each node via
console.
If an event entry is written to Eventlogs, we can control
as we like, as we can use various and many implementations
like WMI, LogParser, eventtrigger, and so on which are
either implemented within the base OS or retrieve via web.
b. Write to some text logs
It would also be cool to have text logs under %systemroot%
\system32\LogFiles\ in a fixed and standard format, say,
W3C, CSV, TSV, and so on.
This way too, we can handle things with what we have.
2. Centralized deployment: Provide MSI binary.
Please provide MSI binary for us sysadmins to deploy in
several ways. For example:
A. Advertize in Active Directory
B. Unattend installation during OS installation before the
initial reboot
3. Group policy template, COM objects, and command line:
Give us ways to centrally control
This means that we want ways to centrally manage, or if it
is not just possible, ways to automate the config and
manage tasks.
4. Central management console
This is either Group policy, or centralized web-based
console like CiscoWorks.
This way we admins can manage things in a detailed and yet
centralized manner.
5. Add the tool itself or the category "Anti-Spyware" in
Security Center applet.
This way we can manage our own PC's security in more
unified manner.
Anyone? Comment? Pls let me see what we users feel, like,
dislike.
Regards,
Kenji Yamamoto [Japanese MVP]