Presentation is loading. Please wait.

Presentation is loading. Please wait.

FileSecure Implementation Training Patch Management Version 1.1.

Similar presentations


Presentation on theme: "FileSecure Implementation Training Patch Management Version 1.1."— Presentation transcript:

1 FileSecure Implementation Training Patch Management Version 1.1

2 confidential What is a Patch ?  A Patch is a incremental change to the Desktop Client software.  A Patch comprises of two files – ­CAB file contains  Old version of the Desktop Client Component on which patch needs to be applied  New version of the Component after applying the patch  Hash digest of the RTP file ­RTP file  This contains the incremental difference of the changes to various Components  Patch is used to update the Desktop Client software to later version.  A given version of Desktop Client may require several patches to update itself to the latest version.

3 confidential Architecture of Patch Management Policy Server Folders storing patch files FileSecure Update Service Check once each day for available patches Serves the patch files Update Client Prompts User User Desktop HTTPS Connection User Desktop

4 confidential How does auto update work ? Policy Server Folders storing patch files FileSecure Update Service Check once each day for available patches Serves the patch files Update Client Prompts User User Desktop HTTPS Connection Download patches User confirms for update Download patch information Upgrade Client Request for patch file FileSecure Desktop Client is updated Version 2.13.1.0Version 2.14.0.0

5 confidential How does auto update work ?  Patch files are placed in an identified folder on the Policy Server.  Policy Server serves the files over HTTPS connection.  Desktop has a FileSecure Update Service running in the background.  The Update Service checks for any new updates on the server once each day.  If any updates are available, the service asks the Update Client to prompt the currently logged in user. If there is no user logged in then the update is skipped for the next time.  Once the user confirms, all the available patches are downloaded one by one and are updated.  It may require restart of the machine.

6 confidential Desktop Client Components  Desktop Client software consists of various components.  Each Component is identified by a unique id. End user is never exposed to this but administrator should be aware of the various components deployed in the environment so that s/he can apply relevant patches.  Default components installed for base Desktop Client – ­Core ­Customization ­Addon  Every component has it’s own version series. Versions of various components installed can be checked by running About FileSecure program from your start menu.

7 confidential Patch Management  What are different type of patches ? ­Core  This includes the core components of FileSecure that are always identical across all customers. ­Custom  This includes components that are part of standard FileSecure Desktop Client installation but are customized for a particular customer. ­Addon  This includes components that are not part of standard FileSecure Desktop Client but are developed and installed along with the Desktop Client for a particular customer. ­There could be more in future.  Does the logged in user need administrator rights ? ­No. The logged in user does not need admin rights. ­All the administrator tasks are performed with higher level privilege.

8 confidential Patch Management  Which Policy Server does the Update Service connect to ? ­The “Update URL” is configured at the time of installing the FileSecure Desktop Client. ­This may be manually entered if the installer is run in interactive mode. ­If the installer is run in silent mode, this can be passed as parameter. ­The Update URL is formed as – /upgrade ­By default, this points to https://upgrade.seclore.com/filesecure/upgrade  If I have older version of Desktop Client installer, how do I get the latest version ? ­If all the required patches are placed on the Policy Server, the Desktop Client will automatically update itself immediately after installation.

9 confidential Patch Management  Where do I place the patch files ? ­You place the patch files on the Policy Server at following location – /upgrade ­There are different folders inside this folder –  core : For core patches  customization : For customization patches  addon : For addon component patches  Separate folder for each component ­You place the files in one of the above folders depending on the type of patch.  How does the Update Service identify the relevant patches? ­It uses file naming convention to identify the relevant patch files. ­E.g. If the version of CORE is 2.13.1.0, then it looks for files “core.2.13.1.0.cab” and “2.13.1.0.rtp” in the “core” folder. ­Therefore, it is important to follow correct naming convention for the patch files.

10 confidential Patch Management  What time during the day does the Update Service updates the client ? ­The update service picks a random time between 10 AM & 6 PM (local machine time). ­This is specifically done to avoid network congestion. ­If the machine is down at that time or no user is logged in, it will try again as soon as the machine restarts or user logs in.  How do I manually update my Desktop Client ? ­You can select menu “Start -> All Programs -> Seclore -> FileSecure -> Check for updates …” ­This will prompt the Update Service to immediately look for updates on the server instead of waiting for the scheduled time. ­Rest of the process will be same as planned updates.

11 confidential Thank You ! SecLore Technology Pvt. Ltd. Website : www.seclore.comwww.seclore.com Support : support@seclore.comsupport@seclore.com Phone : +91-22-40155252


Download ppt "FileSecure Implementation Training Patch Management Version 1.1."

Similar presentations


Ads by Google