archive-com.com » COM » E » EMCOSOFTWARE.COM

Total: 393

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Operation Management View - MSI Package Builder
    Projects Using Placeholders and Filters Application Log Program Preferences Evaluation of the Program Program Updates Main Program Actions How can I leave my Feedback Professional edition manual Enterprise edition manual Operation Management View The Operation Management view shows the detailed progress of each operation being performed at the moment and allows canceling a particular operation or all running operations By default it is located at the bottom of the MSI Package Builder main window Pic 1 The Operation Management view Progress information for every operation is shown in the pane with the progress bar the operation information text and the Cancel button The Cancel button is used to cancel individual running operations whereas if the grouping operation is canceled all the sub operations are also canceled Cancel All The Cancel All button from the Operation Management view toolbar can be used to cancel all the operations running in the application You can cancel all the running operations by clicking the Cancel All button on the toolbar of the Operation Management view Contact Us Privacy Policy Terms of Use Copyright 2001 2016 EMCO Software MSI Package Builder Remote Installer Remote Shutdown Network Inventory Ping Monitor WakeOnLan Network Malware Cleaner Permissions Audit

    Original URL path: http://emcosoftware.com/msi-package-builder/doc/operation-management-view (2016-05-01)
    Open archived version from archive


  • Graphical User Interface features - MSI Package Builder
    with a modern and intuitive graphical user interface because we appreciate the users of our products and would like them to feel glad that they have EMCO programs installed on their PCs Lots of resources were involved in creating this kind of an interface for you and now we are proud we have done it Custom DPI settings are fully supported so that you can use EMCO programs on any monitor with any resolution you like The Microsoft User Interface Guidelines on Layout Icons and Sizing have been a powerful base for this work and we are glad to tell you that they are fully complied with and supported With the help of the skinning support and the Ribbon UI interface every customer can configure the program UI to feel comfortable during each working day EMCO also provides you with the High Contrast skin along with the bonus skins pack which is an accessibility feature designed for people with vision impairment The High Contrast color scheme can increase legibility for some users by heightening the screen contrast with alternative color combinations This chapter gives you a detailed description of how to fully enjoy the graphical user interface features the skinning

    Original URL path: http://emcosoftware.com/msi-package-builder/doc/graphical-user-interface-features (2016-05-01)
    Open archived version from archive

  • Evaluation Wizard - MSI Package Builder
    and Buy now Optionally you can press Exit button to close the program In this section we will help you to choose the option that will best fit your needs The Evaluate option shows you the time left until the evaluation period expires You should choose this option to continue the evaluation process the wizard will be closed and you can start working with MSI Package Builder You can use the program as long as the evaluation period does not expire to get a closer introduction to its main features It you have already purchased the license for using the EMCO MSI Package Builder Enterprise you should choose the Enter License Code option to activate the program This options also should be chosen if the extended evaluation request has been approved by EMCO Software and you have been provided with the Extended License If you are having problems with finding the License Code refer to the Where can I get my License Code section of this document After choosing the Enter License Code option the program activation page is displayed on the screen Pic 2 Activating EMCO MSI Package Builder Enterprise To activate EMCO MSI Package Builder Enterprise copy and paste the License Code to the input field on this page and press Activate the program will be restarted to activate If the evaluation period has expired and you are not sure you have fully introduced yourself to EMCO MSI Package Builder Enterprise main features you can once request the extended evaluation As soon as the request is processed by EMCO Software you are provided with the Extended License to prolong the evaluation period To request the Extended License you should choose the Request extended evaluation option After choosing this option the request form will appear on the screen Pic

    Original URL path: http://emcosoftware.com/msi-package-builder/doc/evaluation-wizard (2016-05-01)
    Open archived version from archive

  • Ribbon - MSI Package Builder
    and reviewing Those tabs simplify access to the program features because they organize the commands in a way that reflects the tasks people perform in those programs Pic 1 The Ribbon bar We are delighted to let you know that we fully conform with Microsoft Ribbons Guidelines and would like to introduce some Ribbon features to you To learn more about Ribbon the story of its development and its usability features you may visit The Story of the Ribbon article from the MSDN blogs Application Menu The Application Menu invoked using the Application button is somewhat similar to the File menu in most programs that use a classic user interface but it gives you more Pic 2 Application Menu It contains links to the most helpful actions located under different tabs but made available from one access point Also you can open the recently used projects using the links from the Recent Projects part Quick Access Toolbar The Quick Access Toolbar is an end user customizable bar located near the Application Menu or below the Ribbon bar depending on the configuration It can contain links to both Ribbon items and Ribbon groups Pic 3 Quick Access Toolbar To add an action link to the quick access toolbar right click this action and select Add to Quick Access Toolbar from the pop up menu The groups can be added in the same way the only difference being that to add a group you should right click its caption Representation and Navigation Features The representation of the Ribbon bar can also be configured to make your work more comfortable You can minimize Ribbon so that the tab s content is only shown when the tab is clicked on thus extending the program workspace Also if it is not convenient for you to

    Original URL path: http://emcosoftware.com/msi-package-builder/doc/ribbon (2016-05-01)
    Open archived version from archive

  • How to choose a Repackaging Mode? - MSI Package Builder
    support silent execution or you cannot find out the parameters to be used for silent execution Also this mode is to be used when you are going to create an MSI package based on generic changes performed manually rather than those performed by existing installations While monitoring existing installations it is recommended to use the Automated Monitoring mode Using this mode guaranties that the monitoring process will stop only after the installation is fully complete thus all the changes performed by the installation are included into the resulting MSI package To use this mode the installation setup should be designed in such a manner that all processes performing the application and operating system configuration exit on installation completion If it is not possible to fulfill these requirements or it is not enough to monitor only those changes that are performed by existing installations you should use the Advanced Monitoring mode In such a case you are responsible for stopping the monitoring process when all required changes are performed The main prerequisite for repackaging via changes monitoring is the fact that the monitoring should be performed in a clean environment And the main disadvantage of this mode is that the resulting MSI will not be fully cross platform thus the repackaging results will be valid only for the same operating system as used for monitoring The Repackaging via Wrapping mode is the recommended one for experienced users Although it is a little more complicated for creating silent MSI packages it allows you to avoid all the limitations of the monitoring technology The installations wrapped into an MSI package will be distributed in the original state thus deployed correctly to any operating system regardless the deployment process particularities It is the mode you should always choose if it is not required to

    Original URL path: http://emcosoftware.com/msi-package-builder/doc/how-to-choose-a-repackaging-mode (2016-05-01)
    Open archived version from archive

  • Automated Monitoring - MSI Package Builder
    continue following the wizard to configure process filters used for monitoring Pic 3 Extending monitoring process filters As for the monitoring filters you can define additional processes to be filtered choosing them from those currently running The wrong processes monitoring filters configuration may lead to improper installation monitoring if the activity of the process required by the installation You must not filter the processes when you are not sure if their activity can affect the installation results Otherwise the MSI package built as a result of such monitoring will not be able to perform the same installation It is also possible to add remove any process from those currently running to from the persistent monitoring filters such as change the persistent monitoring process filters configuration using a corresponding hyperlink After you press Finish the monitoring process is started and as soon as it completes an MSI package is created containing the monitored changes in the specified location When does the monitoring process stop When a monitoring process is running you can see the monitoring progress on a screen It displays how many installations from those defined are already complete Pic 4 Monitoring progress As soon as all the installations are complete the monitoring process is stopped automatically The installation is treated as completed when the installer process and all the processes daughterly to the installer process exit Please note that if the setup wizard suggests running the installed application upon the installation completion you should decline this suggestion Otherwise the monitoring module will wait for the started application to exit You can abandon the monitoring process using the Stop button at any time although it is not recommended The automated monitoring process does not stop Which option should I choose You can face the situation when you have passed through all the steps of the setup wizard but the automated monitoring process does not stop To choose further steps it is required to understand what leads to this situation Let us take a closer look at the list of possible reasons and appropriate solutions for each one First of all the monitoring process may not stop because the installation is still performing the application configuration in background Thus it is recommended to be patient and always wait for some time after the installer application user interface has closed Another possible reason is that the monitored installation has launched the installed application or one of its modules This can happen if you have not unchecked an appropriate option on the installation wizard finish page or if the installation always performs the step of launching the installed program Please note that those executable modules can be run in background or minimized to tray In such a case you should close the launched applications and continue waiting for the monitoring to stop automatically The monitoring module will switch to next installation if any or create the MSI package if this installation is the last one from those monitored as soon as those applications

    Original URL path: http://emcosoftware.com/msi-package-builder/doc/automated-monitoring (2016-05-01)
    Open archived version from archive

  • Advanced Monitoring - MSI Package Builder
    as the monitoring results This project will contain all changes performed by the running processes to the operating system during the monitoring session Pic 1 Configuring MSI package The next step is to provide a path to save a resulting MSI package to and configure the package The detailed information about an MSI package configuration is available in the Creating MSI Package section of this document After configuring the package itself you can already press Finish to proceed with the repackaging procedure Optionally you can continue following the wizard to configure process filters used for monitoring Pic 2 Extending monitoring process filters As for the monitoring filters you can define additional processes to be filtered choosing them from those currently running The wrong processes monitoring filters configuration may lead to improper installation monitoring if the activity of the process required by the installation to succeed is ignored You must not filter the processes when you are not sure if their activity can affect the installation results Otherwise the MSI package built as a result of such monitoring will not be able to perform the same installation As soon as you press the Finish button the monitoring process is started and since that moment till the moment when you stop it all changes except those skipped regarding to the monitoring filters configuration are recorded and saved to the specified project The MSI package based on these changes is created at the specified location When should I stop the monitoring process While using an advanced mode for monitoring changes the monitoring process cannot be stopped automatically because there is no trigger for that So it is up to you to choose the moment when it should be stopped Before stopping the monitoring process you should make sure that all required changes are

    Original URL path: http://emcosoftware.com/msi-package-builder/doc/advanced-monitoring (2016-05-01)
    Open archived version from archive

  • Repackaging via Wrapping - MSI Package Builder
    be no chance that a generated MSI package will be installed incorrectly on specific target machines The disadvantage of this mode is that you need to know the silent installation parameters and possibly provide installation scenario files to generate an MSI package that can be used for silent deployment Another difference that can be treated both as an advantage and as a disadvantage is that multiple installations will be always executed and there will be multiple entries in the Programs and Features section of the Windows control panel after deploying such package To perform repackaging via wrapping either choose the Wrap Installation option in the Repackage Installation wizard or click the Wrap Installation shortcut in the Product Actions group on the Welcome Screen In any case you ll be able to provide a set of installations to be wrapped and their deployment order Pic 1 Repackaging via wrapping MSI Package Builder allows you to wrap both Windows Installer packages and executable installation packages For each package you can define if it should be repaired and uninstalled while repairing and uninstalling a generated MSI package You can also specify a list of additional files if required and the parameters to be passed to the installer to perform install uninstall and repair The provided packages are included into a created MSI package and also saved into a project with the specified name for future usage The detailed information about the wrapped packages configuration is available in the Wrapping Existing Installations section of this document Pic 2 Configuring MSI package The next step is to provide a path to save a resulting MSI package to and configure the package The detailed information about an MSI package configuration is available in the Creating MSI Package section of this document As soon as the package

    Original URL path: http://emcosoftware.com/msi-package-builder/doc/repackaging-via-wrapping (2016-05-01)
    Open archived version from archive



  •