Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
packagers/windows [2020_01_14 13:11] – zim | packagers:windows [2024_03_21 18:09] – [Nasuni Access Anywhere for Windows Apps Packager] steven | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | # SME Windows | + | # Windows |
- | 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 | + | ##### Last updated |
- | Steps for running the Packager: | + | The Windows |
- | * Uninstall old SME Windows | + | |
- | * Down load and INSTALL the new SME Windows packager | + | |
- | * Launch the installed packager | + | |
- | * The launched packager | + | |
- | * 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 | + | |
- | * In the left-hand column of the packager setup page there is a list of all the previous build configurations | + | |
- | {{ :/ | + | See also: |
+ | * [[windows/ | ||
+ | |||
+ | Steps for running the Packager: | ||
+ | * Uninstall old Windows Packager, if any installed already. | ||
+ | * Down load and INSTALL the new Access Anywhere Windows Packager | ||
+ | * Launch the installed Packager | ||
+ | * 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 | ||
+ | * 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 configuration | ||
* 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: | + | {{ : |
* 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 | + | **//To generate Windows Tools from the packager there are following tabs available for setting up the configurations.// |
## General | ## General | ||
- | {{ :/packagers: | + | {{ : |
** From this Tab you can set the following options ** | ** From this Tab you can set the following options ** | ||
Line 34: | Line 37: | ||
* **Packager(Tools) name**, A name can be given to the tools generated from the packager, i.e., different tool name for each Organization or Tool version | * **Packager(Tools) name**, A name can be given to the tools generated from the packager, i.e., different tool name for each Organization or Tool version | ||
* **Cloud Api Endpoint**, In this filed you enter the Appliance url/ | * **Cloud Api Endpoint**, In this filed you enter the Appliance url/ | ||
- | * **User cannot change endpoint**, This option you can enable/ | + | * **User cannot change endpoint**, This option you can enable/ |
* **Enforce secure connection**, | * **Enforce secure connection**, | ||
* **User cannot sign up**, With this setting you enable/ | * **User cannot sign up**, With this setting you enable/ | ||
- | * **Use Windows user name as user name**, If for an organisation the windows login are the same as their SME appliance | + | * **Use Windows user name as user name**, If for an organisation the windows login are the same as their NAA Appliance |
* **Wiki URL**, Here you can enter your wiki URL for the users to access help from. | * **Wiki URL**, Here you can enter your wiki URL for the users to access help from. | ||
===== Components ===== | ===== Components ===== | ||
- | {{ :/packagers: | + | {{ : |
- | **//From this Tab you can select any or all of the following to enable for the new generated | + | From this Tab you can select any or all of the following to enable for the new generated Windows Tools: |
+ | |||
+ | | ||
+ | | ||
+ | * Cloud Drive | ||
+ | * Cloud Sync | ||
+ | * Cloud Sync Up Monitor | ||
+ | * Cloud Mail Backup | ||
+ | * Cloud Migration Assistant | ||
+ | * CloudDAV in Control Panel | ||
+ | * CloudDAV Mapper | ||
+ | * Cloud Drive context menu | ||
+ | * Cloud Drive copy hook for folder operations | ||
+ | * Cloud Drive overlaps on icons in Windows Explorer | ||
+ | * Microsoft Office Addin | ||
+ | * Microsoft Outlook Addin | ||
+ | * Open Office extension | ||
+ | * " | ||
- | * **Cloud Explorer** | ||
- | * **Cloud Edit** | ||
- | * **Cloud Drive** | ||
- | * **Cloud Sync** | ||
- | * **Cloud Sync Up Monitor** | ||
- | * **Cloud Migration Assistant** | ||
- | * **CloudDAV in Control Panel** | ||
- | * **Microsoft Office Addin** | ||
- | * **Microsoft Outlook Addin** | ||
- | * **Open Office extension** | ||
- | * **CloudDAV/ | ||
- | * **Cloud Drive icon handler for executable files** | ||
- | * **Outlook Express/ | ||
===== Local Policies ===== | ===== Local Policies ===== | ||
- | {{ : | + | {{ : |
**//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 79: | ||
===== 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 117: | ||
===== Predefined Settings ===== | ===== Predefined Settings ===== | ||
- | {{ :/packagers: | + | {{ : |
**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 === | + | The packager allows the creation of additional mapped drive letters to specific paths. |
- | * Mapping of cloud drive/s\\ {{ :/ | + | Note that the drive letters are created even if users don't have access to these paths. When the user selects these letters from within Windows Explorer an error is raised which may provider a poor user experience. |
- | * Add new drive by clicking on the '' | + | <WRAP center round important 60%> |
+ | Each mapped drive requires additional system resources. Too many drive letters can lead to the error | ||
+ | “System Error. Code: 8. Not enough memory resources are available to process this command.“ We recommend creating not more than 4 mapped drives. | ||
+ | </ | ||
+ | |||
+ | Mapping of cloud drive/s\\ {{ : | ||
+ | |||
+ | 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 139: | ||
* 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 '' | + | Edit added drive settings by highlighting the drive and clicking on **…** button |
- | | + | |
- | | + | Remove added drive by highlighting the drive an clicking |
+ | |||
+ | 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 162: | ||
===== Auto Update: ===== | ===== Auto Update: ===== | ||
- | {{ :/packagers: | + | {{ : |
**//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 152: | Line 168: | ||
==== How auto-update works: ==== | ==== How auto-update works: ==== | ||
- | Once the SME Cloud tools are installed | + | Once the NAA Cloud tools are installed |
- | * Every time SME cloud tools start, the tools automatically check for a newer version | + | * Every time NAA cloud tools start, the tools automatically check for a newer version |
* The tools also auto-check for new version every 4 hours. | * The tools also auto-check for new version every 4 hours. | ||
* Updates can also be checked manually by going to Cloud Explorer>> | * Updates can also be checked manually by going to Cloud Explorer>> | ||
* 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: | + | {{ : |
* 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 182: | ||
==== 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: | + | {{ : |
- | * Tick the checkbox for “Check for updates” | + | * Tick the checkbox for “Check for updates” |
- | {{ :/packagers: | + | {{ : |
- | * 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 NAA version for the tools. |
- | {{ :/packagers: | + | {{ : |
- | * 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: | + | {{ : |
- | * Save this file and generate a link for it. (e.g., save it to an SME account | + | * Save this file and generate a link for it. (e.g., save it to an NAA Account |
- | * 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: | + | {{ : |
* Now you can generate the tools. | * Now you can generate the tools. | ||
Line 191: | Line 207: | ||
* 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/ | Please refer to [[packagers/ | ||
+ | |||
+ | ===== Signing Packaged Tools: ===== | ||
+ | |||
+ | If you want to sign the packagedTools, | ||
+ | |||
+ | See also [[: | ||