Launch SMS Remote Tools

Forums

My Profile

Inbox

Address Book

My Subscription

My Forums

Launch SMS Remote Tools

Logged in as: Guest

arrSession:exec spGetSession 2,16,53262

	Active Users: There are 0 members and 0 guests.
	Users viewing this topic: none

Printable Version

All Forums >> [Scripting] >> Post a VBScript >> Launch SMS Remote Tools
Do you like VisualBasicScript.com? Link to us and help spread the word about our forum. Thanks!

Page: [1]

Message

<< Older Topic Newer Topic >>

Launch SMS Remote Tools - 11/4/2007 12:54:34 PM

Meg

Posts: 123
Score: 2
Joined: 7/13/2006
From: Australia
Status: offline

I was going to write this script myself but there was already one written here at work. I am not sure who wrote it.

If you are a network administrator and your corporate network uses SMS you will know what I mean.
This is a quick way of launching SMS remote control without having to scroll through thousands of machine names.

Const ForReading = 1, ForWriting = 2, ForAppending = 3
const RemoteExe = "C:\SMSADMIN\bin\i386\remote.exe"

'get Temp Dir
Set WshShell = CreateObject("WScript.Shell")
strTempDir = WshShell.ExpandEnvironmentStrings("%temp%")

' Check for remote.exe
on error resume next
Set oFs = CreateObject("Scripting.FileSystemObject") ' get handle to file interface
Set oF = oFs.getFile(Remoteexe)
if err.number <> 0 then
wscript.echo "Error! Could not find " & RemoteExe & vbcrlf & "You need to install SMS Administrator Console."
wscript.quit
end if
on error goto 0
set of = nothing ' release object

' If no server name on command line, ask the user for one
Set oArgs = WScript.Arguments ' get command line arguments
if oargs.count = 0 then
sNetbiosName = InputBox("Please enter the machine name.","SMS Remote Control Launcher")
if sNetbiosName = vbNullString then
WScript.Quit()
End If
else
sNetbiosName = oArgs(0) ' first arg is server name
end if
' See if we can ping the name 
set oWshShl = wscript.createobject("wscript.shell") ' get handle to shell object
rc = oWshShl.run ("cmd /c ping -n 1 " & sNetbiosName & " > "&strTempDir&"\~smsview.txt",0,true) ' run lookup

' Now read in the information
Set oF = oFs.opentextFile(strTempDir&"\~smsview.txt",forreading)
gotit = 0
badip = 0
Do While oF.AtEndOfStream <> True 
x = oF.readline
if instr(x, "Bad IP address") > 0 then
badip = 1
end if
if instr(x, "Reply from") > 0 then
address = trim(mid(x,12))
address = mid(address,1,instr(address,":") - 1) 
gotit = 1 
end if
loop
oF.close ' close temp file 
Set oF = oFs.getFile(strTempDir&"\~smsview.txt")
of.delete ' delete it

' If we found a valid address, launch the remote tools program 
if gotit = 1 then
rc = oWshShl.run ("C:\SMSADMIN\bin\i386\remote.exe 2 " & address ,1,false)
elseif badip = 1 then
wscript.echo "No IP address was found for " & sNetbiosName
else
' Report the machine not pingable
wscript.echo sNetbiosName & " Did not respond to PING."
end if
wscript.quit

While searching the Internet to see if anyone else has already posted this script, I found a variation which launches Remote.exe with the SMS GUID as an argument instead of the netbios name or IP address.
You will need to replace the variables in <brackets> Both scripts work with SMS2003 and probably SMS2. I tested using an XP Pro SP2 Machine.

Const ForReading = 1, ForWriting = 2, ForAppending = 3
const RemoteExe = "\\<UNC PATH TO THE REMOTE.EXE Application>"
' First check to see if remote.exe is in this directory
Set oFs = CreateObject("Scripting.FileSystemObject") ' get handle to file interface
Set oF = oFs.getFile(Remoteexe)
set oWshShl = WScript.CreateObject("Wscript.Shell")
if err.number <> 0 then
wscript.echo "Error! Could not find " & RemoteExe
wscript.quit
end if
Set oF = nothing
' If no computer name on command line, ask the user for one
Set oArgs = WScript.Arguments ' get command line arguments
if oargs.count = 0 then
sNetbiosName = InputBox("Please enter the machine name.","SMS Remote Control Launcher")
if sNetbiosName = vbNullString then
  WScript.Quit()
end If
else
sNetbiosName = oArgs(0) ' first arg is client name
end if
'Connect to SMS Server via WBEM to translate NetBIOS name to ResourceID
Set objLocator = CreateObject("WbemScripting.SWbemLocator")
Set objService = objLocator.ConnectServer("<SMS SERVERNAME>", "root\SMS\Site_<3CHAR SITECODE>")
Set instances = objService.ExecQuery("SELECT * FROM SMS_R_System WHERE SMS_R_SYSTEM.Name like '"&sNetbiosName&"'")
'Check to see if NetBIOS name is present and unique  
objCount=0
For each job in instances
objCount=objCount+1
next
if objCount = 1 then
For each job in instances
 oWshShl.run (RemoteExe & " 0 "&job.ResourceId&" \\<SMS SERVER HERE>")
next
else
wscript.Echo sNetbiosName & " was not found in the SMS database."
end if

< Message edited by Meg -- 11/4/2007 4:10:42 PM >

Revisions: 1 | Post #: 1

RE: Launch SMS Remote Tools - 11/8/2007 1:51:49 AM

crazymatt

Posts: 287
Score: 0
Joined: 3/4/2005
From:
Status: offline

Here is another script i made for starting the Remote Assistance tool on a remote PC

NOTE!: You must have the SMS client installed on the computer for this script to work, it WILL NOT work without it!

_____________________________

-There is only 10 sorts of people, those who understand binary and those who dont.

(in reply to Meg)

Post #: 2

RE: Launch SMS Remote Tools - 11/8/2007 2:57:10 PM

Meg

Posts: 123
Score: 2
Joined: 7/13/2006
From: Australia
Status: offline

Thanks Crazymatt,

I really like that script, I am thinking of writing a HTA that gives you a choice between all the different remote control methods we can use here at work.
I will see if I can use something from yours if you dont mind.

(in reply to crazymatt)

Post #: 3

RE: Launch SMS Remote Tools - 11/8/2007 6:48:55 PM

crazymatt

Posts: 287
Score: 0
Joined: 3/4/2005
From:
Status: offline

Your welcome, use it all you want :D

For my old job i made a "helpdesk toolset". I made a custom MMC in wich i put all the scripts i could think helpdesk would need.
The reason why i made a mmc of it was that i wanted them to be normal users on their computers but have an easy way of elevating their normal tools. So instead of doing "Run as" on every single script or tool they just did "run as" on the msc toolset and then all scripts from that point was ran with the correct rights.

To give you some ideas i had stuff like those remotescripts above and also scripts for getting whos logged on, renew dhcp-lease, start compmgmt.msc on remote pc, bios check for serial and stuff, had a tool that took the serial number from a hp-machine and checked against a website how much of the warranty was left and a few others.

/CM

_____________________________

-There is only 10 sorts of people, those who understand binary and those who dont.

(in reply to Meg)