Share via


Management Server_library

To enable or disable Mutual Authentication

  1. In the MOM 2005 Administrator console, navigate to Administration / Global Settings.

  2. Open the Security Properties.

  3. On the Security tab of the Security Properties dialog box, clear the Mutual Authentication required check box. [Alternatively, select the checkbox to require mutual authentication.]

  4. Right-click the Management Pack folder and click Commit Configuration Change.

  5. Restart the MOM Service on all of the Management Servers in the management group.

  6. Change this setting on all affected agents. See the procedures below. The first two procedure require that the Control Level=Full.

To change the settings on agents that all use the same Action Account

  1. In the Administrator console, navigate to Administration / Computers and select Agent-managed Computers.

  2. Multi-select all the agents that use the same Action Account, right-click them, and click Update Agent Settings.

  3. In the Update Agent Settings Task dialog, enter the agent Action Account credentials and click OK. This will update the settings you made to the Management Server on all of these agents. If you do not specify the Action Account credentials, the Action Account on all of these agents will be set to Local System.

To change the setting on each agents that use different Action Accounts

  1. In the Administrator console, navigate to Administration / Computers and select Agent-managed Computers.

  2. Select the agent, right-click it and click Update Agent Settings.

  3. In the Update Agent Settings Task dialog, enter the agent Action Account credentials and click OK. This will update the settings you made to the Management Server on only this agent. If you do not specify the Action Account credentials, the Action Account on this agent will be set to Local System.

To change the setting on agents where the Control Level = None

  1. On the managed computer, logon with administrator-level privileges.

  2. In Add or Remove Computers, select Microsoft Operations Manager 2005 Agent and click Change.

  3. Select the Modify option and click Next.

  4. Select the Modify Management Group option, select the management group from the drop-down list, and click Next.

  5. On the Active Directory Configuration page, select the option that matches the change you made on the Management Server and finish the wizard.

To enable or disable Block legacy agents setting

  1. In the MOM 2005 Administrator console, navigate to Administration / Global Settings.

  2. Open the Security Properties.

  3. On the Security tab of the Security Properties dialog box, clear the Mutual Authentication required check box.

  4. Clear the Block legacy agents check box. [To block legacy agents, select the checkbox]

  5. Right-click the Management Pack folder in the Administrator console and click Commit Configuration Change.

  6. Restart the MOM Service on the Management Server.

To enable or disable the Reject new manually installed agents setting

  1. In the MOM 2005 Administrator console, navigate to Administration / Global Settings.

  2. Open the Management Server Properties.

  3. On the Agent Install tab, clear the Reject new manual agent installations check box. (To reject new manually installed agents, select the check box.)

  4. Right-click the Management Pack folder in the Administrator console and click Commit Configuration Change.

    Note

    Before you restart the MOM Service on the Management Server in the next step, use the Event Viewer under the Application Log on the Management Server to verify that Event ID 21241 appears. The description of Event ID 21241 is as follows: The MOM Server detected a change to the rules for one or more computers, and will begin downloading the new rules and configuration settings to the affected computers.

  5. After Event ID 21241 appears on the Management Server, restart the MOM Service on the Management Server.

To enable or disable agent proxying in Global Agent Settings

  1. In the MOM 2005 Administrator console, navigate to Administration / Global Settings.

  2. Open the Agent Properties.

  3. On the Security tab of the Agent Properties dialog box, select the Prevent agents from proxying for other computers or network devices check box. [To enable agent proxying, clear the checkbox]

To enable or disable Server-Side Responses

  1. In the MOM 2005 Administrator console, navigate to Administration / Global Settings.

  2. Open the Security Properties.

  3. On the Security tab, clear the Disable execution of custom responses on Management Servers option. [To disable Server-Side responses, select the checkbox]

  4. Click OK.

To enable or disable Read-Only access for the Web Console

  1. On the server hosting the Microsoft Operations Manager 2005 Web Console application, open the %INSTALLDRIVE%\ Program Files\Microsoft Operations Manager 2005\WebConsole\web.config file in a text editor.

  2. In the <appSettings> node change the node "<!--add key="Readonly" value="true"/-->" to "<add key="Readonly" value="true"/>".

  3. Stop and Restart the Microsoft Operations Manager 2005 Web Console application in the Internet Information Services snap-in.

To update agent settings for a specific MOM 2005 agent (inside a firewall)

  1. In the MOM Administrator console, expand the Administration node.

  2. Expand the Computers node and click Agent-Managed Computers.

  3. In the results pane, right-click the agent-managed computer and select Synchronize Communication Settings.

    Note

        You can use multi-select to select all the agents you want to update and then use the dialog to change all these agents.

  4. In the Update Agent Settings Task dialog box, under Which account do you want to use to update the agent settings, either select the Management Server Action Account option, or select the Other and supply credentials that have administrator rights on the agents.

    Note

        If you have selected multiple agents, the credentials you supply for the account to update the agent settings must be a local administrator on all the agents.

  5. Under Which account do you want to use for the Agent Action Account, either select the Local System option, or select the Other option and supply credentials for an account that has the "Log on as a batch job" privileges on the agent.

    Note

        If you have selected multiple agents, you must either supply credentials for a domain account for the Action Account on all agents, that is, all agents will use the same account, or use the local system account on each agent. If you do not specify an account, the local system is used by default. This setting overwrites the current setting.

  6. Click OK.

To change the Identity of the DAS COM+ application

  1. On the Management Server, open the Component Services snap-in.

  2. Navigate to the Microsoft Operations Manager Data Access Server application and open its Properties dialog

  3. On the Identity tab, enter the accounts <domain\user name> in the User textbox.

  4. Enter the password in the Password and Confirm password textboxes.

  5. Click OK.

  6. Right-click the application and click Shut down.

  7. When the application has completed shutting down, right-click it and click Start.

To use Network Service for DAS where the Management Server and MOM Database are on separate computers

This process requires procedures to be done on both the MOM Database Server and then the MOM Management Server.

Important

    You can only do this if the Management Server is running on Windows Server 2003. Windows 2000 does not support the Network Service account.

On the MOM Database Server:

  1. On the MOM Database Server, verify that the MSSQLSvc Service Principal Name is registered by using "setspn.exe -L <SQL Server FQDN>" at the command line, where <SQL Server FQDN> is the Fully-Qualified Domain Name of the MOM Database Server Instance.

  2. In SQL Server Enterprise Manager, expand the OnePoint folder.

  3. Add a new database user by right-clicking on the Users sub-node of the OnePoint database folder and selecting New Database User.

  4. In the Database Users - New User dialog, enter the computer name in the Login name text box. Computer names follow the format domain\computername$. Do not forget the trailing "$".

  5. Grant this computer account user the db_owner database role membership and click OK.

  6. Navigate to the Security folder for the SQL Server instance.

  7. Add a new SQL Server Login by right-clicking on the Logins folder and selecting New Login.

  8. On the General tab of the SQL Server Properties - New Login dialog, enter the computer name in the Name textbox. Computer names follow the format domain\computername$. Do not forget the trailing "$".

  9. On the Database Access tab, grant this computer account db_owner access to the OnePoint database by selecting the Permit checkbox next to the OnePoint database and then the db_owner checkbox below.

  10. Click OK.

On the Management Server

  1. On the Management Server, stop the MOM Service.

  2. In the Component Services snap-in, expand Component Services / Computers / My Computer / COM+ Applications.

  3. Right-click the Microsoft Operations Manager Data Access Server node and click Shut down.

  4. After the application has stopped, open its properties.

  5. On the Identity tab, select the System Account and the Network Service options, and then click OK.

  6. Start the MOM Service.

  7. After the MOM Service has started, open the MOM Administrator console and confirm that you do not see any DAS errors.

To use Local Service for DAS where the Management Server and MOM Database are on the same computer

Follow this process to use the lower-privileged Local Service account for the DAS component when the MOM Management Server and MOM Database are installed on the same computer.

Important

    You can only do this if the Management Server is running on Windows Server 2003. Windows 2000 does not support the Local Service account.

  1. In the Microsoft SQL Server Enterprise Manager, navigate to the Security folder for the SQL Server instance.

  2. Add a new SQL Server Login by right-clicking on the Logins folder and selecting New Login.

  3. On the General tab of the SQL Server Properties - New Login dialog, enter "NT AUTHORITY\Local Service" in the Name text box.

  4. On the Database Access tab, grant the "NT AUTHORITY\Local Service" account db_owner access to the OnePoint database by selecting the Permit checkbox next to the OnePoint database and then the db_owner checkbox below.

  5. Click OK.

  6. In SQL Server Enterprise Manager, expand the OnePoint folder.

  7. Add a new database user by right-clicking on the Users sub-node of the OnePoint database folder and selecting New Database User.

  8. In the Database Users - New User dialog, select the account "NT AUTHORITY\Local Service" from the Login name combo box.

  9. Grant the Local Service account user the db_owner database role membership and click OK.

  10. Stop the MOM Service.

  11. In the Component Services snap-in, expand Component Services / Computers / My Computer / COM+ Applications.

  12. Right-click the Microsoft Operations Manager Data Access Server node and click Shut down.

  13. After the application has stopped, open its properties.

  14. On the Identity tab, select the System Account and the Local Service options, and then click OK.

  15. Start the MOM Service.

  16. After the MOM Service has started, open the MOM Administrator console and confirm that you do not see any DAS errors.

To use client certificates and SSL with MCF or MMPC

On the source management groups Management Server:

  1. Run the utility runas.exe /user <mmpc_service_account> mmc.exe.

  2. On the File menu, select Add/Remove Snap-in.

  3. On the Standalone tab, click Add.

  4. Double-click on Certificates, click Finish, and then click Close.

  5. Click OK to close the Add/Remove Snap-in dialog.

  6. In the console, expand Console Root/Certificates - Current User/Personal/Certificates. If Certificates does not exist, select Personal.

  7. Right-click and select All Tasks/Request New Certificate.

  8. Click Next and select User certificate type from the list, or select any other certificate type that has client authentication as the certificate purpose.

  9. Click Next and enter a friendly name and description. Click Next.

  10. Verify the settings you entered are correct, and click Finish.

    Note

        On Windows 2000, the wizard requests that you install the certificate. Click Install Certificate to continue.

  11. Verify that the client certificate is present in the Personal Certificates folder of the MMPC service account.

  12. Right-click on the client certificate and select All Tasks/Export.

  13. Click Next and select No, do not export the private key.

  14. Click Next and select DER encoded binary x.509 (.CER).

  15. Click Next, save the file, and then click Next.

  16. Verify that the information you exported is correct, and then click Finish.

  17. Create a directory under the DATADIR directory called "ConnectorService" if one does not already exist. The DATADIR is specified in the HKEY_LOCAL_MACHINE\SOFTWARE\Mission Critical Software\OnePoint registry key and is %Installation Root%\Documents and Settings\All Users\Application Data\Microsoft\Microsoft Operations Manager\ by default.

  18. Rename the certificate file to "ClientCertificate.cer" and put a copy of it on the source Management Server in the ConnectorService directory.

  19. Restart momconn.exe on the source Management Server.

On the destination management groups Management Server:

  1. Obtain a server certificate in Base-64 encoding format. Install the certificate on the destination Management Server. For more information about obtaining server certificates, see the Internet Information Services (IIS) help.

    Note

        If you already have a server certificate, this step is not necessary.

  2. In the IIS Manager, right-click the Microsoft Operations Manager 2005 Connector Framework Web site and click Properties.

  3. On the Directory Security tab, under Secure communications, click Edit. If the Edit button is not enabled, you must install a server certificate.

  4. In the Secure Communications dialog, select the Require secure channel (SSL) checkbox.

  5. Under Client certificates, select the Require client certificates option.

  6. Select the Enable client certificate mapping checkbox.

  7. Click Edit to configure the client certificate mapping. Map the certificate the DAS account (or the account used for the MOM to MOM Connector service if it is different). For more information about completing the mapping, see the Internet Information Services (IIS) help.