Christof Hanke wrote: > Hi, > > is there an intrinsic automatic update mechanism to be expected for the > OpenAFS Client for Windows ? > If not, is there a guaranteed mechanism to do it by a script ?
I have not had anyone approach me with a request for designing an auto-update mechanism or funds to support implementing one. If you are deploying the MSI via Active Directory you can perform the upgrade via the same mechanism. The installers when run in interactive mode will upgrade previous installations. > Secondly, I'd like to know in what timeframe the systray tool will be > replaced. People are here reluctant to roll out the Client with the > obsolete drive mapping. The Network Identity Manager will be a part of MIT Kerberos for Windows 3.0 which is due out in early December. OpenAFS for Windows 2.0 will ship with it next year. Secure Endpoints will provide an AFS Plug-in for KFW 3.0 that can be used to add the missing AFS functionality. The plug-in will support the acquisition of AFS tokens via Kerberos 5 or krb524d. Tokens for multiple cells can be obtained from a single Kerberos 5 identity. The use of Kerberos 5 or krb524d for token construction is configurable by cell. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
