This Guide is intended to serve as a quick, yet detailed introduction to iManager for your new staff who may be unfamiliar with iManager. It can also serve as a desktop reference. It is ideally aimed as a guide to transitioning from ConsoleOne to iManager.
You should already know how to start iManager. Basically, using a browser, you enter the following path to a NetWare server that has iManager installed: https://
Configuring iManager for your Site and to your Preferences
You will most likely want to configure iManager to make it easier to use for how you use it. Be aware that only an iManager Administrator can do this. (When TSNOV is notified of new FICCs, we set them up to be iManager Administrators; they can then make other users Admins.) Later on, after this configuration section is done, you will see how an iManager Admin can promote other staff to also become iManager Admins.
When you first start iManager, you are presented with the generic Home page shown below.
Note: Do not install the new iManager NPMs without contacting your Help Desk. For example, if you install new IDM NPMs before upgrading to IDM 3.5x, you may break IDM manageability.
1. Click the Configure icon.
2. Click iManager Server.
3. Click the Configure iManager link.
The iManager configuration screen appears:
Next, you need to set the system to begin looking for your credentials to log you in. By default, it starts at the top and searches down until finding your container. This takes time, especially if your WAN links are saturated or down.
1. Click the Authentication tab.
2. Change the radio button from “Search from root” to “Search Containers”.
3. Click the Browse/Search icon to browse to your container
By default, until you set it otherwise, the Browse and Search features start at the [Root]. You probably do not want that.
4. Use the Down Arrows to drill down until desired container is visible.
5. If your container does not show up, click Next to show more containers. Note the number of items displayed per page.
6. Click on the line under your container to have it appear in the Selected Objects box.
7. Click OK to finish.
Next, you should check to make sure you are not authenticating (logging in) any farther away, which is more time-consuming than is necessary. Verify that the iManager login does not start all the way across the WAN at your Central Office.
8. Select “Search containers” – not “Search from root”.
Your selected container should already appear in the “Containers to Search” box.
9. If it is not in the “Containers to Search” box, find it by clicking the History icon or the Browse icon at the right.
10. Click Save, then Close.
Next, you can configure how iManager works, and how it loads each time. You can specify whether iManager uses Search or Browse mode by default, how many objects at a time are displayed in either mode, and in which mode iManager presents.
For example, you might like to set up “Favorites” with the functions you use most frequently.
To have Favorites be your initial view,
1. Click the Preferences icon at the top of the tab.
2. Click Manage Favorites.
3. Select the tasks you want from the Tasks dropdown list. You can add as many tasks as you use want, but too many can make it cluttered and less useful.
4. Click the left arrow, between the two dropdown lists. They will be listed under Favorites.
5. You can optionally check the box for “Make favorites my initial view”.
6. Click OK.
NOTE: You can still access tasks that are not in your Favorites by selecting Roles and Tasks.
Now when you click Favorites, just the tasks you use most frequently appear. Also, if you have selected it to be your initial view, they will display when you first start iManager.
Note: “Favorites” settings are user-specific. Thus, each iManager user will need to set his/her own.
You may want to have the default action when you click on the magnifying glass to be “Search” rather than “Browse”, and you will likely want to increase the number of objects displayed at a time.
7. Decide if you want to increase the number of “Results Per Page:” from the defaults of 22 and 14, to something like 96 and 64. Experiment for what works best for you.
8. Set the context to always start from your container, which will be the “[Root]” or “O” context level if you are an admin for an entire tree, or the exact OU context for which you are responsible and have rights to.
I suggest you change the “Starting Context:” to be “Always:” and set to your container.
9. Click Preferences.
10. Click the Object Selector link.
11. Set the Startup Mode to your preference of Browse or Search.
12. Click OK twice.
13. Click Object View. You’ll probably want to leave the Results per Page at the default value.
14. Change the Starting Context as you did before.
Note: You should be able to select your context by clicking the History icon, since you browsed to it earlier.
15. Click OK twice.
This completes configuring iManager to your preferences.
Assigning Roles and Tasks to Staff Members
As the Department or Enterprise Admin, you probably want to delegate many of the day-to-day tasks to your staff, and you may want to make other members of your staff iManager Admins. So now we’ll cover assigning roles or tasks to the people that will be working with it every day. Again, you must be an iManager Admin to perform this function.
1. While still on the Configure page, click Role Based Services.
2. Click the Edit Member Association link. The Member box appears.
3. If the user you want to assign roles and tasks to is in History, you can select it by clicking the History icon. Otherwise, click the click on the Browse/Search icon.
Note: Some of the following screenshots are a nod to those of you who use Firefox as your browser, so you can see it works, and how similar it looks. IE users, understand all selections look very similar and act the same – only the skin is different.
1. Browse to the user’s container and select the user, or do a search on the user ID. The example below shows browsing for the User ID:
The container (OU) you are currently in is listed in “Look in:” Click on a blue down-arrow to drill down into
sub-containers, or the up-arrow to go up one.
This example shows searching for the User ID:
a) Click the Search tab.
b) Check the “Search sub-containers” box. If you have previously set your initial Search context as described, you are set; it will show up in the “Start Search in” box.
c) In the “Search for objects named” box, you can search on the full ID or a partial ID using the asterisk * as a wild card.
d) Click Search to display the object you want in the Results pane.
You’ll find that if you know the object’s name, it’s faster and easier to search rather than to browse. Either way, once you find the user,
2. Click on the User Object in the right pane to select the User ID you want to give Roles and Tasks to.
3. Click OK.
The Edit Association window appears:
You will assign at least one role and scope. For this, you will find Browse works better. However, you should be able to find the object already in History.
4. Select the Scope, which you define as your container.
5. Your container is probably in History. If so, click the link to add it.
6. Without leaving this screen, browse to the RBS Collection so you can select Roles and Tasks.
7. If the user is not in History, click the Browse tab to find desired container.
Your starting context is displayed in the “Look in” box. It should be focused to your beginning OU.
8. Find the User you want to assign the Roles/Tasks to and click the correct underlined entry – NOT the Container Name.
The user appears in the Selected Objects pane.
9. Click OK to return to the Edit Member Association window.
Whether thru Browse or Select, the selected scope appears in the Scope box. Note: This user already had one role assigned; next you will see how to add one or more roles.
10. Click the Search/Browse icon.
11. Browse to the desired RBS Collection and click the Down arrow.
This next screen appears.
The PC-mouse-like icons denote Tasks. You will not select Tasks here, although there are a lot of them. This is one good reason to increase the number of objects per screen past the default of 14, as mentioned earlier, or you’ll be clicking Next a LOT. You can use the scroll bar on the right to view additional tasks.
12. Click Next to proceed to the next screen of objects.
13. Look for the Roles icons, which may remind you of driver’s licenses. Keep using the scroll bar and click Next until you get to the role you want.
In this example, you want this staff member to have the “Help Desk Management” Role.
14. Click the Help Desk Management role, and it will appear in the Selected objects box.
15. To add more Roles, do it the same way. All selected roles will also appear in the Selected objects box.
16. When you are done, click OK.
The Role and Scope information appears. If you chose more than one role or scope, you could see them by clicking the drop-down box arrows.
17. Click Add.
18. Click OK. Don’t forget this step!
Carefully note the next screen:
If you want this staff member to be able to manage all sub-containers – such as a USERS.COOL.NOVELL container – make sure “inheritable” is set to “subtree”. This is the default.
19. Click OK. Important: Be very careful to do this before leaving this screen, or you will lose your changes.
This completes setting up a staff member with iManager access. If you have other staff to configure to have access, then click Repeat Task as shown below.
Adding Other iManager Admins
Now it’s time for you to add other iManager Admins.
1. In the Configure window, click the Configure iManager link under iManager Server.
Remember: as Admins, these staff members will be able to do everything you can do. This includes removing access to any user.
You will see a familiar screen:
2. Make sure you are on the Security tab.
3. Click the Search/Browse icon to look for this user.
It is likely you will know what this user ID is, so doing a search is easier than browsing.
4. Whichever method you use to find this ID, click the user to add it to the Selected Objects.
5. Click OK.
The user is added to the “Authorized users” box. You will not see any indication that anything has happened.
So to verify the desired results, click the drop-down arrow and look for that ID.
6. Click Save. Important: Don’t forget to do this!
At this point, you should see the Success message:
7. If there are other staff members you want as Admins, repeat the above process.
iManager USAGE Overview; Simple User Management
Now you are ready to actually use iManager for User Management tasks. Click the Roles and Tasks button, or the “Favorites” button – if you have it configured – to start using iManager.
User Creation and Deletion
1. Be sure you are in Roles and Tasks.
2. Click Users and select a task you want to do. We’ll choose Create User for now.
If you use these often, consider adding them to your “Favorites” page.
You can use your old templates with iManager. While in Create User,
3. Fill in all the necessary information.
4. Click on the “Copy from template or user object” box and browse to your Template Object(s).
User Management with iManager – it’s as simple as that.
Note: If you are using Identity Manager to automatically create GroupWise accounts, you MUST make sure the template has all GroupWise information cleared. Contact your Central Office Support Staff, through your Help Desk.
Now, you can have a User Home Directory auto-created – often known as the “H:” or “U:” drive.
5. Check the “Create home directory” box.
6. Browse to the Volume where your USERS folder is – try VOL1: The User ID is automatically inserted in the Path box.
7. Ensure that “USERS\” (or whatever you have defined to be home base) precedes the UserID. If necessary, type it in manually.
8. When you’re done, click OK.
Modifying a Template Under iManager
1. To modify a template, click Modify Object under Directory Administration.
Note: If any templates are set to create a GroupWise account, you will need to change that once your site has been converted to automatically create a GroupWise account via IDM/DirXML rules, when an eDirectory account is created using iManager. Otherwise, the GroupWise account will not get created. You can tell if this is so by looking at the properties of the template.
2. Click the GroupWise Information tab. If there is a Post Office listed, the template needs to be changed.
3. To remove PO references, click the Other tab and delete all “email address” and “NGW:” keys.
Browsing To The Template
Remember to check the History first – if the template is there, you can simply select it.
1. Select the template you want. The Modify Object window appears.
2. Click OK.
3. Fill in or edit the information.
Pay special attention to the “Restrictions” tab. You probably want to force more than a 4-character password.
4. When you’re done, click Apply and then OK.