Howard is of course right.
I am executing the script as a domain administrator, against machines
in the domain, so access shouldn't be an issue, and there aren't any
group policies in place either...
I dug into using lanman, as Solli suggested, but I get numeric error
code 1371, which translates into "you can't do this on a built in account."
Win32::Lanman::NetUserSetInfo("\\\\ramoth", "administrator",
{'password' => 'testpassword'});
Next I'm thinking about using psexec and good ol- fashioned net user
commands, but I'd really like to avoid that if I can.
Any other thoughts?
Thanks so much everyone...
-Rick
At 10:32 AM 2/3/2006, Bullock, Howard A. wrote:
Erich Beyrent Wrote:
In order to run this code successfully, does perl have to have special
privs on the target computer? How does one set those permissions?
-------
[Bullock, Howard A.]
Perl does not need any specific permissions. The user context of the
process itself needs adequate permission on the remote computer the same
as you would if you used the GUI tool. In this case the process would
need to be execute under an account that has administrator permission on
the remote computer.
_______________________________________________
Perl-Win32-Admin mailing list
Perl-Win32-Admin@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
--
Rick Coloccia
Network Manager
SUNY Geneseo Computing & Information Technology
119 South Hall, 1 College Circle, Geneseo, NY 14454
Voice: 585-245-5577 Fax: 585-245-5579
_______________________________________________
Perl-Win32-Admin mailing list
Perl-Win32-Admin@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
