RemoteExec Frequently Asked Questions

What Operating Systems are supported by RemoteExec?

RemoteExec supports all these Operating Systems for installation as for target machines:

  • Windows XP
  • Windows Server 2003
  • Windows Vista
  • Windows Server 2008
  • Windows Seven
  • Windows Server 2008 R2
  • Windows 8
  • Windows Server 2012

What are the database systems supported by RemoteExec?

RemoteExec supports these database systems:

  • Microsoft Access database file (mdb)
  • Microsoft SQL Express 2005/2008/2008 R2
  • Microsoft SQL Server 2005/2008/2008 R2/2012

The evaluation version of RemoteExec is provided with a free database (Microsoft Access database file). This free database is limited to 2 GB. You can use a SQL Express version (LAst SQL Express version is up to 10 GB) or a SQL Server database in production environment.

Do I need to install any agent on target computers to execute a job thanks RemoteExec?

No. RemoteExec uses standard Windows APIs and doesn't require any intervention or installation at all on remote computers.

You can choose to install RemoteExec on any computer on your domain. Once done you will be able to target any machine.

The only requirements are:

  • The account running RemoteExec requires administrative privileges on target computers. If not, RemoteExec provides an Impersonation feature allowing you to register an account with these privileges. You can find the Impersonation accounts section into the RemoteExec Console Options.

    New Account Information

  • Any firewall between the RemoteExec administration console and target computers should authorize the Microsoft File and Printer sharing (SMB TCP 445) and ICMP (ping) protocols.
  • The Remote registry service needs to be enabled. Take note that this service is disabled by default from Windows 7 operating system.

What are the requirements to execute remotely a job on a computer?

To execute remotely any job on a computer through RemoteExec:

  • The account running RemoteExec requires administrative privileges on target computers. If not, RemoteExec provides an Impersonation feature allowing you to register an account with these privileges. You can find the Impersonation accounts section into the RemoteExec Console Options.

    New Account Information

  • Any firewall between the RemoteExec administration console and target computers should authorize the Microsoft File and Printer sharing (SMB TCP 445) and ICMP (ping) protocols.
  • The Remote registry service needs to be enabled. Take note that this service is disabled by default from Windows 7 operating system.

I have received my RemoteExec license serial. Where can I register it?

You can register your RemoteExec serial through the Tools/License menu. Just copy/paste the serial and apply it

License

You will also find here the number of machine you can target and the maintenance expiration date.
The RemoteExec maintenance includes all updates and allows you to benefit from our technical support service help and advises.

My remote job failed. How can I find the reason?

Once RemoteExec has been processed all remote action executions, the Result Windows will open to display the status of each remote remote job launched on target computers. You will see all success, failure, warning or information generated (depending of the notification type enabled).
The cause of a warning and failure are displayed with an associated message allowing you to understand the situation.

If meet some difficulties to find the reason of an execution failure, you can begin to investigate testing the basic requirements:

  • Is the registry of the target computer remotely accessible from your administration console (using regedit or regedt32)?
  • Is the administrative share \\ComputerName\admin$ accessible from your administration console?
  • Do you have the administrative rights on the remote computer?
  • Is the server service running on the remote computer?
  • Is the remote registry service running on the remote computer?
  • Is the administrative share on the remote computer (ADMIN$) not disabled?
  • Can you resolve the name of the remote computer from your administration console (check this with the command line "ping computername" from a command prompt window)? 

Our technical support team is also available to help you. Don't hesitate to contact us thanks our web form to help you in your investigation or for any advise.

I get the error “Unable to connect: Access denied” when trying to remotely execute tasks on Windows computers in Workgroup.

The default configuration of a Windows computer in Workgroup doesn’t allow any remote administration.

To allow remote executions, you need to disable the simple file sharing. You can find this options in the Folder Options of the Windows Explorer (View tab).
Additionally the password of the used administrator account should not be empty.

Once done, you can target this Windows Workgroup machine with RemoteExec. As this is a Workgroup system, the account running RemoteExec on your machine should not have sufficient privilege to execute an action on it. Use the Impersonation feature in the Console Option to define a set of credential which has administrative rights on the Workgroup machine you want to reach.

Here you can find details about the impersonation accounts.

When I launch my remote job on several target machines, RemoteExec displays a failed status with the error message "Not enough workstation licenses".

The RemoteExec license system is per computer to target .Once you have successfully targeted a machine, a license is consumed and assigned for this machine. The licenses security system kept in memory which machines are licensed.

This message “not enough workstation licenses” means that you have already use RemoteExec to remotly execute an action on the number of machines corresponding to your license number. As they are all assigned, there is no free licenses for additional ones.

Please contact our sales department if you want additional licenses to target more systems.

If a system has not been targetted by RemoteExec since 30 days, then it will be automatically removed from the license memory. This means that old systems on your network which no longer exist will be automatically removed from the licensed system after 30 days.

If you are currently planning to process to a large migration of your network system, then it could be important for you to get unassigned the licenses of old systems faster than wainting from these 30 days period. In this case, we invite you to contact our technical support team to obtain a larger temporary license for RemoteExec allowing you to use RemoteExec in this context. This service is included into your maintenance subscription.

How can I remove from the RemoteExec license systems which no longer exist on my network?

The RemoteExec license system is per computer to target .Once you have successfully targeted a machine, a license is consumed and assigned for this machine. The licenses security system kept in memory which machines are licensed.

If a system has not been targetted by RemoteExec since 30 days, then it will be automatically removed from the license memory. This means that old systems on your network which no longer exist will be automatically removed from the licensed system after 30 days.

If you are currently planning to process to a large migration of your network system, then it could be important for you to get unassigned the licenses of old systems faster than wainting from these 30 days period. In this case, we invite you to contact our technical support team to obtain a larger temporary license for RemoteExec allowing you to use RemoteExec in this context. This service is included into your maintenance subscription.