enterprise access – shared mailboxes not listed – how do I export them?

[ee61re]

User mailboxes are all listed, but some mailboxes that are used as shared, e.g. reception, etc, do not appear on the list in enterprise mode.

I suspect we are doing something wrong?

Topic

[Support 1]

Thanks for reporting this problem.

Which version of Archive To Go are you using?

Are the shared mailboxes GroupWise Resource objects?

How many eDirectory Trees are in your GroupWise system? If you have not authenticated to the Tree that contains a given mailbox, the mailbox (and its containing post office and domain) will not be listed.

I look forward to your reply.

Regards,
Advansys Support

[ee61re]

Hi – ATG is version 2.0.0.3.

The problem mailboxes are External Entities – we have found we can access them using enterprise mode, but only one at a time, specifying each ID.

(This is workable, but taking longer than hoped, since we cannot batch process)

There is only a single tree, with a single PO.

Thanks

Rob

[Support 1]

Thank you for the clarification.

This is very interesting news about External Entity objects, because as far as I know Archive To Go fails with them in some way. Perhaps something has changed in GroupWise since the last review of these objects.

Could you verify the data exported from your External Entity objects, please? This would involve the following:

• Review the export log in the archive folder. Start with the summary, at the end, to check for any data access failures.
• Start the Viewer and browse a sample of messages (check plain-text and HTML formats, attachments) and contacts, if any.

Archive To Go excludes the following objects from the System view by default:

• External Entity
• External User
• External Post Office
• External Domain
• Non-GroupWise Domain

From your report it seems that we may need to review this default behavior. At present there is no way to make the System view list these objects.

Which version of the GroupWise client are you using? On the server side, which version of the Post Office Agent serves these objects?

For background, could you describe the business/technical reasons why you use External Entity objects as shared mailboxes, please?

If you prefer, you may reply to support@advansyscorp.com.

Regards,
Advansys Support

[This message was edited by Support 1 on September 06, 2010 at 06:24 PM.]

[ee61re]

Hi,

The exports of the problem maiboxes are fine, with no errors or problems – it is simply that system view does not show them, so we can only export one at a time.

We are using GW client and server 6.5.

In terms of the reasons behind using external entity, I’ve no idea (I’m an external consultant), but I suspect it maybe due to these users / mailboxes not actually needing a Novell network login, just a mailbox, and by using External Entity, it doesn’t use a Novell license, perhaps.

[Support 1]

Thank you for the additional information.

I have added an item about this issue to the Archive To Go enhancements list. To assist our engineers in improving the product, please provide the following details about the External Entity objects:

• How many do you need to export?
• Do they belong to an external Post Office?
• Do they belong to an external Domain?
• Do they belong to a foreign (non-GroupWise) Domain?

I look forward to your reply.

Regards,
Advansys Support

[Author]

Replies