Anonymous_User Absent Member.
Absent Member.
3929 views

Groupwise

Alright here it goes, I have about 4,500 users that I about to import into
Groupwise 6.5. These employees have Limited License Mailboxes. This is
done by right clicking on a user, going into groupwise utilities ->
Environment -> Click Client Access tab -> there you will see Client
Licensing. I'm looking for an API that I can use to set this atribute
while createing the user (prefferably in PERL). Or a batch way of doing
it. I found some TID's implicateing that this can be done by multiple
object selection then doing it manually one time. This option does not
seem to work with GW 6.5. Any suggestions???

Mike Lane
Systems Analyst
TxDot
Labels (1)
0 Likes
8 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Groupwise

Hmmmm....

I _think_ your failing to understand GroupWise licensing and Netware
Licensing, which are entirely different.

Netware 6.5 licenses a user in a tree, when a user logs in, it obtains a
license and keeps it for 90 days, and the 90 days is reset every time
that use logs in, or until the license is manualy disconected from that
user and sent back to the pool.

GroupWise licenses are _paper_ licenses, in other words, the honor system.

You can have a 5 user license for your entire Network, and have
1,000,000 users in your tree, but only the first 5 who login will get an
authenticated connection; however, they may ALL use their GroupWise
accounts.

Additionaly, you can create a GroupWise user that is NOT in the NDS
tree, and GroupWise will work just fine, just vreate a Forgien GW user.
There are completely unknow as NetWare users, do not consume licenses,
etc. etc.

This is how you run a GroupWise system without having an NDS tree or
even NetWare licenses, with the exception of the server license ( which
comes with Netware ) and the normal 5 user pack that comes with it when
you purchase NetWare.

The AdminAPI allows you to create GroupWise users and asscoiate them
with NDS accounts, ie:

User AddExistingUser( String UserName, String DN, [String Password],
[String PO],
[String Dom], [String MailboxID] )

Adds an existing NDS User with the given UserName and DN
(distinguished name) to GroupWise. Password will apply to GroupWise
only. See Remarks below.

This is stright from the documentation. As you can see it allows you to
create a GW account for someone who exists in NDS already and set
their password, etc. etc.

---------------------

User AddExternalUser( String UserName, [String PO], [String Dom] )

Adds an external User with the given UserName to GroupWise. Dom, if
supplied, must be an external domain. See Remarks below.

This function allows you to create and external GW user. No reference
to NDS required.

Hope this helps.

Bill.


mlane@dot.state.tx.us wrote:

> Alright here it goes, I have about 4,500 users that I about to import into
> Groupwise 6.5. These employees have Limited License Mailboxes. This is
> done by right clicking on a user, going into groupwise utilities ->
> Environment -> Click Client Access tab -> there you will see Client
> Licensing. I'm looking for an API that I can use to set this atribute
> while createing the user (prefferably in PERL). Or a batch way of doing
> it. I found some TID's implicateing that this can be done by multiple
> object selection then doing it manually one time. This option does not
> seem to work with GW 6.5. Any suggestions???
>
> Mike Lane
> Systems Analyst
> TxDot

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Groupwise

Since GW 6.0 it has had a reporting engine built in to report the
number of active users and their status - Full/Limited. This can be
found under

Tools ->GroupWise Utils->Mailbox-> Library Maintenance

Novell can and does ask for this information during CLA and MLA
audits.

As all of the controls are within ConsoleOne my guess is that there is
currently no published API.

Roger Thomas, Dev SysOp 22

"Bill Sappington" <bill@nospam.oaksystems.com> wrote in message news:419A5F2F.3000409@nospam.oaksystems.com...
> Hmmmm....
>
> I _think_ your failing to understand GroupWise licensing and Netware
> Licensing, which are entirely different.
>
> Netware 6.5 licenses a user in a tree, when a user logs in, it obtains a
> license and keeps it for 90 days, and the 90 days is reset every time
> that use logs in, or until the license is manualy disconected from that
> user and sent back to the pool.
>
> GroupWise licenses are _paper_ licenses, in other words, the honor system.
>
> You can have a 5 user license for your entire Network, and have
> 1,000,000 users in your tree, but only the first 5 who login will get an
> authenticated connection; however, they may ALL use their GroupWise
> accounts.
>
> Additionaly, you can create a GroupWise user that is NOT in the NDS
> tree, and GroupWise will work just fine, just vreate a Forgien GW user.
> There are completely unknow as NetWare users, do not consume licenses,
> etc. etc.
>
> This is how you run a GroupWise system without having an NDS tree or
> even NetWare licenses, with the exception of the server license ( which
> comes with Netware ) and the normal 5 user pack that comes with it when
> you purchase NetWare.
>
> The AdminAPI allows you to create GroupWise users and asscoiate them
> with NDS accounts, ie:
>
> User AddExistingUser( String UserName, String DN, [String Password],
> [String PO],
> [String Dom], [String MailboxID] )
>
> Adds an existing NDS User with the given UserName and DN
> (distinguished name) to GroupWise. Password will apply to GroupWise
> only. See Remarks below.
>
> This is stright from the documentation. As you can see it allows you to
> create a GW account for someone who exists in NDS already and set
> their password, etc. etc.
>
> ---------------------
>
> User AddExternalUser( String UserName, [String PO], [String Dom] )
>
> Adds an external User with the given UserName to GroupWise. Dom, if
> supplied, must be an external domain. See Remarks below.
>
> This function allows you to create and external GW user. No reference
> to NDS required.
>
> Hope this helps.
>
> Bill.
>
>
> mlane@dot.state.tx.us wrote:
>
> > Alright here it goes, I have about 4,500 users that I about to import into
> > Groupwise 6.5. These employees have Limited License Mailboxes. This is
> > done by right clicking on a user, going into groupwise utilities ->
> > Environment -> Click Client Access tab -> there you will see Client
> > Licensing. I'm looking for an API that I can use to set this atribute
> > while createing the user (prefferably in PERL). Or a batch way of doing
> > it. I found some TID's implicateing that this can be done by multiple
> > object selection then doing it manually one time. This option does not
> > seem to work with GW 6.5. Any suggestions???
> >
> > Mike Lane
> > Systems Analyst
> > TxDot



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Groupwise

Re: previous post

I'm working with Mike (using APIs (Win32::OLE) (or possibly Perl)) to add
4000 new users to our NDS tree with Groupwise 6.5 access setup. This
group has to have limited (ie Web) access. (You can find this with
ConsoleOne by picking a user, selecting groupwise utilities->Environment
options->Client Access).

The users ARE going to be added to the Tree, so they'll have (non-login)
accounts there.


Does anyone know where this attribute is stored/specified? (in which
object?)

Also, how do you read this attribute from a given object?
Thank you,

Russell Labay
Texas Department of Transportation
System Analyst

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Groupwise

References to audits aside..

You do not need to change a thing about limited -v- full.

If they don't have the GW client, the only thing they CAN do is use the
web interface.

To prevent people from using any other e-mail client, simply shutdown
POP3 & IMAP.

rlabay@dot.state.tx.us wrote:

> Re: previous post
>
> I'm working with Mike (using APIs (Win32::OLE) (or possibly Perl)) to add
> 4000 new users to our NDS tree with Groupwise 6.5 access setup. This
> group has to have limited (ie Web) access. (You can find this with
> ConsoleOne by picking a user, selecting groupwise utilities->Environment
> options->Client Access).
>
> The users ARE going to be added to the Tree, so they'll have (non-login)
> accounts there.
>
>
> Does anyone know where this attribute is stored/specified? (in which
> object?)
>
> Also, how do you read this attribute from a given object?
> Thank you,
>
> Russell Labay
> Texas Department of Transportation
> System Analyst
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Groupwise

> References to audits aside..
>
> You do not need to change a thing about limited -v- full.
>
> If they don't have the GW client, the only thing they CAN do is use the
> web interface.
>
> To prevent people from using any other e-mail client, simply shutdown
> POP3 & IMAP.
>
> rlabay@dot.state.tx.us wrote:
>
>

Setting the limited vs full options impacts how much how much we have to
pay to Novell for our licensing of users. So we have to have it properly
set in that regard.

Russell Labay
System Analyst - TxDOT

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Groupwise

It isn't stored in NDS, afaik. It's stored in the GW domain.

Hence there is no way to achieve what you want until/if Novell exposes that
via AdminAPI

Time to hire the student to mindlessly click the button for 3 days.



--

<rlabay@dot.state.tx.us> wrote in message
news:w4Jmd.4190$T85.3672@prv-forum2.provo.novell.com...
>> References to audits aside..
>>
>> You do not need to change a thing about limited -v- full.
>>
>> If they don't have the GW client, the only thing they CAN do is use the
>> web interface.
>>
>> To prevent people from using any other e-mail client, simply shutdown
>> POP3 & IMAP.
>>
>> rlabay@dot.state.tx.us wrote:
>>
>>

> Setting the limited vs full options impacts how much how much we have to
> pay to Novell for our licensing of users. So we have to have it properly
> set in that regard.
>
> Russell Labay
> System Analyst - TxDOT
>



0 Likes
johnbaird Absent Member.
Absent Member.

Re: Groupwise



Michael Bell wrote:

> It isn't stored in NDS, afaik. It's stored in the GW domain.
>
> Hence there is no way to achieve what you want until/if Novell exposes that
> via AdminAPI
>
> Time to hire the student to mindlessly click the button for 3 days.


This sort of situation is hardly a positive advertisement for GW and its a
common one. I would receive at least one request per month to provide a
solution requiring changes to 1000+ accounts and which cannot be done using the
Admin API. Has anyone asked Novell about developer access to the programming
interface used by ConsoleOne? Its on my to-do list ...

John
Developer Service SysOp 24



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Groupwise

This is the reason for my comment regarding pushing the issue back
to Novell via the sales channel. Novell has clients with 10,000s of
GW users that must have needed the same work carried out.

The ConsoleOne interface is in fact a set of unsecured DLLs that
read/write the database files directly, not something I think Novell
will publish anytime soon. The only other solution could be using
DirXML / identity manager, but this would take even longer to set up
if it supports the field, plus the cost.

Roger Thomas, Dev SysOp 22

"John Baird" <john@jrbsoftware.com> wrote in message news:419BBE64.1F41C1C4@jrbsoftware.com...
>
>
> Michael Bell wrote:
>
> > It isn't stored in NDS, afaik. It's stored in the GW domain.
> >
> > Hence there is no way to achieve what you want until/if Novell exposes that
> > via AdminAPI
> >
> > Time to hire the student to mindlessly click the button for 3 days.

>
> This sort of situation is hardly a positive advertisement for GW and its a
> common one. I would receive at least one request per month to provide a
> solution requiring changes to 1000+ accounts and which cannot be done using the
> Admin API. Has anyone asked Novell about developer access to the programming
> interface used by ConsoleOne? Its on my to-do list ...
>
> John
> Developer Service SysOp 24
>
>
>



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.