Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 1 subscriber
  • Views 4818 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos Anti-Virus Status Reporter on Window 7

Azwan

Hello,

As per subject above does anyone have experience with this services on Windows 7, just curious as per services info "Sophos Anti-Virus Status Reporter " function Provides information to Windows Security Center on whether Sophos Anti-Virus is up to date and whether on-access scanning is enabled.

D oes sophos console unable to obtain endpoint (windows 7 ) antivirus and update status if this service disable?. Thanks

:19477


This thread was automatically locked due to age.
Parents
  • 0

    As I recall, the problem I ran into once was the .net application was unable to enumerate process that contain 15 characters if the .net application wasn't running with specific rights (it was running as just a member of users). So quite a fendemantal problem  When it hits a process with 15 characters for some reason requires at a minimum seDebugPriveldges to resolve the process name as it gets it using a different method at this point which requires more rights.

    Could you try granting the user for which the .net application is failing, the following right:
    Security Settings - Local Policies - User Rights Assignment - "Debug programs"

    Does the applicaiton then work?   This could be a possible workaround at least for the shortterm, albeit it a potential security risk as it would alow non admins the ability to attach to processes, view memory I guess.

    I would contact the .net application vendor and see if they can fix up their application in some way, I wouldn't suggest you stop the SAVAdmin service as a workaround unless you have to.

    Jak

    :19601
Reply
  • 0

    As I recall, the problem I ran into once was the .net application was unable to enumerate process that contain 15 characters if the .net application wasn't running with specific rights (it was running as just a member of users). So quite a fendemantal problem  When it hits a process with 15 characters for some reason requires at a minimum seDebugPriveldges to resolve the process name as it gets it using a different method at this point which requires more rights.

    Could you try granting the user for which the .net application is failing, the following right:
    Security Settings - Local Policies - User Rights Assignment - "Debug programs"

    Does the applicaiton then work?   This could be a possible workaround at least for the shortterm, albeit it a potential security risk as it would alow non admins the ability to attach to processes, view memory I guess.

    I would contact the .net application vendor and see if they can fix up their application in some way, I wouldn't suggest you stop the SAVAdmin service as a workaround unless you have to.

    Jak

    :19601
Children
No Data