Re: Trend CSM for SMB 3.0 causing MAJOR server issues

a.. Desktop Security

b.. Normal - allows end users read/write access to the Client/Server
Security Agent folders, files, and registries.

c.. High - restricts end users from accessing Client/Server Security
Agent folders, files, and registries.

If you select High, the access permissions settings of the Client/Server
Security Agent folders, files, and registries is inherited from the WINNT
file (for Client computers running Windows NT) or from the Program Files
folder (for Client computers running Windows 2000/XP/Server 2003).

Therefore, if the permissions settings (Security settings in Windows) of the
WINNT file or Program Files folder are set to allow full read/write access,
selecting High still allows clients full read/write access to the
Client/Server Security Agent folders, files, and registries.



--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius


"Jason Jordan" <> wrote in message
news: ups.com...
> Hi,
>
> Has anyone else seen Trend CSM for SMB 3.0 cause major issues on a
> server?
>
> I'm seeing hundreds of Event ID: 333 - failure to write back to the
> registry.... essentially the server is non-functional.
>
> If I completely remove EVERYthing to do with Trend all the problems
> disappear.
>
> I used the Trend KB to remove even the settings from the registry and
> after multiple reboots the server was fine. After reinstalling 3.0, it
> all went bad again.
>
> At this point we've spent some 20 hours trying to track this down for
> the client. As we can't leave them with no AV - I'm about to pull the
> plug on Trend altogether and go with another vendor.
>
> Trend haven't responded to any emails (apparently 7 day support) and
> phone calls go to an answering machine. (This is Australia and
> apparently viruses only attack here during business hours).
>
> It's a shame as we have another 25 sites we've sold the solution to,
> but at this point I think we'll be advising them to go to another
> product on renewal as well.
>
> I can't risk this non-contactability again.
>
> Cheers, Jason
>