Re: Trend Micro CSM 3.6 Install Client?

Richard

One approach I did not see suggested here involves building a Client
Install Package (.msi) and assigning it using Group Policy. It is not
as complicated as it sounds and it is fairly lights-out once you set it
up. Basically it involves the following:

1. In the ofcscan share, navigate to the folder called
\Admin\ClientPackager and run ClnPack.exe to build the msi.
2. Move the resultant msi package to a share that has read access for
Authenticated Users.
3. Setup a Group Policy Object and Assign (NOT Publish) the .msi under
Computer Configuration|Software Settings|Software installation.
4. Assign the GPO to the OU that holds your client computers. By
default, SBS sets up an OU MyBusiness|Computers|SBSComputers

We learned this trick when automatically deploying ISA Firewall Client
via Group Policy.

HTH,
Joe

Richard K wrote:
> I have been successfully using the Trend Micro CSM 3.6 product on my SBS 2003
> installs but the only thing that I can find to be a bit tedious is pushing
> out the client to the XP clients in the domain.
>
> What methods do people use and recommend to push out the client that can be
> as automated as possible in the domain? Sometimes I run into companies where
> they have another solution running on the client and I need to uninstall that
> client before installing the TM client. What do you do there. Also, it
> would be nice to have that when a new XP machine joins the domain they
> automatically get it installed.
>
> Also, any "gotchas" or "make sure you do" thoughts would be helpfull.
>
> Just look for some "best practices" on making my network admin job easier.
>
> Thanks!
>
> -Richard

Great tip, Joe :-).

--
Les Connor [SBS MVP]


"J. M. De Moor" <papajoe.nospam@nospam.net> wrote in message
news:OAw$59JVIHA.4696@TK2MSFTNGP05.phx.gbl...
> Richard
>
> One approach I did not see suggested here involves building a Client
> Install Package (.msi) and assigning it using Group Policy. It is not as
> complicated as it sounds and it is fairly lights-out once you set it up.
> Basically it involves the following:
>
> 1. In the ofcscan share, navigate to the folder called
> \Admin\ClientPackager and run ClnPack.exe to build the msi.
> 2. Move the resultant msi package to a share that has read access for
> Authenticated Users.
> 3. Setup a Group Policy Object and Assign (NOT Publish) the .msi under
> Computer Configuration|Software Settings|Software installation.
> 4. Assign the GPO to the OU that holds your client computers. By default,
> SBS sets up an OU MyBusiness|Computers|SBSComputers
>
> We learned this trick when automatically deploying ISA Firewall Client via
> Group Policy.
>
> HTH,
> Joe
>
> Richard K wrote:
>> I have been successfully using the Trend Micro CSM 3.6 product on my SBS
>> 2003 installs but the only thing that I can find to be a bit tedious is
>> pushing out the client to the XP clients in the domain.
>>
>> What methods do people use and recommend to push out the client that can
>> be as automated as possible in the domain? Sometimes I run into
>> companies where they have another solution running on the client and I
>> need to uninstall that client before installing the TM client. What do
>> you do there. Also, it would be nice to have that when a new XP machine
>> joins the domain they automatically get it installed. Also, any
>> "gotchas" or "make sure you do" thoughts would be helpfull.
>>
>> Just look for some "best practices" on making my network admin job
>> easier.
>>
>> Thanks!
>>
>> -Richard