Video Screencast Help
Search Video Help Close Back
to help

Installer package sent to the client but SEP didn't install

Created: 15 Jan 2013 | 17 comments
kintachi's picture
0 0 Votes
Login to vote

HI,

    As I deploy SEP on the clients I used remote push deployment. I send the installer package and it was sent but SEP didn't install on the clients.

Comments 17 CommentsJump to latest comment

Brian81's picture

Can you post SEP_INST.log? It should be located in %temp% directory

0
Login to vote
SebastianZ's picture

Is this a clean installation or does the target machine has already some previous SEP version?

0
Login to vote
kintachi's picture

Hi,

   There are no SEP or AV installed on the clients.

0
Login to vote
kintachi's picture

Hi Brian,

    As of now Im not on the clients side, I will attached the said log file as soon as I got it. Thanks.

0
Login to vote
Brian81's picture

Sounds good.

As a side note, you can check the best practices guide as well:

Best practices for upgrading to Symantec Endpoint Protection 12.1.2

Article:TECH163700  |  Created: 2011-06-30  |  Updated: 2013-01-02  |  Article URL http://www.symantec.com/docs/TECH163700

 

0
Login to vote
Ashish-Sharma's picture

HI,

How many system not accept SEP client package ?

 

Best practices for upgrading to Symantec Endpoint Protection 12.1.2

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

Steps to prepare computers to install Symantec Endpoint Protection 12.1 client

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

Thanks In Advance

Ashish Sharma

SEPM Knowledgebase Documents  

 

0
Login to vote
Ambesh_444's picture

Hello,

 

Please find below checklist for installing SEP remotely.

  •  Every OS - Windows Firewall must be Off
  • windows 7 and Vista - User Account control(UAC) must be off
  • Every OS - C$ and Admin $ must be shared
  • Every OS - Port 139 and 445 must be open
  • Windows XP - disable simple file sharing
  • Vista, Win 7 and 2008 - Disable File sharing Wizard
■ For legacy communications, open UDP port 2967 on all computers.
■ General communication: TCP 8014 (HTTP)/TCP 443 (HTTPS) for management servers. These are the default ports, and may be customized. See Symantec Endpoint Protection 12.1: How to Change the ports used for communication between the Manager and clients.
 

 

Artical for Remote deployment

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

 

Disable User Account Control (UAC) the Easy Way on Win 7 or Vista
http://www.howtogeek.com/howto/windows-vista/disable-user-account-control-uac-the-easy-way-on-windows-vista/

 

Disable File sharing Wizard
http://www.technipages.com/win7-vista-disable-file-sharing-wizard.html

 

Thank& Regards,

Ambesh

Please mark your thread as 'SOLVED' with the answer that helps you.

0
Login to vote
SebastianZ's picture

As you mentioned package was sent but did not install, can you check if local installation of that package manually works at all or fails as well?

0
Login to vote
kintachi's picture

Hi,

    All local deployment was successful. It always fails in the push deployment. I turned off the windows firewall, UAC, I also disabled file sharing wizard.

0
Login to vote
Ashish-Sharma's picture

Hi,

Do you have open below ports for push deployment ?

Ports used for client software deployment with the Push Deployment Wizard

Client computers

Symantec Endpoint Protection Manager

TCP 139 and 445

Ephemeral TCP ports

Ephemeral TCP ports

TCP 139 and 445

UDP 137, 138

UDP 137, 138

Prepare computers for remote deployment and management

Modify firewall settings to allow communication between Symantec Endpoint Protection Small Business Edition components:
■ Push deployment ports, used on management servers and clients: TCP 139 and 445, UDP 137 and 138, and TCP ephemeral ports.
■ For legacy communications, open UDP port 2967 on all computers.
■ General communication: TCP 8014 (HTTP)/TCP 443 (HTTPS) for management servers. These are the default ports, and may be customized. See Symantec Endpoint Protection 12.1: How to Change the ports used for communication between the Manager and clients.

Reference

http://www.symantec.com/business/support/index?pag...

Thanks In Advance

Ashish Sharma

SEPM Knowledgebase Documents  

 

0
Login to vote
SebastianZ's picture

I think we will have to refer to the install log at the end - if the package goes through but fails to install on the client end - it will be reported in the log.

0
Login to vote
kintachi's picture

Hi Sebastianz,

    Where is the destination folder of the logs?

0
Login to vote
Ashish-Sharma's picture

Hi,

You can find %temp% SEP_INST.log.

Thanks In Advance

Ashish Sharma

SEPM Knowledgebase Documents  

 

0
Login to vote
Ambesh_444's picture

Hi,

Have u open required port.?

 

Thank& Regards,

Ambesh

Please mark your thread as 'SOLVED' with the answer that helps you.

0
Login to vote
KalpeshParmar's picture

Check the disk space.

0
Login to vote
kintachi's picture

Hi All,

    For the status of the push installation, it was successful. The installer package was sent and installed on the client, the problem is the clients are not reporting to the manager after reboot.

0
Login to vote
SebastianZ's picture

Can you verify in the client GUI if the server status is reported as connected? Please check if you can telnet from the client machine over port 8014 to the SEPM Server.

0
Login to vote