Article

geoffc's picture
article
Reads:

4460

Score:
5
5
1
 
Comments:

0

Open Call - Rules that Need Updating when Migrating to IDM 3.5

Author Info

1 August 2007 - 8:13am
Submitted by: geoffc

Author Blog
Author Profile

Tags

Tags Map

(View Disclaimer)

Problem

Just after Brainshare 2007, Novell released IDM 3.5. This release adds many great features that are very useful.

A lot of implementations want to upgrade as soon as possible to get access to the new features. In principle it should be simple at the engine and shim level, and at a binary level it pretty much is straightforward. The binaries pretty much just work, even in mixed modes, even though which is probably not really supported.

But the gotchas come in when it comes to features in the drivers that require changes to policies. Novell tries to document some of them, but it is pretty clear they missed a number of things.

Solution

This Open Call is aimed at collecting a list of those gotchas, documenting them, and making life easier for the next guy.

If you have found a rule that needs to be updated on an existing IDM 2.x, or 3.0x driver, in order to work or use new features in the IDM 3.5 driver please contribute.

Please specify what IDM version you are coming from, the platform you are running the bits and pieces on, which rule and driver, and the specific issues you have found.

Hopefully this will make all our lives easier!

Tips on Driver Updates

- Lotus Notes driver for proper Notes ID file password changing:
http://www.novell.com/coolsolutions/feature/19322.html

- Issue to watch out for with the AS400/i5os/Midrange driver (Bi-directional version, not fanout):
http://www.novell.com/coolsolutions/tip/19301.html


Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).

It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.



Related Articles


User Comments

© 2013 Novell