No mention of the port number used by the profiler agent. Also skipping the monitor server. I also restarted the IIS server after this. Then when I run the commandYourKitTools64.exe status , I getThe monitoring server is running.

Profiling of all processes that will start: enabledProfiler startup options:

From my local desktop, I tried to connect to the remote application by giving, {username@remote_ip} / {username@remote_ip:port} / {remote_ip} and nothing works. I am not sure whether the profiler agent has attached to the iis correctly.

Profiling of all processes that will start: enabledProfiler startup options:

I also checked the log folder and it had created a w3wp.exe-{pid}. Below are its contents16.02-41 0.002: Command line: c:\windows\system32\inetsrv\w3wp.exe -ap DefaultAppPool -v v4.0 -l webengine4.dll -a \\.\pipe\iisipm71c3dff6-7dd1-4548-bc68-a1d4486f39c4 -h C:\inetpub\temp\apppools\DefaultAppPool\DefaultAppPool.config -w