We need to disable patch-in-place for windows installer in 7u6.

Please refer to 7178913 for details/rationale.
What caused this requirement and why is it a stopper for 7u6?
As outlined in 7178913 (see comments above), this is a stopper because if "from7u4" and "from7u5" patches are implemented in the 7u6 release, users upgrading to 7u6 from 7u4/5 will have leftover JavaFX and Java Access Bridge files installed after uninstalling 7u6, or *any* patched release after installing the 7u6 patch.

High-level explanation of the root cause of the above:

In the case of a 7u4/5->7u6 update in which PiP is used, only the newly updated/created JRE files will be installed (notably FX and JAB). The uninstall mechanism will NOT be updated and the existing 7u4/5 uninstaller has no directive to remove the newly patched FX/JAB files.

Conversely, if an uninstall->reinstall model (no PiP) is employed for the update, the 7u6 uninstaller, which DOES have directive to remove the FX and JAB files, will be executed.

The increased cost of full image footprint (vs. PiP footprint) is offset by the following:
1. The addition of FX and JAB files bloats the PiP bundles for 7u4->7u6 and 7u5->7u6 significantly vs. typical patch bundles; 12MB and 1.5MB, repectively. Users will already experience much longer than usual download times.
2. NO 7u4->7u6 or 7u5->7u6 AU planned means descreased impact on our customers.