kobi001

henry.gray: I used the Tinkertry method when I tried the first time. Are you saying that you have you succeeded in installing Forefront using this method? Maybe there has been an update to WS2012R2E to allow Forefront to work? Maybe I missed something when duplicating the method. You had tried in June '14 and I in September '14 when it failed. I know that the Tinkertry method worked without DrivePool as I had tried it before installing DrivePool on my first build. Looking at the Tinkertry site the latest update to the installation method was May 3, 2014. I wonder what has changed? henry.gray, please confirm that you have Forefront up and running and if you did anything differently than the method listed in the Tinkertry link.

Thanks for the advice. My WS2012R2 Essentials box is up and running and all is well. Has there been any other thoughts on the Forefront incompatibility? I am reluctant to destabilize my system...

Sorry for the late reply, I've been away from the server configuration for the week. I installed 1.5.1993.0 but the errors resulted every time I tried to configure a setting, so I uninstalled and all is normal again. My attention is now focused on trying to figure out why I cannot connect a Win 7 Pro box to the server (The server is not available. Try connecting again....arrgh!) I may come back to the Forefront issue later after I figure out my connection problem and will post if I try your suggestions. I will certainly be monitoring if someone comes up with a workaround.

I have the same problem with similar setup. Has there been any update in finding a workaround for allow use of Forefront on WS2012R2 with DrivePool v2.1.1.561?