6.6.3.3 Remote (Target) Machine Information


   Target Machine information:


ZONE 3 is reserved to "Target Machine Information"


This information on this help page relates to the location of either the source file path or the public key file path




In case the source file and the PublicKey file (if the update is signed) are not located in the same folder with the SecureSFX file (when deployed on the TARGET Machine), the description below applies!


You may be able to specify a different path for the source file that will be update and also, a different path for the PublicKEY file.


You may set this information depending on how the files and folder are situated.


If TARGET MACHINE setup looks like the following:


Once you deploy the SecureSFX (SecureCMDLine, SecurePATCH or SecureWizard self-extracting stub installer) into the ROOT folder called herein DEMO_TARGET_LOCATION it will look for the Source file and the

PublicKey file within the same folder location (DEMO_Target_Location), finding none.


Because of this <demo> layout, on the TARGET Machine, the source file is located withing the "Source" sub-folder:



and the PublicKey file is located within the "PublicKey" sub-folder:




Therefore, for this demo case, the following settings apply:


1. Setting the SOURCE_FOLDER to APP_FOLDER (or INSTALL_FOLDER) and sub-folder "Source"

2. Setting the PUBLIC_KEY_FOLDER to APP_FOLDER (or INSTALL_FOLDER) and sub-folder "PublicKey"