I guess when you say it is connected, you can see it on the agent overview screen?
Did you use the .net agent configuration utility to remove the agent?
If yes, I'm wondering if you disabled the wrong agent in case you had several on this machine. Did you restart IIS too as it might not have picked up the change until an IISRESET?
I'd like to disconnect the agent and NOT have to uninstall the software in case I need the server in the future. I have a set amount of licenses and would like to free up the license for use somewhere else.
ok, I can see that the web server agent service isn't there anymore but we knew this already because the IIS agent is no longer connected.
There is no mapping left on the .net agent configuration utility which is as expected.
I'm wondering if the w3wp process is still running even after you bounced IIS because removing the entry on the configuration tool will only take action after the process fully restarts.
If there is no w3wp process on this machine then there cannot be an agent.
In doubt I would reboot the server to be 100% sure as I have seen this many times before where IIS does not actually restart any process especially from the IIS console.
I forgot to confirm that you don't have to uninstall the agent software to disable the agents.
For IIS, remove the module and for .net make it inactive. Restart all the processes.
At least that's the expected behaviour when everything works fine.