On Tue, 10 Apr 2007 11:16:25 +0200 Torsten Geile <geile at oekonet-bremen.de> wrote: TG> Hi, TG> Jean-Jacques Moulis schrieb: TG> > TG> > Some good news! TG> > Wpkg.js works beautifully with Windows Vista. TG> > We are not using the Wpkg installer. TG> > We start Wpkg.js from a Startup script (à la AD but without AD). TG> > By the way, Vista joins one of ours samba domain without problems. TG> > (A nearly out of the box samba 3.0.24. We have some problems with our TG> > main domain, one with lot of specials fixes). TG> > TG> Could you be so kind and describe, what kind of script you use and how TG> you implemented it in your Domain? I suppose you use a samba domain. I TG> would like to use it in our environment, if you allow. TG> Regards, Torsten With pleasure! that's our startup script which runs as System. The Wpkg folder must be readable whithout authentication. (that's not a problem for us as we only install either free or license server controlled software) Tomasz installer is a better solution as it can authenticate as an unprivileged user. --------------Startup.cmd---------------- set MainServer=PDC @net time \\%MainServer% /set /yes >> %TEMP%\startup.log set WpkgRoot=\\%MainServer%\Wpkg set sw=\\%MainServer%\Sw @if not exist "C:\Etc\NoSync" %SystemRoot%\system32\cscript.exe %WpkgRoot%\wpkg.js /synchronize >> %TEMP%\startup.log echo "Wpkg completed at " >> %TEMP%\startup.log time /T >> %TEMP%\startup.log call %WpkgRoot%\Tools\Update.cmd >> %TEMP%\startup.log echo "Update completed at " >> %TEMP%\startup.log time /T >> %TEMP%\startup.log %WpkgRoot%\Tools\postie -host:mail.oursite.org -to:wpkg at oursite.org -from:%computername%@oursite.org -s:WinStartup -file:%TEMP%\startup.log -rm > NUL --------------Startup.cmd---------------- as you can see nothing fancy with the script. To run it on the clients: Define a startup script. this works from W2K to Vista Run gpedit.msc. gpedit.msc --> Local Computer Policy --> Computer Configuration --> Windows Settings --> Scripts --> Startup --> Add \\PDC\wpkg\startup.cmd add also a shutdown script ......... Scripts --> SHutdown --> Add \\PDC\wpkg\shuddown.cmd When you are at it add a Logon an Logoff script gpedit.msc --> Local Computer Policy --> User Configuration --> Windows Settings --> Scripts --> Logon --> Add %LOGONSERVER%\Netlogon\Logon.cmd ........... --> Scripts --> Logon --> Add %LOGONSERVER%\Netlogon\Logoff.cmd You are set for this client. We are using an imaging system for initial deployment so we don't need to repeat the procedure on every client. You could automate this step with an auto-it script or by adding necessary keys and files but I don't know what's the smallest set needed. I'll have a look at that. Regards, Jean-Jacques VDEV _______________________________________________ wpkg-users mailing list wpkg-users at lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users |