December, 2007

Hi all - I am nearly complete with updating the How To Cluster the RMS for SP1 procedures as they will appear in the Deployment Guide.  Here they are, minus a screen shot.  These procedures will work for the RTM version as well, although you will need to skip some SP1 specific steps (like the Encryption KeyBackup or Restore Wizard launching automatically at the end of RMS setup, SP1 has this, RTM does not).  This procedure is from the Mutliple Server, Single Management Group scenario and assumes the prerequisites stated therein. Also, this procedure does not include the steps necessary to add a cluster node to the RMS cluster (AddRMSNode) that was not present when the ManagmentServerConfigTool.exe InstallCluster action was run. That will be added when the Deployment Guide is published with the SP1 update. 

The procedure is attached.

 Chris Fox

We had an error in the readme that went out with the FRS management pack that says that Windows Server 2003 is not a supported platform. This is an error; we do support Windows Server 2003 with this management pack.

 We are currently repackaging the MP with an updated readme and it will be released shortly.

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.

Happy Holidays!!!

Satya Vel | Program Manager | System Center |

This is a visual diagram of how computer discovery works in OpsMgr 2007. The list of prerequisites required to discover servers and install an agents are listed below as well:

Description: RPC endpoint mapper

Port number: 135

Protocol: TCP/UDP

Description: NetBIOS name service

Port number: 137

Protocol: TCP/UDP

Description: NetBIOS session service

Port number: 139

Protocol: TCP/UDP

Description: SMB over IP

Port number: 445

Protocol: TCP

Display Name: Netlogon

Started: True

State: Running

Description: MOM Channel

Port number: 5723

Protocol: TCP/UDP

Display Name: Windows Installer

Started: True

State: Running

Enable: File and Print Sharing

Steps on how to enable F&P can be found here: http://technet2.microsoft.com/windowsserver/en/library/0cf7e1a7-f7a2-49f9-8fee-730d9d1ea2071033.mspx?mfr=true

Enable: Remote Administration Exception

Steps on how to enable Remote Admin can be found here: http://technet2.microsoft.com/windowsserver/en/library/b8057a7a-a0d3-40b5-8224-ea6a4f5e17231033.mspx?mfr=true

 Satya Vel

Below is the complete list of all the command line parameters for OpsMgr 2007 server roles including Audit Collection. And the command line parameters for upgrading to Service Pack 1 (SP1) Release Candidate (RC)

Agent – (MOMAgent.msi)

msiexec.exe /i \\path\Directory\MOMAgent.msi /qn /l*v \logs\MOMAgent_install.log  USE_SETTINGS_FROM_AD=0 MANAGEMENT_GROUP=<MG_Name> MANAGEMENT_SERVER_DNS=<MSDNSName> ACTIONS_USE_COMPUTER_ACCOUNT=0 ACTIONSUSER=<AccountUser> ACTIONSDOMAIN=<AccountDomain> ACTIONSPASSWORD=<AccountPassword>

Typical – (MOM.msi)

msiexec.exe /i \\path\Directory\MOM.msi /qn /l*v \logs\MOMTypical_install.log ADDLOCAL=ALL USE_SETTINGS_FROM_AD=0 MANAGEMENT_GROUP=<MG_Name> MANAGEMENT_SERVER_DNS=<MSName>

SQLSVR_INSTANCE=<servername\InstanceName> ADMIN_ROLE_GROUP=“DomainName/Account” ACTIONS_USE_COMPUTER_ACCOUNT=0 ACTIONSUSER=<AccountName>  ACTIONSDOMAIN=<AccountDomain>  ACTIONSPASSWORD=<AccountPassword> SDK_USE_COMPUTER_ACCOUNT=0 SDK_ACCOUNT=<AccountName> SDK_DOMAIN=<DomainName> SDK_PASSWORD=<Password>

Database --(MOM.msi)

msiexec.exe /i \\path\Directory\MOM.msi /qn /l*v \logs\MOMDB_install.log  ADDLOCAL=MOMDB USE_SETTINGS_FROM_AD=0 MANAGEMENT_GROUP=<MG_Name> SQLSVR_INSTANCE=<servername\InstanceName> DB_SIZE=500 ADMIN_ROLE_GROUP=<AD Security Group Name> DATA_DIR=<SQL data files folder> LOG_DIR=<SQL log files folder>

Server --(MOM.msi)

msiexec.exe /i \\path\Directory\MOM.msi /qn /l*v \logs\MOMServer_install.log  ADDLOCAL=MOMServer USE_SETTINGS_FROM_AD=0 MANAGEMENT_GROUP=<MG_Name> MOM_DB_SERVER=<ServerName\Instance> ACTIONS_USE_COMPUTER_ACCOUNT=0 ACTIONSUSER=<AccountName> ACTIONSDOMAIN=<AccountDomain>  ACTIONSPASSWORD=<AccountPassword> SDK_USE_COMPUTER_ACCOUNT=0 SDK_ACCOUNT=<AccountName> SDK_DOMAIN=<AccountDomain> SDK_PASSWORD=<AccountPassword>

UI --(MOM.msi)

msiexec.exe /i \\path\Directory\MOM.msi /qn /l*v \logs\MOMUI_install.log  ADDLOCAL=MOMUI,MOMMonadShell USE_SETTINGS_FROM_AD=0 MANAGEMENT_GROUP=<MG_Name> ROOT_MANAGEMENT_SERVER_DNS=<RMSDNSName>

WebConsole (MOM.msi)

msiexec.exe /i \\path\Directory\MOM.msi /qn /l*v \logs\MOMUI_install.log  ADDLOCAL=MOMWebConsole WEB_CONSOLE_AUTH_TYPE=0 ROOT_MANAGEMENT_SERVER_DNS=<RMSNetbiosName>

( ‘1’ is windows auth and ‘0’ is Forms auth)

Data Warehouse-  (Reporting2007.msi)

msiexec.exe /i \\path\Directory\Reporting2007.msi /qn /l*v "D:\LOGS\REPORTING_INSTALL.LOG" ADDLOCAL=”MOMREPORTINGDB” SQLSVR_INSTANCE=”<COMPUTERNAME\INSTANCE1>" MOMREPORTINGDBNAME=”SCOMDW” DB_SIZE=”1000”

Reporting Server (Reporting2007.msi)

msiexec.exe /i \\path\Directory\Reporting2007.msi /qn /l*v "D:\LOGS\REPORTING_INSTALL.LOG" ADDLOCAL=”MOMREPORTING” SQLSVR_INSTANCE="<COMPUTERNAME\INSTANCE>" MOMREPORTINGDBNAME=”SCOMDW” MGSERVER=<COMPUTERNAME> PREREQ_COMPLETED="1" REPORT_SERVER_FULL_HTTP_PATH="http://%COMPUTERNAME%:80/ReportServer$INSTANCE1" DATAREADER_USER=<AccountUser> DATAREADER_PASSWORD=<AccountPassword> DATAREADER_DOMAIN=<AccountDomain>  DBWRITEACTIONSUSER=<AccountUser> DBWRITEACTIONSPASSWORD=<AccountPassword> DBWRITEACTIONSDOMAIN=<AccountDomain>

Gateway Server (MOMGateway.msi)

msiexec /i \\path\Directory\MOMGateway.msi /qn /l*v D:\GATEWAY_SERVER_INSTALL_1.LOG ADDLOCAL=MOMGateway,MOMNonRootServer SECURE_PORT=5723 MANAGEMENT_GROUP=MyConfigGroup MANAGEMENT_SERVER_DNS=<MS_Name> IS_ROOT_HEALTH_SERVER=0 ROOT_MANAGEMENT_SERVER_AD=<RMS_Name> ROOT_MANAGEMENT_SERVER_DNS=<RMS_Name> ROOT_MANAGEMENT_SERVER_PORT=5723 ACTIONS_USE_COMPUTER_ACCOUNT=0 ACTIONSUSER=<DomainUser> ACTIONSDOMAIN=<domainname> ACTIONSPASSWORD=<password>

Audit Collection Server (AdtSetup.exe)

The cmd line you will use would look like this:\\PATH\Directory\AdtSetup.exe /i /s /p:ACSInstallParameters.xml

You will need to specify ACSInstallParameters.xml while passing the command line you will configure all your setting in the XML file before passing it. The XML file is attached.

For ‘/i' is for ‘install’, ‘/s’ is for ‘silent’, and ‘/p’ is for parameter (file)… 

These are the command line parameter to upgrade from OpsMgr 2007 RTM to SP1 RC. Users must upgrade the RMS first which will remotely upgrade the DB. When you upgrade the Reporting Server setup will remotely upgrade the Data Warehouse as well. In order to upgrade the RMS, MS or UI you will need to run step 1 and then step 2 of the command line.