Using the Client Status View

The Client Status view displays the current status of remote clients, including the following information:

  • The last time each remote client synchronized

  • The product versions of each remote client

  • The last time Siebel Remote extracted and initialized each remote client

  • The amount of free disk space, in bytes

Siebel Remote updates the data in this screen at the start and end of each synchronization. It does not update this data in the following situations:

  • During an initialization

    If the Free Disk (Bytes) field is reset to zero during a database extract.

  • After applying modifications to the local database if these modifications are applied after data transfers are complete

In these situations, because the work occurs after the remote client disconnects from the Siebel Server, Siebel Remote does not update data in the status screen until the next synchronization. To help avoid running out of disk space on the local computer, the user can examine this information during this next synchronization.

To use the Client Status view

  1. Log in to the Siebel Server with administrator privileges.

    For more information, see Logging in to the Siebel Database as an Administrator.

  2. Navigate to the Administration - Siebel Remote screen, and then the Client Status view.

  3. In the Mobile Clients/Replication Servers list, choose the remote client that you must monitor.

  4. Examine the Siebel Remote Client Status form that displays details for the remote client that is currently chosen in the Mobile Clients/Replication Servers list.

    For more information, see the table in Fields in the Siebel Remote Client Status Form.

Using the Client Status View with Siebel Anywhere

The Product Version field describes the Siebel Anywhere Upgrade kit that the user applied. This information is typically one session behind the current state of the upgrade. When you are using Siebel Anywhere, Siebel CRM does not update the Product Version field with the version information until after the upgrade finishes, and then after the user finishes the next synchronization.