salaing1 Absent Member.
Absent Member.
736 views

iManager and dependence on eDirectory

I'm in the middle of selling the latest iPrint (Appliance 2.1) and GroupWise versions with the assumption that it will run on Active Directory. The customer does not want multiple directories in their environment.

I was thinking that it shouldn't be a problem since they can both use AD for authentication, etc.

Now I'm thinking that they both use iManager to manage the print manager and driver store, etc and also GroupWise 2014.

iManager requires eDirectory in order to authenticate for RBS, etc and to define who can log in.

Question is, is there a way to either A. Use a different ldap source for iManager or B. Use different tools for iPrint and GroupWise. Not command line tools, cause I could always use iprintman for printing. But I want simple administration with the right tools.

Thanks heaps!
Labels (1)
0 Likes
4 Replies
Highlighted
Knowledge Partner
Knowledge Partner

Re: iManager and dependence on eDirectory

On Thu, 23 Feb 2017 21:26:03 GMT, salaing
<salaing@no-mx.forums.microfocus.com> wrote:

>
>I'm in the middle of selling the latest iPrint (Appliance 2.1) and
>GroupWise versions with the assumption that it will run on Active
>Directory. The customer does not want multiple directories in their
>environment.
>
>I was thinking that it shouldn't be a problem since they can both use AD
>for authentication, etc.
>
>Now I'm thinking that they both use iManager to manage the print manager
>and driver store, etc and also GroupWise 2014.
>
>iManager requires eDirectory in order to authenticate for RBS, etc and
>to define who can log in.
>
>Question is, is there a way to either A. Use a different ldap source for
>iManager or B. Use different tools for iPrint and GroupWise. Not
>command line tools, cause I could always use iprintman for printing.
>But I want simple administration with the right tools.
>
>Thanks heaps!


GroupWise does not use iManager. It has its own web-based Admin
interface. You just connect it to the directory service of your
choice.

--
Ken
Knowledge Partner

If this post was helpful and you are logged into the web interface,
please show your appreciation and click on the star below... Thanks!

Create and vote for enhancements!
https://www.microfocus.com/products/enhancement-request.html
--
Ken
Knowledge Partner

Create and vote for enhancements!
https://www.microfocus.com/products/enhancement-request.html
0 Likes
salaing1 Absent Member.
Absent Member.

Re: iManager and dependence on eDirectory

Sweet, just like ZCM, I thought you needed iMan or the mmc snapin to add users, etc.
0 Likes
salaing1 Absent Member.
Absent Member.

Re: iManager and dependence on eDirectory

iPrint will need iManager and iManager needs eDirectory. I can't seem to find a way around it, possibly by running it in unrestricted mode, but preferably using AD or local admin account.
0 Likes
Knowledge Partner
Knowledge Partner

Re: iManager and dependence on eDirectory

salaing Wrote in message:

> iPrint will need iManager and iManager needs eDirectory. I can't seem
> to find a way around it, possibly by running it in unrestricted mode,
> but preferably using AD or local admin account.


The iPrint Appliance is self-contained with its own eDirectory and
iManager which is solely used to operate the appliance. The
appliance can hook into eDirectory 8.8+ or Active Directory on
Windows Server 2008 R2 Enterprise Edition/2012 R2 Standard
Edition[1].

HTH.

[1] https://www.novell.com/documentation/iprint-appliance-2/iprint
_admin/data/b17fk26g.html
--
Simon Flood
Micro Focus Knowledge Partner


----Android NewsGroup Reader----
http://usenet.sinaapp.com/
0 Likes
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.