I'm noticing on a few machines that they will struggle when doing the "disks" scan and I believe because of that long duration on that scan they will end up posting a WMI operation timed out. I've already increased the timeout to 240 seconds and there were still a few machines posting this timeout. When I removed the "disks" scan function from the profile then they scanned successfully.
Is the WMI timeout the entire duration of the scan function? meaning if the whole process takes longer than 4 min it will just time out? If so I would probably just raise this to 480 to see if these machines complete a full scan in that time. That could point to them just being older and slower, which I wouldn't disagree with. But there is one that is a relatively quick machine with an SSD and still times out.
Please sign in to leave a comment.