I am completing the FIM specs for an install and all FIM software requirements need .NET 3.5 (or 3.5.1) (well the install guide says .NET 3.0 for servers other than the Sync server)

Question - I see that EB V3.0 requires .NET 4.0 which means collocated on a FIM Server will require .NET 4.0

Please confirm

TIA

I can see the best practice of running regular FS on say a weekly basis

I assume that I apply FI/FS ONLY for FIM, then other MA's in my preferred order

Becasue I already have a 00:00:30 scheduled check operations for all the MA's then they will take care of any resulting exports/imports/sync's

?

Bob - I am excluding FIM MA exports in the EB exclusions as discussed so that writes to the FIM Service DB do not cause WS errors as observed. Should I also exclude FIM Sync Import/Sync from other sources as they would write to the FIM Sync DB ..

Event Broker extensibility files deployed from the DEV lab have been updated with TEST environment references, but only the changes to the OperationEnginePluginKey extensibility file is persisting. I initially thought this was just error on my part, or a crashed service or something, but I had noticed that after the last reboot I had to re-enter the agent details. I have done this 3 times now I think, and it is only by chance that I can see right now that the timestamp on this filedate is still showing 30/7/2012 when it should be today's date.
I have checked and UAC is not turned on for this server. I have not seen this problem on any other environment so far, but the thing that is unusual (for me) about this deployment is that it is the only one I've seen installed without the IIS option.

EB doco says ……..It should also be noted that there are valid cases where it is useful not to have a schedule on an operation list. This includes
lists which should only ever be manually triggered from Event Broker, and also those that are only ever triggered by the Event
Broker Changes Activity.

Isn’t it the schedule that decides “how often ” the changes detection runs

If so what is the para in the doco saying ?

TIA

I do not usually mark more than one operation for STARTUP, but in the CSO Staff FIM solution I am building I am using this idea right now. I started the scheduler, and then stopped it again while I waited for the first of 3 startup operations to complete ... thinking that the others wouldn't start. They did. I don't think this would be considered "expected behaviour" and I think the scheduler status should be checked before ANY new operation is started. Thoughts?

Noticed that the former Documentation and Support links appear to be missing - can these please be reinstated, or if they are hiding somewhere can they be made more obvious please? I find these useful as I am sure other users will too.

From the Groups page, clicking the "Edit Operation List Groups" button shows a list of all operations, but the context of the group name is lost. You are left with not being able to see the name of the group you're editing. No breadcrumb either.

The number of operation lists that appear on the Home\Index page should be limited.

Order by the next run date and display all of the running lists. If that does not equal a certain number (10?) display as many more as needed.

Hi Product Team!

Attempting to delete operations from "/Operation" (Operation Lists Page) is met with a blank screen. The URL redirects to "/Operation/ModifyOperationLists" but the page is blank.

The only way to delete operations via the GUI is to Open the operation from the operations list. Click Actions and Delete from within the Operation. Even attempting to delete the operation this way acts strange.. When attempting to delete from within the operation the "Are you sure" window pops up for a second and automatically submits the deletion without confirmation.

Happy to ellab on this if required.