ppm install http://www.bribes.org/perl/ppm/Win32-Lanman.ppd
[download]

C:\_32\comp>ppm install http://www.bribes.org/perl/ppm/Win32-Lanman.pp
+d
Installing package 'http://www.bribes.org/perl/ppm/Win32-Lanman.ppd'..
+.
Bytes transferred: 226633
Installing C:\strawberry-perl\perl\site\lib\auto\win32\lanman\lanman.d
+ll
Installing C:\strawberry-perl\perl\site\lib\auto\win32\lanman\lanman.e
+xp
Installing C:\strawberry-perl\perl\site\lib\auto\win32\lanman\lanman.l
+ib
Installing C:\strawberry-perl\perl\html\site\lib\win32\lanman.html
Files found in blib\arch: installing files in blib\lib into architectu
+re dependent library tree
Installing C:\strawberry-perl\perl\site\lib\win32\lanman.pm
Writing C:\strawberry-perl\perl\site\lib\auto\Win32\Lanman\.packlist
[download]

I'll keep trying this method, but so far I'm having trouble for one of the dependencies on ppm. XML-Parser is barfing on Expat.xs and friends. Thanks anyway.

Yes - ppm relies on XML::Parser, which in turn needs the expat library. See http://win32.perl.org/wiki/index.php?title=Expat_Hacking for how to build XML::Parser on Strawberry/Vanilla Perl.

I think that ppm has some other dependencies, too - but, unlike XML::Parser, they are all straightforward to build and install.

Yet another (cheat's) method of installing XML::Parser is to download the ppm tarball from Randy Kobes ppm repository (http://theoryx5.uwinnipeg.ca/ppms/x86/XML-Parser.tar.gz), and extract the contents to the appropriate location within your perl installation. ie copy:

1) the entire contents of the blib/arch/auto folder to 
   C:/strawberry-perl/perl/site/lib/auto

2) the entire contents of the blib/html folder to 
   C:/strawberry-perl/perl/html

3) the entire contents of the blib/lib folder to
   C:/strawberry-perl/perl/site/lib
[download]

I'm fairly sure that particular build of XML::Parser (version 2.34) was built against a static Expat library - so you wouldn't even have to bother building the Expat library if you grab that particular distro !!

Cheers,
Rob

So according to this MS post by executing ntrights + relevant parameters through perl you should be able to unblock the situation.

Alternatively you can run a diff of a registry dump before and after applying the security change on a test machine. Then reapplying through Perl Registry handling this setting on the target machine.

Alternatively you can also ask the network administrator to create an OU (W2K* active directory Organizational Unit) containing all your target machines and to define a group policy applying this security policy. Which may be in the long run the best idea since Domain Group Policies override Local Security Policies thus suddenly breaking your local settings and scripts.

Ntrights.exe

I was kind-of-sort-of hoping to do everything from within Perl, so I could us PAR to pack it all up into an executable, and distribute to machines without Perl installed, without too many external dependencies.

Thanks.