Apptimized Platform User Manual On-boarding Log in Apptimized portal is available at https://app.apptimized.com/ Apptimized portal supports login via single sign-on. The Apptimized portal supports authentication via Microsoft AAD. The option to enforce authentication via Microsoft AAD is available in the organization security settings. When this option is enabled, all users of the organization are required to authenticate via Microsoft AAD. The login screen provides the Microsoft button, and local account sign-in is disabled. The account linking functionality is performed automatically during authentication. The system links the Microsoft AAD identity to the existing user account based on the matching email address. If the system cannot find a corresponding account, an error is displayed. Apptimized sends the follow-up email when the user has been accessed the Apptimized Portal: Apptimized shows the Welcome screen guide message when the user logs in: The option to disable the guide notifications is available under Do not show this message again checkbox. Note . Apptimized shows the following screen when the user logs in after registration (see Register to Apptimized Portal ): When a user does not have an assigned project, Apptimized shows the Create new page screen: A manual to create a project is available at the chapter Create project . When a user has an assigned project, Apptimized shows the Project list page screen: A project assigns to a user by a project administrator. When a user logs in after invitation via email, Apptimized shows the project user has been invited to (see Invite via email ): When a user logs in via trial account, Apptimized shows the following screen: The notification about the remaining trial period is displayed in the header: The option to cancel a subscription is available under the Your Workspace trial end in X days  button. Apptimized shows the following modal window when successful: The option to Confirm subscription cancellation is available under  Yes  button. Apptimized shows the following notification when successful: User Guides  The User Guides enable a user to check the step-by-step instruction of using the Apptimized platform and solutions. The option to check the user guides is available under the Information button. Apptimized solution guides are also available in PDF format. Solution Description User Guide Apptimized Workspace  Packaging Self-service to package and test applications from Apptimized portfolio (check the Packaging ). Apptimized Catalogue Pre-packaged applications on-demand (check the Catalogue ). Dashboard settings My Dashboard page provides information about all applications and projects that are assigned to a user or created by a user. Applications overview is available under the My Applications page: Projects overview is available under the My Projects page: The option to filter projects alphabetically (i.e., from A to Z or from Z to A) is available under the filtering symbol: Keyword search mode available ( Loupe symbol > Enter a search keyword): The option to pin a project available. The project pins when clicking on its icon: The option to unpin a project available. The project unpins when clicking on its icon: The option to extend the workspace is available under the  symbol: The workspace reverts to the initial state when clicking the  symbol. Notifications Apptimized Email notifications Apptimized provides email notifications: 1. Account activation request; 2. Account activation confirmation; 3. Account creation confirmation; 4. Password recovery; 5. Discovery/Packaging/Testing activities: The request status changes; New comment on the request; New attachment on the request 6. Update Monitoring: New version available; Application vulnerability identification. 7. Step execution (If someone in a project doesn`t have the permission to step activities); 8. Project invitation. Apptimized system notifications System notifications inform project members about system maintenance or troubles, the short-term shutdown of all or parts of the system, new releases, etc. System notifications create by a Global Administrator to all project members. Apptimized provides a system notification as a banner – a small line on the top of the page. A system notification remains pinned and available for selected users (a Global Administrator defines them) as long as a user is logged in or as long as Global Administrator set to show it. System notifications’ types are described in the table below: Table 1. Types of system notifications Notification type Description Example Blue banner This notification provides some news. Green banner This notification informs a user about success action. Yellow banner This notification warnings a user. Red banner This notification informs a user about danger or failure action. Apptimized modal window notifications Modal window notification appears when a user logs in. The option to disable the modal window notification is available under the Do not show this message again checkbox. Modal window notification appears when a user needs to confirm an action (i.e., create /delete confirmation, task finishing confirmation, task restarting confirmation, etc.). Project notification settings The project notifications settings are available in the project menu under Notifications . The screenshot below shows the default settings for the project’s notifications: To exclude notification types from the project, uncheck boxes next to the name not required in use. Review a profile The entry point to the user's profile configurations is available Apptimized portal menu under the user’s avatar and name: Apptimized shows the following screen when successful: Two options available: User profile and Portal configuration . User profile Apptimized redirects a user to SSO application when clicking the User profile option. This application enables a user: To secure login with single credentials. To configure the user’s profile settings. To export personal data. To delete an account. Portal configuration Apptimized shows the following screen when successful: Two tabs available: Notification settings and Personal access tokens . Notification settings To disable the notification, uncheck the box in front of the notification’s name not need in use. The changes to the profile apply when clicking on the Save button. Personal access tokens Personal access tokens can be used instead of a login and password for REST APIs  and transferred in the authorization header to access REST APIs. The list of personal access tokens is empty by default. The following screenshot shows the Apptimized screen when tokens exist: Tokens data is grouped into the following categories: Token name Token creation date Token expiration date Actions The option to create a token is available under the Create new token button > Create new personal access token modal window > Token name field > Token expires in (Select the value from the drop-down list) > Save button: Note. A user needs to copy the token to the clipboard before closing the modal window. This option is available under the Copy token to clipboard button or Copy icon: Apptimized shows the following notification when successful: Apptimized shows the following screen when successful: The option to delete token from user's account is available under the Actions column > Delete button > Confirm delete token modal window > Delete button. Apptimized shows the following notification: Create project The option " Create new project " is available for users with the appropriate permission level. To create a new project, click Create new project submenu in My Dashboard . Apptimized shows the following screen: “ Project information ” sets the main information for the new project. All required fields are marked with an asterisk * . The project label color is selected by clicking on the appropriate area of the color palette. The project label color is a user preference. The project label color is used to quickly identify projects on the dashboard. “ Construct your project workflow ” block sets the structure of a new project. “Import” and “ Download” steps in the new project workflow are predefined and can not be changed. Note. “ Import ” step comes with 2 predefined features ( Classic import and Import by CSV file ) and 2 additional paid features ( SCCM import and Catalogue & UM Import ). To activate SCCM import feature the SCCM Integration module must be enabled for the project. The one-time configuration is available for project administrators under Settings in the project menu > Integration > SCCM. To activate Catalogue & UM Import feature the Update monitoring/Catalog module must be enabled for the project. The one-time configuration is available for project administrators under Settings in the project menu > Update monitoring > Enable Update Monitoring / Enable vulnerability Notifications. A new step in the project workflow is created by clicking on the Add step button. Step renaming in the workflow is available by clicking on the relevant field. Exclude a step from the workflow by clicking on the bin symbol. The portal provides verification for permissions. This means that at the workflow construction stage, the user sees only those modules at the "Pick a module" box for which he has permissions. A workflow module is added when dragged and dropped from the " Pick a module " box to the workflow step. The block is removed from the project workflow when dragged and dropped from the workflow step to the " Pick a module " box. Adding steps and modules to the steps allows the user to create a multi-functional and flexible workflow. This functionality makes it possible to carry out multiple manipulations with the application within the same workflow. For example, in one step, a user can provide discovery of one application from a portfolio in Mozilla Firefox, and in another step - pack several applications from a portfolio. A workflow modules description is provided in Table 1. Table 1. Workflow modules Module name Details Discovery – Self Service A user installs an application on the chosen Microsoft Windows platform. A user automatically documents an installation, configuration, and test activities. A user can collaborate with his co-workers and Apptimized support staff. Discovery – Factory Service Apptimized installs, configures, and tests an application for a user. Apptimized documents the configuration for a user. Apptimized contacts a user if any details are needed. Packaging – Self Service A user packages the application using the Apptimized Packaging Tool. A user creates and customizes MSI package and App-V sequence. A user customizes an existing package or sequence. A user tests and debugs installations. Packaging – Factory Service Apptimized packages an application for a user. Apptimized customizes the MSI or App-V output to meet user’s requirements. Apptimized contacts a user if any details are needed while packaging an application. Apptimized notifies a user when the application is ready for testing. Testing – Self Service A user tests created packages on his own. A user runs and documents test cases. A user logs installation or functional errors. A user provides debugging guidance. Testing – Factory Service Apptimized tests created packages for a user. Apptimized runs and documents test cases based on user’s requirements. Apptimized logs installation or functional errors. Apptimized debugging guidance. Each step may have a specific set of modules (both Self Service and Factory Service). A set of modules within one step creates an ability for alternative paths of processing an application. If the step contains only one module, then the process is linear. The process reverts to the initial screen by clicking on the Cancel button and finalizes by clicking on the Create new project button. The project creation process may take a few moments. Apptimized shows the following notification when successful: Workflow Apptimized shows a container-only workflow scheme after the application import is finished. The option to expand a workflow scheme into a more detailed view is available under the  Toggle workflow scheme  button. Apptimized shows the following screen: Possible action scenarios are displayed in dashed lines when the cursor hovers over a point that represents a specific module. An information block with step progress details is available when clicking on the dots, which represent a specific module. Steps and modules that were not used (e.g., skipped) are colored in grey. The current step and the current module are highlighted in blue. The passed steps and modules are colored in green. Apptimized transition screen shows modules for the current step (on the left column) and modules for the next step (on the right column). The modules' borders to be passed are colored in grey. The modules' borders that are already passed are colored in green. Project settings Apptimized projects can be configured to meet specific needs, for instance, to deliver output meeting the user's packaging standards. Project settings are available under the Project menu > Administration > Settings . The project settings menu contains the following categories:   1. General settings: Project settings; Characters substitutions. 2. Workflow: Import; Step settings. 3. Echo; 4. Integration:  Intune; ServiceNow; SCCM. 5. Update Monitoring; 6. Storage 6. Virtualization General; Providers. 7. Apptimized TO GO. Next, each setting block is shown in more detail. General settings Project settings The “ Project settings ” block sets the primary information for the project. All required fields are marked with an asterisk *. This block corresponds to the settings of the Project information block in the Create project step. The screenshot below shows the default values of General project settings : The following additional options can be enabled: Share Portfolio with other projects within organization; Show Portfolios of other projects within organization; Enable Catalogue. To enable the option required in the project, check the box in front of the option name.  The project logo is set by clicking on the Project logo field. The project logo is user preference. The project logo is used to identify projects on the dashboard quickly. The logo must be downloaded as a PNG file only. An option to provide changes to the project workflow is available under the Edit workflow button. Apptimized shows the following screen when successful: The changes in the project workflow are applied when clicking the Edit workflow button. The changes into the Project settings are applied when clicking the Save button. Apptimized shows the following notification when successful: Character substitutions The option to specify characters and ways to substitute them is available under the “ Characters substitutions ” block. To exclude characters, uncheck the box in front of the characters not required in the project (available in the Remove column). The option to create the character substitutions is available under the plus symbol in the Actions column: Add the character in the Original character field > Add the character in the Substituted character field > Save symbol. The option to delete the character substitutions is available under the bin symbol in the Actions column. Workflow settings General The screenshot below shows the project settings for the General workflow configuration ( Workflow > General ). Setting Description Follow workflow rules Enforces the provision of a source and documentation. Can skip steps Allows moving forward in the workflow without satisfying process requirements such as providing a source, documentation, or completing the current step. Revert to Import step Allows moving backward to the start of workflow in order to replace the application source. Revert back completed apps Allows moving backward from the final workflow step to change applications that are already marked as completed. Import The screenshot below shows the default values of the project settings ( Workflow > Import ). The following settings are available under the Import settings block: Allow source change by other modules This setting enables or restricts synchronization of source files from the VM to the portal. If enabled, files placed in the Source or SourceImport drive are uploaded to the portal after VM termination and overwrite existing sources with the same name. If disabled, files placed in the drive are not uploaded and are discarded. The following settings available under  File Upload fields & Metadata blocks. All required fields are marked with an asterisk *:   Setting  Description  Installation source   This setting enables a field for source file uploading if switched on.   Documentations/Instructions This settings enables a user to add the Discovery document field to upload the discovery document under it.   Mandatory   This setting enables a user to make the Discovery document setting as mandatory. This setting displays only if Discovery document setting switched on.   Application icon for Intune   This setting enables a user to add the Application icon for Intune field to upload the Icon for the application and made it available during the Intune push (see https://docs.apptimized.com/books/apptimized-platform-admin-manual/page/upload-package-to-the-microsoft-intune-from-the-apptimized-portal)   Mandatory   This setting enables a user to make the Application icon for Intune setting as mandatory. This setting displays only if Application icon for Intune setting switched on.   Application owner This setting enables Application owner field under application metadata , and enables additional project   permissions under role permissions list   Mandatory This setting enables a user to make the Application owner as mandatory . This setting displays only if Application owner setting switched on .   Architecture This setting enables the Architecture field under application metadata and allows defining the application architecture. A user can set the language codes in the Metadata  block. The following language codes available: Language code Description Example Keep original Apptimized saves the language code value a user indicated on the Import step English (US) ISO 639-1 (Uppercase) A two-character code set entered with uppercase letters EN ISO 639-1 (Capitalize case) A two-character code set entered with the capitalized letter En ISO 639-2 (Uppercase) A three-character code set. Begins with a capital letter ENG ISO 639-2 (Capitalize case) A three-character code set. Begins with a capital letter Eng The default value is Keep original . A user can set the custom fields that required at Import step. These settings are available under “ Custom  fields ” block. Additional fields are used for: providing additional information on each application to empower management within the project; expanding application management  functionality; creating custom dashboards; sorting / grouping / filtering data. The Custom fields section is displayed in 2 blocks:    Information block – this block contains detailed information about Custom fields entries;   Action block – this block provides options to interact with the Custom fields.   Custom fields data is grouped into the following categories:   Category  Description  Name   Indicates the name of the Custom field   Type   Indicates the type of Custom field. The following types are available:   Input   Select   Multiple select   Data type   Indicates the data type of Custom field. The following types are available:   Integer   Text   DateTime   Boolean   Html   Note.   Data type  is available only if the  Input  type was selected.   Source type   Indicates the source type of Custom field. The following types are available:   Custom   Applications   Users   Note.   Source type  is available only if the  Select  &  Multiple select  types were selected.   Required   Indicates the status of the custom field. The following statuses are available:   Yes   No   The number of items per page can be changed to 10, 50, 100, or all items.   The option to move on a next/previous page is available under Next / Prev  buttons   The option to add a Custom field is available under the Add  button.   Apptimized shows the following screen when successful:   The option to add custom field is available after setting  Name, Field Type & Data type  fields and selecting  Required  selector. Note.   Custom field options  section becomes available only if  Select  option was selected under the  Field type  dropdown list &  Custom  option was selected under the  Source type  dropdown list.   The option to add  Customfieldoptions parameter is available after setting  Display & Value fields. The custom field can be designated as required under the  Default checkbox. The option to add a new entry is available under plus button. The option to delete entry is available under  bin symbol. Apptimized shows the following notification when successful: The option to edit  Custom field  name &  Required  switch is available under  Actions  block >  Edit .   The option to remove Custom field is available under the  Actions  block >  Remove .   Apptimized shows the following modal window when successful:   To apply the settings, click the  Save  button. To revert the settings, click on the  Reset  button.   Apptimized shows the following notification when successful:   Note. When the additional field settings are applied they appear in the application metadata block (i.e., at the Import step, at the application settings screen).  Steps settings The set of workflow settings depends on workflow structure (i.e., the number of steps, the set of module types) that was configured during project creation. The screenshot below shows the examples of possible workflow settings configurations. Discovery – Self Service The screenshot below shows the default settings of the Discovery – Self Service module. All required fields are marked with an asterisk * . The option to change a module name is available under the Module name field. The default module name is Discovery – Self Service. The option to change a file name pattern is available under the Document file name pattern field. The default file name pattern is [Manufacturer]_[ProductName]_[ProductVersion].html. To insert the variable tag into the field, click the relevant variable tag from the dropdown list. The option to edit a discovery case template is available under the Edit installation document template button. Apptimized shows the following screen: For more information on how to use the template editor please refer to this user manual . To return the document to the default state, click the Restore installation document template button. To apply edits in a discovery case template, click the Save button. Settings are persisted on click to the Save button. To revert the settings, click on the  Reset  button. Apptimized shows the following notification when successful: Discovery – Factory Service The screenshot below shows the default settings of the Discovery – Factory Service module. All required fields are marked with an asterisk * . The option to change a module name is available under the Module name field. The default module name is Discovery – Factory Service. The option to set the person’s data who will receive notifications on factory requests in the project is available under “ Escalation contact's email address” and “Escalation contact's name” fields. Settings are persisted on click to the Save button. Apptimized shows the following notification when successful: Packaging – Self Service General The screenshot below shows the default settings of the Packaging – Self Service module. All required fields are marked with an asterisk * . The option to change a module name is available under the Module name field. The default module name is Packaging – Self Service. The option to change a results archive name pattern is available under the Name of results archive field. The default archive name pattern is [Manufacturer]_[ProductName]_[ProductVersion]_[PackageType].package.zip. The option to change a package folder name pattern is available under the Name of package folder field. The default package folder name pattern is [Manufacturer]_[ProductName]_[ProductVersion]. To insert the variable tag into the field, click the relevant variable tag from the dropdown list. The following additional options can be enabled: Table 2. Packaging – Self Service additional options Option Details Default value Filter system noise during recording This option allows for applying a filter (exclusion list) to automatically remove the captured system and user activity (noise). Yes and No options available. Yes – the value of this option removes redundant files and registry keys that were created by the system while recording sessions and did not relate to installing software (i.e., telemetry or diagnostics data). No – the system noise which is captured by the application packaging tool will not be removed. Yes Remove Desktop shortcuts This setting indicates the option to remove all desktop shortcuts ( Yes ) from the package or to leave desktop shortcuts in the package ( No ). Yes Produce AppV This setting indicates the option to generate a file in App-V format. Yes and No options available. No Produce VSL This setting indicates the option to generate a file in VSL format. Yes and No options available. No Produce MSIX This setting indicates the option to repackage software to MSIX format. Yes and No options available. No Produce MSI This setting indicates the option to repackage software to MSI format. Yes and No options available. When No option is chosen, a legacy setup for software will be implemented if possible. Yes To turn on the option required in the project, enable the relevant switch in front of the option name. The option to exclude shortcuts from the packaging results archive is available under the Remove shortcuts containing text field. The following options available: Readme (removing shortcuts on txt file); Release notes (removing shortcuts on the page with Release notes ); Uninstall (removing shortcuts on exe file). To exclude shortcuts from the packaging results archive, click the relevant option. Settings are persisted on click to the Save button.  To download the Packaging Self-Service settings in JSON format, click on the Download JSON button. To revert the settings, click on the Reset  button. APPV This option is disabled by default. APPV option becomes active when switched on and once the required settings are completed. The option to specify which version of App-V sequencer will be used is available under the Target App-V versions field. Every version of App-V sequencer has its own workflow and applies for different operating systems. The following Target App-V versions available: 5.1; 5.0 SP3; 5.0 SP2 Hotfix 4+; 5.0 SP1/RTM; 5.0 SP2. The default value is 5.1 . To start an application from App-V, a full load mode must be enabled. The option to enable a full load mode is available under the Require full load switch. Yes and No options available. The default value is Yes . The option to enable interaction with ActiveX is available under the Allow named objects interaction switch. Yes and No options available. The default value is No . The option to enable interaction with COM objects is available under the Allow COM interaction switch. Yes and No options available. The default value is No . The option to write inside App-V is available under the Allow write to virtual FS switch. Yes and No options available. The default value is No . VSL VSL (Virtual Software Layer) is a combination of software components that implement the concept of FS layering. Every software exists in its own container and can access files for write access only within this container unless the opposite is defined in a manifest file.  Real applications could have access to this container for reading and write access to the container content if the opposite is not prohibited in manifest and virtual files can be visible in Windows Explorer like ordinary files. VSL consists of different layers applied on top of another in order to form the package based on the containment of the container. By default, all VSL files are stored under the root directory C:\Program Files\VSL. This can be changed on a machine level, but the directory should be the same for all packages. VSL format key features: 1. ZIP archive with extensions .VSL or .VSLX; 2. Every VSL file contains layers: OS layer; Service layer; Files layer; Registry layer; Manifest layer, etc. 3. Can be contained inside MSI files for compatibility with deployment systems; 4. Is self-contained. No additional software installation is required; 5. Back compatible and non-breaking updates. This option is disabled by default. VSL option becomes active when switched on and once the required settings are completed. To insert the variable tag into the Description field, click the relevant variable tag from the dropdown list. To upload a certificate in . PFX., the Upload certificate (.pfx) field can be used. Click the Open button when the relevant file is chosen. The option to enable an embedded VSL is available under the Embedded VSL in self-contained MSI switch. On and Off options available. The default value is On . MSIX MSIX is the Windows app package format that provides a packaging experience to all Windows apps. The MSIX package format preserves the functionality of existing app packages and/or install files in addition to enabling new packaging and deployment features to Win32, WPF, and WinForm apps. This option is disabled by default. MSIX option becomes active when switched on and once the required settings are completed. All required fields are marked with an asterisk * . To insert the variable tag into the MSIX identity name and MSIX package display name fields, click the relevant variable tag from the dropdown list. The default MSIX identity name pattern is [Manufacturer]-[ProductName]-[ProductVersion] . The default MSIX package display name pattern is [ProductName]-[ProductVersion] . The option to set the certificate publisher's name is available under the Certificate publisher field. The certificate publisher's name should match the certificate subject name (If no, the package will not be signed). The certificate is used to sign the application and is uploaded for a user by default. An option to upload a . PFX certificate is available. To upload a certificate in . PFX the Upload certificate (.pfx) field can be used. Click the Open button when the relevant file is chosen. A self-signed certificate is useful for testing the application before a user is ready to publish it to the store. A user can upload a certificate with the ability to automatically and silently install a certificate for the MSIX package during the VM preparation (for all Self-Service steps: Packaging, Discovery, Testing). So that after the VM is ready, the user can run the MSIX package without additional actions related to installing the certificate. The option to set up Time Stamp Server is available under  Time Stamp Server  field. The default value is http://timestamp.sectigo.com Time Stamp Server enables a user to sign the MSIX application  package with a time-stamping protocol.   MSIX bulk conversion gives a user an ability to create MSIX application packages from an already existing one in silent mode. The option to enable a bulk conversion is available under the MSIX bulk conversation switch. Yes and No options available. The default value is No . MSI This option is enabled by default. The screenshot below shows the default settings for MSI. To insert the variable tag into the Name of MSI package and Name of MST transform fields, click the relevant variable tag from the dropdown list. The default value for MSI package is [Manufacturer]_[ProductName]_[ProductVersion].msi . The default value for MST transform is [Manufacturer]_[ProductName]_[ProductVersion].mst. This option applies if vendor MSI files were found. The option to keep the original (vendor) name of the MSI file during the creation of a transform or to rename it according to the naming conventions for the MSI file is available under the Do not rename vendor MSI name switch. This option affects the vendor MSI files that were found during the installation of the application. Yes (the vendor MSI name will not be changed) and No (the vendor MSI name will be changed according to the Packaging Guideline) options available. The default value is Yes . Installation The screenshot below shows the default settings for the Batch file tab. The option to choose the installation script type is available under the Install script type field. The following options available: Batch , PowerShell and Vbs . The default value is Batch . Table 3. MSI installation settings (the Batch file tab) Setting Details Default value Installation script name This setting indicates the file name of the generated installation command line (msiexec command line). This setting indicates a filename template for naming the .CMD file to install the package. install.cmd Installation script content This setting indicates the command line for installing the package. msiexec /i "%~dp0[MsiName]" /qn Uninstall script name This setting indicates the command line file name for the package uninstallation. uninstall.cmd Installation script content with transforms This setting indicates the command line for installing the package using the created Transform file. msiexec /x [ProductCode] /qn User interface This setting indicates which parameter will be added to the msiexec command line. The following options available: No user interface – the user interface does not show any wizard dialogue. Basic user interface – only a progress bar will be shown during the installation, with the possibility to cancel this process by the Cancel button. Basic user interface with hidden “Cancel” button – shows only progress bar without the ability to cancel the installation process. No user interface Default installation command line This setting indicates the command line for the installation of the MSI with transform. - Installation log This setting indicates the installation log mode. The following options available: None (no logging available). Basic (logging shows only errors appeared during installation/uninstallation). Full (logging shows all informational, warning, error messages during installation/uninstallation). Full Table 4. MSI installation settings (the PSADT tab) Setting Details Default value Install command This setting indicates the command line for installing the package. Execute-MSI -Action 'Install' -Path "[MsiName]" -private:$PackageName Install with transform command This setting indicates the command line for installing the package using the created Transform file. Execute-MSI -Action 'Install' -Path "[MsiName]" -Transform "[MstName]" -private:$PackageName Uninstall command This setting indicates the command line for uninstalling the package. Execute-MSI -Action 'Uninstall' -Path '[ProductCode]' -private:$PackageName Reboot required This setting indicates the reboot mode. Yes and No options available. No User interface This setting indicates which parameter will be added to the msiexec command line. The following options available: No user interface – the user interface does not show any wizard dialogue. Basic user interface – only a progress bar will be shown during the installation, with the possibility to cancel this process by the Cancel button. Basic user interface with hidden “Cancel” button – shows only progress bar without the ability to cancel the installation process. No user interface Default installation command line This setting indicates the command line for the installation of the MSI with transform. - Installation log This setting indicates the installation log mode. The following options available: None (no logging available). Basic (logging shows only errors appeared during installation/uninstallation). Full (logging shows all informational, warning, error messages during installation/uninstallation). Full The option to set the package metadata is available under the module table. The following screenshot indicates the default settings for the module table. To set or change the value choose the relevant field in the module and type the value in square brackets. Table 5. MSI installation settings (the Vbs tab) Setting Details Default value Installation script name This setting indicates the file name of the generated installation command line (msiexec command line). This setting indicates a filename template for naming the .VBS file to install the package. install.vbs Installation script content This setting indicates the command line for installing package. set res = run("%windir%\system32\msiexec.exe /i " & chr(34) & "%~dp0[MsiName]" & chr(34) & " /qn", "0,3010", 0, true) wscript.quit(res.ReturnCode) Installation script content with transforms This setting indicates the command line for installing the package using the created Transform file. set res = run("%windir%\system32\msiexec.exe /i " & chr(34) & "%~dp0[MsiName]" & chr(34) & " TRANSFORMS=" & chr(34) & "%~dp0[MstName]" & chr(34) & " /qn", "0,3010", 0, true) wscript.quit(res.ReturnCode) Uninstall script name This setting indicates the file name of the generated uninstallation command line (msiexec command line). This setting indicates a filename template for naming the .VBS file to ninstall the package. uninstall.vbs Uninstall script content This setting indicates the command line for uninstalling package. set res = run("%windir%\system32\msiexec.exe /x [ProductCode] /qn", "0,3010", 0, true) wscript.quit(res.ReturnCode) User interface This setting indicates which parameter will be added to the msiexec command line. The following options available: No user interface – the user interface does not show any wizard dialogue. Basic user interface – only a progress bar will be shown during the installation, with the possibility to cancel this process by the Cancel button. Basic user interface with hidden “Cancel” button – shows only progress bar without the ability to cancel the installation process. No user interface Default installation command line This setting indicates the command line for the installation of the MSI with transform. - Installation log This setting indicates the installation log mode. The following options available: · None (no logging available). · Basic (logging shows only errors appeared during installation/uninstallation). · Full (logging shows all informational, warning, error messages during installation/uninstallation). Full The tables 6 -7 show the settings that are common for all install script types. Table 6. Installation behavior settings Setting Details Default value Installation context This setting indicates the installation context mode. The following options available: Per-user (access to a program is granted only to a user from which a program was installed); Per-machine (the package installation is required to enable all computer users to access and use the application. A per-machine installation is based on ALLUSERS property value. The per-machine installation provides changes to the system that affects all users. Standard users with limited privileges will be restricted to install a package in the per-machine context. First, obtaining permission is needed. Per-user or per-machine (If this is a per-user installation, the registry value is HKEY_CURRENT_USER ; if this is a per-machine installation, the registry value is HKEY_LOCAL_MACHINE . A per-machine installation is based on ALLUSERS property value. Per-machine Destination drive This setting indicates the drive where a package will be installed, set value for ROOTDRIVE property of MSI. The ROOTDRIVE property specifies the default drive for the destination directory of the installation. Learn more . The following options available: C:\ D:\ C:\ Table 7. Reboot settings Setting Details Default value Reboot after install This setting is based on the REBOOT property value. The REBOOT property suppresses certain prompts for a restart of the system. The following options available: Never; Always; At the end of a chain. Never Shut down any files in use This setting is based on the MSIRMSHUTDOWN property value. When the default value ( Yes ) is set, all system services and files that were shut down to install the update will be restarted. The following options available: Yes; If they are registered for a restart; Only if they have all been registered. Yes If files are in use This setting is based on MSIRESTARTMANAGERCONTROL property value. This setting enables setup authors to specify whether the package will use the Restart Manager or FileInUse Dialog to handle locked files. The following options available: Use Restart Manager; Use FilesInUse Dialog; Disable Shutdown. Use restart manager Display of reboot prompts This setting is based on REBOOTPROMPT property value. This property does not initiate a reboot if one is not needed, it only suppresses any prompts for reboots to the user. The following options available: Suppress; Do not set / Remove. Suppress ARP & Properties The screenshot below shows the default values of ARP & Properties settings. To exclude the Show in ARP , Manual repair from ARP , or Manual uninstall from ARP options, uncheck the box next to the option name not required in packaging settings. To include the Manual feature modification from ARP option to packaging settings, check the box next to the option name. Table 8. Add-Remove Program settings Setting Details Default value Show in ARP This option specifies the listing mode of the program in the ARP (Add-Remove Program) and is based on ARPSYSTEMCOMPONENT property value. When the option is enabled, the program will be listed in the Add-Remove Program. When the option is disabled, the program will be hidden in the Add-Remove Program list. Enabled Manual repair from ARP This option enables or disables the usage of the Repair button in the ARP for the package and is based on ARPNOREPAIR property value. When the option is enabled, the Repair button is added to the ARP for the package. When the option is disabled, the Repair button is removed from the ARP for the package. Enabled Manual uninstall from ARP This option enables or disables the usage of the Uninstall button in the ARP for the package and is based on ARPNOREMOVE property value. When the option is enabled, the Uninstall button is added to the ARP for the package. When the option is disabled, the Uninstall button is removed from the ARP for the package. Enabled Manual feature modification from ARP This option enables or disables the usage of the Modify button in the ARP for the package and is based on ARPNOMODIFY property value. When the option is enabled, the Modify button is added to the ARP for the package. When the option is disabled, the Modify button is removed from the ARP for the package. Disabled Installation Behaviour The option to configure default Apptimized properties is available under the  Installation Behaviour section.   The default Apptimized properties are:   ALLUSERS – indicates the application installation configuration on OS.   ROOTDRIVE – indicates the root drive of the OS for application installation.   The option to set up ALLUSERS property for installation deployment is available under  Installation   context  drop-down.   The following options available:   Per-user – specifies application  installation  under the user part of the  OS ;   Per-machine – specifies application  installation  under the system part  of the OS . (this option is set by default);   Per-user or per-machine – specifies application  installation  under user & system parts (of the OS).   The option to configure ROOTDRIVE property is available under  Destination driver  drop-down list.   The following destinations available:   C:\ - this is the default destination;   D:\.     Reboot   The option to set up reboot properties is available under  Reboot  section.   The following reboot properties available:   REBOOT – this property suppresses certain prompts for a restart of the OS;   MSIRMSHUTDOWN – this property determines how applications or services that are currentrly using files affected by an update should be  shut down  to enable the installation of the update;   MSIDISABLERMRESTART - this  property determines how applications or services that are currently using files affected by an update should be  shut down  and  restarted  to enable the installation of the update ;   MSIRESTARTMANAGERCONTROL - this property specifies whether the MSI package uses the Restart Manager or  FilesInUse Dialog  functionality;   REBOOTPROMPT - this property allows the MSI package provide reboot automatically & suppresses the display of any prompts for reboots to the users;   The option to configure REBOOT property is available under  Reboot after install  drop-down list. The following options available:   Never – declines any reboot after MSI package installation (this is the option by default);   Always – always provides reboot after MSI package installation.   At the end of a chain - declines reboot after MSI package installation by default and provides reboot if there is no user interface at each ForceReboot action.   The option to configure MSIRMSHUTDOWN property is available under  Shut down any files in use  drop-down list. The followiong options available:   Yes - indicates that processes or services that are currently using files affected by the update are shut down. This is the option by default;   If they are registered for a restart – indicates that processes or services that are currently using files affected by the update, and that do not respond to the Restart Manager, are forced to shut down;   Only if they have all been registered – indicates that processes or services that are currently using files affected by the update are shut down only if they have all been registered for a restart. If any process or service has not been registered for a restart, then no processes or services are shut down;   The option to configure applications & services behaviour with files by configuring MSIRESTARTMANAGERCONTROL property is available under  If files are in use  drop-down list. The following options available:   Use Restart Manager – indicates that Windows Installer always attempts to use the  Restart Manager . This is the option by default.   Use FilesInUse Dialog – indicates that Windows Installer always attempts to use the FilesInUse Dialog;   Disable Shutdown – indicates that Windows Installer uses FileInUse dialog by default, and uses the Restart Manager to detect files in use by applications;   The option to configure REBOOTPROMPT property is available under  Display of reboot prompts  drop-down list. The following options available:   Suppress – enables the property. This is the option by default;   Do not set / Remove – removing the property;   The option to configure MSIDISABLERMRESTART property is available under  Disable restart after installing the update  switch. The following options are:   Yes – indicates that processes that were shut down using the Restart Manager while installing the update will not be restarted after the update is applied;   No – indicates that all system services that were shut down to install the update are restarted. All applications that registered themselves with the Restart Manager are restarted. This is the option by default;   Additional properties The option to set the nonstandard properties that should be included to package is available under the Additional properties dropdown menu. This option covers the properties that will be added to the generated MSI or Transform. For example: COMPANY, USERNAME – properties, which contain company name and user’s name. They are used by some software to initialize the user’s information; ACCEPT_EULA – properties, which mean that you agree with all license agreements. The option to create the additional setting is available under the plus symbol in the Actions column: Add the setting name in the Setting field > Add the setting value in the Value field. The option to delete the additional setting is available under the bin symbol in the Actions column. The option to enable the self-healing process on application shortcuts run is available under the Advertised shortcuts switch. Yes and No options available. The default value is Yes . Files & Registry The screenshot below shows the default values of Files&Registry settings. Table 9. Files & Registry settings Setting Details Default value Cab archive name pattern This setting indicates the filename template for naming .CAB files. Cab files contain files that will be installed by MSI package. Data{0}.cab Max cab file size (in MB) These settings indicate the number of files that will be placed in a single cab file. If the size of one cab file is bigger than the provided value, it will be divided into several cab files. 2048 Max files count per cab 9999 Use embedded cab This setting sets the mode to use an embedded file. When the Use embedded cab switch is enabled a .CAB file will be implemented into .MSI . When the Use embedded cab switch is disabled a .CAB file will be outside the .MSI (external CAB). It is a compressed source (opposed to "Loose files" = uncompressed source). Yes Parse ini files to the IniFile table This option indicates the mode to parse ini files. When the Parse ini files to the IniFile table switch is enabled, the ini files will be added via an IniFile table. It is the best practice to add ini files via IniFile table because these files may contain hard-coded values, which in this case can be replaced with MSI properties. When the Parse ini files to the IniFile table switch is disabled, the ini files will be added via an File table. No Map registry data to the appropriate COM tables This setting allows identifying objects and to add them to the appropriate tables. When the Map registry data to the appropriate COM tables switch is enabled, all COM objects will be mapped to MSI via special tables designed for these objects (ProgID, Classes, etc.). It is a better way of COM objects registration according to Microsoft's best practices and helps easily navigate and manage these objects through MSI. When the Map registry data to the appropriate COM tables switch is disabled all COM objects will be added to MSI via Registry table and installed as regular registry keys. No Post process MSI filesystem & components This setting sets the File Table entries for the Language and Version fields. Learn more . Yes Mark components destined for the System folder as permanent A system folder is used by other programs. If the package contains some System folder files, they can be removed from the system during uninstallation. So, it will affect other programs that use these files. When the Mark components destined for the System folder as permanent switch is enabled, the files will be marked as permanent and won’t be removed after the package uninstalling. When the Mark components destined for the System folder as permanent switch is disabled, the files will be deleted after the package uninstalling. Yes Use Duplicate File table for user files installation Some files (.DLL, .OCX, etc.) that are installed in the Common Files folder is used by other programs. If the package contains some of these files they can be removed from the system during uninstallation. So, this affects other programs that use these files. When the Use Duplicate File table for user files installation switch is enabled, the files mark as shared. Every time when such files are installed in this folder, a counter is incremented. This counter shows how many programs use this file. When the package tries to remove this file, the counter is decremented. When this counter equals 0 this file removes from the system. Yes The option to create the кщще keys is available under the block below: Choose the root type > Fill in the Key field > Fill in the Name field > Fill in the Value field. The default value for the Key field is Software\[Manufacturer]\[ProductName]\[ProductVersion] . The default value for the Name field is DummyKey . The default value for the Value field is [PackageCode] . Per User Data This section allows creating separate registry keys for Active Setup. The screenshot below shows the default values of Per User Data settings. The option to create the separate registry keys for Active Setup is available under the Active setup switch. Yes and No options available. The default value is Yes . When the Active Setup switch is enabled, the self-healing process on the user’s logon will be implemented. This option is useful when the program has extensions or when the self-healing process on the advertised shortcut does not work. When the Active Setup switch is disabled, the self-healing process on the user’s logon will not be implemented. The options to specify the component name for active setup keys and registry keys are available in this section. The default value for the ActiveSetup component name field is ApptimizedActiveSetup . To insert the variable tag into the ActiveSetup component name field, click the relevant variable tag from the dropdown list. The option to create the registry keys is available under the plus symbol in the Actions column: Choose the root type > Fill in the Key field > Fill in the Name field > Fill in the Value field. The option to delete the registry key is available under the bin symbol in the Actions column. Branding This option enables a user to check all Apptimized packages installed on the user’s computer. If a user has installed applications to monitor, these branding keys assist a user. These keys contain all information about packages (i.e., installed date, time, manufacturer, etc.). This option is disabled by default.  When the Branding switch is enabled, the branding keys will be included to package. This option a user can use when the program has extensions or when the self-healing process on the advertised shortcut does not work. When the Branding switch is disabled, the output package will not contain any branding keys even if they are specified in the settings above. The screenshot below shows the default values of Branding settings. The options to specify the component name for active setup keys and branding keys are available in this section. The default value for the Branding component name field is ApptimizedBranding . To insert the variable tag into the Branding component name field, click the relevant variable tag from the dropdown list. The option to create the branding keys is available under the plus symbol in the Actions column: Choose the root type > Fill in the Key field > Fill in the Name field > Fill in the Value field. The option to delete the branding key is available under the bin symbol in the Actions column. Transformation This option is disabled by default. When the Skip installation during transformation switch is enabled, all changes which were implemented during installation will capture but the application will not be installed physically. Transformed will be provided based on the implemented changes. When the Skip installation during transformation switch is disabled, all changes which were implemented during installation will capture the application will be installed physically on the system. The option to download JavaScript Object Notation file is available under the Download JSON button. Settings are persisted on click to the Save button. Apptimized shows the following notification when successful: Workspace Launcher  Apptimized Workspace Launcher  is a Windows-based application that  provides a user with a packaging toolset within Apptimized cloud environment.   The Workspace Launcher section enables a user to create customizable bundles with applications available in Apptimized Workspace Launcher and share them with all users inside a project.  The created bundle(s) will appear on the VM while Packaging Self-Service (see the Packaging ). The Workspace Launcher section is available under Project Settings > Workflow > Packaging – Self Service > Workspace Launcher . Apptimized shows the following screen when successful: The option to create a new bundle is available under the Create new bundle button. Apptimized shows the following modal window: Setting Details Bundle name The bundle   name  field allows  defining  the bundle name (e.g., MSI ).   The re is no  default value  for this field .   Bundle description The bundle   description  field allows  defining  the bundle description (e.g., Tools for packaging MSI format ).   The re is no  default value  for this field .   Select categories The select categories   field allows  defining  the categories for a new bundle.  The following options available:  App-V MSI MSIX Productivity System Utility There is no default value for this field.  The option to choose multiple categories is available. Select applications The select applications   field allows  defining  the applications included in a new bundle.  The following options available:  7-Zip Adobe Creative Cloud Cleaner Tool Adobe Customization Wizard App-V 5 Configuration Editor App-V Manage Apptimized MSI Editor Apptimized Packaging Engine AppV 5.1 Sequencer Double Commander InstEd LockHunter MSIX Packaging Tool Notepad++ Process Explorer Process Monitor PsExec Resources Extract WhatChanged Orca InstallWatch There is no default value for this field.  The option to choose multiple applications is available. To apply the settings, click the  Create bundle  button.  Cancel - reverts to the Workspace Launcher section. Apptimized shows the following screen when successful: A bundle can be removed from the list by clicking on the bin symbol ( Actions column > ). A bundle can be edited by clicking on the pen symbol ( Actions column > ). The bundle settings updates are applied when clicking the Update button. Cancel - reverts to the Workspace Launcher section. Custom Actions This option is disabled by default. When the  Custom Actions  switch is enabled, the option to add additional Custom Actions becomes available. Additional Custom Actions will be added to the package under Factory Service automatically.   When the  Custom Actions  switch is disabled, there is no option to add additional Custom Actions to the package. Apptimized shows the following screen when the switch is enabled: Setting Description Action This field allows defining the name of Custom Action. Type This field allows defining the type of Custom Action. The following types available: VBS Script:   38 – Scheduling: Always;   3110 – Execution Context: Deffered, No Impersonate;   3174 – Return Processing: ContinueOnReturn, Execution Context: Deffered, No Impersonate;   Property:   51 – Set Property, Scheduling: Always.   Source This field allows defining the source property of the MSI package (i.e., ProductName). Target This field allows defining the execution parameter that depends on the basic type of custom action (i.e., Entry point).   Note.  If Target is  Null , Custom Action must contain script code.   Condition This   field   allows   defining   the   condition   under   which   the   Custom   Action   will  be  executed  ( e.g .,  Not   installed ).   Sequence This field allows defining the order in which the Custom Action will be performed. The sequence value must be more than 1500 and less than 6600. The option to add an additional field for Custom Action is available under  plus  button. Apptimized shows the following screen when successful: The option to delete the field for Custom Action is available under  bin  button: Note. There is no option to delete the initial Custom Action field. The option to apply settings is available under the  Save  button. Apptimized shows the following notification when successful: The option to download JavaScript Object Notation file is available under Download JSON button: The option to reset settings is available under Reset  button. Packaging Wrappers Wrapper templates This section enables a user: to set the PSADT templates to manage the PSADT parameters (i.e., parameters, replace items, and ZIP templates). The Packaging Wrappers section is available under Project Settings > Workflow > Packaging – Self Service > Packaging Wrappers > Wrapper templates . Apptimized shows the following screen when successful: Download default template The option to download the package wrappers default template is available under the Download default template button. The following default templates available: 1.1.10.1 (MSI, Transform, Legacy) ,  1.1.10.2 (App-V) , 1.1.11.1 (MSI, Transform, Legacy) , 1.1.12.1 (MSI, Transform, Legacy) , 1.1.12.2 (App-V) , 1.1.13.1 (MSI, Transform, Legacy) , 1.1.13.2 (App-V) . Note. After a user downloaded an archive with the default templates, it is recommended to examine the archive structure and files content. The list of placeholders to replace can be formed, or needed modifications to the archive can be provided as a result of the review. Create a new package wrapper template The option to create a new package wrapper template is available under the Create new button. Note. Based on field indicates the state of the wrapper created. The Empty   option creates wrapper without any  predefined  settings. The  Default Wrapper   option  contains predefined parameters, replace items, and templates . The options under the  Project  Wrappers   allow duplicating wrappers created previously on the project.   Note. When the new package template is created, it is recommended to implement the following sequence of actions: 1. Upload a ZIP archive with the wrapper template (see the Templates tab ) 2. Create a list of parameters (see the Parameters tab ) 3. Create a list of replaced items (see the Replace items tab ) Parameters tab This tab enables a user to set the list of parameters to customize wrapper templates. The option to create a new parameter is available under the Add parameter button. Settings Details Name This field sets the name of the created parameter (e.g., Software name ). Parameter naming is a user preference. This field is required. Required This switch allows a user to specify the parameter as required. Description A user can provide here any meaningful description to simplify the parameter's identification. Applicable for the package type This setting indicates the list of package types for which this parameter will be applicable. The following options available: MSI Transform App-V MSIX VSL The multiple-choice is available. Type This setting indicates the type of the created parameter. The following options available: String Select list Editable select list Multiple select list Boolean Date time MSI property TrimmedString The default value is String . Value This field indicates the static or dynamic generated name which a user can apply within the settings for replaced items. The following actions available: The field can stay empty (Apptimized will apply the default value) A user can hardcode the value (e.g., File Zilla 3.46 Eng ) A user can use the variables from the list below (e.g., [Manufacturer][ProductName][ProductVersion][AppLanguage] ). Values This field enables a user to create a predefined list of values (e.g., Windows 10 32 bit , Windows 10 64 bit , Language (Eng) , Language (De) , etc.). This field is disabled by default. The field becomes active when the Select list , Editable select list , or Multiple select list parameter’s type is selected. A user must provide at least one value. Order This field indicates the parameter’s position in the parameters list. This field is required. The parameter settings are applied when clicking the Create button. Apptimized shows the following notification when successful: The option to revert to the package wrapper settings screen is available under the Cancel button. Apptimized shows the following screen when successful: A parameter can be removed from the list by clicking on the bin symbol ( Actions column > ). A parameter can be edited by clicking on the pen symbol ( Actions column > ). The parameter settings updates are applied when clicking the Update button. Replace items tab This tab enables a user to set the list of placeholders to replace in the provided file types or folder names a given parameter value. The option to create a new replace element is available under the Add replace item button. Settings Details Placeholder This setting indicates the variable to be replaced in template files or folders (e.g., AppVendorShort ). This field is required. Replaced by This field indicates the static or dynamic generated name which a user can apply within the settings for replaced items. The following actions available: A user can enter the value manually. The following templates must be implemented: for files - $(ParameterName) , and for folders [ParameterName] A user can use the variables from the list below the field. Package types This setting indicates the list of package types for which this replacement item will be applicable. The following options available: MSI Transform Legacy App-V MSIX VSL The multiple-choice is available. This field is required. File extensions This field indicates the extension of a file for which the replacement rules will be applied (e.g., .PS1 or .TXT ). This field is required. The option to add a file extension is available under the plus symbol. The option to delete a file extension is available under the bin symbol. The replaced item’s settings are applied when clicking the Create button. Apptimized shows the following notification when successful: The option to revert to the package wrapper settings screen is available under the Cancel button. Apptimized shows the following screen when successful: A replaced item can be removed from the list by clicking on the bin symbol ( Actions column > ). A replaced item can be edited by clicking on the pen symbol ( Actions column > ). The replaced item’s settings updates are applied when clicking the Update button. Templates tab This tab enables a user to implement the default wrapping templates. Settings Details File path This field enables a user to define the destination of the installation file or several installation files (e.g., [packagefoldername]\package ). To define the file (s) path, a user needs to select a folder that will store the installation file or several installation files from the hierarchical folder structure on the left-hand side of the settings window. This field is required. Version This field provides information about the wrapper’s version number (e.g., 1.1.1.1 or 1.1.05.1 ). The wrapper’s version number should be represented as a four-part string with the following format: ... This field is required. Package types This setting indicates the list of package types for which this template will be applicable. The following options available: MSI Transform Legacy App-V MSIX VSL The multiple-choice is available. This field is required. Description A user can provide here any meaningful description to simplify the template's identification. The templates settings are applied when clicking the Create button. The option to revert to the package wrapper settings screen is available under the Cancel button. Apptimized shows the following notification when successful: A template can be removed from the list by clicking on the bin symbol ( Actions column > ). A template can be edited by clicking on the pen symbol ( Actions column > ). The template’s settings updates are applied when clicking the Update button. Note. If required to modify the current wrapper template or implement any changes, a user doesn't need to create a new packaging wrapper entry. A user can upload a new wrapper revision ( Template tab > Add template button). A wrapper version number update is needed. Apptimized Platform will automatically use the latest one when the wrapper template updated successfully. Intunewin This section enables a user to operate with Interactive mode during Intunewin wrapping. Interactive mode allows a user to show windows for the user during installation. Note. MSI package can't be interactive due to Intune restrictions. The option to enable Interactive mode is available via the Interactive mode switch. The option is enabled by default. Packaging – Factory Service General The screenshot below shows the default settings of the Packaging – Factory Service module. All required fields are marked with an asterisk * . The option to change a module name is available under the Module name field. The default module name is Packaging – Factory Service. The option to change a results archive name pattern is available under the Name of results archive field. The default archive name pattern is [Manufacturer]_[ProductName]_[ProductVersion]_[PackageType].package.zip. The option to change a package folder name pattern is available under the Name of package folder field. The default package folder name pattern is [Manufacturer]_[ProductName]_[ProductVersion]. To insert the variable tag into the field, click the relevant variable tag from the dropdown list. The following additional options can be enabled: Table 10. Packaging – Factory Service additional options Option Details Default value Filter system noise during recording This option allows for applying a filter (exclusion list) to automatically remove the captured system and user activity (noise). Yes and No options available. Yes – the value of this option removes redundant files and registry keys that were created by the system while recording sessions and did not relate to installing software (i.e., telemetry or diagnostics data). No – the system noise which is captured by the application packaging tool will not be removed. Yes Remove Desktop shortcuts This setting indicates the option to remove all desktop shortcuts ( Yes ) from the package or to leave desktop shortcuts in the package ( No ). Yes Produce AppV This setting indicates the option to generate a file in App-V format. Yes and No options available. No Produce VSL This setting indicates the option to generate a file in VSL format. Yes and No options available. No Produce MSIX This setting indicates the option to repackage software to MSIX format. Yes and No options available. No Produce MSI This setting indicates the option to repackage software to MSI format. Yes and No options available. When No option is chosen, a legacy setup for software will be implemented if possible. Yes To turn on the option required in the project, enable the relevant switch in front of the option name. The option to exclude shortcuts from the packaging results archive is available under the Remove shortcuts containing text field. The following options available: Readme (removing shortcuts on txt file); Release notes (removing shortcuts on the page with Release notes ); Uninstall (removing shortcuts on exe file). To exclude shortcuts from the packaging results archive, click the relevant option. The option to set the person’s data who will receive notifications on factory requests in the project is available under Escalation tab > “ Escalation contact's email address” and “Escalation contact's name” fields. The option to configure allowed and default operating system platforms for packaging is available under the Platforms tab. The Allowed package platforms field defines the list of operating systems permitted for package creation within the current project. Only platforms added to this field will be available for selection when submitting a packaging request. The Default package platform field defines the platform selected automatically when creating a new request. This platform must be chosen from the list specified in the Allowed package platforms field. The option to configure available packaging and wrapping formats for a project is available under the Formats tab. The Select package formats field defines which packaging technologies can be used within the project. The Select wrapper formats field defines which wrapping methods are available for packaging. The Package format and Wrapper format fields in the Defaults section define which formats are automatically selected when creating a new request. Both values must be chosen from the lists defined above. The Exclusions section allows restricting incompatible format combinations. For each wrapper format, one or several  package formats can be excluded to prevent incompatible packaging–wrapping combinations. APPV This option is disabled by default. APPV option becomes active when switched on and once the required settings are completed. The option to specify which version of App-V sequencer will be used is available under the Target App-V versions field. Every version of App-V sequencer has its own workflow and applies for different operating systems. The following Target App-V versions available: 5.1; 5.0 SP3; 5.0 SP2 Hotfix 4+; 5.0 SP1/RTM; 5.0 SP2. The default value is 5.1 . To start an application from App-V, a full load mode must be enabled. The option to enable a full load mode is available under the Require full load switch. Yes and No options available. The default value is Yes . The option to enable interaction with ActiveX is available under the Allow named objects interaction switch. Yes and No options available. The default value is No . The option to enable interaction with COM objects is available under the Allow COM interaction switch. Yes and No options available. The default value is No . The option to write inside App-V is available under the Allow write to virtual FS switch. Yes and No options available. The default value is No . VSL VSL (Virtual Software Layer) is a combination of software components that implement the concept of FS layering. Every software exists in its own container and can access files for write access only within this container unless the opposite is defined in a manifest file.  Real applications could have access to this container for reading and write access to the container content if the opposite is not prohibited in manifest and virtual files can be visible in Windows Explorer like ordinary files. VSL consists of different layers applied on top of another in order to form the package based on the containment of the container. By default, all VSL files are stored under the root directory C:\Program Files\VSL. This can be changed on a machine level, but the directory should be the same for all packages. VSL format key features: 1. ZIP archive with extensions .VSL or .VSLX; 2. Every VSL file contains layers: OS layer; Service layer; Files layer; Registry layer; Manifest layer, etc. 3. Can be contained inside MSI files for compatibility with deployment systems; 4. Is self-contained. No additional software installation is required; 5. Back compatible and non-breaking updates. This option is disabled by default. VSL option becomes active when switched on and once the required settings are completed. To insert the variable tag into the Description field, click the relevant variable tag from the dropdown list. To upload a certificate in . PFX the Upload certificate (.pfx) field can be used. Click the Open button when the relevant file is chosen. The option to enable an embedded VSL is available under the Embedded VSL in self-contained MSI switch. On and Off options available. The default value is On . MSIX MSIX is the Windows app package format that provides a packaging experience to all Windows apps. The MSIX package format preserves the functionality of existing app packages and/or install files in addition to enabling new packaging and deployment features to Win32, WPF, and WinForm apps. This option is disabled by default. MSIX option becomes active when switched on and once the required settings are completed. All required fields are marked with an asterisk * . To insert the variable tag into the MSIX identity name and MSIX package display name fields, click the relevant variable tag from the dropdown list. The default MSIX identity name pattern is [Manufacturer]-[ProductName]-[ProductVersion] . The default MSIX package display name pattern is [ProductName]-[ProductVersion] . The option to set the certificate publisher's name is available under the Certificate publisher field. The certificate publisher's name should match the certificate subject name. If no the package will not be signed. The certificate is used to sign the application and is uploaded for a user by default. An option to upload a . PFX certificate is available. To upload a certificate in . PFX the Upload certificate (.pfx) field can be used. Click the Open button when the relevant file is chosen. A self-signed certificate is useful for testing the application before a user is ready to publish it to the store. A user can upload a certificate with the ability to automatically and silently install a certificate for the MSIX package during the VM preparation (for all Self-Service steps: Packaging, Discovery, Testing). So that after the VM is ready, the user can run the MSIX package without additional actions related to installing the certificate. The option to set up Time Stamp Server is available under  Time Stamp Server  field. The default value is  http://timestamp.sectigo.com Time Stamp Server enables a user to sign the MSIX application  package with a time-stamping protocol.   MSIX bulk conversion gives a user an ability to create MSIX application packages from an already existing one in silent mode. The option to enable a bulk conversion is available under the MSIX bulk conversation switch. Yes and No options available. The default value is No . MSI This option is enabled by default. The screenshot below shows the default settings for MSI. To insert the variable tag into the Name of MSI package and Name of MST transform fields, click the relevant variable tag from the dropdown list. The default value for MSI package is [Manufacturer]_[ProductName]_[ProductVersion].msi . The default value for MST transform is [Manufacturer]_[ProductName]_[ProductVersion].mst. This option applies if vendor MSI files were found. The option to keep the original (vendor) name of the MSI file during the creation of a transform or to rename it according to the naming conventions for the MSI file is available under the Do not rename vendor MSI name switch. This option affects the vendor MSI files that were found during the installation of the application. Yes (the vendor MSI name will not be changed) and No (the vendor MSI name will be changed according to the Packaging Guideline) options available. The default value is Yes . Installation The screenshot below shows the default settings for the Batch file tab. The option to choose the installation script type is available under the Install script type field. The following options available: Batch , PowerShell and Vbs . The default value is Batch . Table 11. MSI installation settings (the Batch file tab) Setting Details Default value Installation script name This setting indicates the file name of the generated installation command line (msiexec command line). This setting indicates a filename template for naming the .CMD file to install the package. install.cmd Installation script content This setting indicates the command line for installing the package. msiexec /i "%~dp0[MsiName]" /qn Uninstall script name This setting indicates the command line file name for the package uninstallation. uninstall.cmd Installation script content with transforms This setting indicates the command line for installing the package using the created Transform file. msiexec /x [ProductCode] /qn User interface This setting indicates which parameter will be added to the msiexec command line. The following options available: No user interface – the user interface does not show any wizard dialogue. Basic user interface – only a progress bar will be shown during the installation, with the possibility to cancel this process by the Cancel button. Basic user interface with hidden “Cancel” button – shows only progress bar without the ability to cancel the installation process. No user interface Default installation command line This setting indicates the command line for the installation of the MSI with transform. - Installation log This setting indicates the installation log mode. The following options available: None (no logging available). Basic (logging shows only errors appeared during installation/uninstallation). Full (logging shows all informational, warning, error messages during installation/uninstallation). Full Table 12. MSI installation settings (the PSADT tab) Setting Details Default value Install command This setting indicates the command line for installing the package. Execute-MSI -Action 'Install' -Path "[MsiName]" -private:$PackageName Install with transform command This setting indicates the command line for installing the package using the created Transform file. Execute-MSI -Action 'Install' -Path "[MsiName]" -Transform "[MstName]" -private:$PackageName Uninstall command This setting indicates the command line for uninstalling the package. Execute-MSI -Action 'Uninstall' -Path '[ProductCode]' -private:$PackageName Reboot required This setting indicates the reboot mode. Yes and No options available. No User interface This setting indicates which parameter will be added to the msiexec command line. The following options available: No user interface – the user interface does not show any wizard dialogue. Basic user interface – only a progress bar will be shown during the installation, with the possibility to cancel this process by the Cancel button. Basic user interface with hidden “Cancel” button – shows only progress bar without the ability to cancel the installation process. No user interface Default installation command line This setting indicates the command line for the installation of the MSI with transform. - Installation log This setting indicates the installation log mode. The following options available: None (no logging available). Basic (logging shows only errors appeared during installation/uninstallation). Full (logging shows all informational, warning, error messages during installation/uninstallation). Full The option to set the package metadata is available under the module table. The following screenshot indicates the default settings for the module table. To set or change the value choose the relevant field in the module and type the value in square brackets. Table 13. MSI installation settings (the Vbs tab) Setting Details Default value Installation script name This setting indicates the file name of the generated installation command line (msiexec command line). This setting indicates a filename template for naming the .VBS file to install the package. install.vbs Installation script content This setting indicates the command line for installing package. set res = run("%windir%\system32\msiexec.exe /i " & chr(34) & "%~dp0[MsiName]" & chr(34) & " /qn", "0,3010", 0, true) wscript.quit(res.ReturnCode) Installation script content with transforms This setting indicates the command line for installing the package using the created Transform file. set res = run("%windir%\system32\msiexec.exe /i " & chr(34) & "%~dp0[MsiName]" & chr(34) & " TRANSFORMS=" & chr(34) & "%~dp0[MstName]" & chr(34) & " /qn", "0,3010", 0, true) wscript.quit(res.ReturnCode) Uninstall script name This setting indicates the file name of the generated uninstallation command line (msiexec command line). This setting indicates a filename template for naming the .VBS file to uninstall the package. uninstall.vbs Uninstall script content This setting indicates the command line for uninstalling package. set res = run("%windir%\system32\msiexec.exe /x [ProductCode] /qn", "0,3010", 0, true) wscript.quit(res.ReturnCode) User interface This setting indicates which parameter will be added to the msiexec command line. The following options available: No user interface – the user interface does not show any wizard dialogue. Basic user interface – only a progress bar will be shown during the installation, with the possibility to cancel this process by the Cancel button. Basic user interface with hidden “Cancel” button – shows only progress bar without the ability to cancel the installation process. No user interface Default installation command line This setting indicates the command line for the installation of the MSI with transform. - Installation log This setting indicates the installation log mode. The following options available: None (no logging available). Basic (logging shows only errors appeared during installation/uninstallation). Full (logging shows all informational, warning, error messages during installation/uninstallation). Full The tables 14 - 15 show the settings that are common for all install script types. Table 14. Installation behavior settings Setting Details Default value Installation context This setting indicates the installation context mode. The following options available: Per-user (an access to a program is granted only to a user from which a program was installed); Per-machine (the package installation is required to enable all computer users to access and use the application. A per-machine installation is based on ALLUSERS property value. The per-machine installation provides changes to the system that affects all users. Standard users with limited privileges will be restricted to install a package in the per-machine context. First obtaining permission is needed. Per-user or per-machine (If this is a per-user installation, the registry value is HKEY_CURRENT_USER ; if this is a per-machine installation, the registry value is HKEY_LOCAL_MACHINE . A per-machine installation is based on ALLUSERS property value. Per-machine Destination drive This setting indicates the drive where a package will be installed, set value for ROOTDRIVE property of MSI. The ROOTDRIVE property specifies the default drive for the destination directory of the installation. Learn more . The following options available: C:\ D:\ C:\ Table 15. Reboot settings Setting Details Default value Reboot after install This setting is based on the REBOOT property value. The REBOOT property suppresses certain prompts for a restart of the system. The following options available: Never; Always; At the end of a chain. Never Shut down any files in use This setting is based on the MSIRMSHUTDOWN property value. When the default value ( Yes ) is set, all system services and files that were shut down to install the update will be restarted. The following options available: Yes; If they are registered for a restart; Only if they have all been registered. YesThis setting is If files are in use This setting is based on MSIRESTARTMANAGERCONTROL property value. This setting enables setup authors to specify whether the package will use the Restart Manager or FileInUse Dialog to handle locked files. The following options available: Use Restart Manager; Use FilesInUse Dialog; Disable Shutdown. Use restart manager Display of reboot prompts This setting is based on REBOOTPROMPT property value. This property does not initiate a reboot if one is not needed, it only suppresses any prompts for reboots to the user. The following options available: Suppress; Do not set / Remove. Suppress ARP & Properties The screenshot below shows the default values of ARP & Properties settings. To exclude the Show ARP , Manual repair from ARP , or Manual uninstall from ARP options, uncheck the box next to the option name not required in packaging settings. To include the Manual feature modification from ARP option to packaging settings, check the box next to the option name. Table 16. Add-Remove Program settings Setting Details Default value Show ARP This option specifies the listing mode of the program in the ARP (Add-Remove Program) and is based on ARPSYSTEMCOMPONENT property value. When the option is enabled, the program will be listed in the Add-Remove Program. When the option is disabled, the program will be hidden in the Add-Remove Program list. Enabled Manual repair from ARP This option enables or disables the usage of the Repair button in the ARP for the package and is based on ARPNOREPAIR property value. When the option is enabled, the Repair button is added to the ARP for the package. When the option is disabled, the Repair button is removed from the ARP for the package. Enabled Manual uninstall from ARP This option enables or disables the usage of the Uninstall button in the ARP for the package and is based on ARPNOREMOVE property value. When the option is enabled the Uninstall button, is added to the ARP for the package. When the option is disabled the Uninstall button, is removed from the ARP for the package. Enabled Manual feature modification from ARP This option enables or disables the usage of the Modify button in the ARP for the package and is based on ARPNOMODIFY property value. When the option is enabled, the Modify button is added to the ARP for the package. When the option is disabled, the Modify button is removed from the ARP for the package. Disabled Additional properties The option to set the nonstandard properties that should be included to package is available under the Additional properties dropdown menu. This option covers the properties that will be added to the generated MSI or Transform. For example: COMPANY, USERNAME – properties, which contain company name and user’s name. They are used by some software to initialize the user’s information; ACCEPT_EULA – properties, which mean that you agree with all license agreements. The option to create the additional setting is available under the plus symbol in the Actions column: Add the setting name in the Setting field > Add the setting value in the Value field. The option to delete the additional setting is available under the bin symbol in the Actions column. The option to enable the self-healing process on application shortcuts run is available under the Advertised shortcuts switch. Yes and No options available. The default value is Yes . Files & Registry The screenshot below shows the default values of Files&Registry settings. Table 17. Files & Registry settings Setting Details Default value Cab archive name pattern This setting indicates the filename template for naming .CAB files. Cab files contain files that will be installed by MSI package. Data{0}.cab Max cab file size (in MB) These settings indicate the number of files that will be placed in a single cab file. If the size of one cab file is bigger than the provided value, it will be divided to several cab files. 2048 Max files count per cab 9999 Use embedded cab This setting sets the mode to use an embedded file. When the Use embedded cab switch is enabled, a .CAB file will be implemented into .MSI . When the Use embedded cab switch is disabled, a .CAB file will be outside the .MSI (external CAB). It is a compressed source (opposed to "Loose files" = uncompressed source). Yes Parse ini files to the IniFile table This option indicates the mode to parse ini files. When the Parse ini files to the IniFile table switch is enabled, the ini files will be added via an IniFile table. It is the best practice to add ini files via IniFile table because these files may contain hard-coded values which in this case can be replaced with MSI properties. When the Parse ini files to the IniFile table switch is disabled, the ini files will be added via an File table. No Map registry data to the appropriate COM tables This setting allows to identify objects and to add them to the appropriate tables. When the Map registry data to the appropriate COM tables switch is enabled, all COM objects will be mapped to MSI via special tables designed for these objects (ProgID, Classes, etc.). It is a better way of COM objects registration according to Microsoft's best practices and helps easily navigate and manage these objects through MSI. When the Map registry data to the appropriate COM tables switch is disabled, all COM objects will be added to MSI via Registry table and installed as regular registry keys. No Post process MSI filesystem & components This setting sets the File Table entries for the Language and Version fields. Learn more . Yes Mark components destined for the System folder as permanent A system folder is used by other programs. If the package contains some System folder files, they can be removed from the system during uninstallation. So, it will affect other programs that use these files. When the Mark components destined for the System folder as permanent switch is enabled, the files will be marked as permanent and won’t be removed after the package uninstalling. When the Mark components destined for the System folder as permanent switch is disabled, the files will be deleted after the package uninstalling. Yes Use Duplicate File table for user files installation Some files (.DLL, .OCX, etc.) that are installed in the Common Files folder is used by other programs. If the package contains some of these files they can be removed from the system during uninstallation. So, this affects other programs that use these files. When the Use Duplicate File table for user files installation switch is enabled, the files mark as shared. Every time when such files are installed in this folder, a counter is incremented. This counter shows how many programs use this file. When the package tries to remove this file, the counter is decremented. When this counter equals 0 this file removes from the system. Yes The option to create the кщще keys is available under the block below: Choose the root type > Fill in the Key field > Fill in the Name field > Fill in the Value field. The default value for the Key field is Software\[Manufacturer]\[ProductName]\[ProductVersion] . The default value for the Name field is DummyKey . The default value for the Value field is [PackageCode] . Per User Data This section allows creating separate registry keys for Active Setup. The screenshot below shows the default values of Per User Data settings. The option to create the separate registry keys for Active Setup is available under the Active setup switch. Yes and No options available. The default value is Yes . When the Active Setup switch is enabled, the self-healing process on the user’s logon will be implemented. This option is useful when the program has extensions or when the self-healing process on the advertised shortcut does not work. When the Active Setup switch is disabled, the self-healing process on the user’s logon will not be implemented. The options to specify the component name for active setup keys and registry keys are available in this section. The default value for the ActiveSetup component name field is ApptimizedActiveSetup . To insert the variable tag into the ActiveSetup component name field, click the relevant variable tag from the dropdown list. The option to create the registry keys is available under the plus symbol in the Actions column: Choose the root type > Fill in the Key field > Fill in the Name field > Fill in the Value field. The option to delete the registry key is available under the bin symbol in the Actions column. Branding This option enables a user to check all Apptimized packages installed on the user’s computer. If a user has installed applications to monitor, these branding keys assist a user. These keys contain all information about packages (i.e., installed date, time, manufacturer, etc.). This option is disabled by default. When the Branding switch is enabled, the branding keys will be included to package. This option a user can use when the program has extensions or when the self-healing process on the advertised shortcut does not work. When the Branding switch is disabled, the output package will not contain any branding keys even if they are specified in the settings above. The screenshot below shows the default values of Branding settings. The options to specify the component name for active setup keys and branding keys are available in this section. The default value for the Branding component name field is ApptimizedBranding . To insert the variable tag into the Branding component name field, click the relevant variable tag from the dropdown list. The option to create the branding keys is available under the plus symbol in the Actions column: Choose the root type > Fill in the Key field > Fill in the Name field > Fill in the Value field. The option to delete the branding key is available under the bin symbol in the Actions column. Transformation This option is disabled by default. When the Skip installation during transformation switch is enabled, all changes which were implemented during installation will capture but the application will not be installed physically. Transformed will be provided based on the implemented changes. When the Skip installation during transformation switch is disabled, all changes which were implemented during installation will capture the application will be installed physically on the system. The option to download JavaScript Object Notation file is available under the Download JSON button. Settings are persisted on click to the Save button. Apptimized shows the following notification when successful: Custom Actions This option is disabled by default. When the  Custom Actions  switch is enabled, the option to add additional Custom Actions becomes available. Additional Custom Actions will be added to the package under Factory Service automatically.   When the  Custom Actions  switch is disabled, there is no option to add additional Custom Actions to the package. Apptimized shows the following screen when the switch is enabled: Setting Description Action This field allows defining the name of Custom Action. Type This field allows defining the type of Custom Action. The following types available: VBS Script:   38 – Scheduling: Always;   3110 – Execution Context: Deffered, No Impersonate;   3174 – Return Processing: ContinueOnReturn, Execution Context: Deffered, No Impersonate;   Property:   51 – Set Property, Scheduling: Always.   Source This field allows defining the source property of the MSI package (i.e., ProductName). Target This field allows defining the execution parameter that depends on the basic type of custom action (i.e., Entry point).   Note.  If Target is  Null , Custom Action must contain script code.   Condition This   field   allows   defining   the   condition   under   which   the   Custom   Action   will  be  executed  ( e.g .,  Not   installed ).   Sequence This field allows defining the order in which the Custom Action will be performed. The sequence value must be more than 1500 and less than 6600. The option to add an additional field for Custom Action is available under  plus  button. Apptimized shows the following screen when successful: The option to delete the field for Custom Action is available under  bin  button: Note. There is no option to delete the initial Custom Action field. The option to apply settings is available under the  Save  button. Apptimized shows the following notification when successful: The option to download JavaScript Object Notation file is available under Download JSON button: THe option to reset settings is available under  Reset  button. Packaging Wrappers This section enables a user: to set the PSADT templates to manage the PSADT parameters (i.e., parameters, replace items, and ZIP templates). The Packaging Wrappers section is available under Project Settings > Workflow > Packaging – Self Service > Packaging Wrappers . Apptimized shows the following screen when successful: Download default template The option to download the package wrappers default template is available under the Download default template button. The following default templates available: 1.1.10.1 (MSI, Transform, Legacy) ,  1.1.10.2 (App-V) , 1.1.11.1 (MSI, Transform, Legacy) , 1.1.12.1 (MSI, Transform, Legacy) , 1.1.12.2 (App-V) , 1.1.13.1 (MSI, Transform, Legacy) , 1.1.13.2 (App-V) . Note. After a user downloaded an archive with the default templates, it is recommended to examine the archive structure and files content. The list of placeholders to replace can be formed, or needed modifications to the archive can be provided as a result of the review. Create a new package wrapper template The option to create a new package wrapper template is available under the Create new button. Note. Based on field indicates the state of the wrapper created. The Empty   option creates wrapper without any  predefined  settings. The  Default Wrapper   option  contains predefined parameters, replace items, and templates . The options under the  Project  Wrappers   allow duplicating wrappers created previously on the project.   Note. When the new package template is created, it is recommended to implement the following sequence of actions: 1. Upload a ZIP archive with the wrapper template (see the Templates tab ) 2. Create a list of parameters (see the Parameters tab ) 3. Create a list of replaced items (see the Replace items tab ) Parameters tab This tab enables a user to set the list of parameters to customize wrapper templates. The option to create a new parameter is available under the Add parameter button. Settings Details Name This field sets the name of the created parameter (e.g., Software name ). Parameter naming is a user preference. This field is required. Required This field allows a user to specify the parameter as required. Description A user can provide here any meaningful description to simplify the parameter's identification. Applicable for the package type This setting indicates the list of package types for which this parameter will be applicable. The following options available: MSI Transform App-V MSIX VSL The multiple-choice is available. Type This setting indicates the type of the created parameter. The following options available: String Select list Editable select list Multiple select list Boolean Date time MSI property TrimmedString The default value is String . Value This field indicates the static or dynamic generated name which a user can apply within the settings for replaced items. The following actions available: The field can stay empty (Apptimized will apply the default value) A user can hardcode the value (e.g., File Zilla 3.46 Eng ) A user can use the variables from the list below (e.g., [Manufacturer][ProductName][ProductVersion][AppLanguage] ). Values This field enables a user to create a predefined list of values (e.g., Windows 10 32 bit , Windows 10 64 bit , Language (Eng) , Language (De) , etc.). This field is disabled by default. The field becomes active when the Select list , Editable select list , or Multiple select list parameter’s type is selected. A user must provide at least one value. Order This field indicates the parameter’s position in the parameters list. This field is required. The parameter settings are applied when clicking the Create button. Apptimized shows the following notification when successful: The option to revert to the package wrapper settings screen is available under the Cancel button. Apptimized shows the following screen when successful: A parameter can be removed from the list by clicking on the bin symbol ( Actions column > ). A parameter can be edited by clicking on the pen symbol ( Actions column > ). The parameter settings updates are applied when clicking the Update button. Replace items tab This tab enables a user to set the list of placeholders to replace in the provided file types or folder names a given parameter value. The option to create a new replace element is available under the Add replace item button. Settings Details Placeholder This setting indicates the variable to be replaced in template files or folders (e.g., AppVendorShort ). This field is required. Replaced by This field indicates the static or dynamic generated name which a user can apply within the settings for replaced items. The following actions available: A user can enter the value manually. The following templates must be implemented: for files - $(ParameterName) , and for folders [ParameterName] A user can use the variables from the list below the field. Package types This setting indicates the list of package types for which this replacement item will be applicable. The following options available: MSI Transform Legacy App-V MSIX VSL The multiple-choice is available. This field is required. File extensions This field indicates the extension of a file for which the replacement rules will be applied (e.g., .PS1 or .TXT ). This field is required. The option to add a file extension is available under the plus symbol. The option to delete a file extension is available under the bin symbol. The replaced item’s settings are applied when clicking the Create button. Apptimized shows the following notification when successful: The option to revert to the package wrapper settings screen is available under the Cancel button. Apptimized shows the following screen when successful: A replaced item can be removed from the list by clicking on the bin symbol ( Actions column > ). A replaced item can be edited by clicking on the pen symbol ( Actions column > ). The replaced item’s settings updates are applied when clicking the Update button. Templates tab This tab enables a user to implement the default wrapping templates. Settings Details File path This field enables a user to define the destination of the installation file or several installation files (e.g., [packagefoldername]\package ). To define the file (s) path, a user needs to select a folder that will store the installation file or several installation files from the hierarchical folder structure on the left-hand side of the settings window. This field is required. Version This field provides information about the wrapper’s version number (e.g., 1.1.1.1 or 1.1.05.1 ). The wrapper’s version number should be represented as a four-part string with the following format: ... This field is required. Package types This setting indicates the list of package types for which this template will be applicable. The following options available: MSI Transform Legacy App-V MSIX VSL The multiple-choice is available. This field is required. Description A user can provide here any meaningful description to simplify the template's identification. The templates settings are applied when clicking the Create button. The option to revert to the package wrapper settings screen is available under the Cancel button. Apptimized shows the following notification when successful: A template can be removed from the list by clicking on the bin symbol ( Actions column > ). A template can be edited by clicking on the pen symbol ( Actions column > ). The template’s settings updates are applied when clicking the Update button. Note. If required to modify the current wrapper template or implement any changes, a user doesn't need to create a new packaging wrapper entry. A user can upload a new wrapper revision ( Template tab > Add template button). A wrapper version number update is needed. Apptimized Platform will automatically use the latest one when the wrapper template updated successfully. Testing – Self Service The screenshot below shows the default settings of the Testing – Self Service module. All required fields are marked with an asterisk * . The option to change a module name is available under the Module name field. The default module name is Testing – Self Service. The option to change a file name pattern is available under the Document file name pattern field. The default file name pattern is [Manufacturer]_[ProductName]_[ProductVersion].html. To insert the variable tag into the field, click the relevant variable tag from the dropdown list. The option to edit a testing case template is available under the Edit testing document template button. Apptimized shows the following screen when successful: To return the document to the default state, click the Restore testing document template button. To apply edits in a discovery case template, click the Save button. Settings are persisted on click to the Save button. To revert the settings, click on the Reset  button. Apptimized shows the following notification when successful: Testing – Factory Service The screenshot below shows the default settings of the Testing – Factory Service module. All required fields are marked with an asterisk * . The option to change a module name is available under the Module name field. The default module name is Testing – Factory Service. The option to set the person’s data who will receive notifications on factory requests in the project is available under “ Escalation contact's email address” and “Escalation contact's name” fields. Settings are persisted on click to the Save button. Apptimized shows the following notification when successful: Echo settings The option to enable Echo is available under the Echo switch. The default value is No . Apptimized shows the following screen when Echo option is enabled: The option to replay the recorded installation and configuration of the application from the initial version is available under the Enable Echo assisted playback (interactive) switch. The option is inactive by default. The option to replay the record automatically against the selected Windows OS is available under the Enable Echo automated playback (non-interactive) switch. The option is inactive by default. A playback mode enables a user to choose how to proceed with recorded test cases when the new platform (VM) is added. Three playback modes available: Automated – when a new platform (VM) is added, all possible test cases run; Opt-In – when a new platform (VM) is added, a user is notified by email to add it manually to the project; Opt-Out – when a new platform (VM) is added, a user is notified by email. A user has 48 hours to cancel prepared test cases or they run automatically. The default value is Automated . Note.   The  Playback Echo scenario from field  is required.  Apptimized  Portal shows the following error screen: Keyword search mode available: To choose an Echo platform, a user can drag and drop a suitable platform from the Available Echo platform / Available non-public Echo platforms container to the Project Echo platforms / Project non-public Echo platforms container. The option to change a file name pattern is available under the Document file name pattern field. The default file name pattern is [Manufacturer]_[ProductName]_[ProductVersion].html. The option to edit a test case template is available under the Edit test case template button. Apptimized shows the following screen when successful: To apply edits in a test case template, click the Save button. To apply the Echo settings, click the Save button. Apptimized shows the following notification when successful: Integration settings Intune Create environment Your Project → Administration → Settings → Integration → Intune → Environments → Create environment Put a name for your environment on the Apptimized Portal and press " Create ".   Then you will faced massage about that your environment was created.    Connect environment After creating your project on the Apptimized Portal you have two options for integrating your Intune environment. Apptimized – use Apptimized provided App Registration Custom – use own App Registration connection Apptimized connection In the “ Application registration type for connection ” you can choose: Connection with Application permissions Connection only with Delegated permissions  In this step, please select the desired Azure App Registration from the dropdown menu. Once selected, this action will automatically create an Enterprise Application (App Registration) in your Azure tenant. This application will integrate with your Azure services securely, and you can manage its settings and permissions within your tenant.   Then press “ Create connection ” button:   In case if you have enough permissions for this operation (Global Admin role) you will faced the next window: After pressing “Accept” connection with your environment will be created and it will back you to the your created   If all went well you would face the status - “ Connected ” And if something went wrong – “ Error ” In this case please press: “Test connection” button: It will update information aboud status of your Intune connection If status don’t change, please contact support. Also here you can see: Connection Mode : Apptimized or Custom Connected By : User who made autorization Connected At : Time when authorization was done In case if you do not have enough permissions, but your Enterprise application settings allow you request it,    you will face the next window.   After pressing “ Request approval ” email will be sent to your Admin and you will see next window. After pressing " Back to app ” you will back to the Intune Environment page.   In this case, the status will be “Not finished”. Also, you will face the next warning (it's ok). And now you need to wait approval from your Admin by Email message. Email Example: After Admin approval you will get the next message on your Email. Example:   After that you need to go to the Intune Environment setting page of your created environment and press “ Update connection ” button. If the request is approved, the status will change to “Connected”, and the environment will be ready for work. If you get the window with the approval request, it means that your request has not been approved yet or denied. In case if you do not have enough permissions and can not request it you will faced the next window:   In this case you can create this type of connection only with Global Administrator permission. Setting that allow you to request Admin consent:   Custom connection The application registration is carried out in the Microsoft Azure portal via administrative credentials. A user can choose one of the following types of accounts: A tenant admin account; A tenant user account (with the enabled “Users can register applications” setting). The option to open an application registration page is available under: Microsoft Azure portal > Azure services > App registrations ; Microsoft Azure portal > Search > Enter a search request (i.e., “App registrations”) > Select the service in the list > App registrations ; Microsoft Azure portal > Menu > All services > Enter a search request (i.e., “App registrations”) > Select the service in the list > App registrations . Microsoft Azure portal shows the screen when successful: The option to create a new application registration is available under the New registration option. Microsoft Azure portal shows the Create window when successful: To create a new application registration, a user fills in the fields in the form (see Table 1 and the Microsoft Azure manual ). Table 1. A new application registration Field name Details Name This field sets a meaningful application name to display to users (i.e., Apptimized Intune Test ) Supported accounts This option identifies types of accounts that can use the application. Three options available: Accounts in this organizational directory only; Accounts in any organizational directory; Accounts in any organizational directory and personal Microsoft accounts; Personal Microsoft account only. Redirect URI This setting is optional, and the values can be provided later.   When clicking on the Register button, Microsoft Azure portal shows the following screen: When the application is successfully registered, a user needs to make a series of settings steps, namely: To add a redirect URIs; To add new client secret string; To grant permissions to the application to call API. Next, each setting block is shown in more detail. The option to add redirect URIs to the application is available under the All services > App registrations > Select the application in the list > Manage menu > Authentication > Platform configurations > Add a platform> Web > Redirect URLs > Fill in new URI > Configure button. The following URL is required to be added:  https://app.apptimized.com/Account/AuthCode The option to add new client secret string is available under the All services > App registrations > Select the application in the list > Manage menu > Certificates & secrets > Client secrets > New client secret button > Fill in the description > Set the expiry mode > Add button. Note. When clicking on the Add button, the client secret value appears (i.e., ~_fd-Y49~haNZ~g8RbDz9yQCF4KQ__1j49 ). A user must copy the value to the clipboard to use it in the client’s application code. It becomes inaccessible once a user leaves this page. The Client secret value correlates with the Client secret field when integrating Intune into the Apptimized portal. The option to configure permissions to the application to call API is available under All services > App registrations > Select the application in the list > Manage menu > API permissions > Add a permission > Microsoft Graph . Microsoft Azure portal shows the following screen when successful: The option to set the types of permissions to the application is available under the Delegated permissions button > Select the permissions from the list > Add permissions button. The screenshot below shows the list of enabled permissions: Some delegated permissions can be consented by non-administrative users, but some higher-privileged permissions require administrator consent. The option to grant permissions is available under the Grant admin consent for [company name] button. Note. If the application runs as a background service or daemon without a signed-in user, the required option is  Application permissions . The  Applications permissions are the permissions that are used by applications that run without a signed-in user present. Using Application permissions enables Apptimized users to push packages to Intune without requiring an own Intune access or even an AAD account in the target Azure directory. By configuring the use of application permissions, the API will be authorized to push packages to Intune without requiring an authenticated AAD Intune user with adequate permissions to provide this authorization. The DeviceManagementApps  permissions in  Applications  permissions  are identical to  Delegated permissions  group. Assignment template After connecting Intune environment, "Create assignment template" is available. Configurating template window List with created templates Intune template Creating Configuration menu List with created templates ServiceNow The option is disabled by default. ServiceNow becomes active when switched on and once the required settings are completed. All required fields are marked with an asterisk * . The option to check the connection status with ServiceNow is available under the Check ServiceNow Connection button. Apptimized shows the following notification when successful: To synchronize ServiceNow data with Apptimized, a user must map ServiceNow table fields with Apptimized table fields. To add additional fields to the list, click on the plus symbol. An additional field can be excluded from the list by clicking on the bin symbol. The Original column names fields fill in with the ServiceNow system name of this value (i.e., u_app_id ). Settings are persisted on click to the Save button. Apptimized shows the following notifications when successful: SCCM The option is disabled by default. SCCM option becomes active when switched on and once the required settings are completed. General settings The one-time configuration is available for project administrators under  Settings  in the project menu >  Integration  section >  SCCM  >  General . SCCM Connector becomes active when switched on and once the required settings are completed. SCCM Connector Initial Configuration A user must follow the next steps to complete the initial configuration of the SCCM Connector: 1. Setting Environment Details Environment Name : Enter a unique name to identify this SCCM environment. Site Code : Specify the SCCM site code for the environment. 2. Configuring Proxy Settings (if required) Using Default Windows Proxy Server : Select Yes to use the default Windows proxy server. If No is selected, a Proxy Address field will appear, where you can manually enter the address of your proxy server. Using Default Windows Credentials : Select Yes to use default Windows credentials for authentication. If No is selected, Username and Password fields will appear, which must be populated with the credentials for proxy access. 3. Updating Settings Installation Type: Automatic  (updates will install automatically when available) or  Manual  (updates require manual installation). Update Types :  All Updates  (the connector will check for all available updates) or  Critical Only  (only critical updates will be checked and applied). 4. Sending News and Updates To Notification Recipient : Select a user from your project team who will receive email notifications for connector updates and API key expiration reminders. Table 18. General Settings Settings Details Environment name A unique name to identify this environment at Apptimized Portal. Site code Site codes and site names identify sites in a Configuration Manager hierarchy.  Configuration Manager Setup prompts for a site code and site name for the central administration site, and secondary site installation. Learn more. Automatic updates Indicates how a user would like Apptimized SCCM Connector application updates to be applied. The following types are: Automatic : updates will install automatically when available. Manual : updates require manual installation from Apptimized portal or directly on a target machine. When checking for updates, check for Selecting the types for updates to check for. The following types are: All updates:  the connector will check for all available updates and automatically install them if Automatic updates are enabled.  Critical only:  only critical updates will be checked and applied. Minor updates will be ignored for automatic installation. Send news and updates to Allows selecting a user from a project team who will receive email notifications for new connector update releases API key expiration reminders.  If the endpoint connects to the internet via the proxy server, the user should configure the connection by turning on  Enable proxy  and selecting  Use default windows credentials  or providing credentials in  Username  and  Password fields . Note. SCCM connector can’t use Windows default proxy settings. A user enters manually the proxy settings (which are configured on a machine) into the Apptimized portal. Generating SCCM API Key and Installing Apptimized SCCM Connector Generating SCCM API Key A user should go to the General section in the portal and select Generate SCCM API Key . A modal window titled Generate a New SCCM API Key will appear. The user has to set the Expiration date  using the calendar to specify how long the connector will be authorized to operate with this key. The user clicks Generate to create the API key. This key will be automatically applied to the connector installer. The modal can now be closed by clicking Cancel , or a .reg file containing the key can be downloaded to apply it to an existing SCCM Connector installation. When the key is generated successfully, the expiration date appears below the Generate SCCM API Key button. Additionally, a green key icon displays in the SCCM Connector Status bar, confirming the key is active. API Key Expiration Status Indicators To ensure seamless operation, the system provides visual indicators for the status of your API key. These indicators help you track the expiration of your API key and take timely action. The Save button can now be pressed to proceed with the Connector installation , or the Application or Package template configuration can be accessed. Green Status : The API key is active and valid. No action is required. Yellow Status :  The API key is nearing expiration, with 7 days or fewer remaining.  A notification email will be sent to the registered email address, alerting user to renew the key. Red Status : The API key has expired. The system will cease to function with the expired key, and an additional email notification will be sent to inform user about the expiration. API Key Expiration Display To provide users with clear visibility into the validity of their API key, the expiration date and time are displayed directly under the Generate SCCM API Key button. Email Notifications for API Key Expiration To help users manage API key validity, the system automatically sends email notifications at critical points: One Week Before Expiration : An email will be sent when the API key enters the yellow status (7 days before expiration). The email will include the expiration date and instructions for renewing the key. Upon Expiration : An email will be sent immediately after the API key enters the red status (expired). The email will inform user the key is no longer valid and provide a link or instructions for generating a new key. Downloading and Installing Apptimized SCCM Connector A user downloads Apptimized SCCM Connector installer from the portal . The user runs the installer on a machine with an access to his SCCM environment. Note . The user has to ensure this machine has network permissions and connectivity to SCCM for seamless operation. During installation, the connector will automatically apply the generated API key, or the user can use the .reg file to manually update an existing installation. SCCM Connector Application Installation To install the SCCM Connector application , a user follows the next steps: Downloading the exact installation files Downloading the ZIP archive containing the SCCM Connector installation files from the portal. Extracting the contents of the archive to a location on a machine with access to the Configuration Manager console. Running the Setup Wizard Locating the install.cmd file within the extracted folder. Right-clicking on install.cmd and select Run as Administrator to open the SCCM Connector Setup Wizard with the required administrative privileges. Clicking Next to proceed in the Setup Wizard . Selecting the Installation Type A user chooses one of the following installation options based on his requirements : If selecting Install as a Service: The connector will be installed as a Windows service, allowing it running in the background even in case no user is signed in. On the next screen the user enters an Active Directory Account Name and Password . These credentials are needed to run and install the service. The user has to ensure the account has the necessary permissions to communicate with the SCCM server. If selecting Install as an Application: The connector will be installed as a standard, which requires the user to be signed in to operate. No additional Active Directory permissions are required, and the user can proceed directly to the installation. Table 19. Types of Installation Installing as a Service Installing as an Application Description Installs the SCCM Connector as a Windows service, allowing it to run in the background, even without a signed-in user. Installs the SCCM Connector as a standard application, which requires a signed-in user to operate. Requirements Requires an Active Directory (AD) user login and password, as the service will use this account’s permissions. No additional Active Directory permissions needed. Benefits Ideal for continuous operation, such as on servers or unattended systems where minimal user interaction is desired. Suitable for personal or single-user environments where continuous background operation is unnecessary. Completing Installation After completing the steps above, the user clicks Install to proceed with the setup. Once it's installed, the user has to verify that the SCCM Connector is operational and configured correctly. Setting Up a New AD User with SCCM Permissions for SCCM Connector Service Installation To install the SCCM Connector as a service and configure it with a new AD user account with the necessary SCCM permissions, a user follows these steps: Step 1: Creating a New Active Directory User Opening Active Directory Users and Computers on a domain controller. Navigating to the Organizational Unit (OU) where the user needs to be created. Right-clicking on the OU, selecting New > User . In the New User Wizard : Entering the Full Name and User Logon Name (e.g., connector ). Clicking Next . Entering and confirming a Password for the new account. Setting password options according to user's organization policy. Clicking Next and  Finish to create the new user. Step 2: Adding User to a Group with SCCM Access Permissions In Active Directory Users and Computers , locating and right-clicking the new user, then selecting Properties . Going to the Member Of tab and clicking Add . In the Enter the object names to select field, typing the name of the AD group that has SCCM Console access (e.g., SCCM Admins or a custom group with SCCM permissions). Clicking OK to add the user to this group, then clicking Apply and OK to save the changes. Step 3: Granting the User "Log on as a Service" Permission Opening the Local Security Policy editor on the server where SCCM Connector will run: Going to Start > Run , type secpol.msc, and pressing Enter . In the Local Security Policy console, expanding Local Policies and selecting User Rights Assignment . Locating Log on as a service in the right pane and double-clicking it. Clicking Add User or Group… , entering the name of the new user (e.g., connector ), and clicking OK . Clicking Apply and OK to save. Step 4: Adding the User to SCCM Administrative Users Opening the Configuration Manager Console . Navigating to Administration > Security > Administrative Users . Clicking Add User or Group in the right pane. In the Add Administrative User dialog: Clicking Browse and selecting the AD user created (e.g., sccm_connector_user). Assigning the Application Administrator or Full Administrator role, depending on the level of access needed. Optionally, specifying which collections the user can manage. Clicking OK to add the user, closing the Administrative Users dialog. Step 5: Confirming Permissions and Testing Access Logging in to the system with SCCM access using the new AD user’s credentials or running SCCM Console from new user. Launching the SCCM Console to confirm that the user has access to SCCM functions. Proceeding with SCCM Connector installation using the Install as a Service option and input the new AD user credentials when prompted. Note . A user has to ensure that the AD account’s password doesn’t expire (if your policy allows) or consider a service account to prevent service interruptions. Verifying Service Runs Under the Correct User After SCCM Connector Installation After installing the SCCM Connector as a service, a user should confirm the service is running under the newly created Active Directory (AD) user by following these steps: Step 1: Verifying the SCCM Connector Service in Services Opening the Services Management Console : On the server where the SCCM Connector was installed, the user presses Windows + R , typing services.msc, and pressing Enter . Locating the SCCM Connector Service : Finding the service named Apptimized SCCM Connector (or a similar name depending on the installation).  3. Checking the Log On Account Right-clicking on the Apptimized SCCM Connector service and selecting Properties . Going to the Log On tab. Ensuring This account is selected and that the Account Name and Password correspond to the newly created AD user (e.g., sccm_connector_user). If the details do not match, updating the account information and click OK . Step 2: Confirming Service is Running Under the Correct User Verifying the Service is Running : In the Services window, checking the Status column to ensure the Apptimized SCCM Connector service is listed as Running . Checking Event Viewer for Errors : Pressing Windows + R , type eventvwr.msc, and pressing Enter to open the Event Viewer . Navigating to Windows Logs > Application . Looking for events related to the Apptimized SCCM Connector service. Specifically, looking for error messages or warnings that might indicate issues with permissions or the service account. Testing SCCM Connectivity : Opening the SCCM Environment Settings at Apptimized portal and verifying the connector can communicate with the SCCM server (e.g., Connector status in Sccm Connector Status Bar should be Connected ). If the connector fails to perform actions, confirming that the user account has the necessary SCCM permissions and the  Log On as a Service rights are correctly applied. Step 3: Troubleshooting Common Issues If the service doesn't start: Double-checking the AD user has the Log on as a service permission. Ensuring the password for the user account is correct and not expired. Checking the permissions on the SCCM Connector folder and files to ensure the service account has appropriate access. If the service starts, but it doesn't communicate with SCCM: Confirming the user account is a member of the correct SCCM administrative group (e.g., SCCM Admins or Application Administrator ). Ensuring the user has the correct permissions to access the necessary SCCM collections . Application Template This section allows you to configure key settings for application deployment in SCCM. Define display and localized names, add administrative comments, organize applications in SCCM folders, and set options for task sequence auto-installation and distribution management during SCCM push. They will be used as default values for push to SCCM. The option to configure SCCM application template is available under  Project settings  >  Integration >  choose  SCCM Environment  >  Application template.     Apptimized shows the following screen when successful: Application Settings Template Table 1. Application template settings  Setting Description Application Display Name ( Required ) The main name displayed for the application in the SCCM Console. This should be descriptive and easily identifiable for administrators. The default value is:  [PackageName] for Workspace can be configured in Settings > Workspace > General > Packaging — Self Service settings > Package name. Dynamic variables in fields are allowed. Localized Application Name The name shown for the application in localized language settings, if applicable. Useful for multi-language environments. The default value is:  [PackageName] for Workspace can be configured in Settings > Workspace > General > Packaging — Self Service settings > Package name. Dynamic variables in fields are allowed. Administrator Comments Notes or comments for administrators to document details about the application (e.g., purpose, version information). Dynamic variables in fields are allowed Folder for Application in SCCM Console Specifies the folder location within the SCCM Console where this application will be organized. Helps with managing and locating applications efficiently. Example: Dummy\Folder;  Dummy.  Note.  The package will be created under the root if the value is empty.  Auto Install in Task Sequence A Yes/No switch that determines whether the application is automatically included in SCCM task sequences for deployment. Copy Package to DML During SCCM Push A Yes/No switch that controls whether the application package is copied to the Distribution Management Library (DML) during the SCCM push process. Deployment Type Template Settings This setting enables a user to implement multiple deployment types by creating multiple deployment type templates within one project. This template can be selected when pushing an application to SCCM, streamlining the deployment setup. The option to enable SCCM deployment templates becomes active when all required fields in the SCCM general tab are filled in. The deployment types section is displayed in 2 blocks:  Information block – this block contains detailed information about the Deployment templates;  Actions block – this block provides the options to operate with the deployment templates.  Deployment type templates data is grouped into the following categories:  Table2. Categories  Сategory    Description    Template name  The field indicates the template name to help a user to identify templates in Apptimized portal.  Name  This field indicates the name of a deployment type.  Technology title  This field indicates the type of template installation.  Source folder  This field indicates the path to the location of the package source.  Path to executable  This field indicates the path to the location of the package source executable file.  Users actions are grouped into the following categories: Edit - enables a user to enter edit Deployment type template;  Delete - allows a user to delete the Deployment type template.  The option to Create new deployment type is available under  Create Deployment type  button. Apptimized shows the following screen when successful:  The set of SCCM deployment type template settings depends on the chosen installer type. Table 3. Deployment types template settings Settings Description Availability of settings depending on the Installer type MSI Script Installer   AppV Microsoft Application Virtualization 4 Microsoft Application Virtualization 5 Deployment type template name The field indicates the template name to help a user to identify templates in Apptimized portal. The default value is  Deployment type template name [number] . This field is required. + + + + Deployment type name This field indicates the name of a deployment type. It is implemented during SCCM application deployment process and is sent to SCCM server. A user can set the  Deployment type name  manually or use the following dynamic variables: This field is required. + + + + Path to the source This field indicates the path to the location of the package source. SCCM deployment template automatically generated this field. This field is required. + + + + Path to the executable This field indicates the path to the location of the package source executable file. A user can set the  Path to the executable  manually or use the following dynamic variables: This field is required. + + + + Copy source to file share This option allows to copy to the folder, the location of which was defined in field  Place for storing sources  in the  General  SCCM settings tab. + + + + Installer type This setting indicates the type of installer to use. The following installer types are available: MSI (Microsoft Installer) ; Script Installer ; AppV (Microsoft Application Virtualization 4) ; AppV (Microsoft Application Virtualization 5) . The default value is  Script Installer . + + + + Script type for the detection method This setting indicates the type of script content of the  detection method . The following script types for detection method are available: Powershell ; VB Script ; JScript . The default value is  Powershell .   +     Detection script content template This field specifies the script template of the detection method. It is possible to provide a custom template with mandatory variables in square brackets, indicating them in any order and quantity. The Connector replaces these variables with specific values during the deployment to SCCM. The default value is  Get-ItemProperty "HKLM:Software\[PackageName]\ [Manufacturer]\[ApplicationName]\[ApplicationVersion]" -ErrorAction SilentlyContinue | Where { $_.IsInstalled -eq 1 }   +     Persist content in the client cache This setting indicates the necessity to upload the application or package source to the client's machine or device cache. Yes  or  No  options are available. The default value is  No .   +     Installation command with parameters This setting indicates the command to run during the package installation. The default value for the Script Installer is  Deploy-Application.exe -DeploymentType Install The default value for the MSI Package is  msiexec /i "\\atd-dist01\Public\CM\DTeam\FeatureData\OSD\Tbreck\Setup1.msi" or msiexec /i "\\atd-dist01\Public\CM\DTeam\FeatureData\OSD\Tbreck\Setup1.msi" /qn + +     Uninstallation command with parameters This setting indicates the command to run during the package uninstallation. The default value is  Deploy-Application.exe -DeploymentType Uninstall   +     Installation context This option defines the context of the package installation. The following installation contexts are available: install for the system; install for a user; install for the system if a resource is a device otherwise install for the user. The default value is  Install for the system . This option corresponds to the term  Installation behaviour  in the SCCM admin console.   +     Should the user be logged on or not This option defines the required user state when the installation starts. The following options are available: only when no users are in the system; only when a user logs in; whether or not users are active in the system. The default value is  Whether or not users are active in the system . This option corresponds to the term  Logon requirement  in the SCCM admin console.   +     Installation visibility for the user This option defines the installation process visibility. The following options are available: normal; minimized; maximized; hidden. The default value is  Normal . This option corresponds to the term  Installation program visibility  in the SCCM admin console.   +     Requires user interaction This setting indicates if the user can be involved in the installation or uninstallation process. Yes  or  No  options are available. The default value is  No .   +     Identify deployment type information from a package file This setting indicates the option of a manual ( Yes ) or automatic ( No ) deployment type information identification. The default value is  No . +   + + The file where to get information This field indicates the file with the deployment type information. The following options are available: MSI file for MsiInstaller; XML manifest for AppvInstaller; AppV file for App5xInstaller. An installation type defines default value. +   + + What to do on a slow network This option specifies actions with package sources in case of a slow network. Following options are available: do nothing; download; download content for streaming. The default value is  Download . + + + + Maximum installation time (minutes) This option indicates the maximum duration per installation in minutes. The default value is  120 . + + + + Estimated installation time by default (minutes) This option indicates the estimated duration per installation in minutes. The default value is  0 . + + + + Run installation program as a 32-bit process on 64-bit client This setting forces the installer to launch as a 32-bit process on the 64-bit client. Yes  or  No  options are available. The default value is  No . + +     Administrator comments This optional field corresponds to the term  Administrator comments  in the SCCM admin console. + + + + The screenshot below shows the default values of the Deployment type template settings: Deployment Template Settings In the Deployment Templates section, a user can set up a reusable deployment template by clicking  Create Deployment . This template provides preconfigured settings for deployment, ensuring consistent application pushes to SCCM. This setting enables a user to implement single deployment by creating multiple deployment templates within one project. The option to enable SCCM deployment templates becomes active when all required fields in the SCCM general tab are filled in. The deployment types sections is displayed in 2 blocks:  Information block – this block contains detailed information about the Deployment templates;  Actions block – this block provides the options to operate with the Deployment templates.  Deployment templates data is grouped into the following categories:  Table1. Categories Сategory    Description    Template name  The field indicates the template name to help a user to identify templates in Apptimized portal.  Name  This field indicates the name of a deployment type.  Distribution group This field indicates group of users or devices where apps should be installed.  Collection type This field indicates the type of collection required for application SCCM deployment. Collection name This field indicates the collection where apps should be installed. Install or uninstall This field indicates should application be installed/uninstalled on/from client machine. Deploy purpose of the installation This field defines if application is required to be installed or user can choose. Set as default This field defines which template should be used by default for SCCM autopush. Users' actions are grouped into the following categories: Edit - enables a user to enter edit Deployment type template;  Delete - allows a user to delete the Deployment type template The settings available for each deployment template include: Table 2. Deployment Template Settings Settings Details Deployment template name A unique name for the deployment template, allowing easy identification and reuse in future application deployments to SCCM. Name of the default distribution group Indicates the default group of users or devices where to Install applications. This setting corresponds to the term " Distribution point group " in the SCCM admin console. Collection type Indicates the type of collection where apps should be installed. The following types are: Device User Collection name Indicates the collection of devices where to install applications. This setting allows you to search and select from existing SCCM collections stored in the Apptimized database. To update the stored collections, click Sync SCCM Collections to the right of the Collection Name field. This sync will retrieve the latest collections from SCCM. The date of the last successful sync is displayed below the Collection Name field, helping you track when the collections were last updated. Collection list is updated automatically weekly. Install or uninstall application This setting indicates whether a task sequence action in SCCM Console can install the application.  Yes  or  No  options are available.  Deploy purpose of the installation This option specifies whether the application deployment can is mandatory or optional.  Available  or  Required  options are available.  Settings are persisted on click to  Save  button. Apptimized shows the following notification when successful: Package template The  option   to   configure  SCCM  package   template   is   available   under   Project  settings  >  Integration > choose SCCM Environment  >   Package   template .   Apptimized shows the following screen when successful: Table 4. Package template settings   Setting   Description   Package name   This setting enables a user to set up the name for package template. This setting is  required .     The default value is:  [Manufacturer]_[ProductName]_[ProductVersion]_[AppLanguage]. Description   This setting enables a user to set an optional descriptions for the package template.   Where unzip package source   This setting enables a user to set up patch for unzipped package source files will be placed on. This section is  required .     Note.  In most cases, this field will be the same as  Source path  field value.   Use package name for the folder name   This setting enables a user to use package name as package folder name. The default value is  No .   Source path   This setting enables a user to set up folder where the source is placed in zip file. The zip file name is ignored under clarifying the source path. This setting is  required .     The default value is  [Manufacturer]_[ProductName]_[ProductVersion]_[AppLanguage]     Note. This path is relative to  Where unzip package source  field value.   Folder for package in SCCM Console   This setting enables a user to set up folder for package in SCCM Console.     Example:    Dummy\Folder;   Dummy.   Note.  The package will be created under the root if the value is empty.   Remove default User account   This setting enables a user to Remove user from Manage Access Account window, which is added to package by default.     The default value is  Yes .   Add account access   This setting enables a user to fill  Group name  and  Permission access level  fields. The default value is  Yes .   Group name   This setting enables a user to fill name of the group that will be addedd to Manage Accont Acces window of SCCM servier. The fill within form is  [domain]\[groupName] . This setting is  required .   Permission access level   This setting enables to set up permission access level for the specified user. The following levels available:   Read;   Change;   Full control;   No access.   The default value is  Read .   Set security scope   This setting enables to set up  Security scope  field to be specified.   Security scope   This setting enables a user to set up Security scope name that will be set to most (or all) packages. This setting is  required .     The default value is  Factory DPs .   Programs for packages The  created   programs   for  SCCM  packages   are   stored   under   Programs   for   packages   section .   The  option   to   create   program   is   available   under   Create   program   button . Apptimized   shows   the   following   screen   when   successful :   Table 5. Program template settings   Setting Description Program name This setting enables a user to set up the name of the program template. This setting is  required .     The default value is  Install.   Command line This setting enables a user to set up the command line of the program template.     The default value is  install.cmd   Start folder   This setting enables a user to set up he name of startup folder of the program template.   User interaction   This setting enables to set up interaction lever of user with package.   The following levels available:   Hidden;   Minimized;   Normal;   Maximized.   The default value is  Hidden .   Program can run   This setting enables a user to define run context of package. The following contexts available:   Whether or not user is logged on;   Only when user is logged on;   Only when no user is logged on.   The default value is  Whether or not user is logged on .   Run mode   This setting enables a user to define permission level of package context run. This setting is available to change only if  Only when user is logged on  setting is set under  Program can run  setting.   The following permission levels available:   Run with Administrative rights;   Run with user rights;   The default value is  Run with Administrative rights .   Allow users to view and interact with the program installation   This setting enables to allow users to view and interact with the program insallation. The default value is  No .   Drive mode   This setting enables to define drive mode of the package installation / uninstallation. The following modes available:   Runs with UNC name;   Required drive letter   Requires specific drive letter (example: Z:).   The default value is  Runs with UNC name .   Allow this program to be installed from task sequence   This setting enables to allow the program to be installaed from the Install Package task sequecne without being deployed. The default value is  No .   Select platfroms   This setting enables to select OS platforms where package can run.   The following platforms available:   All Windows 10 (64-bit);   All Windows 7 (64-bit);   All Windows 8.1 (64-bit);   All Windows Server 2008 R2 (64-bit);   All Windows Server 2012 R2 (64-bit);   All Windows Server 2016 (64-bit);   All Windows 7 (32-bit).   Note . Empty field value is allowing any platform.   Estimated disk space   This setting enables to estimate disk space for packages if required. The value if unknown is 0 or empty.   The default value is 0.   Select unit of a disk sace size   This setting enables to define unit f the disk space if the estimated disk space is set. The following units available:   KB;   MB;   GB.   The default value is  MB .   Maximum allowed run time (minutes)   This setting enables a user to set up maximum allowed run time in minutes. The default value is  120 .   Administrative comment   This optional field corresponds to the term  Administrator comments  in the SCCM admin console.   The option to save settings is available under  Save  button.   Apptimized shows the following notification when successful:   Deployment for packages Created   deployments   for   packages   are   stored   under   Deployments   for   packages   section . The  option   to   create   deployment   is   available   under   Create   deployment   button . Apptimized shows the following screen when successful: Table 6. Package deployment template settings   Setting Description Program name   This setting enables to set up program name to which deployment belongs to.   This field is  required .     The default value is  Install .   Collection type   This setting enables to indicate the collection type that will be loaded from the user SCCM server. This setting is  required . The following types are available:   Device;   User.   The default value is  Device .   Limiting collection for the deployment   This setting enables settng limiting collection for the collection deployment.   Collection folder in SCCM Console   This setting enables setting up a collection path under the SCCM console. Action   This setting enables set the action during deployment. The available action is  Install . The value can not be changed.   Purpose   This setting enables the definition of the requirement of the installation/uninstallation process. The following values are available:   Available;   Required.   The default value is  Available .   Send wake-up packets   This setting enables to define sending  wake-up packets  before deployment under SCCM.   The default value is  No .   Note. This setting is available only if  Required  purpose is set.   Allow clients on a metered internet connection to download content after the installation deadline, which right incurs additional costs   This setting enables to allow clients  on a metered internet connection to download content after the installation deadline, which right incurs additional costs.   The default value is  No .   Note. This setting is available only if  Required  purpose is set.     Rerun behavior   This setting enables to specify rerunning deployment behavior on a client.   The following values are available:   Always rerun program;   Never rerun deployed program;   Rerun if failed previous attempt;   Rerun if succeeded on the previous attempt.   The default value is  Always rerun program .   Note. This setting is available only if  Required  purpose is set.     Recur every   The setting enables to specify a recurring interval. The default value is  1 .   Note . This setting is available only if  Required  purpose is set.     Recurrence interval type   This setting enables selection of recurrence interval types for the schedule.   The following options are available:   Days;   Hours;   Minutes.   The default value is  Days .   Note . This setting is available only if  Required  purpose is set.     Schedule   This setting enables to schedule date and time for the deployment.   Note.  Time must be UTC. The time will be converted to the timezone of the User’s SCCM Server. This setting is   available only if  Required  purpose is set.   Allow users to run the program independently of assignments   This setting enables users to run the program from Software Center. The default value is  Yes . The value can not be changed.   Software installation   This setting enables a user to allow installation of the deployed software outside of maintenance windows.     The default value is  No .   System restart (if required to complete the installation)   This setting enables to set up system restarting outside a maintenance window.     The default value is  No .   Commit changes at deadline or during a maintenance window (requires restarts)   This setting enables to setting up write filters for embedded devices. The default value is  Yes .     Note . If this setting is not enabled, the content will be applied on the overlay and committed later.   Select the deployment option to use when a client uses a distribution point from a current boundary group   This setting enables to specify client behavior on a fast network. The following options are available to select:   Download content from distribution point and run locally;   Run program from the distribution point.     The default value is  Download content from distribution point and run locally .   Select the deployment option to use when a client uses a distribution point from a neighbor boundary group or the default site boundary group     This setting enables to specify client behavior on a slow network. The following options are available to select:   Download content from distribution point and run locally;   Do not run program;     The default value is  Download content from distribution point and run locally .   Allow clients to use distribution points from the default site boundary group   This setting enables allow clients to use shared content.     The default value is  No .   The option to save deployments for packages settings is available under  Save  button.   Apptimized shows the following notification when successful:   The  option   to   save   package   templates   settings   is   available   under   Save   button .   Apptimized shows the following notification when successful:   Update monitoring To receive a notification when an update or upgrade has been released by the application vendor, a user enables the Enable Update Monitoring option. To receive a notification by email when an application vulnerability is found, a user enables the Enable Vulnerability Notifications option. Settings are persisted on click to the Save button. Apptimized shows the following notification when successful: Storage The option to manage the Storage option within the Project is available under the Storage tab. Apptimized shows the following screen when successful: The option activates when  Storage  switch is on. The option is disabled by default. The option to enable the Retention policy is available via Retention policy switch. The option is disabled by default. By configuring the Retention policy, all files older than the configured Retention period will be automatically deleted from the Apptimized storage. The option to enter the value under Retention period (in months) is available in the following field: The option to Save changes is available under the  Save button, to Reset - under  Reset  button Virtualization General The option to manage the Windows platforms within the Project is available under the Virtualization settings > General tab. Apptimized shows the following screen when successful: The option to add a new platform is available under the Add new platform button > Add new platform modal window > Select the value from the drop-down list in the  Select platforms field > Add button. Note. The multiple-choice option is available in the Select platforms field. For each selected item, a separate category will be created. The following Windows platforms available: Windows 7 DE Windows 7 64-bit EN Windows 10 64 bit EN (1809) Windows 10 64 bit EN (1607) Windows 10 64 bit DE (1607) Windows 10 (1809) DE The option to delete the Windows platform from the list within the Project is available under the Delete button > Confirm delete platform modal window > Delete button.  To enable the Windows platform required in the self-service module, check the box in front of the platform name. To apply the virtualization general settings, click the Save button. Providers Azure switch Note.  The Azure-side configuration is available under Azure Tenant VDI Provider Integration The Azure virtualization provider activates when the Azure switch is enabled. All required fields are marked with an asterisk * . The option is disabled by default. Table 21. Azure virtualization provider settings Setting Details Azure subscription name This setting indicates the name of user’s Azure subscription ( portal.azure.com > Subscription > Subscription name ). Subscription Id This setting indicates the user’s subscription Id in Azure ( portal.azure.com > Subscription > Subscription Id ). Client Id This setting indicates the user (application) Id from Azure Active directory. Client Secret This setting indicates the client secret of the application from Azure Active directory. It is a secret string that an application uses to prove its identity when requesting a token. Also, it can be referred to as an application password. Tenant Id This setting indicates the directory (Tenant) Id of Application from Azure Active Directory. Resource group This setting indicates the resource group from portal.azure.com . It is a container that keeps related resources for an Azure solution. Region This setting indicates the region of a resource group at portal.azure.com . Network name This setting indicates the virtual network name from portal.azure.com. Subnet name This setting indicates the subnet name the virtual network from portal.azure.com . VM size This setting indicates a disk size of the VM. VM disk size depends on a user subscription type. The following types of sizes available: General purpose; Compute optimized; Memory optimized Storage optimized; GPU; High performance compute Learn more . Note . It is necessary to select the size of the VM's that supports Generation 1 and 2 if any will be used. OS disk type This setting indicates a disk type of the VM.   The following types available:   Standard HDD;   Standard SSD;   Premium SSD;   Ultra disk.   VMs limit This setting indicates a maximum number of currently running VMs. Yes or No options are available. The default value is No . When the VMs limit switch is activated, a user must enter a number in the Maximum number of currently running VMs field. The option to save settings is available under the  Save button. The option to add a new Azure image is available under the Create new image button. Note . The option to add a new Azure image becomes available after the  Azure switch  settings were set up. Apptimized shows the following modal window: All required fields are marked with an asterisk * . Table 22. Azure image settings Setting Description Name This setting defines the name for a new Azure image. The naming is a user preference. Platform This setting defines the name of Windows platform (i.e., Windows 10 ). OS Build This setting defines the operating system build that will be used (i.e., 18363.753 – is an OS build for Windows 10, version 1909). OS build is a timeline of minor build releases in between the major version number releases. OS Version This setting defines the operation system version that will be used. The following options available: Windows 7; Windows 8; Windows 10. The default value is Windows 10 . OS Language This setting defines the operating system language mode. The following options available: EN; DE. The default value is EN . OS type This setting defines the operating system type mode. The following options available: Windows Server; Desktop Windows. The default value is Windows Server . Enabled This setting indicates that the current image is enabled for use. Disk generation This setting defines the Hyper-V virtual machine generation. The following options available: V1; V2. Link to VHD / Snapshot name This setting indicates the link to VHD / Snapshot that is stored on portal.azure.com storage. Windows username This setting is automatically prefilling with the project creator data (i.e., test.account@apptimized.com ). Setting a Windows username is a user preference and the automatically prefilling data can be changed. Password for log in This setting is automatically prefilling with the project creator data. Setting a login password is a user preference and the automatically prefilling data can be changed. The Azure image creates when clicking the Create button. To Go switch The To Go virtualization provider activates when the To Go switch is enabled. All required fields are marked with an asterisk * . The option is disabled by default. This switch enables the TO GO hypervisor connector implementation within the project. The option to specify within what workflow step the TO GO hypervisor connector will be implemented enables when the switch is activated in front of the step name. The  User name  and  Password fields come prefilled.  The Host field defines the IP address or DNS name of a resource that contains Virtual Machines (i.e.,  10.159.11.2:1233  or  somesite.hive.com ). When the value to the  Host field is added, the Create new image  button appears. The option to create a custom operating system image is available under the Create new image button. Apptimized shows the following modal window (all required fields are marked with an asterisk * ): Table 23. Image settings Setting Description Name This setting defines the name for a new Azure image. The naming is a user preference. This field is required. Platform This setting defines the name of the Windows platform (i.e., Windows 10 ). OS Build This setting defines the operating system build that will be used (i.e., 18363.753 – is an OS build for Windows 10, version 1909). OS build is a timeline of minor build releases in between the major version number releases. OS Version This setting defines the operation system version that will be used. The following options available: Windows 7; Windows 8; Windows 10. The default value is Windows 10 . OS Language This setting defines the operating system language mode. The following options available: EN; DE. The default value is EN . OS type This setting defines the operating system type mode. The following options available: Windows Server; Desktop Windows. The default value is Windows . Server . Enabled This setting indicates that the current image is enabled for use. Base snapshot This setting defines the name of the snapshot (a captured state of a system in a particular time point). It is usually used as a back-up copy or as a basis to troubleshoot issues.   This field is required. Base image This setting defines the name of the existed operating system image which can be used as a basis for this image. This field is required. The custom operating system image settings apply when clicking on the Create button. Apptimized shows the following screen when successful: The option to modify the custom operating system image settings is available under the Edit image button. Upload to VM switch The option to allow uploading files to the running VM activates when the Upload to VM switch is enabled. All required fields are marked with an asterisk * . The following screenshot shows the default settings: The Upload limit field indicates the number of total items that can be uploaded to VM per application. The Max file size field indicates the file size that can be downloaded to VM. The default value is 250 Mb. Settings of the Virtualization providers block are persisted on click to the Save button. Apptimized shows the following notification when successful: Apptimized TO GO settings The option is disabled by default. Apptimized - TO GO becomes active when switched on. Settings are persisted on click to Save button. Apptimized shows the following screen when successful: The option Enable proxy is disabled by default. If the endpoint connects to the internet via the proxy server, configure the connection by turning on  Enable proxy  and selecting  Use default windows credentials  or providing credentials in  Username  and  Password  fields. Settings are persisted on click to  Save  button. In case of success, Apptimized shows the following notification: Project roles Roles option enables the following functionality: To control which group or user is assigned to perform a specific step in the workflow; To control who can navigate the project's menu items; To set Apptimized email notifications (i.e., which users will receive the email notifications). Once the workflow reaches a specific step, the assignment rules will ensure that the task is assigned to the correct group of users (or a user). This will prevent from performing actions by unauthorized users. The project administrator role appears as an initial default role after the project was created. Project administrators can perform any workflow action. To complete the tasks with role assignments, a user must be a Project administrator or must have permission for these activities. Create a role The option to create a role with needed permissions is available under Roles in project settings ( Project menu >  Administration > Roles ). Apptimized opens the following screen: The option to create a new role is available under the Add new role button: Apptimized shows the following modal window when successful: The new role requires its name, project, workflow and updates permissions. All required fields are marked with an asterisk   * . Table 1. Role attributes Attribute Description  Project permissions Dashboards This attribute provides access to the project dashboard. Access to all apps This attribute providees access to all apps if the Application owner field is enabled .   Roles This attribute provides access to perform role management activities for the project. Groups and users This attribute provides access to perform management activities with groups and users for the project. File Storage   This attribute provides access to a dedicated/separate file storage to which the user can upload files for later use. Echo “assisted”   This attribute provides access to assisted Echo playback for interactive sessions such as Discovery and Testing. Echo Testing   This attribute provides test automation capabilities: record the user’s test case and play it back automatically when needed. Echo platforms   This attribute provides the ability to add and remove Echo platforms in project on Echo statistics page. Echo applications   This attribute provides abilities to check applications for new Echo platform and approve new Echo platform in Project on Echo statistics page. Catalogue   This attribute provides access to latest version of the application which was packaged with a standard guide and ready for use. SCCM This attribute provides access to perform SCCM activities within the project. The option becomes active when SCCM is enabled for the project. Intune This attribute provides access to perform Intune activities within the project. The option becomes active when Intune is enabled for the project. Notifications This attribute provides access to project notification settings.  Care This attribute provides access to Apptimized Care functionality within the project. Customiz3r This attribute allows access to receive custom packages from the Care service. The option becomes available when Care is selected for the role. Workflow permissions Import This attribute provides access to perform activities on the Import step of the project's workflow. Discovery Self Service This attribute provides access to perform activities on the Discovery - Self Service step of the project's workflow. Discovery Factory Service This attribute provides access to perform activities on the Discovery - Factory Service step of the project's workflow. Packaging Self Service This attribute provides access to perform activities on the Packaging - Self Service step of the project's workflow. Packaging Factory Service This attribute provides access to perform activities on the Packaging Factory Service step of the project's workflow. Testing Self Service This attribute provides access to perform activities on the Testing - Self Service step of the project's workflow. Download This attribute provides access to perform the Download step in the workflow. Updates View This attribute provides view access to the Updates feature of Apptimized. Modify This attribute provides permissions to operate with updates, including tracking, editing, and processing. Emails This attribute enables receiving e-mail notifications about updates. The option becomes available when Notifications is selected for the role. File Storage (available if the Storage feature is enabled in the project settings) Full control This attribute provides permissions to download, upload, and remove files and directories in project storage. Upload This attribute provides permission to upload files and create directories in project storage. Download This attribute provides permission to access, view, and download content from project storage. Apptimized shows the following notification and screen when successful: Manage a role Users can be added to the role via the Update users or Update groups buttons. A user or group can be selected on the following screens. The Save button applies the changes. The Edit button allows modifying an existing role. The same steps apply as when adding a new role. The role can be removed by selecting the Delete button and confirming the action. Groups & users Groups & users option enables the following functionality: To control which group or user is assigned to perform a specific step in the workflow; To create groups of users with the same permissions; To create groups to perform specific tasks in a project; To set Apptimized email notifications (i.e., which users will receive the email notifications). Once the workflow reaches a specific step, the assignment rules will ensure that the task is assigned to the correct group of users (or a user). This will prevent from performing actions by unauthorized users. All group members have equal permissions until the group manager is assigned. The Project administrators group appears as an initial default group after the project was created. Project administrators can perform any workflow action. To complete the tasks with role assignments, a user must be a Project administrator or must have permission for these activities. Create a group The option to create a group with needed permissions is available under Groups & users in project settings ( Project  menu >  Administration > Groups & users ). Apptimized shows the following screen when successful: The option to create a new group is available under the Create new group button: Apptimized shows the following modal window when successful: The new group requires its name and role. All required fields are marked with an asterisk * . Adding a role to a group implies that the role has already been created (see Project roles chapter). Apptimized shows the following notification and screen when successful: Manage a group Users can be added to the group via the Update members button ( Update members button >  Add users field > Select a user from a drop-down list > Save button). Apptimized shows the following notifications and screen when successful: If the person does not have an Apptimized account, the Email address will not appear in the drop-down menu. The option to invite a new user to Apptimized and to add the to-be-created user account to a group is available under the Update members button >  Add users field > Enter Email > Save button. The person will be informed via Email (see Register to Apptimized Portal ) . The option to delete a group member is available under the Update members button > Bin symbol in front of the user's name > Save button. The option to set a group manager is available under the Update members button >  Group manager field > Select a user from a drop-down list > Save button.  A group can be changed with the Edit  button and by following the same set of operations as for adding a new group. The option to delete the group is available under the Delete button. Apptimized shows the following modal window: Apptimized shows the following notification and screen when successful: Dashboards Default configurations By default, a new project is created with two predefined components in the project dashboard: Portfolio and Overview . Overview dashboard Apptimized shows the following screen upon the project creation: The overview dashboard contains the following blocks: Project stages statistics Your assignments Project basket Completed modules The overview dashboard is filled with data as the project is implemented. The project progress data (i.e., multiple dashboard widgets, depending on enabled modules; a list of assignments; a list of applications) will be displayed in the relevant dashboard blocks. Block name Description Project stages statistics This block shows the Project workflow steps statistics and status.  Project steps statistics is provided in the form of the number of applications used in a particular step (module). Apptimized shows the following screen when the project gets some progress:   Your assignments This block shows a list of applications that are assigned to a user currently logged in. This block is configured as a table. Assignments data is grouped into the following categories: Vendor Software Version Language Actions Project basket This block contains information about all applications that are used in this particular project. This block is configured as a table. Project basket data is grouped into the following categories: Vendor Software Version Language Assignee Actions Completed modules This block shows the statistics of completed steps (modules) within the project. This block is configured as a chart. Each chart sector shows the number of applications completed a particular step (module).   Portfolio dashboard This dashboard shows more detailed information regarding the Project’s applications, and also can display applications from another shared project of the same tenant if enabled.  See more. Create a custom dashboard The  option to create a  custom dashboard provides a user with   a  page that  represents  application data structured  according to  the  user’s  settings applied while dashboard creati on .     To create a new dashboard in a project, click  Add dashboard  in  the  Dashboards  submenu.   Apptimized shows the following modal window: Settings  Details   Dashboard name   Dashboard name  field allows user s  to set  the dashboard name  (e. g .,   “Demo dashboard” ) .     There is no default value in this field.     Share it   Share it  option. Apptimized provides two options to share  the  dashboard :   Sharing with users   Sharing with groups   (e.g., with “Project Administrators”)     There is no default value in this field.   To apply the settings, click the Create button. To revert the settings, click on the Cancel button. Layout The dashboard creation process may take a few moments. Apptimized shows the following notification when successful: The blocks on the screenshot above are containers in which tables or charts are placed.   T he option t o add a new block to the dashboard  is available under the   plus  symbol.   A new block appears in full-width mode by default. To change a width mode, click the drop-down menu. Apptimized shows the following notification when successful: Blocks on the dashboard appear as empty containers by default. The block naming and filling in  is   a user preference.    Widget management and configuration   Apptimized provides  the option to create  and manage  widgets  based on  user’s  settings  preconfigured by a user or by default.   The  W idget  provides a user with quick access to application data.   Every  W idget  requires   conditions and  appearance   configurations  that can be set during  its  creation.   Configurations and appearance vary depending on the widget type (s ee  the  Widget configuration ) .   The screenshot below shows a result for the creation of  a  Table   widget.   The screenshot below shows a result for the creation of  a  Chart   widget.   Add Widget When clicking on  “Add new widget”  Apptimized shows the modal window below. The following widget types available:   T abl e     Chart Echo consumption Note .  If a user chooses  Chart widget  type ,  the field  Based on preset   appears in the modal window   (see the   Widget presets ).   The widget settings become active when clicking on the  Create   button.  Apptimized  shows the  W idget  when successful.   The screenshot below shows a result for the creation of a  C hart  widget  named “Portfolio” .   The option to edit the layout for the dashboard is available under  Settings > Edit dashboard.   Apptimized shows the following screen when successful: The option to delete a block or a widget from a dashboard is available under bin symbol. The option to change the owner is available under Settings > Edit dashboard.   The option is available for project and Global admins only. Widget presets  Widget presets  are pre - configured and automatically generated presets available for Chart widget type.  Every preset is based on the information in  the  project  Portfolio  (see the  Portfolio ).   The option to choose a widget preset is available under  Based on preset   while widget creation  (see the  Add Widget ).   The following  Based on preset  s ettings  available:   Setting Details  Portfolio chart   Portfolio chart  is a setting indicating the option to create a  Chart  widget based on   the  application  number in each  workflow module  (see the  Overview dashboard ).   The default value is the  Portfolio chart .    The screenshot below shows a result for the creation of a widget based on  the  Portfolio chart :       The option to change Widget is available after creation (see Widget configuration ). Echo chart   E cho  chart  is a setting indicating the option to create a  Chart  widget based on a user’s Echo test   cases status.     The screenshot below shows a result for the creation of a widget based on  the  Echo chart :       The option to change Widget is available after creation (see Widget configuration ). Project stages statistics   Project stages statistics  is a setting indicating the option to create a  Chart  widget based on a user’s current  p roject workflow steps statistics and status  (see the  Overview dashboard ).     The screenshot below shows a result for the creation of a widget based on  Project stages statistics :       The option to change Widget is not available after creation. Custom chart   C ustom  chart  is a setting indicating the option to create a  Chart  widget based on a user’s configurations and conditions (see the  Widget configuration  and  Widget conditions configuration ).      The screenshot below shows a  few  result s  for the creation of a widget based on  the  Custom chart :           The widget view varies depending on the  conditions  configuration  set by a user.     The option to change Widget is available after creation (see Widget configuration ). Widget configuration  The option to configure  W idget  is available under  Settings > Edit Chart or Edit Table.   To  c onfigure   widgets, a user is redirected to  the  constructor  page.   C onstructor  page   allows  configuring   widget conditions and widget appearance.    The w idget  configuration process includes the following steps:   Step 1: Widget conditions   Step 2 : Widget appearance  Note .  Step 1:  The w idget  conditions  block is the same for all widget types. Step 2: Widget appearance varies depending on widget type (see the  Table widget appearance configuration  and  Chart widget appearance configuration ).   Widget conditions configuration  The  W idget conditions  block sets the rules by which to apply applications search.    This  block  consists of the condition groups list.   Group consists of logical operators that should be applied to conditions below:   • If all/any of these conditions are true/false;   • Inner group conditions.   The options to add a condition or a group of conditions are available under the  Add condition  and  Add group  buttons.   The following table contains all widget condition settings, options, parameters and values: Condition setting Condition setting options Condition setting parameter Condition setting value App ID   Is less than Is greater than  -   Number     Application owner   Contains   Not in   -   Current user   Users assigned to a project   Vendor   Software   Language   Reference   Is   Is not   Starts with   Ends with   Contains   Is null or empty   -   Integer   Version   Is less than   Is   Is not   Is greater than   -   Integer   Echo   Contains   Not in   Pending   In progress   Success   Failed   Review required   Action required   No Scenario   Disabled   All   -   Updated   Push To Sccm     Is less than   Is   Is not   Is greater than   Date   Current Date   Days Offset   Weeks Offset   Start of week   Start of month   Start of year   End of week   End of month   End of year   Date   Application’s prerequisites   Contains   Not in   -   Applications uploaded to the project & packages   Origin   Contains   Not in   CSV import   Classic import   Intune Import   SCCM Import   Catalogue & UM Import   -   Stage   Starts with   Ends with   Contains   -   Integer   Application’s parent   Contains   Not in   -   Applications uploaded to the project & packages   Factory request type   Factory Request platfom   Factory request start date   Factory request SLA On Time/Overdue   Factory request status   Factory request delivery date   Factory request invoiced   Factory request date of invoicing   Packaging – Factory Service   -   -   Assignee   All   Current   Discovery – Self Service   Packaging – Self Service   Testing – Self Service   Discovery – Factory Service   Packaging – Factory Service   Testing - Factory Service   -   Users assigned to a specific step.   Status   Global   Discovery – Self Service   Packaging – Self Service   Testing – Self Service   Discovery – Factory Service   Packaging – Factory Service   Testing – Factory Service   Is   Is not   Incomplete   Complete   Start Module Time   Finish Module Time   Discovery – Self Service   Packaging – Self Service   Testing – Self Service   Discovery – Factory Service   Packaging – Factory Service   Testing – Factory Service   Is less than   Is    Is not   Is greater than   Date    Current Date    Days Offset   Weeks Offset   Start of week   Start of month   Start of year   End of week   End of month   End of year   Deliverable   Import   Discovery – Self Service   Packaging – Self Service   Testing – Self Serivce   Discovery – Factory Service   Packaging – Factory Service   Testing – Factory Service   Is   Not available   Available   Test status   Testing – Self Service   Testing – Factory Service   Contains   Not in   Untested   Success   Failed   Fixed   Widget appearance configuration  Widget appearance   block  defines widget view for the dashboard   (i.e., widget name, set of columns, chart type,  grouping, ordering, aggregates).   Table widget appearance configuration The screenshot below shows settings a user can apply to configure table widget appearance.   Note. If the project Portfolio is shared with other projects within organization, the Projects to include field appears in the Step 2: Widget appearance block (see the Project settings ). The Project to include field allows a user to include applications from other organization's projects to the Widget. The re is no  default value  for this field .   Setting Description Widget name The widget name field allows defining the widget name (e.g., Portfolio). Default page size This field allows defining number of items per table page. Table Columns This section allows setting up table columns container. Ordering This field allows arranging items in a sequence. The following criteria available:   Ascending;   Descending.   The following items available:   App ID; Application owner;  Vendor;   Software;   Version;   Language;   Assignee: All;   Updated;   Stage;   Assignee: Current.   Grouping This field allows combining data into groups that have the same value in selected columns.  The following items available:   App ID; Application owner; Vendor;   Software;   Version;   Language;   Assignee: All;   Updated;   Stage;   Assignee: Current.   The following order settings available:   Ascending;   Descending.   Aggregates This field allows defining high-level data composed from other more individual data by selected measurement for the column. The following aggregate options available:   Count;   Sum;   Average;   Min;   Max.   The table columns are set when dragged and dropped from the  "Available table columns"  to  the  "Selected table columns"  container.   For columns used on a per-module basis (namely,  Assignee, Status, Test status ) ,  an option to select which module this column should be applied  to  is available:   “Reset columns” button allows to revert actions for columns to initial state. An option to arrange the ordering mode is available under the Ordering block. Ascending and Descending modes are available. Combining data into groups with the same value in columns is available under the Grouping  block. Ascending  and  Descending  order modes are available.   A user sets the fields to include in a group. The “Add level” button creates a new group. Suppose the selected set of columns includes columns aggregated by Numeric field, Echo field, or Test status field. In that case ,   the ability to set the aggregation rules is available:   The settings are applied when clicking the  Save  button. A table widget appears on the project dashboard.   Chart widget appearance configuration The screenshot below shows settings a user can apply to configure chart widget   appearance .   Settings  Details  Widget name   The w idget  name  field allows  defining  the widget name (e.g.,  Portfolio ).   The re is no  default value  for this field .     Chart type   Chart type  field allows  choosing  a type for the chart.   The following options available:   Pie   Bar   The default value is   Pie .     Grouping   The g rouping   field allows  combining  data into groups.   The following options available:   App ID Vendor   Software    Version   Language   Reference   Echo   Updated   Application’s prerequisites    Origin   Stage   Application’s parent   Testcase status   Echo platform   Assignee   Status   Start module time   Finish module time   Deliverable   Test status Push to Sccm Application owner   The default value is  App ID .     Note.  The options Assignee, Status,  Start  module time, Finish module time, Deliverable ,  and  Test status   varies  depend ing  on the project configuration (see the  Create project ).     Note. If the project Portfolio is shared with other projects within organization, the Projects to include field appears in the Step 2: Project appearance block (see the Project settings ). The Project to include field allows a user to include applications from other organization's projects to the Widget. The re is no  default value  for this field .   The settings are applied when clicking the  Save  button. A chart widget appears on the project dashboard.   Apptimized shows the following screen when successful:   Echo consumption widget appearance configuration The screenshot below shows settings a user can apply to configure echo consuption widget appearance.   Note. If the project Portfolio is shared with other projects within organization, the Projects to include field appears in the Step 2: Widget appearance block (see the Project settings ). The Project to include field allows a user to include applications from other organization's projects to the Widget. The re is no  default value  for this field .   Setting Description Widget name The widget name field allows defining the widget name (e.g., Portfolio). Default page size This field allows defining number of items per table page. Table Columns This section allows setting up table columns container. Ordering This field allows arranging items in a sequence. Grouping This field allows combining data into groups that have the same value in selected columns. Aggregates This field allows defining high-level data composed from other more individual data by selected measurement for the column. Clone dashboard  The option to clone the dashboard is available under  Settings > Clone dashboard.   Apptimized shows the following modal window:   Apptimized shows the following modal window: The cloning step  is  finalize d   by clicking on the   Clone  button.   The cloned dashboard appears in the project menu. Apptimized shows the  Dashboard layout  page for the cloned dashboard.   Delete dashboard   The option to  delet e the dashboard is available under  Settings > Delete dashboard .   Apptimized shows the following modal window: Three options available: 1. Delete: Permanently delete; Apptimized reverts to the project dashboard. 2. Reassign to another owner - a new owner can be assigned^ 3. Cancel - reverts to the dashboard. Portfolio The portfolio is available in the project menu under Dashboards > Portfolio . The portfolio provides a user with a wide range of functionality. Namely: To complete a list of applications that exist in a user’s project including their status; To indicate applications which are shared within other projects; To process, delete and configure applications; To sort, filter, and export application data. The following screen shows the portfolio interface in Apptimized Dashboard. Portfolio data is grouped into the following categories: App ID; Vendor; Software; Version; Language; Assignee; Updated; Stage; Actions. The portfolio is performed in 2 blocks: Information block – this block contains detailed information about the application; Action block – this block provides options to manage applications. Table 1. Information block Column name Details App ID A personal static number of the application. Vendor A supplier of the application (i.e., Tim Kosse ). Software The full official name of the application (i.e., FileZilla ). Version A current version of the application (i.e., 3.5.2 ). Language Information on the application language taken from metadata. A user can change this information in the Upload - Confirm step. Assignee This column indicates a person appointed to manage the application. Updated This column indicates the date and time when data on the application was last updated (i.e., 03/30/2020 10:35 ). Stage This column provides the information on a current request step. The information is grouped by template: – (i.e., Upload – Confirm ). The following stages options available: Upload – Confirm / Initialize; Discovery / Testing / Packaging – Initialize; Discovery / Testing / Packaging - ; Discovery / Testing / Packaging – Self Service; Discovery / Packaging – Screenshots; Testing – Results; Download - List of files. The following factory statuses available: Ready for Discovery - a user’s request is submitted to Apptimized and is ready for processing by Apptimized team; In Progress - Apptimized team is processing a user’s request; Delivered - Apptimized team finished processing a user’s request and sent corresponding Deliverables; Action Required – a user must check the request and provide additional information to Apptimized team; Incoming check – Apptimized team is started processing a user’s request and checking all additional information; Factory QA – a user’s Testing request is submitted to Apptimized and is in progress for processing by Apptimized team; Action Required – a user must check a ticket and provide additional information to Apptimized team; Delivered - Apptimized team uploaded the result for a user’s request, and a user must check it; Error Analysis – a user found a bug in the package and sent a bug report to Apptimized team; Approved - when the package is correct, and a user approves a request in the ticket. The number of items per page can be changed to 10, 50, 100, or all items. Keyword search mode available: The columns in the portfolio table can be swapped and grouped in any order. A user can drag and drop a column header to a suitable place. To exclude columns in the portfolio table, uncheck the box next to the column name not required in view. This option is available under Edit Column Settings > Columns . To sort data in columns App ID , Vendor, Software, Version, Language, or Updated select ascending or descending mode. This option is available under Edit Column Settings > Sort Ascending or Edit Column Settings > Sort Descending. An alternative method to sort data in columns: Click the table header > Click the arrow symbol. To filter data in columns Vendor, Software, Version, Language, Assignee, or Stage use Edit Column Settings > Filter > Select the relevant value > Filter button. To exclude import types from the import history table, uncheck boxes next to the name not required in view. To filter data in columns Updated or App ID , use Edit Column Settings > Filter > Show items with value that > Filter button. The action block extended menu: The Process option allows the user to go to the Transition screen page. The Assign option allows the user to assign users responsible for tasks on the application. Assignments revert to the initial settings by clicking the Cancel button and change by clicking the Save button. Apptimized shows the following notifications when successful: Apptimized sends the follow-up email once the user has been assigned to a task: The Settings option allows a user to edit the application metadata. Application settings revert to the initial settings by clicking the Go to last dashboard button and change by clicking the Save button. The Push to SCCM option allows a user to start the deployment of an application to SCCM. Before applying this option, the one-time configuration of Apptimized SCCM Connector by project administrator must be provided (see the SCCM Integration ). The  Push to Intune option allows a user to start the deployment of an application to Intune. Before applying this option, the one-time configuration of Apptimized Intune Connector by project administrator must be provide. (see the Intune Integration ). The Timeline option provides a list of user activities in Apptimized. A user can check all actions, track uploading and reuploading of files and metadata changes (including application icon updates), download the installation source, download generated discovery and testing documents or packages, or revert the workflow to the required step: When a user wrapped a package, Apptimized shows the following screen: The Copy option allows a user to copy the application metadata to the Upload - Confirm step. The option to delete the application is available under Action > Extended menu > Delete . Apptimized shows the following modal window: The applications delete by clicking the Delete button. Apptimized shows the following notification when successful: The pending uploads delete option is available under the Delete pending uploads button. A portfolio database can be downloaded as an Excel file by clicking the Export to Excel button. Import history An import history is available under Import in project menu > Import History . The default view is 10 items per page. The number of items per page can be changed to 10, 50, 100, or all items. Keyword search mode available: Application import history data is grouped into 5 categories: Start time; End time; User; Import type; Status. The columns in the import history table can be swapped and grouped in any order. A user can drag and drop a column header to a suitable place. To exclude columns in the import history table uncheck the box next to the column name not required in view. This option is available under Edit Column Settings > Columns . To sort data in columns User , Start time, or End time select ascending or descending mode. This option is available under Edit Column Settings > Sort Ascending or Edit Column Settings > Sort Descending. An alternative method to sort data in columns: Click the table header > Click the arrow symbol. To filter data in column Import type use Edit Column Settings > Filter > Select all / SCCM import / CSV import / Classic import > Filter button. To exclude import types from the import history table, uncheck boxes next to the name not required in view. To filter data in columns Start time or End time by date, use Edit Column Settings > Filter > Show items with value that > Filter button. To filter data in column User by username, use Edit Column Settings > Filter > Select username > Filter button. To exclude usernames from the import history uncheck the box in front of the names not required in view. The screenshot below shows actions to see the list of applications for a particular import: Application import history data of a particular import is grouped into 5 categories: ID; Vendor; Software; Version; Language. The columns in the import history table can be swapped and grouped in any order. A user can drag and drop a column header into a suitable place. The sorting and filtering options are applied as in the previous example. The option to change an application setting is available under the Settings button. Apptimized shows the following screen: The settings revert to the initial settings by clicking on the Cancel button and change by clicking on the Save button. Import history can be downloaded as an Excel file by clicking on the Export to Excel button.   Classic Import The option to start the import is called “ Classic import ”. It is available under Import in project menu > Start Import section > Classic import option. The initial preparation process may take a moment or two. When successfully imported, Apptimized shows the the Upload sources and documentation/instructions step where Installation Source, Documentation / Instructions, and Application icon for SCCM/Intune are available. Note.  With this type of import, the user can skip loading the source. In this case, the user enters the application metadata manually. But it should be noted that after the import step is completed, the user isn't able to perform actions on the workflow. Subsequently, the user can assign another user to the project, which downloads the source and perform actions on workflow. Three options available to upload Installation Source : Upload application file from user's PC; Upload application file from the Internet; Upload application file from the file storage. The Installation Source uploading progress displays as follows: The upload time depends on the application's size. When each download of an application is completed, the user can start uploading another application. Five application uploads are available for one session. Uploading Discovery Document is optional. A discovery document can be generated on previous sessions. Two options available to upload Discovery Document : Upload application file from user's PC; Upload documentation file from the Internet. One discovery document upload is available for one session. Uploading Application icon for SCCM/Intune is optional. Supported file formats are .png , .jpeg , and .jpg . The maximum file size is 2 MB . The Upload sources and discovery document step is finalised by clicking the Next button. Apptimized shows the Metadata step when successful. The process reverts to the previous step by clicking on the Upload sources and documentation/instructions button. To extract the application metadata automatically a user can select the main installer from the list on the left or can enter the metadata manually into the fields on the right. All required fields are marked with an asterisk * . Note. Apptimized automatically extracts metadata from the following files: exe, msi, msix, msixbundle, appx, appxbundle. The following metadata will be provided: Table 1. Application metadata Metadata Details Previous version of an application This field defines if the previous version of the application is available in the portfolio. The default value is Search by %Vendor% %AppName% %Version% %Language% (AppID %AppID%) . A click opens a dropdown list to select the previous version of the application from the list. Application ID The application ID is a unique identifier generated automatically for every application during its upload. Application ID provides application identification. Reference This field is optional and can stay blank. This field provides additional comments from a user to the Apptimized portal (i.e. internal application ID). Vendor This field defines the vendor name. This is a required field. Software This field defines the application name. This is a required field. Version This field defines the application version. This is a required field. Language This field defines the application language. This is a required field. Architecture The Architecture field defines the system architecture supported by the application. The original value is detected from the installation source. This is a required field. Enable Echo This option defines if Echo is needed to be enabled. The Echo is enabled by default. The prerequisites can be added by clicking on the Add prerequisites button. A prerequisite may be a specific application that must be installed before the target application. A field " Select media type for …" is filled automatically can be changed if needed. A prerequisite is added by clicking on the Save button. Apptimized shows the following notification when successful: Current prerequisites can be changed by clicking on the Edit prerequisites button and by following the same set of operations as for adding a prerequisite. The Metadata step finalizes by clicking on the Finish button. A Transition screen for the application appears where the Workflow scheme and modalities for interaction with the application (namely discovery, packaging, testing) are available. CSV Import The option to start the import is called “ Import from CSV file ”. It is available under Import in project menu > Start Import > Import from CSV file option. The initial preparation process may take a moment or two. When successfully imported, Apptimized shows the Upload CSV file step. The option to upload the CSV file is available under the Click here to select file button. The upload time depends on the application's size. Apptimized shows the following screen when successful: A user can set a CSV Columns separator. Three options available: Comma , Semicolon , or Tab . The default value is Comma . The Upload CSV file step is finalized by clicking the Next button. Apptimized shows the Map your files fields step when successful. The process reverts to the previous step by clicking the Upload CSV file button. A user maps CSV file fields when dragged and dropped modules from the “ Your CSV file ” to the “Application meta data” box. Several CSV file fields can be mapped to one file filed in Apptimized. An option to search for applications with the same value in user's portfolio to remove duplicates in the CSV file is available under Unique field block. The Map your files fields step finalizes by clicking the Finish button. The process reverts to the previous step by clicking the Back button. Apptimized shows the Review mapping and confirm step when successful. If a duplicate application is found, Apptimized shows the notification: The duplicate application is indicated as follows: Exclude applications from the import by clicking the bin symbol. The Review mapping and confirm step finalizes by clicking the Finish button. Apptimized navigates to the Portfolio dashboard and shows the notification when successful. SCCM Import The option to start the import is called “ SCCM Import ”. It is available under Import in project menu > Start Import section > SCCM import option. The initial preparation may take a few moments. In case of a connection failure, Apptimized shows the following message: Single import session imports a single folder. For example, one of the following folders import in the scope of import session: root folder Application or folder Test 1 or folder bis_628 . Note . The checkbox All applications always relates to the current folder. The screen below shows the content import in the root Applications folder. Applications can be excluded from import by unticking checkboxes in front of their names. Note. The icon below means that this application already exists in the project portfolio but can be imported for a second time. As a result, duplicates are created in the project portfolio. The import process starts by clicking on the Next button. It can take up to 30 minutes and is dependent on the number of applications and their size. “Set metadata” shows import candidates' meta information and provides the ability to update it to desired values. All required fields are marked with an asterisk *. Exclude applications from the import by unticking the checkbox. The process reverts to the initial screen by clicking on the Back button and finalizes by clicking on the Finish button. Apptimized shows the following notification when successful: Imported applications appear in the project portfolio.   Catalogue Import The option to start the import is called “ Catalogue Import ” . It is available under Import in project menu > Start Import > Catalogue Import option.   When successfully imported, Apptimized shows the Choose Applications from Catalogue step.   Application import data is grouped into 4 categories:   ID;   Vendor;   Software;   Actions.     The default view is 10 items per page. The number of items per page can be changed to 10, 50, 100, or all items.   An application database can be downloaded as an Excel file by clicking on the  Export to Excel button.   The columns in the import table can be swapped and grouped in any order. A user can drag and drop a column header to a suitable place.   To exclude columns in the import table, uncheck the box next to the column name not required in view. This option is available under Edit Column Settings > Columns .   Keyword search mode available:     To filter data in columns ID, Vendor, or Software , use Edit Column Settings > Filter > Select one or multiple items > Filter button. To exclude data from the import table, uncheck boxes next to the name not required in view.   The option to see all available application versions is available under the Show versions button.       The option to select an application version from Catalogue is available under the Select sources to this version field.       Apptimized shows the following notification when the application version selected:     The Catalogue Import finalize s by clicking on the Finish button.   Apptimized shows the following notification when successful:     The imported applications are available in portfolio.     Update Import The option to start the import is called “ Updates Import ” . It is available under Import in project menu > Start Import >  Updates Import  option.     When successfully imported, Apptimized shows the Choose Applications from Updates   step.     Application import data is grouped into 4 categories:   ID;   Vendor;   Software;   Actions.   The default view is 10 items per page. The number of items per page can be changed to 10, 50, 100, or all items.     An application database can be downloaded as an Excel file by clicking on the Export to Excel button.     The columns in the import table can be swapped and grouped in any order. A user can drag and drop a column header to a suitable place.   To exclude columns in the import table, uncheck the box next to the column name not required in view. This option is available under   Columns .   Keyword search mode available:     To sort data in columns ID , Vendor, or Software , select ascending or descending mode:  Click the table header > Click the arrow symbol .   To filter data in columns ID, Vendor, or Software , use Edit Column Settings > Filter > Select one or multiple items > Filter button. To exclude data from the import table, uncheck boxes next to the name not required in view.     The option to see all available application versions is available under the Show versions button.     Apptimized shows the following screen when successful:     The option to select an application version from Update is available under the Select sources to this version field.       Apptimized shows the following notification when the application version selected:     The Update Import finalizes by clicking on the Finish button at the end of the l ist .     Apptimized shows the following notification when successful:     The imported applications are available in portfolio.       Discovery The following scenarios to open the transition screen available: My Dashboard > My Applications > Choose the project > Actions column > Process option; Project menu > Dashboards > Overview > Your assignments module > Choose the application > Actions column > Process option; Project menu > Dashboards > Portfolio > Actions column > Process option; Project menu > Import > Start import > Classic import / Import from CSV file / SCCM Import /Catalogue & UM Import > Application upload session > Finish. Apptimized shows the following screen when successful: Two discovery scenarios available in Apptimized portal: Discovery – Self Service; Discovery – Factory Service. Discovery – Self Service A user can record a guide to install and configure the application on Apptimized VMs. A user’s actions are automatically captured as step-by-step screenshots and further described in textual format automatically. Before sending a document (which is available in PDF and HTML formats) to Apptimized, the user can change the scenario that they recorded (i.e., to swap screenshots, to edit comments for each screenshot or to delete unnecessary screenshots). Users can also create custom templates for the document, which are available in two formats. Discovery - Self Service characteristics: A user installs an application on the chosen Microsoft Windows platform. A user automatically documents an installation, configuration, and test activities. A user can collaborate with his co-workers and Apptimized support staff. The Discovery - Self Service option is available under the Discovery - Self Service module in the Transition screen . Apptimized shows the following screen when successful: A field " Select discovery – self service platform " is filled automatically and can be changed if needed. To change the discovery – self service platform, click the drop-down menu as it is shown in the screenshot below: The option to revert to the transition screen is available under the Go to Transition screen button. The option to request a virtual machine image is available under the Can’t find the VM image you need? Contact our Support team to request one link. Discovery – Self Service process The option to start the discovery – self service process is available under the Start VM button. Apptimized shows the following screen when successful: The file synchronization process may take few moments. Apptimized shows the following notification: Note.  There is often a situation when a user has already run 2 VMs in parallel. To continue planned activities within the current workflow step, a user must terminate an irrelevant VM. In this case, Apptimized shows the warning box with a list of VMs which are currently running by the user: The information is grouped into the following categories in the modal window:  1. Application 2. VM started time 3. Workflow progress 4. Link The option to select a VM for termination is available under the Go to VM link. A new tab opens when successful: When a VM is terminated, a user returns to the screen where he needs to restart a VM (previously a user started a VM but received a modal window with a list of running VMs). When the synchronization process is finished, Apptimized shows the following screen: Note. If the internal error while starting VM occurred, Apptimized shows the following screen: The following actions are recommended for consideration by a user: 1. Contact the Apptimized support 2. Go to image page button > Select discovery – self-service platform field > Start VM button The uploaded files locate in the Apptimized files folder on the VM desktop. To start the installation process, a user opens the .EXE file located in the Source folder. Every action is captured as a screenshot which is shown in green boxes appearing on the right-hand side: When application installation is completed, a user can provide further configurations (only the Edit and Settings categories). The option to copy files to Temp storage  is available under  Explorer context menu  >  Copy To Temp : The options to finish the VM session is available under the Finish button. The following interface will appear when recording session with Apptimized VM finishes: The option to restart the VM discovery session is available under the Restart button. To confirm the restarting the VM Apptimized shows the following modal window: VM control menu The VM control menu panel is available in the upper right corner of the VM interface. Next, each settings category is shown in more detail. Table 1. VM control menu   Control menu category Details 1 Screenshots This setting indicates the screenshot mode. On and Off options available. The default value is On . 2 Add prerequisites/Edit prerequisites This setting enables a user to add prerequisite applications. Portfolio tab is available by default.  Update Monitoring  &  Catalogue  tabs become available if there are delivered packages on them. Portfolio tab   The option to select application is available under  Select applications  field. The option to select media type for applications is available after the application was selected. The following media types available: Package Source Note . One media type is automatically selected if others are missing. The option to use Source media type is available under  Use Source  >  Select Media  > select source file.     The option  to use Package media type is available under  Use Package > Select Media >  select package file.       Update Monitoring     Update Monitoring tab allows to add prerequisites as applications from  Update Monitoring  delivered packages.     The option to Select application from Update Monitoring is available under  Select applications:  field >  Select Version for application .       Catalogue     Catalogue  tab allows to add prerequisites as applications from  Catalogue  delivered packages.     The option to select applications from the  Catalogue  is available under  Selec applications:  field >  Select Version for application .       The option to Save Changes is available under  Save  button.     Apptimized shows the following notifications when successful:     The option to  Edit prerequisites becomes available after the prerequisites were added.   Note . Uploaded prerequisites are shown in the discovery documentation under the Previous application section. 3 RDP This setting enables a user to work on the VM directly via RDP rather than a browser window. The option to download a file is available under the Download RDP file. The RDP file is available in the Downloads folder in user’s PC. When the remote connection is set, copy the RDP password paste to the modal window. The remote desktop connection window appears when successful: 4 VM Snapshots The setting enables to create a snapshot of the VM to save its current state or to revert to a state saved earlier. This is applicable when the application has prerequisites that need to be present before a certain action (i.e., Discovery, Packaging, or Testing) can be started. The snapshot option is available under the VM snapshot button > Snapshot name field > Take button. 5 Clipboard This setting enables a user to put text from the user’s system to the VM clipboard. Transferring clipboard content between the host machine and the VM is performed via "Cut & Paste" in most user scenarios. If the user experiences any issues with "Cut & Paste", the Clipboard button can be used to put the text to the VM's clipboard. 6 Ctrl + Alt + Del This setting enables to open security options menu at the VM. 7 Fullscreen This setting enables to put a browser in a full-screen mode. 8 Restart This setting enables a user to redo the discovery session on a restarted VM. The following restart options available: OS (Operating system restart. Equal to Power > Restart); VM (Equal to the Reset button on the real PC); Session (Restart current session. All unsaved progress will be lost). When the restart option is chosen, the confirmation model window appears. 9 Finish This setting finishes the VM when the discovery session is completed. Discovery – Self Service screenshots The option to edit the screenshots is available under the Continue with Discovery – Self Service screenshots button. Apptimized shows the following screen when successful: Screenshots can be excluded from discovery by clicking the Delete button. Screenshots can be excluded from discovery in a multiple mode by unticking checkboxes in front of their ID and clicking the Delete selected screenshots button. Apptimized shows the following modal window: When clicking on the Confirm button, Apptimized shows the notification: Screenshots sequence can be changed in discovery by clicking the Up or Down buttons. Comments to the screenshots can be edited by clicking on the comment cell. The Additional comment (Optional) field can stay blank. If any problems accur, the option to contact support is available under the Did you run into problems? button. Apptimized shows the following modal window: When the Contact support option is chosen, the live chat with the support team appears: When the Log problem option is chosen, the modal window appears: The problem category can be chosen by ticking checkboxes in front of their names. Screenshots editing mode finalizes when clicking the Save changes button. Apptimized shows the following interface when successful: The generated document is available in PDF and HTML formats. To download a document, click the Download generated HTML document or Download generated PDF document buttons. A generated HTML document first page sample is available: The option to edit a discovery document is available under the Edit generated document button. The document editing finalizes by clicking the Save button. The option to return to the discovery self-service screen mode is available under the Revert to Discovery – Self Service Self Service button. The option to finish the discovery process is available under the Finish button. Apptimized shows the following screen: Discovery — Factory Service process Discovery - Factory Service characteristics: Apptimized installs, configures, and tests an application for a user. Apptimized documents the configuration for a user. Apptimized contacts a user if any details are needed. The Discovery - Factory Service option is available under the Discovery - Factory Service module in the Transition screen . Apptimized shows the following screen when successful: All required fields are marked with an asterisk * . The option to provide a comment is available under the Reference field. The option to choose the discovery platform is available under the Discovery platform field. Two priority options are available: Normal and Urgent . The default value is Normal . The option to submit  the discovery request is available the  Submit request  button.   Apptimized shows the following modal window: The option to change the Normal priority to Urgent before approving the request is available under the Make urgent button. The option to create the request is available under the OK button. Apptimized shows the following screen when successful: This is an initial screen, and all blocks except the Status block are empty. This screen provides information on the Apptimized  Discovery – Factory Service request (i.e., request progress and status). Additional information that might be needed during the discovery process will be exchanged here. After the request is created, the current priority is displayed on the Factory Service page. Clicking the Priority field opens a modal window allowing the priority to be increased to Urgent . Next, each Discovery – Factory Service block is shown in more detail. Status block The Status block shows discovery progress. The following request statuses appear depending on the Discovery – Factory Service progress: Table 2. Discovery request statuses Request status Description Incoming check The request has not been processed by the Apptimized team yet. The request is in the queue. In progress The request was processed by the Apptimized team. The request is in progress. Action required The Apptimized team asked the user a question. The user answer is needed. Delivered Discovery results are available to the user. Discovery results can be provided in PDF and HTML formats. Error analysis The user rejected the Discovery results. Apptimized team fixes bugs in the Discovery document. Approved The user has confirmed the Discovery results. Canceled The user canceled the Discovery request at the processing stage. The option to cancel the request is available under the Cancel Request button. Apptimized shows the following modal window to confirm the request cancellation: Apptimized shows the following modal window when successful: A user can cancel the discovery request until the Delivered status is achieved, and the discovery deliverables are available. If a user is not satisfied with the discovery results, they can be rejected under the  Factory activity   block.   When a user is satisfied with the discovery results, they must be approved in the Status block. The option to approve the request is available under the Approve Request button. The Approve Request button becomes active when the Delivered status is achieved, and the discovery deliverables are available. Apptimized shows the following modal window to confirm the request approval: Apptimized shows the following screen window when successful: Note. When a user approves the request, the option can`t be canceled. Deliverables block This block provides the discovery results to a user. Discovery results can be provided in PDF and HTML formats. The option to download the discovery results is available under the Download button. If a user is not satisfied with the discovery results, they can be rejected  for   further processing by the  Apptimized  team. The option to reject the discovery results is available under the  Factory request   section under the  Factory activity  block  (see  Factory activity block ) .   Factory activity block The option to contact the specialist from  the  team is available under the  Factory activity block > Factory request   >  Write a message ...  field . The option to add optional attachments to the comment ,  such as screenshots or additional files (max 10 MB per file) ,  is available under the  Select  file . The option to send  a  message is available under the  Add   button.   The option to provide additional comments or attachments to the Apptimized team is available under the  Factory activity block  after the Factory request was solved. The option to ask additional questions to the Apptimized team is available under the  Report a problem   button. Apptimized provides the following modal window when successful: The option to write a text message is available under  the  Write your problem   field. Note. This field is mandatory. The option to attach  a  file is available under the  Select file   field. The option to change the attached file is available under the  Change   button.   The option to remove the attached file is available under the  Remove   button. The option to send  a  message is available under  Send   field.  Cancel –  reverts to  general Factory process  workflow. Apptimized shows the message history interface when successful: Note. The a ttached  files appear above the message history interface. If Apptimized needs some additional information, a user will receive notifications and a warning icon in the dashboard:   If there is  feedback from the user  regarding   the Factory Request, the following notification and status in the dashboard appear:   Apptimized provides the following  notification and  status es  in workflow and dashboard  after the request was solved:   Finish Discovery - Factory Service The Finish button becomes active when a request is approved by a user. The option to create a new request is available under the Create new request button. Apptimized shows the following modal window to confirm the request approval: Apptimized shows the following screen when successful: The option to finish Discovery - Factory Service process is available under the Finish button. Apptimized shows the following screen when successful: Packaging The following scenarios to open the transition screen available: My Dashboard > My Applications > Choose the project > Actions column > Process option; Project menu > Dashboards > Overview > Your assignments module > Choose the application > Actions column > Process option; Project menu > Dashboards > Portfolio > Actions column > Process option; Project menu > Import > Start import > Classic import / Import from CSV file / SCCM Import /Catalogue & UM Import > Application upload session > Finish Apptimized shows the following screen when successful: The packaging process starts by clicking the Packaging module on the Transition screen. An imported application into a project is a prerequisite. Two packaging scenarios available in Apptimized portal: Packaging – Self Service; Packaging – Factory Service. Packaging – Self Service A user implements a built-in packaging tool on VMs – Apptimized Workspace. A user can easily in a couple of clicks create one or several packages of multiple formats and send them to Apptimized for further testing or deployment. Packaging – Self Service characteristics: A user packages the application using the Apptimized Packaging Tool; A user creates and customizes MSI, App-V, MSIX, VSL packages; A user customizes an existing package or sequence; A user tests and debugs installations. The Packaging - Self Service option is available under the Packaging - Self Service module in the Transition screen . Apptimized shows the following screen when successful: Packaging tab Start VM The field Select packaging – self service platform  is filled automatically and can be changed if needed. To change the packaging – self service platform, click the drop-down menu as it is shown in the screenshot below: The option to revert to the transition screen is available under the Go to Transition screen button. The option to use an original Windows desktop image is available via the support link on the Packaging — Self Service screen. The option to start the packaging – self service process is available under the Start VM button. A user can track the VM loading and deploying. Apptimized shows the following screen: Note.  There is often a situation when a user has already run 2 VMs in parallel. To continue planned activities within the current workflow step, a user must terminate an irrelevant VM. In this case, Apptimized shows the warning box with a list of VMs which are currently running by the user: The information is grouped into the following categories in the modal window:  1. Application 2. VM started time 3. Workflow progress 4. Link The option to select a VM for termination is available under the Go to VM link. A new tab opens when successful: When a VM is terminated, a user returns to the screen where he needs to restart a VM (previously a user started a VM but received a modal window with a list of running VMs). Apptimized shows the following screen when successful: Note. If the internal error while starting VM occurred, Apptimized shows the following screen: The following actions are recommended for consideration by a user: 1. Contact the Apptimized support 2. Go to image page button > Select discovery – self-service platform field > Start VM button The option to copy files to Temp storage  is available under  Explorer context menu  >  Copy To Temp : The option to restart VM is available under the Restart button. Apptimized shows the following modal window to confirm restart the task: Apptimized shows the following notification when successful: Workspace Launcher General overview  Apptimized Workspace Launcher  is a Windows-based application  that  provides a user with a packaging toolset within Apptimized cloud environment.   With the  Apptimized Workspace Launcher ,   the   cloud   environment is prepared according to  a  user’s  preference s  so that  any additional  activities  to start packaging are not needed.   With the release of the Workspace Launcher, new shared storage implemented that empowers a user with the enhanced upload and editing capabilities: Editing packages is available both via Apptmized Packaging Engine and favorite third-party tools. All packages synchronize automatically from the VM to the project once it is located in the Packages folder. Apptimized  Workspace Launcher enables the user with additional tools, as part of their daily packaging experience. With  Apptimized  Workspace  ( providing Discovery, Packaging, Testing as Self-Service )  by implementing Workspace Launcher, users can add to the functionality already offered to overcome many packaging scenarios.   The  Apptimized  Workspace Launcher  comes preinstalled on  Apptimized  VMs and  could be launched by a shortcut on the VM’s desktop.   Note.   When the VM starts, the application imported within the project and the VM’s shortcut are available. The packaging toolset is no installed. Once the user selects tools to implement for the desired deliverable, the application starts automatically.   The Apptimized Workspace Launcher applications have no impact on an operating system. The operating system always stays clean, so  no  repackaging conflicts occur ,  or  system  noise does not affect  the  user’s packaging session. By default,  Apptimized Workspace Launcher   comes with the following user interface (UI).   The  Apptimized  Workspace Launcher   UI  consists of  the following elements :   UI element Description 1. Categories filter This component allows a user to navigate between different categories of applications (bundles) and filter the content pane. The following categories available: All App-V Msi Msix Productivity System Utility 2. Top panel 2.1.  Favorites tab This component contains a list of  applications  ( bundles ) a user  marked  as  a  favorite.   2.2. Tools  tab   This component includes a full list of applications in a current category. 2.3. Installed tab This component contains a list of  applications  a user installed .   2.4. Search Launcher field This component enables a user to apply search activities within the current  applications pane .   Keyword search mode available  under the  Search Launcher field > Enter   a   search request. The search result appears when successful:   3. Applications pane This component contains a list of applications (bundles) within the current pane. The list of displayed applications on the Applications pane varies according to the implemented Categories filter and the selected tab. The Applications pane contains items of 2 different types: Application Bundle 4. Current user information 4.1. Launcher settings This component provides information about the logged-in user. Apptimized Platform automatically identifies a user who started the VM within the specific project and step, which considers the user’s preferences. The icon provides a user with Workspace Launcher settings (see the Launcher settings ). Launcher settings Workspace Launcher settings allow a user to create customizable bundles with applications available in Workspace Launcher. Workspace Launcher settings provide a user with two options: Options Manage bundles Exit application  The option to close Apptimized Workspace Launcher application on the VM is available under the Exit application button.  The option to enable shortcuts for Laucnher applications is available under the  Options  bundle. Apptimized shows the following screen when successful: The options to Add Desktop shortcuts and Start menu shortcuts become available when switched on: If applications are installed, then shortcuts are available on the desktop or/and the start menu, according to switched on option. The option to create and manage bundles is available under the Manage bundles button. Apptimized shows the following screen when successful: The option to create a new bundle is available under plus symbol. Apptimized shows the following modal window: Setting Details Bundle name The bundle   name  field allows  defining the bundle name (e.g., MSI ).   The re is no  default value  for this field .   Bundle description The bundle   description field allows  defining the bundle description (e.g., Tools for packaging MSI format ).   The re is no  default value  for this field .   Select categories The select categories   field allows  defining the categories for a new bundle.  The following options available:  App-V MSI MSIX Productivity System Utility There is no default value for this field.  The option to choose a few categories is available. Select applications The select applications   field allows  defining the applications included in a new bundle.  The following options available:  7-Zip Adobe Creative Cloud Cleaner Tool Adobe Customization Wizard App-V 5 Configuration Editor App-V Manage Apptimized MSI Editor Apptimized Packaging Engine Apptimized MSIX AppAttach Converter AppV 5.1 Sequencer Double Commander InstEd InstallWatch LockHunter MSIX Packaging Tool Notepad++ Orca Process Explorer Process Monitor PsExec Resources Extract WhatChanged There is no default value for this field.  The option to choose a few applications is available. To apply the settings, click the  Create bundle  button.  Cancel - reverts to the Manage bundle section. Apptimized shows the following notification when successful: The screenshot below shows a result for the creation of a new bundle: The icon allows a user to edit a bundle, the icon - delete a bundle. Application Application is the smaller actionable item of the Apptimized Workspace Launcher. The application is represented in the form of a card: Application cards are   in a minimized mode   Application cards are  in a maximized mode   Each application card consists of the following elements:   Element Description 1. Icon This block contains a visual logo of an application. 2. Icon to minimize / maximize application card An icon that allows a user to expand or collapse the application card. - An application card is in a minimized mode - An application card is in a maximized mode 3. Application metadata This block contains the meta information of an application. Application metadata is provided by the template (from top to bottom): Application name Application vendor Application version Note. The icon appears when a link to the application vendor site available. 4. Installation button This button enables a user to install an application. 5. Icon to favorite / unfavorite an application An icon that allows a user to toggle the favorite status for an application. - An application is not marked as a favorite - An application is marked as a favorite The Install automatically switch becomes available when successful: 6. Application description This block provides a brief description of the purpose of an application 7. Shortcut buttons This block provides the set of s hortcuts to most usable actions  with an application.   A   process ( action ) gets started by the click on the shortcut button.     Note.  If  a  user has not yet installed the application ,  the  Apptimized Workspace Launcher  will proceed following  steps  after clicking on the Shortcut button :   1. Application installation.  2. Application launch with the required functionality .   Bundle  The bundle is the set of applications that have been grouped by certain usage logic ( e . g ., a toolset for MSI packaging/ editing).   The screenshot below shows  the examples of   the  Apptimized Workspace Launcher   build-in bundles:   The bundle  is represented in  the  form of a  card:   Bundle card is in a minimized mode Bundle card is in a maximized mode   Each bundle card consists of the following elements:   Element Description 1. Icon This block contains a set of visual logos of applications the bundle consists of. 2. Icon to minimize / maximize bundle card An icon that allows a user to expand or collapse the bundle card. - A bundle card is in a minimized mode - A bundle card is in a maximized mode 3. Bundle name  This block contains the name of the bundle and the number of applications the bundle consists of. Application metadata is provided by the template (from top to bottom): Bundle name Number of applications 4. Installation button This button enables a user to install a bundle. 5. Icon to favorite / unfavorite a bundle An icon that allows a user to toggle the favorite status for an application. - A bundle is not marked as a favorite - A bundle is marked as a favorite The Install automatically switch becomes available when successful: 6. Bundle description This block provides a brief description of the purpose of a bundle Key functionality Mark as a favorite The option to mark an application or a bundle as a favorite is available under the Star symbol. The application (bundle) becomes available in the Favorites  tab when successful: Application installation  The option to install an application is available under the  Install  button:   Note.  All applications are in the uninstalled state by default.   Every application  goes through  3 states:   Bundle installation The option to install a bundle is available under the Install button: In this case, the Apptimized Workspace Launcher installs all applications that are part of the bundle collection. The progress bar shows the aggregated process of the collection installation. Note. All bundles are in the uninstalled state by default. Every bundle goes through 3 states: Install automatically The Install automatically switch becomes available after an application or a bundle was marked as a favorite: The option to install an application or a bundle automatically becomes active when switched on. The option is inactive by default. Note. If a user has not yet installed the application, the Apptimized Workspace Launcher will install an application after enabling the Install automatically switch. In the case of a bundle, all contained applications (regardless of the status of an application: favorite / unfavorite) will be installed automatically when the  Install automatically  switch is enabled. Run application The following scenarios to run an application available: Select an application > Click on the Shortcut button (e.g., Run APE ) Select a bundle > Select an application > Click on the Shortcut button (e.g., Transform existing MSI ) Note. If a user has not yet installed the application, the Apptimized Workspace Launcher will proceed following actions after clicking on the Shortcut button: 1. Application installation. 2. Application launch with the required functionality. Upload results from VM to Apptimized Portal To upload created via Workspace Launcher deliverables to Apptimized Portal a user needs to place them into the Packages folder before VM is finished (VM desktop > Apptimized files icon > Packages folder). Note. By default, the Packages folder comes with the Log folder which contains system information.  It is prohibited to a user to add any files to this folder. The Log folder will not be uploaded to the Apptimized Portal after VM is finished. During the synchronization process, every file is treated as a unique package. In case a user created a complex deliverable (i.e., a folder contains 2 or more files) this folder must be compressed into a ZIP archive. The naming of files, folders, and archives should be consistent with the name patterns indicated in the Project settings . Apptimized shows the following screen when successful: Apptimized Packaging Engine The  Apptimized  Packaging Engine (APE) launches when  clicking  Install  the  Apptimized  Packaging Engine   >  Run APE .   The process may take few moments. Apptimized shows the Apptimized Packaging Engine (APE) main screen when successful: Table 1. Apptimized Packaging Engine options Option Details Repackage to MSI, App-V, MSIX, IntuneWin or VSL This option is snapshot-based and enables to create a completely new installer. This option is applicable when a user has a non-MSI vendor installer. A user converts it to MSI or App-V or virtualizes MSI installer into App-V. Transform and edit vendor MSI This option enables the transformation or customizing the existing Windows Installer. This option is applicable when a user has an MSI-based vendor installer and needs to produce an MST for it containing changes made during the installation process and/or configuration post-installation settings. Review and edit result This option enables to review the packages. The option becomes available only after a user completed the repackaging or transformation procedure. Save locally This option enables saving the output locally to verify before uploading back to Apptimized. Upload result to Apptimized This option enables uploading verified output back to Apptimized. A user can upload the output generated by Apptimized or select an archive with modified files to be used as an output. APE general settings The option to review the package formats settings is available under the gear-wheel symbol. When successful APE shows the following screen: A user can scroll down and review the package format settings. The package formats settings are predefined and correlate with the Project settings ( Workflow settings ). A user can provide changes to the settings if needed. When changes to the package formats settings applied, click the Save button. The option to save settings as XML file is available under the Save as xml button (Choose the root to save XML file > Save button). Apptimized packaging engine release notes The option to open Apptimized packaging release notes is available as a TXT file under the file symbol on the APE menu (top right corner). Repackage to MSI, App-V, MSIX, or VSL When clicking the Repackage to MSI, App-V, MSIX, or VSL option, the APE will redirect a user to a Wizard. A user needs to provide input at each step. Capturing installation and configuration APE will capture all changes made to the system by scanning a file and registry changes, after that converting it to a machine-readable form. Those changes will typically include the installation of the application and the features selection, as well as customization of the application's settings to reflect the desired result as documented during the Discovery step. VM preparation and prerequisites installation must proceed before packaging. The prerequisites are considered as applications that need to be present for a user’s software or its installer to function, but a user does not want those software products to be included into the package (e.g., because a prerequisite is already installed on the user’s machines or is managed as a separate dependency package). The option to start a recording session is available under the Start recording button. Note. Any VM activity or inactivity can leave traces in the captured result (including those not relevant to the package or application results). A user needs to confine to the activities needed for packaging and finish the process as quickly as possible). APE shows the following notification when successful: The option to suspend capturing changes made to the filesystem and registry is available under the Pause button. The option to resume the recording is available under the Pause button (click the Pause button again). Once the recording has started a user enables a user to browse the path of the installation file ( Browse button). The option to provide the additional parameters (i.e., to specify additional launch arguments) is available under the Parameters (optional) field. Once the file has been selected, the Run button becomes active. When the synchronization process is finished, APE shows the following screen: When the installation and configuration activities are completed, the record must be finished. The option to stop the record is available under the Stop recording button. This will terminate the recording process and prepare the captured system changes for producing an MSI, MSIX, App-V, or VSL. The terminating process may take few moments (additional post-processing and cleanup will be applied to the output). Note. Apptimized applies advanced logic and filters to keep the snapshot result clean from unneeded or dangerous files and registry keys. However, typically captured results require manual review and adjustments to achieve the desired result or to apply further cleanup from the captured system or user activity. The processing file system changes may take few moments: When successful APE shows the screen: Editing Application Metadata A user can review and adjust the application metadata if required. The default values generate from the portfolio metadata provided during the file import process and do not need to be changed in most of the cases. If the installation session consisted of more than one installer, select the primary installer to extract the metadata. Review captured content The option to the recorded content for the files, registry entries, services, and other system items that were modified or created during the installation is available under the Review recorded content button. APE shows the snapshot editor screen when successful: A user can navigate across different tabs based on the captured content nature: Filesystem; Registry; Shortcuts; Drivers; Services; Certificates; Environment; Registry ACL; Filesystem ACL; Firewall Rules. Filesystem and Registry tabs are presented in a tree structure view. Shortcuts , Environment , ACL , Services , and other tabs are presented in a table-based view. The Filesystem tab shows captured changes to the filesystem (file & folders). The Registry tab shows captured changes to the Windows registry. The Shortcuts tab shows captured shortcuts. The  Drivers  tab shows captured drivers. The Services tab shows all services which were created during source installation. The Certificates tab shows all changes which were added to the Certificate Stores. The Environment tab shows captured environment variables created during the source installation. The Registry ACL tab shows captured permission changes in the Windows registry. The Filesystem ACL tab shows captured changes to filesystem ACLs. An Access Control List (ACL) is a list of Access Control Entries (ACE). Each ACE in an ACL identifies a trustee and specifies the access rights allowed, denied, or audited for that trustee. The Firewall Rules tab shows firewall rules created during the source installation. Due to the nature of the recording process, unwanted resources, also known as system activity or noise, might be captured into the recording result. These happen because the system is altered by the installation (or by the application, by the user, by the other applications, and by the operating system itself) during packaging in areas that are unrelated to the application and are not needed in the package. Those unwanted resources might negatively influence the installation or uninstallation of the package, or other applications and the operating system's stability, or, at least, create unneeded bloat. System activity traces and noise cleaning is required to receive good-quality packages. When recording completed, APE applies a default exclusion list, which filters most of the unwanted system changes from the package (which need to be removed from the package). A user can additionally exclude unwanted resources or re-include resources that were automatically excluded from the list. Such actions should only cover specific scenarios involving changes to the operating system. The option to exclude the files from the package is available under the context menu or using the keyboard shortcuts Ctrl+E or Del . The option to include the files to the package is available under the context menu or using the keyboard shortcut Ctrl+I . Captured resources that are intended to exclude from the package are shown with a red overlay. Captured resources that are intended to include the package are shown with no overlay. The status bar with the total number of files and the number of included files is available in the footer of the Review recorded content window. The option to search files or folders by name is available under the Search in files field available in the footer of the Review recorded content window. The screenshot below shows the tab interface with table-based view (i.e., Shortcuts tab): To exclude the item, tick the checkbox in front of its name. Table 2. Shortcuts tab structure Column name Details Exclude This column provides the option to include or exclude entities. Icon This column provides the shortcut icon. Location This column provides details on the shortcut location (i.e., a physical location of the shortcut file). Destination This column provides details on the shortcut’s target (usually target is an executable file). To exclude the item, tick the checkbox in front of its name. Table 3. Filesystem ACL tab structure Column name Details Exclude This column provides the option to include or exclude entities (i.e., detected file or folder ACL). Review This column provides the option to open the Permission properties for the selected file or folder. This dialogue window enables a user to Set, View, Change, or Remove permissions for the current item. Permissions are set recursively, so to set permissions onto a folder, its subfolders and files only configure permission changes on the parent folder level. The option to set permissions for a group or user that does not appear in the Group or user names box is available under the Add button (Type the name of the group or user > OK button). The option to remove permissions for a group or user that appears in the Group or user names box is available under the Remove button (Type the name of the group or user > OK button). The options to allow or deny permission are available under the Permissions for box (Select the Allow or Deny column  > Check / Uncheck the box). The option to set the special permissions or advanced settings is available under the Advanced button. Path This column provides details on file or folder with detected, modified or created permissions. Table 4. Drivers tab structure Column name Details Exclude This column provides the option to include or exclude entities (i.e., detected driver file). Name This column indicates the name of the driver file. Location This column provides details on the driver location (i.e., a physical location of the driver file). Add ARP entry This column provides an option to add ARP (Add-Remove Program) entry which is based on ARPSYSTEMCOMPONENT property value. Remove on uninstall This column provides an option to automatically delete the driver during the uninstallation process. The option to apply the changes to the recording result is available under the Save button. Analyze for common issues The option to review the most common issues which might lead to a non-working or incomplete installation is available on metadata reviewing screen under the Analyze for common issues button. APE shows a screen when successful: This will show the severity of problems, problem codes, and issue description, both with the recommendations on how to reduce the risk. Table 5. Possible values of the analyzer Severity Problem code Description High DriversInSnapshot The installation driver is not supported in repackaging mode. It won't be included in the final package. Medium ServicesInSnapshot Installation services are detected. This can lead to problems with App-V or AppX packaging formats. EnvironmentalVariablesChanged The environmental variables change is detected. A user must sure this won't overwrite existing entries during installation. Low MSIExecLaunched MSI installation is detected. It's recommended to use transformation instead of repackaging until a user converts the installer to the not MSI format. AutoStartDetected Auto-start modification is detected during the installation. DllHostDetected COM registration is detected. An application may not work when packaged in App-V or AppX formats. SystemFilesIncluded System files were modified during the installation. A user must review captured content and exclude unneeded entries. When the review of the common issues is finished, click the Close button. Save project The option to save settings and apply them in the future is available under the Save project button. APE shows the following window (Choose the root to save project > Save button): When the metadata review completed, the option to proceed to the next step is available under the Next > button. Adjust Format Details The following screen shows the default values for package formats: The adjustment of the format-specific settings is available. These settings are typically pre-defined by Apptimized project administrator in the project settings in accordance with the appropriate Packaging Standards . Before overriding any of pre-defined settings, a user must ensure the feasibility and correctness of provided changes. The option to exclude or to include the package formats is available under the switch in front of their names. When the package format review is completed, the option to proceed to the next step is available under the Next > button. When the packages build, the log information is written to the console. In case of a failure this log may be requested by Apptimized support: The blue background indicates that the build process is still in progress. When it turns to a green background the package type/format has been successfully built. The build time will depend on the number and size of the captured files and may take few minutes. The APE finalizes when clicking the Finish button.   Transform and edit vendor MSI The option “Transform and edit vendor MSI” is applicable when: A necessity to provide changes to existing (vendor) MSI's (i.e., installation options, application configuration) appears. This means the vendor provides the source media in MSI format A user’s target format is also MSI. This is also applicable when nested MSI's were found and extracted during the repackaging of a legacy setup. Any changes to the original MSI will be added by a transform file or MST; the original MSI will remain unchanged. It is not recommended to edit vendor MSI directly or even to repackage to another MSI. Repackaging MSI to App-V by is acceptable. The option to transform and edit the existing MSI is available under the Review and edit vendor MSI button. The option to provide the full MSI installer path is available under the MSI installer path field. Table 6. APE transformation settings (transform options) Settings Details Optional command line arguments This setting provides the command to be executed (i.e., msiexec /i [FilePath] /v*l [LogPath]). Include additional files and subfolders from the installer folder This setting specifies if all files and (sub)folders from the folder in which the MSI locates will use. If the setting is enabled, all folder content will use to build the final package. If the setting is disabled, only the MSI and CAB files will use (everything else will be ignored). The setting is disabled by default. Do not execute installation actions This setting enables a user to run through the MSI's setup screens and do not need to perform a true installation. In that case, only property changes captured by inputs into the MSI's dialog will be taken. The filesystem and registry will remain untouched. The setting is disabled by default. Capture post-configuration This setting enables a user to include additional configuration items outside the MSI setup screens into the MST after the installation (i.e. post-configuration), e.g.: adding extra files or adding extra registry keys. The following cases to capture changes in the MST available: Changes are captured in a separate intermediary MSI; The intermediary MSI is merged into the MST; The intermediary MSI is discarded. Wrap into .intunewin bundle for Intune deployment This setting enables a user to create the .intunewin bundle for Intune deployment. The setting is disabled by default. Package release This is the package version. It is used in the package name. Initially, a release version is 01. If something needs to be changed in this package, then release 02 is made, and the package name differs from the initial one. The package release is not similar to the application version ( (i.e. the application version can be the same but the release will be 02 because some files were added). The field can stay blank. Package release property prefix This prefix is used in the names of the created MSI components, properties, and custom actions. This is the element of branding. A user can put the prefix (i.e., [company name]_SiteURL). So, when the MSI reviews, a user can understand what properties were added additionally (i.e., not by default). Install/Uninstall script file type This setting indicates the script file type. The following script file types available; Batch , PowerShell , and Vbs . The default value is Batch . The APE transform options finalized when clicking the Next button. APE shows the following screen: When the setup wizard procedures are finished, click the Finish button. APE shows the following screen: When the installation completes, a list of MSI properties which were added or changed during the installation is available: PROPERTY = Windows Installer Property name VALUE = Windows Installer property value set during installation DELETE = Delete properties you do not want to include in the MST. The option to change the property name or value is available by double-clicking on the relevant cell. The option to delete an item is available under the bin symbol ( Delete column). Note. Apptimized always replaces special properties. The following properties are marked as red under the transformation screen: When the MSI properties list is reviewed, click the Finish button. The transformation process may take few moments: APE shows the following screen when successful: The option to launch the built-in MSI editor and edit the output is available under the OK button. This case provides changes in the application's settings store in registry keys, which are captured and subsequently merged into the MST file by the "post-configuration capturing" process. The instructions on editing the result in Advanced MSI Editor are provided below. Wrap file(s) Create Wrapper The option to wrap files i.e ., wrap fully configured package - repackaged MSI, MSI+MST, Silent EXE, or package with Apptimized Wrapper ) is available under the Wrap file (s ) > Create Wrapper   tab The process includes the following steps:   Choose the wrapper       Default wrapper is available by default.     Enter the package type     The following package types are available:     MSI   Transform   Legacy   App-V   Empty Wrapper     Clicking the Next button enables proceeding to the Configuration step. APE shows the following windows when successful:       Select source folder or archive files, select necessary file in package format       Note. All content from source folder/archive will be copied to the package   Clicking the Next button enables proceeding to the Review step. APE shows the following window when successful:       The following options to change are available:   Option   Description   Vendor   Indicates application vendor short name   Software   Indicates application software short name   Version   Indicates application version   Language   Indicates language of the application. The following options available:   ENG   DEU   MUI   Architecture   Indicates architecture of the package. The following options available:   x86   x64   PackageRelease   Indicates number of package release   Platform   Indicates platform where package was tested   ScriptDate   Indicates script create/change date in format MM/DD/YY   MSIName*   Indicates MSI location and name(e.g. $env:ProgramFiles/.../Setup.msi)   * - available only for MSI package type.   PackageNameAppv**   Indicates Package Name of AppV package without extension   ** - available only for AppV package type.   APPVPath**   Indicates path to directory with .appv file   ** - available only for AppV package type.   VendorEXESilentInstall***   Indicates path to vendor exe for legacy installation e.g. $env:ProframFiles/.../Setup.exe)   *** - available only for Legacy package type.   VendorEXESilentUninstall***   Indicates path to vendor exe for legacy uninstallation e.g. $env:ProframFiles/.../unin000.exe)   *** - available only for Legacy package type.   SilentInstallParameters***   Indicates silent parameters for installation(e.g. /silent).   *** - available only for Legacy package type.   SilentUninstallParameters***   Indicates silent parameters for uninstallation(e.g. /silent).   *** - available only for Legacy package type.   Uninstall hives***   Indicates all uninstall hives that must be updated, separated by “;”.(e.g. HKLM:SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\18469ED8-8C36-4CF7-BD43-OFC9B1931AF8);HKLM:SOFTWAREWOW6432Node\Microsoft\' dows\CurrentVersion\UninstallV0240359E-6A4C-4884-994-B397A02D89301)   *** - available only for Legacy package type.   MSTName****   Indicates MST location and name(e.g. $env:ProgramFiles/.../Setup.mst)   **** - available only for Transform package type.   Clicking the Next button initiates the Wrapper creation   Wrapper file generating finalizes when clicking the Finish   To finalize the packaging activities, a user must proceed to the reviewing and editing results in APE.   Wrap to IntuneWin The option to create the IntuneWin package (i.e., wrap fully configured package - repackaged MSI, MSI+MST, Silent EXE, or package with Apptimized Wrapper) is available under the   Wrap file (s ) > Wrap to IntuneWin   tab The process includes the following steps: 1. Enter the package name; 2. Select source files folder ( Folder icon > Navigate to source files folder > OK button). The processing source folder may take a while. 3. The Setup file , Install command , and Uninstall command fields are filled-in automatically according to the source files A user can change the prefilled values for these fields. The following setup file types are available: MSI, EXE, VBS, BAT, CMD, PS1, and JS. APE selects the MSI / EXE by default. The option to select the executable file type is available when clicking the drop-down menu in the Setup file field. When choosing an executable file (other than MSI), install and uninstall commands must be set manually. A user can enable Interactive mode . Clicking the Next button enables proceeding to the IntuneWine package creation. APE shows the following windows when successful: 4.  IntuneWin file generating finalizes when clicking the Finish APE shows the following windows when successful: As a result, a user receives the IntuneWin file and text file with the install / uninstall commands, and detection method. To finalize the packaging activities, a user must proceed to the reviewing and editing results in APE. Review and edit results The option to review and edit the packaging result is available under the Review and edit results button. APE shows the package hierarchical tree structure view. The option to rename components is available under the context menu (Context menu > Rename option > Enter a new name  > OK / Cancel button). The option to delete components is available under the context menu (Context menu > Delete option > OK / Cancel button). The option to add components is available under the context menu (Context menu > Add existing files option > OK / Cancel button). The option to add components is available under the context menu (Context menu > Add new folder option > Enter a folder name > OK / Cancel button). The option to add components is available under the context menu (Context menu > Add new folder option > Enter a folder name > OK / Cancel button). The option to launch the Advanced MSI Editor is available under the context menu (Context menu > Edit option). The preparation procedure will take a few moments. Advanced MSI Editor main window appears when successful: Table 7. MSI Advanced Editor menu components Component Details File This component provides the commands for working with the installer file. The following options available: New; Open; Open recent; Save; Save As; Exit. Edit This component provides the commands to apply/cancel last committed action as well as the command to enable the search window. The following options available: Undo; Redo; Find / Replace. Tables This component provides the commands for manipulating the MSI tables, to enable the Summary info and Code Page. The following options available: Add tables; Import tables; Summary information; Code page. Tools This component provides access to the import commands to perform install and uninstall processes. The following options available: Import files; Import registry; Import ini file; Install; Admin install; Uninstall; View Log. Transforms This component provides access to commands for working with the transforms. The following options available: New transform; Apply transform; Remove transform; Save transformed. Validations This component allows ICE validation using existing or custom cub files. The following ICE validations options available: Internal Consistency Evaluators – Full Set (darice.cub); Internal Consistency Evaluators – Merge Modules (mergemod.cub); Internal Consistency Evaluators For NT5 Logo (logo.cub); Internal Consistency Evaluators For Windows Vista Logo (Vistalogo.cub); Internal Consistency Evaluators For XP Logo (XPlogo.cub); Use a custom cub file for validation. Scripting This component executes an existing or custom script. The following options available: Remove shortcuts on the desktop (Remove-Desktop-Shortcuts.ps1); Use custom script. Help This component enables the help mode. The MSI Advanced Editor contains the following tabs: Application; Files; Registry; Shortcuts; Features & components; Custom actions; Properties; Environment; Tables. Table 8. MSI Advanced Editor menu tabs Tab name Details Application This tab provides basic information about MSI. Files This tab enables to work with files associated with the MSI. The files are presented in a hierarchical tree structure view. Folders that contain files are displayed in yellow. The folder’s content is displayed in the table on the right side of the MSI Advanced Editor window. The files in the table on the left can be edited. It is also possible to add and remove custom and standard directories.   The option to delete files is available under the: Cross symbol; Context menu > Remove option. The option to rename files or folders is available under the: Double click on the item > Enter item’s new name > Enter; Context menu > Rename option > Enter. The option to add folders is available under the: Context menu > New Standard Folder option > Select a folder type from the list; Context menu > New Custom Folder option > Enter. The option to add files is available under the: Plus symbol > Import Files option > Import files wizard; Context menu > Import Files option > Import files wizard. The files import process involves the following iterations: 1. Select the target directory: Click the Target Directory field > Select the directory from drop-down list > Continue button; Click the Plus symbol > Insert a new row into the table “Directory” > Enter directory name > Select the directory parent mode from drop-down list > Enter DefaultDir name > Save button > Continue button. 2. Select files or folders to import: Click the Plus symbol > Add files / Add folder button > Browse to find the file > Double click to add the file > Continue button. 3. Select features to assign new components (Select the Feature > Select the Cab type > OK button). 4. The added file appears in the tree.   The option to hide empty folders is available under the Hide empty checkbox on the bottom side of the MSI Advanced Editor window.   Note . When a user adds files & folders that already exist, Advanced MSI Editor shows the following modal window: Registry This tab enables editing registry keys (i.e. add/remove registry keys, import from the file). The registry keys are presented in a hierarchical tree structure view. The registry keys details are presented in the table on the right side of the MSI Advanced Editor window. The option to add a key, registry value or import from a file is available under the Context menu .   The option to add a new value is available under the Context menu > New value option: A new variable creates an empty name and value fields. Double click sets the values of the corresponding fields. The following registry key values available: String; Integer; Binary; Expandable string. The default value is String . The option to create the new key is available under the Context menu > New key option > Enter a new key name > Save button: The generated key will appear in the tree: The renaming and importing activities are the same as in the previous tab. Shortcuts This tab enables a user to create, delete or edit shortcuts. The buttons indicated in block 1 on the screen below are used to add and remove shortcuts. The button indicated in block 2 is used to edit the parameters of the selected shortcut. The option to delete the shortcut is available under the Context menu > Remove shortcut option: When creating a shortcut, an entry with default values appears:   The shortcut changes save when clicking the Save button. Features & components This tab enables a user to add, remove and edit features and components . The option to add a new feature is available under the: Plus symbol > New child feature option; Context menu > New child feature option. The option to add a new component is available under the: Plus symbol > New child component option; Context menu > New child component option. When a new feature or component is added it appears at the end of a tree view: The option to delete an item is available under the: Context menu > Remove option; Cross symbol > Delete just this item / Delete all. When creating a new feature, an entry with default values appears: When creating a new component, an entry with default values appears: The features and components changes save when clicking the Save button. Custom actions The tab enables to view and edit custom or standard Windows Installer actions. The option to add a new custom action is available under the: Plus symbol > New custom action option; Context menu > New custom action option. When creating a new custom action, an entry with default values appears: The following source types available: EXE file stored in a Binary table stream DLL file stored in a Binary table stream JScript file stored in a Binary table stream VBScript file stored in a Binary table stream DLL file that is installed with a product EXE file that is installed with a product Displays a specified error message and returns failure, terminating the installation JScript file that is installed with a product VBScript file that is installed with a product EXE file having a path referencing a directory Directory set with formatted text JScript text stored in this sequence table VBScript text stored in this sequence table EXE file having a path specified by a property value Property set with formatted text JScript text specified by a property value VBScript text specified by a property value The option to choose a binary resource from the file system while creating new custom action is available under the Browse button. MSI advanced editor enables the Browse button when one of the “ … file stored in a Binary table stream” source types is selected.   MSI advanced editor automatically creates a row in Binary table when successful:   The option to add a new standard action is available under the: Plus symbol > New standard action option > Select the action type from the drop-down list; Context menu > New standard action option > Select the action type from the drop-down list. When creating a new custom action, an entry with default values appears: New action is enabled by default. To disable the action, uncheck the checkbox in front of its name (or Context menu > Disable option). The option to delete action is available under the: Select the action in the actions list > Cross symbol; Context menu > Remove option. Properties This enables a user to work with the global variables that Windows Installer uses during an installation. The checkboxes on the left enable filtering by property type. Note. Advanced MSI Editor mark additional properties added under the Project settings (see ARP & Properties ): Environment This tab enables a user to work with environment variables that Windows Installer uses during an installation.   The option to add new envrionemt variable is available under the:   Plus  symbol >  Add variable  option;   Context menu >  Add variable  option;   When creating a new custom action, an entry with default values appears:   The option to create dummy component is available after choosing Component under Component drop-down list >  Create Dummy  button.   The option to create variable is available after filling Environment, Name, Value, Component fields > setting Context, Mode, Install behaviour, Uninstall behaviour options >  Save  button.   AME shows the following screen when successful:  Tables This tab enables to work with MSI tables. The list of available tables is on the left. Empty tables are hidden by default. The checkbox on the bottom of the list enables a user to see empty tables. The grid on the left displays the contents of the table. The content is editable if the table is not read-only.   The table below is the table of contents: The first tab shows the records associated with the selected item, the second tab shows the result of the validation: Save locally The option to save results to the local filesystem for further editing or inspection is available under the Save locally button. The Save locally option becomes active when a package produced. To options to save results available: Uncompressed and Compressed . The default value is Compressed . The result comes compressed in a ZIP file. Upload result to Apptimized The option to transfer the package(s) from the VM to the Apptimized frontend is available under the Upload result to Apptimized button. Two options available: Upload results archive produced during the repackaging/transformation processes from the VM to the frontend; Upload custom file from the VM's file system ( ZIP archive) to the frontend. To select the option, check the box in front of its name (Check the box > Start uploading button). The upload process time depends on the file size and may takea few moments: APE shows the following notification when successful: When the files uploading process is completed, the VM can be terminated. The options to finish the VM session is available under the Finish button. Apptimized shows the following modal window: The following interface will appear when recording session with Apptimized VM finishes: Apptimized MSIX AppAttach Converter General Overview     MSIX  A pp  A ttach is a way to deliver MSIX applications to both physical and virtual machines.   A   Microsoft technology  allowing  to make MSIX packages compliant for virtualized desktop environments such as Windows Virtual Desktop.    The  Apptimized MSIX AppAttach Converter  is a tool that allows to automatically convert the existing MSIX packages to VHD (Virtual Hard Disk) files based on MSIX App Attach technology.   The tool is available  i n  the  Workspace Launcher (see the  Workspace Launcher ).   The option to install the application is available under the Install button (see the Application installation ). Convert existing MSIX package A user can convert the existing MSIX package into MSIX app attach package. This option is available under C onvert the existing MSIX package button. Apptimized shows the following screen when successful: A user can select the existing MSIX package by clicking the Folder icon. A user can select an MSIX file that will be automatically converted to the app-attach package and click the Open button to start the converting process. Apptimized shows the following screen when successful: The creation process may take few moments. Cancel - stop the VHD file creation. After completing the creation a user can save the app-attach package (VHD file by clicking the Save button. The process may take few moments. Apptimized shows the following screen when successful: Package wrapping A wrapper is a set of PowerShell scripts that provides a set of functions to perform common application deployment tasks and to interact with the user during deployment activities. It provides information about the package, commands for installation, de-installation, and post configuration. Regardless of the number of installers in the package, a customer needs to run only the executing wrapper. The option to wrap a recently produced package is available under the Wrap package button. The Wrap package button becomes available when a user has completed the packaging activities and finished the VM. Note. To apply custom templates, a user needs to configure them in Project settings . Apptimized shows the following modal windows: The table below shows the components of the default wrap file configuration at  Initialize  step: Setting Details Wrapper This field indicates the wrapper to be used for wrapping.   The following options are available:   Default Wrapper   [Custom template 1]   [Custom template 2]   …   [Custom template N]   The default value is  Default Wrapper .   Package type This field indicates the list of package types for which this template will be applicable.   The following package types available:   MSI   Transform   Legacy   App-V   The default value is  MSI .   The option to switch to step  Configure  is available under  Next  button. Apptimized shows the following modal window when successful: The option to populate MSI properties is available under package folder > package file The option to switch to step Review is available under Next button. Apptimized shows the following modal window when successful: The table below shows the components of the default wrap file configuration at Review step: Setting Details Vendor This field indicates the vendor of the application. The data synchronizes from the metadata collected at the Import step. Software This field indicates the name of the application. The data synchronizes from the metadata collected at the Import step. Version This field indicates the version of the application. The data synchronizes from the metadata collected at the Import step. Language This field indicates the language of the application. The following options available: ENG DEU MUI The multiple-choice is available. Architecture This field indicates the package architecture. The following options available: x64 x86 The default value is x64 . Package Release This field indicates the package’s version number. The following options available: 01 02 03 Platform This field indicates the platform the test activities were provided. The following options available: Win 10 Win7 Win2k8 Win2k12 Win2k16 Win2k19 The multiple-choice is available. Vendor M S I This field indicates the Vendor name of the selected MSI (i.g., Setup.msi).   Note. This field appears only if the  Transform package type was selected under Initialize  step and the MSI file was selected under  Configure step. Script Date This field indicated the date when the script was created or changed. The default value sets to the package creation date (i.e., Month/Day/Year ). Product Code This field indicates the MSI product code using the template {ProductCode} . MST Name This field indicates the MST file name(i.g., Setup.mst).   Note. This field appears only if the  Transform package type was selected under Initialize  step and the MSI & MST files were selected under Configure step. Package Name This field indicates the name of the package installation file (i.e., TimKosse_FileZilla_3.48.1 ). The package name generates according to the Project settings. A user must follow the naming templates indicated in the Project settings > Workflow settings > Packaging – Self Service > General . The wrap file configuration is applied when clicking the Wrap button. Apptimized shows the following screen: The wrapped package appears in the list when successful: The option to download packaging results is available under the Download button. When the packaging results downloaded, a user can proceed to the next step by clicking the Finish button or can test the package by clicking the Testing tab. Testing tab The best practice is to test packages on a clean machine, i.e. on a different VM than the one the package was created. This also applies to package iterations performed to test the impact of changes made to the package during packaging and editing, also known as trial and error. At the same time, it makes sense to keep the actual packaging machine as a reference for a working installation. Therefore, Apptimized provides a second VM within the Packaging step under the Testing tab. It is possible to switch between the Testing and the Packaging tabs while both VM's are up and running. Again, the Packaging and the Testing  VM's act independently but share the A:\ drive. Whenever a clean VM is needed again (e.g., after some tests), click the Restart button on the Testing tab, and a VM will be provisioned instantly. A user can do the same on the Packaging tab but must be aware that this will discard "reference installation". Apptimized shows the following screen when clicking the Testing tab. The field Select packaging – self service platform  is filled automatically and can be changed if needed. To change the packaging – self service platform, click the drop-down menu as it is shown in the screenshot below: The option to revert to the transition screen is available under the Go to Transition screen button. The option to start the packaging – self service (package testing) process is available under the Start VM button. Apptimized shows the following screen when successful: The option to restart VM is available under the Restart button. Apptimized shows the following modal window to confirm the restart task: Apptimized shows the following notification when successful: The option to launch the package is available under Packages folder > [Package name]> [Package type] > install.cmd . A package will install automatically without requiring any user input: The packaged application must be launched, to check that all configuration settings are correct. A setup wizard will appear: When the package testing activities finish, the VM must be terminated. The options to finish the VM session is available under the Finish button. Apptimized shows the following modal window: The following interface will appear when recording session with Apptimized VM finishes: The option to download package testing results is available under the Download button. When the packaging results are downloaded, a user can proceed to the next step by clicking the Finish button. VM control menu The VM control menu panel is available in the upper right corner of the VM interface. Next, each settings category is shown in more detail. Table 9. VM control menu Control menu category Details Add prerequisites/Edit prerequisites This setting enables a user to add prerequisite applications. Portfolio  tab is available by default.  Update Monitoring  &  Catalogue  tabs become available if there are delivered packages on them. Portfolio  tab   The option to select application is available under  Select applications  field. The option to select media type for applications is available after the application was selected. The following media types available: Package Source Note . One media type is automatically selected if others are missing. The option to use Source media type is available under  Use Source  >  Select Media  > select source file.     The option  to use Package media type is available under  Use Package  >  Select Media  >  select package file.       Update Monitoring     Update Monitoring tab allows to add prerequisites as applications from  Update Monitoring  delivered packages.     The option to Select application from Update Monitoring is available under  Select applications:  field >  Select Version for application .       Catalogue     Catalogue  tab allows to add prerequisites as applications from  Catalogue  delivered packages.     The option to select applications from the  Catalogue  is available under  Selec applications:  field >  Select Version for application .       The option to Save Changes is available under  Save  button.     Apptimized shows the following notifications when successful:     The option to  Edit prerequisites  becomes available after the prerequisites were added. RDP This setting enables a user to work on the VM directly via RDP rather than a browser window. The option to download a file is available under the Download RDP file. The RDP file is available in the Downloads folder in user’s PC. When the remote connection is set, copy the RDP password paste to the modal window. The remote desktop connection window appears when successful: VM Snapshots The setting enables to create a snapshot of the VM to save its current state or to revert to a state saved earlier. This is applicable when the application has prerequisites that need to be present before a certain action (i.e., Discovery, Packaging, or Testing) can be started. The snapshot option is available under the VM snapshot button > Snapshot name field > Take button. Clipboard This setting enables a user to put text from the user’s system to the VM clipboard. Transferring clipboard content between the host machine and the VM is performed via "Cut & Paste" in most user scenarios. If the user experiences any issues with "Cut & Paste", the Clipboard button can be used to put the text to the VM's clipboard. Fullscreen This setting enables to put a browser in a full-screen mode. Restart This setting enables a user to redo the testing session on a restarted VM. The following restart options available: OS (Operating system restart. Equal to Power > Restart); VM (Equal to the Reset button on the real PC); Session (Restart current session. All unsaved progress will be lost). When the restart option is chosen, the confirmation model window appears. Finish This setting finishes the VM when the testing session is completed. Apptimized MSIX PSF Tool  General overview   Package Support Frameworks is an open - source kit  that helps apply fixes to  the  existing desktop application without access to the source code. It can run in an MSIX container.   Apptimized  MSIX PSF  Tool   allows  applying  fixups semi-automatically to  a  Win32 application in existing MSIX files.   The tool is available in t h e Workspace Launcher (see the  Workspace Launcher )   The option to install the application is available under the  Install  button (see the  Application installation )   Run Apptimized MSIX PSF Tool   A user can apply the fixes in existing MSIX files. The option is available under  Run Apptimized MSIX PSF tool  button.   Apptimized shows the following screen when successful:    Select MSIX package   A user can select the existing MSIX package by clicking the  Folder  icon.   A user  can  select an MSIX file  to   automatically check  for  error s  and all the appropriate fixes for them  and click the  Open  button to start the checking process.   Apptimized shows the following screen when successful:   The opening process may take  a  few moments.  Cancel –  stop s  the package opening.   Apptimized shows the following screen after successful ly  opening:   Fixup suggestions are automatically provided after  the  package  open s . They can be manually added, by clicking the Apply suggestions button. To create default fixups based on package content, click  Create .  Cancel –  rever t s to general  Apptimized MSI X PSF Tool  section.   Apptimized shows the following screen when successful:   Apply fixups   Fixup suggestions will be provided in the  general   Apply fixups  section.   Apply  f ixups  allow  setting DLL and file system redirection rules or  setting   command - line arguments   t o  the  MSIX package.   The fixups data is performed in 2 blocks:   Information block – this block contains detailed information about fixups.   Action block – this block provides options to configure the fixups.   Fixup's  data is grouped into the following categories:   Type   Path   Scope   Details   Column name   Details   Type   This field indicates the type of    provided fixup   Path   This field   provide s  the f i le system path to  the  place  fixup   e ffects   Scope   This field indicates the target application (file.exe or  regular expression  pattern)   Details   This field shows the  redirect options (files pattern,  dll  name, etc.)   patterns  of the fixup   Fixup’s actions are grouped into the following categories:   Edit  fixup   Delete  fixup   Make  copy   To apply fixups provided by the  Apptimized MSIX PSF Tool , click  the  Save  button.   Apptimized provides the following screen:   A user can save an MSIX file with all the provided fixes by clicking the  Save  button to start the saving process.   Apptimized provides the following screen when successful:   To cancel implementing the fixups, click  the  Cancel  button.   Apptimized provides the following modal window when successful:   Click  OK  to continue canceling process.  Cancel –  refers to  Apply fixups  section.   Apptimized provides the following screen when successful:   Edit fixup   To edit fixup, click     button in the  Action  tab  or double click the  Fixup row .   Apptimized shows the following screen when successful:   Edit  section is divided into 2 blocks:   Target – indicates the  applications as  a  target for  fixups;   Config  –   allows to change the path and add patterns for fixups.   T arget  section  provides three options to change:   All applications  –   fixup affects all application s  inside of the MSIX package. This option is selected by  default;   Selected applications – allows to choose the optional application for fixup to be  provided;   Process matching the pattern  –   allows to  set up fixup pattern as a  regular expression   target ;   Config  section is divided into  two fields:   Path field – allows to change the path of the  fixup ;   Patterns – allows to set up patter n s for the  fixup;   Delete fixup   To delete fixup, click button in the Action tab.   Apptimized provides the following modal window:   To confirm removing fixup, click  Ok .  Cancel  – refers to  the  general  Apptimized MSIX PSF Tool   menu.   Make a copy To make a copy of a fixup, click  button in the Action tab.   Apptimized shows the following screen when successful:   Sign package To  sign  a  package  with a PFX certificate ,  check the box next to the option name. Apptimized shows the following screen when successful:   Sign package section contains the following fields:   PFX certificate – allows to set up the path of a PFX certificate to be  provided;   Password – allows to set up  the password for a PFX  certificate;   Timestamp server – allows to set up  a timestamp server for a PFX certificate .   Packaging – Factory Service Packaging – Factory Service characteristics: Apptimized packages an application for a user; Apptimized customizes the MSI or App-V output to meet user’s requirements; Apptimized contacts a user if any details are needed while packaging an application; Apptimized notifies a user when the application is ready for testing. The Packaging - Factory Service option is available under the Packaging - Factory Service module in the Transition screen . To proceed packaging the application a user needs to create (see Discovery manual) or upload the discovery document. If before the Packaging step of the workflow, the Delivery step has been completed, Apptimized shows the following screen: If before the Packaging step of the workflow, the Delivery step has not been completed, but a user has a discovery document the option to download, the discovery document is available. The option to download the discovery document is available under the Discovery document field (Click the field > Select the discovery file > Finish upload and continue work button). The option to revert to the transition screen is available under the Go back button. The option to finalize the Discovery document upload is available under the Finish upload and continue work button. Apptimized shows the following interface when successful: All required fields are marked with an asterisk *. The option to provide comments is available under the Reference field. The option to identify packaging technology is available under the Packaging technology field. Table 10. Packaging technologies Packaging technology Details Apptimized Best Practice The MSI of Legacy package will be created by the decision of Apptimized team. MSI The source will be repackaged and the batch file will be used for installation and uninstallation of the package (if another was not agreed with the delivery manager) MSIX MSIX package will be created App-V (latest version) The latest App-V sequencer will be used for creating App-V package App-V 4.6 The 4.6 version of App-V sequencer will be used for creating App-V package App-V 5.0 The 5.0 version of App-V sequencer will be used for creating App-V package App-V 5.1 The 5.1 version of App-V sequencer will be used for creating App-V package The option to choose the discovery platform is available under the Packaging platform field. A user can select several packaging platforms simultaneously. The option to choose the Wrapper format is available under  Wrapper format  field. Table 11. Wrapper formats Wrapper format Details Install.cmd This files are used for transferring application parameters. Apptimized PowerShell Wrapper (based on PSADT) Depending on the customer's requirement and the vendor's logic the package can be repackaged or silent installation can be used. The package will be wrapped in the PowerShell Application Deploy Toolkit. This wrapper will be used for configuration, installation, and uninstallation if the package Intunewin Intunewin package will be provided to the package. Two priority options are available: Normal and Urgent . The default value is Normal . The option to submit the packaging request is available under the Finish button. Apptimized shows the following modal window: The option to change the Normal priority to Urgent before approving the request is available under the Make urgent button. After the request is created, the current priority is displayed on the Factory Service page. Clicking the Priority field opens a modal window allowing the priority to be increased to Urgent . The option to create the request is available under the OK button. Note. If  Apptimize d  Portal can’t connect to SDC, the following error notification appears:   Apptimized shows the following screen when successful: This is an initial screen, and all blocks except the Status block are empty. Note. If  Apptimize d  Portal can’t connect to SDC, the following error notification appears:   This screen provides information on the Apptimized Packaging – Factory Service request (i.e., request progress and status). Additional information that might be needed during the packaging process will be exchanged here. Next, each Packaging – Factory Service block is shown in more detail. Status block The Status block shows packaging progress. The following request statuses appear depending on the Packaging – Factory Service progress: Table 11. Discovery request statuses Request status Description Incoming check The request has not been processed by the Apptimized team yet. The request is in the queue. In progress The request was processed by the Apptimized team. The request is in progress. Factory QA Deliverables are testing by the Apptimized team. Action required The Apptimized team asked the user a question. The user answer is needed. Delivered Packaging results are available to the user. Packaging results are as a package (i.e. MSI ). The package extension depends on packaging technology. Error analysis The user rejected the Packaging results. Apptimized team fixes bugs in the package. Approved The user has confirmed the Packaging results. Canceled The user canceled the Packaging request at the processing stage. Note . When public holidays are approaching that affect the factory packaging performance, Apptimized Portal shows the following notification above the Status block: The option to cancel the request is available under the Cancel Request button. Apptimized shows the following modal window to confirm the request cancellation: Apptimized shows the following modal window when successful: A user can cancel the packaging request until the Delivered status is achieved, and the discovery deliverables are available. If a user is  not  un satisfied with the packaging results, they can be rejected in the   Factory request   section under the  Factory activity  block.   When a user is satisfied with the packaging results, they must be approved in the Status block. The option to approve the request is available under the Approve Request button. The Approve Request button becomes active when the Delivered status is achieved, and the packaging deliverables are available. Apptimized shows the following modal window to confirm the request approval: Apptimized shows the following screen when successful: Note. When a user approves the request, the option can`t be canceled. Deliverables block This block provides the packaging results to a user. Discovery results are provided as a package. The package extension depends on the selected packaging technology. The option to download the testing results is available under the Download button. If a user is not satisfied with the testing results, they can be rejected to further processing by the Apptimized team. The option to reject the testing results is available  in the  Factory request   section under the  Factory activity block . (see Factory activity block)   Factory activity block The option to contact the specialist from  the  team is available under the  Factory activity block > Factory request   >  Write a message...   field .   The option to add supplementary attachments (i.e., screenshots, additional file) is available under the Select file button (Choose a file > Open button > Add button). The file can be a maximum of 10 MB. The option to send  a  message is available under the  Add   button. Apptimized shows the message history interface when successful: The option to provide additional comments or attachments to the Apptimized team is available under the  Factory activity block  after the Factory request was solved.   The option to  ask additional questions to the  Apptimized t eam is available under the  Report a problem   button. Apptimized provides the following modal window when successful: The option to write a text message is available under  the  Write your problem   field   Note. This field is mandatory. The option to attach  a  file is available under the  Select file   field. The option to change the attached file is available under the  Change   button.   The option to remove the attached file is available under the  Remove   button.   The option to send  a  message is available under  Send   field.  Cancel –  reverts to  general Factory process   workflow .   Apptimized shows the  message history interface  when successful:   Note. The attached files appear above the message history interface. If Apptimized needs some additional information, a user will receive notification s   and  a warning icon in the dashboard: If there is   feedback from the user   regardi ng   the Factory Request, the following  notification and status in the dashboard appear: Apptimized   provides  the following  notification and statuses   in  the  workflow and dashboard  after the request  is   re solved:   Finish Packaging - Factory Service The Finish button becomes active when a request is approved by a user. The option to create a new request is available under the Create new request button. Apptimized shows the following modal window to confirm the request approval: Apptimized shows the following screen when successful: The option to finish Packaging - Factory Service process is available under the Finish button. Apptimized shows the following screen when successful: MSIX packaging MSIX is a Windows app package format that provides a modern packaging experience to all Windows apps. The MSIX package format preserves the functionality of existing app packages and/or install files in addition to enabling new, modern packaging and deployment features to Win32, WPF, and Windows Forms apps.  Apptimized Portal allows a user to create MSIX packages with the help of Apptimized Packaging Engine , bulk convert packages to MSIX packaging format within the MSIX bulk conversion , and automatically convert the existing MSIX packages to Virtual Hard Disk files based on MSIX App Attach technology within the MSIX App Attach Converter . Apptimized Packaging Engine The Apptimized Packaging Engine (APE) launches when double-clicking the  Apptimized Packaging Engine  icon.   The process may take few moments.   Apptimized shows the Apptimized Packaging Engine (APE) main screen when successful:   Table 1. Apptimized Packaging Engine options   Option   Details   Repackage to MSI, App-V, MSIX, IntuneWin or VSL   This option is snapshot-based and enables to create a completely new installer.   This option is applicable when a user has a non-MSI vendor installer. A user converts it to MSI or App-V or virtualizes MSI installer into App-V.   Transform and edit vendor MSI   This option enables the transformation or customizing the existing Windows Installer.   This option is applicable when a user has an MSI-based vendor installer and needs to produce an MST for it containing changes made during the installation process and/or configuration post-installation settings.   Review and edit result   This option enables to review the packages.   The option becomes available only after a user completed the repackaging or transformation procedure.   Save locally   This option enables saving the output locally to verify before uploading back to Apptimized.   Upload result to Apptimized   This option enables uploading verified output back to Apptimized.   A user can upload the output generated by Apptimized or select an archive with modified files to be used as an output.   Repackage to MSI, App-V, MSIX, or VSL When clicking the  Repackage to MSI, App-V, MSIX, or VSL  option, the APE will redirect a user to a Wizard. A user needs to provide input at each step.   Capturing installation and configuration APE will capture all changes made to the system by scanning a file and registry changes, after that converting it to a machine-readable form. Those changes will typically include the installation of the application and the features selection, as well as customization of the application's settings to reflect the desired result as documented during the Discovery step.   VM preparation and prerequisites installation must proceed before packaging. The prerequisites are considered as applications that need to be present for a user’s software or its installer to function, but a user does not want those software products to be included into the package (e.g., because a prerequisite is already installed on the user’s machines or is managed as a separate dependency package).   The option to start a recording session is available under the  Start recording  button.   Note.  Any VM activity or inactivity can leave traces in the captured result (including those not relevant to the package or application results). A user needs to confine to the activities needed for packaging and finish the process as quickly as possible).   APE shows the following notification when successful:   The option to suspend capturing changes made to the filesystem and registry is available under the  Pause  button. The option to resume the recording is available under the  Pause  button (click the  Pause  button again).   Once the recording has started a user enables a user to browse the path of the installation file ( Browse  button).   The option to provide the additional parameters (i.e., to specify additional launch arguments) is available under the  Parameters (optional)  field.   Once the file has been selected, the  Run  button becomes active.   When the synchronization process is finished, APE shows the following screen: When the installation and configuration activities are completed, the record must be finished. The option to stop the record is available under the  Stop recording  button.   This will terminate the recording process and prepare the captured system changes for producing an MSI, MSIX, App-V, or VSL. The terminating process may take few moments (additional post-processing and  cleanup  will be applied to the output).   Note . Apptimized applies advanced logic and filters to keep the snapshot result clean from unneeded or dangerous files and registry keys. However, typically captured results require manual review and adjustments to achieve the desired result or to apply further cleanup from the captured system or user activity.  The processing file system changes may take few moments:   When successful APE shows the screen:   Editing Application Metadata A user can review and adjust the application metadata if required.   The default values generate from the portfolio metadata provided during the file import process and do not need to be changed in most of the cases.   If the installation session consisted of more than one installer, select the primary installer to extract the metadata.   Review captured content   The option to the recorded content for the files, registry entries, services, and other system items that were modified or created during the installation is available under the  Review recorded content  button.   APE shows the snapshot editor screen when successful: A user can navigate across different tabs based on the captured content nature:   Filesystem;   Registry;   Shortcuts; Drivers; Services;   Certificates;   Environment;   Registry ACL;   Filesystem ACL;   Firewall Rules.   Filesystem  and  Registry  tabs are presented in a tree structure view.   Shortcuts ,  Environment ,  ACL ,  Services , and other tabs are presented in a table-based view.   The  Filesystem  tab shows captured changes to the filesystem (file & folders).   The  Registry  tab shows captured changes to the Windows registry.   The  Shortcuts  tab shows captured shortcuts. The  Drivers  tab shows captured drivers. The  Services  tab shows all services which were created during source installation.   The  Certificates  tab shows all changes which were added to the Certificate Stores.   The  Environment  tab shows captured environment variables created during the source installation.   The  Registry ACL  tab shows captured permission changes in the Windows registry.   The  Filesystem ACL  tab shows captured changes to filesystem ACLs. An Access Control List (ACL) is a list of Access Control Entries (ACE). Each ACE in an ACL identifies a trustee and specifies the access rights allowed, denied, or audited for that trustee.   The  Firewall Rules  tab shows firewall rules created during the source installation.   Due to the nature of the recording process, unwanted resources, also known as system activity or noise, might be captured into the recording result. These happen because the system is altered by the installation (or by the application, by the user, by the other applications, and by the operating system itself) during packaging in areas that are unrelated to the application and are not needed in the package. Those unwanted resources might negatively influence the installation or uninstallation of the package, or other applications and the operating system's stability, or, at least, create unneeded bloat. System activity traces and noise cleaning is required to receive good-quality packages.   When recording completed, APE applies a default exclusion list, which filters most of the unwanted system changes from the package (which need to be removed from the package).   A user can additionally exclude unwanted resources or re-include resources that were automatically excluded from the list. Such actions should only cover specific scenarios involving changes to the operating system.   The option to exclude the files from the package is available under the  context menu  or using the keyboard shortcuts  Ctrl+E  or  Del .   The option to include the files to the package is available under the  context menu  or using the keyboard shortcut  Ctrl+I .   Captured resources that are intended to exclude from the package are shown with a red overlay.   Captured resources that are intended to include the package are shown with no overlay.   The  status bar  with the total number of files and the number of included files is available in the footer of the  Review recorded content  window.   The option to search files or folders by name is available under the  Search in files  field available in the footer of the  Review recorded content  window.   The screenshot below shows the tab interface with table-based view (i.e.,  Shortcuts  tab):   To exclude the item, tick the checkbox in front of its name.   Table 2. Shortcuts tab structure   Column name   Details   Exclude   This column provides the option to include or exclude entities.   Icon   This column provides the shortcut icon.   Location   This column provides details on the shortcut location (i.e., a physical location of the shortcut file).   Destination   This column provides details on the shortcut’s target (usually target is an executable file).   To exclude the item, tick the checkbox in front of its name.   Table 3. Filesystem ACL tab structure   Column name   Details   Exclude   This column provides the option to include or exclude entities (i.e., detected file or folder ACL).   Review   This column provides the option to open the  Permission properties  for the selected file or folder.   This dialogue window enables a user to Set, View, Change, or Remove permissions for the current item. Permissions are set recursively, so to set permissions onto a folder, its subfolders and files only configure permission changes on the parent folder level.   The option to set permissions for a group or user that does not appear in the  Group or user names  box is available under the  Add  button (Type the name of the group or user >  OK  button).   The option to remove permissions for a group or user that appears in the  Group or user names  box is available under the  Remove  button (Type the name of the group or user >  OK  button).   The options to allow or deny permission are available under  the Permissions for  box (Select the  Allow  or  Deny  column  > Check / Uncheck the box).   The option to set the special permissions or advanced settings is available under the  Advanced  button.   Path   This column provides details on file or folder with detected, modified or created permissions.   Table 4. Drivers tab structure Column name Details Exclude This column provides the option to include or exclude entities (i.e., detected driver file). Name This column indicates the name of the driver file name. Location This column provides details on the driver location (i.e., a physical location of the driver file). Add ARP entry This column provides an option to add ARP (Add-Remove Program) entry which is based on ARPSYSTEMCOMPONENT property value. Remove on uninstall This column provides an option to automatically delete the driver during the uninstallation process. The option to apply the changes to the recording result is available under the  Save  button.   Analyze for common issues The option to review the most common issues which might lead to a non-working or incomplete installation is available on metadata reviewing screen under the  Analyze  for common issues  button.   APE shows a screen when successful:   This will show the severity of problems, problem codes, and issue description, both with the recommendations on how to reduce the risk.   Table 5. Possible values of the analyzer   Severity   Problem code   Description   High   DriversInSnapshot   The installation driver is not supported in repackaging mode. It won't be included in the final package.   Medium   ServicesInSnapshot   Installation services are detected. This can lead to problems with App-V or AppX packaging formats.   EnvironmentalVariablesChanged   The environmental variables change is detected. A user must sure this won't overwrite existing entries during installation.   Low   MSIExecLaunched   MSI installation is detected. It's recommended to use transformation instead of repackaging until a user converts the installer to the not MSI format.   AutoStartDetected   Auto-start modification is detected during the installation.   DllHostDetected   COM registration is detected. An application may not work when packaged in App-V or AppX formats.   SystemFilesIncluded   System files were modified during the installation. A user must review captured content and exclude unneeded entries.   When the review of the common issues is finished, click the  Close  button.   Save project   The option to save settings and apply them in the future is available under the  Save project  button.   APE shows the following window (Choose the root to save project >  Save  button):   When the metadata review completed, the option to proceed to the next step is available under the  Next >  button.   Adjust Format Details   The following screen shows the default values for package formats:   The adjustment of the format-specific settings is available. These settings are typically pre-defined by Apptimized project administrator in the project settings in accordance with the appropriate  Packaging Standards .   Before overriding any of pre-defined settings, a user must ensure the feasibility and correctness of provided changes.   The option to exclude or to include the package formats is available under the switch in front of their names.   When the package format review is completed, the option to proceed to the next step is available under the  Next >  button.   When the packages build, the log information is written to the console. In case of a failure this log may be requested by Apptimized support:   The blue background indicates that the build process is still in progress. When it turns to a green background the package type/format has been successfully built.   The build time will depend on the number and size of the captured files and may take few minutes.   The APE finalizes when clicking the  Finish  button.   MSIX bulk conversion MSIX bulk conversion   is one  of the Apptimized products that provides  a flexible and automated application packaging conversion system.   Bulk c onvert MSI and EXE to MSIX Apptimized Platform  provides   silent  conver sion   of the existing  MSI   packages  and EXE files  to MSIX  within the  MSIX bulk conversion .   The  MSIX bulk conversion  is available under the  Project  menu >  MSIX bulk conversion : The option is disabled by default.   Enable MSIX bulk conversion  T he   MSIX bulk conversion   is available under the   P roject   menu >  Administration  >   Settings :   Apptimized provides the following screen when successful:   To continue enabling  MSIX bulk conversion ,  c lick :   Workflow  >   Packaging – Self Service . General   >  MSIX  button .     The option to enable MSIX bulk conversion is available  under the   MSIX bulk conversion   button . Ye s  and  No  options are available. The default value is  No .   The   MSIX bulk conversion  option becomes active when switched on and once the required settings are completed.   T o apply the settings, click the Save button. Apptimized provides the following notification when successful:   MSIX bulk conversion interface  The option t o start  conversion  process  Projects  >  MSIX bulk conversion : Apptimized provides the following screen:   The screen above shows the default MSIX bulk conversion interface when no applications  are  added .   The packaging data is performed in 2 blocks:   Information block – this block contains detailed information about packages.   Action block – this block provides options to configure  the  package  conversion  process (see the  Package  conversion ) Manage applications in MSIX bulk conversion Add application  The option to add  the  package to the  conversion list  is avai l able under the  Select from portfolio  button :   Apptimized shows the modal window when successful:   Note . If the  application  is not  pack aged , there will be no option s available .   Field   Details   S earch   The  S earch  field allows  find ing the  application  from  the  portfolio .   There is no default value for this field.   Select   The  Select  field allows selecting the application  from  the  portfolio .      There is no default value for this field.   There is an option to select all application s .   To apply the settings, click the Save  button.  Cancel –  revers to the general  Silent c onversion  section.   Apptimized shows the following  notification  when   successful:   When a user adds the application to the MSIX bulk conversion list, Apptimized shows the following screen: Silent conversion data is grouped into the following categories:   App   I D   Vendor   Software   Version   Conversion Status   Testing Status   Column name   Details   App  ID   This component indicates an  I D  of the application  that will be available to a user  for  th e   conversion .   Vendor   The component provides a user with   information about the  v endor of the application .    Software     This component indicates the  name of the application .   Version   This component provides  a user with information about the version of the application.   Conversion Status   This component indicates the state  of conve rsion   of the ap plicatio n .  The following statuses are  provided :   Required preparation – indicates ,  that a file with installation script must be provided .   Ready to start – indicates ,  that a package is ready to be converted .   Processing – indicates ,  that the package is being converted at the time .   Success – indicates the successful result of converting .   Failed  – indicates the unsuccessful result of converting.   Testing Status   This component provides  the state of testing of the application.   The following statuses are provided:   Wait for conversion – indicates that  the  package is ready to be converted.   Ready to start – indicates that  the  testing process is ready to be  started .   Testing – indicates that the package is being tested at the time.   Success – indicates the successful result of testing   Failed – indicates the unsuccessful result of testing.   Package conversion  The option to  convert  a package into the  MSIX  format is available by clicking   Prepare  button.   Apptimized shows the following modal window ,  by clicking  Prepare   button :   Field   Details     Package  conversion  options   The field allows  selecting  a n installation file of the application  to conver t  it .   For every application to convert, the installation file must be selected.    The installation file can be in MSI, EXE ,  or BAT formats.     Certificate publisher   The  field  allows   setting  a publisher  for  the  future package .       The information is automatically filled in  with  the information of the publisher of the package.     There is no default value for this field.     Installation script file   The  Installation script file  field allows  setting   the  installation file of the application to  convert . It is set after selecting  the file in  the  Package convert options   field.     The installation file can be in MSI, EXE ,  or BAT formats.   There is no default value for this field.     To apply the settings, click the  Save  button.  Cancel –  re f ers to the general  Silent conversion  section.   To continue  Package conversion  configuring, select the installation file of the application to  convert .   To apply the settings, click the  Save  button.  Cancel –  re f ers to the general  Silent conversion  section.   Apptimized shows the following notification when successful:   To start  the conver s ion  process, click  Convert .   Apptimized provides the following notification when successful:   Note . The conversion won’t be done  immediately . The process ing  time depends on  the size of the package.   To stop  the  conversi o n process, click  the  Stop   button .   Apptimized provides the following modal window: To stop conversion, click  Confirm .  Cancel –  re f ers to the general  Silent conversion  section.   Apptimized shows the following screen when the  conversion  process  finishes : Test package To test the package, click  the  Test   button  in the  Actions  tab :   Apptimized provides the following screen: Apptimized provides the VM to test the package. After testing, click  the  Terminate   button   to get  the  results of testing :   Apptimized provides the following screen when successful:   To continue ,   click  the  Result   button . Restart   option allows to restart VM and return to testing.   Apptimized provides the following modal window when successful:   To enter the  Testing result  section, click  Result. Cancel – re f ers to the VM testing section.   Apptimized provides the following screen when successful:   The  Result  field indicates the state of testing. There are 2 options available:   Success – indicates ,  that testing was successful.   Failed – indicates ,  that testing was unsuccessful.   To apply the settings, click the  Save  button.  Retest   – refers  to the  VM testing  section.   Apptimized provides the following screen when successful:   Delete application The option to delete the application from the  Silent conversion  tab   is available  in the  Actions  tab  by clicking  button >  Delete .   Apptimized shows the following  modal window  when successful:   To delete the application from  the  conversion tab, click  Delete .  Cancel  - re f ers to the general  Silent conversion  tab.   Apptimized shows the following notification when successful:   Download the application To download the converted package, click  button >  Download. The download process will start immediately. Apptimized MSIX AppAttach Converter General Overview MSIX  A pp  A ttach is a way to deliver MSIX applications to both physical and virtual machines.   A   Microsoft technology  allowing  to make MSIX packages compliant for virtualized desktop environments such as Windows Virtual Desktop.    The  Apptimized  MSIX AppAttach Converter  is a tool that allows to automatically convert the existing MSIX packages to VHD (Virtual Hard Disk) files based on MSIX App Attach technology.    The tool is available  i n  the  Workspace Launcher (see the  Workspace Launcher ).   The option to install the application is available under the  Install  button (see the  Application installation ). Convert existing MSIX package A user can convert the existing MSIX package into MSIX app attach package. This option is available under  C onvert the existing MSIX package  button. Apptimized shows the following screen when successful: A user can select the existing MSIX package by clicking the  Folder  icon. A user can select an MSIX file that will be automatically converted to the app-attach package and click the  Open  button to start the converting process. Apptimized shows the following screen when successful: The creation process may take few moments.  Cancel  - stop the VHD file creation. After completing the creation a user can save the app-attach package (VHD file by clicking the  Save  button. The process may take few moments. Apptimized shows the following screen when successful:   Apptimized MSIX PSF Tool  General overview   Package Support Frameworks is an open - source kit  that helps apply fixes to  the  existing desktop application without access to the source code. It can run in an MSIX container.   Apptimized  MSIX PSF  Tool   allows  applying  fixups semi-automatically to  a  Win32 application in existing MSIX files.   The tool is available in t h e Workspace Launcher (see the  Workspace Launcher )   The option to install the application is available under the  Install  button (see the  Application installation )   Run Apptimized MSIX PSF Tool   A user can apply the fixes in existing MSIX files. The option is available under  Run Apptimized MSIX PSF tool  button.   Apptimized shows the following screen when successful:    Select MSIX package   A user can select the existing MSIX package by clicking the  Folder  icon.   A user  can  select an MSIX file  to   automatically check  for  error s  and all the appropriate fixes for them  and click the  Open  button to start the checking process.   Apptimized shows the following screen when successful:   The opening process may take  a  few moments.  Cancel –  stop s  the package opening.   Apptimized shows the following screen after successful ly  opening:   Fixup suggestions are automatically provided after  the  package  open s . They can be manually added, by clicking the Apply suggestions button. To create default fixups based on package content, click  Create .  Cancel –  rever t s to general  Apptimized MSI X PSF Tool  section.   Apptimized shows the following screen when successful:   Apply fixups   Fixup suggestions will be provided in the  general   Apply fixups  section.   Apply  f ixups  allow  setting DLL and file system redirection rules or  setting   command - line arguments   t o  the  MSIX package.   The fixups data is performed in 2 blocks:   Information block – this block contains detailed information about fixups.   Action block – this block provides options to configure the fixups.   Fixup's  data is grouped into the following categories:   Type   Path   Scope   Details   Column name   Details   Type   This field indicates the type of    provided fixup   Path   This field   provide s  the f i le system path to  the  place  fixup   e ffects   Scope   This field indicates the target application (file.exe or  regular expression  pattern)   Details   This field shows the  redirect options (files pattern,  dll  name, etc.)   patterns  of the fixup   Fixup’s actions are grouped into the following categories:   Edit  fixup   Delete  fixup   Make  copy   To apply fixups provided by the  Apptimized MSIX PSF Tool , click  the  Save  button.   Apptimized provides the following screen:   A user can save an MSIX file with all the provided fixes by clicking the  Save  button to start the saving process.   Apptimized provides the following screen when successful:   To cancel implementing the fixups, click  the  Cancel  button.   Apptimized provides the following modal window when successful:   Click  OK to continue cancelling process.  Cancel –  refers to  Apply fixups  section.   Apptimized provides the following screen when successful:   Edit fixup   To edit fixup, click     button in the  Action  tab  or double click the  Fixup row .   Apptimized shows the following screen when successful:   Edit  section is divided into 2 blocks:   Target – indicates the  applications as  a  target for  fixups;   Config  –   allows to change the path and add patterns for fixups.   T arget  section  provides three options to change:   All applications  –   fixup affects all application s  inside of the MSIX package. This option is selected by  default;   Selected applications – allows to choose the optional application for fixup to be  provided;   Process matching the pattern  –   allows to  set up fixup pattern as a  regular expression   target ;   Config  section is divided into  two fields:   Path field – allows to change the path of the  fixup ;   Patterns – allows to set up patter n s for the  fixup;   Delete fixup   To delete fixup, click button in the Action tab.   Apptimized provides the following modal window:   To confirm removing fixup, click  Ok .  Cancel  – refers to  the  general  Apptimized MSIX PSF Tool   menu.   Make a copy To make a copy of a fixup, click  button in the Action tab.   Apptimized shows the following screen when successful:   Sign package To  sign  a  package  with a PFX certificate ,  check the box next to the option name. Apptimized shows the following screen when successful:   Sign package section contains the following fields:   PFX certificate – allows to set up the path of a PFX certificate to be  provided;   Password – allows to set up  the password for a PFX  certificate;   Timestamp server – allows to set up  a timestamp server for a PFX certificate .       Testing The following scenarios to open the transition screen available: My Dashboard  >  My Applications  > Choose the project > Actions column >  Process  option; Project menu  >  Dashboards  >  Overview  >  Your assignments  module > Choose the application > Actions column >  Process  option; Project menu  >  Dashboards  >  Portfolio  > Actions column >  Process  option; Project menu  >  Import  >  Start import  >  Classic import / Import from CSV file / SCCM Import /Catalogue & UM Import  > Application upload session >  Finish Apptimized shows the following screen when successful: The testing process starts by clicking on the Skip to [Step name] button (before or after discovery step) and clicking in the Testing module on the Transition screen. An imported application into a project is a prerequisite.  Two testing scenarios available in Apptimized portal: Testing – Self Service; Testing – Factory Service. Note. A source for Testing step downloads at the Import step (see Classic impor t, CSV import , SCCM import , Catalogue & UM Import ). Depending on the project workflow structure, a source can be an EXE file, a package). Next, the most common cases with the Testing are provided: 1. The project workflow consists of 3 steps (Discovery - Self Service, Packaging - Factory Service, Testing - Self Service). A user uses a Classic import option to import the source ( EXE file). The user goes through the steps sequentially. When the package is ready the user starts the Testing step with the package (i.e., Selects the testing platform > Starts VM > Opens Packages folder >Launches install.cmd file > Performs the testing actions > Finish VM > Reviews the testing results). 2. The project workflow consists of 3 steps (Discovery - Self Service, Packaging - Factory Service, Testing - Self Service). A user uses a Classic import option to import the source ( EXE file). The user skips the Discovery - Self Service and Packaging - Factory Service steps. The user starts the Testing step with the existing source (i.e., Selects the testing platform > Starts VM > Opens Source folder >Launches EXE file > Performs the testing actions > Finish VM > Reviews the testing results). 3. The project workflow consists of 1 step (Testing - Self Service). A user uses a Classic import option to import the source ( MSI file). The user starts the Testing step with the existing source (i.e., Selects the testing platform > Starts VM > Opens Source folder >Launches package file > Performs the testing actions > Finish VM > Reviews the testing results). Testing – Self Service A user can record a guide to install and configure the application on Apptimized VMs. Also, a customer can enable a testing option and set the status of testing. Testing - Self Service characteristics: A user tests created packages on his own. A user runs and documents test cases. A user logs installation or functional errors. A user provides debugging guidance. The Testing - Self Service option is available under the Testing - Self Service module in the Transition screen. Apptimized shows the following screen when successful: A field " Select testing – self service platform " is filled automatically and can be changed if needed. To change the testing – self service platform, click the drop-down menu as it is shown in the screenshot below: The option to revert to the transition screen is available under the Go to Transition screen button. Testing – Self Service process The option to start the testing – self service process is available under the Start VM button. Apptimized shows the following screen when successful: The file synchronization process may take few moments. Apptimized shows the following notification: Note. There is often a situation when a user has already run 2 VMs in parallel. To continue planned activities within the current workflow step, a user must terminate an irrelevant VM. In this case, Apptimized shows the warning box with a list of VMs which are currently running by the user: The information is grouped into the following categories in the modal window:  1. Application 2. VM started time 3. Workflow progress 4. Link The option to select a VM for termination is available under the Go to VM link. A new tab opens when successful: When a VM is terminated, a user returns to the screen where he needs to restart a VM (previously a user started a VM but received a modal window with a list of running VMs). When the synchronization process is finished, Apptimized shows the following screen: Note. If the internal error while starting VM occurred, Apptimized shows the following screen: The following actions are recommended for consideration by a user: 1. Contact the Apptimized support 2. Go to image page button > Select discovery – self-service platform field > Start VM button The option to copy files to Temp storage  is available under  Explorer context menu  >  Copy To Temp : The uploaded files locate in the Apptimized files folder on the VM desktop. To start the installation process, a user opens the .EXE file located in the Source folder. Every action is captured as a screenshot which is shown in green boxes appearing on the right-hand side: When application installation is completed, a user can provide further configurations (only the Edit and Settings categories). The options to finish the VM session is available under the Finish button. The following interface will appear when recording session with Apptimized VM finishes: The option to restart the VM testing session is available under the Restart button. To confirm the restarting the VM Apptimized shows the following modal window: VM control menu The VM control menu panel is available in the upper right corner of the VM interface. Next, each settings category is shown in more detail. Table 1. VM control menu   Control menu category Details 1 Screenshots This setting indicates the screenshot mode. On and Off options available. The default value is On . 2 Add prerequisites This setting enables a user to add prerequisite applications. Portfolio  tab is available by default.  Update Monitoring  &  Catalogue  tabs become available if there are delivered packages on them. Portfolio  tab   The option to select application is available under  Select applications  field. The option to select media type for applications is available after the application was selected. The following media types available: Package Source Note . One media type is automatically selected if others are missing. The option to use Source media type is available under  Use Source  >  Select Media  > select source file.     The option  to use Package media type is available under  Use Package  >  Select Media  >  select package file.       Update Monitoring     Update Monitoring tab allows to add prerequisites as applications from  Update Monitoring  delivered packages.     The option to Select application from Update Monitoring is available under  Select applications:  field >  Select Version for application .       Catalogue     Catalogue  tab allows to add prerequisites as applications from  Catalogue  delivered packages.     The option to select applications from the  Catalogue  is available under  Selec applications:  field >  Select Version for application .       The option to Save Changes is available under  Save  button.     Apptimized shows the following notifications when successful:     The option to  Edit prerequisites  becomes available after the prerequisites were added. Note . Uploaded prerequisites are shown in the testing documentation under the Previous application section. 3 RDP This setting enables a user to work on the VM directly via RDP rather than a browser window. The option to download a file is available under the Download RDP file. The RDP file is available in the Downloads folder in user’s PC. When the remote connection is set, copy the RDP password paste to the modal window. The remote desktop connection window appears when successful: 4 VM Snapshots The setting enables to create a snapshot of the VM to save its current state or to revert to a state saved earlier. This is applicable when the application has prerequisites that need to be present before a certain action (i.e., Discovery, Packaging, or Testing) can be started. The snapshot option is available under the VM snapshot button > Snapshot name field > Take button. 5 Clipboard This setting enables a user to put text from the user’s system to the VM clipboard. Transferring clipboard content between the host machine and the VM is performed via "Cut & Paste" in most user scenarios. If the user experiences any issues with "Cut & Paste", the Clipboard button can be used to put the text to the VM's clipboard. 6 Ctrl+Alt+Del This setting enables to open security options menu at the VM. 7 Fullscreen This setting enables to put a browser in a full-screen mode. 8 Restart This setting enables a user to redo the testing session on a restarted VM. The following restart options available: OS (Operating system restart. Equal to Power > Restart); VM (Equal to the Reset button on the real PC); Session (Restart current session. All unsaved progress will be lost). When the restart option is chosen, the confirmation model window appears. 9 Finish This setting finishes the VM when the testing session is completed. Testing – Self Service screenshots The option to edit the screenshots is available under the Continue with Testing – Self Service screenshots button. Apptimized shows the following screen when successful: The following options to log test session results are available: Untested; Success; Failed. The default value is Untested . The field Optional comment can stay blank. Screenshots can be excluded from testing by clicking the Delete button. Screenshots can be excluded from testing in a multiple mode by unticking checkboxes in front of their ID and clicking the Delete selected screenshots button. Apptimized shows the following modal window: When clicking on the Confirm button, Apptimized shows the notification: Screenshots sequence can be changed in testing by clicking the Up or Down buttons. Comments to the screenshots can be edited by clicking on the comment cell. The Additional comment (Optional) field can stay blank. If any problems occur, the option to contact support is available under the Did you run into problems? button. Apptimized shows the following modal window: When the Contact support option is chosen, the live chat with the support team appears: When the Log problem option is chosen, the modal window appears: The problem category can be chosen by ticking checkboxes in front of their names. Screenshots editing mode finalizes when clicking the Save changes button. Apptimized shows the following interface when successful: The generated document is available in PDF and HTML formats. To download a document, click the Download generated HTML document or Download generated PDF document buttons. A generated HTML document first page sample is available: The option to edit a testing document is available under the Edit generated document button. The document editing finalizes by clicking the Save button. The option to return to the testing self-service screen mode is available under the Revert to Testing – Self Service Self Service button. The option to finish the testing process is available under the Finish button. Apptimized shows the following screen: Testing – Factory Service Testing – Factory Service characteristics: Apptimized tests created packages for a user. Apptimized runs and documents test cases based on user’s requirements. Apptimized logs installation or functional errors. Apptimized debugging guidance. The Testing - Factory Service option is available under the Testing - Factory Service module in the Transition screen . Apptimized shows the following screen when successful: All required fields are marked with an asterisk * . The option to provide a comment is available under the Reference field. The option to choose the discovery platform is available under the Testing platform field. Two priority options are available: Normal and Urgent . The default value is Normal . The option to submit the testing request is available the Submit request button. Apptimized shows the following modal window: The option to change the Normal priority to Urgent before approving the request is available under the Make Urgent button. After the request is created, the current priority is displayed on the Factory Service page. Clicking the Priority field opens a modal window allowing the priority to be increased to Urgent . The option to create the request is available under the OK button. Apptimized shows the following screen when successful: This is an initial screen, and all blocks except the Status block are empty. This screen provides information on the Apptimized Testing – Factory Service request (i.e., request progress and status). Additional information that might be needed during the testing process will be exchanged here. Next, each Testing – Factory Service block is shown in more detail. Status block The Status block shows testing progress. The following request statuses appear depending on the Testing – Factory Service progress: Table 2. Testing request statuses Request status Description Incoming check The request has not been processed by the Apptimized team yet. The request is in the queue. In progress The request was processed by the Apptimized team. The request is in progress. Action required The Apptimized team asked the user a question. The user answer is needed. Delivered Testing results are available to the user. Testing results can be provided in PDF and HTML formats. Error analysis The user rejected the Testing results. Apptimized team fixes bugs in the Testing document. Approved The user has confirmed the Testing results. Canceled The user canceled the Testing request at the processing stage. The option to cancel the request is available under the Cancel Request button. Apptimized shows the following modal window to confirm the request cancellation: Apptimized shows the following modal window when successful: A user can cancel the discovery request until the Delivered status is achieved, and the discovery deliverables are available. If a user is not satisfied with the testing results, they can  be  rejected in the  Factory request   section  under the  Factory activity   block. When a user is satisfied with the testing results, they must be approved in the Status block. The option to approve the request is available under the Approve Request button. The Approve Request button becomes active when the Delivered status is achieved, and the testing deliverables are available. Apptimized shows the following modal window to confirm the request approval: Apptimized shows the following screen window when successful: Note. When a user approves the request, the option can`t be canceled. Deliverables block This block provides the testing results to a user. Discovery results can be provided in PDF and HTML formats. The option to download the testing results is available under the Download button. If a user is not satisfied with the testing results, they can be rejected to further processing by the Apptimized team. The option to reject the testing results is available under the Factory request  section under the  Factory activity   block (see  Factory activity block ).   Factory activity block The option to contact specialists from the Apptimized team and provide comments or attachments is available under the  Factory activity  block. The option to write a message in the Factory request is available under the   Write a message ...  field .   The option to add optional attachments to the comment ,  such as screenshots or additional files (max 10 MB per file) ,  is available under the  Select  file . The option to send  a  message is available under the  Add   button. The option to provide additional comments or attachments to the Apptimized team is available under the  Factory activity block  after the Factory request was solved.   The option to ask additional questions to the Apptimized team is available under the  Report a problem   button. Apptimized provides the following modal window when successful:   The option to write a text message is available under the  Write your problem  field   Note! This field is mandatory. The option to attach a file is available under the  Select file  field   The option to change the attached file is available under the  Change  button.   The option to remove the attached file is available under the  Remove  button.   The option to send a message is available under  Send  field.  Cancel –  reverts to  general Factory process  workflow.   Apptimized shows the message history interface when successful: Note .   The a ttached  files appear above the message history interface.   If Apptimized needs some additional information, a user will receive notifications and a warning icon in the dashboard:   If there is  feedback from the user  regarding   the Factory Request, the following notification and status in the dashboard appear:   Apptimized provides the following  notification and statuses in workflow and dashboard  after the request was solved:   Finish Testing - Factory Service The Finish button becomes active when a request is approved by a user. The option to create a new request is available under the Create new request button. Apptimized shows the following modal window to confirm the request approval: Apptimized shows the following screen when successful: The option to finish Testing- Factory Service process is available under the Finish button. Apptimized shows the following screen when successful: Download The download process starts by clicking the Download module on the Transition screen : The set of documents to download depends on: the workflow structure (i.e., the number of steps, the set of module types) that was configured during project creation; the number of steps a user completed (a user can skip steps (for example, after importing the application user proceeds to the testing step). Thus, regardless of the workflow structure, the step may remain without results (generated documents), if the user skipped it. The screenshot below shows the examples of possible download page configurations: The option to download results is available under the Download installation source, or Download package, or Download generated [discovery/testing] HTML document, or Download generated [discovery/testing] PDF document buttons. Table 1. Possible download document options Step Type of a document Extensions Example Import Installation source Discovery document EXE HTML, PDF FileZilla_3.34.0_win64-setup_bundled.exe Discovery – Self Service Discovery document HTML, PDF   TimKosse_FileZilla_3.34.0.pdf TimKosse_FileZilla_3.34.0.html Discovery – Factory Service Packaging – Self Service Package   MSI, MSIX, App-V, VSL, ZIP FileZilla_3.34.0.msi   Packaging – Factory Service Testing – Self Service Testing document   HTML, PDF TimKosse_FileZilla_3.34.0.pdf TimKosse_FileZilla_3.34.0.html Testing – Factory Service In case of a wrapping functionality was used, a wrapped package becomes available at Packaging - Self Service step deliverables: The process reverts to the initial screen by clicking the Go to Transition screen button. The process finalizes by clicking on the Complete button. Note. Rating the Apptimized experience is optional. Apptimized shows the following notification when successful: Catalogue Apptimized Catalogue is one of the Apptimized features that provides access to a store, where a user can purchase the version of the application which is packaged according to a standard procedure and is ready for use. The latest application versions available for orders within 24 hours release of the update by the vendor, and ready for download within 48 hours after the request. Note. The "catalogue" option appears in the project menu after it is initiated in the project settings by the project administrator. The Catalogue is available under the Project menu > Catalogue : Apptimized shows the following screen when successful: Apptimized sends the follow-up email when the user has been accessed the Apptimized Catalogue:   New request New package request The option to make a request for a new package in the Apptimized Catalogue is available under the Request new Catalogue package block > Select the value from the drop-down list in the Application field > Select the value from the drop-down list in the Version field > Select the value from the drop-down list in the Platform field > Select the value from the drop-down list in the Format field > Request button. All required fields are marked with an asterisk * . Note. The multiple-choice option is available in the Platform and Format fields. For each selected item, a separate catalogue request will be created. Apptimized shows one of the following modal windows: a) the request doesn’t include a match to the previously made request; b) the request includes a match to the previously made request. Apptimized shows the following screen when successful: New package request from the Updates The option to import source file from the Updates interface is available under Actions > Process latest version > Select source file > Request catalogue package Apptimized shows the following screen when successful: New application request The option to create a request to add an application to the Catalogue list is available under the Request for add application link. The Apptimized Team will check the possibility to add the application to the Catalogue list. Apptimized shows the modal window when successful: Enter the value in the Vendor name field > Enter the value in the Software name field > Select the value from the drop-down list in the Platform field > Select the value from the drop-down list in the Package type field > Request button. All required fields are marked with an asterisk * . Note. The multiple-choice option is available in the Platform and Package type fields. For each selected item, a separate request will be created. Apptimized notifies the user when the request is submitted. The following screen provides an example of the notifications: Apptimized sends the following email when  the application  can  be added to  the  Catalogue list. Apptimized sends the following email when the application  can't   be added to  the Catalogue list.   Catalogue request monitoring New Catalogue requests appear in the Active requests tab of the Catalogue deliverables block. After the Apptimized processed the request and the package is available, the request appears in the Completed requests tab. Apptimized notifies the user when the requested package is ready. The following screen provides the example of the notification: Catalogue active request data is grouped into 7 categories: Application; Version; Platform; Format; Order date; Remained time; Status. The columns in the catalogue request table can be swapped and grouped in any order. A user can drag and drop a column header to a suitable place. To exclude columns in the catalogue request table, uncheck the box next to the column name not required in view. This option is available under Edit Column Settings > Columns . To sort data in columns select ascending or descending mode. This option is available under Edit Column Settings > Sort Ascending or Edit Column Settings > Sort Descending . To filter data in columns use Edit Column Settings > Filter > Select a value > Filter button. To exclude the item the catalogue request table, uncheck boxes next to the name not required in view. Keyword search mode available. Catalogue completed request data is grouped into 7 categories: Application; Version; Platform; Format; Order date; Delivered date; Actions. Request history can be downloaded as an Excel file by clicking the Export to Excel button. Apptimized shows the following screen after the request was completed: The option to download a package after the catalogue request is completed is available under the Actions column > Download . The option to import application as a source is available under the  Actions > Import as source   Apptimized shows the following modal window when successful:   Enter the value in the  Vendor name  field > Enter the value in the  Software name  field > Enter the value in the  Version  field > Enter the value in the  Language  field >  Import  button. All required fields are marked with an asterisk  * .   Apptimized shows the following notification and screen when successful:   The option to import application as a package is available under the  Actions > Import as package .   Note . This option becomes available if  Packaging – Self Service  module is presented on the project.   Apptimized shows the following modal window when successful:     Enter the value in the  Vendor name  field > Enter the value in the  Software name  field > Enter the value in the  Version  field > Enter the value in the  Language  field >  Import  button. All required fields are marked with an asterisk  * .   Apptimized shows the following notification and screen when successful:         Update Monitoring Update Monitoring is one of the Apptimized products that provides a user with a flexible and automated notification system. Also, the Apptimized Update Monitoring subscription enables a user to download a vendor media in a few clicks directly from the portfolio. Apptimized Update Monitoring informs users when the software vendor has released an application update or found vulnerabilities. Apptimized monitors over 380 of the most widely used applications.   Note. The Update monitoring appears in the project menu after it is initiated in the project settings by the project administrator. The following screenshot shows the notification email when the vendor releases a new version of the monitored application: Update monitoring interface The Update Monitoring is available under the Project menu > Updates : Apptimized shows the following screen when successful: The screen above shows the default Apptimized Portal interface when no applications are added. When a user adds the application to the monitoring list, Apptimized shows the following screen: Updates group data into six categories: Table 1. Update Monitoring data categories Category Details Vendor This category provides the details about the application’s vendor (e.g., Tim Kosse ) Software This category provides the details about the application’s name (e.g., FileZilla ) Latest version This category provides information about the newest version of the application released by the vendor and available in the Apptimized Platform. Your version This category provides information about the latest version of the application that is pinned within the recent user’s activities on the Updates page. The following colours are implemented to indicate the current state of the monitored application: - The latest version is available in the user’s packaged application portfolio - The newer version (in comparison to the one a user has in the portfolio) has been released by the vendor - The version a user has in the packaged application portfolio is outdated. This means that there are two or more recent releases of the application provided by the vendor   Note . The application version can be pinned in the following cases: 1. A user started the application monitoring ( Project menu > Updates  option > Track updates button > Select the application > Save button) 2. A user requested to process the latest version of the application ( Actions column > Process latest version button > Confirm update software > Yes button) 3. A user changes the version of the application ( Actions column > Versions button > Process column > Select the application’s version > Confirm update software > Yes button) 4. A user changes the version of the application manually ( Actions column > Edit button > Your version field > Enter the numeric value > Save button) Version’s mask This category indicates what versions of the same application are tacked for updates in parallel. The highest version of an application is tracked by default, but some vendors support several versions of applications (i.e., Java Runtime Environment ) in parallel. The version’s mask option enables a user to monitor an application version in addition to the highest one. Actions This category enables a user to provide the activities under the monitored applications. The following actions available: Process latest version Versions Edit Untrack Manage applications in Updates Add application The option to add an application to the monitoring list is available under the Track application button > Select the best matching application > Save button. Keyword search mode available. The application appears in the list of monitored applications when successful: New application request The option to create a request to add an application to the Update monitoring list is available under the Missing an application? button. The Apptimized Team will check the possibility of adding the application to the Updates list. Apptimized shows the modal window when successful: Enter the value in the  Vendor name  field > Enter the value in the  Software name field >  Request  button. All required fields are marked with an asterisk  * . Apptimized notifies the user when the request is submitted. The following screen provides an example of the notifications: Apptimized sends the following email when the application can be added to the Update monitoring list. Apptimized sends the following email when  the application  can't   be added to  the Update monitoring list. Update the application’s version The option to update the application’s version is available under: Your version column > Click on the highlighted application version > Process column > Select the application’s version > Confirm update software > Yes button). Actions column > Process latest version button > Confirm update software > Yes button). Actions column > Versions button > Process column > Select the application’s version > Confirm update software > Yes button. Note. In the case of a source media is not available for a certain update version, Apptimized shows the following screen: Actions column > Edit button > Edit software modal window > Your version field > Enter the numeric value > Save button. Edit monitored application settings The  option to change the settings of the monitored application is available under the Actions column > Edit button.      Apptimized opens the window when successful:     The option to change the application version manually is available under General in the Your version field.     The option to receive notifications about monitored applications is available under the Send notifications by Project Role or Group membership checkbox. This option is enabled by default.     The option to assign a user to receive Update Monitoring notifications is available under the Send notifications to specific users field.     The option to remove a user from Update Monitoring notifications is available under the Remove button.     The option to remove all users from Update Monitoring notifications is available under the Remove all items button.     The option to define how the monitored application is serviced is available under the Lifecycle servicing option setting.   Two servicing modes are available:   No – disables automatic delivery of update packages.   Care – enables automatic delivery of update packages when a new version of the application is released by the vendor.     If Care is enabled in the project, the following menu items are available:     Option   Description   Package type   This option defines which package formats should be generated for the monitored application. The following package types are available:     • Intunewin     • Apptimized PowerShell Wrapper (based on PSADT)       Multiple values can be selected.    This option is required .   Target platforms   This option indicates which operating systems the generated packages will support.     This option is required .   Bitness   This option defines the architecture type of the generated package. The following options are available:      • x86     • x64       Multiple values can be selected.    This option is required .   Application manager   This option allows selecting the user responsible for managing the application.      This option is required .   Discovery document (.html, .pdf, .doc, .docx)   This option allows attaching the discovery document for the monitored application. The following actions are available:      • Change – upload a new discovery document.    • Remove – delete the existing discovery document.    • Preview – open the document in a new tab for viewing.     To save the changes, click Save button.   Apptimized shows the following notification when successful:   Untrack applications The option to exclude the application from the list of monitored applications is available under the Actions column > Untrack button: The option to exclude all applications from the list of monitored applications is available under the Untrack all updates button: Vulnerability notifications Update Monitoring also provides the application’s vulnerability tracking feature for a user. Apptimized vulnerabilities tracking is based on the next services: NIST National Vulnerability Database Common Platform Enumeration (CPE) Common Weakness Enumeration (CWE) CIRCL incident statistics and threat ranking toolswatch/vFeed To receive vulnerability notifications, a user needs to enable this option in the project settings . The project administrator role is required. The option to check the list of detected vulnerabilities is available under the Update monitoring > Your version column > Click on the highlighted application version > Vulnerabilities tab. Apptimized notifies a user when the vulnerability is detected. The following screenshot provides the example of the notification: Export to CSV file Update Monitoring applications can be downloaded as a report file by clicking on the Export to CSV button. Echo Apptimized Echo provides test automation capabilities so that repeated app and package testing is simplified. A user can record a test case, and Echo will play it back automatically when needed. Note . Enabling Echo in Project settings by a project administrator is a prerequisite. Apptimized Echo is available under the Project menu > Echo : Apptimized shows the following screen when successful: This is an initial screen when no Echo activities are implemented. Echo dashboard The Echo statistics tab opens by default. The option to manage Echo platforms is available under the Manage Echo platforms button. Apptimized shows the following modal window when successful: To choose an Echo platform, a user can drag and drop a suitable platform from the  Available Echo platform / Available non-public Echo platforms  container to the  Project Echo platforms / Project non-public Echo platforms  container. The activities on managing Echo platforms finalize when clicking the Save button. The Echo platforms colors indicate the status of platform support by Microsoft: Green – the platform is currently supported by Microsoft; Yellow - the platform is currently supported by Microsoft. The Microsoft support will end in 2 months; Red - Microsoft does not support the platform. The option to filter Echo platforms in the Echo statistics table is available under the Filter platforms columns button. To exclude entities from the table, uncheck boxes next to the name not required in view. The echo reports overview is available under the Echo reports tab > Get report button: The option to set the Echo report time frames is available under the date field (Click the date field > Set the start date > Set the end date > Apply button). The option to customize columns in the Echo reports table is available under the Select columns button. To exclude entities from the table, uncheck boxes next to the name not required in view. When Echo activities are implemented, Apptimized shows the following screen: Table 1. Echo results statuses (Echo states) Icon Status Details Pending Tests are scheduled to start in a moment. Echo results will be available after the VM termination. Progress Tests will be completed in a moment. Echo results will be available after finishing the VM. Success Tests were completed as it was expected. Review A minor discrepancy between test results and the reference test case occurs. Failed A major discrepancy between the test result and the reference test case occurs. Echo statistics and overview Echo test cases statistics is available at Dashboards > Overview >Echo status chart. The instructions on how to set the overview page are available in the Dashboards chapter. Echo results are also available at My Dashboard > My Applications > Applications table > Echo column: The following statuses available: Table 2. Echo statuses Icon Status Details Disabled Status for the application with the disabled Echo option. No scenario Status for the application with enabled Echo option with no Echo scenario provided. Pending The echo is preparing to work on the application. Tests are scheduled to start momentarily. Echo results will be available after finishing the VM. In Progress The echo is working on the application. Tests will be completed momentarily. Echo results will be available after finishing the VM. Review At least one test failed, but all have finished and are no longer running or waiting. A minor discrepancy between test results and the reference test case occurs. Success The echo is ready to use. All tests are finished and succeeded. Failed Something went wrong with the Echo. All tests have finished and are no longer running or waiting. A major discrepancy between test results and the reference test case occurs. In this case, a user needs to run Echo Discovery again. The option to see the Echo performance is available under the echo status button: Test session results are grouped into the following columns: Image name; Platform; OS build; OS language; Start time and date; End time and date; VM state; Actions. Table 3. Actions with the application test session results Action Details Retest This option provides the possibility to run the VM one more time (e.g., if progress failed). Apptimized shows the following modal window: When clicking the Restart button, the retesting process launches automatically and Apptimized shows the following screen: Apptimized shows the following screen when successful: Results This option provides the ability to review the Echo performance and check the generated screenshots. Apptimized shows the following screen, when clicking the Result button: Test session results for the applications consist of the following components: Main information (i.e., software, platform, test, project, and user information). Editing this block is not available; Log test session results (i.e., platform test result (review, success, failed), additional comment). Editing this block is available; Screenshots tab. Editing this block is not available; Echo logs tab. Editing this block is not available; Windows logs tab. Editing this block is not available. Next, Log test session results block is shown in more detail. The option to log the platform test result is available under the Platform test result field (Log test session results block > Platform test result field > Select the test result > Save button). Review , Success and Failed options available. The field Additional comment is optional and can stay blank. The option to revert to the test session results screen is available under the Go back button. The option to restart the test case automatically is available under the Retest automatically button ( Results button > Log test session results block > Retest automatically button). Apptimized shows the following modal window to confirm restart activities: Apptimized shows the following screen when successful: The retesting process my take a few minutes. Apptimized shows the following screen when successful: The option to restart the test case manually is available under the Retest manually button ( Results button > Log test session results block > Retest manually button). This option provides the ability to change the Discovery result. Note . When clicking the Retest manually button the previous Echo deletes. VM preparation process may last a few moments: Apptimized shows the following screen: To receive new test results all installation and settings activities for the application must be proceeded.   The option to revert to the previous screen (i.e., Test session results ) is available under the Go back button. Apptimized shows the following screen when successful: When a user runs the retest activities, a screen of the VM is locked for not to disturb the Echo work. But a user can enable the Lock screen switch to involve in Echo process: The option to put text from the user’s host machine VM clipboard is available under the Clipboard button. Transferring clipboard content between the host machine and the VM works via "Cut & paste" in the majority of user scenarios. The option to provide a full-screen mode for a browser is available under the Fullscreen button. The option to stop the current VM session and to start it from scratch manually is available under the Retest manually button. The option to review discovery documentation is available under the Open discovery document button. Apptimized opens the discovery document in a new tab: The option to stop the VM is available under the Terminate button. All screenshots which were already produced will be saved and the Echo script will be changed. Apptimized shows the following modal window and notification: If a user fails test result this status will keep in the test session results. To proceed with the manually retest results, a user changes a platform test result from Failed to Success ( Log test session results block > Platform test result field > Success > Save button): If the test fails, there is an opportunity to choose one of the following remediation options: Repackage (Applicable when a user needs to request a change in the current package or send a new package request); Desktop App Assure (Applicable when the issue can’t be remediated by the latest app version or an updated package, nor can it be accepted); Accept (Applicable when the issue is of minor nature and doesn’t impact users’ productivity – and there is no alternative now). Apptimized shows the following screen when the remediations applied: The option to review the test case remediations is available under the Remediators button. Download This option provides the ability to download test case results documentation in HTML . View This option provides the ability to check the VM current session. The View button is disabled by default and becomes active when the VM restarts and retesting activities are in progress. Show history This option provides the ability to see the test case history. The option to clean all test case history is available under the Delete all history button. The option to delete a specific test case is available under the Remove button. The option to download test case results documentation in HTML is available under the Download button. The option to review test case results is available under the Results button. The keyword search available. Echo notifications The option to set the Echo notifications within the project is available under the Project menu > Notifications > Echo Playback Notifications checkbox and Project menu > Notifications > Echo Platform Notifications checkbox. To disable the notification, uncheck the box in front of the notification’s name not need in use. Apptimized sends to a user the Echo application testing summary within a project on a daily basis. The screenshot below shows an example of the email notification: Echo with vendor media (Discovery) If a user wants to automate testing of original vendor media (i.e., "raw, unpackaged software") as it was provided by the software vendor to the internal IT department or dev team, the Echo must be implemented at the Discovery - Self Service step. The following use cases available: Providing a manual installation (e.g., installation from exe , including feature selection and configuration); Providing a post-installation configuration (e.g., changing the application's setting after launching the application); Providing a typical use case like creating a file, entering, manipulating, and saving data. The following scenarios to open the transition screen available: My Dashboard > My Applications > Choose the project > Actions column > Process option; Project menu > Dashboards > Overview > Your assignments module > Choose the application > Actions column > Process option; Project menu > Dashboards > Portfolio > Actions column > Process option; Project menu > Import > Start import > Classic import > Application upload session > Apptimized Echo plays back test cases automatically in the following cases: a new version of the application released by the vendor uploaded to Portfolio and pushed to Discovery again (see Playback: Apptimized Assisted Discovery for future application versions ); a new version of Windows released by Microsoft ( Playback: WaaS automated OS compat testing for vendor media ). To start producing the Echo scenario via Discovery - Self Service , the relevant Playback Echo scenario form must be selected in the Project menu > Settings > Echo > Playback Echo scenario from field > Discovery – Self Service . Recording: Discovery – Self Service The option to import application is available under the Project menu > Import > Start import > Classic import > Application upload session > Next button. When the application is uploaded, and the metadata is reviewed, the Enable Echo option must be activated as it is shown on the screenshot below: Apptimized shows the transition screen when successful: The next step is available when clicking the Discovery – Self Service block. Apptimized shows the following screen when successful: The discovery process actions with Echo are similar to discovery process actions without Echo (see Discovery – Self Service manual ). VM preparation may take a few moments: When the synchronization process is finished, Apptimized shows the following screen: The uploaded files locate in the Apptimized files folder on the VM desktop. To start the installation process, a user opens the . EXE file located in the Source folder. Every action is captured as a screenshot which is shown in green boxes appearing on the right-hand side: When installation session and configuration settings completed, click the Finish button to terminate the VM. Apptimized shows the following modal window: Apptimized shows the following screen when successful: The next step available when clicking the Continue with Discovery - Self Service – Screenshots button. The screenshots review is finished when clicking the Save changes button. Apptimized shows the following screen when successful: The generated document is available in PDF and HTML formats. To download a document, click the Download generated HTML document or Download generated PDF document buttons. The option to edit a discovery document is available under the Edit generated document button. The document editing finalizes by clicking the Save button. The option to return to the discovery self-service screen mode is available under the Revert to Discovery – Self Service button. The option to finish the discovery process is available under the Finish button. The option to inspect the Echo results is available under the Project menu > Echo. Apptimized shows the following screen when successful: Playback: Apptimized Assisted Discovery for future application versions With Apptimized Echo a user can record the Discovery step activities for the application, and then (if the newer version of the application is released and a user added it to project’s portfolio), a user can specify the initial version of the application for which the Discovery step was recorded. By doing so, a user doesn’t need to perform a Discovery step for the newer version of the application anymore. When the workflow proceeds to the Discovery step, it will replay the recorded installation and configuration activities of the application from the initial version. So, a user saves time significantly. This feature is called Apptimized Assisted Discovery . To run Apptimized Assisted Discovery the new version of the application must be imported. The option to import application is available under the Project menu > Import > Start import > Classic import > Application upload session > Next button . When the application is uploaded, and the metadata is reviewed, the previous version of the application must be indicated, and Enable Echo option must be activated as it is shown on the screenshot below: When changes to the Previous version of the application field applied, the Show recorded Echo scenario option becomes available. A user can click on it to make sure that the needed Echo Discovery was selected: The import step finalizes when clicking the Finish button. Apptimized shows the transition screen when successful: The next step is available when clicking the Discovery – Self Service block. Apptimized shows the following screen when successful: The option to set the platform is available under the Select Discovery -Self-Service platform field (select a value from the drop-down list). The option to set the Echo assisted self-service mode is available under the Self-Service mode field (select a value from the drop-down list): The VM starts when clicking the Start VM button. VM preparation may take a few moments: Apptimized shows the following screen when successful: User’s interactions to VM are not needed. The Echo provides the Discovery activities automatically. When the playback scenario finished, Apptimized shows the following screen: The VM will be terminated automatically. Note. When any issues occur, the notification comes in yellow (i.e., minor issues) or red (i.e., major issues) color.   A user can Retest results or Continue with Discovery – Self Service – Screenshots . When the review of the generated screenshots completed, click Save changes button. Apptimized shows the following screen when successful: The generated document is available in PDF and HTML formats. To download a document, click the Download generated HTML document or Download generated PDF document buttons. The option to edit a discovery document is available under the Edit generated document button. The document editing finalizes by clicking the Save button. The option to return to the discovery self-service screen mode is available under the Revert to Discovery – Self Service button. The option to finish the discovery process is available under the Finish button. The option to inspect the Echo results is available under the Project menu > Echo. Apptimized shows the following screen when successful: Echo with packages (Testing) Apptimized Echo provides test automation capabilities by which repeated application and package testing is simplified. Echo will playback a recorded test case automatically when needed. If a user wants to automate testing of packages or software that has been prepared for automated and silent installation (e.g., for mass deployment via ESD), the Echo must be implemented at the Testing - Self Service step. The following use cases available: Automated installation (e.g., from install.cmd; Providing a typical use case like creating a file, entering, manipulating, and saving data. The following scenarios to open the transition screen available: My Dashboard > My Applications > Choose the project > Actions column > Process option; Project menu > Dashboards > Overview > Your assignments module > Choose the application > Actions column > Process option; Project menu > Dashboards > Portfolio > Actions column > Process option; Project menu > Import > Start import > Classic import > Application upload session > Apptimized Echo plays back test cases automatically in the following cases: a new version of the package is released by the packaging group (or by the packaging self-service or by the Apptimized packaging factory), is uploaded to Portfolio and is pushed to Testing again (see Playback: Apptimized Assisted Testing for future package versions and repeated testing (iterations) ); a new version of Windows is released by Microsoft (see Playback: WaaS automated OS compat testing for vendor media ).   To start producing the Echo scenario via Testing - Self Service , the relevant Playback Echo scenario form must be selected in the Project menu > Settings > Echo > Playback Echo scenario from field > Testing – Self Service . Recording: Testing – Self Service The option to import package (e.g., MSI ) is available under the Project menu > Import > Start import > Classic import > Application upload session > Next button. When the application is uploaded, and the metadata is reviewed, the Enable Echo option must be activated as it is shown on the screenshot below: Apptimized shows the transition screen when successful: Skipping to the Testing modules required. The next step is available when clicking the Testing – Self Service block. Apptimized shows the following screen when successful: The testing process actions with Echo are similar to testing process actions without Echo (see Testing – Self Service manual ). VM preparation may take a few moments: When the synchronization process is finished, Apptimized shows the following screen: The uploaded files locate in the Apptimized files folder on the VM desktop. To start the installation process, a user opens a file (i.e., EXE, MSI ) located in the Source folder (or an installation file in the Packages folder). Every action is captured as a screenshot which is shown in green boxes appearing on the right-hand side: When installation session and configuration settings completed, click the Finish button to terminate the VM. Apptimized shows the following modal window: Apptimized shows the following screen when successful: The next step available when clicking the Continue with Testing - Self Service – Screenshots button. The following options to log test session results are available: Untested; Success; Failed. The default value is Untested . The field  Optional comment  can stay blank. The screenshots review is finished when clicking the Save changes button. Apptimized shows the following screen when successful: The generated document is available in PDF and HTML formats. To download a document, click the Download generated HTML document or Download generated PDF document buttons. The option to edit a testing document is available under the Edit generated document button. The document editing finalizes by clicking the Save button. The option to return to the discovery self-service screen mode is available under the Revert to Testing – Self Service button. The option to finish the discovery process is available under the Finish button. The option to inspect the Echo results is available under the Project menu > Echo. Apptimized shows the following screen when successful: Playback: Apptimized Assisted Testing for future package versions and repeated testing (iterations) Apptimized Echo enables a user to record Testing step activities for the package, and then (if the newer version of the application is released, a new package of it is created and added to project’s portfolio), a user can specify the initial version of the application on which Testing step was recorded. By doing so, a user doesn’t need to perform the Testing step for the newer version of the package anymore. When the workflow proceeds to the Testing step, it will replay the recorded installation and configuration activities of the package. So, a user saves time significantly. This feature is called Apptimized Assisted Testing . To run Apptimized Assisted Testing the new version of the application (or package) must be imported. The option to import application is available under the Project menu > Import > Start import > Classic import > Application/ package upload session > Next button . When the application (package) is uploaded, and the metadata is reviewed, the previous version of the application must be indicated, and Enable Echo option must be activated as it is shown on the screenshot below: When changes to the Previous version of the application field applied, the Show recorded Echo scenario option becomes available. A user can click on it to make sure that the needed Echo Discovery was selected: The import step finalizes when clicking the Finish button. Apptimized shows the transition screen when successful: The next step is available when clicking the Testing – Self Service block. Apptimized shows the following screen when successful: The option to set the Echo assisted self-service mode is available under the Self-Service mode field (select a value from the drop-down list): The VM starts when clicking the Start VM button. VM preparation may take a few moments. Apptimized shows the following screen when successful: User’s interactions to VM are not needed. The Echo provides Testing activities automatically. When the playback scenario finished, Apptimized shows the following screen: User’s interactions to VM are not needed. The Echo provides the Discovery activities automatically. When the playback scenario finished, Apptimized shows the following screen: The VM will be terminated automatically. Note. When any issues occur, the notification comes in yellow (i.e., minor issues) or red (i.e., major issues) color. A user can Retest results or Continue with Testing – Results . When the review of the generated screenshots completed, click Save changes button. Apptimized shows the following screen when successful: The generated document is available in PDF and HTML formats. To download a document, click the Download generated HTML document or Download generated PDF document buttons. The option to edit a testing document is available under the Edit generated document button. The document editing finalizes by clicking the Save button. The option to return to the testing self-service screen mode is available under the Revert to Testing – Self Service button. The option to finish the discovery process is available under the Finish button. The option to inspect the Echo results is available under the Project menu > Echo.   Playback: WaaS automated OS compat testing for vendor media Apptimized Echo allows a user to understand, will the package work properly on the next releases of the Windows platform or not. The next Windows releases are available to Apptimized as Windows Insider builds. When Echo enabled and the non-public testing platforms (Windows Insider builds) are selected in project settings, Echo will record the installation and configuration of created packages, and then recorded steps will be replayed automatically against the selected Windows Insider builds. A user will receive an automatic notification if playback succeeds on a new Windows update. To implement saved Echo, a new version of the application must be imported via the Classic import ( Project menu > Import > Start import > Classic import > Application upload session > Next button). When the application is uploaded, and the metadata is reviewed, the previous version of the application must be indicated, and Enable Echo option must be activated as it is shown on the screenshot below: When changes to the Previous version of the application field applied, the Show recorded Echo scenario option becomes available. A user can click on it to make sure that the needed Echo Discovery was selected: The import step finalizes when clicking the Finish button. Apptimized shows the transition screen when successful: Any other actions with the Discovery - Self Service are not needed. The option to check the Echo status of the new application is available under the: Project menu > Apptimized shows the following screen when successful: Note. The Echo status of the new application in a portfolio will change to Pending. The Success Echo status of new application means that new application processed through Testing as it was saved in the previous version via Echo: My Dashboard > My Applications . Apptimized shows the following screen when successful: Note. The Echo status of the new application in a portfolio will change to Pending. The Success Echo status of new application means that new application processed through Testing as it was saved in the previous version via Echo:   Echo Assumptions Summarizing the FAQ on Echo results Apptimized support team assumes that a user is not trying to do the following actions during the recording step or Echo playback: Mouse gestures: drag & drop of windows or individual elements of a window. Recording actions in web browsers (i.e., Internet Explorer, Edge, Chrome, Firefox, etc.) and web applications (i.e., Slack, Microsoft Teams, GitHub Client).  Recording actions on applications without a graphical user interface (GUI). Echo is a GUI-based testing automation tool for Windows applications. It supports win32 and UWP applications. It cannot be used to test GUI-less applications such as services, drivers, and other types of applications that do not have a graphical user interface. However, you can still record the installation and launch of such applications. Interaction with Windows Explorer: Echo does not record and replay the next actions made in Windows Explorer: - opening the context menu by click on the right mouse button and work with the context menu; - creating, deleting, copying and pasting folders and files manually (installation process of an application will be recorded properly); - working with tray icons and calling the application’s main GUI from the tray. Entering text in Java-based applications (software that requires "Oracle Java" prerequisite or works based on Java core technologies). Working with CMD: switching between folders, adding, deleting, copying, cutting and pasting files, launching executable and other files via CMD. Echo filters interaction with CMD during recording, because there is much of system noise that processing in the background through CMD. In terms of changes in the application’s logic, core technologies and UI from one version of the application to another, Echo does support: Change of text, color, and font of the application’s UI element ( * ); Change of position of the application’s UI element within one page (except Java-based applications); Change of graphical design (size, color, form) of the page-container of the application’s UI element (except Java-based applications); Echo does not support the next changes between different version of the application: Change of sequence of windows for the installation process, the application’s startup and configuration, including adding new windows or removal of old ones; Removal of application’s UI elements. Example: user clicked on button “OK” in the application’s settings in the previous version of the application during recording, but in the new version, this button doesn’t exist; Change of type of the application’s UI element. Example: element previously was a checkbox, but in the new version, it is an item of the dropdown list; Moving the application’s UI element from one UI’s page to another. Example: “Ask for updates” dropdown list was on “General” tab of app’s settings, but in the new version it is on the “Miscellaneous” tab; Change of location for menu list items within different parent items. Example: a user clicked on “Tools” menu on app’s main page, then selected the dropdown list “Options”, and “Advanced” list item. On the newer version of the app “Options” dropdown list is located under another list “Miscellaneous”, which is under “Tools” menu. In such case, Echo will not play click on “Options” dropdown list on the newer version and will fail. ( * ) “application’s UI element(s)” means UI element which was a part of recorded (Discovery or Testing) document. Example: A user enabled the recording of the Discovery step of the application “Mozilla Firefox” (version 61). A user added the newer version (i.e., 65) of this application, in which a vendor changed the sequence of windows of the installation process. If a user wants the Echo to perform Assisted Discovery on version 65 but based on recorded steps with version 61, Echo will fail because of changed GUI logic. Some applications are built by their vendors to contain complex logic regards to the interaction of users with GUI elements. Examples: Echo supports Java-based applications partially, but input in text fields in such applications is not supported; Some UI elements are too complicated for automatic testing by Echo: windows that are built as panels, text boxes with complex logic of implementation, etc. Apptimized Echo might fail with recording or playback of such test cases. When a user encounters an issue, contact with the Apptimized support team (to provide the needed information to reproduce the issue) is required.   Storage Apptimized Storage enables uploading applications and using it in a future for several times skipping the Import step. A user directly uploads the application or creates a directory to group applications. Apptimized Storage enables uploading applications once and using them in the future several times, skipping the Import step. A user directly uploads the application or creates a directory to group applications. Note. The "storage" option appears in the project menu after it is initiated in the project settings by the project administrator. The Storage is available under the Project menu > Storage : Apptimized shows the following screen when successful: The option to upload an application is available under the Upload file button > Click here to select file button > Browse to select the file > Open button. The application appears in the Storage when successful. The option to create a folder is available under the New directory button > Enter a folder name > Save button. All required fields are marked with an asterisk * . The folder appears in the Storage when successful. The option to delete an application or a folder is available under the Delete button. The option to download an application is available under the Download button. The option to open the folder is available under the Open button. The option to create a new subfolder is available under the New directory button. The sequence of actions is the same as it described above. The option to add a new application is available under the Upload file button. The sequence of actions is the same as it described above. The option to revert to the Storage initial screen is available under the Get back to the root directory button. Care and Care+ Care Apptimized Care  is one of the Apptimized services that provides access to a store, where a user can track the version package of the application which is packaged according to a standard procedure and is ready for use.   The latest application versions available for orders within 2 hours release of the update by the vendor, and ready for download within seconds after the request.     Note.  The "Updates" option appears in the project menu after it is initiated in the  project settings  by the project administrator.   Apptimized sends the follow-up email when the user has accessed the Apptimized Care:     Apptimized Care interface   The  Care  is available under the  Project  menu >  Updates   Apptimized shows the following screen when clicking Updates button:   The screen above shows the default Apptimized Portal interface when several applications are added.   Care groups data into six categories:   Table 1. Care data categories   Category   Details   Vendor   This category provides the details about the application’s vendor (e.g., Tim Kosse )   Software   This category provides the details about the application’s name (e.g., FileZilla )   Latest version   This category provides information about the newest version of the application released by the vendor and available in the Apptimized Platform.   Autopush This category shows if Autopush is active. Your version   This category provides information about the latest version of the application that is pinned within the recent user’s activities in the Care page.   The following colors are implemented to indicate the current state of the monitored application:   - The latest version is available in the user’s packaged application portfolio    - The newer version (in comparison to the one a user has in portfolio) has been released by the vendor   - The version a user has in the packaged application portfolio is outdated. This means that there are two or more recent releases of the application provided by the vendor       Note . The application version can be pinned in the following cases:   1. A user started the application package monitoring ( Project menu > Updates option > Track updates button > Select the application > Save button)   2. A user requested to process the latest version of the application ( Actions column > Process version packages section > Select the Windows bitness > Select PSADT or Intunewin package > Download package or Push to SCCM / Intune > Confirm update software > Yes button)   3. A user changes the version of the application package ( Actions column > Versions button > Process package column > Select the application’s version > Download package or Push to SCCM / Intune > Confirm update software > Yes button)   4. A user changes the version of the application manually ( Actions column > Edit button > Your version field > Enter the numeric value > Save button)   Servicing option  This category provides information on whether the Care or Care+ service is enabled.   The following options are available:   Care - indicates that Care service is enabled; Care+ - indicates that Care+ service is enabled; -  indicates that none of the services are enabled.   Actions   This category enables a user to provide the activities under the monitored applications.   The following actions are available:   Process version packages for Windows 32 bit, Windows 64 bit   Versions   Edit   Untrack   Application Versions Page The separate window with all available application versions is available under Actions column > Versions option. When successful, Apptimized shows the following screen: The page displays all available versions of the selected application, including release date and release type information, and allows processing of source files for a selected version. The version table supports search by Version column, sorting by Version and Release Date . The Release Date column displays the vendor release date using user date/time formatting. New request  New package request   The option to track an application package and add it to the monitoring list is available under the Track application  button > Select the best matching application > Save button.   Keyword search mode available.     The application appears in the list of monitored applications when successful:   Apptimized notifies the user when the request is submitted. The following screen provides an example of the notifications:   New application request   The option to create a request to add an application to the Update monitoring list is available under the Missing an application?  button. The Apptimized Team will check the possibility to add the application to the Update monitoring list.   Apptimized shows the modal window when successful:   Enter the value in the Vendor name field > Enter the value in the Software name field > Request button. All required fields are marked with an asterisk * . Apptimized notifies the user when the request is submitted. The following screen provides an example of the notification:   Apptimized sends the following email when the application can be added to the Care list of apps. Apptimized sends the following email when the application can't be added to the Сare list of apps.   Update the application’s version   The option to update the application’s version is available under:   Your version column > Click on the highlighted application version > Process package column > Select the application’s version > Select the packaging format > Download Package /P ush to SCCM as Application / Push to Intune buttons > Confirm update software > Yes button).   Actions column > Process version packages section > Select the Windows bitness > Select PSADT or Intunewin package > Download package or Push to SCCM / Intune > Confirm update software > Yes button)     Actions column > Versions button > Process package column > Select the application’s version > Select the packaging format > Download Package /P ush to SCCM as Application / Push to Intune buttons > Confirm update software > Yes button).   Note. In the case of the packages are not available for a new update version for a time, Apptimized shows the following screen:   Actions column > Edit button > Edit software modal window > Your version field > Enter the numeric value > Save button.     Edit monitored application settings   The option to change settings of the monitored application is available under the Actions >  Edit button. Apptimized shows the modal windows when successful:     All required fields are marked with an asterisk * .   The option to change the version of the application manually is available under the Your version field.     The option to create the Apptimized packaging request for the monitored application is available under the Сreate package request on update option. The following options are available     Option   Description   Care   This option enables the Care service (see Care )   Care+   This option enables the Care+ service (see Care+ )       Care option is enabled by default.   General Tab Table 2. Packaging request   Option   Description   Packaging technology   This option indicates which packaging technology should be implemented by Apptimized specialists.   The following packaging technologies available:   Apptimized PowerShell Wrapper (based on PSADT)   Intunewin   This option is required.   Both technologies enabled by default.   Target platforms This option indicates which packaging platform should be implemented by Apptimized specialists.   The following packaging platforms available:   Windows 10 64 bit     This option is required.   Packaging platform option is enabled by default.   Bitness   This option indicates the bitness of the created package.   The following options available:   x86   x64   This option is required.   Both options enabled by default.   Application manager   This option allows to set up default user assignee for managing application (downloading, editing, deploying, untracking).   Discovery document   This option allows to upload the discovery document of the application provided by the Apptimized team.   Application language Specifies the default language of the application included in the delivered Care package. To modify the default language, the Customizer must be enabled in the project. Note. The multiple-choice option is available in the Package types and Bitness fields.   Updates Configuration A user goes to Administration > Settings > Updates Sections The Updates section in the Administration > Settings menu includes three parts: General , Intune , and SCCM . Below is a description of each section and its available options: Table 3. Updates Settings Section Description Options General Configure general settings for updates and notifications. Enable Updates : Enables the Updates feature for Care and Care+ applications. Enable Vulnerability Notifications: Sends email notifications when application vulnerabilities are detected. Intune Predefine default templates for Intune Auto-Push Deployments. Set default Intune Assignment Template. Configure default Intune Template for streamlined deployments. SCCM Predefine default templates for SCCM Auto-Push Deployments. Set default Deployment Type Template. Configure default Deployment Template  SCCM application pushes. The Intune section in the Updates settings allows configuring default templates for Intune Auto-Push deployments. Below are the available options: Table 4. Intune Settings Option Description Required Enable Auto-Push (checkbox) If enabled, additional options for configuring Intune Auto-Push are displayed. no Intune Environment Specifies the target Intune environment for deployments, yes Intune Template Predefined template for configuring application deployment settings in Intune. yes Intune Assignment Template Optional template for assigning applications to groups or users in Intune. no The SCCM section in the Updates settings allows configuring default templates for SCCM Auto-Push deployments. Below are the available options: Table 5. SCCM Options Option Description Required Enable Auto-Push (checkbox) If enabled, additional options for configuring SCCM Auto-Push are displayed. no SCCM Environment Specifies the target SCCM environment for deployments, yes Deployment Type Template Predefined template for configuring application deployment settings (e.g., installation methods, rules). yes Deployment Template Predefined template for configuring deployment settings (e.g., scheduling, user experience settings). no Intune Push Tab Table 6. Push Option   Description   Intune Environment This option allows choosing an appropriate environment. Intune Template This option allows choosing created templates. Intune Assignment Template This option allows choosing assignment templates. Enabling Auto-Push is available in the checkbox.  Enabling Supersedence is available in the checkbox.  Auto-push for latest version is available under  "Install the latest version" . Apptimized shows the following screen when successful:   App versions older than the current ones are cleared during the autopush process. A " Create Assignment Template" button allows creating assignment templates: Apptimized shows the following screen when successful:   Editing of template is available: Table 7. Editing Template Option   Description   End User Notifications This option allows choosing to show all toast notifications, s how toast notifications for computer restarts or hide all toast notifications. Delivery Optimization Priority This option has two functions: "content download in foreground" and "content download in background". Time Zone This option allows choosing an appropriate time zone. Application Availability This option allows specifying when the app is downloaded to the user's device. Application Installation Deadline This option allows specifying when the app is installed on the targeted device. When more than one assignment is made for the same user or device, the app installation deadline time is picked based on the earliest time possible. Restart Grace Period This option allows starting as soon as the app installation has finished on the device. When the setting is disabled, the device can restart without warning. Device Restart Grace Period The default value is 1,440 minutes (24 hours). This value can be a maximum of 2 weeks. Restart grace period will be Enabled by default.  When installing the app, the following window will appear: SCCM Push Tab The SCCM Push tab allows users to configure settings for pushing applications to SCCM (System Center Configuration Manager). Below is a detailed explanation of the options displayed in the image: Table 8. SCCM Push Option   Description   Required Example SCCM Environment Select the target SCCM environment, where the application will be deployed. yes "Demo Environment" Deployment Type Template Choose a predefined template that defines deployment type settings, such as installation methods and rules.   yes "Demo Deployment Type Template" Deployment Template Select a template for deployment configuration, including scheduling and user experience settings.   no "Demo Deployment Template" Enable Auto-Push Automates application deployment to SCCM without manual intervention.   no Checkbox  (Enabled/Disabled) Install the latest version Autopush for the lates available version in SCCM immediately. no  Checkbox (Enabled/Disabled) Enable Supersedence Allows an application to supersede an older version during deployment.   no Checkbox (Enabled/Disabled) Auto-Push Workflow  When Enable Auto-Push is checked: The application is automatically exported to SCCM using the selected templates. You can specify whether the deployment applies to x86 , x64 , or both architectures (if applicable). No further manual actions are required for deployment initiation. Ensure that the SCCM environment and templates are properly configured to avoid deployment issues. Use Case for Auto-Push : Automating deployments for routine application updates or large-scale rollouts. Reducing manual steps in the SCCM deployment process. Untrack applications     The option to exclude the application from the list of monitored applications is available under the Actions column > Untrack button:     The option to exclude all applications from the list of monitored applications is available under the Untrack all applications button:   Notifications    Apptimized notifies the user when the new package version is available. The following screen provides an example of the email notification:     Apptimized notifies the user when the application package track request is resubmitted. The following screen provides an example of email notification: Care+ Apptimized Care + is a fully configurable automated application lifecycle management and packaging service. The "Care +" option appears in Updates after it is initiated in the  project settings by the project manager.  Apptimized shows the following screen when clicking Updates button:   The screen above shows the default Apptimized Portal interface when several applications are added.   Care+ and Care groups data into six categories:   Table 1. Care+ and Care data categories   Category   Details   Vendor   This category provides the details about the application’s vendor (e.g., Tim Kosse )   Software   This category provides the details about the application’s name (e.g., FileZilla )   Latest version   This category provides information about the newest version of the application released by the vendor and available in the Apptimized Platform.   Autopush This category shows if Autopush function is active. Your version   This category provides information about the latest version of the application that is pinned within the recent user’s activities in the Care page.   The following colors are implemented to indicate the current state of the monitored application:   - The latest version is available in the user’s packaged application portfolio    - The newer version (in comparison to the one a user has in portfolio) has been released by the vendor   - The version a user has in the packaged application portfolio is outdated. This means that there are two or more recent releases of the application provided by the vendor       Note . The application version can be pinned in the following cases:   1. A user started the application package monitoring ( Project menu > Updates option > Track updates button > Select the application > Save button)   2. A user requested to process the latest version of the application ( Actions column > Process version packages section > Select the Windows bitness > Select PSADT or Intunewin package > Download package or Push to SCCM / Intune > Confirm update software > Yes button)   3. A user changes the version of the application package ( Actions column > Versions button > Process package column > Select the application’s version > Download package or Push to SCCM / Intune > Confirm update software > Yes button)   4. A user changes the version of the application manually ( Actions column > Edit button > Your version field > Enter the numeric value > Save button)   Сare/+   This category provides information on whether the Care or Care+ service is enabled.   The following options are available:   Care - indicates that Care service is enabled; Care+ - indicates that Care+ service is enabled; -  indicates that none of the services are enabled.   Actions   This category enables a user to provide the activities under the monitored applications.   The following actions are available:   Process version packages for Windows 32 bit, Windows 64 bit   Versions   Edit   Untrack   New package request   The option to track an application package and add it to the monitoring list is available under the Track application  button > Select the best matching application > Save button.     The application appears in the list of monitored applications when successful. New application request   The option to create a request to add an application to the Update monitoring list is available under the Missing an application?  button. The Apptimized Team will check the possibility to add the application to the Update monitoring list.   Apptimized shows the modal window when successful:   Enter the value in the Vendor name field > Enter the value in the Software name field > Request button. All required fields are marked with an asterisk * . Update the application’s version   The option to update the application’s version is available under Actions >Versions :   Apptimized shows the following screen: Editing Monitored Application Settings The option to edit the application’s settings is available under Actions >Edit : Table 2. Editing Settings Option   Description   Your Version This category provides information about the latest version of the application. Send Notifications by Project Role or Group membership This checkbox enables sending notifications. Send Notifications to Specific Users This option allows choosing specific users by providing their emails.  Lifecycle Servicing Option This option provides information on whether Care or Care+ service is enabled.   Package type This option indicates which packaging technology should be implemented by Apptimized specialists.   Target platforms This option indicates which packaging platform should be implemented by Apptimized specialists. Packaging platform option is enabled by default.   Urgent This option gives an opportunity to speed up the packaging process. Please clarify the deadlines with your project manager. Bitness   This option indicates the bitness of the created package.   The following options available:   x86   x64   This option is required.   Both options enabled by default.   Application Manager   This option allows setting up default user assignee for managing application (downloading, editing, deploying, untracking).   Comment This field gives an opportunity to provide description to auto generated issues and suggestions. Discovery Document   This option allows uploading the discovery document of the application provided by the Apptimized team.   Trigger  This option allows defining events to control the frequency of update package delivery.  The following triggers available: Version-based Time-based Security release-based Customiz e r Customiz e r is the next evolution of our Care product, allowing customers to apply custom settings ensuring every Care package meets their requirements.   How to access Customizer   To enable Customiz e r in a project, navigate to Project Settings and select the corresponding checkbox.       Note: If the checkbox is not visible in the settings, contact the Apptimized support team or the designated contact person from Apptimized to request the necessary permissions.   Customiz ation settings overview   All custom configurations are stored under the “Updates – Customization” and “Updates – Wrapper” sections in the project settings. These settings apply to all Care packages enabled within the project.     The Customization tab contains the following settings:     Table 1. Configuration settings   Configuration   Description   Package Name   Defines the naming convention for packages   Detection method script template   Specifies the script template used to verify successful installation and uninstallation during Intune deployment   Disable auto-update functionality   Enables or disables application auto-update functionality (if supported)   Remove desktop shortcuts   Removes desktop shortcuts or leaves them based on the vendor’s default behavior   Pressing the Save button opens the Confirm the action modal window. The modal window allows to select whether to apply the updated settings to all existing Care applications in the project or only to new ones. The Yes button applies the settings to all existing Care applications, while the No button applies them only to new ones. The Wrapper tab configures the PowerShell App Deployment Toolkit (PSADT) template and includes the following settings:   Table 2. Wrapper settings   Configuration   Description   Deployment Mode   Defines the package installation mode (Silent, Interactive, or Non-Interactive)   Installation logs location   Specifies the log file path for PSADT and package logs   Branding location   Configures the registry key path used for package branding   Custom Logo   Sets a custom logo for the PSADT installation window (preferred format: .ico, 64×64). The Set default option restores the default logo. Custom Banner   Sets a custom banner for the PSADT installation window (preferred format: .png, 450×50). The Set default option restores the default banner. Per-application settings In addition to the customization settings applied to all applications within a project, there is an option to configure each application individually with additional customization options. To access  per-application settings , navigate to the Updates page > click the Actions (three-dot) button > select Edit for the desired application. All available settings are displayed under the Care – Customizer submenu item. Per-application settings include three main sections, each offering different customization options: General , Additional , and Advanced settings. General per-application settings include the same configurations available in the project settings, providing the option to overwrite them at the application level. Table 3. General per-application settings Configuration   Description   Detection method script template  Specifies the script template used to verify successful installation and uninstallation during Intune deployment Disable auto-update functionality  Enables or disables application auto-update functionality (if supported) Remove desktop shortcuts Removes desktop shortcuts or leaves them based on the vendor’s default behavior Application language Specifies the default language of the application included in the delivered Care package Additional per-application settings display the default values for installation parameters and applications to close within the Care package. These values can be modified as needed to meet specific application requirements. Table 4. Additional per-application settings Configuration   Description   Installation parameters Specifies the set of parameters applied to the application source file during the installation process Apps to close  Specifies the list of processes that are closed during package installation and uninstallation Advanced per-application settings allow adding PowerShell scripts and files to enable additional customization options. Clicking the Add PowerShell Script button opens a modal window where a PowerShell script can be added to be included in the final generated Care package. Table 5. Add PowerShell script modal window Configuration   Description   Section Specifies the section where the PowerShell script will be included ( Pre-Installation, Installation, Post-Installation, Pre-Uninstallation, Uninstallation, or Post-Uninstallation ) Architecture  Defines the package architecture(s) to which the PowerShell script applies Comment Adds a comment above the PowerShell script to describe the action it performs PowerShell script A multiline section that may include PowerShell and PSADT cmdlets to be added to the final generated Care package Clicking the Add File button opens a modal window where files (up to 100 MB in size) can be added to the package. These files can later be used within PowerShell scripts to include additional configuration files, license files, or prerequisite installers. Table 6. Add file modal window Configuration   Description   Upload file Field used to upload a file to the package Applicable for architecture  Defines the package architecture(s) to which the file will be added Location Specifies the package folder where the file should be placed (custom subfolders are created automatically if needed) After making the necessary changes, click the Save button. Clicking the Reset button restores default values for all fields but does not remove PowerShell scripts or added files. P rocess ing customized packages   Once at least one configuration is modified from its default value, Customiz e r becomes active for the project. When a new version of the application is released, customized packages will be generated alongside the default Care packages.   If a user needs a customized package immediately instead of waiting for a new version release , they can navigate to the Updates menu and generate a customized package for the latest available version by clicking the “Create Customized Packages” button.   Once customized packages are delivered, users can manage them via the Actions context menu under the “Process Customized Packages” section.   By selecting a package, users can choose to:   Download the package locally   Push the package to a connected deployment system (Intune or SCCM)     Additionally, users can access all available package versions by clicking the “Versions” button .    This page lists both default Care and customized packages for all available versions.     Email notifications   Users receive an email notification when a customized package is delivered.       In case a default Care application was reworked, users are notified that regenerating the customized package may be necessary if the mentioned in email reason affects its functionality   IntuneWin Bulk Conversion IntuneWin Bulk Conversion feature allows users to migrate their SCCM packages to intunewin format using an automated tool. IntuneWin Bulk Conversion IntuneWin Bulk Conversion feature allows users to migrate their SCCM packages to intunewin format using an automated tool. Apptimized sends the follow-up email when the user has accessed the IntuneWin Bulk Conversion feature :  Trial Project Overview Apptimized shows the first project filled with the top 10 most wanted applications: A user can now process converting these applications to IntuneWin format or can give it a try and upload his own packages for a conversion.   The project is already configured to work with the conversion with the predefined settings. To check the conversion settings, the user should go to Administration > Settings > Bulk Conversions > IntuneWin  This page shows all the configurations applied to all newly created conversion in the project. Table 1. IntuneWin Bulk Conversion Settings Option Details   [PackageName] placeholder value This option shows a construction of the PackageName that will be applied to the result package Name of result archive This option provides a r esult package archive name template Detection method script template  This option shows a PowerShell script template which will be used to check if the package is installed or uninstalled Path to store .intunewin file  This option shows the Intunewin file location in the result package structure Path to store detection method file  This option shows a d etection method file location in the result package structure Path to store txt file with deployment commands  This option provides information about t xt file with deployment commands location in the result package structure Path to store extracted content of .intunewin file  This option shows the Intunewin package extracted content location in the result package structure Key file to detect the package location  This option shows t he file name in the source archive that points to the level where the package is located (e.g. Deploy-Application.exe for PSADT packages) An entry point file for Intune wrapping  This option provides a f ile name used for intunewin conversion as an entry point (usually, it's an installation file without arguments) Install commands This option provides the i nstallation file name with arguments Uninstall commands  This option provides the u ninstallation file name with arguments Responsible people to receive notifications  This field gives information about p eople who will receive an email notification if the conversion for the particular application fails   Testing image  This option allows choosing the i mage that will be used for testing incoming packages Skip incoming packages testing  If this option is enabled, the applications will be converted without incoming packages testing Bulk Conversion Creation To create the first Bulk Conversion a user should go to Bulk conversions > IntuneWin . The following screen will be displayed: On this page all Bulk Conversions a user creates will be displayed. The " Create Bulk Conversion" button should be pressed to proceed. A user has to enter a name of a conversion in the following field: Selecting applications for converting to the .intunewin format is available in the next window: The maximum application count per conversion is 200 . If the count is more than 200, the first 200 will be processed. There is also a possibility to overwrite bulk conversion settings to apply changes only for the current conversion using the “Settings tab”. When the bulk conversion configuration is finished, the user can click on “ Create” button to save the changes and run conversion later or “Run now” button to start conversion immediately. Bulk Conversion Processing A newly created bulk conversion is listed on the page with the “In progress” status. A user can click on the “View” action button to review the bulk conversion details. The list contains every application that is part of the conversion. Applications are currently in the "Pending" stage, which indicates they are being queued up for processing. When hovering over the “Pending” status , information about the position in queue and estimated launch time will be shown. Table 2. Stages Stage Details   Pending The application in the queue and is ready to be converted Testing The incoming app is going to be tested to make sure installation and uninstallation works properly Wrapping The application is being wrapped to the. intunewin format Table 3. Statuses Status Details   Pending The application in the queue and is ready to be converted In progress  The current stage is in progress Skipped If the “Skip incoming packages testing” option is enabled in conversion settings, the status will be set to the “Testing stage” Failed A conversion is failed for some reason Removed The application is removed from bulk conversion and should be processed manually Success A conversion is finished successfully  When the conversion completes, a user will receive corresponding email notification : As a result, Bulk Conversion Status will be set to “Completed”. Navigating to the conversion details , a user can download individual results package by clicking on the “Download” action button. \ Importing Own Packages In addition to working with predefined packages in the trial project, it is possible to import own packages to attempt converting them to the .intunewin format. To learn how to import the packages into the project, please follow this link . It's important to note that the application metadata and the PackageName components used in the package should match exactly .  Prior to start converting the imported packages, it’s important to review the conversion settings if anything should be changed. If a user struggles with understanding which settings should be changed, he should contact Apptimized support team. Error Handling In case the conversion for the particular application fails, a user will receive an email notification with detailed information about the issue: The conversion item status will be changed to 'Failed'.   The hint with explanation of the reason for the failure will be shown: In case the installation or uninstallation of incoming package fails as shown on the screenshot above, it’s required to check the package and fix problems manually. After the package is fixed, the archive should be re-uploaded to the Portfolio item. A user should go to Dashboards > Portfolio. Finding a failed application in the Dashboard list is available by clicking on the “ Settings ” action button. A user should c lick on the “Reupload source” button and re-upload fixed package archive. To restart the conversion process for the following item , a user goes back to Bulk Conversion > “Restart” action button. In case it doesn’t work, a user can skip testing the application by clicking on the “Mark test as success” action button. Additionally, by using the "Mark as removed" action button, an application can be removed from the conversion process if it cannot be converted automatically for any reason. The application needs to be manually converted in this case. If the conversion for the particular application fails for a technical reason, a user can try to restart the conversion. If it doesn’t help, he should contact the support team.