Forum Discussion

Rob H's avatar
Rob H
Retired GoTo Contributor
17 years ago

Rescue Script Repository Thread- Share your scripts

Welcome to the new LogMeIn Community. One of the things that we would like to foster is the sharing of lots of great ideas and neat tips and tricks. I thought that I would get the ball rolling by publishing the LogMeIn Rescue Scripts that I use on a day to day basis, when I’m doing product demonstrations. These are fairly basic, but hopefully it will get everyone thinking of how powerful this feature can be. Scripts are a great way to automate repetitive, mundane or pain in the neck tasks.

 

I have provided a few scripts which perform individual tasks but I have worked with a lot of users who combine multiple tasks into a single script. So when you are providing remote support and it is your standard operating procedure to perform tasks A,B,C and D for troubleshooting or diagnostic purposes, then chances are, you can automate those tasks with LogMeIn Rescue scripting.

 

Haven’t had the opportunity to dabble with scripts in Rescue yet? No problem, below are step by step instructions on how to get scripts set up in your Technician Console. Additional instructions can be found in the LogMeIn Rescue Technician Console Users Guide, in the section named "Working with Scripts"

https://secure.logmeinrescue.com/Common/Pdfs/rescue_tech_console_userguide.pdf

1.       Create a folder named LogMeIn_Rescue_Scripts anywhere on your C: drive (best in a location that won’t be moved) and put the XML file in there.

2.       Within the LogMeIn_Rescue_Scripts create six individual folders named:

a.      Defrag_Info_Sample

b.       Drivers_Details_Sample

c.         MAC_Info_Sample

d.       One_Click_Ipfonfig_Sample

 

Normally step 2 is not required in the real world, but the software we use for the community only allows me to upload individual files, not folders.

3. Copy the scripts (below) into the corresponding folder which you created in step 2. 

4. Open up the Technician Console, click on “options” (upper left corner) then select “Edit Scripts.”

5. Click the “Import” button then browse to the LogMeIn_Rescue_Scripts folder and point to the XML Document and this will import the scripts.

Once your scripts have been imported you will notice that you have the option to run a given script when the customer applet starts after you have connected to a remote computer. You can also change the order in which the scripts appear in your Technician Console, so you can move frequently used scripts towards the top, and lesser used scripts to the bottom.

 

Do you have a great script that you use and think will be useful to others? If so, email it along with a brief explanation to  rescuescripts*at*logmein*dot*com and I will post them to the community. If you do send me some examples please let me know if you would like to make an anonymous contribution or if it’s OK that I can use your name and/or LogMeIn community login name.

Script Links: (Right click, select "save link as" then change the file extension from.txt to .cmd)

Defrag Info

http://community.logmein.com/html/assets/defrag info Cdrive.cmd  

Driver Info

http://community.logmein.com/html/assets/driverdetails.cmd  

MAC Address

http://community.logmein.com/html/assets/getmacaddress.cmd

IP Config

http://community.logmein.com/html/assets/startipconfig.cmd  


Use of these scripts are at your own risk. The scripts are provided “as is” without any warranty of any kind and LogMeIn disclaims any and all liability regarding any use of the scripts.  Please see the following Terms and Conditions for more information.

 

 

Message Edited by AndyS on 11-13-2008 02:38 PM
Message Edited by Rob H on 11-23-2009 09:01 AM
  • Im trying to get a .cmd-script that pulls the serialnumber from the bios and outputs it in the chatwindow but I cant get it to work. code:

    WMIC bios get serialnumber /format:list'

    If I run the cmd on my computer it works fine but when I run it from rescue I get cryptic letters in chatwindow. What am I doing wrong?

     

    While Im at it I can ask if there is a way to get the serial-information under the System Info tab in technician console?

     

     

    • Rob H's avatar
      Rob H
      Retired GoTo Contributor

      I know it's been a while, but try this instead (courtesy of members of our support and development team).

      @echo off wmic SystemEnclosure GET SMBIOSAssetTag > tmp.txttype tmp.txt

       

      What's happening is that the WMIC command outputs Unicode text as opposed to ASCII text (which the Tech console understands) the "type" command converts the Unicode to plain ASCII.

       

      At this time the remote system serial number cannot be pulled into the System Info tab.

      • jesus_moreno85's avatar
        jesus_moreno85
        New Member

        Hello Rob,

         

        I tried using your script this way:

        @echo off wmic bios get serialnumber > tmp.txttype tmp.txt

         

        but I get (no output) in the Tech Console. I am trying to gather the computer serialnumber/asset tag using the above command. If you could assist me with this issue I would greatly appreciate it.

         

        Thanks.

    • kappisto's avatar
      kappisto
      New Contributor
      Possibly stupid question - why .cmd instead of .bat?
  • Rob H's avatar
    Rob H
    Retired GoTo Contributor

    Here’s a few more scripts that might be useful, but first I’d to thank my colleague, Csaba Jaromi, my counterpart in our Amsterdam office who put these together.


    The new scripts are:
    •    Display BOOT.INI contents (XP)
    •    Display BOOT.INI contents (Vista)
    •    Display current user Proxy settings (XP)
    •    Display current user Proxy settings (Vista)
    •    Get HOSTS file contents
    •    Power profiles available and currently active profile details
    •    Detailed scheduled task information

    Of this new batch, I think the power profile is my favorite, it returns results that look like this:

    Field Description          Value
    -----------------          -----
    Name                       Home/Office Desk
    Numerical ID               0
    Turn off monitor (AC)      After 20 mins
    Turn off monitor (DC)      After 5 mins
    Turn off hard disks (AC)   Never
    Turn off hard disks (DC)   After 10 mins
    System standby (AC)        Never
    System standby (DC)        After 5 mins
    System hibernates (AC)     Never
    System hibernates (DC)     After 20 mins
    Processor Throttle (AC)    Not Supported
    Processor Throttle (DC)    Not Supported


    With all the emphasis on being green, this is a great tool to help the tech community to do their part.

    To download and use these scripts in your Rescue Tech Console: 
    Create the following folders in your Logmein_Rescue_Scripts folder. Keeping the syntax the same as below is important because that’s what the XML file will be looking for (once the scripts are installed in your Technician Console then you can change the file and folder names as well as the descriptions).


    Boot_INI_Contents_Sample
    Boot Settings for Vista
    Hosts_File_Content_Sample
    Power_Profile_Sample
    Proxy_Settings_Sample
    Scheduled_Tasks_info_Sample
    Proxy_Settings_Vista

    Next, put the attached files in their corresponding folder and the the XML file in your  Logmein_Rescue_Scripts  folder.


    Now, open up your Technicians Console and click on the “Options” menu (upper left) and select “Edit Scripts” and in the lower left hand corner select “Import” then browse to your Logmein_Rescue_Scripts  folder and select the “New Scripts 09.XML” file, then click on  the “Open” button. This should import all of the new scripts. Click the “Close” button in the lower left corner of the Technician Console and you should be all set.

     

    Please note that the disclaimer in the initial post of this thread apply to these scripts as well.

    Message Edited by Rob H on 02-05-2009 09:13 AM
    • garybarr's avatar
      garybarr
      Active Contributor

      Boot_INI_Contents_Sample
      Boot Settings for Vista
      Hosts_File_Content_Sample
      Power_Profile_Sample
      Proxy_Settings_Sample
      Scheduled_Tasks_info_Sample
      Proxy_Settings_Vista

       

      Anyone still have these scripts?   The links seems to be empty and I can't find them anyplace else.

      • msdl's avatar
        msdl
        New Member

        I've been looking into automating a few things with my LMI workflow.

         

        Is it possible to script actions in the LMI client?

        One example I want to script is, save chatlog to a folder on my computer, and then transfer it to the customer's desktop.

         

        Is this possible with the clients current functionality?

    • wekalegs's avatar
      wekalegs
      Visitor

      Hi Rob H I must be dumb but where are the attached files??

       

       

  • Very helpful!

    Thank you

    Where can i learn how to build my own scripts?

    • Rob H's avatar
      Rob H
      Retired GoTo Contributor

      Great question. Technician Console scripts can be written in and deployed using any language the operating system can execute. For example a script can be written in a batch file using Visual Basic, or it can be a software package.

       

      Some of the examples I provided are probably about as simple as you can get. All I did is use the command you would use at the C prompt and paste it into Notepad and saved it with a ".cmd" extension. 

       

      Perhaps a good place to start is using basic commands. Try Googling "command prompt cheat sheet" and that should get you started.

       

      Does anyone have any resources for scripting which they have found useful?

      Message Edited by Rob H on 11-13-2008 05:10 PM
      • Bob5's avatar
        Bob5
        Visitor

        To debug VBS scripts interactively, like Visual Basic code debugging, I looked for and found SplineTech VBS Debugger.  http://www.remotedebugger.com/ also appears to have a Java and ASP remote versions.  ~ $80 for a personal version.  Saved me tons of time.

         

        Bob5