Cannot see Exchange provisioning UI after Update 2
I recently applied Update 2 and now the Exchange provisioning controls are not being displayed in Active Directory management agents. When I open the Properties of an ADMA and go to the Configure Extensions page, I do not see the "Provision for" label or drop-down menu, but I do see the "RPS URI" label and textbox. If I then swith to another page within the MA and return to the Configure Extensions page, I do not see any of these controls. First view of Configure Extensions After clicking away and returning One guy at Microsoft has suggested, "I have seen things like this happen when using the client on a virtual machine, or through particular remote desktop tools. I would recommend using the Remote Desktop Client for viewing the FIM Synchronization Service Client." However, we are using the standard MS RDC and MS RDC Manager to connect to the server hosting the synch service. Has anyone else seen this issue? Does anyone know of any fixes or resolutions short of reinstalling FIM?
July 16th, 2012 6:13pm

I saw something similar happen when I imported my ILM Server Configuration export into FIM 2010 R2, only in my case I never did see the RPS URI box, just the blank area allowing no Exchange configuration. I found I could export the AD MA configuration from FIM, delete the MA and its connector space, import the MA from the file and then run a full import/full sync to repopulate the connector space. After the MA configuration was re-imported, the Exchange configuration pieces were back in the UI. I have not actually tested the Exchange 2010 provisioning after having done this, however. But this could save you having to rebuild FIM from scratch if it works for you. Chris
Free Windows Admin Tool Kit Click here and download it now
July 17th, 2012 9:27am

THANK YOU! I had the exact same issue as described where the Exchange Provisioning UI elements were missing - in a FIM 2010 R2 environment that was upgraded from ILM 2007 with FP1. Exporting the MA, Deleting the MA and its ConnectorSpace, and then Importing it again fixed the problem.
August 24th, 2012 1:03pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics