Skip to content

{ Category Archives } Logs

Using powershell to parse a csexport file

From time to time it’s necessary to access detailed data about objects in the connector space of a FIM Sync MA. One way to do this is with the csexport command line tool (found in the Bin folder) but the XML it produces isn’t particularly pretty and it doesn’t open nicely in Excel.
Luckily powershell has [...]

A Basic Requests Reporting Method

There were a few FIM reporting sessions at TEC, none of which I managed to make it to, though I hope the presenters will be making their solutions generally available as they are undoubtably more correct and complete than what I’ve been doing. However a couple of people did ask that I post my method [...]

Updating RequestStatusDetail

Not long ago I wrote a post about writing status messages back to the Request object from a custom workflow. I used custom attributes because I was following the only documentation I could find. But Henrik said “why don’t you use RequestStatusDetail?” – and actually the reasons were a. I hadn’t thought of it, and [...]

Archiving the Import and Export Logs, and viewing them with a stylesheet

A long time ago I wrote up a method that could be used to archive the MIIS import and export logs, while also making them more readable with a stylesheet. I’ve now implemented this on a FIM 2010 server, and it works, so I’m going to write it up again.

Troubleshooting missing group member errors

In some implementations, it makes sense (usually by improving performance) to separate your user and group provisioning into seperate MAs. One downside of this approach, however, is that you can run into export errors when trying to update a group with a member who doesn’t exist in the external directory – and this includes delete [...]

Hacking the import/export logs

Here’s a trick that is worth knowing – though I’m only recommending it for TEST ENVIRONMENTS – consider yourself warned.
You may have noticed the ”test only” log file options on the import and export run profiles. Being able to stop the run at the log file is incredibly useful for testing what would have been exported, without actually [...]

Monitoring MIIS

Good monitoring and alerting is an essential, but often under-loved, part of any computing infrastructure. The complexities and multiple dependencies of even a straight-forward MIIS installation make systematic monitoring absolutely essential.
Server Health
Obviously you will be monitoring that the server itself is actually up. I believe something a little more than a ping is required to confirm [...]

A Stylesheet for the Import and Export Logs

Follwing on from yesterday’s post, where I wrote about hanging on to your import and export logs, I now present a way to view them using an xml stylesheet.
The first problem with this approach is that the xml files produced by MIIS don’t work with a stylesheet. The stylesheet name must be included in [...]

Getting the Value from your Import and Export Logs

As I’ve mentioned before, I don’t think there’s a lot of value in keeping days of Run History. Far more useful are the Import and Export logs that you should be dumping from your Run Profiles. Using these files you can track exactly what went in and out, and more importantly, when it happened. This [...]

Keep That Run History Under Control!

I expect that learning to keep the Run History under control is something that most MIIS designers have learnt through unpleasant experience. But in case you haven’t, a brief overview.
The Run History is stored in the MicrosoftIdentityIntegrationServer database, and contributes massively to the growth the database. If you don’t regularly delete the Run History, your [...]