We had done all of this through Group Policy. We created a seperate container in AD, then moved the Requisite Citrix Servers into their container and applied the server level lockdowns. Then created user accounts for the application to run under (so we could apply or deny everything appropriately at the file level - not members of domain users, etc.) per kiosk and added those users to their container and applied the user level lockdowns. Make sure when doing it through GP that you restrict what they can execute (ie. iexplore, acrord32.exe, ppview.exe, etc.) or you might as well not have applied any lockdowns. Then as we refreshed the servers, we just put them in their correct group, tested lockdowns, and deployed. No special software required. It is really eye opening to have an IT auditor (paid hacker) sit down with you at your kiosk to see what all he does to try to break into things he shouldn't....as an admin, it is very humbling the first time, but a great learning experience. On 2/7/07, Matt Kosht <matt.kosht@xxxxxxxxx> wrote:
SBC SITES ONLY GOOGLE SEARCH: http://www.F1U.com ************************************************ For Archives, RSS, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link:I am trying to publish a website as a Citrix PS 4.0 published app and have it locked from changing any IE settings (like going to another website). I tried kiosk mode but the full screen isn't going to work for clients who need to do things besides having the website on the screen. Ideas? -Matt
//www.freelists.org/list/thin ************************************************