We are testing a Windows Server 2008 Standard Terminal Services mini-farm set up in VMWare to help manage a single application remote deployment. This application stores a LOT of settings in the per-user registry so we lose a lot of the benefits of terminal services (centralized app management, less user headaches, etc.) if we have the users log in as themselves. So, we have a single domain login (termsvc) that all the users login with. This feels bad for obvious reasons.
So, is there a way we can install (and more importantly: configure and continue to upgrade) this app ONCE and then "share" the registry with all the users so they can log in as themselves instead of all sharing a single login? Maybe have a single terminal services profile that these users share? What are our options here?
Thanks!
Best Answer
Perhaps I am over-simplifying, but ...
1- ID the registry changes -- see this question for suggestions on how to do so. Edit out the "machine" section of the changes.
2- Use GPO or login script to publish those changes as each user logs on.