SMS 2003 points to entire domain

SMS 2003 in this environment points to the entire domain even though software is only deployed to desktops and laptops.

I believe it should only point to the "Desktop" OU, or whatever it's named, the OU that holds all the desktops and laptops.
The concern someone raised is.........what if a Desktop is in the wrong OU, it will not receive SMS deployments.
Well........it shouldn't be in a "wrong" OU.

Anyway, I am curious as to what you think of the scenario.
Why point to the entire domain and why not?

Thanks so much.

0 Comments   [ + ] Show comments

Answers (2)

Posted by: dunnpy 12 years ago
Red Belt
Your SMS site boundaries are generally either AD sites or IP subnets - which will cover, in general, your whole AD.
You could just include the client subnets and exclude the server subnets here, but there are other configuration options that you can exclude servers with, including the client installation settings to only target desktop OSs

Then depending how you target computers for software deployment you can use AD group membership (computer) and a query to bring that OU membership into a collection. You can specify which OUs are queried on a schedule as part of the SMS settings - thereby just including your desktop OUs.

The option is always there then to deploy to servers at a later stage with a minor configuration change.

Hope that helps,

Posted by: anonymous_9363 12 years ago
Red Belt
Remember that SMS/SCCM isn't just for deploying software, but for use as a management/reporting tool.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ