Search results for query: *

Thanks for replying. The other servers and workstations which make up about 25% of the computers in the domain belong to another group. Those computers are mixed in the same OU with ours currently. I believe there is a common factor in the naming of their computer where they have 2 characters...

What's the best way to automate the client install if I do not want to deploy to every computer in the domain? Would this be the best way? Create sub OUs for the workstations that I don't want to have the client. Create a SMS collection that populates from the OU that I do want to get the...

Would this be the best way to manage updates to certain servers? Create sub OUs under the existing OUs the servers are currently in and call it something like sms managed servers. Move the servers that I want to get patches into this sub OU. Then create a collection that populates itself from...

Thanks for all the answers guys.

That's what I was afraid of. I was hoping not to add anymore to our current login script. So basically if a user manages to remove the client or the computer gets reimaged, the SMS server will not know on it's own to redeploy the client out to it? Thanks, Don

To control the client installation, I populate a collection manually and right click the collection and choose install client. As an initial test I need to push the client out to 2 of our 40 schools. I've created 40 collections that automatically populated themselves from AD. So I was wondering...

Was wondering if I can confine automatic deployment of the SMS client to a collection? I know that turning on client push will deploy to the whole site and I know I can push to a collection, but I have to initiate the push everytime I put a new workstation into the collection. Just wondering if...