Patch Mgmt > File Source
This function defines where each machine gets patch executable files from prior to installation and where these patch executables are copied on the local machine
Note: Patches are downloaded (or copied from a file share) to the local machine's hard disk. Several patches, especially service packs, also may require significant additional local disk space to completely install. Verify the machine in question has plenty of available disk space on the drive specified in the “Copy packages to temp directory on local drive with most free space” option.
Copy packages to temp directory on local drive with most free space
Before the scheduled patches are installed, they are all copied to the local computer. The default location is the temporary directory specified in Temp Directory on the local hard drive having the most free disk space. Uncheck this box to always use the temporary directory on the drive where the Agent is installed.
Delete package after install
After each patch install the patch install package is typically deleted 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 temporary directory specified in Temp Directory on the drive specified in the previous option.
Download from Internet
Each machine downloads the patch executable file directly from the internet at the URL specified in Patch Location.
Pushed from system server
First the server checks to see if it already has a copy of the server file. If not, the new patch executable is downloaded automatically by the system server, stored on the system server, and 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 system server.
Note: Default location for patch files stored on the server itself is C:\Kaseya\KaWeb\ManagedFiles\VSAPatchFiles\
Pulled from file server using UNC path
This method can be best if you support many machines on the same LAN. The patch executable file is copied from a file share accessible to this computer.
Note: The specified path to the file must be in UNC format such as \\computername\dir\.
First the server tasks the agent on the server providing the file share to see if the patch file is already in the file share. If not, the agent downloads the patch file either directly from the internet, or gets it from the system server. This procedure automatically loads all patch install files to the file share for you.
Download from the internet - Use this setting when the server running the file share has full internet access.
Download from the system server - Use this setting when the server running the file share is blocked from getting internet access.
Note: Your server MUST have access to the internet in either case, in order to download new patch files.
After the patch file has been downloaded to the file share the agent on the remote machine copies the patch install package from the file share to the \temp directory on a local disk drive with the most free space available. Connecting to a network drive requires a user credential with access rights to that file share. Two connection methods are available:
Set Credential - If a credential has been specified for this machine ID, the patch install script will use that credential to access the file share and to install the patch files.
User Logged In - If a credential has not been set for this machine ID, then a user must be logged in during the install process in order for the agent to connect to the remote file share. The patch file is then installed using the system privileges of the agent service.
Note: The file share computer must also have an agent on it. That agent automatically downloads each patch executable from the internet for later distribution to other managed machines on the network.