Looking to update GroupShield from 5.2 to 6.0.1

[jatkinson]

Hi there,

Having renewed our grants etc and waited patiently for new McAfee products to come out I'd like to start the New Year off by updating EPO, GroupShield and VirusScan.

I am looking at installing EPO 3.5 to a new server rather than update EPO 3.0 on an existing server to which I don't see a problem, anything I ought to be aware of just in case?

My main concern is with GroupShield. What have your experiences been? My gut tells me to remove 5.2 and install a clean copy of 6.0.1 onto my Exchange Server (W2K DC with Exchange 2K installed). Are there any issues/pitfalls to be aware and careful of?

Finally I'll be installing VirusScan 8.0i over 7.1 using EPO 3.5 when all is installed, configured and working OK.

I'll probably run EPO 3.5 and VirusScan 8.0i in a test environment however I don't have another Exchange Server in a test environment so any info you can provide would be greatly appreciated.

Many thanks

jatkinson.

 

[mattmsudawg]

With updating EPO, if you are currently using EPO and the agents, make sure you give the new server the same IP address and host name unless you want to redeploy the agents to all your clients.

 

[jatkinson]

Thanks for that matt, the current server will continue to exist as it is used for something else unrelated (hence one of the reasons for wanting to move EPO to its own server), so you're right I will need to redeploy the agents. Thanks for bringing it to my attention.

 

[alicep]

I just went from 5.2 to 6 on Groupshield. The groupshield interface is very different. All the features are there, but different ways to get them configured. There is an upgrade guide on the website that you will want to look at prior to installing. I uninstalled 5.2 and then installed 6. After doing the install, I did a dat update and then ran an ondemand scan just in case a virus slipped through while I the product was uninstalled.

Are you using the spamkiller add-on? I can't say that upgrade has worked for me - at all. Very painful conversion from 2.02 to 2.1 add-on. I won't bore you with the details if you are not using spamkiller. If you are interested, I'll fill you in on my recent experience so you can prepare.

As for VirusScan 8.0i, there is a message about it on the mcafee tech support hold recording. It says if you are loading 8.0i on a computer with Groupshield installed, turn off port blocking on port 25. I haven't upgraded to that version yet, but I made a note for future reference. Use your grant to create a login ID on the tech portal and you will see that announcement.

 

[jatkinson]

Hey Alice, thanks for your post and the sound tip re VirusScan 8.0i and port 25.

We're not currently using the spamkiller add-on no, I was interested in this way back when McAfee anounced plans for it alonogside GroupShield 6 although now I am looking at bringing in an anti-spam solution at the linux mail gateway we run rather than onto the Exchange Server itself.

How have you found spamkiller in general, I mean aside from the problems you have obviously encountered when upgrading. Does it do a good job, is it worth me looking at?

Cheers

 

[alicep]

It does detect the spam and sends it to either users junk folder or public junk folder. You can tweak the threshold for detection and the default filtering works. I have not added any custom policies or added any additional filters.

Tech support says it will learn what is valid mail over time. I am hoping it is a fast learner! I am still getting messages into my inbox that are junk mail, but we are not having many false detections.

This version doesn't work on the internet connector, but instead scans all email on the server (including internal user to internal user). That has not been a problem so far, but it is different than the previous spamkiller.

Mcafee wouldn't support version 2.02, thus the upgrade.
2.02 would automatically add a users' contacts to the whitelist. version 2.1 does not include this feature. Our users forced to rebuild their whitelist. No import feature for the whitelist, either. In your case of a new installation, this won't be an issue since your users would not be losing a feature.

I guess the other thing to mention is that you can install the user black list/whitelist server (optional). It installs BWLISTS server and BWUPDATE server on IIS and by default requires Anonymous access and doesn't allow https. Documentation doesn't tell you this or give a way to secure the site.

 

[jatkinson]

Hi Alice

Thanks for the info and again another sound tip. I'll give spamkiller some thought and if I decide to go with it, will probably end up posting progress etc on the forum.