#remoteexec

Our 4 software solutions and our Technical Support have been nominated for the Windows IT Pro 2012 Community Choice Awards:

FileAudit in Category #3 "Best Auditing & Compliance Product"

RemoteExec in Category #6 "Best Deployment/Configuration Product"

UserLock in Category #6 "Best Security Product"

WinReporter in Category #25 "Best Systems Monitoring Product"

Technical Support in Category #30 "Best Vendor Tech Support"

Our 4 software solutions have been nominated for the 2011 Windows IT Pro Community Choice Awards.

You use and appreciate them? Please help us creating awareness about our innovative Infrastructure & Security Management solutions for Microsoft Windows by voting for them before September 7th (it will only take 2 minutes of your time)!

- UserLock UserLock limits concurrent logins, restricts access, monitors, alerts and reports on session activity throughout the corporate Windows network. Nominated in category #22: Best Security Product

- RemoteExec    RemoteExec remotely installs applications, executes programs/scripts and updates files and folders on Windows systems throughout the network. Nominated in category #6: Best Deployment/Configuration Product

- FileAudit  FileAudit monitors, archives and reports on access (or access attempts) to sensitive files and folders stored on Microsoft Windows systems. Nominated in category #3: Best Auditing & Compliance Product

- WinReporter  WinReporter retrieves detailed information about hardware, software and security settings from Windows systems and automatically generates reports. Nominated in category #25: Best Systems Monitoring Product

You can also show your appreciation for the great job performed by our dedicated Technical Support Team by voting for IS Decisions as “Best Vendor Tech Support” (category #30).

RemoteExec can easily deploy the Windows 7/2008 R2 Service Pack 1. This can be useful if you have to update servers without an Internet connection or workstations with the Windows Update engine turned off.

Direct deployment

You can update your system directly following the 6 steps below. Before getting started, check to see if the Targets Computers are being used as this operation will consume resources and will require at least one reboot.

Open RemoteExec and go to Remote Jobs/New Remote Job/Update installation through the Configuration tree.

In the first section Settings, browse to the Service Pack installation file in File field. RemoteExec will detect automatically the name, type, architecture and operating systems concerned. We advise you to keep the option Don't reboot disabled1 : this update needs at least one reboot to process fully. There is nothing else to set.

1: The reboot will be initiated only if no session is open on the target computers. If a session is opened or locked, RemoteExec will notify the user through a popup inviting him to reboot the computer . If you want to force the reboot, you need to create a Multiple actions with first this Update installation and then a Reboot System action. Make sure that the following options are enables for this reboot: Force applications to close and Reboot only if needed.

As you see below, the second section called Filter that RemoteExec automatically configures the required conditions. You can set additional filters such as the target OS level since this Service Pack can address both Windows 7 and Windows 2008 R2.

Go to the Target Computers section and select the computers on which you want to deploy this Service Pack.

You can now start your update by clicking on

The Progress window will open in a new tab to permit you to follow the remote operation process.

Schedule this update

The size of this new service pack needs to be taken in consideration for this operation:

32 bits version: 537 MB

64 bits version: 903 MB

The time taken for this deployment can fluctuate (depending on the target computer system and the bandwidth available) between 15 minutes to more than half an hour. As in every Windows Service Pack installation, hardware resources will be impacted. That is why we advise to schedule this operation during off business hours. In the example below, we have planned it for Sunday evening

Follow the previous steps 1 to 4.

Instead of launching the deployment directly, click in the Quick Access Pane on .

Enter a name on the Schedule Wizard for this new Task.

Validate the new Task name and the Windows scheduler pop-up window will appear. Set the task to Once and choose the Start time settings. Validate by clicking OK. You will be prompted to set an administrative account for this Task. The RemoteExec Scheduler now displays our new scheduled job.

Want more?

In this example we have scheduled the SP1 update on Sunday evening. You can also schedule the results report of this deployment in order to find it into our mailbox2 Monday morning when coming back to work.

Go to Reporter/Execution results through the Configuration tree.

Set the Report as wanted. In the Time section, leave the Execution combo list to the last Execution done3.

Click in the Quick Access Pane on

Select the Task we previously created and click OK. The Report will be added in the chosen Scheduled Task.

In the Configuration Tree, go to the Scheduled Task.

Select the Report node Execution results. The report configuration form will be displayed into the Central Window. Go to the Document Generation section and check the box for The first file to generate. Choose the path and format settings for the report.

Click on Add notification in the Quick Access pane. It will be added just after the Execution results report into the Scheduled Task.

Double click on the Notification line to display its parameters. Check the box Send documents by E-mail and fill in the different fields as needed. The report will be available in your email box when you will come back to work on Monday morning and you will be able to check if the SP1 deployment was successful.

2 : The SMTP information used for the email expedition needs to be set in the Console Options available at the bottom of the Configuration tree.

3 : When you schedule a report, if you select the latest execution, the report will always be generated for the latest execution.

The example below illustrates the use of a predefined System Action to ensure the automatic shutdown of all workstations. The time you choose for switching off your computer must coincide with your company business needs.

Take note that:

A user might be working on the target machine.

A session can be opened on the target machine without a user in front of it, but with documents opened or applications running.

A session can be locked on the target machine with some documents opened or applications running.

Our goal in this example is to shutdown all computers, even those with documents unsaved or applications running. You should communicate this as part of your global Green Charter to your users.

How to shutdown all computers

Open RemoteExec and go to Remote Jobs/New Remote Job/System action through the Configuration tree.

In the first section «Settings», choose in the combo list System action named Shutdown.

RemoteExec can check if a user is currently working on the target machine, and can process the System action differently in this case. Choosing the option Immediate execution, notify otherwise means:

If there is no user connected on the workstation, the shutdown will be initiated immediately.

If there is a user connected on the workstation, a Notification will be displayed to the connected user. The shutdown will be initiated depending on the mode defined in step 4 for this Notification.

Notification mode Two options to define how the shutdown will be initiated:

Execute after showing notification during The shutdown will be executed after displaying the message during the number of minutes typed. The Notification displayed can be hidden by users, but it regularly pops in foreground.

Indefinitely notify every The Notification is displayed indefinitely until users click on the button to initiate the shutdown. Users can hide the Notification, but it will pop again every number of minutes you’ve defined.

As we defined in the preamble, we want to shutdown all workstations. We will choose here to execute this System action after the Notification period. We will set a sufficient delay allowing users to finish their current work.

Leave the third combo list on the Don't wait for the end of the execution option. (This option is pertinent in multi action mode, not in our example here).

Check the Force applications to close option. We will be sure that all sessions kept opened will be closed. Although users have been informed about this Green Charter action, there will be always some thoughtlessness.

Set your Notification message to explain the imminent shutdown and provide instruction to avoid losing documents/work recently modified.

We want to power off all workstation from our network. That's why in Target Computers section we have selected the whole domain. As we don't want servers to be concerned by this Remote Action, we will set the Filter section option named OS level only to workstation.

The remote shutdown job is now ready and fully set. This is how the Notification will be displayed to users connected on the target machines:

Click in Quick Access Pane on

Enter a name on the Schedule Wizard for this new task.

Once validating the new task name, the Windows scheduler pop-up will appear. Set the task to Daily and the hour settings in according to your company hours. Validate by clicking OK. You will be prompted to set an administrative account for this task. In this example setting 09h30 PM means that the computers will be powered off by 10:00 at the latest. (9h30 + 30 minutes countdown). The RemoteExec Scheduler now displays our new scheduled Job.

Want more ?

In this example, all computers have been shut down during the night. In the same way, you may decide to automatically switch on computers on allowing users to work immediately upon their arrival. This is also possible through RemoteExec Wake up System action.

The computers using the Wake-on-line technology (available on most computers today) can be remotely powered on if this option is enabled. You just have previously to scan the Mac addresses and Subnet of your network machines using the System action Get wake up info (which can also be scheduled). Then using the same concept, you can choose to wake up users' computers automatically.

During your tests

If for any reason you remotely launch a shutdown that you want to abort, you can use the specific System action.

CCleaner supports the cleaning of temporary or potentially unwanted files left by certain programs, including Firefox, Opera, Internet Explorer, Safari, and other applications along with browsing history, cookies, Recycle bin, memory dumps, file fragments, log files, system caches, application data, autocomplete form history, and various other data. Source: Wikipedia

Deployment with default settings

Download the latest version of CCleaner from: http://www.piriform.com/ccleaner/download

Open RemoteExec and go to Remote Jobs/New Remote Job/File execution through the Configuration tree.

In the first section «Settings», browse the File field to the setup file previously downloaded.

You can find in the help file of CCleaner all command line parameters. /S: Performs a silent install of CCleaner with default options. /D= Permits to choose a different installation folder than the default. /L= Choose the language file identified by the locale ID.

List of locale ID: http://support.microsoft.com/kb/221435

List of CCleaner supported language: http://www.piriform.com/docs/ccleaner/ccleaner-settings/...

At minima you must specify the /S as Argument. If you'd like, you can choose the installation path and language.

Set the Context to Administrative and keep the Auto option checked. RemoteExec will optimize the remote execution.

Go to the Target Computers section and select the computers on which you want to deploy CCleaner.

You can now start your deployment by clicking on . The Progress window will pop in a new tab allowing you to follow the remote execution process.

Custom installation

First install CCleaner on your own computer.

Personalize the parameters.

Save these parameters in an ini file: Menu Options/Advanced – Check the box «Save all settings to INI file». This option allows CCleaner to use the parameters stored into this INI file instead of those contained in the Windows registry. Once this option enabled, your CCleaner installation is now portable.

Open RemoteExec and go to Remote Jobs/New Remote Job/File operation.

Select in the «Settings» section the Operation «Copy a folder».

In the Source path, browse to the installation folder on your workstation. By default: C:\Program Files\CCleaner.

Type in the Target path field the folder path you want to set on Target Computers1. It can be the same as on your workstation: C:\Program Files\.

Go to the Target Computers section and select the computers on which you want to deploy CCleaner.

You can now start your deployment by clicking on . The Progress window will pop in a new tab allowing you to follow the remote execution process.

1: If the target path doesn’t exist, all the folders composing the path tree will be created Note: If you already have a CCleaner installation on Target Computers (with default parameters or even personalized parameters as done here), you can update/change the CCleaner settings using the Ini file. Change the parameters as wanted in your proper installation or directly in an Ini file copy then push it using RemoteExec selecting the File operation «Copy a file». Ini settings description: http://www.piriform.com/docs/ccleaner/advanced-usage/ccleaner-ini-files/using-ccleanerini-to-modify-how-ccleaner-runs

Using CCleaner

You can run CCleaner remotely and silently on computers using RemoteExec. The settings taken into account for this remote runs are those set on target machines (see previous paragraph).

RemoteExec and go to Remote Jobs/New Remote Job/File execution through the Configuration tree.

In the File field, specify the remote CCleaner.exe path. By default: C:\Program Files\CCleaner\CCleaner.exe

Fill Argument(s) field with «/AUTO».

Set the Context to Administrative.

Uncheck the Auto box.

Select the Verb «Open».

Select «No» for the Copy files option.

Go to the Target Computers section and select the computers on which you want to run CCleaner.

You can now start your remote execution by clicking on . The Progress window will pop in a new tab allowing you to follow the remote execution process.

Note: When you run CCleaner.exe using the /AUTO parameter, CCleaner does not run the Registry cleaner. You cannot currently run the Registry cleaner through a command-line parameter.

Mozilla Firefox is a free and open source web browser descended from the Mozilla Application Suite and managed by Mozilla Corporation. The latest Firefox features include tabbed browsing, spell checking, incremental find, live bookmarking, a download manager, private browsing and location-aware browsing. Source: Wikipedia

How to deploy Firefox

Download the latest Firefox version from: http://www.mozilla.com

Open RemoteExec and go to Remote Jobs/New Remote Job/File execution through the Configuration tree.

In the first section «Settings», browse the File field to the setup file previously downloaded.

By default, Firefox setup is not a silent package. The argument to make it silent is indicated in the Mozilla help resources: «-ms». Fill in the Argument(s) field with «–ms».

Set the Context to Administrative and keep the Auto option checked. RemoteExec will then optimize the remote execution.

Go to Target Computers section and select the computers on which you want to install FireFox.

You can now start your deployment by clicking on . The Progress window will pop in a new tab allowing you to follow the remote execution process.