Experiences with access rights in the portal and manual restart of the Cache builder service
We have a lot of impatient users who would like to have access to certain requests in the portal asap. According to the KB article, some changes are synchronized to the portal DB every 2 hours, others get synchronized every 24 hours. Which kind of acess rights belong to which action?
- adding an AD Group to a user role in Service Manager
- adding a user to an existing group in AD; this group or its nested group already has permissions in the portal
- creating a new AD group and add it to a group that has already permissions in the portal
What effect has the manual restart of the Cache Builder Service?
This morning, I added an existing AD group to a user role in Service Manager and restarted the Cache Builder service. This group already has access to incident work items and certain requests, but they want to have access to some new requests being available on the portal for about 3 weeks now. Even after 4 hours, those requests are still not visible to the user in question, he can only see the older requests. He even restarted its machine to make sure that nothing is left in the browser cache.
Are we all to impatient? I thought, restarting the Cache builder service would speed up the access rights. Does it take longer than expected? I would be glad to get a good explanation, so I can tell the users that they probably have to wait until the next day. I'm tired of restarting the service with obviously not the expected effect. The users are unsatisfied and so I'm I after telling them to try again and again and again.....
Thanks for your tipps.