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".
  • Services Modifications - MSI Package Builder
    the generated MSI package installation For the Create operation the scope of options is the widest Together with the service name used to install the service you must also provide a display name used for the service and a path to the file from the current project to be used as the service executable on the General tab It is also recommended to provide a service description which is displayed in a services section of the computer management console for each installed service The other options available for service creation on the General tab are the execution options those are the service type startup type and the arguments to be passed to the service on startup On the Log On tab for the service being created you can choose it should log on as a local system or as a specific user For the local system account it is possible to define if the service should interact with desktop On this tab you can also configure an error control level used for this service You can choose from the following Normal the startup program logs the error in the event log but continues the startup operation Critical the startup program logs the error in the event log if possible If the last known good configuration is being started the startup operation fails Otherwise the system is restarted with the last known good configuration Ignore the startup program ignores the error and continues the startup operation The Dependencies tab is also used while configuring the service creation and allows defining the services this service depends on The service name is provided to the Dependency field and you can add edit and remove dependencies on line using the corresponding buttons built into this field While specifying a service name display name description startup arguments and dependencies you can use the property definition placeholders standing for the standard MSI properties See the Property Definition Placeholders section of this document for the list of available placeholders For the other operations except Create the Log On and Dependencies tabs are not used and only the Name field from the top part of the General tab is used As for the Delete operation the service name is the only field to be specified The service with the matching name will be deleted from a target PC during a generated MSI package installation For the Control operation after providing a service name you should define triggers to start and stop the service on You can choose between Install Uninstall Both and None options to start and stop the service on As for the Restart operation you should choose if it should be restarted on install uninstall or both events Edit The Edit button from the Management group on the Services contextual Ribbon page should be used to change the selected services modification Delete The Delete button from the Management group on the Services contextual Ribbon page allows you to delete the selected services modifications from the selected

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


  • Side-by-side Assemblies Deployment - MSI Package Builder
    project and can be edited only after the projects containing those changes are prepared Let us take a closer look at configuring side by side assemblies Win32 Assembly The Win32 Assembly button from the New group on the Project Ribbon page and on the Assemblies contextual Ribbon page should be used to add a new Win32 assembly to the currently configured project NET Assembly The NET Assembly button from the New group on the Project Ribbon page and on the Assemblies contextual Ribbon page should be used to add a new NET assembly to the currently configured project To add a new assembly to a project you can choose the New Win32 Assembly and New NET Assembly items from the Assemblies view pop up menu Alternatively you can use the Win32 Assembly and NET Assembly button from the New group on the Project and Assemblies Ribbon pages The dialog will appear on the screen to let you configure the assembly to be added Pic 1 Configuring a Win32 Assembly While configuring a Win32 assembly you should provide a path to the assembly manifest and security catalog files If it is required you should also add assembly files to the Assembly Files table As for a NET assembly it is required to provide a path to the assembly file Optionally it is possible to add configuration files required for the assembly installation to the Assembly Files table Edit The Edit button from the Management group on the Assemblies contextual Ribbon page should be used to change the selected assembly Delete The Delete button from the Management group on the Assemblies contextual Ribbon page allows you to delete the selected assemblies from the selected project Copy To The Copy To button from the Management group on the Assemblies contextual Ribbon page should

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

  • Drivers Deployment - MSI Package Builder
    the driver creation and allows defining the drivers this driver depends on The driver name is provided to the Dependency field and you can add edit and remove dependencies on line using the corresponding buttons built into this field While specifying a driver name display name description and dependencies you can use the property definition placeholders standing for the standard MSI properties See the Property Definition Placeholders section of this document for the list of available placeholders For the Delete operation the Dependencies tab is not used and only the Name fields from the General tab is applicable The driver with the matching name will be deleted from a target PC during a generated MSI package installation If you would like to register the basic driver as a filter for one or more device classes you should enable the Register this driver as a device class filter option on the General tab After that you will be able to register this driver to device classes as a lower level or an upper level filter on the Device Class Filters tab The Device Class Filters tab contains a list of device class filters the configured driver is used as You can add and remove the filter configuration entries using the corresponding buttons on the toolbar Let us take a closer look on the device class filter configuration Pic 2 Registering a driver as an upper level device class filter When registering the driver as a device class filter you must provide the device class to register the driver to into the Device Class field Within the Filter Type drop down you should choose the type of the filter to be registered A Lower Level filter driver monitors and or modifies I O requests to a particular device Typically such filters redefine hardware behavior to match expected specifications For example a lower level class filter driver for mouse devices could provide acceleration performing a nonlinear conversion of mouse movement data An Upper Level filter driver adds value for a particular device For example an upper level device filter driver for a keyboard could enforce additional security checks The Dependency and Order fields are responsible for the filter driver position in a scope of all filter for the specified device class To add a new driver package deployment action you should either choose the New Driver Package item from the pop up menu or press the Driver Package button from the New group on the regular Project and contextual Drivers Ribbon pages The file system browser will be opened to let you choose the driver information file for the package As soon as it is choses you will see the New Driver Package dialog where you are proposed to configure the driver package deployment action in detail Pic 3 Adding a driver package be pre installed during an MSI package installation The common information on a driver package being configured is displayed on the General tab As you can see the Driver Information

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

  • Using Pre and Post Actions - MSI Package Builder
    to be executed should be provided to the Command field You can input the action command manually and choose a file to be opened either from the project or from the local file system Use the Select File and Select Project File buttons build into the edit box to select required files The parameters to be passed to the command are to be defined in the Parameters field Both the Command and Parameters fields support the property definition placeholders so you can use the standard MSI properties while configuring the actions See the Property Definition Placeholders section of this document for the list of available placeholders The Windows Installer does not allow installing configuring and uninstalling packages in parallel though it is impossible to execute installation repair or uninstallation of another MSI package within the pre and post actions execution scope As for the start type you can choose between Before Install After Uninstall Before Uninstall and After Uninstall So you can for example check some prerequisites and perform preparation steps before the package installation and perform a kind of clean up after uninstalling the package For each action you can choose if to run it as administrator or as invoker if the installer should wait for the action to complete and if it should analyze the completion result The Administrator value from the Run As drop down should be selected only for executing the actions that required administrative privileges to function It is insecure to run all actions as administrator If the successful action completion is required for the installation to complete successfully than you can check both the Wait until this action is completed and Interrupt the install uninstall process if this action is completed with an error options But be aware of the fact that if the action is implemented incorrectly the whole installation will fail Move Up The Move Up button from the Order group on the Pre Post Actions contextual Ribbon page should be used to move the selected actions up the execution order Move Down The Move Down button from the Order group on the Pre Post Actions contextual Ribbon page should be used to move the selected actions down the execution order By default the actions execution order is the same as the addition order but you can reorder the actions using the Move Up and Move Dow n items from the pop up menu or the Order group on the Pre Post Actions contextual Ribbon page Edit The Edit button from the Management group on the Pre Post Actions contextual Ribbon page should be used to change the selected action configuration Delete The Delete button from the Management group on the Pre Post Actions contextual Ribbon page allows you to delete the selected actions from the selected project Copy To The Copy To button from the Management group on the Pre Post Actions contextual Ribbon page should be used to copy the selected actions to another project Move To The Move To

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

  • Wrapping Existing Installations - MSI Package Builder
    is possible to use the property definition placeholders See the Property Definition Placeholders section of this document for the list of available placeholders Together with the common properties you can also use the PackageSetupFile and the PackageSetupDir placeholders The PackageSetupFile placeholder stands for the path to the setup file during the package deployment and the PackageSetupDir is replaced with the path to the setup file location To be able to repair and uninstall this wrapped package you should enable the Allow Repair and Allow Uninstall options within the Maintenance Parameters group In case if the wrapped package is an MSI you can define the windows installer parameters used for uninstall and repair if required Otherwise if the wrapped package is an executable installer you should define a command line to be executed to uninstall and or repair the package Move Up The Move Up button from the Order group on the Wrapped Packages contextual ribbon page should be used to move the selected packages up the deployment order Move Down The Move Down button from the Order group on the Wrapped Packages contextual ribbon page should be used to move the selected packages down the deployment order By default the wrapped packages deployment order is the same as the addition order but you can reorder the packages using the Move Up and Move Down items from the pop up menu or the Order group on the Wrapped Packages contextual Ribbon page Please take into account that the install repair and uninstall order for the wrapped packages is the same Edit The Edit button from the Management group on the Wrapped Packages contextual Ribbon page should be used to change the selected wrapped package configuration Delete The Delete button from the Management group on the Wrapped Packages contextual Ribbon page allows you to delete the selected wrapped packages from the selected project Copy To The Copy To button from the Management group on the Wrapped Packages contextual Ribbon page should be used to copy the selected wrapped packages to another project Move To The Move To button from the Management group on the Wrapped Packages contextual Ribbon page allows you to move the selected wrapped packages to another project The wrapped packages can be changed deleted and transferred between projects To change the wrapped package select it and either double click or choose the Edit item in pop up menu or on the Wrapped Packages contextual Ribbon page While editing a wrapped package you can define the same scope of properties as during its creation To delete the wrapped from the project select it and choose the Delete item in the pop up menu or on the Wrapped Packages contextual Ribbon page The well known drag drop and copy paste techniques are fully supported for copying and moving wrapped packages between projects Also you can use the Copy To and Move To buttons from the Management group on the Wrapped Packages contextual Ribbon page to transfer the selected wrapped packages to

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

  • Capturing Changes - MSI Package Builder
    Also you can use it to simply review the changes performed to the underlying operating system during the monitoring session Start Monitoring The Start Monitoring button from the Capture group on the Home Ribbon page should be used to start a new session for tracking changes performed to the system Stop Monitoring The Stop Monitoring button from the Capture group on the Home Ribbon page should be used to stop the currently running monitoring session To start a new monitoring session to capture the changes performed to the underlying operating system you can press the Start Monitoring button from the Capture group on the Home Ribbon page or choose the Start Monitoring item from the Projects view pop up menu The wizard will appear on the screen where you can provide a name for the project to be created on a basis of the changes monitored and choose additional processes to be filtered during the monitoring process The activity of the filtered processes will be ignored by the monitoring modules thus the changes performed by these processes will not be included into the resulting set As soon as the monitoring is started you can perform the changes to be monitored thus run the applications you are going to track activity of and or perform the changes manually To stop the capturing procedure press the Stop Monitoring button from the Capture group on the Home Ribbon page or choose the Stop Monitoring item from the Projects view pop up menu When the monitoring process is stopped the project with the specified name is created containing all the changes performed to the underlying operating system while the monitoring was active If you want to create an MSI package based on these changes you should first prepare the created project For the detailed

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

  • Signing MSI Packages - MSI Package Builder
    digital certificate used in the signature usually supplies the signer identification information however Thus the private key must be supplied through some other means Additionally the signature must include the certificate chain for the cryptographic service provider CSP up to a root certificate trusted by the user in order for the signed file to be authenticated So in all there are several items that need to be provided in order to generate a digital signature Microsoft has developed a certificate store technology to reduce the above complexity Using this technology when a user enrolls to obtain a certificate they specify the private key information the CSP information and the certificate store name for the certificate The certificate will then be stored in the certificate store and be associated with the other items When the user wants to sign a package they only need to identify the certificate in the certificate store The code signing tool will retrieve the certificate the private key and the certificate chain for the CSP all based on the specified certificate When signing a package a trusted time server is used to generate a time stamp for a digital signature This is performed to guarantee that the package is signed with the certificate that is neither expired not revoked Requirements for Digital Certificate For the digital certificate to be used by MSI Package Builder for signing generated MSI packages the following set of requirements must be met 1 The certificate must include the Code Signing 1 3 6 1 5 5 7 3 3 within its Intended Purpose 2 The certificate s Valid From date must be less and the Valid To date must be greater than a package signing date 3 The digital certificate must be installed in the Current User certificates storage 4 Both private key and signer identification information must be supplied 5 The private key must be available together with the sigining certificate in the certificate storage In case you have a private key in a separate file please use the tool provided by Microsoft for preparing the private public key pair for importing into the certificates storage as described Pvk2Pfx Combine PVK SPC to PFX In case if the digital certificate does not meet the above stated requirements MSI Package Builder will not offer you to use it for signing MSI packages Configuring Packages Signing MSI Package Builder allows you both to define the common packages signing configuration to be used for adding digital signatures to generated MSI packages and to override those settings for specific projects The common digital signing options are specified on the Packages Signing preference page and the overriding feature can be used either when creating an MSI package or in the Project Details view Pic 1 Configuring the package signing options In any case if you enable the packages signing you are proposed to select the signing certificate to be used for creating a digital signature and choose the time server for generating a digital signature

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

  • Importing MSI Package - MSI Package Builder
    edition manual Enterprise edition manual Importing MSI Package With MSI Package Builder you can not only create new MSI packages but also modify existing ones using the embedded MSI import capability Just choose an MSI you want to modify import it to a new project perform the changes needed and build a new one This feature is designed to handle the situation when you have generated an MSI package deleted the project but need to make some changes to the package or upgrade it Though it is guaranteed that the import of the MSI package built with any previous version of MSI Package Builder is fully supported some MSI features are not available in the MSI Package Builder import technology So if you are importing a generic MSI package please check the import results and a newly generated MSI package carefully The feature of creating a new MSI package on a basis of an existing MSI package is available in the Project Setup wizard Alternatively you can use the Import MSI Package button from the Project Management group on the Home Ribbon page or the Import MSI Pakcage link in the Product Actions group on the Welcome Screen Import MSI Package The Import MSI Package button from the Project Management group on the Home Ribbon page should be used to create a new MSI Package Builder project based on a changes performed by an existing MSI package In any case you will reach the page where you are proposed to provide the path to the existing MSI package to import and a name for the project to be created as a result Pic 1 Importing an existing MSI package When the import is complete you can see the project that contains the changes performed by the specified MSI package created

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



  •