Endpoint Protection

 View Only
Expand all | Collapse all

Endpoint Upgradation Problem

Srikanth_Subra

Srikanth_SubraNov 04, 2011 12:44 AM

Srikanth_Subra

Srikanth_SubraNov 08, 2011 10:18 PM

  • 1.  Endpoint Upgradation Problem

    Posted Nov 03, 2011 06:37 AM

    Hi,

    we are ahving one big problem, we upgraded our symantec manager console from 11.0.6300 to 12.1. but after upgradation the manager is upgraded, but client packahages are not showing in install packages tab. it is having only old one..so for now also mty clients are in old version only

    Kindly help me bcoz we upgraded before 15 days, but still do no how to get those packages



  • 2.  RE: Endpoint Upgradation Problem

    Broadcom Employee
    Posted Nov 03, 2011 06:53 AM

    Hi,

    You can opt any of the following option.

    AutoUpgrade--assign client packages to groups in the Manager console, either manually or by using the Upgrade Groups Wizard.

    Permit product updates in LiveUpdate Settings policy for a client group in the Manager console.

    Local installation from product disc.

    Run the Client Deployment Wizard from the Manager console. It will walk you through the creation of a client package that can be deployed via a weblink and email, remote push, or saved for later local installation or deployment using third-party tools.

    Autoupgrade is one of the easiest way to upgrade clients.   

    http://www.symantec.com/docs/TECH96789

    I hope it will help you !!


  • 3.  RE: Endpoint Upgradation Problem

    Broadcom Employee
    Posted Nov 03, 2011 06:55 AM

    you can reconfigure the SEPM, or you can import the SEP 12.1 packages.

    The way to import packages

    http://www.symantec.com/business/support/index?page=content&id=TECH122824



  • 4.  RE: Endpoint Upgradation Problem

    Posted Nov 03, 2011 07:40 AM

    All the above steps can be performed if only the packages are available in my server..but in my console itself no packages..now what to do?



  • 5.  RE: Endpoint Upgradation Problem

    Broadcom Employee
    Posted Nov 03, 2011 07:45 AM

    Hi,

    After upgrade latest packages should automatically come up.

    You can try to run upgrade.bat file, it would be under bin folder,C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\upgrade.bat

    If above suggested step didn't help, go ahead and import packages manually as suggested by Pete_4u2002.



  • 6.  RE: Endpoint Upgradation Problem

    Posted Nov 03, 2011 07:49 AM

    Now i manually imported the packages and tried istallation manually in one server..but it is not installaing..any ideas?



  • 7.  RE: Endpoint Upgradation Problem

    Broadcom Employee
    Posted Nov 03, 2011 07:54 AM

    Hi,

    SEP_Inst logs can guide us to troubleshoot issue further.

    SEP_Inst logs from the machine where SEP failed to install.



  • 8.  RE: Endpoint Upgradation Problem

    Broadcom Employee
    Posted Nov 03, 2011 08:11 AM

    does the package list out in SEPM?

    what is the error message?



  • 9.  RE: Endpoint Upgradation Problem

    Posted Nov 03, 2011 11:04 PM

    kindly provide the location of log file..ive searched and not found any where



  • 10.  RE: Endpoint Upgradation Problem

    Posted Nov 03, 2011 11:06 PM

    after imported and tried installation manually iam getting below error



  • 11.  RE: Endpoint Upgradation Problem

    Posted Nov 03, 2011 11:11 PM

    No error message and all, in install packages tab there was no newe packages..



  • 12.  RE: Endpoint Upgradation Problem

    Posted Nov 03, 2011 11:23 PM

    oh! at last i found the log file..herewith iam attaching the log file..kindly analzye and help me..

    Property(S): IPSDefs_DefsDate = 20110514.005
    Property(S): InstallScriptHash = e222a9a3b272888061de798791785fd3e8b88bdabb4cee212e579af6f3431369
    Property(S): InstallScriptPath = C:\Program Files\Symantec\Symantec Endpoint Protection\12.1.671.4971.105\Scripts\installscript.sis
    Property(S): TempInstallScriptPath = C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\32b58084-4ba1-4f95-8ea0-c99d85944089\installscript.sis
    Property(S): ProductToBeRegistered = 1
    MSI (s) (FC:E8) [17:29:41:105]: Note: 1: 1708
    MSI (s) (FC:E8) [17:29:41:105]: Product: Symantec Endpoint Protection -- Installation operation failed.

    MSI (s) (FC:E8) [17:29:41:168]: Cleaning up uninstalled install packages, if any exist
    MSI (s) (FC:E8) [17:29:41:168]: MainEngineThread is returning 1603
    MSI (s) (FC:34) [17:29:41:262]: Destroying RemoteAPI object.
    MSI (s) (FC:18) [17:29:41:308]: Custom Action Manager thread ending.
    === Logging stopped: 11/3/2011  17:29:41 ===
    MSI (c) (60:CC) [17:29:41:340]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (60:CC) [17:29:41:340]: MainEngineThread is returning 1603
    === Verbose logging stopped: 11/3/2011  17:29:41 ===



  • 13.  RE: Endpoint Upgradation Problem

    Broadcom Employee
    Posted Nov 04, 2011 12:11 AM

    the log shows install of SEP failed, however does not list all the info. You may attach whole file itself.



  • 14.  RE: Endpoint Upgradation Problem

    Posted Nov 04, 2011 12:44 AM
      |   view attached

    Please find the file

    Attachment(s)

    zip
    SEP_INST old.zip   96 KB 1 version


  • 15.  RE: Endpoint Upgradation Problem

    Broadcom Employee
    Posted Nov 04, 2011 01:06 AM

    Error 1308. Source file not found: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\Symantec\CommonAppData\Symc\Name\Version\Data\BASH\BASHOpts.bak.  Verify that the file exists and that you can access it.
    MSI (s) (FC:E8) [17:28:33:606]: Product: Symantec Endpoint Protection -- Error 1308. Source file not found: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\Symantec\CommonAppData\Symc\Name\Version\Data\BASH\BASHOpts.bak.  Verify that the file exists and that you can access it.

     

    are you using local administreator to install SEP? If not , try using that account.

    If that does not work use the cleanwips and install the software.



  • 16.  RE: Endpoint Upgradation Problem

    Posted Nov 04, 2011 01:36 AM

    yes iam using local admin account only..cleanwipe where i find the tool, is it OK to use the tool in server operating system?



  • 17.  RE: Endpoint Upgradation Problem

    Broadcom Employee
    Posted Nov 04, 2011 01:49 AM

    you can get it from Symantec Support team by opening a ticket with them. It's okay to run on server OS, however note that it will remove all the symantec products that are installed on the system.



  • 18.  RE: Endpoint Upgradation Problem

    Posted Nov 04, 2011 04:37 AM

    Running Cleanwipe on server is not recomended. I would request you to go through manuall uninstallation procedure else conatct Symantec Support.



  • 19.  RE: Endpoint Upgradation Problem

    Posted Nov 04, 2011 05:46 AM

    N0 i dont want to remove all the symantec products..it is very difficult since it is having the symantec manager also



  • 20.  RE: Endpoint Upgradation Problem

    Posted Nov 08, 2011 03:14 AM

    What is the status..still iam in the same issue..symantec is not installing



  • 21.  RE: Endpoint Upgradation Problem

    Broadcom Employee
    Posted Nov 08, 2011 10:46 AM

    Hi,

    Follow the steps to install client packages to an existing manager

    1. On the manager, open the Symantec Endpoint Protection installation CD, and go to \SEPM\Packages.
    2. Copy the package files (.dat and .info) from the CD to \Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\packages.
    3. Go to \Program Files\Symantec\Symantec Endpoint Protection Manager\, and double-click upgrade.bat.
    4. Run the Client Deployment Wizard to deploy the packages to clients.

    I believe after following these steps package should list under SEPM.

    Export Package from SEPM and deploy on clients or use Auto upgrade.

    http://www.symantec.com/docs/TECH96789



  • 22.  RE: Endpoint Upgradation Problem

    Posted Nov 08, 2011 10:18 PM

    i will check and let u know



  • 23.  RE: Endpoint Upgradation Problem

    Posted Jan 24, 2012 04:37 AM

    we logged as case with symantec technical support and the issue resolved..thanks for the help extended