Client Option Set- General Usage

[GRice]

Curious as to how others manage Client Option Sets? we are a windows shop and really only introduced 2008 server last year (2010). So we've only managed one to this point. Do you guys split one for 2003 server, one for 2008 server, specific opt sets for SQL, .NET, JAVA, Spefic Apps, etc?

 

[mallirajan]

Hi

It is possible to create an individual cloptset for each versions of windows server's. Create a cloptset with naming occording to the versions and the add the include excludes to them.

1. Define cloptset "---"
2. Define clientopt "<cloptsetname>" <option> with sequence number incase more things to be added like domain, include excludes etc.

3. register or update the node with cloptset="----" Then restart the TSM client service to get the modifications effective for the existing nodes.

Then the concern include exclude files specified for that windows version can be used effectively.

Regards
Malli Rajan

 

[Phil_02GT]

Here we have 1 client option set for all Windows versions, 1 for AIX, 1 for Linux, etc
We put generic stuff in the option set and what is specific to a server in the dsm.sys/dsm.opt