I did a great deal of work with this about 3 weeks ago.
All my testing was with the 3.5 client, but some of
this should be applicable to earlier clients. We
also run an aklog-style environment, and have our
own software on the NT machines to get tickets/tokens.
Problem #1 is the afsdsbmt.ini file - which we programatically
modify to map a home drive for each user, creating a submount
of \\blah-afs\username to the user's home directory. The
WritePrivateProfile* functions map the .ini writes/reads to
the user's profile\windows directory, while the AFS service,
running as system, expects afsdsbmt.ini to be in C:\WTSRV\
This is straight Terminal Server, I know at one time WinFrame
handled this better, I don't know about MetaFrame.
You can handle the afsdsbmt.ini deal by setting compatibility
flags for each app that would modify afsdsbmt.ini - but I had
lots of reaaaallly slow access times doing the SetToken calls
we do for the aklog-style setup. It eventually would work, but
times were in the high seconds (50-60) range.
We're actually a source code customer, but I did not look
through the source code to see how the service handles tokens
on behalf of the user. I have some concerns with multi-user
access here, but I imagine it's done okay because it did appear
to work.
However, I haven't looked at the source for this either, and
don't know how the disk caching is supposed to work for AFS,
but I had some possible concerns with multiple write access
to the AFSCache file.
I've decided, mosty because of the time delays setting the
tokens, to hold off trying to support it here. There
might also be some licensing issues, with it being licensed
on a per client basis, where you'd have to buy enough client
licenses equal to the license count on the Terminal Server.
Jason
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Daniel Blakeley
> Sent: Wednesday, August 11, 1999 2:46 PM
> To: [EMAIL PROTECTED]
> Subject: AFS and Microsoft Terminal Server
>
>
>
> Has anyone been able to get Microsoft Terminal Server to work with NT
> AFS? We want our UNIX systems to be able to occasionally use Windows
> applications. So Terminal Server with Cytrix UNIX clients seemed like
> a good idea. AFS 3.4 patch 11 for NT doesn't seem to work.
>
> - Daniel
>
> --
> Daniel Blakeley (N2YEN) Cornell Center for Materials Research
> [EMAIL PROTECTED] E20 Clark Hall
