I just want to be sure, when you say “locked account”, that you’re not referring to an account that is disabled or expired. I’m specifically inquiring about a GroupWise mailbox that is restricted to Limited License and can only be accessed with WebAccess, not with the full Windows GroupWise client. The alternative to Limited License is Full License, allowing access by either WebAccess or the Windows client.
Thanks for the clarification, which helps us to understand the nature of the problem. It is correct that Archive To Go uses the GroupWise Client APIs to access a mailbox. In your testing, does Archive To Go account access fail for both Archive To Go’s Local and Enterprise Access modes?
Yes, it fails when using both Local and Enterprise mode. When I switch the account to Full License both Local and Enterprise work.
This is a concern for us because we have over 3,500 Limited License accounts–and growing, since they’re quite a bit less expensive.
A Limited License account can be switched to Full License to allow Archive To Go to work, but even though it can be switched back to Limited License afterwards, for auditing purposes it remains a Full License mailbox and is over twice as expensive to license from Novell.
GroupWise engineering is looking into this issue. The initial response from Novell indicates that the intent is not to prevent trusted applications, like Archive To Go, from accessing Limited Accounts. Should this problem be confirmed by GroupWise engineering, it will be fixed.
In the mean time, as the problem solution is not within our control (as a third party developer), when using Archive To Go you will need to convert Limited to Full accounts. For those accounts that you convert for use only with Archive To Go (Enterprise Mode), I suggest that you keep track of the Account IDs. Once this issue is registered as an official Novell defect number, perhaps you can advise Novell of the Account IDs which were converted soley as a work-around to this problem.
