Jeffrey, I am running Windows 10 Education on x64 architecture. The version of the AFS client I am installing is 1.7 provided by YFS. *yfs-openafs-en_US-AMD64-1_7_3301.msi *I've installed it along with one dll file - afscreds_1033.dll. But thanks to the information you provided I was able to get it running.
Thanks for your help, On Fri, Sep 2, 2016 at 10:40 AM, Jeffrey Altman <jalt...@auristor.com> wrote: > On 9/1/2016 4:07 PM, Odoom, Jason wrote: > > > > Hello, > > > > I've been having difficulty installing OpenAFS on Windows 10. I receive > > the error "Installation of network provider failed" when installing the > > OpenAFS client msi package. I saw from a previous mailing list[1] that I > > have to run the msi with administrative privileges. However, that does > > not fix the issue. How do I fix this issue? > > > > [1]:https://lists.openafs.org/pipermail/openafs-info/2011- > January/035370.html > > <https://lists.openafs.org/pipermail/openafs-info/2011- > January/035370.html> > > > > Any assistance would be appreciated, > > > > > > -- > > -Jason Odoom > > ARCS Student Assistant > > Jason, > > When requesting assistance it is important that you be specific about > the variables in your environment: > > * what version of Windows are you using? You say Windows 10 > but Windows 10 is a moniker that describes every version of > Windows shipped since 29 July 2015 as well as many different > variants? > > home, professional, educational, enterprise, tablet, mobile, IoT, ... > > x64, x86, arm, ... > > Within each variant there are major milestone releases with > different features and requirements. > > * what version of OpenAFS are you installing and whose packaging? > > > If you are not already aware, the OpenAFS client for Windows 1.7.x is > implemented with several "system" component extensions > > * two file system drivers > > * two network provider dlls. one for authentication and one for > interfacing with the file system drivers to support drive letter > mapping, path evaluation, etc. > > * a system service > > * a suite of file explorer object classes > > All of the OpenAFS MSIs and the binaries included within them were > signed by Your File System, Inc. with a SHA1 hash. Microsoft has warned > for years that SHA1 code signing would be deprecated. Due to additional > weaknesses in SHA1 hashes Microsoft and Mozilla decided to accelerate > the deprecation process. > > https://blogs.windows.com/msedgedev/2015/11/04/sha-1-deprecation-update/ > > While SHA1 signed MSIs are still accepted, SHA1 signed system binaries, > depending upon the Windows variant and domain policy, are not. An > attempt to install a system binary on a system that requires SHA2 > signatures will fail. > > Also, it is important to note that as of Windows 10 version 1607 the new > driver signing requirements for file system drivers are being enforced. > > https://blogs.msdn.microsoft.com/windows_hardware_ > certification/2016/07/26/driver-signing-changes-in- > windows-10-version-1607/ > > However, I doubt that this is the cause of the problems you are > experiencing. Last night I clean installed the 1607 professional 1607 > build on both x86 and x64. The AuriStor distributed OpenAFS for Windows > installers (1.7.3301) that utilize the AuriStor (formerly Your File > System) packaging installed successfully on both systems and the client > operated as expected. The drivers included in this installer are > accepted under the grandfather exception for cross-signing certificates > issued before 29 June 2015. > > Jeffrey Altman > > -- -Jason Odoom ARCS Student Assistant
