Connecting to a Remote Integration Services Server
Connecting to an instance of Integration Services on a remote server, from SQL Server Management Studio or another management application, requires a specific set of rights on the server for the users of the application.
To manage packages that are stored on a remote server, you do not have to connect to the instance of the Integration Services service on that remote server. Instead, edit the configuration file for the Integration Services service so that SQL Server Management Studio displays the packages that are stored on the remote server. For more information, see Configuring the Integration Services Service.
To connect to Integration Services on a Remote Server
Open SQL Server Management Studio.
Select File, Connect Object Explorer to display the Connect to Server dialog box.
Select Integration Services in the Server type list.
Type the name of a SQL Server Integration Services server in the Server name text box.
The Integration Services service is not instance-specific. You connect to the service by using the name of the computer on which the Integration Services service is running.
The Browse for Servers dialog box does not display remote instances of Integration Services. In addition, the options available on the Connection Options tab of the Connect to Server dialog box, which is displayed by clicking the Options button, are not applicable to Integration Services connections.
When a user without sufficient rights attempts to connect to an instance of Integration Services on a remote server, the server responds with an "Access is denied" error message. You can avoid this error message by ensuring that users have the required DCOM permissions.
To configure rights for remote users on Windows Server 2003 or Windows XP
If the user 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.
Open Control Panel, double-click Administrative Tools, and then double-click Component Services to start the Component Services MMC snap-in.
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.
Select the DCOM Config node, and then select MsDtsServer in the list of applications that can be configured.
Right-click on MsDtsServer and select Properties.
In the MsDtsServer Properties dialog box, select the Security tab.
Under Launch and Activation Permissions, select Customize, then click Edit to open the Launch Permission dialog box.
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.
Click OK to close the dialog box.
Under Access Permissions, repeat steps 7 and 8 to assign the appropriate permissions to the appropriate users and groups.
Close the MMC snap-in.
Restart the Integration Services service.
To configure rights for remote users on Windows 2000 with the latest service packs
Run dcomcnfg.exe at the command prompt.
On the Applications page of the Distributed COM Configuration Properties dialog box, select MSDTSServer and then click Properties.
Select the Security page.
Use the two separate dialog boxes to configure Access Permissions and Launch Permissions. You cannot distinguish between remote and local access - Access permissions include local and remote access, and Launch permissions include local and remote launch.
Close the dialog boxes and dcomcnfg.exe.
Restart the Integration Services service.
SQL Server Integration Services does not support the delegation of credentials, sometimes referred to as a double hop. In this scenario, you are working on a client computer, Integration Services is installed on a second computer, and SQL Server is installed on a third computer. Although SQL Server Management Studio successfully passes your credentials from the client computer to the second computer on which Integration Services is running, Integration Services cannot delegate your credentials from the second computer to the third computer on which SQL Server is running.