Can FIM Reporting be installed on 2 FIM servers/nodes of an F5 virtual server.

I am trying to verify if I install FIM reporting on both servers/nodes as would I with the FIMService.

I am concerned that that the FIMService on both Nodes might initiate the reporting job and what effect this might have.

TIA

Nigel

No, you can't install reporting on two service nodes. 

Is the ask specifically about the FIM Reporting piece or the SQL SSRS front-end? In the case of the first component, there's a safeguard in place to ensure that only one server processes the reporting jobs at a time if it's enabled on more than one FIM Service server. In the case of SSRS, you can absolutely load balance this.

Thanks Brian

I am planning to put ALL FIM roles onto two nodes behind F5. I understand that FIM reporting has to be installed with FIMservice so yes I want to install FIM reporting role onto both FIMService nodes. I understand that I CAN do this from your response (thankyou) because "there's a safeguard in place to ensure that only one server processes the reporting jobs at a time if it's enabled on more than one FIM Service server

Can you explain what or how this safeguard works - specifically which FIMService node will run this and how the other FIMService node (2) will pick up the job if the first FIMService (node 1 )fails - do I have to configure anything ?

Brian- with respect ; is Tomek's reply incorrect in the context of my configuration - otherwise I would need a standalone FIM Service server (not part of the F5 virtual server) running Reporting with no FIM reporting HA (beyond Hyper-V or other single node HA options) ?

I realllllyyyy appreciate this feedback and discussion as I have found very little w3 or forum information about load balancing and HA for FIM reporting (I don't mean the SCSM or DW components)

Thanks again

Nigel

Hi Tomek , many thanks for your response. Could you clarify please wrt my feedback to Brian. I really do want to ensure that  I cross all the t's and dot all the i's on this :)

TIA

Nigel

Nigel-

I don't have an install handy to find the specifics, but, there's a locking mechanism of sort that ensures the reporting job only runs on one place. You don't need to do anything to ensure a job is picked up if one of the nodes is down and along that line you also can't force jobs to run on a specific node if multiple nodes have reporting enabled.

Thanks Brian - please could you keep me posted if you uncover the specifics

Best Regards

Nigel