Views:

Table of Contents

Background

Microsoft removed the Interactive Services Detection Service on Windows 10 Version 1803 and Windows Server 2019. With this change, the run as a service option in LogWare III does not work on these versions of Windows.

In all versions of Windows 10, Windows Server 2016 and Windows Server 2019, Microsoft removed the keyboard and mouse interactivity on Session 0. This prevents interacting with the Interactive Services Detection session.

It is possible to set up LogWare to run as a service using third-party software. These software tools are not free and are available from each company’s web sites. The following instructions are for some third-party tools we have found to help set up LogWare III to run as a service. See Other Information for links to the web sites.

 

 

Windows Server 2019 and Windows 10 Version 1803 and Newer

Add Interaction with services running on session 0

Because Microsoft removed the Interactive Services Detection Service, third-party software is required to get access to the UI while LogWare III is running as a service. FireDaemon Technologies Limited has software that enables this access. To install their software:

  • Download the FireDaemon Zero installer from their web site. There is a 30-day trial for testing purposes.
  • Double-click the FireDaemon Zero installer to display the Welcome screen.
  • Follow the installation screens to complete the installation.
  • The software is ready to use. NOTE: There are steps below for using the software.

Keyboard and Mouse interaction for Session 0

In all versions of Window 10, Windows Server 2016 and Windows Server 2019, Microsoft removed the keyboard and mouse interactivity on Session 0. FireDaemon Technologies Limited has a driver that restores the keyboard and mouse interactivity. To install the driver:

  • Download the FireDaemon ZeroInput zip file from their web site.
  • Extract the files to a folder.
  • Navigate to the new folder, right click on the FDUI0Input.INF file, and select the Install menu option.
    mceclip0.png
  • There is no notification if the installation was successful, but if it fails a message is displayed.

Set up LogWare III to run as a service

The Windows tools used for setting an application to run as a service on older versions of Windows do not work on Windows 10 Version 1803 and Windows Server 2019. Core Technologies Consulting, LLC has their AlwaysUp software that works on the new operating systems.

  • Download the AlwaysUp installer from their web site. There is a 30-day trial for testing purposes.
  • Run the AlwaysUp installer to display the Welcome screen.
  • Follow the installation screens to complete the installation.
  • The software is ready to use.
  • Launch the AlwaysUp software.
  • Select the Add a new application toolbar button.
    mceclip1.png
  • Add Application dialog is displayed.
  • Enter a name for the service (i.e. LogWare III Client Service)
  • Use the browse button next to the Application text box to select the Logware3 executable or type in the full path. The default path is C:\Program Files (x86)\Fluke Calibration\LogWare III Client\LogWare3.exe.
    mceclip2.png
  • Select the Save >> button. NOTE: There are other options available with the AlwaysUp software you might find useful. Review the other tabs of the Add Application dialog for more capabilities.
  • On the AlwaysUp main screen, the service will appear in the Applications list and the state is stopped. You can start the service from here but there are still more setup steps and the computer will need to be restarted later.
    mceclip3.png
  • Close the AlwaysUp application.

LogWare setup

When LogWare runs as a service, the application does not run under a specific user account. There is a LogWare3.ini file in the C:\ProgramData\Fluke Calibration\LogWare III Client. This file contains the settings for the log sessions to start automatically and the user account for logging in at startup. Depending on the rights of the user doing the setup, this file may not actually get updated in the C:\ProgramData\Fluke Calibration\LogWare III Client folder. Windows may create a virtual store folder under the user’s profile to save the LogWare3.ini file settings. When LogWare starts as a service it will use the LogWare3.ini file in the C:\ProgramData\Fluke Calibration\LogWare III Client folder that does not have the correct setup. To resolve this, launch LogWare III by right clicking on the desktop shortcut and select Run as an administrator. Now all settings are saved in the LogWare3.ini file in the C:\ProgramData\Fluke Calibration\LogWare III Client folder.

Reboot

After all of the steps above are complete, reboot the computer.

Usage

Once Windows is running again, you will see a new FireDaemon Zero icon in Task bar notification area.

mceclip4.png

Double-click this icon to display the LogWare III UI in session 0. To exit the session 0, double-click FireDaemon Zero icon in the task bar or right click on the icon for menu options.

mceclip5.png

By default, session 0 will automatically close after 30 seconds but this is changeable by right-clicking on the FireDaemon Zero icon in Task bar notification area and selecting Options. Select the Quirks tab to turn of the Automatic return after 30 seconds.

mceclip6.png

 

 

Windows Server 2016 and Windows 10 Prior to Version 1803

Keyboard and Mouse interaction for Session 0

In all versions of Windows 10, Windows Server 2016 and Windows Server 2019, Microsoft removed the keyboard and mouse interactivity on Session 0. FireDaemon Technologies Limited has a driver that restores the keyboard and mouse interactivity. See Other Information for links to the web sites.
To install the driver:

  • Download the FireDaemon ZeroInput zip file from their web site.
  • Extract the files to a folder.
  • Navigate to the new folder, right-click on the FDUI0Input.INF file, and select the Install menu option.
    mceclip0.png
  • There is no notification if the installation was successful, but if it fails a message is displayed.

Enable Windows Interactive Services

Run RegEdit to open the Registry Editor. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows. Verify the NoInteractiveServices value is set to zero. If the value is “1”, double-click on the item and change it to “0”.

mceclip8.png

Close the Registry editor.

Launch the Services application in Windows. Find the Interactive Services Detection service in the list of local services.

mceclip9.png

If the service startup type is set to Manual, right-click on the item in the list and select Properties. On the Properties dialog, set the Startup type to Automatic.

mceclip10.png

Select the OK button to close the Properties dialog. The status will still be blank but that is fine. This will start automatically after a reboot later.

LogWare Setup

When LogWare runs as a service, the application does not run under a specific user account. There is a LogWare3.ini file in the C:\ProgramData\Fluke Calibration\LogWare III Client. This file contains the settings for the log sessions to start automatically and the user account for logging in at startup. Depending on the rights of the user doing the setup, this file may not actually get updated in the C:\ProgramData\Fluke Calibration\LogWare III Client folder. Windows may create a virtual store folder under the user’s profile to save the LogWare3.ini file settings. When LogWare starts as a service it will use the LogWare3.ini file in the C:\ProgramData\Fluke Calibration\LogWare III Client folder that does not have the correct setup.

To resolve this, launch LogWare III by right-clicking on the desktop shortcut and select Run as an administrator. Now all settings are saved in the LogWare3.ini file in the C:\ProgramData\Fluke Calibration\LogWare III Client folder.

Log in to LogWare III using an account that has the rights to edit the LogWare III Options. Select the Tools | Options menu option. On the General tab:

  • Check the “Automatically start Real-Time Log Session(s) upon login” option.
  • Add any log session configuration files to the list you want to start up automatically.
  • Check the “Enable LogWare auto-login” option.
  • Select the user account for logging in automatically. NOTE: This must be an account that does not have a password. Otherwise, each time the service starts, someone will have to enter a password.
    mceclip11.png
  • Select the Misc tab. Check the “Run LogWare as a service on this computer” option.
    mceclip12.png
  • Select the OK button.

Reboot and Usage

After all of the steps above are complete, reboot the computer. When Windows is running again, there should be an Interactive Services Detection icon flashing in the toolbar.

mceclip13.png

NOTE: The icon may take a few minutes to appear.

Click on the Interactive Services Detection icon to show the Interactive Services Detection notification.

mceclip14.png

Select “View the message” to view the LogWare III UI in Session 0. To return, select the “Return now” option.

mceclip15.png

 

 

Windows Server 2012 R2 and Windows 8.1

Enable Windows Interactive Services

Run RegEdit to open the Registry Editor. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows. Verify the NoInteractiveServices value is set to zero. If the value is “1”, double-click on the item and change it to “0”.

mceclip8.png

Close the Registry editor.

Launch the Services application in Windows. Find the Interactive Services Detection service in the list of local services.

mceclip9.png

If the service startup type is set to Manual, right-click on the item in the list and select Properties. On the Properties dialog, set the Startup type to Automatic.

mceclip10.png

Select the OK button to close the Properties dialog. The status will still be blank but that is fine. This will start automatically after a reboot later.

LogWare Setup

When LogWare runs as a service, the application does not run under a specific user account. There is a LogWare3.ini file in the C:\ProgramData\Fluke Calibration\LogWare III Client. This file contains the settings for the log sessions to start automatically and the user account for logging in at startup. Depending on the rights of the user doing the setup, this file may not actually get updated in the C:\ProgramData\Fluke Calibration\LogWare III Client folder. Windows may create a virtual store folder under the user’s profile to save the LogWare3.ini file settings. When LogWare starts as a service it will use the LogWare3.ini file in the C:\ProgramData\Fluke Calibration\LogWare III Client folder that does not have the correct setup.

To resolve this, launch LogWare III by right-clicking on the desktop shortcut and select Run as an administrator. Now all settings are saved in the LogWare3.ini file in the C:\ProgramData\Fluke Calibration\LogWare III Client folder.

Log in to LogWare III using an account that has the rights to edit the LogWare III Options. Select the Tools | Options menu option. On the General tab:

  • Check the “Automatically start Real-Time Log Session(s) upon login” option.
  • Add any log session configuration files to the list you want to start up automatically.
  • Check the “Enable LogWare auto-login” option.
  • Select the user account for logging in automatically. NOTE: This must be an account that does not have a password. Otherwise, each time the service starts, someone will have to enter a password.
    mceclip11.png
  • Select the Misc tab. Check the “Run LogWare as a service on this computer” option.
    mceclip12.png
  • Select the OK button.

Reboot and Usage

After all of the steps above are complete, reboot the computer. When Windows is running again, there should be an Interactive Services Detection icon flashing in the toolbar.

mceclip13.png

NOTE: The icon may take a few minutes to appear.

Click on the Interactive Services Detection icon to show the Interactive Services Detection notification.

mceclip14.png

Select “View the message” to view the LogWare III UI in Session 0. To return, select the “Return now” option.

mceclip15.png

 

 

Other Information

Keywords: Logware, Service, Logware III, Temperature, Logging