7 Replies Latest reply on Mar 15, 2010 10:02 AM by alps

    Enteo training

    Bankeralle Apprentice
      Hi

      We have just started to use Enteo at Work and i have some general question regarding Enteo

      Is it possible to see any "gui" installation during installation of an msi,  
          escript package etc...... Or is everythin run silently??

      EScript. How do you uninstall an escript package. If it's a msi you simply delete the policy but that dont work when dealing with escripts i think. Do you have to script the installation and uninstallation. If yes could you show me some examples

      Thx for all answers ....
        • 1. Re: Enteo training
          NicoS1 Master
          Hello Bankeralle,

          welcome to the board.

          Regarding MSI installations, the escript command "MSIInstallproduct" always tries to run an MSI in silent mode. If you want to see a gui during an msi installation you could use the "RunAs" or "Execute" Command and run "msiexec" with your MSI file you want to install as parameter.

          Other setups like Installshield, Nullsoft Installer, Innosetup, Wise etc. are normally installed via silent switches which depend on the Installer themselfe. If you leave out the silent switches the setup is run normally, similar as if you doubleklick the exe :-)

          Regarding uninstallation, it's very important that you tell the package that it can be uninstalled! You can achieve this in your package under "Execution Option", there is a tab named "Deinstall" or something similar.

          Enteo has serveral commands with it will revert automaticly during a uninstall. MSIInstallProduct is one of them! So you don't need to modfy the script itselfe for uninstallation. Others are InstallFileList, CreateLink etc. (all commands which are reverted automaticly are documented somewhere in the help files).

          If you need to revert anything during an uninstall which cannot be reverted automaticly, you have to make a "jump mark" (? sorry, dont know how the command is named in the english version) at the end of the script which is named $BeginUninstallScript  (watch the exact spelling please). Enteo will recognize this point automaticly and everything you put in your script under $BeginUninstallScript will be executed when you uninstall a package, either via Software Shop or be deleting a policy and say that it should be uninstalled.

          For example:


          : $BeginUninstallScript
          RunAs("C:\Program Files\Mozilla Firefox\uninstall\helper.exe","/S" ... )


          Would be the Uninstall part for Mozilla Firefox, since its no MSI and it's installed via a Wise or Nullsoft installer (forgot which one exactly). But don't forget to activate the uninstall option in the execution options, other wise this does not work ;-)
          • 2. Re: Enteo training
            Bankeralle Apprentice
            Thx for the answer, because im brand new in the enteo world i dont quite get it working

            1. About seeing the gui
                If i run the instalaltion like this(for an msi)
                Execute('msiexec /i .\Ekstern$\Msidata\Notepad2.msi" /qb! ALLUSERS=1')
                The msi get's installed but without any gui.
                What am i doing wrong
            2. Regarding uninstall of an escript package
                I made an escript package with the following syntax
            Image and video hosting by TinyPic

                The instalaltion work fine but not the uninstallation. Even though i hva checked under define execution settings  for uninstalaltion. When deleting the policy it seems like the application get installed again
            • 3. Re: Enteo training
              NicoS1 Master
              To 1. The /qb! makes the setup unattended (if possible), and should show a UI (just status bar, without cancel button. The nearest cause for NO UI showing up would be, that the Installation runs in the Service Installation Mode.

              Enteo has 3 kinds of installers:
              1. Service Installer: Runs in the context of your Enteo Admin User, runs and installs software even if no user is logged on. But cannot install user specific parts! Also Script installed by the Service Installer shows NO Interactive parts (MessageBoxes, MSI UI's...)

              2. AutoInstaller: Is what gets triggert by the NiAgent32.exe which should be started when a User is logged on, this one runs in the User Context, can install userparts (or script parts which require interactive actions), but only runs when a user is logged on.

              3. Software Shop: Similar to the Autoinstaller, just the User can trigger installations when he wants manually (Shop Policys).

              In the execution options you can select when a script should be allowed to run:
              "Only if user is logged on"
              "Only if no user is logged on"
              "No matter if user is logged on or not"
              (I dont know if the 3 options are named exactly like that in the english version)

              They simlply mean:
              "Only if user is logged on" => Only can be installed via Autoinstall (2) or Software Shop (3)
              "Only if no user is logged on" => Only can be installed via Service Install (1)
              "No matter if user is logged on or not" => Can be installed via all Installers (1,2,3)

              Now... if you apply a software policy and click "execute changes now" on the client, normally the Serviceinstaller starts first and the autoinstaller right after. So the Serviceinstaller installs your package without showing any UI cause it can't.

              So it should work if you flag your package "Only if User is logged on".

              For the 2nd problem, you should check the client logfile and maybe post it here.

              The default path is C:\Program Files\Common Files\Enteo\NiLogs and then you have either:
              NI32_x.log = Software Shop Logfiles
              NIAI32_x.log = Auto Installer Logfiles
              NISRV32_x.log = Service Installer Logfiles

              I don't know which installer executed your package, so you have to check by yourselfe. x = an upcounting number.
              • 4. Re: Enteo training
                alps Specialist
                Hello,

                one interesting question regarding your post, NicoS: How does the flagging relate to your posting above? Sometimes I am a little bit confused, why there is a "Computer-related" part and "Computer-related Service-executed" part, because I would assume that the Computer-related part is executed anyway under the service account, because computer related needs rights in every case. In our environment user accounts are always restricted and don't have local admin accounts and my guess is in other environments this is also the case, however I am wondering why a lot of lines in the Enteo Workbench are flagged just "Computer-related" when you make a recording of an installation. Furthermore...if for example a MSI installation is not flagged at all (means "Executed always") the installation fails tough I remeber that I heard in the past, that the installer recognized that there are not enought rights and will be requesting those from the service account?
                • 5. Re: Enteo training
                  NicoS1 Master
                  Hello alps,

                  my post was more specific to the package flagging in the package execution options.

                  Well, I had several problems with that, too. Cause there had been some changes from the v6.0 release till todays release.

                  Well the difference between user-related and compter-related should be clear, but the difference between as service is not sometimes. I cannot say it 100% sure, but I think the behavior is as following:

                  Computer Related:
                  With Shop & AutoInstaller = Logged on User rights.
                  With ServiceInstaller = Service Rights.

                  Computer Related as Service:
                  With Shop & AutoInstaller = Service rights.
                  With ServiceInstaller = Service Rights.

                  User Related:
                  With Shop & AutoInstaller = Logged on User Rights.
                  With ServiceInstaller = Doesn't get executed.

                  User Related as Service:
                  With Shop & AutoInstaller = Service rights.
                  With ServiceInstaller = Doesn't get executed.

                  Maybe someone could tell me if I'm right or wrong.

                  MSI Flagging is a completely different story... I remember like a year ago where half of our MSI packages stopped working after we applied a Cumu Patch... It somehow worked in the past without any flagging, but then it suddenly stopped and most of our installations failed. Since then we either run MSI Installations only with Service Installer (then flagging doesnt really matter) or you simply flag it computer related as service. The only problem is: If you have flagged a MSIInstallProduct Line as Computerrelated with service, then doubleclick it to change anything (like Loglevel or Transform), click ok... then it automaticly changes back to computer related without service.

                  I don't know if its a common enteo issue, or if its maybe a problem with our GPOs... but well... it works if its flagged correctly.

                  The only command (besides script related parts like if, else, set) that works best without any flagging is the RegLoad Command it automaticly detemerines what rights it needs (for HKLM parts).
                  • 6. Re: Enteo training
                    Bankeralle Apprentice
                    Thx for the reply

                    We are going to use the service installerer in our environment. So i guess now that this is not possible. I thought this was possible if you changed the cmd syntax to runas og execute as you described in your first reply..


                    1. Service Installer: Runs in the context of your Enteo Admin User, runs and installs software even if no user is logged on. But cannot install user specific parts! Also Script installed by the Service Installer shows NO Interactive parts (MessageBoxes, MSI UI's...)
                    • 7. Re: Enteo training
                      alps Specialist
                      Hi NicoS,

                      thanks for your explanation and sharing experience. I thought somehow my installation is coruppted when the computer-related commands didn't work under restricted accounts anymore. Good to see that I am not alone :-)