STP.Updater Client

The STP.Updater Client receives patches and updates for selected STP programs from the STP.Updater Server and installs them on the local workstation.

Client Service

The STP.Updater Client allows for the updating of STP client applications without needing to be logged in as a local administrator.

The update is carried out by the Windows service STP.Updater ClientUpdateService, which has the necessary administrative rights assigned.

Client Application

The client application receives patches and updates for selected STP programs from the STP.Updater Server and passes them to the STP.Updater ClientUpdateService. The service then performs the update.

Settings

To manually change the settings for the STP.Updater Client, right-click the STP.Updater Client icon in the taskbar and select "Settings..." from the context menu.

On Windows 7 and Windows Vista, you must confirm the launch of the configuration program in User Account Control. Click this icon in the taskbar:

If necessary, enter the username and password of a local administrator and click the Yes button in User Account Control.

On Windows XP, the "Run As" window opens. If you are logged in as a local administrator, uncheck the box to protect the computer and data from unauthorized program activity and click the OK button.

If you are not logged in as a local administrator, select the option button for Another User, enter the username and password of a local administrator, and click the OK button.

In the "STP.Updater Client – Settings" window, you can configure the check frequency and the connection to the STP.Updater Server.

Check Frequency

  • "Daily": Select this option and enter a time in the input field. The update check occurs once daily at the specified time.
  • "Hourly": Select this option, and the update check occurs once per hour.
  • "Every 5 Minutes": Select this option, and the update check occurs every 5 minutes.
  • "Manual": Select this option, and the update check occurs when you click "Check for Updates" from the STP Client Updater context menu.

Connection to the Updater Service

Hostname/IP Address

  • Enter the computer name or IP address of the STP.Updater Server.

Port

  • Enter the port used by the Windows service

STP.Updater Server for communication with the STP.Updater Client.

The startup type set during the STP.Updater Client setup cannot be changed later through these settings. Run the STP.Updater Client setup again to change the startup type.

Start STP.Updater Client

Depending on the configuration chosen during setup, the STP.Updater Client starts automatically when Windows starts. You can also start the STP.Updater Client via

Start > Programs > STP AG > Administration > STP.Updater Client

or

Start > All Programs > STP AG > Administration > Start STP.Updater Client.

The STP.Updater Client icon will then appear in the taskbar.

The server is reachable.

If the STP.Updater Server is not reachable or the Windows service STP.Updater ClientUpdateService is not started, the STP.Updater Client icon in the taskbar will be crossed out.

You will also receive a notification if the STP.Updater Server is not reachable or if the Windows service STP.Updater ClientUpdateService is not started on the [workstation].

Updating Client Service and Application

The STP.Updater Server must be up to date.

The product repository directory must contain a suitable UpdateManifest.xml file and the setup for the current version.

When the application starts, it automatically checks for available updates. According to the set option, the updater will automatically check for updates at specified intervals. If updates are found, you will receive a notification. You can choose to perform or cancel the update. You will be notified again about the available update during the next check.

To manually update the STP.Updater Client, right-click the STP.Updater Client icon in the taskbar and select "Check for Updates" from the context menu.

Update STP Client Programs

The program must support the STP.Updater Client. The setup or patch files must be placed in the product repository directory. This is done through the server setup of the corresponding client application or by manually placing them in the product repository.

When the STP.Updater Client starts, it automatically checks for available updates. According to the set option in the updater, the STP.Updater Client will automatically notify you of available updates at specified intervals.

If updates are found, you will receive a notification. You can choose to perform or cancel the update. You will be notified again about the available update during the next check.

To manually update an STP client program, right-click the STP.Updater Client icon in the taskbar and select Check for Updates from the context menu or start the update search with a double-click on the STP.Updater Client icon in the taskbar.

Check for Updates

The search for updates occurs automatically at the configured intervals. If you selected the Manual option during setup or in the STP.Updater Client settings, no automatic search will occur.

You can also manually start the search for updates at any time. Double-click the STP.Updater Client icon to start the search for available updates.

All STP applications configured for the STP.Updater Client will be checked for new patches and updates. If a patch or update is found, you will be notified. You can choose to perform or cancel the update. You will be notified again about the available update during the next check.

If you agree to the update, it will be executed.

If the application is still open, you will receive a corresponding message. Close the application and confirm the message with Yes, and the update will be executed.

Updates for the STP.Updater Client are always executed first. After restarting the STP.Updater Client, it will check for available updates again.

The scheduled search for updates will not be executed if the user logs off the workstation.

On a terminal server, applications should not be updated on a timed schedule because the terminal server needs to be put into a special operating mode for this. However, since the STP.Updater Client is a prerequisite for installing other STP client applications, it must be present on the computer before installing the STP client application.

The Windows service STP Updater ClientUpdateService is disabled by checking the box for installation on a terminal server.

Note
It is not checked whether the installation is actually on a terminal server.

Additionally, regardless of the selected setting of the installation checkbox on a terminal server, the start of the STP.Updater Client on a terminal server is prevented.

The STP.Updater Server is not reachable.

  • Start the Windows service Updater Server on the server.
  • Check the network connection. Is the server reachable?
  • Check the firewall settings on the server and on the workstation computer.

The STP.Updater Client service is not running.

  • Start the Windows service Updater ClientUpdateService on the workstation computer.

Log File

The STP.Updater Client writes log files to the following folders:

Windows Server 2008/Vista/Windows 7

  • C:\Users\<Username>\AppData\Local\STP AG\

    Updater Client\Logs

  • C:\Users\<Username>\AppData\Local\STP AG\STP.Updater.ClientUpdateUI\Logs

The Windows service STP.Updater ClientUpdateService writes log files to the folder:

  • C:\Windows\System32\config\systemprofile\AppData\Local\

    STP AG\STP.Updater.ClientUpdateServer\Logs

Windows Server 2003/Windows XP

  • C:\Documents and Settings\<Username>\

    Local Settings\Application Data\STP AG\

    Updater Client\Logs

  • C:\Documents and Settings\<Username>\

    Local Settings\Application Data\

    STP AG\STP.Updater.ClientUpdateUI\Logs

The Windows service STP.Updater ClientUpdateService writes log files to the folder:

  • C:\Documents and Settings\LocalService\Local Settings\Application Data\STP.Updater.ClientUpdateServer\Logs

These files may be empty as only errors are logged. The directory C:\Documents and Settings\LocalService is a hidden directory.

Except for the files LogConfig.xml and LogFile.txt, you can delete all log files if you do not need them for troubleshooting.

Related to