Yes exactely. This did not help unfortunately.
We managed to fixed it. It seems that the epo installer 5.0 does not respect default installation directories set by the system on a different volume (any other than C:\). Having installed it on c:\ did the trick.
As it resolved our situation but does not fix the issue, we consider this thread as unresolved.
Can you clarify a bit on this? The installer should certainly let you specify a drive other than C... which default installation directories are you referring to?
The thing is, if you change the registry keys for Program Files (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion), the .NET Framework redistributables get installed on the right drive, but the ePO installer still looks on c:\ for the oledb dll files.
In addition, the proposed default installation directory does not respect the registry keys mentioned above.
Not that big of an issue, but still probably worth to mention in a kb regarding the issue described above.
In addition to the answer mentioned above, here's a reproducable steps list:
1) Install Windows Server 2012, x64
2) Change registry keys in "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion" from C:\ to D:\ (Should be about 3-5 keys to edit).
3) Install SQL Server 2012, defaults with mixed auth mode (windows auth and sql auth)
4) Try login from SQL Management Tools as well as from cmd console - works
5) Try remote login - works
6) Try install ePO 5.0 on the same server - installs .NET redistributable. Later fails when trying to validate server credentials.