Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
packagers/windows [2020_01_14 13:11]
zim
packagers/windows [2020_07_09 00:48] (current)
steven [Predefined Settings]
Line 1: Line 1:
-SME Windows ​File Fabric Apps Packager+# File Fabric ​Windows ​Apps Packager
  
-The Packager is a desktop application that allows organizations to create pre-configured Windows Tools installers for their organizations. They can choose what components will be installed and how they will be configured. For documentation on Windows Tools see [[windowstools]].+The Windows ​Packager is a desktop application that allows organizations to create pre-configured Windows Tools installers for their organizations. They can choose what components will be installed and how they will be configured. For documentation on Windows Tools see [[windowstools]].
  
 Steps for running the Packager: Steps for running the Packager:
-  * Uninstall old SME Windows ​packager, if any installed already. +  * Uninstall old Windows ​Packager, if any installed already. 
-  * Down load and INSTALL the new SME Windows ​packager +  * Down load and INSTALL the new File Fabric ​Windows ​Packager 
-  * Launch the installed ​packager +  * Launch the installed ​Packager 
-  * The launched ​packager ​will retain all the configuration information of any previously created ​SME Windows Tools.+  * The launched ​Packager ​will retain all the configuration information of any previously created Windows Tools.
   * This information is kept in the file %AppData%\Local\SME\Cloud Apps Packager\SME.Packages.db   * This information is kept in the file %AppData%\Local\SME\Cloud Apps Packager\SME.Packages.db
-  * When packager ​is uninstalled this file is not removed and will be used by the newly installed ​packager +  * When the Packager ​is uninstalled this file is not removed and will be used by the newly installed ​Packager 
-  * In the left-hand column of the packager setup page there is a list of all the previous build configurations +  * In the left-hand column of the packager setup page there is a list of all the previous build configuration
- +
-{{ :/​packagers:​windows:​images:​sme_wpwss1.png?​nolink&​200 }} +
   * If one of these configurations is selected, then other than any new features all the previously selected options will be chosen for the new tools which can be changed before building new version.   * If one of these configurations is selected, then other than any new features all the previously selected options will be chosen for the new tools which can be changed before building new version.
  
-  * If new configurations are required then simply select New, give this configuration a name and change the settings according to your requirnment.+  * If new configurations are required then simply select New, give this configuration a name and change the settings according to your requirement\\ \\ 
  
-{{ :/packagers:​windows:​images:​sme_wpwss2.png }}+{{ :​packagers:​windows:​images:​sme_wpwss2.png?200 |}} \\ \\ 
  
   * Any existing configurations can be renamed or options from it can be changed   * Any existing configurations can be renamed or options from it can be changed
  
-**//To generate ​SME Windows Tools from the packager there are following tabs available for setting up the configurations.//​**+**//To generate Windows Tools from the packager there are following tabs available for setting up the configurations.//​**
  
 ## General ## General
  
-{{ :/packagers:​windows:​images:​sme_wpwss3.png }}+{{ :​packagers:​windows:​images:​sme_wpwss3.png?400 |}}
  
 ** From this Tab you can set the following options ** ** From this Tab you can set the following options **
Line 42: Line 39:
 ===== Components ===== ===== Components =====
  
-{{ :/packagers:​windows:​images:​sme_wpwss4.png }}+{{ :​packagers:​windows:​images:​sme_wpwss4.png?400 |}}
  
-**//From this Tab you can select any or all of the following to enable for the new generated ​SME Windows Tools://**+**//From this Tab you can select any or all of the following to enable for the new generated Windows Tools://**
  
   * **Cloud Explorer**   * **Cloud Explorer**
Line 62: Line 59:
 ===== Local Policies ===== ===== Local Policies =====
  
-{{ :​packagers:​windows:​images:​sme_wpwss5.png?​nolink&​600 ​}}+{{ :​packagers:​windows:​images:​sme_wpwss5.png?​400 |}}
  
 **//Here admin can set the local policies for the generated tools i.e., if you want to fix type of sync the tools should perform. Set default settings for the sync etc.,//** **//Here admin can set the local policies for the generated tools i.e., if you want to fix type of sync the tools should perform. Set default settings for the sync etc.,//**
Line 72: Line 69:
 ===== Block Dropbox with a Windows Firewall outbound rule ===== ===== Block Dropbox with a Windows Firewall outbound rule =====
  
-  * If selected this will block+  * If selected this will block DropBox access
  
 ===== Cloud Sync ===== ===== Cloud Sync =====
Line 110: Line 107:
 ===== Predefined Settings ===== ===== Predefined Settings =====
  
-{{ :/packagers:​windows:​images:​sme_wpwss6.png }}+{{ :​packagers:​windows:​images:​sme_wpwss6.png?400 |}}
  
 **Here you can setup the settings like number of drive mappings, Cache management etc.,** **Here you can setup the settings like number of drive mappings, Cache management etc.,**
  
-=== Cloud Drive ===+### Cloud Drive
  
-  * Mapping of cloud drive/s\\ {{ :/packagers:​windows:​images:​sme_wpwss7.png }}+Mapping of cloud drive/s\\ {{ :​packagers:​windows:​images:​sme_wpwss7.png?400 |}}
  
-  * Add new drive by clicking on the ''​%%+%%'' ​button a new window will open where you can Specify the:+Add new drive by clicking on the **+** button a new window will open where you can Specify the:
  
   * Drive Letter   * Drive Letter
Line 124: Line 121:
   * Cloud folder (leave empty for cloud root folder) to map the drive to a specific folder from Cloud.   * Cloud folder (leave empty for cloud root folder) to map the drive to a specific folder from Cloud.
  
-  * Edit added drive settings by highlighting the drive and clicking on ''​%%%%'' ​button +Edit added drive settings by highlighting the drive and clicking on **** button 
-  ​* ​Remove added drive by highlighting the drive an clicking ​''​%%-%%'' ​button+ 
 +Remove added drive by highlighting the drive an clicking ​**-** button
  
-  * Cache folder (if left empty then system cache folder is used)+Cache folder (if left empty then system cache folder is used)
  
   * In this field, you can specify full path of a customer defined cache folder   * In this field, you can specify full path of a customer defined cache folder
   * Or leave it empty for system cache folder.   * Or leave it empty for system cache folder.
  
-  * Delete cached files on shutdown+Delete cached files on shutdown
  
   * By ticking this check box the cache will be deleted when the tools are shutdown.   * By ticking this check box the cache will be deleted when the tools are shutdown.
  
-  * Folder refresh timeout+Folder refresh timeout
  
   * Here you can set how often are the folders refreshed (default 3 minutes)   * Here you can set how often are the folders refreshed (default 3 minutes)
Line 146: Line 144:
 ===== Auto Update: ===== ===== Auto Update: =====
  
-{{ :/packagers:​windows:​images:​sme_wpwss8.png }}+{{ :​packagers:​windows:​images:​sme_wpwss8.png?400 |}}
  
 **//The Windows auto-update enables the installed branded tools to check for newer version of the tools. The generated tools check for updates on startup, every 4 hours or the user can manually check for new updates from “About”//​** **//The Windows auto-update enables the installed branded tools to check for newer version of the tools. The generated tools check for updates on startup, every 4 hours or the user can manually check for new updates from “About”//​**
Line 159: Line 157:
   * If there are new versions of the tools available, a message will popup “No application(s) update found” ⁃ If there are new updates available then the user will be informed of the updates and prompted to download them.   * If there are new versions of the tools available, a message will popup “No application(s) update found” ⁃ If there are new updates available then the user will be informed of the updates and prompted to download them.
  
-{{ :/packagers:​windows:​images:​sme_wpwss9.png }}+{{ :​packagers:​windows:​images:​sme_wpwss9.png?400 |}}
  
   * If the user clicks on “Click here to download the new setup package” then new tools installer is downloaded from the link that is entered in the auto-update text file.   * If the user clicks on “Click here to download the new setup package” then new tools installer is downloaded from the link that is entered in the auto-update text file.
Line 166: Line 164:
 ==== How to setup auto-update while generating the Windows Tools: ==== ==== How to setup auto-update while generating the Windows Tools: ====
  
-  * In the packager go to the Auto Update tab+  * In the packager go to the Auto Update tab \\ 
  
-{{ :/packagers:​windows:​images:​sme_wpwss10.png }}+{{ :​packagers:​windows:​images:​sme_wpwss10.png?400 |}} \\ 
  
-  * Tick the checkbox for “Check for updates”+  * Tick the checkbox for “Check for updates” ​\\ 
  
-{{ :/packagers:​windows:​images:​sme_wpwss11.png }}+{{ :​packagers:​windows:​images:​sme_wpwss11.png?400 |}} \\ 
  
-  * In the first field for “Generated Package version” Enter your own tools version (Numerical). The second field “ Packager Version” displays the SME version for the tools.+  * In the first field for “Generated Package version” Enter your own tools version (Numerical). The second field “ Packager Version” displays the SME version for the tools. ​\\ 
  
-{{ :/packagers:​windows:​images:​sme_wpwss12.png }}+{{ :​packagers:​windows:​images:​sme_wpwss12.png?400 |}} \\ 
  
-  * Create a text file of the format: ⁃ First line containing the latest package version ⁃ Second line containing the link to the new generated package (can be left blank when you create this file) ⁃ Third line and below, contain any release notes (Optional)+  * Create a text file of the format: ⁃ First line containing the latest package version ⁃ Second line containing the link to the new generated package (can be left blank when you create this file) ⁃ Third line and below, contain any release notes (Optional). \\ 
  
-{{ :/packagers:​windows:​images:​sme_wpwss13.png }}+{{ :​packagers:​windows:​images:​sme_wpwss13.png?400 |}} \\ 
  
   * Save this file and generate a link for it. (e.g., save it to an SME account and generate and copy a URL for the file)   * Save this file and generate a link for it. (e.g., save it to an SME account and generate and copy a URL for the file)
-  * Enter the URL for the text file in the field: “ Update info file address” In the Packager.+  * Enter the URL for the text file in the field: “ Update info file address” In the Packager. ​\\ 
  
-{{ :/packagers:​windows:​images:​sme_wpwss14.png }}+{{ :​packagers:​windows:​images:​sme_wpwss14.png?400 |}} \\ 
  
   * Now you can generate the tools.   * Now you can generate the tools.
   * Save these Tools and generate a URL for them   * Save these Tools and generate a URL for them
-  * Copy the URL for the tools in the second line of the auto-update text file.+  * Copy the URL for the tools in the second line of the auto-update text file. \\ \\  ​
  
-=== CloudEdit Branding ===+=== CloudEdit Branding===
  
 Please refer to [[packagers/​cloudedit_branding|this page]]. Please refer to [[packagers/​cloudedit_branding|this page]].