Cool Solutions

Dealing with Problems Creating GroupWise Accounts via IDM



By:

December 18, 2007 12:34 pm

Reads: 3328

Comments:0

Score:0

Problem

GroupWise accounts are intermittently not being automatically created through IDM; this happens even though all the rules seem to be set up properly to automatically create GroupWise accounts when a User account is created with iManager. If Active Domain (AD) accounts are also set to be created by IDM, that is working fine. Synchronization of all values to AD, as well as to GW in other containers, is working fine. In some instances, automatic GW account creation through IDM (formerly DirXML) works flawlessly; in some, only sporadically; and in some cases, not at all. The process may even be working for other User IDs created by the same Admin in the same OU (container) on the same day.

User creation, as per Novell recommendations, and mandated by management has been changed from ConsoleOne to iManager. Container Administrators, even Tree Administrators, are employing User Templates previously defined for use with ConsoleOne, but they are now being used through iManager. Many, but not all, of these User Templates have a Post Office definition under the GroupWise “Information” tab.

Cause

You cannot have IDM and a template, even through iManager, fighting over what creates the GroupWise account. They will both back off, call it a draw, and neither will create it.

Solution

A) The easy, non-responsive – and unlikely to succeed – way is to delete the templates and tell the Container Admins to create new templates without any GroupWise information. If YOU are the only Container Admin, and you need to make other drastic template changes, maybe this is your option.

B) If the above is not the case, you need to modify the existing templates. You do need ConsoleOne for this.

1. In the container where you are having problems, do a search for Object Type: Template.

2. Make sure you checkmark Search Subcontainers.

3. Bring up the Properties of the template.

The first thing you will find is there is no way to remove the PO information under the GroupWise tab. Indeed, you cannot even modify it. So what do you do?

4. Click the Other tab.

5. Checkmark the “Show read only” box.

6. Highlight and delete every attribute that starts with NGW:*. You will only be able to delete one at a time.

7. When all NGW attribute entries are gone, click Apply, then Close. (See Note: below.)

8. Wait a few seconds, then open Properties of this template again to make sure there is no “Post Office” information – that this box is blank under the GroupWise Information tab.

Visibility will probably show up as Post Office; let not your heart be troubled, as this is OK.

9. Make sure you tell your Container Admins to quit ConsoleOne and iManager, then restart iManager before attempting to create any more users.

10. For good measure, it is not a bad idea to have them reboot their PCs, as well.

Note: There are also advocates of deleting the Attribute “EMail Address”. I have not found it to be necessary, yet neither have I found it to be harmful. I recommend leaving it alone at first. If you still find GW accounts are not automatically being created, by all means try deleting it.

Side Note: Of course, you will get increased calls from your Container Admins asking, “why, Why, WHY! can’t we keep using ConsoleOne and our templates!” <sniff>. Unfortunately, we can tell them to just Embrace the Web, Get a Life, and Deal With It, but that never works.

Environment

- Netware 6.x
- IDM 3.x
- iManager 2.5+
- ConsoleOne 1.3.6x
- Groupwise 7.x

VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

Categories: Uncategorized

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

Comment

RSS