locked
Can we "fool" the discovery service for client installations (SCCM 2007 SP2) RRS feed

  • Question

  • This question has been asked before, albeit in a slightly different way (see http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/a9996dce-8b64-4336-b5e0-c7168c99f1d9), so here's my take....

    Can we prevent the discovery service / client push installer from installing the SCCM client on machines in a particular AD OU/container?   By default, when a computer joins the domain, it ends up in the Computers container; we tend to use this a dumping ground for temporary machines/VM's etc. and they only get moved to their home OU if/when they are allocated.  I'd like to exclude anything/everything in the Computers container from automatically receiving the SCCM client, so we can prevent the database from being cluttered with random computer data (and so that the SCCM client doesn't get in the way of anything we're testing/debugging in a VM, for example).

    Regards,

    Mark.
    Monday, February 22, 2010 3:34 PM

Answers

  • Don't include the container in your AD discovery or remove access to that container for the siteserver.
    Monday, February 22, 2010 3:48 PM