ThinKiosk 2.0 Beta Available:

It’s ready!

I’ve uploaded a copy of ThinKiosk 2.0 for you to start testing, Its available on the downloads page. A full list of new features can be found in my previous preview blog.

When you start testing, again use a new OU and Group Policy Object, I’ve changed it again (last time, Promise!)

A few quick Points:

  • Find a bug?
  • Want a new feature?
  • Want some help?

Drop me an email  on Andrew(at)andrewmorgan.ie or leave a comment below and we’ll have a quick chat.

Want to help translate ThinKiosk?

Drop me an email on  Andrew(at)andrewmorgan.ie to let me know you’re awesome and want to help, then download a copy of the language file from the downloads page. All translators will be forever immortalised on the Credits page.

Don’t worry if you’re language isn’t already in the worksheet, add an additional column and fire away.

Note: Please don’t reorder the tabs or sorting.

Want to help further development of ThinKiosk?

If you have access to any of the following environments, I’d be very interested in talking to you about doing some testing.

  • Web access portal to Windows Remote Desktop services.
  • a MEDV environment.
  • a web portal to a VMware View environment.

If you have another web based access to an SBC or VDI environment I’m also happy to test also.

And, of course, any such testing will also result in aforementioned immortality.

Want to give back?

I have a donate button over there —->

:)

4 thoughts on “ThinKiosk 2.0 Beta Available:

  1. Pete Mitchell

    Would it be possible to have an option to automatically log the user off the thin client PC when they disconnect / log out of their Xendesktop VM? I know that the Citrix Desktop Lock will do this, but your app is much better in other respects.

    Reply
    1. Andrew Morgan

      Hi Pete, I normally recommend that you configure the thin device to login as a generic account, then have the user authenticate on the web interface.

      The web interface can be configured to time out as quickly as a minute after launch and the kiosk is ready to be logged in again (via the web interface) by the next user.

      Is there a reason you are avoiding a generic account? I hope you don’t mind me asking but it helps me better understand the use case.

      Thanks,

      A

      Reply
      1. Pete Mitchell

        Security reasons. I’m not able to use a generic login for thin client machines.

        Thanks,
        Pete

        Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>