He clicked “Start” on the Default Web Site. Green triangle. “Running.”
“Helen. It’s Jamal. I need local admin rights on DEV-WS-042.”
There it was.
A sigh. “Ticket.”
Another sigh. Longer. “Hold.”
whoami /groups | findstr “S-1-5-32-544”
He picked up his phone. Called Helen in IT. you must be an administrator to use iis manager windows 10
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 rebooted. Logged back in. Opened PowerShell.
But here he was. The company’s legacy ASP.NET app had to be tested locally. And IIS Manager wouldn’t budge. He clicked “Start” on the Default Web Site
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.
He tried the obvious first: right-click, “Run as administrator.” UAC prompt. He clicked “Yes.” Same error. The machine laughed at him.
“Okay,” he muttered. “You want an administrator? I’ll give you an administrator.” It’s Jamal
Jamal smiled. He had become, for one fleeting moment, an administrator.
The error message glared on the screen:
Please view this site in portrait mode.