Disabling Hash and Full Path Checking

Hash and full path checking can be disabled for a particular file group. Disabling hash checking is often practical in the midst of a system-wide application update. For example, if an update to Microsoft Office is being installed to one Terminal Server at a time, hash checking can be temporarily disabled until the update has been installed to all the servers and the version of Microsoft Office has been made consistent across the entire farm. Once new hashes are computed for the updated program executables, only then can hash checking be re-enabled.

As well, full path checking can optionally be disabled for various purposes. For example, if the same application is installed to different target folders on different Terminal Servers, full path checking may fail depending on which Terminal Server the user happens to log on to. However, this particular scenario can be mitigated by maintaining multiple file groups for the same application, where each file group is associated with a particular target folder.

Next: Block-IT (HAC)