Hi and firstly I want to say a huge thanks for these forums and the help they've provided me!
Now on to my question
We have a single SCCM 2007 R2 setup that services multiple branch offices in a single AD Domain (mixed mode).
Ordinarily SCCM pushes the client to all machines that are discovered via AD system discovery, what I wanted to ask was is there some script or method of identifying if a machine has a certain .txt file on it's C: drive (this .txt file is created at the time of the successful SCCM client install) and if the .txt files exists then SCCM does not push down/cache the client installation package...however if the .txt file is not found on the machine the client package will proceed with the download and installation?
Please forgive me if there is some native or inherent way of doing this as I am still very much getting the grip of SCCM slowly.
This would be run once a week against all machines that have been discovered within the AD sites and populated in SCCM.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
Hi and firstly I want to say a huge thanks for these forums and the help they've provided me!
Now on to my question
We have a single SCCM 2007 R2 setup that services multiple branch offices in a single AD Domain (mixed mode).
Ordinarily SCCM pushes the client to all machines that are discovered via AD system discovery, what I wanted to ask was is there some script or method of identifying if a machine has a certain .txt file on it's C: drive (this .txt file is created at the time of the successful SCCM client install) and if the .txt files exists then SCCM does not push down/cache the client installation package...however if the .txt file is not found on the machine the client package will proceed with the download and installation?
Please forgive me if there is some native or inherent way of doing this as I am still very much getting the grip of SCCM slowly.
This would be run once a week against all machines that have been discovered within the AD sites and populated in SCCM.
Many thanks in advance for any help or advice.
Z
Share this post
Link to post
Share on other sites