Endpoint Protection

 View Only
  • 1.  Problem in installing SEP 11 MR 5 64 bit client on Vista and 7 x64

    Posted Mar 17, 2010 01:42 AM


    Hi All,

    I'm having problem in installing the SEP 11 MR5 64 bit client package on my 64 bit workstation, from my SEP Mgr. console it was successfully "pushed" and i can see the green dot pf "SUCCESSFULL" deployment status, however in the client desktop, i cannot see any SEP on the tray icon.

    but instead the installation left one directory C:\TEMP\Clt-Inst in all of my 64 bit workstation, for all of the 32 bit workstations (XP, Vista and 7) everything is working fine.

    no firewall is enabled at the moment in all of my workstation, so can anyone help me here please ?

    Thanks.


  • 2.  RE: Problem in installing SEP 11 MR 5 64 bit client on Vista and 7 x64

    Posted Mar 17, 2010 01:55 AM
    when you are pushing the package make sure you are pushing the 64 bit package from the drop down menu,
    the install file can be found in temp directory
    start-run-%temp%
    sep_inst.log
    look for return value 3, if it shows pending file rename operations follow this document , reboot, install liveupdate and then run the install 


    http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007121609023348


  • 3.  RE: Problem in installing SEP 11 MR 5 64 bit client on Vista and 7 x64
    Best Answer



  • 4.  RE: Problem in installing SEP 11 MR 5 64 bit client on Vista and 7 x64

    Posted Mar 17, 2010 02:08 AM
    Hi All,

    Thanks for replying to my thread, however whenI tried to look for the log file in all of my 64 bit client's my hard disk sub dirs. it returns 0 or nothing ? and now in the C:\TEMP\Clt-Inst only contains 1 file vpremote.exe instead of the full unzipped 64 bit client package :-|

    @Aravind: The article that you sent to me, is it still valid for Vista 64 bit and Windows 7 client install ?
     




  • 5.  RE: Problem in installing SEP 11 MR 5 64 bit client on Vista and 7 x64

    Posted Mar 17, 2010 02:14 AM
    can u export the package and install it locally ?lets see what error message it gives.
    did u find sep_inst.log file? it might be in windows dirctory 


  • 6.  RE: Problem in installing SEP 11 MR 5 64 bit client on Vista and 7 x64

    Posted Mar 17, 2010 02:27 AM
    # Open the Windows Registry editor (regedit.exe) browse to the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
    # Verify the following Reg Multi String value PendingFileRenameOperations exists under this key.
    Note: If you do not find the PendingFileRenameOperations value in the location above, this error message can be generated if there are pending changes in:
    HKEY_LOCAL_MACHINE\SYSTEM\ControlSetXXX\Control\SessionManager\PendingFileRenameOperations

    # If HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired exists, right-click on the RebootRequired registry key and choose Export.
    # Provide a different file name than in step 4 for the exported registry key and click Save
    # Delete RebootRequired sub-key

    (delete the value after double clicking on the "PendingFileRenameOperations" string value), no need to restart the client just perform another push install from the server.

    but how to automate this process in more than 10 clients ? sounds ridiculous if i have to send email for every affected users or even call them one by one to use regedit ?

    Thanks for your reply.


  • 7.  RE: Problem in installing SEP 11 MR 5 64 bit client on Vista and 7 x64

    Posted Mar 17, 2010 06:49 AM
    Yes you can use it for vista also.Sine it is 64 bit thre may be a small chage in the regisry path..

    Try by first installing liveupdate and install SEPM.If not helps pls paste/attach sep_inst.log here..


  • 8.  RE: Problem in installing SEP 11 MR 5 64 bit client on Vista and 7 x64

    Posted Mar 17, 2010 06:33 PM
    thanks mate,

    http://service1.symantec.com/support/ent-security.nsf/docid/2010020115105548?Open&seg=ent

    is the one that finally reolves my problem, eventhough it is for Win 7 and 2008R2 but it also applies to 64 bit client.