Never mind, I've fixed it. In fact, I'm not sure if the OLAP database ever existed in the first place since I installed FEP 2010.
Anyway, the solution may come in handy for others in the same position. There's are a couple of executables in the FEP 2010 installation folder (%ProgramFiles%\Microsoft Forefront\Forefront Endpoint Protection on my system), called EnterpriseSecurityDW.exe
and EnterpriseSecurityDW2008.exe (the latter presumably is for running against SQL 2008). I can't find any official documentation on these executables, but they do give you their required arguments if you run them from a command prompt.
Anyway, since we're running against SQL 2008 R2, I decided to try the EnterpriseSecurityDW2008.exe. The following set of parameters worked for me (line breaks added for readablility:
EnterpriseSecurityDW2008.exe
- /serverName:OurDBServer\SQL2008
- /sqlDatabaseName:FEPDW_ABC
- /OlapDb:FEPDW_ABC
- /reportsUser:ABC\FEP_Reporting
- /overwriteDatabase:1
ABC is the ConfigMgr site code for the existing Data Warehouse database, and also the NetBIOS AD domain name. The sqlDatabaseName is the name of the data warehouse DB on the SQL instance, not the core FEP database (FEPDB_ABC). The OlapDb is the name that
will be given to the OLAP database hosted by Analysis services.
Note that the arguments are case-sensitive, so this won't work if you specify /servername instead of /serverName, for example. Remember to run this under an administrative command prompt, and if your SQL server is not local to the ConfigMgr machine, make
sure that the user account you're running it under has appropriate permission on the SQL instance.
Hope this is useful for someone.
Chris.
- Marked as answer by
Chris McKeown
Monday, May 23, 2011 1:27 PM