AppController upgrade from 2.0 to 2.5 / 2.6 release Sync behavior.

AppController upgrade from 2.0 to 2.5 / 2.6 release Sync behavior. -

AppController needs 3 mandatory fields information of a user from Active Directory, which include Name, Last Name and Email to retrieve user information in its database. Two different lists in the AppController database which include

AppController maintains two lists in its database:

i) List Master of users

ii) a list of user ID (which contains the samAccountName attribute. value)

in 2.5 and above release AppController if any of the 3 above required fields are missing in active Directory for user , AppController do not put that user information in its local database and will not show users information Managing user portal. This results in the user can not access the applications receiver

Upgrading from 2.0 to 2.5 or version 2.6

Problem: .. L the user can not see the AppController applications in one of the receivers. Also the user information does not appear in Manage AppController user portal despite manual execution or forced synchronization.

Of the two tables above, incase one of the 3 mandatory fields of a user are missing then only list user ID has been updated and are not Master Users List in AppController v2.0 .This was a behavior v2.0 AppController. All new users or update information in Active Directory was shot by AppController using its midnight daily synchronization or performing manual synchronization.

AppController after initial recovery is about 2.0 and is upgraded to 2.5 or version 2.6 synchronization behavior changes. New version of AppController replaces the daily automatic synchronization with the sync motor delta, which after a few minutes in contact with the AD and only pulls the update, and recently added user information rather than do a full synchronization.

Delta In Sync When AppController synchronizes with Active Directory on a periodic basis AppController seems that for the changes to Active Directory instead of synchronizing with the entire directory. This process results in much faster performance in earlier versions of AppController

During the first synchronization process :.

If one of the three required attributes that include: Name, Name, Email are missing and delta synchronization does not occur

Name	LastName	Email	Delta Sync
√	√	√	√
√	√	X	X
√	X	√	X
X	√	√	X

once first time synchronization process is complete, if one of the required attributes are changed 3 AD synchronization delta automatically synchronize information in the user.

FirstName	LastName	Email	Delta Sync
changed	NotChanged	NotChanged	√
changed	NotChanged	changed	√
NotChanged	changed	changed	√
changed	NotChanged	changed	√
changed	changed	NotChanged	√

therefore, snacks upgrade from v2.0 to v2.5, if there is information about the missing field of 3 required mandatory fields then we do not see that users information in the list of remote users.

This is a case of angle and that is observed when AppController is updated from 2.0 to 2.5 and above. Post 2.0 of AppController no similar problem and we can safely assume that all users with Name, Last Name and E-mail address will be able to see their respective applications in the receiver, they have the right of access.

If for one of the users, first name or name or email address is missing in the subsequent addition of the missing information in AD, will be synchronized delta for AppController.

Solution

We have two solutions to solve the problem if the upgrade is performed from 2.0 to 2.5 or 2.6 versions:

1. make a temporary change in the e-mail address for users in AD and allow synchronization delta identify the change and make the record in AppController. Once the record shows in AppController, we can return the change of email address in AD for the user.

1. Delete user id information from an arrays of AppController and do a manual sync ie Update from Active Directory Control Point option

NOTE : .. We recommend you use the first workaround rather than going directly to the DB

Tweet