Let’s start off with the why? As an MSP (Managed Service Provider), security is at the forefront of every decision we make as a provider to our clients. This comes with complex passwords, policies and layers, meaning changing network settings would normally ask for permission. Especially in IT, our devices are locked down tight, so this little trick brought a little bit of sanity back.
I had a Dell server come back and needed to blow away the data and create a new virtual disk. When I plugged my laptop directly into the iDRAC port I wanted to use the GUI through a browser to delete and configure the new virtual disk. Changing the network adapter settings started to drain the life from my body as a pop-up continued to persist with every change I made.
Tip: Watch The Other Guys, it’s so damn good haha.
Brain: “Chad, go into Computer Management and add yourself through the Local Users and Groups, it’ll be easy.”
Unfortunately, when I went to add myself as a member of this group, the machine had no idea of the users within our Azure AD…even though the machine was AAD joined.
Thanks again Microsoft! I’ll take a rain check on the member’s list in a Dynamic Distribution List on EAC too.
As we all know and ❤️, PowerShell is invaluable when it comes to administering these days. Open up PS as an administrator and punch in this syntax;
|Net localgroup “Network Configuration Operators” /add “AzureAD\email@example.com”|
Once you’re done, go back into computer management and open Network Configuration Operators, you should see the user account added.
On my journey to finding answers, these articles assisted me greatly…