Defining a custom login script is not an operation you perform with OpenAFS. Instead you define your own Network Provider to configure a login script OR you define your own WinLogon Event handler and perform
the drive mapping in the Logon Event.

Jeffrey Altman

Mike Bydalek wrote:
One of the last obstacles I have to rolling out OpenAFS company wide is that of Windows. So far, I have everything working beautifully with single sign-ons with a MIT Kerberos realm. The final part of my Windows setup is that of getting the data off the client machines and onto the AFS server.

One of the caveats to using the Kerberos logins is that you need a local account, which contains a local profile. What I did was map all my users to this account. What I need to do is have it redirect folders to the appropriate /afs directory, or (ideally) use roaming profiles. I've come across a really interesting page regarding this at http://www.coe.uncc.edu/~rmdyer/krblogon.htm. The problem is that this just seems overkill for my setup.

All I want to do is just have one additional drive map to /afs/.../home/%USERNAME% when a user logs in, and redirect the desktop and "My Documents" (Start with the basics).

Does anyone know of a good way to do basic things like this when logging into Windows? I don't see a way to call a login script via. the OpenAFS 1.4.1-rc2 client that I'm testing.

Thank you,
Mike
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to