[THIN] Re: carrying HKCU permissions via flex ops

Hmm, okay, how about regini?
http://support.microsoft.com/kb/q245031/

You can use that in the logon scripts to set permissions..

Andrew

On 24/08/05, Lilley, Brian <brian.lilley@xxxxxxxx> wrote:
> 
> yeah, it would but we have some 1000 applications which we wrap and which 
> may define restrictions to the users HKCU. Thinking aloud here.... these 
> restrictions are normally carried by the roaming profile and presumably are 
> sucessfully applied at user logon via winlogon (which is running as 
> system??)...
>  arrrgghhh..... even if I run proflwiz as system the reg keys will be laid 
> down but the user will have access to them??
>  
> -----Original Message-----
> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]*On 
> Behalf Of *Dogers
> *Sent:* 24 August 2005 14:39
> *To:* thin@xxxxxxxxxxxxx
> *Subject:* [THIN] Re: carrying HKCU permissions via flex ops
> 
> Would setting the permission in a GPO on HKUsers\.Default not work?
> 
> (Okay, I'll admit, it's a guess :) )
> 
> Andrew
> 
> On 24/08/05, Lilley, Brian <brian.lilley@xxxxxxxx> wrote: 
> > 
> > Hey Flexops guru's.. I've got a question for yah.....
> >  How does one transport the permissions of registry keys in HKCU via the 
> > flexops proflwiz tool? We have the scenario where certain keys are 
> > permissioned as read only for the user??
> >  thanks in advance, 
> >  Brianos
> > 
> > 
> > ==============================================================================
> > Please access the attached hyperlink for an important electronic 
> > communications disclaimer: 
> > 
> > http://www.csfb.com/legal_terms/disclaimer_external_email.shtml
> > 
> > 
> > ==============================================================================
> > 
> 
> 
> ==============================================================================
> Please access the attached hyperlink for an important electronic 
> communications disclaimer: 
> 
> http://www.csfb.com/legal_terms/disclaimer_external_email.shtml
> 
> 
> ==============================================================================
>

Other related posts: