Solved

symantec endpoint on sbs 2008 reinstall fails

Posted on 2009-07-02
14
871 Views
Last Modified: 2013-12-09
I have a brand new SBS 2008 server that was once set up correctly with SEP 11 (MR4)  It was having issues with shares disappearing, clients being disabled and not registering properly with the server, etc so i decided to remove/reinstall the program on the server.  The uninstall had issues but I finally got it removed by calling Symantec for the SEP 11 removal tool.  I am now running into problems when I try to re-install the console.  It appears that there are registry permissions preventing me from continuing and the installation fails.  I have tried installing as the domain administrator as well as another account with admin privileges.  I have attached the error.  Once I get the error it rolls back and fails.  Anyone ran into this yet?
error.jpg
0
Comment
Question by:univision-computers
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 7
  • 4
14 Comments
 
LVL 20

Assisted Solution

by:jimmymcp02
jimmymcp02 earned 250 total points
ID: 24835288
did you use the latest cleanwipe?
 
http://www.experts-exchange.com/Software/Internet_Email/Anti-Virus/Symantec/Q_24355519.html
 
If not there were some issues with the previous version that left registry info. also the previous version did fully support 64bit OS for win2k8 and vista 64
0
 
LVL 6

Author Comment

by:univision-computers
ID: 24850977
Yes, I called Symantec and got the cleanwipe tool.  It removed the program but I was unable to re-install it due to the registry error above.  And yes, it was the latest version of the software so it should have been 64 bit compatible....I think... it was version 11.0.4000 MR4 (Since that original install they have released maintenance patch 2.....version 11.0.4000 MR4 MP2 which I have downloaded and will try to install)

I called Symantec again and they reviewed the logs to determine that the error was due to a failed removal of the unmanaged client on the server.  Apparently when you install from the autorun menu it defaults to the 32 bit and is not smart enough to know that you are using a 64 bit machine.  Also instead of installing the managed client on the server it installs the unmanaged...

The tech directed me to the manual removal method:

 Title: 'How to uninstall Symantec Antivirus, Symantec Endpoint Protection,and Symantec Endpoint Protection Manager, and what to do if that fails'  
0
 
LVL 20

Expert Comment

by:jimmymcp02
ID: 24856269
i believe thats and issue with MR4.... symantec tries to install a 32bit on a 64 bit. that issue is fixed on MP1 or MP2
0
Online Training Solution

Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action. Forget about retraining and skyrocket knowledge retention rates.

 
LVL 6

Author Comment

by:univision-computers
ID: 24869634
I've got MP2 but it still appears to install into the (x86) directory so it may or may not be fixed.  I am thinking of calling Symantec again to see for sure.  I don't want to go through the same thing again...
0
 
LVL 20

Expert Comment

by:jimmymcp02
ID: 24879382
Did you try installing by browsing to the folder instead of using the autorun feature?
 
 
 
0
 
LVL 6

Author Comment

by:univision-computers
ID: 24880318
Symantec called me back today and the technician confirmed that it is still a 32-bit management console even in the MR4 MP2 version.  There is no 64 bit server console at this point.  However, once the console is installed and you make the client install packages you can build a x64 installer that makes the server a 64 bit managed client.  I will try the install again in a few days and post on the results.
0
 
LVL 6

Author Comment

by:univision-computers
ID: 25016261
To give an update, the admin console installed successfully on the server, but not the client.  Symantec reviewed the logs after the client install failed again and they found that the DCOM settings had been changed or restricted in some way.  They suggested this article to fix it:
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2002103013521548?Open&seg=ent

I will post back and report if that works or not.
0
 
LVL 6

Author Comment

by:univision-computers
ID: 25118393
That solution did not fix it.  I will try to get Symantec on the phone and see if they will fix it for me.  I am out of ideas :(
0
 
LVL 20

Expert Comment

by:jimmymcp02
ID: 25118656
wow.... this is an interesting issue. keep us posted...
0
 
LVL 6

Accepted Solution

by:
univision-computers earned 0 total points
ID: 25227067
OK so I am excited.  I found that  it was not just Symantec having this issue but also Windows updates and other programs as well.  It appears to be a registry issue dealing with the Windows Installer service.  It normally appears as an error like the one above - Error:  Could not open Key "Unknown\Components\_______" and fails with any number of different keys.  Apparently Microsoft has a fix for it in Server 2008, Vista, XP, Server 2003 and perhaps others.  Here is the link:  http://support.microsoft.com/Default.aspx?id=313222

It worked for an Exchange update and I am now rebooting, so next I will try SEP and see how it goes!
0
 
LVL 6

Author Comment

by:univision-computers
ID: 25235341
SEP installed successfully.  It was definitely due to the Windows Installer issue.  Hope this helps someone else, it has been a struggle for me!
0

Featured Post

Salesforce Made Easy to Use

On-screen guidance at the moment of need enables you & your employees to focus on the core, you can now boost your adoption rates swiftly and simply with one easy tool.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

While rebooting windows server 2003 server , it's showing "active directory rebuilding indices please wait" at startup. It took a little while for this process to complete and once we logged on not all the services were started so another reboot is …
A project that enables an administrator to perform actions within a user session context not just at the time of login but any time later on day(s) or week(s) later.
As developers, we are not limited to the functions provided by the VBA language. In addition, we can call the functions that are part of the Windows operating system. These functions are part of the Windows API (Application Programming Interface). U…
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question