Cannot Install Endpoint Protection 11.0.5 on a Windows 7 client
I am having difficulty installing a managed client on a windows 7 enterprise client. (both push deployment and direct install from mapped drive)
The log shows the following:
-- DECABI_LOGGING -- Enter LURegisterDecomposerABI()
-- DECABI_LOGGING -- GetDecomposerABIProperties Registry created.
-- DECABI_LOGGING -- GetDecABIDirectory() -- failed to get Installed Apps key from registry.
-- DECABI_LOGGING -- Decomposer ABI DLL version is: not installed
-- DECABI_LOGGING -- Could not get Decomposer ABI version from LiveUpdate. (HRESULT=-2147221164)
-- DECABI_LOGGING -- Decomposer ABI version registered with LiveUpdate is: not installed
-- DECABI_LOGGING -- Decomposer ABI sequence number registered with LiveUpdate is: not installed
-- DECABI_LOGGING -- For rollback using Decomposer ABI custom action property: sizeof= 130 not installed:not installed
-- DECABI_LOGGING -- LiveUpdate registration failed. (HRESULT=-2147221164)
CustomAction LU_Register_Decomposer_ABI.611D9A69_39FC_4998_998E_1ECADF28A979 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (F8:24) [16:23:13:257]: User policy value 'DisableRollback' is 0
MSI (s) (F8:24) [16:23:13:257]: Machine policy value 'DisableRollback' is 0
Action ended 16:23:13: InstallFinalize. Return value 3.
MSI (s) (F8:24) [16:23:13:270]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=996442833,LangId=1033,Platform=589824,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (F8:24) [16:23:13:270]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (F8:24) [16:23:13:270]: Executing op: DialogInfo(Type=1,Argument=Symantec Endpoint Protection)
MSI (s) (F8:24) [16:23:13:271]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (F8:24) [16:23:13:271]: Executing op: RegisterBackupFile(File=C:\Config.Msi\2821c8.rbf)
MSI (s) (F8:24) [16:23:13:272]: Executing op: ActionStart(Name=LU_Register_Decomposer_ABI.611D9A69_39FC_4998_998E_1ECADF28A979,,)
MSI (s) (F8:24) [16:23:13:272]: Executing op: ProductInfo(ProductKey={530992D4-DDBA-4F68-8B0D-FF50AC57531B},ProductName=Symantec Endpoint Protection,PackageName=Symantec AntiVirus
Comments
Hi
You can follow this document , if its professional its not supported first install LU and then install SEP
https://www-secure.symantec.com/connect/forums/windows-7-profession-1105-wont-install-rolls-back
https://www-secure.symantec.com/connect/forums/endpoint-wont-install-fresh-install-windows-7
Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq
What do you mean - SEP RU5 is
What do you mean - SEP RU5 is not support on Windows 7??
Ya know, this is getting a bit silly isn't it?
Seems to me that there's a huge issue with all thes folks coming in and stating they can't push SEP to Windows 7.
Network admins and others don't have time to hold hands on a CENTRALLY MANAGED AND DEPLOYED software. Sort of defeats the purpose, doesn't it? I mean, really - the fix is to start over and install each little piece by itself - to 350 computers?
We'll be putting Windows 7 out there coming up - and it won't be pretty if we have to deal with this on a PC by PC install basis for hundreds of computers all over Iowa........
I'd say - stop with the band-aids and fix it..........fix what's obviously wrong with the install processes for SEP packages. Let's not rely on the consumer to have to jump hoops.
Was this not seen in beta testing? I'm seriously quite confused - I've never seen so many complaints of the exact same issue in such a short time except in the cases of bad definitions being rolled out.................
My sites - http://theamcpages.com & http://antique-engines.com
Toy:
Shadow:
Installing Live Update 3.5
Hi,
Installing Live Update 3.5 and Installing the RU5 client completes the installation.
However, doing this process on multiple instances ends up in BIG task. :(
Try by installing in other
Try by installing in other computers in normal way and see whether it is giving any problem...
Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind
Windows 7 *is* a supported OS
Not sure where Rafeeq got the information that Windows 7 isn't a supported OS with RU 5, but I assure everyone it is.
We do QA test our software...quite extensively, as anyone who's been around Symantec software, and seen release dates pushed back multiple times, can attest to. However, it is flatly impossible to test every configuration. We try to test against as many configuration scenarios as we can.
Hi Chris, so what is the
Hi Chris,
so what is the solution now, it make no sense how extensively you folks doing testing but bottom line is SEP 11.0 RU5 "FAILS to install on Windows 7", we need and solution period.
Thank you.
VLE
Cant test every configuration, not even a fresh install?
I realize that every config can't be tested, but this isn't even working on a fresh install of Windows 7. I would have hoped that Symantec would have tested a fresh load to form a baseline, but from what I see this is not the case.
Furthermore then entire reason we purchased SEPM was to have a single management interface to deploy and configure Endpoint Protection. The solution of "install Live Update on every workstations" is unacceptable and Symantec should not even be offering this as a solution. If I have to personally visit every machine I might as well install a desktop based solution, perhaps provided by a company that places a little more importance on customer service.
I wasn't able to push an
I wasn't able to push an install of SEP 11.0.5 to my Windows 7 laptop (upgrade from Vista, not a fresh install), however what did work for me was exporting an install package from SEPM (not as a .EXE file but all the files in a tree/set of folders),then copying this package to my laptop, and running the install manually.
I dunno, I wasn't able to get
I dunno, I wasn't able to get into the beta.......... but this sure seems like a BIG one to have missed, sorry! It just seems that install failures with LU involved apparently are not new, as we were facing them here with MR4 when I was working with support attempting to get a reinstall on our file server here. It failed constantly and ended up being a LU failure. We had to remove LUCHECK from the package to make it go. That was MR4. Now I see all these with RU5, same symptoms, all these in the forum, and wonder how many folks don't post it here, or call support instead or find other solutions. You can bet, as a support person, what you see reported is typically only a very small percent of what really exists, but folks either figure it out, or call, or get it solved in other generic IT forums.
It's starting to worry me - however, since I saw that same issue here, with MR4, and we'll be hitting Windows 7 in a few weeks...... and there's no way we can manually install like that.
I guess I'll have to do a few test machines and see what happens here................ I hope it's being worked on, though - as I can assume some folks will see the issues just attempting to install to hundreds of computers and be a bit aprehensive. It's a bad taste right out of the box.....
(having done beta testing for roughly a decade with Symantec, I also know that there were, at least a few years back, intense deadlines in the testing - we used to get builds in the mail early in the week, and read the documents and find we had to post results that same week............as the next build was coming the following week. I've not done beta testing for a few years, however, so maybe those VERY tough deadlines imposed on beta testers have been relaxed a bit. But back then, we had to really dedicate a lot of time on it, and often were not able to fully get through the test scripts if we also had full time jobs. I found most of my bugs by not following the scripts, however, as most end-users won't follow the directions anyway. So you have to think like a real customer, throw away the documents, install over old builds and hope for the best. LOL )
I saw that "unsupported OS" comment and it really bothered me! Wait, ALL of Windows 7, all versions, are supposedly supported...... but wait, in support, it's said not all are?
My sites - http://theamcpages.com & http://antique-engines.com
Toy:
Shadow:
This last resort worked for me !!!
In the registry,
Find
HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\AppData
value=%APPDATA%
and change it to
HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\AppData
value=%USERPROFILE%\AppData\Roaming
Install SEP client again.
http://service1.symantec.com/support/ent-security....
Registry
In sad news, my client already had the adjusted registry as above.
The SEP marks as successfully deployed in my Console, arrives and attempts to uninstall in the client system and then just as it is about to finish, it reverses and dissappears.
The next time I search for unmanaged computers via the IP, theclient is listed again.
What's going on Symantec????
walks, talks like ...
If it smells like and squishes underfoot like a turd, I don't care what you call it.
thank you anoobi, that
thank you anoobi,
that fixed the installation for me.been driving people nuts with the isntallation not working.
Would you like to reply?
Login or Register to post your comment.