Vous êtes ici : Accueil OS Deployment Adding Remote Control to Lenovo RnR

Adding Remote Control to Lenovo RnR

Par kchampli Dernière modification 19/09/2008 11:26
Contributeurs : jack

This task is based on the ideas in Eric Coidan's Adding Remote Control to LANDesk PE.pdf but is specific to the Lenovo Rescue and Recovery environment. You will need Rescue and Recovery 4 or better to be installed on the laptops and desktops to be managed. A LANDesk Management Gateway is assumed as well.

For those unfamiliar with the product, Rescue and Recovery provides a dual-boot instance of WindowsPE in which backup and restoration tools are provided to the end user. LANDesk administrators with access to the LDMS for TVT product can set policies for how RnR backups work and what the end user can configure, but cannot remote control the user during a system restoration job without using this technique. This can be configured post-RnR installation without rebooting to the RnR environment.

In short, a Lenovo administration tool called rrutil.exe will be used to inject a directory tree containing LANDesk remote control components and configuration scripts into the RnR environment. The tool can be downloaded from http://www.lenovo.com/thinkvantageadmin and is also included the the example package on this page.The package is RnR4_2_7_10_2008.zip

When you extract it, you'll see there's two main directories "RTO_Vista" and "RTO_XP". Each of those will have 3 things:

  • RTOtemp - Contains the files that we need to place into the preboot environment:
    • It should look like RTOtemp\preboot\rto & RTOtemp\preboot\SWWORK
    • Under the \SWWORK directory there's an RTO.tbi file, this has all the command lines needed to get the remote control agent up and running. When RnR boots up, this command (RTO.tbi) is run...I won't get into the specifics, but essentially it's a bunch of batch files with fancy file extensions.
    • the \RTO directory has all the remote control "pieces" from LANDesk. They are all pretty universal so you don't need to replace them with the ones you have on your Core Server. Feel free to look at the contents and see how little is actually needed to get Remote Control to work. The example script is using a non-secured configuration of course; full integrated security remote control would take more effort, as well as being less likely to work properly when it's really needed to support an offsite user with a broken laptop and a questionable hotel network.
  • rrutil.exe - This is a Lenovo program that does the "putting" of the contents into the preboot environment
  • RTP_XPRNR.cmd - This command will run RRUTIL.exe and do its magic (meant to automate this whole process).


The order of operations comes down to the following:

  1. Target host systems that have RnR and LANDesk on them
  2. Extract that zip file to the root of the drive, like this: C:\RnR4_2\RTO_Vista\RTOtemp (or RTO_XP)
    1.         ***It's important that the path matches that out line and you'll need to edit the batch file to point to the C: drive (it's pointing to D: currently).
  3. Run the .cmd file and wait for the magic to happen

You should be able, after it says "successful", to boot into RnR but still be able to right click that machine on the LDMS console and remote control it.

To double check that it's working as advertised, if you boot into RnR and hold down the "Shift"+"Ctrl"+"Alt" keys on the LEFT side of the keyboard and click the "restart" button in RnR on the top left it will open a command line terminal. If you type "taskmgr" it should open the windows task manager and TWO processes should be running: issuser.exe & rcgui.exe.

Navigation
Se connecter


Mot de passe oublié ?
Nouvel utilisateur ?
 
Server Says:
Vulcans do not approve of violence.
-- Spock, "Journey to Babel", stardate 3842.4
Safety First!
243 Days without a Dumpster fire.
 

Réalisé avec le CMS Plone, le système de gestion de contenu Open Source

Ce site respecte les normes suivantes :