If you are like me and just itching to try and install OpsMgr 2007 DB and Reporting on Longhorn and cannot wait till SQL 2008 to install SQL on Longhorn as they do not support SQL 2005 on Longhorn you can try my HACK!! Yes, this is NOT supported by the OpsMgr team and our test manager will probably kill me for posting this on the web but what the heck that why there are blogs. These steps are a culmination of things Stephanie and Melissa on our test team and I have tried to get it to work. So here it goes…
ü Add Roles via Server Manager (Go to APPWIZ.CPL and then select “Turn Windows features on or off”): Application server, IIS 7 (w/IIS6 support), and dependent components. You can verify this by clicking on Roles and seeing under the Role Services installed for the below options.
ü Install SQL 2005 RTM STD or Ent. Install the ‘SQL Server Database Services’ and ‘Reporting Services’. Default Instance Name. Domain account for Service Account. Windows authentication mode. SQL Collations default. Install default configuration for report server installation options.
ü Install SQL 2005 SP2. Use default Settings
ü Set the ReportServer application pool to run under LocalSystem
o Open IIS Manager.
o Expand the tree until you can select Application Pools.
o Right-click the ReportServer$Instance Pool and select Advanced Settings. (as shown in the image below)
o Select Identity under Process Model, click the browse (…) button.
o In the Application Pool Identity window, select LocalSystem from the Built-in account list box. Press OK twice.
ü Enable script execution in the ReportServer vdir
o In IIS Manager, expand the tree through the default website and select the ReportServer vdir.
o Select Handler Mappings from the Features View under IIS. (as shown in the image below)
o Select the ISAPI-dll
o From the Handler Mappings Actions pane, select Edit Feature Permissions. (as shown in the image below)
o Check the Script checkbox and press OK.
ü Disable ApplicationHost Modules
o Navigate to <Drive>:\Windows\System32\inetsrv\config\applicationHost.config and open the applicationHost.config file in notepad
o Replace the “Add” parameter for “DynamicCompressionModule” and “StaticCompressionModule” to “remove” so it should look like this
ü Reporting Services configuration
o Launch Reporting Service Configuration Tool by going to Startà Programs àMicrosoft SQL Server 2005 à Configuration Tools à Reporting Services Configuration
o Ensure in Web Service Identity tab is green and the ASP .Net Service Account is set to NT Authority\System, the Application Pool for Report Server and Report Manager is set to ReportServer
o Check next to the Web Service Identity tab is green and the Built-in Account: Local System. You need to choose the drop down and reselect it again and then click Apply. If the Apply button is not activated it will not take effect.
ü Ensure you can browse to http://<servername>/reports without any errors. If no reports are present the Report Manager UI should state “There are no items in Home. Click Help for more information about this page”.
Do not try this in your production environment.
Satya Vel | Program Manager | System Center |
PingBack from http://www.systemcenterforum.org/windows-2008-support-coming-to-operations-manager-2007/
La gente del grupo de producto de Ops Manager publico la manera de realizar la instalacion de la base
I did not do the <remove name... part and it worked anyway. I had a lot of issues when I edit applicationHost.config. Now I have all Ops Mgr components running in Hyper-V and 2008.
I saw an interesting blog post from the Operations Manager product team about Ops Mgr db and reporting
Thought not supported in ANY way…the OpsMgr product team blog tells you how to do it… http://blogs.technet