Share File and XenMobile are undoubtedly the industry leader in the EMM and the EFSS room and together they allow any company to really their workforce to mobilize. At Citrix, we only work hard not to make these products great individually, but also integration, to ensure that these products make a natural fit for each other and seamlessly use another skill. Read the blog here for more forward on some of these consumer integrations between Share File and XenMobile.
However, limited integration efforts not only to the consumer facing functions. Currently, for customers using a standalone Share File deployment, user provisioning management tool can be managed either manually or via the user. However, when running customers Share File in conjunction with XenMobile, we have the user provisioning process streamlines of Share File User Provisioning to integrate by AppC. If the relevant Share File Super-user is configured with administrative privileges in the AppC Docs tab, the user accounts are created automatically for roles in the Share File-level control, which are associated to Share File.
Provisioning with AppC
[1945001DieserBeitrag] aims at demystifying the provisioning process when AppC is used as a provisioning process. It explains what from the time the user goes to the Active Directory (AD) is added, is provided by the time the Share File account for the user. To learn, to two activities, one of which to be aware of the provision sequence drive:- The AppC-AD Delta Sync - The AppC performs a synchronous operation with AD every 5 minutes on the clock (12:00, 12:05, 12: 10 ... etc.). At this point the AppC checked for all users that have been added / deleted AD or users who have changed their membership and make appropriate updates to the database
- The deployment task timer. - This timer runs every 15 minutes on the clock (12:00, 12:15, 12: 30 ... etc.) and look for the list of users in AppC that must be provided in Share File. Once the AppC has a list of users that it needs for the provision, it is planning a deployment task with a delay of 15 minutes, at which point the user in Share File provided.
The flow chart below shows the flow of the provisioning process
This process can be best understood with an example scenario.
- 03:32: Assume that a new user ( u_demo1 ) created in AD and an AD group, one Ticket configured role in the "Docs" tab of AppC
- 03:35 .: in this 5 minute interval on the clock, AppC Delta will run synchronously with AD and learn that u_demo1 is a newly created user. , Assume that a second user ( u_demo2 ): At this point AppC the user will add to its own database
- 3:36 is created in AD and an AD group assigned .: in the AppC
- 15:39 Docs tab to a configured role that one third Adopted. Users ( u_demo3 ) in AD and an AD group in the AppC Docs tab configured to a role cards
- 03:40: this 5-minute interval on the clock, AppC is again delta synchronization run with AD and learn that u_demo2 and u_demo3 are both new users. At this point adds AppC both the users own database
- 15.45 .: In this 15-minute interval on the clock, the deployment task timer runs for changes in the AppC user database to check. AppC understands that u_demo1 u_demo2 and u_demo3 belong to a role that is configured in the Share File Docs tab, and that all three users must be provided in Share File , , is AppC with a 15-minute delay determining these users
- 04:00 a deployment task plan: The 15 minute delay timer expires and AppC provisions u_demo1 , u_demo2 and u_demo3 in Share File
time of user creation for provisioning .:
- u_demo1 - 28 min
- u_demo2 - 23 min
- u_demo3 - 21 min
Hopefully this clarifies some questions about Share File User provisioning with AppC. Whether you are AppC or UMT used to provision users, includes the process of communication between AD, AppC and Share File-control plane. In those cases, if the process is not complete, users see certain error messages when they try to log their Share File accounts.
Common errors and how to
to solve 1. subscription required
seen this error when a user has been provided in the Share File had either manually or by the UMT but the AppC has no chance to reconcile the user. This error can also occur if the user has not yet been synchronized in the database AppC of AD. The snapshot shows a view of the user both in Share File and AppC when the user is not reconciled.
resolution : matching the user with the appropriate domain account in AppC. Then can choose takes place manually synchronize on the Docs tab or wait to run to the car reconciliation process every night 02.00 either the administrator.
2. Your account will be setup
This scenario is likely to occur if AppC for providing is used by File Share users. This occurs when the user of AD has been synchronized in the AppC database after the 5-min Delta Sync, but has not yet been provided in Share File.
Resolution: [1945010Warten] are brought for providing task timer for providing the user in the Share File control plane and the user in AppC consistent
3. account has been disabled
seen this error when the user account was provided in Share File and has also in AppC, but the user status to "Disabled" in the Share File-control plan will be reconciled.
Resolution: Re-enable the user to Share File
0 Komentar