Re: Symantec Client Security
Whats msi ? Mabye disconnect from the internet till you get it sorted . Uninstall old firewall thru add remove , then install the new one. Msi is a mobo weird eh ?
Re: Symantec Client Security
Quote:
Originally Posted by peat moss
Whats msi ? Mabye disconnect from the internet till you get it sorted . Uninstall old firewall thru add remove , then install the new one. Msi is a mobo weird eh ?
MSI is the Microsoft Instal Wizard. I have found a way to fix this littel glitch...I tell ya that google guy is great :-P. Thanks anyways
Re: Symantec Client Security
Right. Maybe you could mention what solved the problem?
In any case... You should also remove the AntiVirus 2004 which is part of Internet Security 2004. Not just the Firewall.
And as for the setup... Just reinsert the CD. It has an Autorun.
Re: Symantec Client Security
I'm left to guess. Fn post the solution, jeez. Windows Install Clean Up, is what helped me clear up an .msi problem.
Re: Symantec Client Security
Quote:
Originally Posted by Catracho
MSI is the Microsoft Instal Wizard. I have found a way to fix this littel glitch...I tell ya that google guy is great :-P. Thanks anyways
.msi-something is, if I'm not mistaken, a file format used by symantech security products (like Norton).
[EDit: Had a look around too, and in this case it was to do with the windows installer, according to many.]
They use it instead of .exe:s or something, so in this case I think it was trying to start up the firewall anyway, but couldn't.
Norton has a tendency to dig in, so take a look at your startup entries, see if it's still there, and next time, try unloading the scanner and firewall entirely before uninstalling.
Also, load up your task manager after you've uninstalled everything (through add/remove programs, like someone said), and see if there are still norton-related processes running, if so, you may need to delete something from the registry and remove stuff by hand.
You need to do all of this before installing the symantech client security thing, since it's going to use the same kind of processes.
EDitII: Symantech does use .instmsi files, for installations, .nsi-files, in norton, instead of shortcuts (I think), and .msi-files (instead of .exe, I think, again).
I found 'em in the symantech corp installer, and in the start menu-folder for norton, on someone else's computer right now.
But in this case it's the MS installer apparently.
Bit confusing though.
Re: Symantec Client Security
MSI - MicroSoft Installer, now known as Windows Installer.
If you know how to do it, you can often uninstall software by directly manipulating the msi scripts. But for Symantec Client Security the scripts are written in such a way that IT DOESN'T WORK. You can even get to the situation where parts of your system are locked out because half of the software is still working, and you've uninstalled the configuration parts.
If you want to uninstall any of the Symantec products and your installation is corrupt, the only way to do it is to reinstall first.
Re: Symantec Client Security
I'm glad this came up, 'cos I'm going to have to uninstall norton from someone else's machine soon, and like I edited in above, it is a tad confusing.
Re: Symantec Client Security
Quote:
Originally Posted by SnnY
I'm glad this came up, 'cos I'm going to have to uninstall norton from someone else's machine soon, and like I edited in above, it is a tad confusing.
Symantec also has cleaner tools to remove stubborn leftovers as well, I had to do this back when I tried to install 2003 0ver 2002. Now I only mess with mine after a re-format :shifty:
Re: Symantec Client Security
Why not just go through the extra efforts of actually un-installing the entire suite (NIS2004) through whichever method you choose (add/remove programs applet or installation CD) then running an application such as RegSeeker to remove registry and other various entries/strings you nolonger need? After which, cleaning out your C:\Program Files\Common Files\Symantec and related systems folders in Documents and Settings would also be of great help. Lastly- running a cleaner application such as CCleaner to clear out any residule unwanted files is certain to ensure that SCS v3.0 will install effortlessly.
Of course, not that I have done this already myself. :whistling Personally, IMO, if you are going to undertake such a step with any high-end Symantec product, do it right. :)