Re: [Condor-users] Win7 and kbdd daemon

["Ralph&Maria Finch" <ralphmariafinch@xxxxxxxxx>]

Would you mind sharing your script, or emailing it to me? We have had
keyboard detection problems for a couple of years and it looks like
7.6.1 is finally going to solve them. We also run mostly Win7x64 now
with a few XPx86 machines, and upgrading Condor is a hassle; right now
we do it by hand on 20 computers.

Ralph Finch
Calif. Dept. of Water Resources
Sacramento, CA USA
rfinch@xxxxxxxxxxxx

On Wed, Jul 13, 2011 at 10:25 PM,  <Greg.Hitchen@xxxxxxxx> wrote:
>
> For anyone interested in this topic, read on to hear our experiences.
>
> Firstly thanks to Tim, John, Mike (and Ian by way of Mike's reply)
>
> We now have 7.6.1 working on our Win7 (32 bit and 64 bit) PCs
> and correctly detecting user activity (keyboard/mouse).
>
> We found 2 issues to contend with when installing (we have an AD logon
> script that basically copies condor from a file server, along with the
> appropriate config file, a few reg entries, also creates and starts the
> condor service, etc.)
>
> Our script also creates a scheduled task to run itself daily as this
> script also checks for updated binaries and/or config files.
>
> We did NOT find that the KBDD would modify the registry (as suggested by
> John below) so we get our script to do that.
>
> We also found that condor_kbdd started at logon time would initially silently
> fail as the user did not have write permissions to the condor log directory.
> All the condor folders get created with full access for SYSTEM but only read
> access for User. This is different for XP where User also gets write permissions.
> New win7 security model I guess. Anyway we just shelled out a command in our
> script (kix) to do this:
>
> cacls c:\path_to_condor\log /t /e /g BUILTIN\Users:F
>
> and this did the trick.
>
> Thanks again for the help.
>
> Cheers
>
> Greg
>
>
>
> -----Original Message-----
>
> From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Timothy St. Clair
> Sent: Thursday, 7 July 2011 9:17 PM
> To: Condor-Users Mail List
> Subject: Re: [Condor-users] Win7 and kbdd daemon
>
> 7.6.1
>
> If you are not using the .msi, you will need to make certain that the
> kbdd is added to the registry for per login startup.
>
> HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run = [INSTALLDIR]\bin
> \condor_kbdd.exe
>
> Cheers,
> Tim
>
> -----Original Message-----
>
> From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of John (TJ) Knoeller
> Sent: Friday, 8 July 2011 5:15 AM
> To: Condor-Users Mail List
> Subject: Re: [Condor-users] Win7 and kbdd daemon
>
>
> Starting with 7.4.4 If you use the MSI installer and tell it that the machine you are installing on should
> pay attention to user activity, then the installer will modify the registry so that the KBDD is started
> whenever the user logs on.
>
> As a backup to that, if you put the KBDD into the DAEMON_LIST.   when the daemon KBDD starts up,
> it will realize that it can't do it's job (since it's running as system) so it will also modify the registry
> so that the KBDD is started when the user logs on.
>
> On Win7 and Vista, It's the KBDD running as the current user that listens in on user input and puts the machine into OWNER state, the one in the DAEMON_LIST is prohibited by desktop isolation from listening in on user input.
>
> So it's slightly wasteful to put KBDD in the DAEMON_LIST on Win7 and Vista, but it does get the job done (note that you have to log off and back on again after installing condor before the KBDD running as user actually starts up).
>
> -tj
>
> -----Original Message-----
>
> From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of John (TJ) Knoeller
> Sent: Friday, 8 July 2011 5:47 AM
> To: Condor-Users Mail List
> Subject: Re: [Condor-users] Win7 and kbdd daemon
>
>
> Todd just reminded me - There was a bug in all versions of Condor prior to 7.6 where if you restarted condor while a user was logged on, the KBDD would not restart and would not know how to talk to the restarted Condor daemons, so it would cease to work until you logged off and back on again.
>
> So the matrix is:
>
> For all versions of Condor before 7.4.4
>    Use the MSI installer and the KBDD will work until you restart Condor then it will fail until you logoff and back on.
>
> For Condor 7.4.4 until 7.6.0
>    Use the MSI installer _or_ add KBDD to the DAEMON_LIST and KBDD will work until you restart (see above).
>
> For Condor 7.6.0 and later
>    Use the MSI installer _or_ add KBDD to the DAEMON_LIST, there are no known bugs with the KBDD
>
> -tj
>
> -----Original Message-----
>
> From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Michael O'Donnell
> Sent: Friday, 8 July 2011 8:20 PM
> To: Condor-Users Mail List
> Subject: Re: [Condor-users] Win7 and kbdd daemon
>
>
> I believe there was a bug in 7.6.0 with KBDD for W7/Vista. Therefore, you may want to use 7.6.1 to be safe. Here was the posting by Ian.
>
> https://lists.cs.wisc.edu/archive/condor-users/2011-June/msg00027.shtml
>
> There is a bug in the 7.6.0 condor_kbdd daemon -- on resume the listen port of the condor_startd can change and often does. If the listen port of the condor_startd daemon changes, existing condor_kbdd instances silently starts to fail to send updates on keyboard and mouse activity to the startd. In this case you'll see your policies that normally rely on keyboard idle and mouse idle timers start to fail.
>
> It's fixed in 7.6.1.
>
> Regards,
> - Ian
>
> --
> Ian Chesal
> ichesal@xxxxxxxxxxxxxxxxxx
> http://www.cyclecomputing.com/
>
>
>
> On Thu, 2011-07-07 at 15:17 +0800, Greg.Hitchen@xxxxxxxx wrote:
>> Hi All
>>
>> Just wondering if someone has a summary of the status of the
>> condor_kbdd daemon
>> with regards to working correctly for Win7.
>>
>> What version/s of 7.4 and 7.6 correctly detect keyboard activity on
>> Win7, and what (if anything)
>> special needs to be done to config files (or the registry) to allow it
>> to work?
>>
>> I have searched the user-list archives and wiki but am finding it
>> difficult to
>> dig out this information.
>>
>> Thanks for  any info/help.
>>
>> Cheers
>>
>> Greg
>>
>> P.S. Our "installs" are not via MSI installs but via extracting and
>> copying
>> the zip file
>> _______________________________________________
>> Condor-users mailing list
>> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
>> subject: Unsubscribe
>> You can also unsubscribe by visiting
>> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>>
>> The archives can be found at:
>> https://lists.cs.wisc.edu/archive/condor-users/
>
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/
>