On Thursday, 26.04.2007 at 09:54 +0200, Marco Gaiarin wrote: > Mandi! Tomasz Chmielewski In chel di` si favelave... > > > > "it is important to set the ALLUSERS variable, or at the first > > > wpkginst run the permisisons/ACL of the folder > > > %PROGRAMFILES%\WPKG will be totally blanked preventing the > > > wpkg service to run at next boot." > > The power of WIKI, this is mine! ;) > > > That warning is true only if you're installing as user SYSTEM. > > mmmmhhhhh... in my experience it is totally ininfluent who are the > user that install, but if you install WPKG as user X and run wpkginst > with user Y, without ALLUSERS, %ProgramFile%\WPKG permission are wiped > out. I think that's what happened to me :-( I installed WPKG originally as local Administrator. However, I set WPKG to *run* as 'SYSTEM' as suggested. When I tried updating the WPKG settings using 'wpkginst.exe' the permissions of %ProgramFile%\WPKG went away, meaning that WPKG would not subsequently launch. I think I need to reinstall WPKG on each client using ALLUSERS, (or 'Everyone' in the GUI installer). Dave. -- Dave Ewart davee at ceu.ox.ac.uk Computing Manager, Cancer Epidemiology Unit Cancer Research UK / Oxford University PGP: CC70 1883 BD92 E665 B840 118B 6E94 2CFD 694D E370 Get key from http://www.ceu.ox.ac.uk/~davee/davee-ceu-ox-ac-uk.asc N 51.7518, W 1.2016 wpkg-users mailing list wpkg-users at lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users |