I found myself in this exact situation yet again today and finally decided to sit down and solve it once and for all.
Unfortunately you google this and discover that it’s not possible due to the amount of data that process monitor generates and can’t pass it all over the wire.
You need ultimately to run Process Monitor remotely. However perhaps that computer is always in use and you simply can’t log in locally to launch resource monitor or process monitor. You need to figure out what exactly what processes and files are causing that disk IO. You are reviewing log files and discover that a remote computer (perhaps a virtual machine running on shared storage) is running wild and hammering on the disk. Have you ever been in the following situation? I have finally solved something that has been a pain in my side for years now.
0 kommentar(er)
