Highlighted
sselaya
New Member.
1736 views

Moving Users from one OU to another breaks Mobility for user

We are segmented out our OU's based on departments in our eDirectory tree for different reasons. Anyway, last night we moved 130 users from one OU to another. About 25 of those users are using mobility. After the move their devices quit syncing. From the mobility console the user and device dissapeared both from the mobility view as well as the groupwise view. We use a group to manage adding users to mobility. The users will still in the group with correct context. The only way we could get the users to sync again was to remove them from the group, allow the group to be polled by the mobility server (I assume at this time mobility deleted the user from the system even though we could not see the user anymore from the console) and then we readded the user back to the group and once again had the mobility server poll the group.

We learned the hard way, but I have no idea why mobility could not figure this out on its own. As removing and adding the users back in was a tedious process.
Labels (1)
0 Likes
3 Replies
jmarton2 Absent Member.
Absent Member.

Re: Moving Users from one OU to another breaks Mobility for user

sselaya wrote:

> We are segmented out our OU's based on departments in our eDirectory
> tree for different reasons. Anyway, last night we moved 130 users
> from one OU to another. About 25 of those users are using mobility.
> After the move their devices quit syncing.


I believe this is a known issue. I'll see what I can find out.

> From the mobility console
> the user and device dissapeared both from the mobility view as well
> as the groupwise view. We use a group to manage adding users to
> mobility. The users will still in the group with correct context.
> The only way we could get the users to sync again was to remove them
> from the group, allow the group to be polled by the mobility server
> (I assume at this time mobility deleted the user from the system even
> though we could not see the user anymore from the console) and then
> we readded the user back to the group and once again had the mobility
> server poll the group.


Just curious, before/after the move, where the users' containers
defined in Mobility's LDAP settings? I know the group was, just
curious about the users.

--
Novell Knowledge Partner
Enhancement Requests: http://www.novell.com/rms

Joe Marton Emeritus Knowledge Partner
0 Likes
ukrause Super Contributor.
Super Contributor.

Re: Moving Users from one OU to another breaks Mobility for

You may use Groups as a workaround. As the engine will store the LDAP DN of a User in the database, a move will never make it. So one idea is to remove the user from all connectors, move him and bring him back to the connectors. The other way should be putting the users in groups. As the group membership is (in contrast to users) regularly checked (LDAP Polling intervall), it will update the DN by removing the "old" and adding the "new" automatically.
0 Likes
jmarton2 Absent Member.
Absent Member.

Re: Moving Users from one OU to another breaks Mobility for user

ukrause wrote:

> You may use Groups as a workaround.


The original poster is using groups, yet it still broke.

"We use a group to manage adding users to mobility. The
users will still in the group with correct context."

--
Novell Knowledge Partner
Enhancement Requests: http://www.novell.com/rms

Joe Marton Emeritus Knowledge Partner
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.