[OpenAFS] Client install on Windows Server 2012R2

Garrison, Christine ecgarris@iu.edu
Mon, 27 Jun 2016 21:25:19 +0000


Thanks, Jeff.=0A=
=0A=
As usual, I am asking my questions clumsily.=0A=
=0A=
What should my user install in order to use OpenAFS client on his Windows S=
erver 2012R2 machine? We have somewhat dated instructions for configuring t=
o our cell in IU's KB, and I'm trying to clarify for him to be able to get =
set up and working. =0A=
=0A=
I don't want to make him use our rickety Samba gateway for this purpose in =
particular; efficiency and untranslated access to the fileservers is import=
ant.=0A=
=0A=
Thanks again for your help.=0A=
=0A=
Christine=0A=
--=0A=
E. Christine Garrison=0A=
Indiana University=0A=
Research Technologies=0A=
Research Storage=0A=
=0A=
________________________________________=0A=
From: Jeffrey Altman <jaltman@auristor.com>=0A=
Sent: Monday, June 27, 2016 5:09 PM=0A=
To: Garrison, Christine; openafs-info@openafs.org=0A=
Subject: Re: [OpenAFS] Client install on Windows Server 2012R2=0A=
=0A=
On 6/27/2016 3:33 PM, Garrison, Christine wrote:=0A=
> Hello OpenAFS folks,=0A=
>=0A=
>=0A=
> I've got a user with a Win 2012R2 Server that's trying to install and=0A=
> configure the OpenAFS for Windows client. Their OS is 64 bit.=0A=
>=0A=
>=0A=
> We tried an install of OpenAFS for Windows 1.7.31 from the openafs.org=0A=
> website, but got a missing DLL error (sorry, he closed the shared screen=
=0A=
> too fast for me to jot it down) when trying to run the server manager to=
=0A=
> do a config of the cell.=0A=
=0A=
Christine,=0A=
=0A=
None of the cell management GUI tools work on Windows.  Just don't=0A=
install them or expect them to work.  The "Server Manager" literally a=0A=
tool for managing the cell not the client.=0A=
=0A=
> We're more familiar with the 1.6.x client here; can it be run on Win=0A=
> Server 2012R2?=0A=
=0A=
The OpenAFS 1.6 clients on Windows use the SMB gateway interface that=0A=
doesn't work on Windows 7 or above.=0A=
=0A=
FYI, as of July 29th all new installations of Windows will require=0A=
Secure Boot.  At that time Microsoft signed device drivers will become=0A=
mandatory.  AuriStor, Inc. hopes to have its Windows client approved for=0A=
Microsoft's signatures by that date.=0A=
=0A=
Jeffrey Altman=0A=
=0A=