0

How are people doing this where they work/play? I am sick of dealing with registry hacks in the NTUSER.DAT file for the default user and erasing profiles for a guest account that is used for a lot of public kiosks. I push out those changes through AD. These computers are domain-joined, but a lot of politics has prevent the proper solution of a domain account for the kiosk guest user. Does anyone handle this in a particularly clever way?

2 Answers 2

1

If the kiosks are Windows xP and if you can find it I suggest using Steady State, you wont be able to find it on the Microsoft site as it has been discontinued.

The Windows Team blog has a write up on how to replicate most of the funtionality under Windows 7.

http://windowsteamblog.com/windows/b/springboard/archive/2010/09/27/steady-state-for-windows-7.aspx

1
  • This is why different departments abandoned Pharonics DeepFreeze. Post-deployments became impossible, and reliable methods became unstable. Essentially you have to create arbitrary maintenance windows for simple updates. Easy for servers, not easy for 24 hour students labs. Haha.
    – songei2f
    Mar 8, 2011 at 19:46
-1

Only domain users (and domain computers) can be managed through a Group Policy. I would like to suggest too migrate those local users to domain users.

2
  • "These computers are domain-joined, but a lot of politics has prevent the proper solution of a domain account for the kiosk guest user." Next time, RTFOP.
    – songei2f
    Mar 7, 2011 at 14:21
  • An workaround would be to script it with delprof.exe and use that script in a Group Policy startup script. You can target that Group Policy to the domain computer.
    – Turdie
    Mar 7, 2011 at 15:41

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .