I see where I can disable access to Integration Manager and Table Import. I also see where I can restrict access to the Integration Site Enabler. None of our users have access to these, yet they have access to "Run Integration." This was an issue on Dynamics 10 and is still the same on Dynamics 2013.
How do I restrict a user from accessing Run Integration other than removing INtegration Manager from the set file (we are on citrix so it's not like we can just not install Integration Manager).
You will need to use VB Script to require a password before the integration can be run.
Kind regards,
Leslie
Leslie Vail, CPA, MVP, MCT, MCITP, MCP, MCITSASCI, Inc. * PO Box 600965 * Dallas, TX 75360 * 972-814-8550 * leslievail@earthlink.net
I'm confused. The "Run Integration" is a menu item. Why can it not be restricted/allowed for certain users? We have over 25 integrations. I can't really be expected to have to password protect them all and maintain all these passwords.
I think this will work on Citrix, based on installed I have done in the past on Citrix.
The location of the integration database is stored by the user in Citrix (not sure if in registry or in user specific files). Anyway, log in via Citrix as the user that you want to deny the ability to run integrtions to.
Pull up integration manager and go to Tools>Create Database. Create a blank IM database. Then, Tools>Options and point to the newly created IM Database which is empty.
So, I believe what you will wind up with is, that users you want to allow to run integrations will be pointed at the real IM database and others you don't will not see any integrations to run.
Test this approach and see if it works. No promises.
Warren
Hi Mebenz,
We'll come up with something for you :)
Do you want some users to have the ability to run certain integrations, but not all integrations, or is it an all or nothing situation?
We did use separate set files for users to get around this users but didn't want to do this with the new version. We want to be able to restrict the app completely for users and those with access could runwhichever ones allowed them to run (ie Dynamics security allows or resrticts the windows as we don't use eConnect).
We modified the integration manager ini file to point to the mdb file so we didn't have to do the location for every user. Plus we have 4 citrix servers in a farm so we'd have to repeat that if they happened to log onto another server.