Deny logon locally is what i meant by deny interactive logon.
Well, GPOs can be applied to an OU affecting all users and computers within
that OU and down the OU hierarchy. But you can also use security filteging
if it is impossible to place all required user and computer objects into one
OU. By default, "Authenticated Users" group (which means all authenticated
user and computer accounts) is granted "read" and "apply group policy"
permissions on the GPO. You can remove this entry from the ACL, and add only
the group you need, granting it "read" and "apply group policy". This way
only users and computers who a) located under the OU where the GPO is linked
and b) are member of the group you have granted permissions will be affected
by this GPO.