New Ranks & Badges For The Community!
Notice something different? The ranks and associated badges have gone "Star Fleet". See what they all mean HERE
Absent Member.
Absent Member.

Re: NSM 2.0 - .net requirement

Cheers ... yep, I agree, iManager is horrible. I use it ONLY when
there's no other tool to do the same job..and so far that's pretty much
only the administration/creation of NDPS print queues.

I've done my fair share of complaining to Novell in recent years about
the push to iManager - and I told our account manager that obviously the
developers don't actually use and manage a large tree on a daily basis,
because if they did, then they would realise that any web based
management tool is a bad idea and they'd stop pushing everything over to
it. The answer they give of course is they need to be "multi
platform".... I'd ask the question, how many people administer a
Novell/Netware/eDir environment and NOT use Windows workstations to do
so???? I can't imagine many.

Oh well - enough bitching 🙂 I still use NWadmin as my main tool and
only use Console One when I need to adjust groupwise stuff. My tree has
some 30,000 objects and I've not had a problem yet.. nwadmin is still the
fastest way of skipping around objects and making quick changes. My
helpdesk uses ConsoleOne soley.. They're going to hate me when I force
them to use iManager (hope that day never comes).

> Dave wrote:
> > When I start the admin tool, it complains that I dont have .Net
> > Framework 1.1, but does actually fire up and work. I am running
> > .Net Framework 2.0.
> >
> > Are there any known issues running 2.0 instead ? I don't really feel
> > like having two versions of .Net installed !

> I don't know if there are any issues with .Net 2.0 and NSM, but

according to
> NSM documentation, .Net 2.0 is not supported -->
> - - - - - - - - -
> NSMAdmin has the following minimum requirements for Windows:
> - .NET 1.1 SP1 Framework installed (Does not support .Net 2.0 Framework)
> - .NET security settings adjusted if running the executable from a

> drive
> - - - - - - - - -
> > On a side note - why hasn't NSM management been placed into iManager
> > (as much as I hate iManager) ? Running yet another config tool is
> > crazy to say the least - I thought novell stopped doing that.

> iManager sucks and that may be the reason why NSM developers made

> It sure looks like Novell tries to do everything the hard way or maybe
> someone at Novell just isn't doing his/hers job?
> Now we have to use NWadmin, ConsoleOne, iManager, DNS/DHCP management
> console, Remote manager and this new NSMAdmin to handle Novell products
> efficiently. Aaaarrgggghh...
> Sure, some standalone admin tool tasks can be made using iManager, but

> iManager is like pulling teeths. I'm pretty sure nobody actually uses
> iManager if it is not absolutely necessary.
> PS. Copy and follow-ups goes to new storage-manager group
> --
> Make.
> PS. Please remove any extras if replying via email

0 Replies
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.