Endpoint Protection

 View Only
  • 1.  Nothing happens when setup.exe is started

    Posted Jun 16, 2009 12:33 PM
    Strange problem with installing the SEP client. Through the SEPM console, I packaged a setup.exe file, which I placed on the network for client installation. The problem occurs when the setup is launched, a setup.exe process will appear in the task manager, also in [c:\docs&settings\username\localsettings\temp] a symantec folder will appear with all the unpacked files. After 20 seconds or so the setup files and symantec folder gets deleted and the setup.exe process stops.

    There are no failure logs or failure messages provided by the installation. I've also tried copying the setup.exe file straight to the local laptop which failed as well with the same problem.

    However, I can install the SEP client straight from the [Symantec Endpoint Protection MR4_EN_CD1] folder.

    Symantec support didn't have any answers, so now I'm trying to troubleshoot further.


  • 2.  RE: Nothing happens when setup.exe is started

    Posted Jun 16, 2009 12:40 PM
     The best way to troubleshoot a install failure issue is by going through Install Log.
    If this setup.exe is not creating one enable MSI logging manually at the time of installation.
    Once we have the logs we would get a clear picture.
    How to Enable Windows Installer Logging
    support.microsoft.com/kb/223300


     



  • 3.  RE: Nothing happens when setup.exe is started

    Posted Jun 16, 2009 12:47 PM
    When you install the package on the computer manually, right click on the exe and use the "Run As" option. You can use the local administrator or domain administrator credentials for this.

    Just to rule out an issue with a corrupt package, export another oackage with the same settings and deploy it to the machine to check if the issue gets resolved.

    Cheers,
    Aniket


  • 4.  RE: Nothing happens when setup.exe is started

    Posted Jun 16, 2009 01:14 PM
    Aniket, that's what is so strange about the package b/c it works on other machines. What we have is a bunch of laptops which have Win XP SP3 images on them. Those laptops fail, but the package works for another set of laptops that have different XP SP3 images on them. I also tried what you mentioned with runas. I was actually logged in as the local admin as well.

    I will try msi logging.


  • 5.  RE: Nothing happens when setup.exe is started

    Posted Jun 16, 2009 02:29 PM
    The problem Vikram is that i'm not running the .msi file from symantec. I'm running the packaged setup.exe file. In the registry I created the [Installer] key under the root of [hkey_local_machine\software\policies\microsoft\windows]

    I created the Reg_SZ entries as well. The msi.log file only runs when executing .msi files. My problem is that I get no installation failure log when i run the setup package.


  • 6.  RE: Nothing happens when setup.exe is started

    Posted Jun 16, 2009 02:47 PM
    Have you tried creating a package with non-single exe and deploying on this client.
    There mightbe some issue with setup wrapper on this client.
    Do you get any errors or warnings in Event Viewer at the time of install. 


  • 7.  RE: Nothing happens when setup.exe is started

    Posted Jun 16, 2009 02:50 PM
    Even if you run setup.exe it will run the MSI file in the background.
    SETUP.exe is nothing but just wrapped up MSIand other files.
    The log MSI installer creates does not have the name sep_inst.log it will have some diffrent name.some alphnumeric i don't remeber right now.
    you can check in %temp% by time modified and it will be a big file