CICT

FileMaker 15.0.2 Windows Update - Tests So Far

Discussion created by CICT on Sep 29, 2016
Latest reply on Oct 1, 2016 by CICT

This is where we've got to investigating the update options due to the lack of standalone Windows 15.0.2 updaters for FM Pro and Pro Advanced, which is being carried out in advance of our Citrix/RemoteApp server update tests.

 

Running the download for FM Pro and Pro Advanced creates a folder in the User\AppData\Temp\ folder.

FileMaker Pro created a folder Update-bb89e2cc-066c-4262-9725-fd2f989d5e93 containing a file fmp.15.0.2.220.updates.x64.withoutui

FileMaker Pro Advanced created a file fmpa.15.0.2.220.updates.x64.withoutui, but I didn't spot a containing folder. However, as this was the first test, we will go back and check again after seeing the FMP download.

 

Test 1 was carried out on FMPA by exiting the program, the temp file fmpa.15.0.2.220.updates.x64.withoutui was retained, despite the app exit, and copied to the Windows desktop, leaving the original file in the Temp folder. Running the Desktop located updater file as Administrator failed to run, giving the following error in the Windows Event Log:

"Product: FileMaker Pro 15 Advanced -- You cannot install or uninstall FileMaker on this system. Please refer to the system requirements in the installation instructions for more information."

 

However, launching FMPA again then running the same updater file from the Desktop did work and FMPA was updated to v15.0.2.220 without noticeably exiting and restarting (it was minimised in the background at the time, so we could access the Desktop located updater file). The fmpa.15.0.2.220.updates.x64.withoutui file in the Temp folder was deleted, the one on the Desktop was retained.

 

At this point we thought FileMaker had actively prevented us from running the installer manually.

 

However, varying the above for FileMaker Pro, the in app download created AppData\Local\Temp\Update-bb89e2cc-066c-4262-9725-fd2f989d5e93\fmp.15.0.2.220.updates.x64.withoutui.

Again, we canceled the update and exited FMP and the temp file was retained. This time we moved (as opposed to copied) the Update-bb89e2cc-066c-4262-9725-fd2f989d5e93\fmp.15.0.2.220.updates.x64.withoutui folder/file to the Desktop and it did run successfully without FMP running and was retained on the Desktop. FMP confirmed that it had been updated to 15.0.2.220

 

Our next steps are to repeat the FMP Advanced update following the same procedure as the FMP update and then see whether these files can be copied to another PC and run successfully. If so, we will proceed on to a newly built RemoteApp server and test this there, although our suspicion, flying in the face of best (safest) practice from FMI, is that putting the server into user install mode and using the in app upgrade will also work fine for streaming purposes.

 

Will keep you posted

Regards

Andy

Outcomes