Thanks to reader IK

This is in reference to post "Trend Officescan Not
Updating" posted on 8/31/03, thanks IK for posting the
hotfix and link needed from Trend. I was having this
exact same problem and have corresponded with Trend but
was never able to get it resolved. I have since obtained
this hotfix and for the first time, my w/s updated
automatically. I did not need to do a manual update.

One question though, while my w/s updated automatically,
when I opened the Trend Server Protect Management Console,
I noticed that the server was still at pattern 628 (the
last pattern file). It downloaded pattern 630 (the
newest) and deployed it to all the w/s but the server is
still at 628. I could hit the "deploy now" button & it
would update to 630. Is there a separate hotfix for
this. Or is it something I'm missing? I'm running the
Client Server Suite from Trend.

Anyone know the answer to this?

TIA!

Kevin
Wed Sep 10 21:57:38 CDT 2003

Mike, not sure about Server Protect, but on the older Trend SBS package, I
created two batch jobs that I schedule on my server. Both batch jobs run the
same identical .bat file - which checks the Trend web site for updates -
but oone is scheduled to run everytime the server is rebooted, the other
runs every morning at 6am --- just in case!

The content of the batch file is this:

copy "c:\program files\trend\officescan\pccsrv\lpt$vpn.*" "c:\officescan nt"
copy "c:\program files\trend\officescan\pccsrv\pccnt\drv\vsapint.sys"
"c:\officescan nt"
copy "c:\program files\trend\officescan\pccsrv\pccnt\drv\tmfilter.sys"
"c:\officescan nt"
net stop "officescannt realtime scan"
net start "officescannt realtime scan"
net stop "officescannt listener"
net start "officescannt listener"

"mike" <mike@nospam.com> wrote in message
news:104d01c377ed$5a89f150$a601280a@phx.gbl...
> This is in reference to post "Trend Officescan Not
> Updating" posted on 8/31/03, thanks IK for posting the
> hotfix and link needed from Trend. I was having this
> exact same problem and have corresponded with Trend but
> was never able to get it resolved. I have since obtained
> this hotfix and for the first time, my w/s updated
> automatically. I did not need to do a manual update.
>
> One question though, while my w/s updated automatically,
> when I opened the Trend Server Protect Management Console,
> I noticed that the server was still at pattern 628 (the
> last pattern file). It downloaded pattern 630 (the
> newest) and deployed it to all the w/s but the server is
> still at 628. I could hit the "deploy now" button & it
> would update to 630. Is there a separate hotfix for
> this. Or is it something I'm missing? I'm running the
> Client Server Suite from Trend.
>
> Anyone know the answer to this?
>
> TIA!

Mike
Wed Sep 10 22:49:40 CDT 2003

Thanks Kevin for your reply. I'll see if I could put this
to work too.


>-----Original Message-----
>Mike, not sure about Server Protect, but on the older
Trend SBS package, I
>created two batch jobs that I schedule on my server. Both
batch jobs run the
>same identical .bat file - which checks the Trend web
site for updates -
>but oone is scheduled to run everytime the server is
rebooted, the other
>runs every morning at 6am --- just in case!
>
>The content of the batch file is this:
>
>copy "c:\program
files\trend\officescan\pccsrv\lpt$vpn.*" "c:\officescan nt"
>copy "c:\program
files\trend\officescan\pccsrv\pccnt\drv\vsapint.sys"
>"c:\officescan nt"
>copy "c:\program
files\trend\officescan\pccsrv\pccnt\drv\tmfilter.sys"
>"c:\officescan nt"
>net stop "officescannt realtime scan"
>net start "officescannt realtime scan"
>net stop "officescannt listener"
>net start "officescannt listener"
>
>"mike" <mike@nospam.com> wrote in message
>news:104d01c377ed$5a89f150$a601280a@phx.gbl...
>> This is in reference to post "Trend Officescan Not
>> Updating" posted on 8/31/03, thanks IK for posting the
>> hotfix and link needed from Trend. I was having this
>> exact same problem and have corresponded with Trend but
>> was never able to get it resolved. I have since
obtained
>> this hotfix and for the first time, my w/s updated
>> automatically. I did not need to do a manual update.
>>
>> One question though, while my w/s updated automatically,
>> when I opened the Trend Server Protect Management
Console,
>> I noticed that the server was still at pattern 628 (the
>> last pattern file). It downloaded pattern 630 (the
>> newest) and deployed it to all the w/s but the server is
>> still at 628. I could hit the "deploy now" button & it
>> would update to 630. Is there a separate hotfix for
>> this. Or is it something I'm missing? I'm running the
>> Client Server Suite from Trend.
>>
>> Anyone know the answer to this?
>>
>> TIA!
>
>
>.
>

Mike
Thu Sep 11 17:17:25 CDT 2003

Hi John, A quick update to this....I sent an e-mail to
Trend inquiring about this, they wanted me to close window
& reopen to see if it would refresh. Well I had already
done that & that was not the problem. I decided to wait
an extra day to see if it would deploy on its own and lo
and behold it did...so I did not need to do anything. It
just seemed to be a bit behind. Hopefully the hotfix
works for you too.



>-----Original Message-----
>Mike,
>
>I am in a similar situation to you. I am waiting to
receive the B1144
>hotfix. When I install it I will see if it breaks the
>ServerProtect updating and post back.
>
>John
>
>"mike" <mike@nospam.com> wrote in message
>news:104d01c377ed$5a89f150$a601280a@phx.gbl...
>> This is in reference to post "Trend Officescan Not
>> Updating" posted on 8/31/03, thanks IK for posting the
>> hotfix and link needed from Trend. I was having this
>> exact same problem and have corresponded with Trend but
>> was never able to get it resolved. I have since
obtained
>> this hotfix and for the first time, my w/s updated
>> automatically. I did not need to do a manual update.
>>
>> One question though, while my w/s updated automatically,
>> when I opened the Trend Server Protect Management
Console,
>> I noticed that the server was still at pattern 628 (the
>> last pattern file). It downloaded pattern 630 (the
>> newest) and deployed it to all the w/s but the server is
>> still at 628. I could hit the "deploy now" button & it
>> would update to 630. Is there a separate hotfix for
>> this. Or is it something I'm missing? I'm running the
>> Client Server Suite from Trend.
>>
>> Anyone know the answer to this?
>>
>> TIA!
>
>
>.
>