<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Creeva's World 2.0 - Latest Comments in The Kiosk Series - Part Three - Microsoft SteadyState vs Group Policies | Creeva's World 2.0</title><link>http://creevasworld20.disqus.com/</link><description></description><language>en</language><lastBuildDate>Thu, 15 Jan 2009 16:18:56 -0000</lastBuildDate><item><title>Re: The Kiosk Series - Part Three - Microsoft SteadyState vs Group Policies | Creeva's World 2.0</title><link>http://creeva.com/2008/04/09/the-kiosk-series-part-three-microsoft-steadystate-vs-group-policies/#comment-5150920</link><description>As an aside Steady state offers a group policy template. Install SteadyState on the machine you use for group policies and you can import the template into group policy. It has many of the same options and doesn't require as much fiddling with obscure settings. (Registry Keys and such)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrew</dc:creator><pubDate>Thu, 15 Jan 2009 16:18:56 -0000</pubDate></item><item><title>Re: The Kiosk Series - Part Three - Microsoft SteadyState vs Group Policies | Creeva's World 2.0</title><link>http://creeva.com/2008/04/09/the-kiosk-series-part-three-microsoft-steadystate-vs-group-policies/#comment-3859760</link><description>To be honest - I haven't really attempted to actually remove steady state - on the machines I employ these on I would just do a system wipe.   If I get a chance I'll attempt to go through and try it and see how it goes and what I find.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">creeva</dc:creator><pubDate>Mon, 17 Nov 2008 09:02:15 -0000</pubDate></item><item><title>Re: The Kiosk Series - Part Three - Microsoft SteadyState vs Group Policies | Creeva's World 2.0</title><link>http://creeva.com/2008/04/09/the-kiosk-series-part-three-microsoft-steadystate-vs-group-policies/#comment-3854569</link><description>I want to remove all traces of SteadyState regarding logon especially. Also my SystemRestore no longer functions. I removed every file with regedit. But it's still present. OS is XP Pro.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul</dc:creator><pubDate>Mon, 17 Nov 2008 03:21:17 -0000</pubDate></item><item><title>Re: The Kiosk Series - Part Three - Microsoft SteadyState vs Group Policies | Creeva's World 2.0</title><link>http://creeva.com/2008/04/09/the-kiosk-series-part-three-microsoft-steadystate-vs-group-policies/#comment-1718189</link><description>I haven't looked at Netkey's solution.   I will be looking them up now and seeing what they have to offer, thanks for the tip.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Creeva</dc:creator><pubDate>Mon, 19 May 2008 09:32:29 -0000</pubDate></item><item><title>Re: The Kiosk Series - Part Three - Microsoft SteadyState vs Group Policies | Creeva's World 2.0</title><link>http://creeva.com/2008/04/09/the-kiosk-series-part-three-microsoft-steadystate-vs-group-policies/#comment-1718188</link><description>Have you or your team looked at the platforms offered by companies like Netkey? They offer content distribution and quite a comprehensive suite of security and deployment tools. We've been looking very hard at them for some time during our project but haven't made up our minds yet as to whether to implement their software or not with our kiosks.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ben Cecka</dc:creator><pubDate>Sun, 18 May 2008 02:18:52 -0000</pubDate></item><item><title>Re: The Kiosk Series - Part Three - Microsoft SteadyState vs Group Policies | Creeva's World 2.0</title><link>http://creeva.com/2008/04/09/the-kiosk-series-part-three-microsoft-steadystate-vs-group-policies/#comment-1718187</link><description>I still have to do 3 more parts on this series - might get another part done this weekend.   That being said, at work we talked to MS on a conference call and we are partially implementing one of their solutions which is a mixture of GPO stuff, and steadystate (at least on the drawing board for right now). &lt;br&gt;&lt;br&gt;To automatically login in a user there is a registry entry that you can put in the user name and passwords and that will cache it for you and auto login.   The problem with using steadystate with user accounts and auto login is that user accounts must be local and not domain accounts, and the session timer makes absolutely no sense with auto login.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Creeva</dc:creator><pubDate>Thu, 01 May 2008 18:54:55 -0000</pubDate></item><item><title>Re: The Kiosk Series - Part Three - Microsoft SteadyState vs Group Policies | Creeva's World 2.0</title><link>http://creeva.com/2008/04/09/the-kiosk-series-part-three-microsoft-steadystate-vs-group-policies/#comment-1718186</link><description>Thanks so much for the work you've put into this series. I'm currently working on a similar project with a retail customer facing kiosk. This contrast between SteadyState (which I just ran across this afternoon) and GPO was just what I was looking for.&lt;br&gt;&lt;br&gt;This is probably a very simple question, but what methods are you looking at (or are you) to log in a restricted domain user account on startup?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ben Cecka</dc:creator><pubDate>Thu, 01 May 2008 18:39:00 -0000</pubDate></item></channel></rss>