Re: Windows Non-Interactive Logons (aka Scheduled Tasks) and AFS

Christopher D. Clausen wrote:
> Jeffrey Altman <[email protected]> wrote:
>> Is anyone going to be upset if I disable integrated logon support for
>> non-interactive logon sessions such as those produced by "Scheduled
>> Tasks"?
> 
> Sounds good to me.  In fact, I'd prefer it if integrated logon was not 
> enabled by default in the installers.

What do you mean by this?

Do you mean that "afslogon.dll" should not be registered as a Network
Provider or that it should not obtain "AFS" tokens?

>> It has been brought to my attention that for each non-interactive
>> logon session a new Kerberos v5 credential cache server is being
>> spawned.  As
>> a result, some systems that provide large numbers of remote process
>> executions are falling over when the maximum number of processes is
>> reached.
>>
>> I have committed code to disable integrated logon support until such
>> time as I can figure out how to ensure that when the executed process
>> terminates that the Kerberos v5 credential cache server is terminated.
> 
> Ah, ok.

I should have said "disabled integrated logon support for
non-interactive logons".   Integrated logon for interactive logons is
still present.

Jeffrey Altman