Installing Remote Intelligent Device Client

Hardware and software requirements

The hardware and software requirements for the Remote Intelligent Device Client are as follows:

• A Windows NT domain system that runs in the same domain as the server and is not a domain controller. If the system is in a different domain, it (the domain) must have bidirectional trust with the server’s domain.

• Pentium III-compatible processor

  • 1 GHz
  • 512 MB RAM

  • 500 MB available hard disk space

  • Microsoft mouse or compatible pointing device
• Windows 2012 64-bit, Windows 2008 R2 64-bit

• IIS with the following components: Common Files, World Wide Web Service, and Internet Information Services Manager.

Additional requirements

Remote Intelligent Device Client installation also requires the following:

• Access to the network copy of the server setup
• Windows user account that belongs to the Administrators group

 

1. Log in to the system using an account that belongs to the Administrators group.
2. Navigate to the network where you have kept the server setup files.
3. Run \MessageServer\setup.exe. The InstallShield wizard configures your system and displays a welcome message.

4. Click Next. The setup shows the License Agreement page.

5. Review the License Agreement and select I accept the terms of the license agreement.
6. Click Next. The setup shows the installation options.

7. Select Custom and click Next. The setup shows a list of features.

8. Select Intelligent Device Client. Clear any other feature you are not installing at this time.

9. Click Next. The setup checks the system for installation requirements and displays the results.

Note: The setup cannot continue until all pre-requisite components are installed. (Double-click an item in the list for more information.) If any required components are missing, click Cancel and exit the installation setup. Install the components, then install Intelligent Device Client.

10. Click Next. The setup shows installation settings.

Note: If other installation features are included, the setup might request additional information before displaying installation settings.

11. Review the installation settings and click Next to start the installation. The setup installs the selected component and displays a message indicating that the installation is complete.

12. Click Finish.

13. Continue to Configuring the remote Intelligent Device Client.

 

Specifying the HP CR server

When you install Intelligent Device Client on a remote machine, you must specify the IP Address of the server in OmISAPIU.xml:

1. Go to ...\Omtool\Omtool Server\WebAPI\DesktopWebAPI\Scripts.
2. Open OmISAPIU.xml for editing.

Note If the server is part of a cluster, the following setting should be made in the file:

<Server Name="OmtoolServer"><ServerName> Primary_Server_name</ServerName>

<Server Name="OmtoolServer"><ServerName>Secondary_Server_name</ ServerName>

</Server>

3. Locate the ServerName node.
4. Specify the name or the IP address of the server. For example, <ServerName>[IP Address]</ServerName>.
5. Save and close the file.
6. Go to ...\Omtool\Omtool Server\WebAPI\WebAPI\Scripts.
7. Open OmISAPIU.xml for editing.
8. Locate the ServerName node.
9. Specify the name or the IP address of the server. For example, <ServerName>12.123.4.5</ServerName>.
10. Save and close the file.

Adding the remote server’s name to DCOM

1. Add the remote server’s name to DCOM on the server. For example: VMTesting$.

Note: You must append the name with a dollar sign ($).

2. Select Computers in the Object Types when adding the server name.
3. Reboot the server.

Adding the application pool logon account to the Admins group

There are application pools (WebAPI) managing the worker processes handling requests from other client applications. By default, they run as Local System.

Note: If the security policy in the LAN does not permit the application pool to run as Local System, the application pool identity can be reconfigured using any account that belongs to the Domain Users group. If you change your login to a network account, Integrated Windows Authentication will not work for the virtual directories that use the application pool. The work around requires Kerberos protocol changes in the active directory.

If necessary, modify the application pool identity. For instructions, consult the Windows documentation on IIS: http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/c9b5db6f-874e-4ec9-93ed1733367c117b.mspx?mfr=true

• If Intelligent Device Client is installed on a remote system, add the application pool logon account to the Admins group which has the required Distributed COM permissions to communicate with the server. See Creating Admins group.

• If Intelligent Device Client is installed on the server and both application pools run as Local System, skip this step.

 

Other configurations include:

• Modifying the directory security configuration of virtual directories (optional). See Optional configurations.

 

Before you remove the Intelligent Device Client, remove all other applications in the LAN that require/use the Intelligent Device Client. Then remove Intelligent Device Client.

To remove Intelligent Device Client from a remote system:

1. Click Start > Control Panel > Add or Remove Programs to open the Add or Remove Programs page.
2. Select HP CR Server and click Change/Remove. The InstallShield wizard is initialized and it shows the following message.
3. Select Remove option and click Next.
4. Follow the prompts to remove Intelligent Device Client.

During installation, Intelligent Device Client allows the IIS web server extension WebDAV to run. After Intelligent Device Client is removed, WebDAV is still allowed to run. If WebDAV should be prohibited from running, change the status of this web server extension to Prohibited. For more information, consult the Windows documentation on IIS.