Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Upgrading From 4.1 to NG Useful Tips

Status
Not open for further replies.

Piloria

IS-IT--Management
Mar 12, 2002
435
GB
Some Quirks that i encountered when upgrading to NG

1. NG runs in eitherbound mode only. When upgrading from 4.1 and you are configured as inbound you will need new rules to allow trafic from the firewall for anything it requires. (DNS, HTTP, LDAP, SMTP for alerts, AV updates ect...)

2. NG introduces a new parameter in the firewall object under SMTP for max mail size (default 1Mb) this is in addition to any rules you have set up for CVP

3. i dont know if this is NT spacific but was a massive pain. NG has a fault that if any of the objects are longer than 19 chars then the policy wont install after the upgrade giving the message "cant find executable"
 
There is also a bug in the upgrade process that if you have manually edited the objects_C file, the upgrade process will error out. Which means you have to do a freash install and recreate all your ojects and rules, if you wish to migrate to NG. We are in the middle of a migration to NG and we ran into the above problem. As well as a couple others that were Hardware specific.
 
What SP was on the 4.1 before the upgrade? Which FP did you move to? Did you run the upgrade verifier tool? (requires software subscription, I think...)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top