fInheritAutoLogon

(imported topic written by USMC175)

I’m evaluating the ‘fInheritAutoLogon’ value within the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp

The fInheritAutoLogon value on my test Win2008 R2 box is ‘0’.

Using this relevance produces the expected FALSE result:

q: (value “fInheritAutoLogon” of key “HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp” of registry) = 1

a: FALSE

Using this relevance however produces an unexpected TRUE result:

q: exists key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp” whose (exists value “fInheritAutoLogon” whose (it != 1) of it) of registry

a: TRUE

I also tested both statements on an XP box (with fInheritAutoLogon = 0) with the same results. The second relevance statement returns the unexpected TRUE result.

Why would the second statement return the incorrect TRUE?

(client version 7.2.5.22)

(imported comment written by NoahSalzman)

“TRUE” looks right to me if you set the value to “not 1”. Are you sure you want “not equals” in the second script?

Perhaps you want “not exists a key whose value is 0”?

(imported comment written by USMC175)

Thanks Noah.