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

From: Giskard Reventlov (rgiskard_at_nospam.com)
Date: 02/23/04 

Date: Mon, 23 Feb 2004 17:36:05 -0500

Can we use the remote tools to connect from one client to another client.
I tried to run the remote tool from one of the clients which was a remote
tool client but I get the following error:
"This application has failed to start because MFC70U.DLL was not found.
Re-installing the application may fix the problem".
Or is there anything else that i need to install on the clients ?

Thanks
-Giskard

"Jim Davie" <jdavie@tampabay.rr.com> wrote in message
news:rWp_b.99212$jH.640039@twister.tampabay.rr.com...
> Thanks so much for the assistance! This is great and will improve my
> department's efficiency greatly!
>
>
> "Stan White [MS]" <stanwh@microsoft.com> wrote in message
> news:%23wflUWi%23DHA.2216@TK2MSFTNGP10.phx.gbl...
> > 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:
> >xp \
> > 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?
    ... Establishing a Remote Tools Connection by Using Remote.exe ... All Remote Tools functions are also available by running the Remote.exe ... SMS Remote Tools functionality. ... client belongs. ...
    (microsoft.public.sms.setup)
  • re: Remote Tools on XP
    ... I mean that the Legacy Client should not install on W2K+ in SMS 2003 SP1 and above. ... If you disable Remote Tools on the site server, then reattach the site server to the network, when it installs the client, the clients will not try and install remote tools. ... I would expect the freeze to occur when the client was installed, not on the next boot, because that is when the drivers are installed. ...
    (microsoft.public.sms.tools)
  • RE: SMS and Dameware
    ... Also check under Site Settings | Client Agents | Remote Tools Client Agent. ... The main reason for us is that it is easier to control who has ...
    (microsoft.public.sms.misc)
  • Re: Remote tools client agent.
    ... Do you have a problem using push installation or do you have a problem ... Is the Client itself installed? ... In the sms administrator console, do you see remote tools under site ... >> Kim Oppalfens ...
    (microsoft.public.sms.admin)
  • 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)