Policies - Settings tab - Patch File Source

Policy Management > Policies > Settings tab > Patch File Source checkbox

The Patch File Source category defines, by policy, the file source for patch executable files.

• Copy packages to working directory on local drive with most free space - Patches are downloaded, or copied from a file share, to the managed machine's hard disk. Several patches, especially service packs, may require significant additional local disk space to completely install. Check this box to download patches to the working directory, but use the drive on the managed machine with the most free disk space. Uncheck this box to always use the drive specified in Working Directory for the machine ID.
• Delete package after install (from working directory) - The install package is typically deleted after the install to free up disk space. Uncheck this box to leave the package behind for debugging purposes. If the install fails and you need to verify the Command Line switches, do not delete the package so you have something to test with. The package is stored in the Working Directory on the drive specified in the previous option.
• Download from Internet if machine is unable to connect to the file server - Optionally check this box to download from the internet. This is especially useful for laptops that are disconnected from the company network but have internet access.
• Download from Internet - Each managed machine downloads the patch executable file directly from the internet at the URL specified in Patch Location.
• Pulled from system server - First the Kaseya Server checks to see if it already has a copy of the patch file. If not, the new patch executable is downloaded automatically and stored on the Kaseya Server, then used for all subsequent distributions to managed machines. When a patch needs to be installed on a managed machine, this patch file is pushed to that machine from the Kaseya Server.

  Note: The location for patch files stored on the Kaseya Server is <Kaseya installation directory>\WebPages\ManagedFiles\VSAPatchFiles\

• Pulled from file server using UNC path - This method is recommended if you support many machines on the same LAN. Patch files are downloaded to a local directory on a selected machine ID. The local directory on the machine ID is configured to be shared with other machine IDs on the same LAN. All other machine IDs on the same LAN use a UNC path to the shared folder located on the first machine ID.
  1. Identify an agent machine that will act as the file server machine for other machines on the same LAN.
  2. Create a share on the file server machine and specify the credential that will allow other machines on the same LAN to access it. This is done manually, outside of the File Source page.
  3. Set an agent credential for the file server machine with the shared directory using Agent > Manage Agents. All other machines on the same LAN will use the credential set for the file server machine to access the shared folder.
  4. Enter a UNC path to the share in the Pulled from file server using UNC path field. For example, \\computername\sharedname\dir\.

     In the next three steps you tell the VSA which machine ID is acting as the file server machine and where the shared directory is located using local file format notation.

  5. Use the Machine Group Filter drop-down list to select a group ID.
  6. Select a machine ID from the File share located on drop-down list.
  7. Enter a shared local directory in the in local directory field.

     Note: The value in the in local directory field must be in full path format, such as c:\shareddir\dir.

     When a file is downloaded, the Kaseya Server first checks to see if the patch file is already in the file share. If not, the file server machine automatically loads the patch file either directly from the internet or gets it from the Kaseya Server.

  8. File Server automatically gets patch files from - Select one of the following options:
     • the Internet - Use this setting when the file server machine has full internet access.
     • the system server - Use this setting when the file server machine is blocked from getting internet access.
• Pulled from LAN Cache - Uses the Agent > LAN Cache and Agent > Assign LAN Cache pages to manage file sourcing for patch executable files.