> I cannot get a perl script to run as the logon script in NT4. Perl is
> installed on the client, but none of the Domain Controllers. The value of
> the logon script is "allusers.pl" in UMFD, and the script is located in
> %LOGONSERVER%\Netlogon. Bath files run without problems, but when I change
> the value to "allusers.pl", it will not run.
I'd wrap the .pl in a .bat
c:\> pl2bat %LOGONSERVER%\Netlogon\allusers.pl
> It will run however, if I
> enter %LOGONSERVER%\Netlogon\allusers.pl in a cmd window. Does anyone know
> if Perl must be installed on the Domain Controllers to get this to work when
> logging into the domain, or am I doing something else wrong?
If it is installed on the client computers it doesn't have to be on
the server. I did not install it on the clients, but only on the
server. On the clients I mapped a drive to the instalation.
Actualy you may edit the .bat you get to map the drive for you and
call perl off that path then.
And it's not you who does something wrong. It's windows. Though maybe
it's a feature. The thing is that to "execute" a file acording to its
mapping in the registry HKEY_CLASSES_ROOT and execute an .exe, .com,
.bat or .cmd are two different things. There are system calls that
will execute the later, but will not know what to do with the former.
The distinction is smaller in WinNT/2k than in Win9x, but it is still
there.
HTH, Jenda
== [EMAIL PROTECTED] == http://Jenda.Krynicky.cz ==
: What do people think?
What, do people think? :-)
-- Larry Wall in <[EMAIL PROTECTED]>
_______________________________________________
Perl-Win32-Admin mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-admin
