Showing posts with label SCOM 2007. Show all posts
Showing posts with label SCOM 2007. Show all posts

Sunday, June 1, 2014

How to install a certificate to a Windows Server 2008 R2 SP1 from a Windows Server 2003 R2 SP1 Standalone CA which is the certificate enrollment Web pages is not patch

How to install a certificate to a Windows Server 2008 R2 SP1 from a Windows Server 2003 R2 SP1 Standalone CA which is the certificate enrollment Web pages is not patch (http://support.microsoft.com/kb/922706/en-us)

Since the Windows Server 2008 R2 cannot download and install the Root CA certificates and also request a client certificates from a Windows Server 2003 R2 SP1 Standalone CA which is the certificate enrollment Web pages is not patched.

We will need a Windows XP (Or Windows Server 2003) machine to complete the task.

Download the Root CA certificates

1: On a Windows XPstart the Internet Explorer
2. Go to the certificate server website (in our case http://abc....../certsrv)
3. Click on Download CA certificate, certificate chain, or CRL
4. Click Download CA Certificate chain and save it on the machine.
5. Once the certificate is downloaded, copy it to the unmanaged Windows Server 2008 R2 (Our target monitored server)

6. Login the unmanaged Windows Server 2008 R2

7. Open an MMC connect to Local Computer and load the certificates snap-in (Local Computer)
8. Go to Trusted Root Certification Authorities right click, all tasks, import and import the Root CA.

Request the unmanaged Windows Server client certificates and installation

1. start the Internet Explorer
2. Go to the certificate server website (in our case http://demo-dc01/certsrv)
3. Click on Request a certificate, choose Advanced certificate request next click

Create and submit a request to this CA

On the Advanced Certificate Request page, do the following:

  1. Under Identifying Information, in the Name field, enter a unique name, for example, the fully qualified domain name (FQDN) of the computer you are requesting the certificate for. For the remaining fields, enter the appropriate information.

clip_image001Note

Event ID 20052 of type Error is generated if the FQDN entered into the Name field does not match the computer name.

 

  1. Under Type of Certificate Needed:
    Click the list, and then select Other.
    In the OID field, enter 1.3.6.1.5.5.7.3.1,1.3.6.1.5.5.7.3.2
  2. Under Key Options, make the following selections:
    Click Create a new key set
    In the CSP field, select Microsoft Enhanced Cryptographic Provider v1.0
    Under Key Usage, select Both
    Under Key Size, select 1024
    Select Automatic key container name
    Select Mark keys as exportable
    Clear Export keys to file (not required for Windows Server 2008 AD CS)
    Clear Enable strong private key protection
    Click Store certificate in the local computer certificate store.
  3. Under Additional Options:
    Under Request Format, select CMC
    In the Hash Algorithm list, select SHA-1
    Clear Save request to a file
    In the Friendly Name field, enter the FQDN of the computer that you are requesting the certificate for.
  4. Click Submit.
  5. If a Potential Security Violation dialog box is displayed, click Yes.
  6. When a Certificate Pending page displays, close the browser.

To approve the pending certificate request

  1. Log on to the computer hosting Certificate Services as a certification authority administrator.
  2. On the Windows desktop, click Start, point to Programs, point to Administrative Tools, and then click Certification Authority.
  3. In Certification Authority, expand the node for your certification authority name, and then click Pending Requests.
  4. In the results pane, right-click the pending request from the previous procedure, point to All Tasks, and then click Issue.
  5. Click Issued Certificates, and confirm the certificate you just issued is listed.
  6. Close Certification Authority.

To retrieve the certificate

  1. Log on to the computer where you want to install a certificate (for example, the gateway server or management server).
  2. Start Internet Explorer, and connect to the computer hosting Certificate Services (for example, http://<servername>/certsrv).
  3. On the Microsoft Certificate Services Welcome page, click View the status of a pending certificate request.
  4. On the View the Status of a Pending Certificate Request page, click the certificate you requested.
  5. On the Certificate Issued page, click Install this certificate.
  6. In the Potential Scripting Violation dialog box, click Yes.
  7. On the Certificate Installed page, after you see the message that Your new certificate has been successfully installed, close the browser.

On Windows XP

Step 4: Open an MMC connect to Local Computer and load the certificates snap-in (Local Computer)

Step 5: Go to Personal, select the client certificate which is you just installed right click, all tasks, export -> “Personal Information Exchange - PKCS #12 (.PFX)

  1. In the new wizard kill “Next”
  2. Select “Yes , Export the private key”
  3. Click “Next”
  4. Select “Personal Information Exchange – PKCS #12 Certificates (PFX)”
  5. Select “Enable Strong protection (requires IE5.0, NT4 SP4 or above)”
  6. Click “Next”
  7. Type a password for the certificate twice and kill “Next”
  8. Select “Browse” c:\serverFQDN.pfx”
  9. Click “Next”
  10. Check the export information and if correct kill “Finish”
  11. Click “OK” to finish the export

Save the .pfx on desktop and copy it to the unmanaged Windows Server 2008 R2

Install the Client certificates on unmanaged Windows Server 2008 R2

  1. Login the Windows Server 2008 R2
  2. On the start menu kill “Start” and “Run”

  3. Type “cmd”

  4. Navigate to > cd “program files\System Center Operations Manager 2007\Supportools\i386”

  5. Type >MOMcertimport.exe “c\:servername.domain.com.pfx” or “c:\servername.pfx”

  6. Type the asked password for the certificate import and press “Enter”.

  7. The certificate is now imported in OpsMgr 2007.

  8. Restart the “OpsMgr Health Service” on the server.

Reference:

How to Obtain a Certificate Using Windows Server 2003 Stand-Alone CA in Operations Manager 2007

http://technet.microsoft.com/en-us/library/bb735417.aspx

How to use Certificate Services Web enrollment pages together with Windows Vista or Windows Server 2008

http://support.microsoft.com/kb/922706/en-us

Update for Windows Server 2003 (KB922706)

http://www.microsoft.com/en-us/download/details.aspx?id=4758

http://www.toolzz.com/?p=279

http://blogs.technet.com/b/operationsmgr/archive/2009/09/10/step-by-step-for-using-certificates-to-communicate-between-agents-and-the-opsmgr-2007-server.aspx Print Friendly and PDF
Share/Bookmark

Monday, May 5, 2014

Apply SCOM 2007 SP1 Rollup hotfix and CU 1 steps

SCOM 2007 SP1 Rollup Hotfix and CU1 upgrade:

Install KB971541 (Description of System Center Operations Manager 2007 Service Pack 1 Update)
1. Run Server Update
2. Check Application Log:
“1022 - Update KB971541 successfully”

“11728 - Configuration Completed”

“1022 - Update KB97154-ENU Successfully”

“11728 - Configuration completed successfully”

3. Run Reporting Server Update
4. Check Application Log:
“1022 - Update “KB971541 successfully”
“11728 - Reporting Server - configuration”
5. Go to “Add/Remove Program” check -> System Center Operating Manager 2007 version “6.0.6278.0”
6. check -> System Center Operating Manager 2007 Reporting Server version “6.0.6278.0”

Install KB2028594 (Cumulative Update 1 for System Center Operations Manager 2007 SP1)
1. Run Server Update
2. Check Application log:
“1022 - Update KB2028594 successfully”
“11728 - Configuration Completed”
3. Check ALL event log to see if there are any errors
4. Go to SCOM DB by using SQL Server Management Studio
5. Select DB “Operation Manager DB”(OpsDB)
6. Copy the “CU1_Database.sql” to a new query and run “Parse” to check the query is there are any syntax error
7. If no error occurs, execute the SQL script.
8. Select DB “Operation Manager DW” (Warehouse)
9. Copy the “CU1_DataWarehouse.sql” to a new query and run “Parse” to check the query is there are any syntax error
10. If no error occurs, execute the SQL script.
11. Import the MP update
12. Go to SCOM console -> Administration Tab -> Management Packs - Click “Import Management Packs” -> Select “Micros.SystemCent.DataWarehouse” (You will see a “6.0.6278.112” - “Microsoft Generic Report Library”
13. Click “Import”
14. Go to “Administration” -> Device Management -> Pending Management” -> Approve Agent Update

Remark: The SCOM admin console also need to apply the above update for remote administration (On client side)

Reference:
The SP1 Cumulative Update 1 (CU1) for OpsMgr 2007 SP1 has shipped

http://blogs.technet.com/b/kevinholman/archive/2010/07/31/opsmgr-2007-sp1-cu1-hotfix-ships-and-my-experience-installing-it.aspx


http://wenku.baidu.com/view/ef488dfbf705cc1755270998.html


http://blogs.technet.com/b/kevinholman/archive/2009/11/09/opsmgr-2007-sp1-cumulative-rollup-hotfix-has-shipped.aspx

Get it from the download Center:

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=62b6c324-38b9-47df-bd89-a62908f0b642

The KB article describing the fixes, changes, and instructions:

http://support.microsoft.com/?kbid=2028594

Print Friendly and PDF
Share/Bookmark

Saturday, September 28, 2013

SCOM 2007 SP1 maintenance mode history

To get maintenance mode history, you will need to use SSMS to run the following query to check those maintenance mode history which is available in the OperationsManager database or DW:

select * from dbo.vMaintenanceModeHistory

 

Reference:

http://blogs.technet.com/b/kevinholman/archive/2009/06/05/maintenance-mode-tying-the-text-of-the-category-to-the-database.aspx

http://www.greypixel.nl/?p=209

Print Friendly and PDF
Share/Bookmark

Saturday, August 24, 2013

Re-install the SCOM agent from SCOM console

  1. Go to “Administration” -> “Device Management” -> “Agent Managed”

  2. Find the problematic monitored server

  3. Select it and go to “Actions” -> Uninstall....

  4. After the uninstall completed, select the “Agent Managed” again, right click and select “Discovery Wizard”

  5. Add the problematic monitored server again to start to re-install SCOM agent

  6. After the reinstall completed, go to “C:\Program Files\System Center Operations Manager 2007\HelperObjects” to copy the “OOMADs.msi” to this folder.

  7. Check the “Managed agent” status of the server and also the event log of the problematic monitored server.

Print Friendly and PDF
Share/Bookmark

SCOM 2007 reconnect those disconnected "Not monitor" agent

SCOM 2007 reconnect those disconnected "Not monitor" agent

  1. Login the problematic monitored server (client)
  2. Stop the “OpsMgr Heath Service”
  3. Go to “C:\Program Files\System Center Operations Manager 2007”
  4. Rename the folder “Health Service State”
  5. Go to SCOM console
  6. Go to “Administration” -> “Device Management” -> “Agent Managed”
  7. Find the problematic monitored server
  8. Select it and go to “Actions” -> “delete”

  9. Go back to the problematic monitored server

  10. Restart the “Health Service State”

  11. Check the “Managed agent” status of the server and also the event log of the problematic monitored server.

Print Friendly and PDF
Share/Bookmark