We have various devices that have been deployed over the years and for some reason, random devices (a few hundred) appear to be missing files within the LMI installation folder. For example, a third_...
Hi HappyHippo,
The software already runs a check when it starts up, any errors encountered should be captured in the log file. As debug logging is not enabled by default, the logs may not have all the details. If you have a computer that you have not run the script on yet, could you first enable debug logging and then:
- wait a day before running the script on it?
- reboot the computer and wait an hour or so before running the script on it?
Once you have the debug logs please create a support ticket and attach them.
For the Windows Update issue. We would need also need debug LMI logs and Windows Update logs to compare. The best thing to do for that is:
- Enable debug logging on the LogMeIn host
- Go into LogMeIn Central > Updates > Windows > select a host
- Under the Update settings page for that host, click on Check for Updates now
- After 30 minutes grab the debug log off the host and create a Windows update log:
To create the Windows Update Log:
- Open PowerShell.
- Type the following command at the PowerShell console: Get-WindowsUpdateLog3. When it finishes running, the cmdlet will create the classic WindowsUpdate.log file in your Desktop folder.