On 08/08/07, Jerry Haltom <[EMAIL PROTECTED]> wrote: > I don't get it. I've been able to run AutoIt scripts from a service account, > which has it's own Windows Station. Thus it is able to create Windows, and > access them. This works just fine right now.
See the bottom of http://wpkg.linuxkidd.com/live.php > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Will Sheldon > Sent: Tuesday, August 07, 2007 7:36 PM > To: wpkg-users > Subject: Re: [wpkg-users] More elegant solution to onscreen login to > runAutoit install scripts > > On 08/08/07, Will Sheldon <[EMAIL PROTECTED]> wrote: > > Hi everyone, > > > > I have been using unattended for a while, and just found wpkg. I think > > it's going to make my life much easier! > > > > After reading http://wpkg.linuxkidd.com/ (the gui mailing list > > subscription is down?) and seeing his (or in about 2% of cases her - i > > couldn't find his/her name anywhere) info on installing using autoit > > scripts and a limited install account (that ties up the machine during > > install) I realised that a more elegant solution is possible: > > > > Configue XP to support multiple terminal services sessions (the > > current XP kernel is multiuser) According to Riccardo Raneri > > (http://riccardo.raneri.it/blog/eng/index.php/2006/04/24/windows-xp-mu > > ltiuser-remote-desktop/) the current kernel only allows 3 concurrent > > sessions, but we would only need a maximum of two. > > > > To do this you have to downgrade termsrv.dll to version 5.1.2600.2055 > > (xpsp_sp2_beta1.031215-1745) - download available from > > http://www.orbitfiles.com/download/id20947665). > > > > Windows sfp would have to be overcome, but that can be achieved by > > putting the dll in the $OEM$\$1\System32\Dllcache\ folder on your > > install share. > > > > then a custom adm/reg file for domains/workgroups respectively to > > tweak HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal > > Server\Licensing Core\EnableConcurrentSessions (DWORD) to a value of 1 > > and you're nearly laughing. > > > > It would then be possible to script an RDP session to be called from a > > server when the machine starts, so the machine boots, calls a script > > from the server with it's own machinename as a parameter which in turn > > calls an RDP session to the machine with the install account, which > > does what it currently already does, (with the exception of > > suppressing any reboot requests!) then logs out. > > > > This would allow a full interactive autoit lead install to be run in > > the 'background' (relative to the console user) > > > > What do you think? > > > > > > Will. > > > > Actually, it seems that that patch only works if you are not a member of a > domain, and have fast user switching enabled. > > However, there are reports that TerminalserverNoRestrPatch-1-1.zip > will do it for domain users. The version i found contained a trojan, so i've > given up on that route. > > I guess that the version from 2003 may do the trick, but i haven't tried it > yet as it's probably against the terms of the eula ;-( Damn those M$ > lawyers. > > W > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > wpkg-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wpkg-users > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ wpkg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wpkg-users
