SMS 2.0 client deployment question

[Mase]

I would like to deploy the SMS 2.0 client with as little impact on the network as possible. Are there any other ways to deploy the client at remote sites other than using the NETLOGON method? <br>
<br>
I would also like to push out the client to specific groups on a gradual basis.. is there a utility that will differentiate the group a user belongs to when they login to determine whether or not they will get the client?<br>
<br>
Thanks in advance.

 

[ntadmin]

You can use the resource kit tool IFMEMBER.EXE to check who is in a Global Usergroup. We use this to map drives for certain users.