NOD32?

I will google it and give it a try.

@Jito463
But the NAV versions are far from what we want - the SAV is better since NAV is more heavy on the system.


@smc1979
Wow, Cool!
Yet another Symantec/Norton bug. I love them.

@RogueSpear
Yup, me too - always would recommend Symantec products. The fact is that Symantec still is the best in business, in their niche - no other product has as much flexibility, capability (or suitability to system administration, as indeed we have been seeing). And it does its core job well - As much as our dear anti-Symantec flamers try to make the scene foggy (by talking of virus detection, blocking, etc.) - it still detects viruses as perfectly as I'd like to, and I love its script-blocking abilities and IM protection. But in the last couple of years, there's been one-slip-too-many. Unless you're dealing with the absolute latest hardware, there's just no way the Norton 2004/2005 series will sit lightly on your machine.

Personally, I've stayed with NAV2002 for my machine at home. And at the time this thread was started, there was a need for some SAV deployment - so thought I might as well have the latest version deployed since anyway SAV series doesn't suck-out as much resources as Norton 2k4/2k5.

I still support Symantec. But since some time, I've been checking out other options. And I've almost totally moved over to ZoneLabs. See the latest ZoneAlarm SecuritySuite - it has firewall/antivirus/IM-protection/data-protection - and a good interface to control all of it properly. Its perfectly suited to the company gateway (to block viruses at source itself, without letting it spread to client-PCs). And you don't need to worry about computer-illiterate employees since just one good admin is enough to manage it at the central server. I just can't stop raving about the huge time-dividend (in terms of not much work needed to maintain it) I got ever since I replaced 30 troublesome NAV clients, with one ZASS at the gateway. (and yeah, just as Symantec, there are lot of anti-ZoneAlarm people too, I prefer to ignore!)

Well for now I would LIKE to stay with SAV 9.0, I also have 8 but havent used it in some time.

I have done the following test on SAV 9 to try and fix the problem with no luck.

I first completely disabled SAV, disabled all the services and startup items.
No luck with the page file.

I then did a scan for any file with the word pagefile in it. Lots of files there but no leads.

I was looking through the files of the SAV setup. of course a ton of Dlls.

I am going to start the long task of deleteing each dll 1 by 1 from the system and see if they are causeing the problem.

Right now from what I can tell is the SAV install is doing something since SAV is completely disabled and the I still have the pagefile error.

God I love a Challenge! LOL

SAV 8.1 installed with /qn doesn't have that problem. My page file is set to 200 mb. I didn't like SAV 9.x much, and still use the older version. The page file bug is a pretty major one...

What theme is it on your screenshot, if you don't mind me asking? Reply in PM - ok.

@smc1979
You have the 9.0.0.1400 version, right?
Why not try moving to v9.0.1.1100 - which is the newest. Your bug might have got fixed.

Cause I cant get it to update

OK I tested SAV 9.0.0.338, 9.0.0.1400, 9.0.1.1000, and finally 9.0.1.1100


I have the page file problem on EVERY single one. and of course for each one once you uninstall and reboot the problem is fixed. Anyone know how to get ahold of symantec to bring this to there attention.

just help me, the noob, out - what does this page file problem REALLY do to the system, and why is it so serious?

Basicly when SAV is installed you can no longer resize the pagefile on C:\.

Now if you have another drive to pagefile on or you have over a gig of ram then this wont be problem for you since you dont need to mess with the pagefile. (if you lots of ram the page file is barley touched)

But on systems with low ram the pagefile is used alot and the bigger you make it (to a point) the better. But if you cant rezie it or put it on a different drived your screwed.

To some this isnt no big deal, to admins and techs like me performance means everything and the pagefile plays a role in it.

So you mess with my performance then it is a problem :-D

Did any of you guys report this pagefile issue to Symantec? I'm at the 90% mark w/ my unattended (working on the S's now obviously) and would like to know if they have acknowledged the issue or to just go w/ 8 atm.

I've already spent such an obscene amount of time with their tech support for the issue that I described earlier, I would hate to spend that kind of time again only to be told "we're working on it." Would rather go through a root canal.

I'm curious if anyone out there has seen a change log for SCS 2.01 or for SAV 9.01. Try as I do, I can't find any information. I suppose that's why I blow $2,500 a year for "Gold Support."

not to sidetrack the discussion, because I'd love to see a resolution to the pagefile problem, but I'd love to get a link to "nonav". I didn't know that it even existed until Pesko mentioned it, and it'd obviously make my testing much faster/better... thanks!

-joe

It appears that SAV 9.02 is out. More testing..

hhmm the update isnt on nortons ftp or website.

How did you hear about the update and where can I get it to test it?

Actually I got it from a co-worker who also has several licensed clients for this product. I was browsing through the documentation and it does appear legit. I asked about a corresponding version 2.02 for SCS but no luck there.

You can get a clue from my post:
$oem$\Prog$\Symantec\Liveupdate\Settings.Merge.LiveUpdate

If you drop this file in the symantec directory, it merges with Settings.LiveUpdate at first run.

well, after much searching, I finally found nonav... to anybody that wants to find it, I'd suggest the following google search term: "NONAV Symantec AntiVirus Uninstall utility"

I normally would not post links to software on this board, but as this is only an uninstall tool, I don't think that it should be a problem. Also, anybody with the common sense to do google searches can find it.

Thanks to Pesko and everybody else for letting me know it's out there; this will save me tons of time testing!!

-joe

If still wondering, which virus def does Liveupdate likes, try this:
http://liveupdate.symantec.com/encfull2.x86 (5 Mb)
Despite the .x86 extension is a .zip file. Rename and use the contents as usual.
It's only updated once a month, first wednesday >= 15 every month.
When Liveupdate run, it only download a small piece:
http://liveupdate.symantec.com/enccurd2.x86 (~300 Kb)
This other is a patch for the first one, but I don't know how Liveupdate apply it.

RogueSpear

Can you help me locate the update for 9.02 I would love to test it and see if the pagefile is fixed.

I find it odd that the 9.01 is still the latest download on Symantec's site. I'm really not sure of the origins of my copy to be honest. But with the amount of scratch I lay out for a Gold Support Contract, which as far as I can tell is only useful for free upgrades, I don't feel very guilty about having it. If I can locate the source I'll definately post it here. I simply have not had the time to test this, but I plan on it within 24 hours.

By the way, I would not count on this problem being fixed. I was browsing through Symantec's message boards where someone (you?) asked about this very problem with all builds of version 9 and the tech support wrote back that this problem was first surfaced with the version 8 series but was resolved with version 9 and that the guy should upgrade. It seems that their reading comprehension sucks since this guy clearly stated he was using version 9. And the other thing that bothers me to no end is that as far as I am concerned this is HUGE freakin bug that demonstrates some pretty Mickey Mouse software development. Now depending on how large your enterprise is, you could be spending from $1,000 to $50,000 easy to upgrade to V9. I am QUICKLY losing faith in Symantec (are you people reading this?!?).

I just dont know what to say.

If symantec (it wasnt me on the msg board) cant cleary read then they are of course out sourcing to someone who cant read english right or used a translater, cause how the hell can you get the number 8 and 9 mixed up!

Can you point me to this fourm where this was posted? I will post so much of my findings on this they will cry LOL

http://www.symantec.com/techsupp/enterpris..._ts_online.html

When you get to the page, there is a drop down list to chose which forum. When you go to a forum you will notice a search box towards the top. I found the page file issue by searching for "pagefile."

Give 'em hell..

EDIT:

http://servicenews.symantec.com/cgi-bin/di...client_security

Here is the post I referenced earlier.

Ok here is what I posted to them, lets hope it does some good.

nice letter!

maybe it'll help... (wishful thinkng?)

Installing a Server from AIP just created, give me errors about missing files.
This only work for Clients instalations or I did somethig wrong?
I resolved copying from original .cab the folowing mising files, one by one, pressing Retry every time

Maybe the list is not complete, because was did from memory.

@Nilfred When you setup an AIP for some reason the process does not copy over some files. Look for alerules.exe and INSTOPTS.DAT from the original source and copy them to the root of your AIP.

Well, Liveupdate runs... And yes! there is a damm 9 Mb update for Server:
http://liveupdate.symantecliveupdate.com/ennluxdb.x86
This is a .zip file and contanis 3 files:The last one is copied over here:

This is a recommended virus definition update method by Symantec, so I recommend it too

Well its been 5 days now since I made that post to symantec about the pagefile problem and still no reply, yet the other posts on there they replyed within 2 days or less. hhhmmm wonder why they havent responded to mine?

Another fellow posted the same issue yesterday. No answer there either.

well I just posted the same msg again to a new topic, I will get there attention one way or another until this is fixed. I cant belive how dumb they are all they say to others is "its not our fault". And dont even look into it.

Man I hate that!

Well I got ahold of build 9.0.2.1000 and the pagefile problem still hasnt been fixed.
I had to get this build off another tech (not sure why it isnt on there site)

And of course still no reply to my comments on the page file from symantec
I even sent them an email!!

It is just so hard to think that symantec is acting like this. You would think they wouldnt.

This is VERY dissapointing.

I got a hold of the change log. Goes from V9.0.0.1300 to current.

Well belive it or not I got the pagefile problem fixed, but I dont know if the fix is wise to use.

Basicly it is still a bug in SAV cause the pagefile works fine if it is on a different drive other than C:.

Now when you go to config the auto protect and tell it to exclude certain files the pagefile isnt listed. So the only option was to tell it to ignore all files with the extension sys so dont scan any files *.sys.

I rebooted and it my pagefile was fixed. By the way this problem is even on XP sp1.

Now I am not sure or not but is it wise to ingore sys files?
since I have now seen what is causing this problem it would be such a easy fix for symantec but for some reason I cant see them fixing it.

You can tell SAV to ignore individual files, such as pagefile.sys. I know this works because I have it ignoring a couple of files related to DameWare Mini Remote. I'll have to give this a try.

well with my SAV when I go to tell it the certain files to ignore pagefile.sys isnt listed :-(

RogueSpear, is 9.0.2.1000 a officle release, they just simply havent updated there site?

I like to use the latest build at all times, so if this build is safe I would like to use it, but if it is a beta of some kind then it would be nice to know.

I read the release notes you put up, but it only says 9.0.2.1000 but nothing about it.

HHMM maybe I need coffee

You have to click on the + symbol to expand the details. I don't remember right now, but there may not have been any changes to the firewall component of SCS.

Well there is no way to set the pagefile inside the program. But you can from the reg.

here is the reg fix for the pagefile problem

And it works ok. so now you can run this as part of your XP setup and the pagefile will be ok.

At least it has for my tests.

EDIT:
I updated the reg file later in this thread.

Beat me to the punch! I was just going to make one of those too!

On a side note: I think its strange that you can see IO.SYS, ntldr, etc in the exclusions dialog box, but not pagefile.sys.

Well done on the fix! Now if we could just figure out my terminal services problem, maybe Symantec would hire us as lead engineers.

Holy pizza toppings batman!!!
I got a reply from symantec and they are going to fix the problem hehe;

Also on one note I replyed back to that with our fix LOL.

Maybe they will get it fixed faster now.

This is a great site here.

I've been browsing through here and didn't see any postings on doing a silent live update after installing Symantec AV 9.0.

So hopefully this isn't a repost.

I'm not sure if all versions have a .msi file with them but mine does. This code will work with either the setup.exe or .msi but the .exe will return immediately, that is why I put in the waiting part. Using .msi you can do the AV install and the definitions right after each other with no problems.

The key thing that makes the live update work is making sure that your current working directory is the symantec folder. Without that it will never run. This is likely a security feature or just Symantec being picky and not wanting anyone else running their update. Weird huh?

Someone more into batch files than I could do this in a FOR loop since that is basically what I am doing anyway.



So, if not something old I missed, hope that helps some of you.

Sorry guys, but the pagefile fix wont work if the exclude check box isnt checked. so this fixed reg file will take care of it. sorry I didnt see it last time.

Just simply run this reg file after you install sav once you reboot the settings will take effect.

@boredwithxp You seem to have a pretty good handle on available command line switches in SAV. Do you happen to know of any for ALEScan.exe that is a part of the Symantec Client Firewall (part of SCS)?

Nope I just knew that Symantec AV CE was doing silent live update everytime I start windows and I knew the program it was using to do it so I just played around with it and got it to work.

Now all my Symantec installs do live updates automatically (assuming they have net access during install). This I think is a much better solution than dealing with extra definition files that take up extra space.

This is only my second posting on this site anyway, I'm a newbie at this silent install stuff. Right now I am working on a unattended DVD with XP Pro, Office 2k3, Symantec, Nero, Zonealarm, and whatever else I can make unattended. Visual studio doesn't want to be unattended or I would put that on there too.

Very useful site with lots of info I've already refered a friend here and he is working on his own unattended install now.

let me see if i understand...

as long as i have the code below called (lets say its called: updateSAV.cmd) after SAV installs, itll update (if im connected to the internet)?

This will do it.

Just remember .msi installer will not return until install is done.
The .exe installer will return imediately and you need the wait time for that.

If you are using only the .msi then all you need is change to directory where you installed SAV, then run VPDN_LU.exe /s /start

This is a simpler version without all the messages I used for testing.

INSTALL is the installation location, passed to the .msi file, and used to run updates.

TRIES is an how many minutes (approx.) to wait for install to finish, which is important for the .exe setup.

PUSHD and POPD are built into xp, not sure if they are in dos or not.
PUDHD will change to a folder and store the current folder
POPD will change back to the stored folder

If you want just the updates then remove the line that calls the installer, you need to keep the variables or the wait loop won't work.

Well after a lot of testing and yelling at the screen I have found the reg fix works but not on the automated installs.

Turns out for some strange reason after the auto install you simply need to open and close SAV for it to take effect. Strange and still works but not good enough for me and my auto installs.

So thanks to rogue I started playing with the grc.dat file.
Now the auto install works with the fix and no reg file needed

So just put this file in the same dir as the setup of SAV and you should be all good to go.

Please let me know if anyone has any trouble.

Me and rogue make a good team LOL

Hi
I know this have nothing to do with silent install, but I hope some of you can help me.
Symantec do not offer any tool to backup the groupsettings in 9.x but you it can be backup if you follow the procedure discripe below (Unsupported !!) (Copy from an email I got from Symantec Support). I want to collect the settings from all my primery parent servers remote on one server. Does any one know how to do that?

--- Copy from Email start---

Solution:
The following method is not a supported means of product configuration. We
strongly recommend backing up the registry on both servers before moving
forward with these instructions. Because of the changes being made and the
volatile nature of making these types of changes we also strongly
recommend doing thorough testing in a test network environment before
attempting these changes in the production environment. The following
steps will outline the process of retaining client groups between server
groups when moving the primary server of one group into another. It is
also suggested that you read through the entire document before following
the steps provided.

1. If Symantec Antivirus 9 right click the client group and ensure
"Inherit settings from Server Group" is Not Checked

2. Go to the registry of the primary server you will be moving
3. Backup the registry entry (Registry (or) File -> Export Registry File)
for each client group you want to keep and put them in a shared location

Example: If I have three client groups with the names testgroup1,
testgroup2, and testgroup3. I would backup the following keys:

HKLM\Software\INTEL\LANDesk\VirusProtect6\CurrentVersion\Groups\
testgroup1
HKLM\Software\INTEL\LANDesk\VirusProtect6\CurrentVersion\Groups\
testgroup2
HKLM\Software\INTEL\LANDesk\VirusProtect6\CurrentVersion\Groups\
testgroup3

CRITICAL NOTE: DO NOT BACKUP THE GROUPS KEY


4. Move the Primary server to the new server group
5. CRITICAL: When prompted with "Do you want to apply settings from the
New Server Group? This could take several minutes" choose "NO"
6. At the Primary Server of the new server group Import each .reg file
you created in step 3
7. Lock the server group
8. Unlock the server group

You should now see all the client groups and they should have maintained
all of their settings.

If you would like your new secondary server to have same Auto-Protect
Settings as the new server group please do the following:

1. Right click the new server group
2. Go to All Tasks --> Symantec Antivirus --> Client Auto-Protect Options
3. Click Yes on the message
4. Click Reset All --> Reset All

This will propagate the server group settings to the new secondary server.
If your client group has "Inherit settings from Server Group" Unchecked
they will not be affected by this change.

--- Copy from Email end---

I use the 9.02 MSI as follows - command line switches specify your SSC server and few other things:

msiexec.exe /i "%systemdrive%\Install\nav9\Symantec AntiVirus.msi" RUNLIVEUPDATE=0 REBOOT=ReallySuppress NETWORKTYPE=1 SERVERNAME=xxxxxx ADDLOCAL=SAVMain,SAVUI,SAVHelp,OutlookSnapin /QB" /f

As you can see you can specify which componens of SAV9 to install, in my case I choose NOT to install the firewall stuff. Also you get to specify which SSC server to connect right after install for defs and NOT to run LU.



Hope this helps
Boyan