5nowman Posted June 25, 2019 Posted June 25, 2019 (edited) Really odd one! Hopefully others have experienced this. Server 2019 Standard (with Gui). Logged in with administrator - went to NIC and saw the page with NIC adaptors Settings > Network and Adaptors > Change Adaptor Options. Gave the server a static IP, Created a new DC new forest (usual add role process etc). Restarted.. logged in with administrator (domain) Now when I go to Settings > Network and Adaptors > Change Adaptor Options. I get a message that I do not have permissions!!! NO permission to go to control.exe in system32 (which I can get to if I browse). I copied the Domain Administrator account to create a new one Account... and that account can do the above fine. Anyone else had this? Should I be worried and start a new DC again ? I've built MANY servers before.. this has never happened.... Any input would be cool! 5nowman Edited June 25, 2019 by 5nowman
Fazza Posted June 26, 2019 Posted June 26, 2019 Its by design in Server 2019 - we all know we shouldnt be using the Domain Administrator account (but a lot do) so I think this is Microsofts way of forcing the issue. Create a new user with Domain Admin rights (or give your own account Domain Admin rights) and then log on with that and you can change the NIC settings. There is a group policy setting (I seem to have read somewhere) that can 'correct' this issue but it fixes you being able to access the NIC etc. but breaks other things so best not to go down that route!
5nowman Posted June 26, 2019 Author Posted June 26, 2019 Its by design in Server 2019 - we all know we shouldnt be using the Domain Administrator account (but a lot do) so I think this is Microsofts way of forcing the issue. Create a new user with Domain Admin rights (or give your own account Domain Admin rights) and then log on with that and you can change the NIC settings. There is a group policy setting (I seem to have read somewhere) that can 'correct' this issue but it fixes you being able to access the NIC etc. but breaks other things so best not to go down that route! It isn't uncommon and it does happen to everybody ! A feature??? Omg.
tmoon-mint Posted June 26, 2019 Posted June 26, 2019 This also happens on Windows 10 with the built in administrator account. If you use another account or go directly via legacy control panel it should work fine.
5nowman Posted June 26, 2019 Author Posted June 26, 2019 This is why I have not seen it on windows 10. I NEVER enable the administrator account.... I think the SID used to be generic and the rule of thumb is use a different account.
Fazza Posted June 26, 2019 Posted June 26, 2019 It isn't uncommon and it does happen to everybody ! A feature??? Omg. Yep! We came across it the other week as we've only just gotten around to install it and when we found the GPO that 'fixes' the issue it allowed us to change the NIC IP address but it then denied us access to two of the storage drives so we couldnt access peoples home folders!!!
googlemad Posted June 27, 2019 Posted June 27, 2019 It does the same in 2016 I noticed so going forward we need to stop using the default domain admin account and use individual domain admin accounts I guess...
Fazza Posted June 28, 2019 Posted June 28, 2019 It does the same in 2016 I noticed so going forward we need to stop using the default domain admin account and use individual domain admin accounts I guess... We all know that's what we're supposed to do but it's not necessarily what we actually do!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now