[smc1979]

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

[RogueSpear]

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.

[smc1979]

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

Quote

Ok for starters my customer has 30 machines all of which use SAVCE v9.0.1.1100 ALL of which are also set to unmaged and without a server for now until it is set up.

All 30 computers are Windows XP With SP2, all fresh installs, on all of them SAVCE v9.0 is messesing up the page file.

I have done a lot of testing with this and have gone as far as disabling everythin that has to do with SAVCE v9.0 to the point where it is not running what so ever and the problem is still there. the moment you uninstall SAVCE v9.0 the problem is fixed.

This has been a big problem and I can not belive that symantec has heard nothing about it.

I have screen shots, file comparasions and the whole 9 yards if your own tech support cant fix this.

Its as easy as this, install Windows XP with SP2 already intergrated, Install NOTHING else, now install SAVCE v9.0 and reboot.

There you go the page file no longer grows to what you want. Now if you go in and set it higher and apply it will grow, reboot and it is gone.

So far since I have completely disable SAVCE v9.0 and the problem is still there then that tells me there is a conflict either with the install or one of the services it installs.

I have contacted over a dozen other people with SAVCE v9.0 and they ALL have the same problem with Windows XP sp2 only, no one has told me different for any other Windows OS.

Here is a link on some of the issues.

http://www.msfn.org/board/index.php?showtopic=23991&st=320

If sysmantec can not easily see this problem for them selves then it is time my customers move away from Sav 9 corp.

I have worked hard to try and locate the problem even telling sav to leave the page file alone, nothing works. plain and simple this is a problem with SAV.

Please fix this as it is killing the performance of the machines which I can not let happen much longer. This computers need the page file to be larger and SAV wont let it happen.

[a06lp]

nice letter!

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

[Nilfred]

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

d:\sav91400\program files\Symantec AntiVirus\CLT-INST\WEBINST\brnotsup.htm
d:\sav91400\program files\Symantec AntiVirus\CLT-INST\WEBINST\default.htm
d:\sav91400\program files\Symantec AntiVirus\CLT-INST\WEBINST\intro.htm
d:\sav91400\program files\Symantec AntiVirus\CLT-INST\WEBINST\logo.jpg
d:\sav91400\program files\Symantec AntiVirus\CLT-INST\WEBINST\oscheck.htm
d:\sav91400\program files\Symantec AntiVirus\CLT-INST\WEBINST\plnotsup.htm
d:\sav91400\program files\Symantec AntiVirus\CLT-INST\WEBINST\readme.htm
d:\sav91400\program files\Symantec AntiVirus\CLT-INST\WEBINST\start.htm
d:\sav91400\program files\Symantec AntiVirus\CLT-INST\WEBINST\webinst
d:\sav91400\program files\Symantec AntiVirus\CLT-INST\WEBINST\WebInst.cab
d:\sav91400\program files\Symantec AntiVirus\CLT-INST\WEBINST\webinst\files.ini
d:\sav91400\program files\Symantec AntiVirus\Logon\NBPSHPOP.EXE
d:\sav91400\program files\Symantec AntiVirus\Logon\OSVER.EXE
d:\sav91400\program files\Symantec AntiVirus\Logon\VPLOGON.BAT
d:\sav91400\program files\Symantec AntiVirus\Logon\VPSCAN16.BAT
d:\sav91400\program files\Symantec AntiVirus\Logon\vp_log32.exe
d:\sav91400\program files\Symantec AntiVirus\Logon\VP_LOGIN.INI
d:\sav91400\System32\CBA\pds.exe

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

[RogueSpear]

@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.

[Nilfred]

Well, Liveupdate runs... And yes! there is a damm 9 Mb update for Server:
http://liveupdate.sy...om/ennluxdb.x86
This is a .zip file and contanis 3 files:

ennluxdb.x86\NAV70.DIS
ennluxdb.x86\SAVCE.DIS
ennluxdb.x86\VD1AA826.XDB

The last one is copied over here:

"c:\Archivos de programa\SAV\VD1AA826.XDB"

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

[smc1979]

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?

[RogueSpear]

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

[smc1979]

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!

[smc1979]

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.

[RogueSpear]

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

Attached File(s)

•  Release_notes.7z (29.87K)
  Number of downloads: 42

[smc1979]

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.

[RogueSpear]

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.

[smc1979]

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

[smc1979]

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

[RogueSpear]

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.

[smc1979]

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.

[RogueSpear]

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.

[smc1979]

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

Quote

I can understand your frustration with this issue, Shane. If it is
any consolation symantec is actually aware of the problem, which has
been entered as a defect and is currently being analysed by
development. We have created a Knowledge Base article which is still
a work in progress and is not yet publicly available. I have
submitted a request to publish the document as soon as possible. When
the document is available, you can access it and book mark the
following URL:

Title: 'After installing SAV CE 9.0 the pagefile size has changed.'
Document ID: 2004042913251448
> Web URL: http://service1.symantec.com/support/ent-s...rc=ent_gold_nam

When a solution is found, it will be implemented in a maintenance
release of symantec AntiVirus Corporate Edition (SAVCE) 9.0, and the
document will be updated. Configuring Auto-Protect to load as a
service rather than a device driver has resolved the issue for most
customers.

Workaround:

It is possible to configure Auto-Protect to load at service startup,
instead of at system startup. This causes a small window of
vulnerability when the system starts up and shuts down, during which
Auto-Protect is not enabled.

Use the procedure that applies to your server or type of client.

To delay the loading of Auto-Protect until service startup on managed
clients:
1. In the left pane of the symantec System Center console, right-click
the server group that you want to change, and then click Unlock Server
Group.
2. Right-click the desired server or server group, and then click All
Tasks > symantec AntiVirus > Client Auto-Protect Options.
3. Click Advanced.
4. Under Startup Options, click symantec AntiVirus start.
5. Click OK, then click Reset All to propagate the change to clients.

To delay the loading of Auto-Protect until service startup on
unmanaged clients:
1. Start symantec AntiVirus.
2. On the Configure menu, click File System Auto-Protect.
3. Click Advanced.
4. Under Startup Options, click symantec AntiVirus start.
5. Click OK in both open dialog boxes, and then exit Symantec
AntiVirus.

To delay the loading of Auto-Protect until service startup on
antivirus servers:
1. In the left pane of the symantec System Center console, right-click
the server group that you want to change, and then click Unlock Server
Group.
2. Right-click the desired server or server group, and then click All
Tasks > symantec AntiVirus > Server Auto-Protect Options.
3. Click Advanced.
4. Under Startup Options, click symantec AntiVirus start.
5. Click OK to save the change.
6. In the Server Auto-Protect Options dialog box, click OK to apply
this change to the specified servers.

Please let us know if you need additional assistance.

Sincerely,

Barbara Coleman
Symantec Technical Support