EMCO Remote Installer Documentation Remote Installer Overview | Download | Purchase

Service Deployment Page

Remote Installer uses a service to operate remote Machines. This service can be installed by the program on demand or by a system administrator at any time. The service deployment type is configured on the Service Deployment preference page Pic 1. To change the deployment type, click the Preferences button in the Application Menu and switch to the Service Deployment preference page using the appropriate link in the navigation bar on the left of the Preferences dialog within the Installer group.

Choosing the remote service deployment type

Pic 1. Choosing the remote service deployment type

On the Service Deployment page, you are offered to choose if the state of the remote service should be maintain automatically by the program or the remote service deployment should be overseen by the network administrator. The difference between these two modes is that when the Automatic Deployment mode is used, Remote Installer requires administrative access to the remote file system so the remote Machine should be configured to allow access to its file system. Access to the file system is required to perform the remote service installation and updates. When the Manual Deployment mode is used, the program does not need to access the remote Machines' file system to work with the service; however the remote operation will fail if the remote service installation or update is required.

In the Manual Deployment mode, the program adds an information to the Execution Results when it fails to operate the remote Machine because the required remote service installation or update cannot be performed.

For manual deployment, the network administrator should use one of the installation packages supplied with the program. Those packages are available in the Setup folder of the program installation – this folder can be reached using the Remote Service Setup link in the program sub-menu of the Start menu. The installations are shipped in form of both an executable file, which is platform-independent, and two different platform-dependent MSI files, which can be used, for example, for automatic deployment through GPO.

For both the manual and automatic deployment modes, you can choose the action to perform upon the task completion, if required. There is no action to perform by default, but it is possible to stop or uninstall the remote service after the task is completed.