password protect icons and disable windows key

I am looking at using desktopx for a couple of kiosk machines in a museum. I'd like to disable the windows keys so that windows+e does not work, etc.. and I'd also like to password protect some of the icons, such as "shutdown", to prevent everyday users from shutting the machine down and/or opening up windows explorer.

7,916 views 15 replies
Reply #1 Top
You would have to buy DesktopX 3 Enterprice. https://www.stardock.com/products/desktopxenterprise/
Reply #2 Top
Unless you have DeskopX 2 that is, it had a security tab in the options.
Reply #3 Top
I'm fine with getting desktopx enterprise... only $14.95 per license.. not a problem. The thing is.. I would really like to test the security features and understand how to setup the desktops with those features so I can present it to those who make the decisions regarding software purchases.

It is possible that we will deploy this in a higher capacity if it meets all our needs.
Reply #4 Top
If you have XP Pro, you can use this method to disable "WinKey+E" function Link

There is also a registry edit which will disable the WinKey function for Windows 2000 - which may or may not work on XP Link
Reply #5 Top
You can do what I did on my kids' computer; put a rubber washer under the Win key to prevent the pushing of it.

My dad did that for us kids back in '77 under the Reset key for the Apple ][.
Reply #6 Top
The thing is.. another application for this might be for a large event that my company hosts... in which we rent 200 pc's to handle registration. Currently we use 98 with a custom shell application. It's really sweet.. but OS limited.. We can setup any number of "buttons" that we want and it's just a reg entry to adjust it from being a public button and a password protected one. Since shell=explore.exe isn't in the win.ini on the 98 machines, none of the shortcuts work.. It's a pretty slick setup, but I know all the new shells like desktopX all run on top of windows..

I need to disable all access to the start menu and any shortcuts that might allow a user to open other applications on the machine. We just have icons for 3 applications they need to run plus log off and shutdown buttons.. and an explorer button that is password protected.
Reply #7 Top
According to the WinGuides site, the registry edit for disabling the WinKey will work on NT/2000/XP versions of Windows Link

I have not disabled this function on any machine, so I do not have first hand experience with it, but just in case you want to go with the Regedit method.
Reply #8 Top
Okay.. I'll give the regedit method a try for that, but I need to get the password protected icons before I'm able to demo the product.
Reply #9 Top
Just noticed the $499 price tag for the initial license for desktopX enterprise.. now I really need to test it out beforehand... $14.95, I was willing to drop that without a thought to test it, but now that it's a $500 investment, I really need to make sure it will do what we want.
Reply #10 Top
:bump: How about screenshots of the security tab/options? Or a straight answer regarding setting a password on an icon?
Reply #11 Top
What do I have to do to get an answer on this? Seriously? Simple yes or no and a screenshot would be great.

Yes you can password protect an icon..

Here is how..

or No, not a feature..
Reply #12 Top
I can't recommend DesktopX for kiosk machines since it lacks basic features like being able to lock a layout to prevent users from dragging icons etc. around and messing up the layout =\
Reply #13 Top
I can't recommend DesktopX for kiosk machines since it lacks basic features like being able to lock a layout to prevent users from dragging icons etc. around and messing up the layout =\


Are you refering to the IconX feature? (Which now is separated from DX) Because every object in DX can be locked.
Reply #14 Top
If the icons can be locked.. that's great.. but can they be locked down as well???
Reply #15 Top
"Are you refering to the IconX feature? (Which now is separated from DX) Because every object in DX can be locked."

thomassen: I was mixing up IconX with DesktopX, my bad

I was putting together a test for a kiosk machine project
in DesktopX and got so frustrated because the icons wouldn't
stay in place and they also had the bad habit of changing
appearance from time to time without any user input.

Since IconX was linked through DesktopX I took it as a feature
of DesktopX. I guess I could have made it to work by building
every single object on screen from scratch in DesktopX but
that wasn't an option back then because of tight deadline.

I used another solution that was easier(at least for me)
to get to grips with.

Sorry for the confusion.