|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
I've been emailing and calling Trend Micro support for several days now
about an issue where the server's TM Client is failing to update it's
pattern definitions. All the client workstations update automatically, the
Exchange messaging agent updates automatically, but the TM Client on the
server fails to update either automatically or manually. A manual update
concludes with "Update Succeeded", but the pattern stays at the old version.
I'm on the phone again now, with someone who's English is pretty poor. He
asked me to wait while he read the correspondence and phone logs, then
proceeded to ask me questions clearly answered in the original service
request and again in each email and phone call.
I've received several solutions by phone and email, but they're always for
the wrong problem, not for the issue I'm having. I got a solution for when
the Exchange messaging agent fails to update, but I wrote that the messaging
agent IS updating. Then I got a solution for the server failing to retrieve
the updated pattern from TM, but I wrote that auto updates are working for
everything except the TM Client on the server. Email only gets answered
after 2 days, if at all.
Does anyone have any suggestions either for my current problem or how to get
through to knowledgeable TM support?
Thanks, Paul Shapiro
|
|
I'm working w/ Trend on the same issue. No solution yet.
The problem on my server started about one week ago and I have had to
manually unload the client and then reload it for the update to take.
MikeMc
"Paul Shapiro" <paul[ at ]hideme.broadwayData.com> wrote in message
news:%23QKa6s0vHHA.4640[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text] > I've been emailing and calling Trend Micro support for several days now
> about an issue where the server's TM Client is failing to update it's
> pattern definitions. All the client workstations update automatically, the
> Exchange messaging agent updates automatically, but the TM Client on the
> server fails to update either automatically or manually. A manual update
> concludes with "Update Succeeded", but the pattern stays at the old
> version.
>
> I'm on the phone again now, with someone who's English is pretty poor. He
> asked me to wait while he read the correspondence and phone logs, then
> proceeded to ask me questions clearly answered in the original service
> request and again in each email and phone call.
>
> I've received several solutions by phone and email, but they're always for
> the wrong problem, not for the issue I'm having. I got a solution for when
> the Exchange messaging agent fails to update, but I wrote that the
> messaging agent IS updating. Then I got a solution for the server failing
> to retrieve the updated pattern from TM, but I wrote that auto updates are
> working for everything except the TM Client on the server. Email only gets
> answered after 2 days, if at all.
>
> Does anyone have any suggestions either for my current problem or how to
> get through to knowledgeable TM support?
>
> Thanks, Paul Shapiro
>
|
|
Same solution works here, and the problem started about the same time. Hmmm.
I tried uninstalling the TM Client, rebooting and reinstalling. Same
behavior- no change at all.
"SMC" <mmcelrath[ at ]earthlink.net> wrote in message
news:u1bxbQ2vHHA.2040[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text] > I'm working w/ Trend on the same issue. No solution yet. > > The problem on my server started about one week ago and I have had to > manually unload the client and then reload it for the update to take. > > MikeMc > > "Paul Shapiro" <paul[ at ]hideme.broadwayData.com> wrote in message > news:%23QKa6s0vHHA.4640[ at ]TK2MSFTNGP03.phx.gbl... >> I've been emailing and calling Trend Micro support for several days now >> about an issue where the server's TM Client is failing to update it's >> pattern definitions. All the client workstations update automatically, >> the Exchange messaging agent updates automatically, but the TM Client on >> the server fails to update either automatically or manually. A manual >> update concludes with "Update Succeeded", but the pattern stays at the >> old version. >> >> I'm on the phone again now, with someone who's English is pretty poor. He >> asked me to wait while he read the correspondence and phone logs, then >> proceeded to ask me questions clearly answered in the original service >> request and again in each email and phone call. >> >> I've received several solutions by phone and email, but they're always >> for the wrong problem, not for the issue I'm having. I got a solution for >> when the Exchange messaging agent fails to update, but I wrote that the >> messaging agent IS updating. Then I got a solution for the server failing >> to retrieve the updated pattern from TM, but I wrote that auto updates >> are working for everything except the TM Client on the server. Email only >> gets answered after 2 days, if at all. >> >> Does anyone have any suggestions either for my current problem or how to >> get through to knowledgeable TM support?
|
|
Do you have the login script in there that makes the clients install the
software? If so take it out.
http://msmvps.com/blogs/cgross/archive/2007/04/27/unexpected-behavior-with-autopcc-in-trend-c-s-m-3-6.aspx
Paul Shapiro wrote:
[Quoted Text] > Same solution works here, and the problem started about the same time. Hmmm. > I tried uninstalling the TM Client, rebooting and reinstalling. Same > behavior- no change at all. > > "SMC" <mmcelrath[ at ]earthlink.net> wrote in message > news:u1bxbQ2vHHA.2040[ at ]TK2MSFTNGP03.phx.gbl... >> I'm working w/ Trend on the same issue. No solution yet. >> >> The problem on my server started about one week ago and I have had to >> manually unload the client and then reload it for the update to take. >> >> MikeMc >> >> "Paul Shapiro" <paul[ at ]hideme.broadwayData.com> wrote in message >> news:%23QKa6s0vHHA.4640[ at ]TK2MSFTNGP03.phx.gbl... >>> I've been emailing and calling Trend Micro support for several days now >>> about an issue where the server's TM Client is failing to update it's >>> pattern definitions. All the client workstations update automatically, >>> the Exchange messaging agent updates automatically, but the TM Client on >>> the server fails to update either automatically or manually. A manual >>> update concludes with "Update Succeeded", but the pattern stays at the >>> old version. >>> >>> I'm on the phone again now, with someone who's English is pretty poor. He >>> asked me to wait while he read the correspondence and phone logs, then >>> proceeded to ask me questions clearly answered in the original service >>> request and again in each email and phone call. >>> >>> I've received several solutions by phone and email, but they're always >>> for the wrong problem, not for the issue I'm having. I got a solution for >>> when the Exchange messaging agent fails to update, but I wrote that the >>> messaging agent IS updating. Then I got a solution for the server failing >>> to retrieve the updated pattern from TM, but I wrote that auto updates >>> are working for everything except the TM Client on the server. Email only >>> gets answered after 2 days, if at all. >>> >>> Does anyone have any suggestions either for my current problem or how to >>> get through to knowledgeable TM support? > > |
|
Hello!
My virus patterns are all working fine on servers, workstations, and
Exchange, but the virus scan engine was old up until a couple days ago. I do
not run the autopcc script once the clients are installed, so maybe I got
lucky.
While we are on the "Trend not updating" subject, has anyone noticed that
the virus engine does not get updated to the same version that can be
downloaded manually? It is set to do so in the Security Dashboard, but it
was not updating the scan engine a week ago when the Update Center had a
newer version..
I emailed Trend's tech support about it and never got a response. I just
checked my servers and clients' servers, and it is updated now.
Trend CSMS for SMB 3.6 build 1095.
Scan engine 8.500.1002 (was at 8.320.1004 even when Update Center had
8.500.1002)
Virus pattern 4.585.00
BTW, watch out for phishing emails getting through the filter. Yes, it is
checked to detect, but I have had at least 8 come through undetected.
Gregg Hill
"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa[ at ]pacbell.net>
wrote in message news:468DE5B1.50902[ at ]pacbell.net...
[Quoted Text] > Do you have the login script in there that makes the clients install the > software? If so take it out. > > http://msmvps.com/blogs/cgross/archive/2007/04/27/unexpected-behavior-with-autopcc-in-trend-c-s-m-3-6.aspx> > Paul Shapiro wrote: >> Same solution works here, and the problem started about the same time. >> Hmmm. I tried uninstalling the TM Client, rebooting and reinstalling. >> Same behavior- no change at all. >> >> "SMC" <mmcelrath[ at ]earthlink.net> wrote in message >> news:u1bxbQ2vHHA.2040[ at ]TK2MSFTNGP03.phx.gbl... >>> I'm working w/ Trend on the same issue. No solution yet. >>> >>> The problem on my server started about one week ago and I have had to >>> manually unload the client and then reload it for the update to take. >>> >>> MikeMc >>> >>> "Paul Shapiro" <paul[ at ]hideme.broadwayData.com> wrote in message >>> news:%23QKa6s0vHHA.4640[ at ]TK2MSFTNGP03.phx.gbl... >>>> I've been emailing and calling Trend Micro support for several days now >>>> about an issue where the server's TM Client is failing to update it's >>>> pattern definitions. All the client workstations update automatically, >>>> the Exchange messaging agent updates automatically, but the TM Client >>>> on the server fails to update either automatically or manually. A >>>> manual update concludes with "Update Succeeded", but the pattern stays >>>> at the old version. >>>> >>>> I'm on the phone again now, with someone who's English is pretty poor. >>>> He asked me to wait while he read the correspondence and phone logs, >>>> then proceeded to ask me questions clearly answered in the original >>>> service request and again in each email and phone call. >>>> >>>> I've received several solutions by phone and email, but they're always >>>> for the wrong problem, not for the issue I'm having. I got a solution >>>> for when the Exchange messaging agent fails to update, but I wrote that >>>> the messaging agent IS updating. Then I got a solution for the server >>>> failing to retrieve the updated pattern from TM, but I wrote that auto >>>> updates are working for everything except the TM Client on the server. >>>> Email only gets answered after 2 days, if at all. >>>> >>>> Does anyone have any suggestions either for my current problem or how >>>> to get through to knowledgeable TM support? >>
|
|
No, I use IE to deploy clients.
MikeMc
"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa[ at ]pacbell.net>
wrote in message news:468DE5B1.50902[ at ]pacbell.net...
[Quoted Text] > Do you have the login script in there that makes the clients install the > software? If so take it out. > > http://msmvps.com/blogs/cgross/archive/2007/04/27/unexpected-behavior-with-autopcc-in-trend-c-s-m-3-6.aspx> > Paul Shapiro wrote: >> Same solution works here, and the problem started about the same time. >> Hmmm. I tried uninstalling the TM Client, rebooting and reinstalling. >> Same behavior- no change at all. >> >> "SMC" <mmcelrath[ at ]earthlink.net> wrote in message >> news:u1bxbQ2vHHA.2040[ at ]TK2MSFTNGP03.phx.gbl... >>> I'm working w/ Trend on the same issue. No solution yet. >>> >>> The problem on my server started about one week ago and I have had to >>> manually unload the client and then reload it for the update to take. >>> >>> MikeMc >>> >>> "Paul Shapiro" <paul[ at ]hideme.broadwayData.com> wrote in message >>> news:%23QKa6s0vHHA.4640[ at ]TK2MSFTNGP03.phx.gbl... >>>> I've been emailing and calling Trend Micro support for several days now >>>> about an issue where the server's TM Client is failing to update it's >>>> pattern definitions. All the client workstations update automatically, >>>> the Exchange messaging agent updates automatically, but the TM Client >>>> on the server fails to update either automatically or manually. A >>>> manual update concludes with "Update Succeeded", but the pattern stays >>>> at the old version. >>>> >>>> I'm on the phone again now, with someone who's English is pretty poor. >>>> He asked me to wait while he read the correspondence and phone logs, >>>> then proceeded to ask me questions clearly answered in the original >>>> service request and again in each email and phone call. >>>> >>>> I've received several solutions by phone and email, but they're always >>>> for the wrong problem, not for the issue I'm having. I got a solution >>>> for when the Exchange messaging agent fails to update, but I wrote that >>>> the messaging agent IS updating. Then I got a solution for the server >>>> failing to retrieve the updated pattern from TM, but I wrote that auto >>>> updates are working for everything except the TM Client on the server. >>>> Email only gets answered after 2 days, if at all. >>>> >>>> Does anyone have any suggestions either for my current problem or how >>>> to get through to knowledgeable TM support? >>
|
|
Did exactly the same thing. Now, as of this morning, I have another Win2003
server that's not getting the latest pattern file (4.585). I have another
Win2003 server that is outside of the domain on a DMZ that did get its
pattern file update however.
It's probably not related, but I did add my first Vista test machine w/
Trend to the network about the time I started having problems.
MikeMc
"Paul Shapiro" <paul[ at ]hideme.broadwayData.com> wrote in message
news:%23GT46H4vHHA.1212[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text] > Same solution works here, and the problem started about the same time. > Hmmm. I tried uninstalling the TM Client, rebooting and reinstalling. Same > behavior- no change at all. > > "SMC" <mmcelrath[ at ]earthlink.net> wrote in message > news:u1bxbQ2vHHA.2040[ at ]TK2MSFTNGP03.phx.gbl... >> I'm working w/ Trend on the same issue. No solution yet. >> >> The problem on my server started about one week ago and I have had to >> manually unload the client and then reload it for the update to take. >> >> MikeMc >> >> "Paul Shapiro" <paul[ at ]hideme.broadwayData.com> wrote in message >> news:%23QKa6s0vHHA.4640[ at ]TK2MSFTNGP03.phx.gbl... >>> I've been emailing and calling Trend Micro support for several days now >>> about an issue where the server's TM Client is failing to update it's >>> pattern definitions. All the client workstations update automatically, >>> the Exchange messaging agent updates automatically, but the TM Client on >>> the server fails to update either automatically or manually. A manual >>> update concludes with "Update Succeeded", but the pattern stays at the >>> old version. >>> >>> I'm on the phone again now, with someone who's English is pretty poor. >>> He asked me to wait while he read the correspondence and phone logs, >>> then proceeded to ask me questions clearly answered in the original >>> service request and again in each email and phone call. >>> >>> I've received several solutions by phone and email, but they're always >>> for the wrong problem, not for the issue I'm having. I got a solution >>> for when the Exchange messaging agent fails to update, but I wrote that >>> the messaging agent IS updating. Then I got a solution for the server >>> failing to retrieve the updated pattern from TM, but I wrote that auto >>> updates are working for everything except the TM Client on the server. >>> Email only gets answered after 2 days, if at all. >>> >>> Does anyone have any suggestions either for my current problem or how to >>> get through to knowledgeable TM support? > >
|
|
I manage three seperate SBS 2003 R2 installations with Trend CSM 3.5 on all.
I have had the same problem on all of them for about a week.
One of the clients also has a Server 2003 file server and the pattern file
does not update on that server as well. All Win XP Pro clients update fine.
I also found that if I stop and restart the Client/Server Security Agent
service, then it will update to the newest pattern file. Once a new pattern
file is released though, I need start/restart service again.
"Paul Shapiro" wrote:
[Quoted Text] > Same solution works here, and the problem started about the same time. Hmmm. > I tried uninstalling the TM Client, rebooting and reinstalling. Same > behavior- no change at all. > > "SMC" <mmcelrath[ at ]earthlink.net> wrote in message > news:u1bxbQ2vHHA.2040[ at ]TK2MSFTNGP03.phx.gbl... > > I'm working w/ Trend on the same issue. No solution yet. > > > > The problem on my server started about one week ago and I have had to > > manually unload the client and then reload it for the update to take. > > > > MikeMc > > > > "Paul Shapiro" <paul[ at ]hideme.broadwayData.com> wrote in message > > news:%23QKa6s0vHHA.4640[ at ]TK2MSFTNGP03.phx.gbl... > >> I've been emailing and calling Trend Micro support for several days now > >> about an issue where the server's TM Client is failing to update it's > >> pattern definitions. All the client workstations update automatically, > >> the Exchange messaging agent updates automatically, but the TM Client on > >> the server fails to update either automatically or manually. A manual > >> update concludes with "Update Succeeded", but the pattern stays at the > >> old version. > >> > >> I'm on the phone again now, with someone who's English is pretty poor. He > >> asked me to wait while he read the correspondence and phone logs, then > >> proceeded to ask me questions clearly answered in the original service > >> request and again in each email and phone call. > >> > >> I've received several solutions by phone and email, but they're always > >> for the wrong problem, not for the issue I'm having. I got a solution for > >> when the Exchange messaging agent fails to update, but I wrote that the > >> messaging agent IS updating. Then I got a solution for the server failing > >> to retrieve the updated pattern from TM, but I wrote that auto updates > >> are working for everything except the TM Client on the server. Email only > >> gets answered after 2 days, if at all. > >> > >> Does anyone have any suggestions either for my current problem or how to > >> get through to knowledgeable TM support? > > > |
|
Which one of the Client Security Agent Services?
"jrieszer" <jrieszer[ at ]discussions.microsoft.com> wrote in message
news:57790D52-EC7D-4F39-B6EF-3ED24DE46711[ at ]microsoft.com...
[Quoted Text] >I manage three seperate SBS 2003 R2 installations with Trend CSM 3.5 on >all. > I have had the same problem on all of them for about a week. > > One of the clients also has a Server 2003 file server and the pattern file > does not update on that server as well. All Win XP Pro clients update > fine. > > I also found that if I stop and restart the Client/Server Security Agent > service, then it will update to the newest pattern file. Once a new > pattern > file is released though, I need start/restart service again. > > "Paul Shapiro" wrote: > >> Same solution works here, and the problem started about the same time. >> Hmmm. >> I tried uninstalling the TM Client, rebooting and reinstalling. Same >> behavior- no change at all. >> >> "SMC" <mmcelrath[ at ]earthlink.net> wrote in message >> news:u1bxbQ2vHHA.2040[ at ]TK2MSFTNGP03.phx.gbl... >> > I'm working w/ Trend on the same issue. No solution yet. >> > >> > The problem on my server started about one week ago and I have had to >> > manually unload the client and then reload it for the update to take. >> > >> > MikeMc >> > >> > "Paul Shapiro" <paul[ at ]hideme.broadwayData.com> wrote in message >> > news:%23QKa6s0vHHA.4640[ at ]TK2MSFTNGP03.phx.gbl... >> >> I've been emailing and calling Trend Micro support for several days >> >> now >> >> about an issue where the server's TM Client is failing to update it's >> >> pattern definitions. All the client workstations update automatically, >> >> the Exchange messaging agent updates automatically, but the TM Client >> >> on >> >> the server fails to update either automatically or manually. A manual >> >> update concludes with "Update Succeeded", but the pattern stays at the >> >> old version. >> >> >> >> I'm on the phone again now, with someone who's English is pretty poor. >> >> He >> >> asked me to wait while he read the correspondence and phone logs, then >> >> proceeded to ask me questions clearly answered in the original service >> >> request and again in each email and phone call. >> >> >> >> I've received several solutions by phone and email, but they're always >> >> for the wrong problem, not for the issue I'm having. I got a solution >> >> for >> >> when the Exchange messaging agent fails to update, but I wrote that >> >> the >> >> messaging agent IS updating. Then I got a solution for the server >> >> failing >> >> to retrieve the updated pattern from TM, but I wrote that auto updates >> >> are working for everything except the TM Client on the server. Email >> >> only >> >> gets answered after 2 days, if at all. >> >> >> >> Does anyone have any suggestions either for my current problem or how >> >> to >> >> get through to knowledgeable TM support? >> >> >>
|
|
I have SBS 2003 R2 with Trend CSM 3.6 and the problem started for me just
over a week ago. I did manage to update the pattern file by rebooting the
server but since that time it hasn't updated again. At least now I know I'm
not the only one with this problem.
I've only had to deal with their support once before, on a licensing issue.
In that case they resolved the problem in less than 24 hours. If only they
could resolve this one as quickly . . .
BrianY
"jrieszer" wrote:
[Quoted Text] > I manage three seperate SBS 2003 R2 installations with Trend CSM 3.5 on all. > I have had the same problem on all of them for about a week. > > One of the clients also has a Server 2003 file server and the pattern file > does not update on that server as well. All Win XP Pro clients update fine. > > I also found that if I stop and restart the Client/Server Security Agent > service, then it will update to the newest pattern file. Once a new pattern > file is released though, I need start/restart service again. > > "Paul Shapiro" wrote: > > > Same solution works here, and the problem started about the same time. Hmmm. > > I tried uninstalling the TM Client, rebooting and reinstalling. Same > > behavior- no change at all. > > > > "SMC" <mmcelrath[ at ]earthlink.net> wrote in message > > news:u1bxbQ2vHHA.2040[ at ]TK2MSFTNGP03.phx.gbl... > > > I'm working w/ Trend on the same issue. No solution yet. > > > > > > The problem on my server started about one week ago and I have had to > > > manually unload the client and then reload it for the update to take. > > > > > > MikeMc > > > > > > "Paul Shapiro" <paul[ at ]hideme.broadwayData.com> wrote in message > > > news:%23QKa6s0vHHA.4640[ at ]TK2MSFTNGP03.phx.gbl... > > >> I've been emailing and calling Trend Micro support for several days now > > >> about an issue where the server's TM Client is failing to update it's > > >> pattern definitions. All the client workstations update automatically, > > >> the Exchange messaging agent updates automatically, but the TM Client on > > >> the server fails to update either automatically or manually. A manual > > >> update concludes with "Update Succeeded", but the pattern stays at the > > >> old version. > > >> > > >> I'm on the phone again now, with someone who's English is pretty poor. He > > >> asked me to wait while he read the correspondence and phone logs, then > > >> proceeded to ask me questions clearly answered in the original service > > >> request and again in each email and phone call. > > >> > > >> I've received several solutions by phone and email, but they're always > > >> for the wrong problem, not for the issue I'm having. I got a solution for > > >> when the Exchange messaging agent fails to update, but I wrote that the > > >> messaging agent IS updating. Then I got a solution for the server failing > > >> to retrieve the updated pattern from TM, but I wrote that auto updates > > >> are working for everything except the TM Client on the server. Email only > > >> gets answered after 2 days, if at all. > > >> > > >> Does anyone have any suggestions either for my current problem or how to > > >> get through to knowledgeable TM support? > > > > > > |
|
Unloading the Client (right-click the system tray icon and choose Unload)
and restarting it seems to update the patterns for me. Still not a great
solution, but quicker than rebooting. Yesterday's insight from TM support
was a suggestion to browse their support web, which I had already done. I
got nowhere with my request for an elevation to higher-level support.
"BrianY" <BrianY[ at ]discussions.microsoft.com> wrote in message
news:DF021C9F-E271-4283-8F7B-29462B8A8062[ at ]microsoft.com...
[Quoted Text] >I have SBS 2003 R2 with Trend CSM 3.6 and the problem started for me just > over a week ago. I did manage to update the pattern file by rebooting the > server but since that time it hasn't updated again. At least now I know > I'm > not the only one with this problem. > > I've only had to deal with their support once before, on a licensing > issue. > In that case they resolved the problem in less than 24 hours. If only > they > could resolve this one as quickly . . . > > BrianY > > "jrieszer" wrote: > >> I manage three seperate SBS 2003 R2 installations with Trend CSM 3.5 on >> all. >> I have had the same problem on all of them for about a week. >> >> One of the clients also has a Server 2003 file server and the pattern >> file >> does not update on that server as well. All Win XP Pro clients update >> fine. >> >> I also found that if I stop and restart the Client/Server Security Agent >> service, then it will update to the newest pattern file. Once a new >> pattern >> file is released though, I need start/restart service again. >> >> "Paul Shapiro" wrote: >> >> > Same solution works here, and the problem started about the same time. >> > Hmmm. >> > I tried uninstalling the TM Client, rebooting and reinstalling. Same >> > behavior- no change at all. >> > >> > "SMC" <mmcelrath[ at ]earthlink.net> wrote in message >> > news:u1bxbQ2vHHA.2040[ at ]TK2MSFTNGP03.phx.gbl... >> > > I'm working w/ Trend on the same issue. No solution yet. >> > > >> > > The problem on my server started about one week ago and I have had to >> > > manually unload the client and then reload it for the update to take. >> > > >> > > MikeMc >> > > >> > > "Paul Shapiro" <paul[ at ]hideme.broadwayData.com> wrote in message >> > > news:%23QKa6s0vHHA.4640[ at ]TK2MSFTNGP03.phx.gbl... >> > >> I've been emailing and calling Trend Micro support for several days >> > >> now >> > >> about an issue where the server's TM Client is failing to update >> > >> it's >> > >> pattern definitions. All the client workstations update >> > >> automatically, >> > >> the Exchange messaging agent updates automatically, but the TM >> > >> Client on >> > >> the server fails to update either automatically or manually. A >> > >> manual >> > >> update concludes with "Update Succeeded", but the pattern stays at >> > >> the >> > >> old version. >> > >> >> > >> I'm on the phone again now, with someone who's English is pretty >> > >> poor. He >> > >> asked me to wait while he read the correspondence and phone logs, >> > >> then >> > >> proceeded to ask me questions clearly answered in the original >> > >> service >> > >> request and again in each email and phone call. >> > >> >> > >> I've received several solutions by phone and email, but they're >> > >> always >> > >> for the wrong problem, not for the issue I'm having. I got a >> > >> solution for >> > >> when the Exchange messaging agent fails to update, but I wrote that >> > >> the >> > >> messaging agent IS updating. Then I got a solution for the server >> > >> failing >> > >> to retrieve the updated pattern from TM, but I wrote that auto >> > >> updates >> > >> are working for everything except the TM Client on the server. Email >> > >> only >> > >> gets answered after 2 days, if at all. >> > >> >> > >> Does anyone have any suggestions either for my current problem or >> > >> how to >> > >> get through to knowledgeable TM support? >> > >> > >> >
|
|
Regarding Trend support, I recently had a problem with phishing emails
getting to my Inbox in spite of servers being up-to-date and properly
configured. I send great detail in my messages to Trend, and I get back
basic answers written for children such as "Turn on phishing detection...."
with directions how to do so. It seems as though their tech support thinks
we are all idiots.
After their last response, I finally replied with
"Please stop treating me as though I am a complete moron. Let's just make a
few things clear so you know where to start. I am a professional network
consultant. I am a Trend Micro reseller. I have installed and configured
Trend Micro Client Server Messaging Security from version 2.0 to 3.6 on
multiple servers at multiple clients. I have a fully updated system, and so
do my clients."
I would not be expecting a whole lot out of them for support.
Gregg Hill
"news.microsoft.com" <paul.hideme[ at ]broadwayData.com> wrote in message
news:%237rk68JwHHA.3508[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text] > Unloading the Client (right-click the system tray icon and choose Unload) > and restarting it seems to update the patterns for me. Still not a great > solution, but quicker than rebooting. Yesterday's insight from TM support > was a suggestion to browse their support web, which I had already done. I > got nowhere with my request for an elevation to higher-level support. > > "BrianY" <BrianY[ at ]discussions.microsoft.com> wrote in message > news:DF021C9F-E271-4283-8F7B-29462B8A8062[ at ]microsoft.com... >>I have SBS 2003 R2 with Trend CSM 3.6 and the problem started for me just >> over a week ago. I did manage to update the pattern file by rebooting >> the >> server but since that time it hasn't updated again. At least now I know >> I'm >> not the only one with this problem. >> >> I've only had to deal with their support once before, on a licensing >> issue. >> In that case they resolved the problem in less than 24 hours. If only >> they >> could resolve this one as quickly . . . >> >> BrianY >> >> "jrieszer" wrote: >> >>> I manage three seperate SBS 2003 R2 installations with Trend CSM 3.5 on >>> all. >>> I have had the same problem on all of them for about a week. >>> >>> One of the clients also has a Server 2003 file server and the pattern >>> file >>> does not update on that server as well. All Win XP Pro clients update >>> fine. >>> >>> I also found that if I stop and restart the Client/Server Security Agent >>> service, then it will update to the newest pattern file. Once a new >>> pattern >>> file is released though, I need start/restart service again. >>> >>> "Paul Shapiro" wrote: >>> >>> > Same solution works here, and the problem started about the same time. >>> > Hmmm. >>> > I tried uninstalling the TM Client, rebooting and reinstalling. Same >>> > behavior- no change at all. >>> > >>> > "SMC" <mmcelrath[ at ]earthlink.net> wrote in message >>> > news:u1bxbQ2vHHA.2040[ at ]TK2MSFTNGP03.phx.gbl... >>> > > I'm working w/ Trend on the same issue. No solution yet. >>> > > >>> > > The problem on my server started about one week ago and I have had >>> > > to >>> > > manually unload the client and then reload it for the update to >>> > > take. >>> > > >>> > > MikeMc >>> > > >>> > > "Paul Shapiro" <paul[ at ]hideme.broadwayData.com> wrote in message >>> > > news:%23QKa6s0vHHA.4640[ at ]TK2MSFTNGP03.phx.gbl... >>> > >> I've been emailing and calling Trend Micro support for several days >>> > >> now >>> > >> about an issue where the server's TM Client is failing to update >>> > >> it's >>> > >> pattern definitions. All the client workstations update >>> > >> automatically, >>> > >> the Exchange messaging agent updates automatically, but the TM >>> > >> Client on >>> > >> the server fails to update either automatically or manually. A >>> > >> manual >>> > >> update concludes with "Update Succeeded", but the pattern stays at >>> > >> the >>> > >> old version. >>> > >> >>> > >> I'm on the phone again now, with someone who's English is pretty >>> > >> poor. He >>> > >> asked me to wait while he read the correspondence and phone logs, >>> > >> then >>> > >> proceeded to ask me questions clearly answered in the original >>> > >> service >>> > >> request and again in each email and phone call. >>> > >> >>> > >> I've received several solutions by phone and email, but they're >>> > >> always >>> > >> for the wrong problem, not for the issue I'm having. I got a >>> > >> solution for >>> > >> when the Exchange messaging agent fails to update, but I wrote that >>> > >> the >>> > >> messaging agent IS updating. Then I got a solution for the server >>> > >> failing >>> > >> to retrieve the updated pattern from TM, but I wrote that auto >>> > >> updates >>> > >> are working for everything except the TM Client on the server. >>> > >> Email only >>> > >> gets answered after 2 days, if at all. >>> > >> >>> > >> Does anyone have any suggestions either for my current problem or >>> > >> how to >>> > >> get through to knowledgeable TM support? >>> > >>> > >>> > > >
|
|
I spoke with a supervisor for tech support on Thursday regarding this issue.
He promised to call back on Friday at a prearranged time. He did not. My own
customer policy is to call when I say I'm going to call even if it's to say
'I don't have any additional information, but I'm still working on it'.
MikeMc
"Gregg Hill" <bogus[ at ]nowhere.com> wrote in message
news:uRLzlFLwHHA.2004[ at ]TK2MSFTNGP06.phx.gbl...
[Quoted Text] > Regarding Trend support, I recently had a problem with phishing emails > getting to my Inbox in spite of servers being up-to-date and properly > configured. I send great detail in my messages to Trend, and I get back > basic answers written for children such as "Turn on phishing > detection...." with directions how to do so. It seems as though their tech > support thinks we are all idiots. > > After their last response, I finally replied with > "Please stop treating me as though I am a complete moron. Let's just make > a few things clear so you know where to start. I am a professional network > consultant. I am a Trend Micro reseller. I have installed and configured > Trend Micro Client Server Messaging Security from version 2.0 to 3.6 on > multiple servers at multiple clients. I have a fully updated system, and > so do my clients." > > I would not be expecting a whole lot out of them for support. > > Gregg Hill > > > > > "news.microsoft.com" <paul.hideme[ at ]broadwayData.com> wrote in message > news:%237rk68JwHHA.3508[ at ]TK2MSFTNGP03.phx.gbl... >> Unloading the Client (right-click the system tray icon and choose Unload) >> and restarting it seems to update the patterns for me. Still not a great >> solution, but quicker than rebooting. Yesterday's insight from TM support >> was a suggestion to browse their support web, which I had already done. I >> got nowhere with my request for an elevation to higher-level support. >> >> "BrianY" <BrianY[ at ]discussions.microsoft.com> wrote in message >> news:DF021C9F-E271-4283-8F7B-29462B8A8062[ at ]microsoft.com... >>>I have SBS 2003 R2 with Trend CSM 3.6 and the problem started for me just >>> over a week ago. I did manage to update the pattern file by rebooting >>> the >>> server but since that time it hasn't updated again. At least now I know >>> I'm >>> not the only one with this problem. >>> >>> I've only had to deal with their support once before, on a licensing >>> issue. >>> In that case they resolved the problem in less than 24 hours. If only >>> they >>> could resolve this one as quickly . . . >>> >>> BrianY >>> >>> "jrieszer" wrote: >>> >>>> I manage three seperate SBS 2003 R2 installations with Trend CSM 3.5 on >>>> all. >>>> I have had the same problem on all of them for about a week. >>>> >>>> One of the clients also has a Server 2003 file server and the pattern >>>> file >>>> does not update on that server as well. All Win XP Pro clients update >>>> fine. >>>> >>>> I also found that if I stop and restart the Client/Server Security >>>> Agent >>>> service, then it will update to the newest pattern file. Once a new >>>> pattern >>>> file is released though, I need start/restart service again. >>>> >>>> "Paul Shapiro" wrote: >>>> >>>> > Same solution works here, and the problem started about the same >>>> > time. Hmmm. >>>> > I tried uninstalling the TM Client, rebooting and reinstalling. Same >>>> > behavior- no change at all. >>>> > >>>> > "SMC" <mmcelrath[ at ]earthlink.net> wrote in message >>>> > news:u1bxbQ2vHHA.2040[ at ]TK2MSFTNGP03.phx.gbl... >>>> > > I'm working w/ Trend on the same issue. No solution yet. >>>> > > >>>> > > The problem on my server started about one week ago and I have had >>>> > > to >>>> > > manually unload the client and then reload it for the update to >>>> > > take. >>>> > > >>>> > > MikeMc >>>> > > >>>> > > "Paul Shapiro" <paul[ at ]hideme.broadwayData.com> wrote in message >>>> > > news:%23QKa6s0vHHA.4640[ at ]TK2MSFTNGP03.phx.gbl... >>>> > >> I've been emailing and calling Trend Micro support for several >>>> > >> days now >>>> > >> about an issue where the server's TM Client is failing to update >>>> > >> it's >>>> > >> pattern definitions. All the client workstations update >>>> > >> automatically, >>>> > >> the Exchange messaging agent updates automatically, but the TM >>>> > >> Client on >>>> > >> the server fails to update either automatically or manually. A >>>> > >> manual >>>> > >> update concludes with "Update Succeeded", but the pattern stays at >>>> > >> the >>>> > >> old version. >>>> > >> >>>> > >> I'm on the phone again now, with someone who's English is pretty >>>> > >> poor. He >>>> > >> asked me to wait while he read the correspondence and phone logs, >>>> > >> then >>>> > >> proceeded to ask me questions clearly answered in the original >>>> > >> service >>>> > >> request and again in each email and phone call. >>>> > >> >>>> > >> I've received several solutions by phone and email, but they're >>>> > >> always >>>> > >> for the wrong problem, not for the issue I'm having. I got a >>>> > >> solution for >>>> > >> when the Exchange messaging agent fails to update, but I wrote >>>> > >> that the >>>> > >> messaging agent IS updating. Then I got a solution for the server >>>> > >> failing >>>> > >> to retrieve the updated pattern from TM, but I wrote that auto >>>> > >> updates >>>> > >> are working for everything except the TM Client on the server. >>>> > >> Email only >>>> > >> gets answered after 2 days, if at all. >>>> > >> >>>> > >> Does anyone have any suggestions either for my current problem or >>>> > >> how to >>>> > >> get through to knowledgeable TM support? >>>> > >>>> > >>>> > >> >> > >
|
|
Successfully Pattern Update!
1. Rolled back to Virus Engine 8.320.1004 via the Dashboard.
2. Only 2 of 7 computers automatically rolled back. The others I had to
manually uninstall and then reinstall the client. The Exchange server is
still on Virus Engine 8.500.1002 (it never would roll back but it did update
to the new Virus Pattern).
3. This only affects Win2003 servers inside the domain. My web server, on a
DMZ outside the domain, is running on Virus Engine 8.500.1002 and updates
without any problem.
MikeMc
"Paul Shapiro" <paul[ at ]hideme.broadwayData.com> wrote in message
news:%23QKa6s0vHHA.4640[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text] > I've been emailing and calling Trend Micro support for several days now
> about an issue where the server's TM Client is failing to update it's
> pattern definitions. All the client workstations update automatically, the
> Exchange messaging agent updates automatically, but the TM Client on the
> server fails to update either automatically or manually. A manual update
> concludes with "Update Succeeded", but the pattern stays at the old
> version.
>
> I'm on the phone again now, with someone who's English is pretty poor. He
> asked me to wait while he read the correspondence and phone logs, then
> proceeded to ask me questions clearly answered in the original service
> request and again in each email and phone call.
>
> I've received several solutions by phone and email, but they're always for
> the wrong problem, not for the issue I'm having. I got a solution for when
> the Exchange messaging agent fails to update, but I wrote that the
> messaging agent IS updating. Then I got a solution for the server failing
> to retrieve the updated pattern from TM, but I wrote that auto updates are
> working for everything except the TM Client on the server. Email only gets
> answered after 2 days, if at all.
>
> Does anyone have any suggestions either for my current problem or how to
> get through to knowledgeable TM support?
>
> Thanks, Paul Shapiro
>
|
|
Thanks for the update. I spoke with yet another TM support tech last night
and told him that the common thread among the people experiencing this was
that it occurred around the time the virus engine was updated. He told me
they don't have problems with the virus engine. He asked for a debug log
when the problem was occuring, which I sent last night. I'll let you know if
I get anywhere with support.
Paul Shapiro
"SMC" <mmcelrath[ at ]earthlink.net> wrote in message
news:%23CKod47wHHA.5108[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text] > Successfully Pattern Update! > > 1. Rolled back to Virus Engine 8.320.1004 via the Dashboard. > > 2. Only 2 of 7 computers automatically rolled back. The others I had to > manually uninstall and then reinstall the client. The Exchange server is > still on Virus Engine 8.500.1002 (it never would roll back but it did > update to the new Virus Pattern). > > 3. This only affects Win2003 servers inside the domain. My web server, on > a DMZ outside the domain, is running on Virus Engine 8.500.1002 and > updates without any problem. > > MikeMc > > > > "Paul Shapiro" <paul[ at ]hideme.broadwayData.com> wrote in message > news:%23QKa6s0vHHA.4640[ at ]TK2MSFTNGP03.phx.gbl... >> I've been emailing and calling Trend Micro support for several days now >> about an issue where the server's TM Client is failing to update it's >> pattern definitions. All the client workstations update automatically, >> the Exchange messaging agent updates automatically, but the TM Client on >> the server fails to update either automatically or manually. A manual >> update concludes with "Update Succeeded", but the pattern stays at the >> old version. >> >> I'm on the phone again now, with someone who's English is pretty poor. He >> asked me to wait while he read the correspondence and phone logs, then >> proceeded to ask me questions clearly answered in the original service >> request and again in each email and phone call. >> >> I've received several solutions by phone and email, but they're always >> for the wrong problem, not for the issue I'm having. I got a solution for >> when the Exchange messaging agent fails to update, but I wrote that the >> messaging agent IS updating. Then I got a solution for the server failing >> to retrieve the updated pattern from TM, but I wrote that auto updates >> are working for everything except the TM Client on the server. Email only >> gets answered after 2 days, if at all. >> >> Does anyone have any suggestions either for my current problem or how to >> get through to knowledgeable TM support?
|
|
While you're at it, mention that tons of PDF spams are getting through!
Gregg Hill
"Paul Shapiro" <paul[ at ]hideme.broadwayData.com> wrote in message
news:eYtci38wHHA.4736[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text] > Thanks for the update. I spoke with yet another TM support tech last night > and told him that the common thread among the people experiencing this was > that it occurred around the time the virus engine was updated. He told me > they don't have problems with the virus engine. He asked for a debug log > when the problem was occuring, which I sent last night. I'll let you know > if I get anywhere with support. > Paul Shapiro > > "SMC" <mmcelrath[ at ]earthlink.net> wrote in message > news:%23CKod47wHHA.5108[ at ]TK2MSFTNGP03.phx.gbl... >> Successfully Pattern Update! >> >> 1. Rolled back to Virus Engine 8.320.1004 via the Dashboard. >> >> 2. Only 2 of 7 computers automatically rolled back. The others I had to >> manually uninstall and then reinstall the client. The Exchange server is >> still on Virus Engine 8.500.1002 (it never would roll back but it did >> update to the new Virus Pattern). >> >> 3. This only affects Win2003 servers inside the domain. My web server, on >> a DMZ outside the domain, is running on Virus Engine 8.500.1002 and >> updates without any problem. >> >> MikeMc >> >> >> >> "Paul Shapiro" <paul[ at ]hideme.broadwayData.com> wrote in message >> news:%23QKa6s0vHHA.4640[ at ]TK2MSFTNGP03.phx.gbl... >>> I've been emailing and calling Trend Micro support for several days now >>> about an issue where the server's TM Client is failing to update it's >>> pattern definitions. All the client workstations update automatically, >>> the Exchange messaging agent updates automatically, but the TM Client on >>> the server fails to update either automatically or manually. A manual >>> update concludes with "Update Succeeded", but the pattern stays at the >>> old version. >>> >>> I'm on the phone again now, with someone who's English is pretty poor. >>> He asked me to wait while he read the correspondence and phone logs, >>> then proceeded to ask me questions clearly answered in the original >>> service request and again in each email and phone call. >>> >>> I've received several solutions by phone and email, but they're always >>> for the wrong problem, not for the issue I'm having. I got a solution >>> for when the Exchange messaging agent fails to update, but I wrote that >>> the messaging agent IS updating. Then I got a solution for the server >>> failing to retrieve the updated pattern from TM, but I wrote that auto >>> updates are working for everything except the TM Client on the server. >>> Email only gets answered after 2 days, if at all. >>> >>> Does anyone have any suggestions either for my current problem or how to >>> get through to knowledgeable TM support? > >
|
|
On Jul 11, 12:55 pm, "Gregg Hill" <b...[ at ]nowhere.com> wrote:
[Quoted Text] > While you're at it, mention that tons of PDF spams are getting through! > > Gregg Hill > > "Paul Shapiro" <p...[ at ]hideme.broadwayData.com> wrote in message > > news:eYtci38wHHA.4736[ at ]TK2MSFTNGP05.phx.gbl... > > > Thanks for the update. I spoke with yet another TM support tech last night > > and told him that the common thread among the people experiencing this was > > that it occurred around the time the virus engine was updated. He told me > > they don't have problems with the virus engine. He asked for a debug log > > when the problem was occuring, which I sent last night. I'll let you know > > if I get anywhere with support. > > Paul Shapiro > > > "SMC" <mmcelr...[ at ]earthlink.net> wrote in message > >news:%23CKod47wHHA.5108[ at ]TK2MSFTNGP03.phx.gbl... > >> Successfully Pattern Update! > > >> 1. Rolled back to Virus Engine 8.320.1004 via the Dashboard. > > >> 2. Only 2 of 7 computers automatically rolled back. The others I had to > >> manually uninstall and then reinstall the client. The Exchange server is > >> still on Virus Engine 8.500.1002 (it never would roll back but it did > >> update to the new Virus Pattern). > > >> 3. This only affects Win2003 servers inside the domain. My web server, on > >> a DMZ outside the domain, is running on Virus Engine 8.500.1002 and > >> updates without any problem. > > >> MikeMc > > >> "Paul Shapiro" <p...[ at ]hideme.broadwayData.com> wrote in message > >>news:%23QKa6s0vHHA.4640[ at ]TK2MSFTNGP03.phx.gbl... > >>> I've been emailing and callingTrendMicro support for several days now > >>> about an issue where the server's TM Client is failing to update it's > >>> pattern definitions. All the client workstations update automatically, > >>> the Exchange messaging agent updates automatically, but the TM Client on > >>> the server fails to update either automatically or manually. A manual > >>> update concludes with "Update Succeeded", but the pattern stays at the > >>> old version. > > >>> I'm on the phone again now, with someone who's English is pretty poor. > >>> He asked me to wait while he read the correspondence and phone logs, > >>> then proceeded to ask me questions clearly answered in the original > >>> service request and again in each email and phone call. > > >>> I've received several solutions by phone and email, but they're always > >>> for the wrong problem, not for the issue I'm having. I got a solution > >>> for when the Exchange messaging agent fails to update, but I wrote that > >>> the messaging agent IS updating. Then I got a solution for the server > >>> failing to retrieve the updated pattern from TM, but I wrote that auto > >>> updates are working for everything except the TM Client on the server. > >>> Email only gets answered after 2 days, if at all. > > >>> Does anyone have any suggestions either for my current problem or how to > >>> get through to knowledgeable TM support?
Hello,
I'm having the same problem at many clients that I'm supporting. I
have about 13 Trend CSM 3.6 servers and about 30-50% of the clients go
"red" and services stop upon a boot. I have tried removing
autopcc.exe from the login script, but the problem continues. I have
added a script to the startup process which changes the services to
automatically start if they are stopped, then the script starts the
services. We STILL have 10-15% of the clients that won't stay
started. I have called Trend support and they indicated that they
haven't heard about this and suggested that we uninstall/reinstall the
clients (which we've done) and/or unintsall/reinstall the server
(which we've done). I think they just wanted to get me off of the
phone.
If any one has any suggestions for fixing this without "jimmying" the
login script/registry/services, I'd really appreciate it. In the
meantime, I am going to call Trend again. I will post again if they
offer anything worthwhile.
Thanks,
Tom
|
|
On Jul 12, 2:15 pm, erde...[ at ]gmail.com wrote:
[Quoted Text] > On Jul 11, 12:55 pm, "Gregg Hill" <b...[ at ]nowhere.com> wrote: > > > > > While you're at it, mention that tons of PDF spams are getting through! > > > Gregg Hill > > > "Paul Shapiro" <p...[ at ]hideme.broadwayData.com> wrote in message > > >news:eYtci38wHHA.4736[ at ]TK2MSFTNGP05.phx.gbl... > > > > Thanks for the update. I spoke with yet another TM support tech last night > > > and told him that the common thread among the people experiencing this was > > > that it occurred around the time the virus engine was updated. He told me > > > they don't have problems with the virus engine. He asked for a debug log > > > when the problem was occuring, which I sent last night. I'll let you know > > > if I get anywhere with support. > > > Paul Shapiro > > > > "SMC" <mmcelr...[ at ]earthlink.net> wrote in message > > >news:%23CKod47wHHA.5108[ at ]TK2MSFTNGP03.phx.gbl... > > >> Successfully Pattern Update! > > > >> 1. Rolled back to Virus Engine 8.320.1004 via the Dashboard. > > > >> 2. Only 2 of 7 computers automatically rolled back. The others I had to > > >> manually uninstall and then reinstall the client. The Exchange server is > > >> still on Virus Engine 8.500.1002 (it never would roll back but it did > > >> update to the new Virus Pattern). > > > >> 3. This only affects Win2003 servers inside the domain. My web server, on > > >> a DMZ outside the domain, is running on Virus Engine 8.500.1002 and > > >> updates without any problem. > > > >> MikeMc > > > >> "Paul Shapiro" <p...[ at ]hideme.broadwayData.com> wrote in message > > >>news:%23QKa6s0vHHA.4640[ at ]TK2MSFTNGP03.phx.gbl... > > >>> I've been emailing and callingTrendMicro support for several days now > > >>> about an issue where the server's TM Client is failing to update it's > > >>> pattern definitions. All the client workstations update automatically, > > >>> the Exchange messaging agent updates automatically, but the TM Client on > > >>> the server fails to update either automatically or manually. A manual > > >>> update concludes with "Update Succeeded", but the pattern stays at the > > >>> old version. > > > >>> I'm on the phone again now, with someone who's English is pretty poor. > > >>> He asked me to wait while he read the correspondence and phone logs, > > >>> then proceeded to ask me questions clearly answered in the original > > >>> service request and again in each email and phone call. > > > >>> I've received several solutions by phone and email, but they're always > > >>> for the wrong problem, not for the issue I'm having. I got a solution > > >>> for when the Exchange messaging agent fails to update, but I wrote that > > >>> the messaging agent IS updating. Then I got a solution for the server > > >>> failing to retrieve the updated pattern from TM, but I wrote that auto > > >>> updates are working for everything except the TM Client on the server. > > >>> Email only gets answered after 2 days, if at all. > > > >>> Does anyone have any suggestions either for my current problem or how to > > >>> get through to knowledgeable TM support? > > Hello, > > I'm having the same problem at many clients that I'm supporting. I > have about 13TrendCSM3.6 servers and about 30-50% of the clients go > "red" andservicesstop upon a boot. I have tried removing > autopcc.exe from the login script, but the problem continues. I have > added a script to the startup process which changes theservicesto > automatically start if they are stopped, then the script starts theservices. We STILL have 10-15% of the clients that won't stay > started. I have calledTrendsupport and they indicated that they > haven't heard about this and suggested that we uninstall/reinstall the > clients (which we've done) and/or unintsall/reinstall the server > (which we've done). I think they just wanted to get me off of the > phone. > > If any one has any suggestions for fixing this without "jimmying" the > login script/registry/services, I'd really appreciate it. In the > meantime, I am going to callTrendagain. I will post again if they > offer anything worthwhile. > > Thanks, > > Tom
Okay, I may have run across the solution when looking at the Known
Issues section of the read me for 3.6. Apparently there's a known
issue for this and MS has a hotfix (it's one of those that requires a
call in to MS support to get). Since I do not have any current test
cases, I cannot verify that this works, but any feedback would be
appreciated.
Here is the link to the read me: http://www.trendmicro.com/ftp/documentation/readme/readme_csm_36.txt
Here is the link to the KB article: http://support.microsoft.com/default.aspx?scid=kb;en-us;892489
Here is a link to the file (link may wrap):
http://thehotfixshare.net/download/index.php?dir=English/Windows%20XP/&file=WindowsXP-KB892489-x86-ENU.exe
Please post if this fix helps.
Thanks,
Tom Erdely
|
|
The hotfix you linked only seems to apply to WinXP SP2. My WinXP
workstations are updating successfully. It's the SBS server's TM Client that
won't update the pattern. So the hotfix might fix some issues, but I don't
think it's going to fix the TM client problems. Certainly not mine. See
below where Mike Mc reported success by rolling back to an older version of
the TM Virus Engine.
<erdelyt[ at ]gmail.com> wrote in message
news:1184264710.196944.139960[ at ]o61g2000hsh.googlegroups.com...
[Quoted Text] > On Jul 12, 2:15 pm, erde...[ at ]gmail.com wrote: >> On Jul 11, 12:55 pm, "Gregg Hill" <b...[ at ]nowhere.com> wrote: >> >> > While you're at it, mention that tons of PDF spams are getting through! >> >> > Gregg Hill >> >> > "Paul Shapiro" <p...[ at ]hideme.broadwayData.com> wrote in message >> >> >news:eYtci38wHHA.4736[ at ]TK2MSFTNGP05.phx.gbl... >> >> > > Thanks for the update. I spoke with yet another TM support tech last >> > > night >> > > and told him that the common thread among the people experiencing >> > > this was >> > > that it occurred around the time the virus engine was updated. He >> > > told me >> > > they don't have problems with the virus engine. He asked for a debug >> > > log >> > > when the problem was occuring, which I sent last night. I'll let you >> > > know >> > > if I get anywhere with support. >> > > Paul Shapiro >> >> > > "SMC" <mmcelr...[ at ]earthlink.net> wrote in message >> > >news:%23CKod47wHHA.5108[ at ]TK2MSFTNGP03.phx.gbl... >> > >> Successfully Pattern Update! >> >> > >> 1. Rolled back to Virus Engine 8.320.1004 via the Dashboard. >> >> > >> 2. Only 2 of 7 computers automatically rolled back. The others I had >> > >> to >> > >> manually uninstall and then reinstall the client. The Exchange >> > >> server is >> > >> still on Virus Engine 8.500.1002 (it never would roll back but it >> > >> did >> > >> update to the new Virus Pattern). >> >> > >> 3. This only affects Win2003 servers inside the domain. My web >> > >> server, on >> > >> a DMZ outside the domain, is running on Virus Engine 8.500.1002 and >> > >> updates without any problem. >> >> > >> MikeMc >> >> > >> "Paul Shapiro" <p...[ at ]hideme.broadwayData.com> wrote in message >> > >>news:%23QKa6s0vHHA.4640[ at ]TK2MSFTNGP03.phx.gbl... >> > >>> I've been emailing and callingTrendMicro support for several days >> > >>> now >> > >>> about an issue where the server's TM Client is failing to update >> > >>> it's >> > >>> pattern definitions. All the client workstations update >> > >>> automatically, >> > >>> the Exchange messaging agent updates automatically, but the TM >> > >>> Client on >> > >>> the server fails to update either automatically or manually. A >> > >>> manual >> > >>> update concludes with "Update Succeeded", but the pattern stays at >> > >>> the >> > >>> old version. >> >> > >>> I'm on the phone again now, with someone who's English is pretty >> > >>> poor. >> > >>> He asked me to wait while he read the correspondence and phone >> > >>> logs, >> > >>> then proceeded to ask me questions clearly answered in the original >> > >>> service request and again in each email and phone call. >> >> > >>> I've received several solutions by phone and email, but they're >> > >>> always >> > >>> for the wrong problem, not for the issue I'm having. I got a >> > >>> solution >> > >>> for when the Exchange messaging agent fails to update, but I wrote >> > >>> that >> > >>> the messaging agent IS updating. Then I got a solution for the >> > >>> server >> > >>> failing to retrieve the updated pattern from TM, but I wrote that >> > >>> auto >> > >>> updates are working for everything except the TM Client on the >> > >>> server. >> > >>> Email only gets answered after 2 days, if at all. >> >> > >>> Does anyone have any suggestions either for my current problem or >> > >>> how to >> > >>> get through to knowledgeable TM support? >> >> Hello, >> >> I'm having the same problem at many clients that I'm supporting. I >> have about 13TrendCSM3.6 servers and about 30-50% of the clients go >> "red" andservicesstop upon a boot. I have tried removing >> autopcc.exe from the login script, but the problem continues. I have >> added a script to the startup process which changes theservicesto >> automatically start if they are stopped, then the script starts >> theservices. We STILL have 10-15% of the clients that won't stay >> started. I have calledTrendsupport and they indicated that they >> haven't heard about this and suggested that we uninstall/reinstall the >> clients (which we've done) and/or unintsall/reinstall the server >> (which we've done). I think they just wanted to get me off of the >> phone. >> >> If any one has any suggestions for fixing this without "jimmying" the >> login script/registry/services, I'd really appreciate it. In the >> meantime, I am going to callTrendagain. I will post again if they >> offer anything worthwhile. >> >> Thanks, >> >> Tom > > Okay, I may have run across the solution when looking at the Known > Issues section of the read me for 3.6. Apparently there's a known > issue for this and MS has a hotfix (it's one of those that requires a > call in to MS support to get). Since I do not have any current test > cases, I cannot verify that this works, but any feedback would be > appreciated. > > Here is the link to the read me: > http://www.trendmicro.com/ftp/documentation/readme/readme_csm_36.txt> > Here is the link to the KB article: > http://support.microsoft.com/default.aspx?scid=kb;en-us;892489> > Here is a link to the file (link may wrap): > > http://thehotfixshare.net/download/index.php?dir=English/Windows%20XP/&file=WindowsXP-KB892489-x86-ENU.exe> > Please post if this fix helps. > > Thanks, > Tom Erdely
|
|
I must be the lucky one here. I have five installations on SBS 2003. One on
RTM, two on SP1, and two on R2. All of them are updating properly.
As of a few minutes ago, mine were all at the following level:
CSMS for SMB version 3.6 build 1095
Program version - 7.6.1095
Engine version = 8.500.1002
Virus pattern = 4.593.00
In anticipation of the "Why do you still have one on the initial release?"
question, the answer is three short words: very cheap customer.
Gregg Hill
"Paul Shapiro" <paul[ at ]hideme.broadwayData.com> wrote in message
news:%23IiQc7MxHHA.4300[ at ]TK2MSFTNGP04.phx.gbl...
[Quoted Text] > The hotfix you linked only seems to apply to WinXP SP2. My WinXP > workstations are updating successfully. It's the SBS server's TM Client > that won't update the pattern. So the hotfix might fix some issues, but I > don't think it's going to fix the TM client problems. Certainly not mine. > See below where Mike Mc reported success by rolling back to an older > version of the TM Virus Engine. > > <erdelyt[ at ]gmail.com> wrote in message > news:1184264710.196944.139960[ at ]o61g2000hsh.googlegroups.com... >> On Jul 12, 2:15 pm, erde...[ at ]gmail.com wrote: >>> On Jul 11, 12:55 pm, "Gregg Hill" <b...[ at ]nowhere.com> wrote: >>> >>> > While you're at it, mention that tons of PDF spams are getting >>> > through! >>> >>> > Gregg Hill >>> >>> > "Paul Shapiro" <p...[ at ]hideme.broadwayData.com> wrote in message >>> >>> >news:eYtci38wHHA.4736[ at ]TK2MSFTNGP05.phx.gbl... >>> >>> > > Thanks for the update. I spoke with yet another TM support tech last >>> > > night >>> > > and told him that the common thread among the people experiencing >>> > > this was >>> > > that it occurred around the time the virus engine was updated. He >>> > > told me >>> > > they don't have problems with the virus engine. He asked for a debug >>> > > log >>> > > when the problem was occuring, which I sent last night. I'll let you >>> > > know >>> > > if I get anywhere with support. >>> > > Paul Shapiro >>> >>> > > "SMC" <mmcelr...[ at ]earthlink.net> wrote in message >>> > >news:%23CKod47wHHA.5108[ at ]TK2MSFTNGP03.phx.gbl... >>> > >> Successfully Pattern Update! >>> >>> > >> 1. Rolled back to Virus Engine 8.320.1004 via the Dashboard. >>> >>> > >> 2. Only 2 of 7 computers automatically rolled back. The others I >>> > >> had to >>> > >> manually uninstall and then reinstall the client. The Exchange >>> > >> server is >>> > >> still on Virus Engine 8.500.1002 (it never would roll back but it >>> > >> did >>> > >> update to the new Virus Pattern). >>> >>> > >> 3. This only affects Win2003 servers inside the domain. My web >>> > >> server, on >>> > >> a DMZ outside the domain, is running on Virus Engine 8.500.1002 and >>> > >> updates without any problem. >>> >>> > >> MikeMc >>> >>> > >> "Paul Shapiro" <p...[ at ]hideme.broadwayData.com> wrote in message >>> > >>news:%23QKa6s0vHHA.4640[ at ]TK2MSFTNGP03.phx.gbl... >>> > >>> I've been emailing and callingTrendMicro support for several days >>> > >>> now >>> > >>> about an issue where the server's TM Client is failing to update >>> > >>> it's >>> > >>> pattern definitions. All the client workstations update >>> > >>> automatically, >>> > >>> the Exchange messaging agent updates automatically, but the TM >>> > >>> Client on >>> > >>> the server fails to update either automatically or manually. A >>> > >>> manual >>> > >>> update concludes with "Update Succeeded", but the pattern stays at >>> > >>> the >>> > >>> old version. >>> >>> > >>> I'm on the phone again now, with someone who's English is pretty >>> > >>> poor. >>> > >>> He asked me to wait while he read the correspondence and phone >>> > >>> logs, >>> > >>> then proceeded to ask me questions clearly answered in the >>> > >>> original >>> > >>> service request and again in each email and phone call. >>> >>> > >>> I've received several solutions by phone and email, but they're >>> > >>> always >>> > >>> for the wrong problem, not for the issue I'm having. I got a >>> > >>> solution >>> > >>> for when the Exchange messaging agent fails to update, but I wrote >>> > >>> that >>> > >>> the messaging agent IS updating. Then I got a solution for the >>> > >>> server >>> > >>> failing to retrieve the updated pattern from TM, but I wrote that >>> > >>> auto >>> > >>> updates are working for everything except the TM Client on the >>> > >>> server. >>> > >>> Email only gets answered after 2 days, if at all. >>> >>> > >>> Does anyone have any suggestions either for my current problem or >>> > >>> how to >>> > >>> get through to knowledgeable TM support? >>> >>> Hello, >>> >>> I'm having the same problem at many clients that I'm supporting. I >>> have about 13TrendCSM3.6 servers and about 30-50% of the clients go >>> "red" andservicesstop upon a boot. I have tried removing >>> autopcc.exe from the login script, but the problem continues. I have >>> added a script to the startup process which changes theservicesto >>> automatically start if they are stopped, then the script starts >>> theservices. We STILL have 10-15% of the clients that won't stay >>> started. I have calledTrendsupport and they indicated that they >>> haven't heard about this and suggested that we uninstall/reinstall the >>> clients (which we've done) and/or unintsall/reinstall the server >>> (which we've done). I think they just wanted to get me off of the >>> phone. >>> >>> If any one has any suggestions for fixing this without "jimmying" the >>> login script/registry/services, I'd really appreciate it. In the >>> meantime, I am going to callTrendagain. I will post again if they >>> offer anything worthwhile. >>> >>> Thanks, >>> >>> Tom >> >> Okay, I may have run across the solution when looking at the Known >> Issues section of the read me for 3.6. Apparently there's a known >> issue for this and MS has a hotfix (it's one of those that requires a >> call in to MS support to get). Since I do not have any current test >> cases, I cannot verify that this works, but any feedback would be >> appreciated. >> >> Here is the link to the read me: >> http://www.trendmicro.com/ftp/documentation/readme/readme_csm_36.txt>> >> Here is the link to the KB article: >> http://support.microsoft.com/default.aspx?scid=kb;en-us;892489>> >> Here is a link to the file (link may wrap): >> >> http://thehotfixshare.net/download/index.php?dir=English/Windows%20XP/&file=WindowsXP-KB892489-x86-ENU.exe>> >> Please post if this fix helps. >> >> Thanks, >> Tom Erdely > >
|
|
|