Re: Old BM 3.5 system crashed

[Craig Johnson]

You could have them call me if they still need help. I deal with
servers like that all the time.

You cannot directly upgrade a 3.5 server to 3.9. Only 3.8 (sp5) was
supported for a direct in-place upgrade. (However, I've done some
upgrades, and most of the important stuff upgrades OK).

There are big changes between 3.5 and 3.9, including filters moving to
NDS and all config done with iManager on proxy, access rules and vpn.
Any time you go to BM 3.8 or 3.9 (or really any earlier version) it is
really important to have a health foundation to start with (NDS, time
sync, proper replica placement, LDAP, etc.) BM makes a lot of use of
the infrastructure provided with NetWare and eDir, and you can have
some grief if there are problems with one or more of those components).

You don't really ever need to 'remove' BMgr either. Simply not
starting the services and disabling the filters will allow the server
to run more or less as a normal NetWare server. You don't need to
remove bits from eDirectory - the presence of the BMgr attributes and
licenses won't cause any problems.

Craig Johnson
Novell Knowledge Partner
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***