Hello again, We made this test with secure boot enabled. Could still install the client "in the future".
We tried this on versions 1607, 1703 and 1709. MVH Anders -----Original Message----- From: Lars Schimmer [mailto:l.schim...@cgv.tugraz.at] Sent: den 9 december 2017 14:09 To: Anders Nordin <anders.j.nor...@ltu.se>; Andreas Ladanyi <andreas.lada...@kit.edu>; openafs-info@openafs.org Subject: Re: [OpenAFS] Windows 10 Pro and OpenAFS Client On 2017-12-08 13:20, Anders Nordin wrote: > Hello, > > What does this mean exactly? Will it be possible to install the > OpenAFS-client after 31.12.2017? Is it just an academic problem? We set a > computers BIOS to the future and, installed the OS (non-networked) and then > installed the client (non-networked), and it worked fine. It is a real issue. Because WIndows 10 compatibility is only signed with secure mode. Also the new Windows secure settings and anti-malware tools do only work in secure mode reliable. Also some companies do have the need to enable secure boot. And, nevertheless, no one knows what changes MS will do next time without announcing it. OpenAFS needs a substainable big contribution into the MS branch with getting a MS signature and be a valid kernel driver for the next years. To bad my gorup can´t do that (20 people only) and so we do migrate away from the AFS. > MVH > Anders MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schim...@cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723
