How to use Remote.exe to establish a Remote Control session in Systems Management Server 2.0 and in Systems Management Server 2003
This article was previously published under Q201793
You can use the Remote.exe command-line tool to start a Remote Control session with a Microsoft Systems Management Server (SMS) client.All the Remote Tools functions that are available by using the user interface are also available from the command line when you run Remote.exe to establish a Remote Tools connection. This is useful when you develop programs that require the functionality in SMS Remote Tools.
By default, Remote.exe is located in the %SystemRoot%\SMS\Bin\I386 folder on a primary or secondary site installation. On a computer where only the SMS Administrator console is installed, Remote.exe is located in the %SystemRoot%\SMSADMIN\Bin\I386 folder.
Use Remote.exe with the following syntax:
remote address_type address \\site_server_name\Theaddress_type parameter can have the following values:
- 0 for SMS Resource ID
- 1 for IPX
- 2 for TCP/IP
- 3 for NetBIOS
Note You can also access syntax information by typing remote.exe /? at a command prompt.
The following are two examples of the correct command-line syntax:
remote 2 172.16.0.0 \\big_server\NoteIn SMS 2003, the IPX and the NetBIOS address types apply only when you want to connect to SMS 2.0 clients. SMS 2003 clients use only TCP/IP connections.
remote 3 dubn_netbios \\big_server\
remote 3 dubn_netbios \\big_server\
When you use Remote.exe, the resource that you specify is always resolved to a resource ID in the SMS database. SMS object security is scanned to determine if the user has the permissions to remotely control the resource. The available remote control features depend on SMS resolving the computer address that you supply, instead of on how security controls are applied.
To establish a Remote Tools connection, you must have the Use Remote Tools permission and the Read permission for the collection that contains the client. If you are not a local administrator, your domain account must also be included in the Permitted Viewers list. To add your account to the Permitted Viewers list in SMS 2003 and SMS 2.0, follow these steps:
- In the SMS Administrator Console, expand the Site Database\Site Hierarchy\Your Site\Site Settings node.
- Click Client Agents, and then double-click Remote Tools Client Agent.
- Click the Security tab, and then click the Add button.
Note The Add button displays a yellow star.
- Type your domain account, and then click OK two times.
315755 Remote Tools may connect to the wrong Systems Management Server clientSMS 2003 does not retrieve the IP address from the SMS database. SMS 2003 instead uses either the IP address that you supply or resolves the computer name to an IP address by using WINS name resolution requests.
You can connect to a client by using its resource ID. To do this, use the following command syntax, where site_server is the NetBIOS name of your site server:
remote 0 <Resource_ID> \\site server\The following is an example of the correct command-line syntax:
remote 0 2 \\big_server\When you use a resource ID, Remote.exe tries to connect by using all the available protocols for the destination client. To determine the resource ID of a client, follow these steps:
- In the SMS Administrator Console, open a collection.
- Right-click the client computer, and then click Properties.
http://www.microsoft.com/downloads/details.aspx?FamilyID=58833cd1-6dbb-45bb-bb77-163446068ef6&DisplayLang=enIf you use Remote.exe without any command-line options, the Remote Tools Address Connection dialog box appears. Click the address type that you want to use, and then type the address.
After you configure the parameters, click OK to connect to the client. A connection to the client is established if all the following conditions are true:
- The Remote Control Agent (Wuser32.exe) is running on the client.
- The SMS Administrator Console and the client share a common network protocol.
- The SMS security permissions are configured correctly.
For more information about Remote Tools security, see one of the following documents:
- SMS 2003 Microsoft Systems Management Server 2003 Concepts, Planning, and Deployment Guide: Part 2, Chapter 5, "Understanding SMS Security"
- SMS 2.0 SMS Administrators Guide: Chapter 4, "Creating your SMS Security Strategy"
Article ID: 201793 - Last Review: 02/27/2007 23:10:16 - Revision: 5.2
Microsoft Systems Management Server 2.0 Standard Edition, Microsoft Systems Management Server 2003
- kbinfo kbremoteprog KB201793