Historique RemoteExec®
RemoteExec 4.03
- Fixed: reg files with a space in the name were not correctly registered
- Fixed: The Windows Vista user access control is supported
- Improved: The use of impersonation accounts when the account running RemoteExec doesn't have administrative rights on the remote computer
- Fixed: Some issues with action filters when scheduling tasks
- Improved: The remote registry service of remote workstations is automatically started when needed
- Fixed: An action sequence with a reboot in it was aborting after the reboot on Windows 2000 computers
- Fixed: Internet Explorer 7 updates were not correctly detected
RemoteExec 4.02
- Fixed: reg files were not correctly registered in all cases
- Fixed: RemoteExec was not working with remote x64 computers in some cases
- Fixed: New MDAC/MSXML hot fixes were not correctly detected
- Added: Ability to easily deploy Internet Explorer 7 using the predefined action "Hotfix/update installation"
- Fixed: Some issues with Windows Vista
- Fixed: The shutdown/logoff notification was not moveable
RemoteExec 4.01
- Fixed: Bug in the filter when a remote execution was scheduled
- Fixed: Error descriptions weren't saved in logs during scheduled remote executions.
- Fixed: The wake-on-lan was not 100% compliant with the standard. Some computers did not wake up.
- Fixed: In some case the context menu was very slow to display
- Fixed: Some handles where not immediately released on executables to deploy.
- Improved: The splash screen and the banner are not displayed on 256 colours screens.
RemoteExec 4.0
- Fixed: A problem while killing remote processes in multiple action mode
- Fixed: When canceling a system action the wait process was not stopped
- Fixed: Executing an immediate logoff on Windows NT4/2000 computers without a logged on user was leading to a system shutdown
- Fixed: In the french version only. Items in the combo box allowing to wait the end of the execution of a system action were not correctly ordered.
RemoteExec 4.0 beta 2
- Updated: The help file was updated and is available online
- Improved: Command line mode. Three new switches /EXE /ARGS /FOLDER in order to be able to dynamically change the executable in a script. See the help file.
- Fixed: A bug while loading an action file from the current working folder in Command line mode.
- Updated: The new license system is ready. If you are already customer you can ask for your new RemoteExec 4 license key (support@remoteexec.com) if your maintenance is up to date.
This beta version will work until end February
RemoteExec 4.0 beta
-
For a full documentation on all new features please read the What's new file.
- Improved: RemoteExec is able to configure the silent installation switches for more kind of Microsoft updates
- Added: The mini scanner can now filter computers on the processor type (x86, x64, ia64) and on the system language
- Added: Ability to power off computers
- Added: Ability to power on computers using the wake-on-lan technology. RemoteExec can scan MAC addresses & subnets automatically.
- Improved: The shutdown/logoff notification: indefinite notification, the user can hide the notification, immediate reboot for workstations without logged on user.
- Added: Ability to execute several actions in one pass using the "Multiple actions" mode.
- Added: Ability to add many files to execute at a time using the "Multiple actions" mode
- Improved: Ability to detect if the remote process returned an error code
- Improved: In the "Msi installation" action, ability to detect if a Windows installer package is already installed.
- Added: Impersonation accounts in order to authenticate on remote computers using different user accounts.
- Added: Ability to display the log contents in a progress window
- Added: Ability to restart or schedule from the progress window the action for all unavailable computers.
- Added: New predefined action "File operations" allowing deploying or deleting files or folders
- Added: New predefined action "Local account maintenance" allowing changing the local administrator password or disabling all other local accounts on all workstations of the network.
- Added: New execution context: System, the remote process is started with the localsystem account
- Added: New execution context: Interactive system, same as previous but the process can access the user desktop. Allows you to temporary give administrative rigths to a simple user (e.g. setup without silent mode).
RemoteExec 3.08
- Fixed: RemoteExec was unable to deploy the hotfix KB885836 (MS04-041) and most newer Mircrosoft hotfixes on WinDows XP SP 2 workstations. The installation was hanging while starting.
Important! If the mentioned problem occurs you need first to reboot all concerned computers with RemoteExec before to be able to use successfully this new version.
RemoteExec 3.07
- Added: a document explaining how to configure the Windows XP SP2 firewall to allow remote executions with RemoteExec
- Added: Support of the new Internet Explorer cumulative patch naming convention (IE6.0sp1-KB867801-x86-ENU.exe)
- Added: Support of the new Windows XP service pack naming convention (WindowsXP-KB835935-SP2-ENU.exe)
- Added: Ability to search computers in the Global Catalog of the Active Directory
RemoteExec 3.06
- Added: Ability to run a scheduled task only on remaining computers each time (unavailable in previous schedules). To do this check check "Execute the task only once on each computer" in the RemoteExec tab of the task properties.
- Fixed: If you abort and cancel an execution all computers name are now saved in the logs
- Added: Ability to use additionnal arguments for msi intallation. See the msiexec documentation for more information.
- Added: 2 filter operators on the content of the custom registry value "Contain" and "Doesn't contain"
- Improved: Internet Explorer hotfixes are now correctly detected
- Improved: New ping subroutine. In some cases RemoteExec was not able to ping remote computers.
RemoteExec 3.05
- Support of the new Microsoft patch name reference (e.g. WindowsXP-KB823980-x86-ENU.exe)
RemoteExec 3.04
- Fixed: When trying to browse for a working folder on Windows 2003 RemoteExec was crashing.
- Improved: The computer browser
RemoteExec 3.03
- New: Ability to update a msi installation after patching the network image
- New: Support of Windows 2003 in the filter
- Fixed: Bug when saving an action with the filter. The filter was not saved.
RemoteExec 3.02
- Added: You can now deploy the service pack 1 for Windows XP but you need to use the SP1a release available at the following URL:
http://www.microsoft.com/downloads/details.aspx?FamilyID=83e4e879-fa3a-48bf-ade5-023443e29d78&DisplayLang=en
Reminder: The first release of the SP1 cannot be deployed with RemoteExec because in some cases the installation stuck and the remote computer becomes corrupted after a reboot (blue screen). - Fixed: The computer browser bug mentioned in the 3.01 is now really fixed
- Fixed: Other bug in the computer browser. In some cases computers were listed under the false domain.
- Fixed: Bug in console mode. Symptom: Failed to start 0006 Invalid handle
- Added: RemoteExec ping each computer before launching the execution in order to avoid long timeouts on unavailble computers. If needed this feature can be disabled with the following registry value: HKEY_LOCAL_MACHINE\SOFTWARE\ISDecisions\RemoteExec\NoPing = 1 (DWORD)
- Improved: When scheduling a task and when the password for the current account is already entered the account information for the schedule is automatically set.
- Improved: After the configuration of a schedule RemoteExec ask (and save) the password for the selected user account if the "Full administrative" context is selected in order to avoid that RemoteExec ask the password at the execution.
RemoteExec 3.01
- Fixed: The computer browser was not displaying the computers of the local domain in some cases
- Fixed: RemoteExec was blocking when launched for the first time with a new account through the task scheduler (in consequence of the License Agreement).



Commander



