Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NT policies - how i remove them completely?

Status
Not open for further replies.

dasein47

MIS
Mar 21, 2002
15
US
Hello,

I have a terminal server NT 4 running Citrix and i want to put it into production.

Users connect via WYSE terminals and use a terminal server desktop to do their work (email, surf internet, run apps, etc) I wanted to prevent any domain user from installing software on their desktops/profiles. I have found a way to do this, but have screwed up the policies somehow and can't seem to get it back to the original state - allowing everyone to install software.

Simply, does anyone know how to remove all traces of any policy on an NT Terminal Server 4 system?

Kip
 
You can't remove the policy. You can only create a new policy that reverses the effects of the first one. You need to find the policy options that you 'checked,' for example, and clear them (not grey them) and find the ones you cleared, and check them. Grey means 'leave as-is'. Deleting the policy also means 'leave as-is'. You have to proactively reverse the effects of the pernicious policy.

Happily, group policies in Win2k don't work this way, and don't permanently 'tattoo' the registries of the clients.

ShackDaddy
 
I don't know if this is an option for you but whenever this happens to me I just delete the .pol file and then delete the user profile. Once the user logs on again their profile is recreated without policies (assuming you didn't miss any machine or user policies). I have a very similar setup as you and have done this many times when testing policies. Hope this helps
 
Thanks shackdaddy and bp1169! those are both great suggestions and after trying them, i'm farily certain my registry on the server is corrupted. luckily i have a server farm and can ghost an existing one to this one, newSIDD, change name, rejoin domain, etc. this will work, eliminate this policy issue and remove any possibility of registry corruption.

i do know now how to correctly set policies.

thanks again!

kip
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top