Re: Launching SMS 2.0 Remote Tools from a Command line?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Stan White [MS] (stanwh_at_microsoft.com)
Date: 02/23/04 

Date: Mon, 23 Feb 2004 07:56:21 -0800

remote.exe can be used to RC machines outside of the SMS console:

The content below describes that process.
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/sms/sms2003/maintain/operate/opsguide/ops_9vqm.asp

Establishing a Remote Tools Connection by Using Remote.exe
All Remote Tools functions are also available by running the Remote.exe
program directly from the command line to establish a Remote Tools
connection. This is useful if you are developing applications that require
SMS Remote Tools functionality.

This program is located in the %SystemRoot%\SMS\Bin\I386 directory for a
primary or secondary site installation, and in the
%SystemRoot%\SMSADMIN\Bin\I386 directory for an SMS Administrator console
installation.

Remote.exe uses the following syntax:

Remote <Protocol_Type> <Address> \\<Site Server Name>\ [/SMS:NOSQL]

Where:

  a.. Protocol_Type is 1 for IPX, 2 for TCP/IP, or 3 for NetBIOS.
  Note

    a.. A value of 0 introduces a special case, described later in this
section.
  a.. Address is a valid IPX network number, IP address or client name, or
NetBIOS name.
Examples:

C:\SMS\BIN\I386> REMOTE 2 172.16.0.0 \\BIG_SERVER\

C:\SMS\BIN\I386> REMOTE 3 DUBN_NETBIOS \\BIG_SERVER\

  Note

    a.. The Internetwork Packet Exchange (IPX) and NetBIOS protocol types
apply only when you conduct remote sessions on SMS 2.0 clients. SMS 2003
clients use only TCP/IP.
  a.. Site Server Name is the site server name of the site to which the
client belongs.
When you use Remote.exe with an explicit Protocol_Type of 2 (TCP/IP), SMS
resolves a client name to its IP address and then uses that address to
attempt a connection. Name resolution is not attempted when you use
Remote.exe with an explicit Protocol_Type of 1 (IPX) or 3 (NetBIOS).

When you use the following syntax: Remote 0 <Resource_ID> or Remote (with no
options), Remote.exe attempts a connection for all available protocols. To
determine a client' Resource ID number, right-click a client in the SMS
Administrator console under Collections, and then click Properties. The
Resource ID field for the client appears in the <Client> Properties dialog
box. You can also obtain a client's resource ID by using a custom query run
through Windows Management Instrumentation (WMI).

To connect to a client by using its resource ID, use the following command
syntax:

Remote 0 <Resource_ID> \\<Site Server Name>\

Example:

C:\SMS\BIN\I386> REMOTE 0 2 \\BIG_SERVER\

When you use 0 in the first parameter, Remote.exe attempts to connect by
using all available protocols for the target client.

The Site Server Name parameter is the site server name for the site to which
the client belongs.

The SMS:NOSQL option is used in place of the Site Server Name option to
allow direct connection to the client without using data in the SMS site
database. This is useful if the client's name resolution is not current, or
if the client's IP address is not updated in the SMS site database. An
address type of 0 is not valid when used in conjunction with the SMS:NOSQL
option.

Example:

C:\SMS\BIN\I386> REMOTE 2 172.16.0.0 /SMS:NOSQL

If you use Remote.exe with no command-line options, the Remote Tools Address
Connection dialog box appears. You can use this dialog box to enter the
following parameters:

  a.. Address type (NetBIOS name, IP address, or IPX address)
  b.. Address (any valid NetBIOS name, IP address or client name, or IPX
network number)
When you have entered the parameters, click OK to connect to the client. A
connection to the client is established if the following conditions are met:

  a.. The Remote Control Agent (Wuser32.exe) is running on the client
  b.. The SMS Administrator console and client share a common protocol
Note

  a.. SMS 2003 Remote Control clients listen only for TCP connection
attempts. NetBIOS and IPX connections are made by Remote.exe for backward
capability with SMS 2.0 clients. 

-- 
Stan [MSFT]
--
--
This posting is provided "AS IS" with no warranties, and confers no rights.
--
--
"Jim Davie" <jdavie@tampabay.rr.com> wrote in message
news:Wxa_b.110219$B81.533761@twister.tampabay.rr.com...
> Is there any way to call the MS SMS Remote Tools (allows for remote
control,
> remote, reboot, etc.) from a command line?
>
> For example, I would like to be able to bring up the remote tools for a
> system without having to actually find trhe client in a collection and use
> the all task option.
>
> I was thinking of something where I could just pass a client name to the
> executable...
>
> TIA,
> Jim Davie
>
>

Relevant Pages

  • Re: Launching SMS 2.0 Remote Tools from a Command line?
    ... You will need to install the SMS admin console in order to use RC to connect ... > Can we use the remote tools to connect from one client to another client. ... >>> Establishing a Remote Tools Connection by Using Remote.exe ...
    (microsoft.public.sms.setup)
  • Re: Evan [MSFT] Did not help
    ... If "remote tools client agent" is enabled in the sms admin ui for the site ...
    (microsoft.public.sms.misc)
  • Re: Deploying SMS Adv Cleint to clients
    ... Today I tried to deploy agent to client and it seems to be Connection ... 1- I tried to connect to Remote SMS Secondary Server registry (also Domain ...
    (microsoft.public.sms.admin)
  • Re: Launching SMS 2.0 Remote Tools from a Command line?
    ... > Establishing a Remote Tools Connection by Using Remote.exe ... > SMS Remote Tools functionality. ... Site Server Name is the site server name of the site to which the ... > client belongs. ...
    (microsoft.public.sms.setup)
  • Re: Stale Client Information and XP Firewall
    ... also edit the registry to tell remote tools to use the network's name ... > attempt to connect to a client using remote tools, ... > address has been aquired by the client. ... > I am using SMS 2003 with a single site. ...
    (microsoft.public.sms.setup)