Endpoint Protection

I am currently in the process of testing. Our current version of SEP (10.1.9.x) does not support 64bit servers. We would like to move to Win2k8 R2 which is a 64bit OS. I have a test server setup with 10.2.x and I have successfully installed an agent on a Win2k8 test server, however attempted to do a remote client install to a Win2k3 Sp2 server and the there doesn't seem to be a 32bit client present on the 10.2.x server, yet the 10.2.x server is being hosted on a 32bit Win2k3 Sp2 box. I am slightly confused as to why there isn't a 32bit client and a 64bit client on the server at the same time.

I am obviously missing something. Any input is welcome! 

First this is not SEP this is SAV.
The major drawback of SAV 10.x is 64 bit is not fully supported.It can be made server and it cannot receive definitions from parent server it has to download on its own.

Even the virus definitions for 32 bit and 64 bit is different so as 32 bit server only downloads 32bits defs so it cannot update 64 bit clients.

the most important point SAV 10.x has reached END OF LIFE from symantec

SEP 11.x is fully supported on 64bits and it can be managed by 64 bit servers.So the solution over here would be Migrate to SEP 11.x

First of all, my mistake on the naming. I realized as soon as I posted. =)

Second, while it's nice that SEP 11.x fully supports 64bit OS's, 10.x is what I currently have licensing for and will probably be the only thing I have licensing for for the remainder of the year (budget constraints). For the third and fourth quarter, we will most likely have a limited number of Win2k8 R2 servers rolled out, so I think I am fairly comfortable with the Win2k8 R2 servers going to the internet to get 10.x virus updates. 

So this brings me back to my original query, while 10.x (specifically 10.2) does seem to support Win2k8 R2 albeit in a limited capacity, why do I not have the ability to deploy Win2k3 Sp2 agents? The specific error message that I am getting when trying to remotely install is as follows:

"The server (HostServer32bit) is not hosting any compatible Symantec AntiVirus (SAV) 32 bit installers for the 32 bit client (ClientServer32bit)."

Vikram, your post was helpful!

Check this :-

Error: "The server (server name) is not hosting any compatible Symantec AntiVirus 32-bit installers for the 32-bit client."
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2006101313560148

That's not quite the answer. If you navigate to the "C:\Program Files\SAV\CLT-INST" directory and look at the sub directories, there is data in the "WIN32VISTA" and "WIN64VISTA" directories, but no where else. There basically aren't any installers other then those two. It's almost as if the installer I used did not have anything on it except the Vista data. 

Since its a Server OS so it expects to install SAV secondary server on it..
The best way to install SAV clients on Server OS is by doing a PULL install

on the 2k3 server go to \\SAV Server Name\VPHOME\CLT-INST\SAV
and install it from there..it will install as a client and will start communicating with SSC and parent server and will be full client.

Thanks for your reply Vikram, I don't think I described the issue very well. Recapping my last post:

On the 10.2.x server the following folder structure/composition is in place:

C:\Program Files\SAV\CLT-INST

• \IA64 - No data in subfolder
• \WEBINST - No data in subfolder
• \Win32 - No data in subfolder
• \Win32CS - No data in subfolder
• \WIN32VISTA - Data in folder, install files
• \WIN64 - No data in subfolder
• \Win64VISTA - Data in subfolder, Install files

So if I were to go to the 2k3 server, and navigate to \\SAV1\VPHOME\CLT-INST\WIN32 (the appropriate folder for the pull to a the 2k3 server) there would not be any install data there.

I hope this clears up any confusion. Again thanks for your input Vikram. I appreciate the help.

Hmm..well what you can do is from CD1 SAV folder copy the WIn32 and Win64 folder and in the install files just replace the GRC.dat file and pki folder of the parent server.

from win32vista install files so now you will have those folders and they will communicate to SSC after installation also

What's interesting, is that there is no WIN32 folder on the CD. Did I perhaps download an odd version of 10.2?

Actually CD2 contains 10.1.9 so that what you want copy the SAV and SAV64 folder from CD2.

Note : 10.2.x is only and only for Vista and WIn2k8 for rest of the OS its 10.1.x
So even if you download and instal 10.2 SSC it will be 10.1.9 SSC and SAV server.

Ok, so basically i would copy all the files out of the SAV folder into the C:\Program Files\SAV\CLT-INST\WIN32 folder? So in this folder there would be all the files from SAV plus the PKI folder that is currently in the WIN32 folder?

C:\Program Files\SAV\CLT-INST\WIN32 folder will only contain content of SAV folder plus new GRC and pki

create win64 folder
C:\Program Files\SAV\CLT-INST\WIN64
and put contents SAV64 with grc and pki.

How do I go about generating a GRC and PKI?

Copy from C:\program files\SAV\grc.dat
C:\program files\SAV\pki

One thing I also noticed, is it appears that the 64 bit client seems to update just fine from the 10.2.x server. Perhaps I misinterpreted what you were saying? I updated the server's vdefs from 4/10/2010 rev. 4 to 4/13/2010 rev. 5 and the W2k8 server's vdefs are at the same revision level now.

Managing 64-bit clients with Symantec System Center

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2006010609164848

I see the technical note at the bottom of the article but I am seeing behavior that is different. I have set the client to update the virus definitions as often as possible so I will check at the next update point to verify that the win2k8 server is indeed not updating its vdefs.

Could it be that the win2k8 server is going to the internet by itself without grabbing the vdefs from the server? Does it bypass the a/v server all together? Even though it cannot receive vdefs from the server, does this mean it cannot automatically update itself?

I also had to update a registry key on the SAV server to get the win32 install to work properly:

HKLM\Software\INTEL\LANDesk\VirusProtect6\CurrentVersion

I then created a new string value Named:
Win32InstDir

And assign the value:
C:\Program Files\SAV\Clt-Inst\Win32

Its not that win2008 won't update its just 64 bits don't get defs from SAV server..all 32 bit OS receive defs from Primary/Secondary server. All 64 bits needs to get defs from internet or Liveupdate administrator.

What if I install the SAV server on a 64 bit OS? Would the 64 bit OS be able to manage both 32 bit clients and 64 bit clients?

Thanks for your help on this! 

You cannot install SAV server on 64 bit.