New Group Policy not working on 2008 RDS in 2012 Domain - Security Filtering problem?

-

we have windows 2008 r2 rds in windows 2012r2 domain. want lockdown 2008 rds domain users have added new  security group--named "data collection users". these users "domain users" , login 2008 rds using windows xp sp3 machines run specific application -they not use local desktops anything. added group local rdu group on rds.  not have other users login rds through terminal, including domain admins.

so far have done these steps:

  1. on dc, created new ou (called terminal servers) and moved rds it.
  2. opened group policy on dc, , under gp objects, created new policy called "ts users lockdown".
  3. linked policy ou.
  4. under security filtering removed authenticated users, added rds computer account (called qs2), added "data collection users" , chose allow "read" , "apply policy"
  5. under security filtering, domain admins, chose deny "apply group policy"
  6. we edited policy (under computer configuration>at>sys>gp) to enable loopback processing - replace mode.
  7. we first tested policy trying remove "run" startup menu , "prohibit access control panel".
  8. we ran group policy force update within gp management - ran successfully.
  9. we did not reboot rds.
  10. neither of settings tried in step 7 worked.  why not?

here images security filtering:

hi,

restart rdsh server, since enabled loopback mode on.

-tp



Windows Server  >  Remote Desktop Services (Terminal Services)



Comments

Post a Comment

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

-
looking options resolve error , prevent in future. thanks help. hardware: 2 node dell hv cluster running2012r2 dc 8 nic/ea in multiplex mode 4x hyper-v 4x hosts storage: 2x synology nas, accessed through iscsi hosts , cluster relevant logs: log name:      microsoft-windows-failoverclustering/diagnostic source:        microsoft-windows-failoverclustering date:          event id:      2050 task category: none level:         warning keywords:       user:          system computer:      l description: [dcm] filter wimmount found @ unsafe altitude 180700 log name:      system source:        microsoft-windows-failoverclustering date:         event id:      5125 task category: cluster shared volume level:         warning keywords:       user:          system computer: description: cluster shared volume 'volume1' ('cluster disk 1') has identified 1 or more active filter drivers on device stack interfere csv operatio
Read more

Failed to delete the test record dcdiag-test-record in zone test.com

-
ps c:\users\administrator.test> dcdiag /test:dns directory server diagnosis performing initial setup:    trying find home server...    home server = dc02    * identified ad forest.    done gathering initial info. doing initial required tests    testing server: default-first-site-name\dc02       starting test: connectivity          ......................... dc02 passed test connectivity doing primary tests    testing server: default-first-site-name\dc02       starting test: dns          dns tests running , not hung. please wait few minutes...          ......................... dc02 passed test dns    running partition tests on : forestdnszones    running partition tests on : domaindnszones    running partition tests on : schema    running partition tests on : configuration    running partition tests on : test    running enterprise tests on : test.com       starting test: dns          test results domain
Read more

Azure MFA with Azure AD and RDS

-
i have setup following lab in azure , need help. a server (domain controller) , remote desktop services. and server multi factor authentication server. i have setup following one http://www.rdsgurus.com/uncategorized/step-by-step-using-windows-server-2012-r2-rd-gateway-with-azure-multifactor-authentication/ and when im connecting got following error. the user "domain\username", on client computer "xxx.xxx.xxx.xxx", did not meet connection authorization policy requirements , therefore not authorized access rd gateway server. authentication method used was: "ntlm" , connection protocol used: "rpc-http". following error occurred: "23003". also on security log i've got following authentication details: connection request policy name: ts gateway authorization policy network policy name: - authentication provider: radius proxy authentication server: test.test.local authentication type: - eap t
Read more