Using su.exe under the Task Scheduler is a bad idea: It implies
that you have a batch file with an unencoded password. A much
safer solution is to specify under the Task Scheduler the account
under which the task should run, thus eliminating the need for
su.exe.


"fred" wrote in message
news:bn08b4$3bv$1@news.x-echo.com...
> Does anyone have had problem with su.exe (from the Res Kit) service afte
> r applying the MS03-39 patch on RPC ?
> I can't have it work since this patch has been applied on a W2K computer
> Everything was fine : I have a scheduler that launches su tasks every
> day. And now, it doesn't work anymore : no error message, rights assigne
> ment and service are ok, but the task won't launch...
> If someone have any idea...
> thanks for your attention.
>
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Article poste via Voila News - http://www.news.voila.fr
> Le : Mon Oct 20 11:02:28 2003 depuis l'IP : 81.255.30.220 [VIP
726496316247]