Loopback: http://deployhappiness.com/loopback-policy-how-a-computer-gets-a-transgender-operation
Policy or Preference: http://deployhappiness.com/policy-or-preference
You must create Active Directory Organizational Units (OUs) to apply group policies against. You can't apply policies to the built-in AD containers.
Policies apply to either users or computers. Loopback processing can make user policies apply to certain computers.
Group policies often seem not to 'take effect' when you think they should.
Time plays an underestimated role in the activation or roll-out of group policies. Test it again in the morning!
gpupdate /force
on domain controllergpupdate /force
on workstation computerUse Group Policy Management to manage group policies.
Use Group Policy Editor to edit a specific Group Policy Object (GPO).
View resultant policies:
Use the CLI:
https://mashtips.com/how-to-use-the-group-policy-results-gpresult-exe-command-line-tool/
gpupdate /force gpresult /R gpresult -H GPResult.html
Check computer group membership:
Get-ADComputer "tucson-svr" -Properties MemberOf gpresult /scope computer /v net localgroup
Group Policies 'flow down', so you may need to Block Inheritance to a container using Group Policy Management.
http://technet.microsoft.com/en-us/library/gg563788.aspx
Edit an existing group policy, or add a new one, and add 'Administrators':
Computer Configuration → Policies → Windows Settings → Security Settings → Local Policies → User Rights Assignment → Log on as Batch Job
By default, background images are not displayed nor can users change the background unless the RDP client is set to 'Lan' or the best connection speed in the client settings.
If you set a solid color background at a fast speed, the setting will 'stick' even when going back to slower connection speeds
You have to have Desktop backgrounds enabled in the client before any of the following server-side stuff will work.