Lars Schimmer wrote:
Ok, grabbing a procmon log, which filters should I apply before I make it public? Without its really BIIIG. In this special case, cache is now 400 MB and user profile juts 140 MB around, it should fit.
How about just reading the output and finding where there are errors? I should not have to be the one to do this for you.procmon is really powerful. You can filter on the contents of any field. Path name, process, result, duration, etc. You can highlight
entries based upon any criteria to make them standout. Filter sets can be named and saved to permit easy switching between views. You are looking for errors so start by filtering out successful results and those entries are are going to fail because they are not supported such as FASTIO requests sent to AFS.
It worked for the user til a "special, unknown" event happens, the event was not install software, remove software, firewall setup,..
procmon will help you here as well. For each request that is logged you can view the "duration" of the request. See where the delays are. See which processes are involved in the request that is taking so long. If there is a 30 second delay it should be quite easy to locate with a highlight for entries whose duration is greater than 1 second. Jeffrey Altman Secure Endpoints Inc.
smime.p7s
Description: S/MIME Cryptographic Signature
