Five minutes passed. He could hear keyboard clacking. “Jamal, I’ve added your AD account to the local ‘IIS_IUSRS’ and ‘Performance Log Users’ groups. Reboot, then try whoami /groups . You should see S-1-5-32-544 — that’s the Administrators alias.”
Then he closed IIS Manager, opened VS Code, and swore never to speak of the dark arts again.
“Helen. It’s Jamal. I need local admin rights on DEV-WS-042.” you must be an administrator to use iis manager windows 10
He opened IIS Manager. No error. The tree of application pools, sites, and folders expanded like a mechanical flower.
He tried the obvious first: right-click, “Run as administrator.” UAC prompt. He clicked “Yes.” Same error. The machine laughed at him. Five minutes passed
Another sigh. Longer. “Hold.”
He picked up his phone. Called Helen in IT. Reboot, then try whoami /groups
But here he was. The company’s legacy ASP.NET app had to be tested locally. And IIS Manager wouldn’t budge.
Jamal leaned back in his chair, staring at the grey dialog box like it had personally insulted him. He was a developer, not a system admin. His job was to write clean React components, not wrestle with Windows permissions on a Friday at 4:47 PM.
He clicked “Start” on the Default Web Site. Green triangle. “Running.”
He opened lusrmgr.msc . His user, jamal_dev , was in the Users group. Not Administrators . That was the problem. His IT department, in its infinite wisdom, had stripped local admin rights from every developer after the SolarWinds scare.