I'm having an issue with a WMI script when trying to use the WMI MIIS_RunHistory. I can make a query after the FIM Service has been started, but after I have run the WMI Query a few times against the MIIS_RunHistory using a -filter "MaName='MANAME'" or "MaGuid='MaGUID'" it stops returning results. This is exactly like the issue detailed here http://www.identitytrench.com/2010/03/runhistory-parsing.html The only relable way to reference the RunHistory is to use -filter("RunProfile='ProfileName'"). or to not use any filter and return all the RunHistory and reference [1] as the first item in the array is always the latest RunHistory Is this a known issue?

Hi Peter, I am surprised to hear you are having this problem. We have written tools that use the WMI interface to retrieve run information and I have never seen the result you are reporting. -Jeremy

Hi Peter, I am surprised to hear you are having this problem. We have written tools that use the WMI interface to retrieve run information and I have never seen the result you are reporting. -Jeremy Are you running FIM FCS, or have you applied any patches. When I bounce the WMI Service (which also restarts the FIM service) it works again for a while... Until it stops again.

No, Experience so far has been on ILM 2007 FP1. I will be installing our tool on FIM 2010 Update 1 this week. What you describe sounds like a bug. If I see the same behaviour you are seeing then I will be contacting PSS. -Jeremy

No, Experience so far has been on ILM 2007 FP1. I will be installing our tool on FIM 2010 Update 1 this week. What you describe sounds like a bug. If I see the same behaviour you are seeing then I will be contacting PSS. -Jeremy I have just duplicated this in my test environment using FIM RTM MSDN, plus then applied Update 1 of the Sync Service and still had the problem. MaName doesn't work at all, I could use the "MaGuid='...'" 17 Times. The 18th time it didn't return anything. However when I dropped the -filter, or changed it to filter on RunProfile then it worked again. Sounds like a bug to me. Time to log a call... Done Case# 110053077124404