This message was deleted.

...maybe better to redirect to hkcu instead? https://blog.fslogix.com/fslogix-advanced-rule-examples

hmm no - not what I´m looking for. Value is already inside HKCU want to handle it by FSLOGIX only / no GPOs, WEM etc.

I have tried something similar last week, I don't think this is doable. I ended pushing a reg key via GPP and targeting the same AD group.

I agree with @Jonathan Pitre. As far as I know you cannot set new registry values only "manipulate" existing values

@Kasper Johansen Of course, but in my tests it was only possible to manipulate STRING values, no DWORD values.

Hmm...that should be possible...let me check

Lets have a look at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\DisableRepair. When I set the following rule the Vallue disappears completely:

Hmm...I am seeing the same thing with another registry value

for me it seems that he would like to push "0" instead of dword0x000000 A registry rule was encountered with a type mismatch for path \REGISTRY\MACHINE\SOFTWARE\Microsoft\Active Setup\DisableRepair.

I can't remember if that is supposed to happen, I have mostly done hiding rules and they are of course hidden

Corrrect, thats what i´m also seeing. Eventlog reports the type mismatch.

Specifying the hex value doesn't work either

Have I won 50.000$ now? 😄

Haha...FSLogix is now MS, no chance of you getting 50K for that 😄

also the reg_sz works perfect..

I'll look for an earlier version of the Fslogix Agent and do some testing

The “Specify Value Rule” in the Rules Editor has only ever supported a REG_SZ, the recommended approach as previously mentioned is using a redirection rule. Having said that I swear there was a way of doing it by manipulating the rules file directly, there used to be an article in the old knowledge base, but that gone now!!