Client Package install on Windows 7

Did you try with a Silent install package from SEPM?

Are you using correct version of client package?(32bit package
should use for installing in 32 bit os and 64 bit package should use in 64 bit)

Yes, I used 32 bit.
It is a silent install yes.

Paul

I'm a bit confused - you mention the download of RU5 via LiveUpdate...........
I'd build the packages from the downloaded CD files, not from anything in LU - is the thing in LU simply an update that can or will only run via LU?
I guess I'd use the CD files to update your SEM servers/console, then using that tool, build the new packages and deploy from there, ignoring anything in LU.
I'm just tossing things out here - I'd only trust for a package building what I'd downloaded through CD1 and CD2.
I'd only build a package using the console AFTER I'd updated SEM first, getting SEM up to RU5.
However.... MAYBE I've misunderstood what or how you have done this..........

whch realese version of SEP 11.0 will be support to Windows 7 & Windows Server 2008 Server

RU5 - the current version, will support Server2008 R2 and if I'm correct, Windows7 as well.
Server MMVIII R2 has some pretty drastic changes over the original release of MMVIII, so I don't believe anything prior to RU5 would work on it.
7 has some of the same things, as I recall............

RU5 is the update that support Windows 7.

The management console only had the install packages for MR4.
Then a recent update pulled down new packages which are marked as version MR5 - happened the day after Windows 7 came out or the next.

Maybe I will try a new package from the CD.

This is the log error when it rolls back:

Property(S): ProductToBeRegistered = 1
Property(S): MsiFilterRebootMode_RebootAtEndModeBefore = 1
Property(S): MSIRemoveWFPAppException_RB.17E5C180_F281_4425_9348_3E891E7F8D1F = SMC Service;C:\Program Files\Symantec\Symantec Endpoint Protection\Smc.exe;SNAC Service;C:\Program Files\Symantec\Symantec Endpoint Protection\SNAC.EXE;Symantec Email;C:\Program Files\Common Files\Symantec Shared\ccApp.exe;
Property(S): MSIRemoveWFPAppException.17E5C180_F281_4425_9348_3E891E7F8D1F = SMC Service;C:\Program Files\Symantec\Symantec Endpoint Protection\Smc.exe;SNAC Service;C:\Program Files\Symantec\Symantec Endpoint Protection\SNAC.EXE;Symantec Email;C:\Program Files\Common Files\Symantec Shared\ccApp.exe;
Property(S): MSIAddWFPAppException_RB.17E5C180_F281_4425_9348_3E891E7F8D1F = SMC Service;C:\Program Files\Symantec\Symantec Endpoint Protection\Smc.exe;SNAC Service;C:\Program Files\Symantec\Symantec Endpoint Protection\SNAC.EXE;Symantec Email;C:\Program Files\Common Files\Symantec Shared\ccApp.exe;
Property(S): MSIAddWFPAppException.17E5C180_F281_4425_9348_3E891E7F8D1F = SMC Service;C:\Program Files\Symantec\Symantec Endpoint Protection\Smc.exe;SNAC Service;C:\Program Files\Symantec\Symantec Endpoint Protection\SNAC.EXE;Symantec Email;C:\Program Files\Common Files\Symantec Shared\ccApp.exe;
MSI (s) (68:88) [16:25:26:375]: Note: 1: 1708
MSI (s) (68:88) [16:25:26:375]: Product: Symantec Endpoint Protection -- Installation operation failed.

MSI (s) (68:88) [16:25:26:375]: Windows Installer installed the product. Product Name: Symantec Endpoint Protection. Product Version: 11.0.5002.333. Product Language: 1033. Manufacturer: Symantec Corporation. Installation success or error status: 1603.

Open the SEP_INST.log and search for Return value 3 and post 5-10 lines above it.

Just to confirm have you tried the testsec utility which checks permissions?

do u have a copy of that
most of the times its because of permissions the installations would rolll back.

if you have checked permissions well we can go further with troubleshooting

Not sure if this is good or bad -

Fortunately, I already looked at the log - found that spot then tested. The bad news is the original log was overwritten.
BUT the basic information was that the live update portion failed.

I installed live update first - and that worked  - then ran the setup (the custom package) and that fianlly installed correctly.

All of which sounds good but not something I would want to do on a lot of laptops.

Given these results is there some easier fix so just the one setup can be run.
Two of the laptops were clean Windows 7 installs, so there should not be anything effecting SEP.

Any other way of addressing this?

Thanks
Paul

It is better to upgrade your manager
to RU 5(It is the only version which symantec support officially in windows 7) first and export a package from that and you can use it foe installing
in your PCs. If not possible download RU5 from https://fileconnect.symantec.com/
and add it to your SEPM >For this login to SEPM Admin --->install
packages Here you will get one option as add client install package .You can
use this option for adding RU5 to SEPM

After adding it export a package and
try. It should work.

for migrating to RU 5 you can use
below doc

http://service1.symantec.com/support/ent-security.nsf/docid/2009090313483348

For exporting package you can use
below procedure

To create the new custom install
package

In the Symantec Endpoint Protection
Manager Console, on the Admin tab, under Tasks, click Install Packages.

The current default client
installation packages appear on the right.

Under View Install Packages, click
Client Install Packages.

Under Tasks, click Export client
install package.

Browse to or create a preferred export
folder, and select it.

Select whether or not you want to
create a single ".exe" file.

Select Installation Settings and
Features.

Select Custom Install Settings from
the settings drop down.

Select Custom feature set from the
features drop down.

Select the group to which the client
will be installed. If no group has been created, select the Default group.(Or
you can make the client as unmanaged)

Select the Preferred Mode. The default
is Computer mode.

Click OK.

The new install package is created in
the location that you specified.

Given that Symantec was kind enough to push the RU5 client on to our current server install, I would think that using that package should be okay to use without going through the process of upgrading the server.

With all the reading of issues that people have with installs of SEP, try this link below.  It might work.

Be sure though to first do this...

1 - Turn off UAC
2 - Turn off  Firewall (turn back on later)
3 - Disconnect Mapped Drives
4 - Edit registry per link blow
5 - Reboot
6 - Run Setup.ext or push to local workstation and install SEP.

Here's the reg hack:

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

Nope -

The registry already had that entry and the rest had no effect on the outcome.

This is surely a bug of some sort.

We're having the same issue installing the client on Windows 2008 R2 havent tried windows 7 yet. We have the same scenerio as you. Created a 11.0.5 deployment package using 11.0.2010 manager. To get the client to finally install we have to install live update first. Have you found a solution yet?

Same issue.

Client OS: Windows 7 Pro

SEP Client Version 11.0.5002.333
SEPM Version 11.0.5002.333

Tried silent and unattended modes.
Turned off UAC & firewall.
Verified registry key.

I am tired of Symantec...

I had exactly same problem! Try installing unmanaged then copying sylink.xml file from a working client.

Check out: http://service1.symantec.com/support/ent-security....

And also https://www-secure.symantec.com/connect/forums/sep...

Installing remotely was not working, while creating install packahe with setup.exe file was giving Program Compatability Assistant error and not running. Copying sylink.xml helped.