Special Keys Disabled DSC

[shoemakesmusic]

well that's the bad news.  My support contract is up.  I purchased it probably right around a year ago.  I'm just now getting around to using this particular feature.  That's my fault, I know.  I guess it won't hurt to call and see what they say. I will definitely post back if I find anything out.

Thanks for the help.  I'm hoping someone out there knows. 

[Verne_D]

Hi shoemakesmusic,

You need to ensure that you're logged in as an admin on the local domain whose privledges you are trying to modify. If you are able to check the box, you should have the keyboard filter driver installed. For people who are not able to access the Disable special keys check box, you can modify the installation of the DSC module to add this driver. By default it is not installed. This setting is stored in the local domain, so one needs to be configured in order to apply it. Search the LabVIEW help for some instructions on this.

I hope this helps!

[shoemakesmusic]

Yes, I am the administrator and can add/remove users.  I added a user to that box and then checked that box.  The box appears to be checked but when I say ok and then go back to the security menu it is unchecked.  I logged in as the user that I added to that box and all of the windows keys that are supposed to be blocked still work.  And like you said, before I installed the Keyboard filter driver I was unable to check that box, but after I installed it I am able to check that box, but it does not appear to do anything and unchecks itself.

[Verne_D]

Hi shoemakesmusic,

There is a known issue in DSC 8.5 and 8.6 with this. The bug is #41894, and it was fixed for the 2009 DSC release. Even though the box is unchecked when you reopen the security menu, if you're logged in as the group whose privledges you have set and saved, the key catching should still occur. To turn off the feature, you have to check and uncheck the box in the same session. I apologize for the confusion.

[shoemakesmusic]

Ok, well I finally got the keyboard filter to work.  The only thing I did was reboot my system. I didn't change any settings.  Only problem I have now is it is not user specific.  If I add a user to the restricted list it effects all users.  I even tried adding a group (Operators) and it still effects Administrators.  As soon as I remove the user or group from the list I then regain control of windows keys for all users not just the one I added to the restricted list.  This somewhat defeats my purpose of wanting Operators to have no access and Administrators to have full access.

[Verne_D]

Can you walk me through how you're changing active users to test this? Changes wont occur in these settings until LabVIEW is restarted. If you can put together a walkthrough of exactly what to do, I'd like to try to reproduce the issue.

[shoemakesmusic]

No problem.  Let me preface that I finally got it working on one system.  The last problem I was having was that anytime I added a user to the keyboard filter option it would apply to all.  What I didn't realize was that you had to add users to the same list but without checking the keyboard filter box.  Once I did that everything works as intended.  Now the problem I'm having is I installed the keyboard filter driver on another machine, exactly the same way as before, using exactly the same version of LabView, and I can't for the life of me get it to work on this new machine.  I've rebooted LabView and the CPU multiple times and set it up the same way and it will not work.  Only difference is the new machine is a dual monitor system.  I wouldn't think that would have anything to do with it though.  So I'm somewhat back to square one except that on my initial machine it does work.  Very frustrating.  

But my procedure has been this:

Install Keyboard Filter Driver.  Reboot CPU.  Open LabView project.  Go to Tools--> Options --> Security -->Add user to the restricted list and check the keyboard filter box.  Add users to the restricted list and don't check the box (for users I want to have full access). And press "Ok".  That's it.  Then I log in as the restricted user to see if it works.  Then I log in as the unrestricted user to see if it is not restricted.  Like I said, on my first machine it works great.  Just as I want it to.  But now my second machine refuses to restrict any user.   I'm sure there is something I'm missing.  There's really not that much to it though.

Thanks so much for the help! 

[Verne_D]

It looks like you're doing it right. I don't have DSC for 8.5 installed, though, mine works on 2009 using the same steps. The only other thing I can think of is to make sure the accounts you're managing look right in the Domain Account Manager. I use an Admin and a Guest I might see if I can't dig up 8.5 and try some more.