Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

SEP 11.0.5 deployment to Windows 7

Created: 16 Mar 2010 • Updated: 21 May 2010 | 14 comments
This issue has been solved. See solution.

I want to upgrade my company's SEP from 11.0.2 to 11.0.5 however I have been unsuccessful at deploying to Windows 7 computers from my Windows Server 2003 R2. I can install an unmanaged version, but I cannot deploy a managed version. I have turned off the firewall and UAC for the Windows 7 test machine. The deployment wizard says it pushed out the installation completely but the recipient computer does not have the program installed, even after a reboot. What am I missing? It works fine for XP, so is this just a windows 7 issue?

Comments 14 CommentsJump to latest comment

Vikram Kumar-SAV to SEP's picture

Well..if you have less number of win7 clients..then you can try copying the package locall on the machine and trying the install.

Vikram Kumar

Symantec Consultant

The most helpful part of entire Symantec connect is the Search button..do use it.

P_K_'s picture

After pushing the package go to the machine  and in Run type %temp%

Look for SEP_Inst.log

search for Return value 3 and paste 5-6 lines before and after that,

If you see an error"Symantec Endpoint Protection has detected that there are pending system changes that require a reboot. Please reboot the system and return the installation"

then
In the registry, navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\
Rename  PendingFileRenameOperations registry value from the right pane. to PendingFileRenameOperations2
IPush the package again

Title: 'SEP installation fails in Windows 7 and Windows 2008 R2'
Document ID: 2010020115105548
> Web URL: http://service1.symantec.com/support/ent-security....

MCT MCSE-2012 Symantec Technical Specialist (SCTS)

jenmbq's picture

Symantec Endpoint Protection. Product Version: 11.0.5002.333. Product Language: 1033. Manufacturer: Symantec Corporation. Installation success or error status: 1603.

MSI (c) (0C:D8) [13:23:30:232]: Doing action: LaunchConditions
Action 13:23:30: LaunchConditions. Evaluating launch conditions
Action start 13:23:30: LaunchConditions.
Info 2898.For Tahoma8 textstyle, the system created a 'Tahoma' font, in 0 character set.
Info 2835.The control ErrorIcon was not found on dialog SetupError.
Symantec Endpoint Protection has detected that there are pending system changes that require a reboot.  Please reboot the system and rerun the installation.
MSI (c) (0C:D8) [13:23:34:968]: Product: Symantec Endpoint Protection -- Symantec Endpoint Protection has detected that there are pending system changes that require a reboot.  Please reboot the system and rerun the installation.

Action ended 13:23:34: LaunchConditions. Return value 3.
MSI (c) (0C:D8) [13:23:34:968]: Doing action: SetupCompleteError
Action 13:23:34: SetupCompleteError.
Action start 13:23:34: SetupCompleteError.
Info 2898.For TahomaBold10 textstyle, the system created a 'Tahoma' font, in 0 character set.
Action 13:23:34: SetupCompleteError. Dialog created
MSI (c) (0C:78) [13:23:34:984]: Note: 1: 2731 2: 0

I changed the registry file and re-deployed the installation package. It doesn't look like it is working yet.

AravindKM's picture

For installing in windows 7 you should have 11.0.5.11.0.2 is not compatible with windows 7.
In the deployment wizard assure that you are selecting RU5.
Double check your SEPM having RU5(11.0.5) client package..
Migrating to Symantec Endpoint Protection 11.0 RU5 (If you re still not migrated to RU5 use this doc for migration)

About preparing computers for remote deployment
Double check with this doc and assure that you are not missing anything..

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

Symanticus's picture

Hi All,

You're not alone, I'm also facing the same problem in installing the SEP 11 MR5 64 bit client package to all my 64 bit workstation too.

he 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 I also wondering how could this be happens ?

/* Infrastructure Support Engineer */

Symanticus's picture

I tried to look for the log file in all of 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 :-|

/* Infrastructure Support Engineer */

SEPhatesSPECTOR's picture

same issue here w/ Windows 7. We could not deploy from the migration deploy wizard, or set an Install Package. We plan on migrating to Windows 7 this summer.

jenmbq's picture

I tried all that was suggested for trying to deploy the package, but nothing worked.

So I started to just try installing from the SEP CD1, which didn't work. Then I exported a client install package to put on a network drive to use to try to install(not a single .exe file) I set the policy to export a managed client so the client automatically is added to a selected group. After I started this install and it was configuring installation files it would prompt that there are pending changes and a restart is required. I've restarted almost a half dozen times. Anything I try requests me to restart my computer. This does not sound right.

I was going to try to just replace the sylink.xml file once I could get an unmanaged package installed but if I'm not sure what my next steps should be if I can't install from the CD.

Vikram Kumar-SAV to SEP's picture

Delete this Reg key run install without rebooting.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\
PendingFileRenameOperations

and/or 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet001\Control\SessionManager\
PendingFileRenameOperations

Vikram Kumar

Symantec Consultant

The most helpful part of entire Symantec connect is the Search button..do use it.

jenmbq's picture

I found a registry key under the CurrentControlSet001 and deleted it. There wasn't one inside CurrentControlSet. But before restarting anything, I tried to install. It got much further than it ever has but at one point the progress bar started to go backwards. Then it closed without any prompt and the program didn not successfully install.

EDIT: I installed Live Update first, then edited the registry and was able to SUCCESSFULLY install an unmanaged version on the Windows 7 computer.

Vikram Kumar-SAV to SEP's picture

Yes..actually the reason for failure was liveupdate but once it got stuck with pending rename operation it wont allow it unless they key is deleted.

Vikram Kumar

Symantec Consultant

The most helpful part of entire Symantec connect is the Search button..do use it.

Symanticus's picture

Yes, Vikram has the answer it is tested by me for all 64 bit workstation and server OS that is the most common problem.

Delete that registry key value (empty it). and then perform the install again :-)

Cheers,

Albert

/* Infrastructure Support Engineer */

jenmbq's picture

This process to install SEP 11.0.5 on a windows 7 computer is pretty tedious. After attempting everything in my knowledge to install the program for a managed computer, I had to follow a workaround plan.

  1. Export a Client Package (not a single .exe file) for an unmanaged client.
  2. Install Live Updates the LUSetup.exe in that exported folder
  3. Restart
  4. Delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet001\Control\Session Manager\PendingFileRenameOperations. (If that file was inside CurrentControlSet I would have to delete that one too)
  5. Run setup.exe from that exported folder
  6. Restart
  7. Find the C:\program files\symantec\SEP\sylink.xml file from a working managed client to copy into the computer’s C:\program files\symantec\SEP folder.
  8. Watch it all work   :)   (And possibly another restart)

This seems like a lot of work for a program that supports the new operating system. But, at least it works for the new operating system. I’m thankful for that. I look forward to a hotfix that I would expect to come out soon though if everyone is having this issue in upgrading.

SOLUTION
P_K_'s picture

Hi jen, The steps that you are doing just needs to be done olny if the Install pacakge version in SEPM is 11.0.5000  if the version is 11.0.5002.333 then you don't need to follow the steps Just create the package and push it.

MCT MCSE-2012 Symantec Technical Specialist (SCTS)