For those of you wondering how Laserfiche 9.2 will work on the up and coming Windows 10, so far it is working on my test machine with no current issues.
The KB article will go out later today as KB 1013672
All 9.2 version products are compatible with Windows 10.
There is a known issue where some of the web products will not install because the installer does not correctly detect the IIS version. The KB article details the workaround for it.
Additionally, Microsoft Edge does not offer extension/plugin support, which will affect detection of Web Scanning, Office Integration and digital signatures in Web Access. The workaround there is to use IE or another browser.
Thanks, Blake! We played with Windows 10 here too and there were no problems with LF software on it.
What plans do Laserfiche have to officially announce compatibility of Laserfiche products on Microsoft Windows 10?
I'm not sure what you're looking for. Windows 10 is not out yet. We're testing the builds as Microsoft releases them (on the fast track).
The official release date of Microsoft Windows 10 is 29th July 2015.
I would expect to see an official announcement at or around that time. It would be inappropriate to officially announce support off of pre-release builds although, as Miruna has noted, we're not encountering any notable issues so far.
Microsoft Windows 10 is officially released TODAY. Any news when Laserfiche will officially announce compatibility of Laserfiche products with Microsoft Windows 10?
The KB article will go out later today as KB 1013672
All 9.2 version products are compatible with Windows 10.
There is a known issue where some of the web products will not install because the installer does not correctly detect the IIS version. The KB article details the workaround for it.
Additionally, Microsoft Edge does not offer extension/plugin support, which will affect detection of Web Scanning, Office Integration and digital signatures in Web Access. The workaround there is to use IE or another browser.
Hi Miruna -
Does the compatability extend to Win 10 versions like Home and Pro?
Thanks
Home, no, because it does not offer Windows Authentication. You have to upgrade to Pro, which does allow Windows Authentication, both in IIS and as a member of a domain. Workflow installed OK on Pro (it failed on home, for the same reason) and we are working through some other issues with Web Access. To be continued...
Update - we have WA 9.2 running on a Win 10 Pro machine. The installation is a little quirky. Here is a summary of the steps we had to use:
Turn off UAC for the account you'll use for installation.
We logged in as Owner, and got no UAC Prompts.
IIS registry key set to 8 major version, in HKEY_Local_Machine and in Wow6232Node
Make sure World Wide Web (IIS) is installed with ASP 4.5, .net extensibility 4.5, ISAPI Extensions and Filters, Static Content, Basic and Windows Authentication
Accept the default offered, "ApplicationPoolIdentity" for the WA Service. Otherwise, it thinks IIS is not installed.
It should pass the Web Access Prerequisites.
Set the IIS registry keys back to 10 major version, in HKEY_Local_Machine and in Wow6232Node.
Change the WebAccessApplicationPoolIdentity set to MachineName\Owner in IIS.
The pool was restarted. Then ISS restarted. And it worked!
Shout out to Shule about the tip to use a real account for the ApplicationPoolIdentify.
Update 2: It looks for Forms and Mobile, you also have to change the registry keys (both of them) otherwise IIS detection will fail and roll back your installation.
On the other hand Workflow Web Designer worked fine without this.
Hi Bill,
Having to update the IIS value is covered in the KB: https://support.laserfiche.com/KB/1013672.
Are there items you ran into that aren't covered in the KB article that are specific for Windows 10? Some of these are general requirements (such as making sure the IIS components are enabled).
Hi Justin -
Yes, there are some items that were specific to Win 10. We are finding that both Win 10 and Server 2012 are very particular about a range of file and access permissions. In several cases, we were not able to get servers/other products installed and running by selecting Local System as a default user, or the IE default users. More often than not, we are having to use a local account with administrator privileges in place of Local System and the IIS equivalent. This is for the set up where everything is on one machine.
Our suggestion is to try using the defaults accounts anyway, but in the event of any installation error, go back and use an administrator or owner account instead.