달력

1

« 2025/1 »

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
2009. 6. 4. 11:33

HPC 2008 Management Pack 설정 (관리팩) SystemCenter2009. 6. 4. 11:33

1. 모든 노드(Head/Compute)에 대해 Agent Proxy 설정
2. 기본 작업 계정 설정
   - Cluster Admin 권한이 있는 작업 계정 생성
   - 생성한 작업 계정을 모든 노드의 기본 작업 계정으로 설정
3.  (Optional) 클러스터링의 경우
   - Head 노드와 SQL Server가 Clustering되어 있는 경우에는
     각 가상 Head 노드와 가상 SQL Server를 '유지관리모드'로 설정
4. 성능 임계치 모니터 설정
   - 다음 각 모니터는 기본적으로 사용하지 않는 상태이므로
      모니터링을 통해 '사용'으로 변경하는 작업이 필요

[모니터 이름/Target]
   - Cluster CPU Usage/HPC 2008 Head Node
   - Cluster Disk Throughput/HPC 2008 Head Node
   - Cluster Network Usage/HPC 2008 Head Node
   - Daily Job Queue Time/HPC 2008 Job Scheduler

:
Posted by 커널64
2009. 6. 4. 10:48

Active Directory Management Pack 설정 (관리팩) SystemCenter2009. 6. 4. 10:48

1. 모든 DC에 대해 Agent Proxy 설정

2. Replication Monitoring을 위한 Domain Admins 그룹의 계정 생성(예: AD-Repl-Mon)

3. ADSIEDIT를 이용해 OpsMgrLatencyMonitors 컨테이너 생성(자동으로 생성될 수 있음)
   - adsiedit.msc 실행
   - Domain [ComputerName] 더블클릭
   - DC = DomainName, DC = com 우클릭 > New > Object
   - OpsMgrLatencyMonitors 컨테이너 생성

4. RunAs account 생성 및 설정
   - Run As Account > Display Name: AD-REPL-MON > 계정 정보/암호 입력 > 생성
   - Run As Profile > AD MP Account 더블클릭 > 모든 DC에 대해 Run As Account 설정

5. Client Monitoring 활성화
   - 새 그룹 생성 > Display Name: AD Client Monitoring Group
   - Monitoring에 사용할 서버들을 구성원으로 추가
   - Authoring > Management Pack Objects > Discovery > AD Client Monitoring Discovery
       > Overrides > Overrides for Group > AD Client Monitoring Group 선택 > Enable: True

6. Intersite Replication Latency 임계치 수정
   - Authoring > Management Pack Objects > Monitor
       > Active Directory Domain Controller Server Computer Role > Entity Health > Availability
       > AD Replication Monitoring > Overrides > 개체 또는 그룹 선택
       > Intersite Expected Max Latency (min) 수정

7. Replcation Latency 보고서를 위한 성능 수집 활성화
   - Authoring > Management Pack Objects > Rule > Active Directory Domain Controller Server
       > AD Replication Monitoring Preformance Collection (Sources) > Override > Domain Contoller
   - Authoring > Management Pack Objects > Rule > Active Directory Domain Controller Server
       > AD Replication Monitoring Preformance Collection (Targets) > Override > Domain Contoller

8. Task에 대한 파라미터 설정
   - Windows Support Tools의 설치 경로 확인
   - Monitoring > Microsoft Windows Active Directory > Active Directory Server 2003 > DC Server 2003 State
   - Action 창에서 Task 실행 > Override 클릭 > 설치 경로로 Override
:
Posted by 커널64
2009. 5. 31. 10:29

SCOM 2007의 ACS Reporting 설치 (ACS 보고서 배포) SystemCenter2009. 5. 31. 10:29

ACS로 사용할 관리 서버 준비 후
1. ACS 보고 서버로 사용할 SRS 서버에 관리자 계정으로 로그인
2. 임시 폴더 생성 (예: C:\ACS)
3. 설치 미디어의 \ReportModels\acs 내용을 임시 폴더로 복사
4. 설치 미디어의 \SupportTools\ReportingConfig.exe 파일을 임시 폴더로 복사
5. 명령 프롬프트 실행해 임시 폴더로 이동 후 다음 명령 실행
UploadAuditReports "<AuditDBServer\Instance>" "<Reporting Server URL>" "<임시 폴더>"
(예: UploadAuditReports "AuditDbServer\Instance" http://ReportServer/ReportServer$instance" "C:\ACS")
위 명령을 통해 Db Audit라는 데이터 원본을 생성하고 Audit.smdl, Audit5.smdl 보고 모델을 업로드하고 Reports 폴더의 모든 보고서를 업로드한다.
6. 웹브라우저를 실행해 다음 URL로 접근한다.
http://<ReportingServerName>/Reports$<InstanceName>
7. Audit Reports 폴더 클릭, 오른쪽 상단의 Show Detail 클릭
8. 'Db Audit' 데이터원본 클릭
9. 인증을 'Windows Integrated Security'로 설정

:
Posted by 커널64
2009. 5. 31. 10:13

SCOM 2007 보고서 배포 오류 - 'SqlException': Timeout expired SystemCenter2009. 5. 31. 10:13

Symptoms:
Event Type: Error
Event Source: Health Service Modules
Event Category: Data Warehouse
Event ID: 31569
사용자 삽입 이미지

Data Warehouse failed to enumerate database components to be deployed. Failed to enumerate Data Warehouse components for deployment. The operation will be retried. Exception 'SqlException': Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Component Instance name: <Instance name> Instance ID: {AC6FACD9-

Resolution:
1. OpsMgr DW 데이터베이스에 대해 exec sp_updatestats 실행
2. 1의 방법으로 해결되지 않을 경우
http://support.microsoft.com/?kbid=954643 설치 후
Managementpackinstall.sp.sql 쿼리 실행
:
Posted by 커널64
2009. 5. 28. 11:24

SCOM 2007의 방화벽 예외 구성 (Firewall Exception) SystemCenter2009. 5. 28. 11:24

Component

Exception

Port and Protocol

Configured By

RMS

·         System Center Management service

·         System Center Data Access service

·         Operations Manager Connector Framework

·         Operations Manager Customer Experience Improvement

·         Operations Manager Application Error Monitoring

5723/TCP

5724/TCP

51905/TCP

51907/TCP

51906/TCP

Setup

Setup

Setup

Setup

Setup

Management server

·         System Center Management service

·         System Center Data Access service

·         Operations Manager Connector Framework

·         Operations Manager Customer Experience Improvement

·         Operations Manager Application Error Monitoring

5723/TCP

5724/TCP

51905/TCP

51907/TCP

51906/TCP

Setup

Setup

Setup

Setup

Setup

Web console

Operations Manager Web console

51908/TCP

Setup

Web console, forms authentication, http

World Wide Web Services, http

80/TCP

Windows Firewall

Web console, forms authentication, https

Secure World Wide Web Service

443/TCP

Windows Firewall

OperationsManager database

·         SQL Server database server

·         If using a named instance, add

1433/TCP

1434/UDP

Windows Firewall

Windows Firewall

Operations Manager data warehouse database

·         SQL Server database server

·         If using a named instance add

1433/TCP

1434/UDP

Windows Firewall

Windows Firewall

Operations Manager Reporting

SQL Server Reporting Services

80/TCP

Windows Firewall

Agent, manual installation of MOMAgent.msi

System Center Management service

5723/TCP

Windows Firewall

Agent, push installation

·         System Center Management Service

·         File and Print Sharing

·         Remote Administration

5723/TCP

137/UDP, 138/UDP, 139/TCP, 445/TCP

135/TCP, 445/TCP

Windows Firewall

Windows Firewall

Windows Firewall

Agent, pending repair

·         System Center Management service

·         File and Print Sharing

·         Remote Administration

5723/TCP

137/UDP, 138/UDP, 139/TCP, 445/TCP

135/TCP, 445/TCP

Windows Firewall

Windows Firewall

Windows Firewall

Agent, pending upgrade

·         System Center Management service

·         File and Print Sharing

·         Remote Administration

5723/TCP

137/UDP, 138/UDP, 139/TCP, 445/TCP

135/TCP, 445/TCP

Windows Firewall

Windows Firewall

Windows Firewall

gateway

System Center Management Service

5723/TCP

Setup

Operations Manager Audit Collection Service database

·         SQL Server

·         If using a named instance, add

1433/TCP

1434/UDP

Windows Firewall

Windows Firewall

Operations Manager Audit Collection Service Collector

ACS Collector Service

51909/TCP

Windows Firewall

 

:
Posted by 커널64
2009. 5. 20. 13:13

DPM Server 2007 설치 (원격 SQL Server Instance) SystemCenter2009. 5. 20. 13:13

기존의 SQL Server를 사용해 DPM Server를 설치하는 경우(분리 설치)

DPM Server
KB940349 - VSS update rollup package
KB955543 - Resolve Snapshot issue
.NET Framework 2.0
Powershell 1.0
IIS, ASP.NET, WDS
SQL Server 2005 SP3 Workstation Component

Remote SQL Server Instance
SQL Server 2005 SP2 이상 필요
SQL Server 2008 지원 안함
SRS 사전 설치 및 구성
SQLPrep.msi 설치 (DPM 설치 미디어)
SQL Server Agent Serice 시작 유형: 자동

:
Posted by 커널64
2009. 5. 15. 10:16

Windows Server 2008 Core NIC Speed & Duplex 설정 Virtualization2009. 5. 15. 10:16

다음 레지스트리 키를 열어서 0000으로 시작하는 키 중에서 DriverDesc를 확인해 물리적인 NIC를 확인 후
하위 키 Ndi를 참고해 키 값을 변경한다.

HKLM\System\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}

:
Posted by 커널64
2009. 5. 13. 10:42

(SCOM 2007) Gateway Server 및 Agent의 Failover 구성 Cmdlet SystemCenter2009. 5. 13. 10:42

Powershell

Agent의 Failover 설정 Cmdlet
$primaryMS = Get-ManagementServer | where {$_Name -eq 'Filtering'}
$failoverMS = Get-ManagementServer | where {$_Name -eq 'Filtering'}
$agent = Get-Agent | where {$_Name -eq 'Filtering'}
Set-ManagementServer -AgentManagedComputer: $Agent -ManagementServer: $PrimaryMS -FailoverServer: $FailoverMS

Gateway 서버의 Failover 설정 Cmdlet
$PrimaryMS = Get-ManagementServer | Where {$_Name -eq 'Filtering'}
$failoverMS = Get-ManagementServer | Where {$_Name -eq 'Filtering'}
$gatewayMS = Get-ManagementServer | Where {$_Name -eq 'Filtering'}
Set-ManagementServer -GatewayManagementServer: $gatewayMS -ManagementServer: $PrimaryMS -FailoverServer: $failoverMS
:
Posted by 커널64
2009. 5. 11. 18:58

2009년 4월 14일 SCVMM 2008 Hotfix Rollup Virtualization2009. 5. 11. 18:58

invalid-file

List of issues that are fixed

Issue 1

When you migrate VMware virtual machines, the resource pools that are associated with the virtual machines are changed.

Issue 2

Hyper-V virtual machines have a status of "unsupported cluster configuration" if a node in a Windows Server 2008 Failover Cluster does not respond or has been restarted.

Issue 3

Differencing disks are lost when the following conditions are true:
  • You migrate a virtual machine from a Virtual Server host.
  • Multiple virtual machines share the same parent virtual hard disk file.

Issue 4

The agent status is not updated for Windows Server 2008 Failover Cluster nodes.

Issue 5

Hyper-V virtual machines in a Windows Server 2008 Failover Cluster have a status of "unsupported cluster configuration" if the cluster has a resource that has an MSCluster_Property_Resource_Cluster_Extension_XP_Type type. This resource type is typically used by storage replication software.

Issue 6

If you add a Virtual Center server by using an account that is a member of the Enterprise Admins group, you receive the following error message when the refresh host job runs:
Error (2951) Virtual Machine Manager cannot complete the VirtualCenter action on server servername.domainname.com because of the following error: Login failed due to a bad username or password. (InvalidLogin).
This hotfix rollup also includes the fixes that are documented in the following Virtual Machine Manager 2008 update:
959596  (http://support.microsoft.com/kb/959596/ ) Description of the System Center Virtual Machine Manager 2008 update to address physical to virtual (P2V) issues
:
Posted by 커널64
2009. 5. 7. 08:46

Windows 2000 Server P2V Fail (ID : 3128) Virtualization2009. 5. 7. 08:46

ID: 3128
Details: Unknown error (0x80041001)

다음 두 개의 클래스에 대한 WMI 쿼리가 실패하면서 에이전트가 죽는 현상으로
Private Hotfix 적용 후 CIMWIN32 provider에 대한 Recompile이 필요하다.
Win32_SCSIController, Win32_SCSIControllerDevice

The process that runs a WMI statement stops responding on a Windows 2000 Service Pack 3 or later-based computer
http://support.microsoft.com/default.aspx?scid=kb;EN-US;889405


c:\winnt\system32\wbem 폴더로 이동
명령 실행 : mofcomp cimwin32.mfl
명령 실행 : mofcomp cimwin32.mof
:
Posted by 커널64

티스토리툴바