![]() |
|
SPONSORED LINKS BY GOOGLE |
|
2
8th October 14:18
External User
Posts: 1
|
Howdie!
scale schrieb: Two steps here: Group those machines that shall only allow logins from a certain group into a OU and apply the following policy: CompConf\Windows Settings\Security Settings\Local Policies\User Rights Assignment - "Allow Log on locally". This lists the users and group allowed to log on locally at the machines. Add your group in there and wipe all other users out (but leave your Admins group in there in order to not lock yourself out). Second: get your accounting users and modify their "Log on to" attribute through Active Directory Users and Computers Properties. cheers, Florian -- Microsoft MVP - Windows Server - Group Policy. eMail: prename [at] frickelsoft [dot] net. blog: http://www.frickelsoft.net/blog. |
|
|
4
11th October 22:19
External User
Posts: 1
|
A GPO created in the domain always overwrites local GPO.
-- Regards G Johansson fantomen@NOSPAM.GPfaq.se http://GPfaq.se |
|
|
5
11th October 22:19
External User
Posts: 1
|
Howdie!
scale schrieb: It (the AD-policy) will definately overwrite the local policy. It the principle that you, as the Active Directory Group Policy Administrator should have more "power" than local administrators and therefore "replace" settings made locally. cheers, Florian -- Microsoft MVP - Windows Server - Group Policy. eMail: prename [at] frickelsoft [dot] net. blog: http://www.frickelsoft.net/blog. |
|
|
SPONSORED LINKS BY GOOGLE |
|
|