Summary
Express Software Manager provides centralized deployment of the Express Client via the Express Administrative Console. Absence of certain 3rd party software and client configuration issues may cause such deployment to fail. This Technical Note describes the steps necessary to resolve these issues.

Client Fails to Install
For remote installation of the Express Client, workstations must have the following installed and enabled:

• Microsoft Windows Management Instrumentation (WMI) version 1.5 or higher
• The Windows Remote Procedure Call service
• File and Print Sharing for Microsoft Networks

The information below discusses errors that may occur when these requirements are not met. If client installation fails and the status is "Invalid Class", the most likely situation is that some of the required WMI components are not installed.

This situation is most likely on Windows 2003 Server where most of WMI is installed by default, but the WMI Install Provider is not. To remedy this on Windows 2003 Server:

• Open Add or Remove Programs from Start/Control Panel.
• Click Add/Remove Windows Components.
• Scroll down the list and select Management and Monitoring Tools.
• Click Details and select WMI Windows Installer Provider. Click OK.
• Click Next and complete the installation of the WMI Windows Installer Provider component.

Once the proper WMI components are installed, you can reissue the installation request. Remote installation requires that proper credentials be supplied when the installation request is made. Supplied credentials must have administrative privileges on the target client machine(s) in order for the installation to be successful. Here are some tips in making sure the credentials are specified correctly:

• Credentials should include both the domain and user name. For example, if you are using an account named "itmanager" on which is a domain administrator account on the "mycompany" domain, you'd specify the full user name as:
  mycompany\itmanager
• DCOM must be enabled on the target client machine. You can check the following registry setting to determine whether or not DCOM is enabled:
  HKEY_LOCAL_MACHINE\Software\Microsoft\OLE\EnableDCOM
  A value of Y indicates DCOM is enabled; N indicates it is disabled. See also this Microsoft Knowledgebase article: http://support.microsoft.com/default.aspx?scid=kb;en-us;825750.
• One way you can verify that a particular set of credentials has the required privileges to install to a particular machine is to check to see if the target machine's admin$ share can be accessed. From Start/Run, enter:
  \\target-machine\admin$
  (where "target-machine" is the name of the client machine) and enter the credentials you plan to use to install. If you can not access the machine's administrative share with this set of credentials, you won't be able to install the client remotely.
• The target client machine must be a member of the domain of which the domain administrator account being used exists. The machine does not have to be logged into the domain, just be a member of it.

You can use alternate methods such as installing via login scripts or on the machine directly if you don't have the required access remotely to the client. Note, however, that part of the Express Client runs as a service even when the machine is not logged in and therefore must be installed using a privileged account. A client installation failure with a status of "RPC Server Not Available" can result in two different situations:

The Windows RPC Server is not started
The Remote Procedure Call service must be running on the client machine to allow the Express Server to connect to it and install the client. Normally this service starts automatically on system boot-up. You can check the status if this service as follows:

• From Start/Control Panels, Select Administrative Tools, then Services to display the list of services installed on your system.
• Find the Remote Procedure Call Service. Make sure it is running and set to start automatically on startup.
• If the service is stopped, right click the name and select Start.
• If the services specifies startup type as manual rather than automatic, right click the service, select Properties, click on the General tab and change the startup type to Automatic.

File and Print Sharing are not enabled
File and print sharing must be installed and enabled to allow the client installation process to copy installation files to the client. You can check to see if it is installed as follows:

• From Start/Control Panels, select Network Properties or Network and Dialup Connections/Local Area Connection, depending on your operating system. This will bring up a properties dialog showing you the networking components you have installed.
• Make sure that File and Print Sharing for Microsoft Networks is installed and enabled.
• If it is not installed, click Install, select Client, then click Add. You will see a list of networking clients; select File and Print Sharing for Microsoft Networks and click OK to install this component.