Managing NMB

UFAD and Network Managed By (NMB) – How it works

"NMB is set by a department directory coordinator from the ‘Admin Menu’, launched within the portal. It is what places a user in a particular OU within UFAD. Regardless of what a person’s ‘Employee’ relationship is set to, NMB should be set to place them in an OU which is managed by their regular IT support group. For most this will match their ‘Employee’ relationship, but not all.

When NMB is set, it is stored in a DB2 table in the campus registry. UFAD manages a MS-SQL server that runs a DTS job every 15 minutes. This job reads in any NMB values that have changed and processes them, incorporating Microsoft Identity Integration Server (MIIS) in the process. NMB values are then compared against a SQL table that is maintained by UFAD. This table ‘maps’ each possible NMB value to a particular OU within the UFAD structure, then MIIS accomplishes the actual movement within UFAD.

When we request submission of any desired OU changes, what we are doing behind the scenes is altering our mapping table. If any NMB’s need to map to a different OU we simply change their mapping and re-harvest the user accounts to move them to the new OU. If an OU needs to be renamed, we programmatically create the new OU using the new name, change the NMB mapping to point to the new OU so that any future NMB changes go to the new location, re-harvest existing users and *manually* delete the old OU. This part of the process is done manually to ensure that all users have been moved to the new OU before the old OU is deleted from the UFAD tree. Nothing is ever deleted from UFAD without manual verification, although with CommVault now in place recovery from a mistake would be fairly simple."

See also:

• NMB handling on hire and fire

Problem:

Gatorlink user is not in UFAD or is in wrong OU. The symptom of this may be that they cannot login to UFAD, but they can in other Gatorlink services. You can confirm by doing a right clicking on ad.ufl.edu in ADUC (see Setting up an Admin workstation if you are lost already) and selecting find. Type in the Gatorlink name in the find box and click find. If the user does not display, this is likely the problem. If the user does display, the problem is likely a password synchronization issue. They should change their Gatorlink password to correct that.

Cause:

The Network Managed By Relationship is not there or correct.

Solution:

Please note that Directory Coordinators can perform the following function. DSAs can request this ability for OU Admins...

1. Login to http://my.ufl.edu
2. Click Quick Links from the menu on the left
3. Click Admin Menu from the menu on the left
4. Click Manage Directory Information
5. Enter the persons UFID in the Enter UFID box
6. Click Get Basic Info
7. Click Relate Person
8. Select Network Managed By from the Select Affilation pulldown
9. Click Lookup PS Department
10. Type in part of the name for your department
11. Click the Name of your department
12. Click Submit

Problem:

You have users in your OU who no longer work for your department.

Cause:

The Network Managed By Relationship is still set to your department for those users.

Solution:

First follow proper exit procedures. Then your Directory Coordinator may...

1. Login to http://my.ufl.edu
2. Click Quick Links from the menu on the left
3. Click Admin Menu from the menu on the left
4. Click Manage Directory Information
5. Enter the persons UFID in the Enter UFID box
6. Click Get Basic Info
7. Click the remove box next to all items under Network Managed By