http://sccmconfighelp.wordpress.com/2013/07/25/sccm-applications-demystified-part-2-requirement/ - Part 2
http://sccmconfighelp.wordpress.com/2013/07/25/sccm-applications-demystified-part-2-detection-rules/ Part 3
http://sccmconfighelp.wordpress.com/2013/07/29/sccm-applications-demystified-part-4-application-request/ Part 4
http://sccmconfighelp.wordpress.com/2013/07/29/sccm-applications-demystified-part-5-application-request-contd/ - Part 5
While we are done with the Concept of Applications in SCCM 2012 , We are aware that what are requirements in SCCM 2012 , We will now take up the concept of Detection Rules .
Detection Rules : A Detection rule is a concept by which we can find out if a Software has already been present on the user's machine . If the software is present we may not want to install it again . As a direct benefit of this would be that we are not Utilizing the Network bandwidth for the software deployment which the user machine already has !!
Sample Flow Chart :
SCCM Detection Rule Window:
There are Three Types of Detection Rules in SCCM :
- File System – This method allows you to detect whether a specified file or folder exists on a client device, thus indicating that the application is installed.
The File system setting type does not support specifying a UNC path to a network share in the Path field. You can only specify a local path on the client device. - Registry – This method allows you to detect whether a specified registry key or registry value exists on a client device, thus indicating that the application is installed.
Select the option This registry key is associated with a 32-bit application on 64-bit systems to check 32-bit registry locations for the specified registry key first. If the registry key is not found, then 64-bit locations will be searched.
Windows Installer – This method allows you to detect whether a specified Windows Installer file exists on a client device, thus indicating that the application is installed.
0 comments:
Post a Comment