1. Very important
If the user/group is not a member of the local Administrators group, add the user to the Distributed COM Users group. You can do this in the Computer Management MMC snap-in accessed from the Administrative Tools menu.
2. Give user/group remote Launch and activate permissions, so that they can connect from there machines to the SSIS server.
Open Control Panel, double-click Administrative Tools, and then double-click Component Services to start the Component Services MMC snap-in.
3.
Expand the Component Services node in the left pane of the console. Expand the Computers node, expand My Computer, and then click the DCOM Config node.
4.
Select the DCOM Config node, and then select MsDtsServer in the list of applications that can be configured.
5.
Right-click on MsDtsServer and select Properties.
6.
In the MsDtsServer Properties dialog box, select the Security tab.
7.
Under Launch and Activation Permissions, select Customize, then click Edit to open the Launch Permission dialog box.
8.
In the Launch Permission dialog box, add or delete users, and assign the appropriate permissions to the appropriate users and groups. The available permissions are Local Launch, Remote Launch, Local Activation, and Remote Activation. The Launch rights grant or deny permission to start and stop the service; the Activation rights grant or deny permission to connect to the service.
9.
Click OK to close the dialog box.
10.
Under Access Permissions, repeat steps 7 and 8 to assign the appropriate permissions to the appropriate users and groups.
11.
Close the MMC snap-in.
12.
Restart the Integration Services service.
13. If you cannot add a package or migrate it to server. Try adding user to msdb database and give read and write permissions.
Some other things to keep in mind are replace . by servername\instance in the file MsDtsSrvr.ini.xml on that server
