EPO 2.5.1 to EPO 3.1 migration questions 1

[NickFerrar]

I'm trying to do a migration from our current environment of EPO 2.5.1 with VirusScan/Netshield 4.5.1 to EPO 3.1 with VirusScan Enterprise 7.1

I'm creating the new environment in parallel to the old one and intend to migrate some test clients across first and when happy do a 'big bang' cut-over. My plan was to use EPO 2.5.1 to remove the 2.5 agent and VirusScan 4.5.1 and then discover the computers in the new EPO, push the new agent to them and then deploy VS 7.1 to them.

However I can't see a way of uninstalling VS 4.5.1 through EPO 2.5.1, is this possible - if so how? My fallback plan is to remove the agent through EPO 2.5.1 discover the client in EPO 3.1, push the new agent out to it which then lists VS 4.5.1 as installed and then run a deployment task in EPO 3.1 to uninstall the VS 4.5.1 However I've hit a snag in I can't find the correct VS 4.5.1 source to read into the EPO 3.1 in order that it's available to uninstall through a deployment task.

I've got VS 4.5 loaded in the repository fine but the uninstall doesn't work when the client has 4.5.1 (no real suprise) but all the source files I can find for 4.5.1 don't have the xxx.z package file in them in order to import into EPO 3.1

Is there a package file out there for 4.5.1 or do you have to do it differently? Reading in the 4.5.1 NAP file didn't help and doing a pull task to try and update the EPO didn't help (I was hoping it would update the installed 4.5 package to 4.5.1 !).

 

[b0pp]

Hi nick,

I can't really remember, but if i'm correct you can install VirusScan 4.5.1 from epo 2.5.1 by marking it to uninstall from policies. So click the directorylevel at which you want this to be done, than go to the ROOT of the policies for VirusScan 4.5.1, the spot where you can install it too...

Furthermore: to install or remove software from Epo 3.0.1 you need to check in the PkgCatalog.z file which is included with the installation files. If you have an old download or cd with VirusScan 4.5.1, than this file won't be among the other installation files, for the simple fact that Epo 3.0.1 nor PkgCatalog.z files existed back than. You have to download VirusScan 4.5.1. again using your Grant# to get the correct PkgCatalog.z. Than, if you have checked it in the repository, you can mark it as "Remove" from within the Deployment task.

Take one more option in consideration though: VirusScan 7.1 removes VirusScan 4.5.x and Netshield 4.5.0 automatically during setup, and from my experience this works really smoothly. It actually doesn't overwrite any files, but executes the same uninstall string as would you perform an uninstall from Epo, so basically it's the same thing.

My advise is to just set VirusScan 7.1 to install. Offcourse try it out on a few machines, you'll love it

Mention that virusscan 7.1 won't install on Windows 9x, you'll still need 4.5.1 for those machines.

Regards

 

[NickFerrar]

b0pp,

Cheers - I think you've saved me some headaches! I'll test the VS7.1 install auto uninstalling the VS4.5.1 as I agree this is a better way if it does work properly.

Our grant number recently changed and I haven't been able to get the new one from our head office yet but also good to know the .z files are available there if I need them.

 

[toddpfc]

First of all, make sure you are at ePO 3.0.2 (fewer bugs). You can uninstall the ePO 2.5 client and do a push from the new 3.0.2 and install VirusScan 7.1 over top of the 4.5.1 as it does an automatic removal of the older version. Out of 500 clients, I had to visit fewer than 5 to complete the upgrade. VirusScan 7.1 with ePO 3.0.2 is very well behaved and integrated.

 

[NickFerrar]

Oh I thought I'd read here that 3.0.02 was buggy and had been withdrawn so I was avoiding it. If this isn't the case I'd certainly want to use the latest version.

 

[b0pp]

toddpfc, consider yourself to be one of the happy few that don't have tremendous problems after implementing epo 302. NAI really have their hands full at the moment resolving the issues that epo 302 has caused at lots of customers around the globe.

you can't even download epo 302 anymore, as they have pulled it back.

301 is actually the best version at the moment...

btw nick: you can upgrade epo 251 to 301 as well, and enable 2.x to 3.01 upgrade in the policies for epo agents

 

[NickFerrar]

Any news on when they will re-release sp2? I had it downloaded before it was withdrawn and it mentions it resolves one I've experienced - a couple of our servers can't be contacted by the EPO to do an agent install, even though the server the EPO is on can contact them just fine.

 

[b0pp]

nope, no official news on this yet, and i don't know anymore unfortunately.

I know, epo lacks good functionality to automatically distribute the agent. Sometimes you just can't get a clue why a send agent install won't work...

In the field we often use logonscripts to make sure every node gets an agent. Strings like:

if not exist "C:\Program Files\Network Associates\Common Framework\FrameworkService.exe" \\server\share\FramePkg.exe /install=agent /silent

They work just fine. I know it's a workaround but the installation of the agent merely is a detail.

If you have only few servers that you can't get it pushed to, i advise you to stop wasting time in trying to solve this and just run FramePkg.exe once locally. Much faster...

 

[bfralia]

As said above, don't install SP2, it creates more problems that it cures. I did an uninstall on 3.0.2 and reinstalled 3.0.1 as the agent for 3.0.2 wouldn't install on most Win2kPro clients without dorfing with the local security policy on each client.

Now on to EPO 3.0.1 - It works well with NT, 2k, XP, and 2003 computers both clients and servers. However be aware that the remote registry MUST be started for it to work. Also it doesn't work well at all on XP Home versions (I know they should not be in a business environment but I didn't buy the.

EPO 3.0.1 is a pain on W95/98 computers. File and Print sharing along with remote administration MUST be turned on assuming you want epo to deploy the agents and software.

Once getting through the registry and w95/98 problems it's great.

 

[altafk]

Does anyone know if 3.02a (3.0.0 SP2a) is ok to install? Has anyone installed this then Patch 4?

 

[bfralia]

I haven't installed it but started a thread asking about people's success with sp2a. I got burned pretty bad on sp2 and had to completely uninstall and reinstall 3.0.1.

All the responses (from people actually using it) are pretty positive. I'm going to look into upgrading soon.