SCVMM의 P2V 시 BITS 포트 변경

1. HKLM\Software\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings
2. DWORD 값 생성, P2VBITSTcpPort
3. 해당 DWORD의 값을 원하는 포트로 설정
4. Virtual Machine Manager 서비스 재시작

SCCM 하드웨어 인벤토리 커스터마이징

- 레지스트리 정보 수집 및 보고(Resource Explorer)

Primary site server의 <ConfigMgr Install Directory>\inboxes\clifiles.src\hinv 폴더의 두 개의 MOF 파일(Configuration.mof, SMS_def.mof)을 기반으로 하드웨어 정보가 수집된다.

Configuration.mof

이 파일은 하드웨어 인벤토리 클라이언트 에이전트에 의해 수집되는 데이터 클래스를 정의하는데 사용된다.

데이터 클래스는 시스템에 존재하는 WMI 데이터나 레지스트리 키를 기반으로 생성될 수 있다.

SMS_def.mof

이 파일은 하드웨어 인벤토리 에이전트에 의해 수집된 데이터 정보를 보고에 보여줄지 말지를 정의한다.

보고 클래스는 WMI 데이터 클래스를 기반으로 하며 기본적으로 제공되는 클래스나 Configuration.mof에서 사용자 정의를 통해 추가된 클래스가 될 수 있다.

SMS_def.mof 파일에 설정된 클래스 보고 정보는 클라이언트의 컴퓨터 정책 실행 간격 중에 보고 정책으로 변환된다. 클라이언트는 새로운 보고 정책을 컴파일 한 후 보고 정책 정보는 클라이언트의 WMI 저장소의 Root\CCM\Policy\Machine 네임스페이스, InventoryDataItem 클래스에 저장된다.

HKLM\SOFTWARE\Custom Value 키 하위로 다음과 같은 키가 있는 상황을 예로 들면

 


1. 먼저 Configuration.mof 파일에 다음과 같은 내용을 추가한다.

#pragma namespace("\\\\.\\root\\cimv2")

#pragma deleteclass("Win32Reg_CustomValue",NOFAIL)

[ dynamic,

provider("RegProv"),

ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Custom Value")

]

class Win32Reg_CustomValue

{

[Key] string ApplicationName;

[PropertyContext("ProductName")] string ProductName;

[PropertyContext("ProductFile")] string ProductFile;

[PropertyContext("ProductVer")] string ProductVer;

};

위 내용을 요약하면

- cimv2 네임스페이스에 있는 Win32Reg_CustomValue 클래스 제거

- HKEY_LOCAL_MACHINE\\SOFTWARE\\Custom Value에 대한 레지스트리 검색 프로바이더 정의

- Win32Reg_CustomValue 클래스 생성 및 값 설정

2. 다음으로 SMS_def.mof 파일에 다음과 같은 내용을 추가한다.

#pragma namespace ("\\\\.\\root\\cimv2\\sms")

#pragma deleteclass("Win32Reg_CustomValue",NOFAIL)

[ SMS_Report (TRUE),

SMS_Group_Name ("Custom Inventory")

SMS_Class_ID ("KWANGSEOK|CustomInventory|1.0") ]

class Win32Reg_CustomValue : SMS_Class_Template

{

[SMS_Report (TRUE), Key ] string ApplicationName;

[SMS_Report (TRUE)] string ProductName;

[SMS_Report (TRUE)] string ProductFile;

[SMS_Report (TRUE)] string ProductVer;

};

위 내용을 요약하면

- cimv2\sms 네임스페이스에 있는 Win32Reg_CustomValue 클래스 제거

- 보고 여부 설정 및 그룹 이름, 클래스 ID 설정

- Win32Reg_CustomValue 클래스 생성 및 값 입력

3. 위 과정이 완료된 후 컴퓨터 정책/하드웨어 인벤토리 실행이 끝나면

Resource Explorer > Hardware 하위에서 확인이 가능하다.

App-V의 모델
1. Standalone Model
시퀀싱 작업의 한 부분으로 .msi 패키지를 생성해 배포한다.(GPO, SCCM)
.msi 패키지 파일에는 배포 정보, 바로가기, 설치 루틴이 포함된다.

사용 환경
- App-V 환경에 접속할 수 없는 원격지 사용자가 있는 경우
- SMS 2003, SCCM 2007등 소프트웨어 관리 솔루션이 이미 있는 경우
- 소프트웨어를 배포하기 위한 대역폭이 충분하지 않은 경우

2. Streaming Model
응용 프로그램은 Feature Block을 통해 전송(Streaming)된다.
프로그램이 실행되는 데에는 Feature Block 1(FB1)만 필요하다.
이는 응용 프로그램의 빠른 실행을 가능하게 한다.

사용 환경
- 응용 프로그램의 배포에 SCCM 2007 SP1 with R2을 사용하는 경우
- Active Directory가 구성되어 있지 않은 상황에서 스트리밍을 이용해 배포하려 하는 경우

스트리밍 서버 역할 종류
- App-V Management Server or Streaming Server(Active upgrade) - RTSP/RTSPS
- File Server(No Active upgrade) - SMB
- IIS Server(No Active upgrade) - HTTP/HTTPS

3. Full Infrastructure Model
하나 이상의 App-V 관리 서버로 구성되며 SQL Server 데이터베이스가 필요하다.
App-V의 관리를 위해 관리 콘솔이 필요하다.(관리 서버에 설치하거나 별도의 워크스테이션에 설치한다.)

사용 환경
- 관리 서버를 이용해 응용 프로그램의 바로가기를 클라이언트에 배포하고자 하는 경우
- 관리서버의 추가적인 보고서 기능을 필요로 하는 경우
- 그룹 기반의 응용 프로그램 배포가 필요한 경우
- 라이선스 관리가 필요한 경우
- 응용 프로그램을 클라이언트로 신속하게 배포하고자 하는 경우

구성 역할
- App-V Management Server
- Streaming Server
- Server running App-V Management Web Service
- SQL Server
- Active Directory
- App-V Management Console
- Sequencer for creating virtualized application packages
- App-V Client installed on systems requiring app virtualization (desktops, VMs, or Terminal Servers)

고가용성 구성
- SQL Server (MSCS) - SQL Server 2000(SP3a/SP4), SQL Server 2005(SP1/SP2), SQL Server 2008
- Streaming Server(Network Load-Balancing)
- Management Server(Network Load-Balancing)
- Management Server Service(N/A)

-       The requested operation cannot be performed on a file with a user-mapped section open. (0x800704C8)

-       'VMName' Microsoft Synthetic Ethernet Port (Instance ID {7E0DA81A-A7B4-4DFD-869F-37002C36D816}): Failed to Power On with Error 'The specified network resource or device is no longer available.' (0x80070037)

-       The I/O operation has been aborted because of either a thread exit or an application request. (0x800703E3)

-       Virtual machines disappear from the Hyper-V Management Console

부모 파티션에 백신 프로그램이 설치되어 있는 경우 위와 같은 증상이 발생할 수 있다.

해결 방법

백신 설정에서 다음 사항에 대해 예외 설정

-       Default virtual machine configuration directory (C:\ProgramData\Microsoft\Windows\Hyper-V)

-       Custom virtual machine configuration directories

-       Default virtual hard disk directory (C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks)

-       Custom virtual hard disk directories

-       Snapshot directories

-       Vmms.exe

-       Vmwp.exe

– Find all managed servers that are down and not pingable
SELECT bme.DisplayName, s.LastModified
FROM state AS s, BaseManagedEntity AS bme
WHERE s.basemanagedentityid = bme.basemanagedentityid AND s.monitorid
IN (SELECT MonitorId FROM Monitor WHERE MonitorName = ‘Microsoft.SystemCenter.HealthService.ComputerDown’)
AND s.Healthstate = ‘3′
ORDER BY s.Lastmodified DESC

– Operational Database Version
SELECT DBVersion FROM __MOMManagementGroupInfo__

– Find a computer name from it’s Health Service ID (guid from agent proxy alerts)
SELECT id, path, fullname, displayname FROM ManagedEntityGenericView WHERE ID = ‘<GUID>’

– ALERTS SECTION –
——————–

– Most common alerts, by alert count
SELECT AlertStringName, AlertStringDescription, AlertParams, Name, SUM(1) AS AlertCount, SUM(RepeatCount+1) AS AlertCountWithRepeatCount
FROM Alertview WITH (NOLOCK)
WHERE ResolutionState = (0|255)
GROUP BY AlertStringName, AlertStringDescription, AlertParams, Name
ORDER BY AlertCount DESC

– TOP 10 common alerts
SELECT Top(10) AlertStringName, AlertStringDescription, AlertParams, Name, SUM(1) AS AlertCount, SUM(RepeatCount+1) AS AlertCountWithRepeatCount
FROM Alertview WITH (NOLOCK)
WHERE ResolutionState = (0|255)
GROUP BY AlertStringName, AlertStringDescription, AlertParams, Name
ORDER BY AlertCount DESC

– Most common alerts, by repeat count
SELECT AlertStringName, AlertStringDescription, AlertParams, Name, SUM(1) AS AlertCount, SUM(RepeatCount+1) AS AlertCountWithRepeatCount
FROM Alertview WITH (NOLOCK)
WHERE ResolutionState = (0|255)
GROUP BY AlertStringName, AlertStringDescription, AlertParams, Name
ORDER BY AlertCountWithRepeatCount DESC

– Number of alerts per day
SELECT CONVERT(VARCHAR(20), TimeAdded, 101) AS DayAdded, COUNT(*) AS NumAlertsPerDay
FROM Alert WITH (NOLOCK)
GROUP BY CONVERT(VARCHAR(20), TimeAdded, 101)
ORDER BY DayAdded DESC

– Number of alerts per day by resolution state
SELECT
CASE WHEN(GROUPING(CONVERT(VARCHAR(20), TimeAdded, 101)) = 1) THEN ‘All Days’ ELSE CONVERT(VARCHAR(20), TimeAdded, 101) END AS [Date],
CASE WHEN(GROUPING(ResolutionState) = 1) THEN ‘All Resolution States’ ELSE CAST(ResolutionState AS VARCHAR(5)) END AS [ResolutionState],
COUNT(*) AS NumAlerts
FROM Alert WITH (NOLOCK)
GROUP BY CONVERT(VARCHAR(20), TimeAdded, 101), ResolutionState WITH ROLLUP
ORDER BY DATE DESC

– EVENTS SECTION –
——————–

– Most common events by day by count
SELECT CASE WHEN(GROUPING(CONVERT(VARCHAR(20), TimeAdded, 101)) = 1)
THEN ‘All Days’
ELSE CONVERT(VARCHAR(20), TimeAdded, 101) END AS DayAdded,
COUNT(*) AS NumEventsPerDay
FROM EventAllView
GROUP BY CONVERT(VARCHAR(20), TimeAdded, 101) WITH ROLLUP
ORDER BY DayAdded DESC

– Most common events by event number
SELECT Number, COUNT(*) AS "Number of Events"
FROM EventView
GROUP BY Number
ORDER BY "Number of Events" DESC

– PERFORMANCE SECTION –
————————-

– Performance Insertions per day
SELECT CASE WHEN(GROUPING(CONVERT(VARCHAR(20), TimeSampled, 101)) = 1)
THEN ‘All Days’ ELSE CONVERT(VARCHAR(20), TimeSampled, 101)
END AS DaySampled, COUNT(*) AS NumPerfPerDay
FROM PerformanceDataAllView
GROUP BY CONVERT(VARCHAR(20), TimeSampled, 101) WITH ROLLUP
ORDER BY DaySampled DESC

– Most common performance insertions by perf object and counter name:
SELECT pcv.objectname, pcv.countername, count (pcv.countername) AS total FROM performancedataallview AS pdv, performancecounterview AS pcv
WHERE (pdv.performancesourceinternalid = pcv.performancesourceinternalid)
GROUP BY pcv.objectname, pcv.countername
ORDER BY count (pcv.countername) DESC

– Most common performance insertions by perf object name:
SELECT pcv.objectname, count (pcv.countername) AS total FROM performancedataallview AS pdv, performancecounterview AS pcv
WHERE (pdv.performancesourceinternalid = pcv.performancesourceinternalid)
GROUP BY pcv.objectname
ORDER BY count (pcv.countername) DESC

– Most common performance insertions by perf counter name:
SELECT pcv.countername, count (pcv.countername) AS total FROM performancedataallview AS pdv, performancecounterview AS pcv
WHERE (pdv.performancesourceinternalid = pcv.performancesourceinternalid)
GROUP BY pcv.countername
ORDER BY count (pcv.countername) DESC

– STATE SECTION –
——————-

– State changes per day:
SELECT CASE WHEN(GROUPING(CONVERT(VARCHAR(20), TimeGenerated, 101)) = 1)
THEN ‘All Days’ ELSE CONVERT(VARCHAR(20), TimeGenerated, 101)
END AS DayGenerated, COUNT(*) AS NumEventsPerDay
FROM StateChangeEvent WITH (NOLOCK)
GROUP BY CONVERT(VARCHAR(20), TimeGenerated, 101) WITH ROLLUP
ORDER BY DayGenerated DESC

– MANAGEMENT PACK INFO –
————————–

– To find all installed Management Packs and their version:
SELECT MPName, MPFriendlyName, MPVersion, MPIsSealed
FROM ManagementPack WITH(NOLOCK)
ORDER BY MPName

– Rules per MP:
SELECT mp.MPName, COUNT(*) AS RulesPerMP
FROM Rules r
INNER JOIN ManagementPack mp ON mp.ManagementPackID = r.ManagementPackID
GROUP BY mp.MPName
ORDER BY RulesPerMP DESC

– Rules per MP by category:
SELECT mp.MPName, r.RuleCategory, COUNT(*) AS RulesPerMPPerCategory
FROM Rules r
INNER JOIN ManagementPack mp ON mp.ManagementPackID = r.ManagementPackID
GROUP BY mp.MPName, r.RuleCategory
ORDER BY RulesPerMPPerCategory DESC

– Monitors Per MP:
SELECT mp.MPName, COUNT(*) AS MonitorsPerMPPerCategory
FROM Monitor m
INNER JOIN ManagementPack mp ON mp.ManagementPackID = m.ManagementPackID
GROUP BY mp.MPName
ORDER BY COUNT(*) DESC

– To find your Monitor by common name:
SELECT * FROM Monitor
INNER JOIN LocalizedText LT ON LT.ElementName = Monitor.MonitorName
WHERE LTValue = ‘My Monitor Name’

– To find all Rules per MP that generate an alert:
declare @mpid AS varchar(50)
SELECT @mpid= managementpackid FROM managementpack WHERE
mpName=‘Microsoft.BizTalk.Server.2006.Monitoring’
SELECT rl.rulename,rl.ruleid,md.modulename FROM rules rl, module md
WHERE md.managementpackid = @mpid
AND rl.ruleid=md.parentid
AND moduleconfiguration LIKE ‘%<AlertLevel>50</AlertLevel>%’

– To find all rules per MP with a given alert severity:
declare @mpid AS varchar(50)
SELECT @mpid= managementpackid FROM managementpack WHERE
mpName=‘Microsoft.BizTalk.Server.2006.Monitoring’
SELECT rl.rulename,rl.ruleid,md.modulename FROM rules rl, module md
WHERE md.managementpackid = @mpid
AND rl.ruleid=md.parentid
AND moduleconfiguration LIKE ‘%<Severity>2</Severity>%’

– Number of instances of a type:  (Number of disks, computers, databases, etc that OpsMgr has discovered)
SELECT mt.ManagedTypeID, mt.TypeName, COUNT(*) AS NumEntitiesByType
FROM BaseManagedEntity bme WITH(NOLOCK)
LEFT JOIN ManagedType mt WITH(NOLOCK) ON mt.ManagedTypeID = bme.BaseManagedTypeID
WHERE bme.IsDeleted = 0
GROUP BY mt.ManagedTypeID, mt.TypeName
ORDER BY COUNT(*) DESC

– Number of Views per Management Pack:
SELECT mp.MPName, v.ViewVisible, COUNT(*) AS ViewsPerMP
FROM [Views] v
INNER JOIN ManagementPack mp ON mp.ManagementPackID = v.ManagementPackID
GROUP BY  mp.MPName, v.ViewVisible
ORDER BY v.ViewVisible DESC, COUNT(*) DESC

– Grooming:
SELECT * FROM PartitionAndGroomingSettings WITH (NOLOCK)

– All managed computers count:
SELECT COUNT(*) AS NumManagedComps FROM (
SELECT bme2.BaseManagedEntityID
FROM BaseManagedEntity bme WITH (NOLOCK)
INNER JOIN BaseManagedEntity bme2 WITH (NOLOCK) ON bme2.BaseManagedEntityID = bme.TopLevelHostEntityID
WHERE bme2.IsDeleted = 0
AND bme2.IsDeleted = 0
AND bme2.BaseManagedTypeID = (SELECT TOP 1 ManagedTypeID FROM ManagedType WHERE TypeName = ‘microsoft.windows.computer’)
GROUP BY bme2.BaseManagedEntityID
) AS Comps

– Classes available in the DB:
SELECT * FROM ManagedType

– Classes available in the DB for Microsoft Windows type:
SELECT * FROM ManagedType
WHERE TypeName LIKE ‘Microsoft.Windows.%’

– Every property of every class:
SELECT * FROM MT_Computer

– All instances of all types once discovered
SELECT * FROM BaseManagedEntity

– To get the state of every instance of a particular monitor the following query can be run, (replace <MonitorName> with the name of the monitor):
SELECT bme.FullName, bme.DisplayName, s.HealthState FROM state AS s, BaseManagedEntity AS bme
WHERE s.basemanagedentityid = bme.basemanagedentityid
AND s.monitorid IN (SELECT MonitorId FROM Monitor WHERE MonitorName = ‘<MonitorName>’)

– For example, this gets the state of the Microsoft.SQLServer.2005.DBEngine.ServiceMonitor for each instance of the SQL 2005 Database Engine class.
SELECT bme.FullName, bme.DisplayName, s.HealthState
FROM state AS s, BaseManagedEntity AS bme
WHERE s.basemanagedentityid = bme.basemanagedentityid
AND s.monitorid IN (SELECT MonitorId FROM Monitor WHERE MonitorName = ‘Microsoft.SQLServer.2005.DBEngine.ServiceMonitor’)

– To find the overall state of any object in OpsMgr the following query should be used to return the state of the System.EntityState monitor:
SELECT bme.FullName, bme.DisplayName, s.HealthState
FROM state AS s, mt_managedcomputer AS mt, BaseManagedEntity AS bme
WHERE s.basemanagedentityid = bme.basemanagedentityid
AND s.monitorid IN (SELECT MonitorId FROM Monitor WHERE MonitorName = ‘System.Health.EntityState’)

– Rules are stored in a table named Rules. This table has columns linking rules to classes and Management Packs.
– To find all rules in a Management Pack use the following query and substitute in the required Management Pack name:
SELECT * FROM Rules WHERE ManagementPackID = (SELECT ManagementPackID FROM ManagementPack WHERE MPName = ‘Microsoft.Windows.Server.2003′)

– To find all rules targeted at a given class use the following query and substitute in the required class name:
SELECT * FROM Rules WHERE TargetManagedEntityType = (SELECT ManagedTypeId FROM ManagedType WHERE TypeName = ‘Microsoft.Windows.Computer’)

– The Alert table contains all alerts currently open in OpsMgr. This includes resolved alerts until they are groomed out of the database. To get all alerts across all instances of a given monitor use the following query and substitute in the required monitor name:

SELECT * FROM Alert WHERE ProblemID IN (SELECT MonitorId FROM Monitor WHERE MonitorName = ‘Microsoft.SQLServer.2005.DBEngine.ServiceMonitor’)

– To retrieve all alerts for all instances of a specific class use the following query and substitute in the required table name, in this example MT_DBEngine is used to look for SQL alerts:
SELECT * FROM Alert WHERE BaseManagedEntityID IN (SELECT BaseManagedEntityID FROM MT_DBEngine)

– To determine which table is currently being written to for event and performance data use the following query:
SELECT * FROM PartitionTables WHERE IsCurrent = 1

– To retrieve events generated by a specific rule use the following query and substitute in the required rule ID:
SELECT * FROM Event_00 WHERE RuleId = (SELECT RuleId FROM Rules WHERE RuleName = ‘Microsoft.Windows.Server.2003.OperatingSystem.CleanShutdown.Collection ‘)

– To retrieve all events generated by rules in a specific Management Pack the following query can be used where the Management Pack name is substituted with the required value:
SELECT * FROM EventAllView
WHERE RuleID IN (SELECT RuleId FROM Rules WHERE ManagementPackId =
(SELECT ManagementPackId FROM ManagementPack WHERE MPName = ‘Microsoft.Windows.Server.2003′))

– To retrieve all performance data for a given rule in a readable format use the following query:
SELECT pc.ObjectName, pc.CounterName, ps.PerfmonInstanceName, pd.SampleValue, pd.TimeSampled
FROM PerformanceDataAllView AS pd, PerformanceCounter AS pc, PerformanceSource AS ps
WHERE pd.PerformanceSourceInternalId IN (SELECT PerformanceSourceInternalId FROM PerformanceSource
WHERE RuleId = (SELECT RuleId FROM Rules WHERE RuleName =‘ Microsoft.Windows.Server.2003.LogicalDisk.FreeSpace.Collection’))

– Information on existing User Roles:
SELECT UserRoleName, IsSystem FROM userrole

– Grooming in the DataWarehouse:
– Grooming no longer uses SQL agent jobs.  Grooming is handled by scheduled stored procedures, that run much more frequently, which provides less impact than in the previous version.
– Default grooming for the DW for each dataset, to examine Data Warehouse grooming settings:
SELECT AggregationIntervalDurationMinutes, BuildAggregationStoredProcedureName, GroomStoredProcedureName, MaxDataAgeDays, GroomingIntervalMinutes FROM StandardDatasetAggregation

– The first row is the interval in minutes.
– NULL is raw data, 60 is hourly, and 1440 is daily.
– The second and third row shows what data it is
– MaxDataAgeDays has the retention period in days - this is the field to update if the administrator wants to lower the days of retention.
– RAW alert – 400 days
– RAW event – 100 days
– RAW perf – 10 days (hourly and daily perf = 400 days)
– RAW state – 180 days  (hourly and daily state = 400 days)

– AEM Queries (Data Warehouse):

– Default query to return all RAW AEM data:
SELECT * FROM [CM].[vCMAemRaw] Rw
INNER JOIN dbo.AemComputer Computer ON Computer.AemComputerRowID = Rw.AemComputerRowID
INNER JOIN dbo.AemUser Usr ON Usr.AemUserRowId = Rw.AemUserRowId
INNER JOIN dbo.AemErrorGroup EGrp ON Egrp.ErrorGroupRowId = Rw.ErrorGroupRowId
INNER JOIN dbo.AemApplication App ON App.ApplicationRowId = Egrp.ApplicationRowId

– Count the raw crashes per day:
SELECT CONVERT(char(10), DateTime, 101) AS "Crash Date (by Day)", COUNT(*) AS "Number of Crashes"
FROM [CM].[vCMAemRaw]
GROUP BY CONVERT(char(10), DateTime, 101)
ORDER BY "Crash Date (by Day)" DESC

– Count the total number of raw crashes in the DW database:
SELECT count(*) FROM CM.vCMAemRaw

– Default grooming for the DW for the AEM dataset:  (Aggregated data kept for 400 days, RAW 30 days by default)
SELECT AggregationTypeID, BuildAggregationStoredProcedureName, GroomStoredProcedureName, MaxDataAgeDays, GroomingIntervalMinutes
FROM StandardDatasetAggregation WHERE BuildAggregationStoredProcedureName = ‘AemAggregate’

– MISCELLANEOUS SECTION –
—————————

– Simple query to display large tables, to determine what is taking up space in the database:
SELECT so.name,
8 * Sum(CASE WHEN si.indid IN (0, 1) THEN si.reserved END) AS data_kb,
Coalesce(8 * Sum(CASE WHEN si.indid NOT IN (0, 1, 255) THEN si.reserved END), 0) AS index_kb,
Coalesce(8 * Sum(CASE WHEN si.indid IN (255) THEN si.reserved END), 0) AS blob_kb
FROM dbo.sysobjects AS so JOIN dbo.sysindexes AS si ON (si.id = so.id)
WHERE ‘U’ = so.type GROUP BY so.name  ORDER BY data_kb DESC

– Is SQL broker enabled?
SELECT is_broker_enabled FROM sys.DATABASES WHERE name = ‘OperationsManager’

– How to identify your version of SQL server:
SELECT  SERVERPROPERTY(‘productversion’), SERVERPROPERTY (‘productlevel’), SERVERPROPERTY (‘edition’)

– SQL 2005:
– SQL Server 2005 RTM                    2005.90.1399
– SQL Server 2005 SP1                     2005.90.2047
– SQL Server 2005 SP1 plus 918222  2005.90.2153
– SQL Server 2005 SP2                     2005.90.3042

Windows 2003

클라이언트 로그 위치
32bit : %WINDIR%\System32\CCM\Logs
64bit : %WINDIR%\SysWOW64\CCM\Logs

서버 로그 위치
Server Log : <INSTALL_PATH>\Logs
Site Role Log : %ProgramFiles%\SMS_CCM\Logs

SCCM Toolkit을 이용해서 분석하면 좀 더 쉽게 분석이 가능하다.

-클라이언트 로그 파일-
CAS - Content Access Service. Maintains the local package cache.
Ccmexec.log - Records activities of the client and the SMS Agent Host service.
CertificateMaintenance.log - Maintains certificates for Active Directory directory service and management points.
ClientIDManagerStartup.log - Creates and maintains the client GUID.
ClientLocation.log - Site assignment tasks.
ContentTransferManager.log - Schedules the Background Intelligent Transfer Service (BITS) or the Server Message Block (SMB) to download or to access SMS packages.
DataTransferService.log - Records all BITS communication for policy or package access.
Execmgr.log - Records advertisements that run.
FileBITS.log - Records all SMB package access tasks.
Fsinvprovider.log (renamed to FileSystemFile.log in all SMS 2003 Service Packs) - Windows Management Instrumentation (WMI) provider for software inventory and file collection.
InventoryAgent.log - Creates discovery data records (DDRs) and hardware and software inventory records.
LocationServices.log - Finds management points and distribution points.
Mifprovider.log - The WMI provider for .MIF files.
Mtrmgr.log - Monitors all software metering processes.
PolicyAgent.log - Requests policies by using the Data Transfer service.
PolicyAgentProvider.log - Records policy changes.
PolicyEvaluator.log - Records new policy settings.
Remctrl.log - Logs when the remote control component (WUSER32) starts.
Scheduler.log - Records schedule tasks for all client operations.
Smscliui.log - Records usage of the Systems Management tool in Control Panel.
StatusAgent.log - Logs status messages that are created by the client components.
SWMTRReportGen.log - Generates a usage data report that is collected by the metering agent. (This data is logged in Mtrmgr.log.)

-서버 로그 파일-
Ccm.log - Client Configuration Manager tasks.
Cidm.log - Records changes to the client settings by the Client Install Data Manager (CIDM).
Colleval.log - Logs when collections are created, changed, and deleted by the Collection Evaluator.
Compsumm.log - Records Component Status Summarizer tasks.
Cscnfsvc.log - Records Courier Sender confirmation service tasks.
Dataldr.log - Processes Management Information Format (MIF) files and hardware inventory in the Configuration Manager 2007 database.
Ddm.log - Saves DDR information to the Configuration Manager 2007 database by the Discovery Data Manager.
Despool.log - Records incoming site-to-site communication transfers.
Distmgr.log - Records package creation, compression, delta replication, and information updates.
Hman.log - Records site configuration changes, and publishes site information in Active Directory Domain Services.
Inboxast.log - Records files that are moved from the management point to the corresponding SMS\INBOXES folder.
Inboxmgr.log - Records file maintenance.
Invproc.log - Records the processing of delta MIF files for the Dataloader component from client inventory files.
Mpcontrol.log - Records the registration of the management point with WINS. Records the availability of the management point every 10 minutes.
Mpfdm.log - Management point component that moves client files to the corresponding SMS\INBOXES folder.
MPMSI.log - Management point .msi installation log.
MPSetup.log - Records the management point installation wrapper process.
Ntsvrdis.log - Configuration Manager 2007 server discovery.
Offermgr.log - Records advertisement updates.
Offersum.log - Records summarization of advertisement status messages.
Policypv.log - Records updates to the client policies to reflect changes to client settings or advertisements.
Replmgr.log - Records the replication of files between the site server components and the Scheduler component.
Rsetup.log - Reporting point setup log.
Sched.log - Records site-to-site job and package replication.
Sender.log - Records files that are sent to other child and parent sites.
Sinvproc.log - Records client software inventory data processing to the site database in Microsoft SQL Server.
Sitecomp.log - Records maintenance of the installed site components.
Sitectrl.log - Records site setting changes to the Sitectrl.ct0 file.
Sitestat.log - Records the monitoring process of all site systems.
Smsdbmon.log - Records database changes.
Smsexec.log - Records processing of all site server component threads.
Smsprov.log - Records WMI provider access to the site database.
SMSReportingInstall.log - Records the Reporting Point installation. This component starts the installation tasks and processes configuration changes.
SMSSHVSetup.log - Records the success or failure (with failure reason) of installing the System Health Validator point.
Srvacct.log - Records the maintenance of accounts when the site uses standard security.
Statmgr.log - Writes all status messages to the database.
Swmproc.log - Processes metering files and maintains settings.

-관리 콘솔 로그 파일-
RepairWizard.log - Records errors, warnings, and information about the process of running the Repair Wizard.
ResourceExplorer.log - Records errors, warnings, and information about running the Resource Explorer.
SMSAdminUI.log - Records the local Configuration Manager 2007 console tasks when you connect to Configuration Manager 2007 sites.

-관리 포인트 로그 파일-
MP_Ddr.log - Records the conversion of XML.ddr records from clients, and copies them to the site server.
MP_GetAuth.log - Records the status of the site management points.
MP_GetPolicy.log - Records policy information.
MP_Hinv.log - Converts XML hardware inventory records from clients and copies the files to the site server.
MP_Location.log - Records location manager tasks.
MP_Policy.log - Records policy communication.
MP_Relay.log - Copies files that are collected from the client.
MP_Retry.log - Records the hardware inventory retry processes.
MP_Sinv.log - Converts XML hardware inventory records from clients and copies them to the site server.
MP_Status.log - Converts XML.svf status message files from clients and copies them to the site server.

-모바일 장치 관리 로그 파일-
DmClientHealth.log - Records the GUIDs of all the mobile device clients that are communicating with the Device Management Point.
DmClientRegistration.log - Records registration requests from and responses to the mobile device client in Native mode.
DmpDatastore.log - Records all the site database connections and queries made by the Device Management Point.
DmpDiscovery.log - Records all the discovery data from the mobile device clients on the Device Management Point.
DmpFileCollection.log - Records mobile device file collection data from mobile device clients on the Device Management Point.
DmpHardware.log - Records hardware inventory data from mobile device clients on the Device Management Point.
DmpIsapi.log - Records mobile device communication data from device clients on the Device Management Point.
dmpMSI.log - Records the MSI data for Device Management Point setup.
DMPSetup.log - Records the mobile device management setup process.
DmpSoftware.log - Records mobile device software distribution data from mobile device clients on the Device Management Point.
DmpStatus.log - Records mobile device status messages data from mobile device clients on the Device Management Point.
FspIsapi.log - Records Fallback Status Point communication data from mobile device clients and client computers on the Fallback Status Point.

-모바일 장비 클라이언트 로그 파일-
DmCertEnroll.log - Records certificate enrollment data on mobile device clients.
DMCertResp.htm (in \temp) - Records HTML response from the certificate server when the mobile device Enroller program requests a client authentication certificate on mobile device clients.
DmClientSetup.log - Records client setup data on mobile device clients.
DmClientXfer.log - Records client transfer data for Windows Mobile Device Center and ActiveSync deployments.
DmCommonInstaller.log - Records client transfer file installation for setting up mobile device client transfer files on client computers.
DmInstaller.log - Records whether DMInstaller correctly calls DmClientSetup and whether DmClientSetup exits with success or failure on mobile device clients.
DmInvExtension.log - Records Inventory Extension file installation for setting up Inventory Extension files on client computers.
DmSvc.log - Records mobile device management service data on mobile device clients.

-운영체제 배포 로그 파일-
CCMSetup.log - Provides information about client-based operating system actions.
CreateTSMedia.log - Provides information about task sequence media when it is created. This log is generated on the computer running the Configuration Manager 2007 administrator console.
DriverCatalog.log - Provides information about device drivers that have been imported into the driver catalog.
MP_ClientIDManager.log - Provides information about the Configuration Manager 2007 management point when it responds to Configuration Manager 2007 client ID requests from boot media or PXE. This log is generated on the Configuration Manager 2007 management point.
MP_DriverManager.log - Provides information about the Configuration Manager 2007 management point when it responds to a request from the Auto Apply Driver task sequence action. This log is generated on the Configuration Manager 2007 management point.
MP_Location.log - Provides information about the Configuration Manager 2007 management point when it responds to request state store or release state store requests from the state migration point. This log is generated on the Configuration Manager 2007 management point.
Pxecontrol.log - Provides information about the PXE Control Manager.
PXEMsi.log - Provides information about the PXE service point and is generated when the PXE service point site server has been created.
PXESetup.log - Provides information about the PXE service point and is generated when the PXE service point site server has been created.
Setupact.log Setupapi.log Setuperr.log Provide information about Windows Sysprep and setup logs.
SmpIsapi.log - Provides information about the state migration point Configuration Manager 2007 client request responses.
Smpmgr.log - Provides information about the results of state migration point health checks and configuration changes.
SmpMSI.log - Provides information about the state migration point and is generated when the state migration point site server has been created.
Smsprov.log - Provides information about the SMS provider.
Smspxe.log - Provides information about the Configuration Manager 2007 PXE service point.
SMSSMPSetup.log - Provides information about the state migration point and is generated when the state migration point site server has been created.
Smsts.log - General location for all operating system deployment and task sequence log events.
TaskSequenceProvider.log - Provides information about task sequences when they are imported, exported, or edited.
USMT Log loadstate.log - Provides information about the User State Migration Tool (USMT) regarding the restore of user state data.
USMT Log scanstate.log - Provides information about the USMT regarding the capture of user state data.

-네트워크 접근 보호(NAP) 로그 파일-
Ccmcca.log - Logs the processing of compliance evaluation based on Configuration Manager NAP policy processing and contains the processing of remediation for each software update required for compliance.
CIAgent.log - Tracks the process of remediation and compliance. However, the software updates log file, *Updateshandler.log - provides more informative details on installing the software updates required for compliance.
locationservices.log - Used by other Configuration Manager features (for example, information about the client’s assigned site) but also contains information specific to Network Access Protection when the client is in remediation. It records the names of the required remediation servers (management point, software update point, and distribution points that host content required for compliance), which are also sent in the client statement of health.
SDMAgent.log - Shared with the Configuration Manager feature desired configuration management and contains the tracking process of remediation and compliance. However, the software updates log file, Updateshandler.log, provides more informative details about installing the software updates required for compliance.
SMSSha.log - The main log file for the Configuration Manager Network Access Protection client and contains a merged statement of health information from the two Configuration Manager components: location services (LS) and the configuration compliance agent (CCA). This log file also contains information about the interactions between the Configuration Manager System Health Agent and the operating system NAP agent, and also between the Configuration Manager System Health Agent and both the configuration compliance agent and the location services. It provides information about whether the NAP agent successfully initialized, the statement of health data, and the statement of health response.

-시스템 상태 검사 포인트 로그 파일-
Ccmperf.log -Contains information about the initialization of the System Health Validator point performance counters.
SmsSHV.log - The main log file for the System Health Validator point; logs the basic operations of the System Health Validator service, such as the initialization progress.
SmsSHVADCacheClient.log - Contains information about retrieving Configuration Manager health state references from Active Directory Domain Services.
SmsSHVCacheStore.log - Contains information about the cache store used to hold the Configuration Manager NAP health state references retrieved from Active Directory Domain Services, such as reading from the store and purging entries from the local cache store file. The cache store is not configurable.
SmsSHVRegistrySettings.log - Records any dynamic changes to the System Health Validator component configuration while the service is running.
SmsSHVQuarValidator.log - Records client statement of health information and processing operations. To obtain full information, change the registry key LogLevel from 1 to 0 in the following location:HKLM\SOFTWARE\Microsoft\SMSSHV\Logging\@GLOBAL

-DCM(Desired Configuration Management) 로그 파일-
ciagent.log - Provides information about downloading, storing, and accessing assigned configuration baselines.
dcmagent.log - Provides high-level information about the evaluation of assigned configuration baselines and desired configuration management processes.
discovery.log - Provides detailed information about the Service Modeling Language (SML) processes.
sdmagent.log - Provides information about downloading, storing, and accessing configuration item content.
sdmdiscagent.log - Provides high-level information about the evaluation process for the objects and settings configured in the referenced configuration items.

-Wake On LAN(WOL) 로그 파일-
Wolmgr.log - Contains information about wake-up procedures such as when to wake up advertisements or deployments that are configured for Wake On LAN.
WolCmgr.log - Contains information about which clients need to be sent wake-up packets, the number of wake-up packets sent, and the number of wake-up packets retried.

-소프트웨어 업데이트 서버 로그 파일-
ciamgr.log - Provides information about the addition, deletion, and modification of software update configuration items.
distmgr.log - Provides information about the replication of software update deployment packages.
objreplmgr.log - Provides information about the replication of software updates notification files from a parent to child sites.
PatchDownloader.log - Provides information about the process for downloading software updates from the update source specified in the software updates metadata to the download destination on the site server.
replmgr.log - Provides information about the process for replicating files between sites.
smsdbmon.log - Provides information about when software update configuration items are inserted, updated, or deleted from the site server database and creates notification files for software updates components.
SUPSetup - Provides information about the software update point installation. When the software update point installation completes, Installation was successful is written to this log file.
WCM.log - Provides information about the software update point configuration and connecting to the Windows Server Update Services (WSUS) server for subscribed update categories, classifications, and languages.
WSUSCtrl.log - Provides information about the configuration, database connectivity, and health of the WSUS server for the site.
wsyncmgr.log -Provides information about the software updates synchronization process.

-WSUS 서버 로그 파일-
Change.log - Provides information about the WSUS server database information that has changed.
SoftwareDistribution.log - Provides information about the software updates that are synchronized from the configured update source to the WSUS server database.

-소프트웨어 업데이트 클라이언트 컴퓨터 로그 파일-
CAS.log - Provides information about the process of downloading software updates to the local cache and cache management.
CIAgent.log - Provides information about processing configuration items, including software updates.
LocationServices.log - Provides information about the location of the WSUS server when a scan is initiated on the client.
PatchDownloader.log - Provides information about the process for downloading software updates from the update source to the download destination on the site server. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.
PolicyAgent.log - Provides information about the process for downloading, compiling, and deleting policies on client computers.
PolicyEvaluator - Provides information about the process for evaluating policies on client computers, including policies from software updates.
RebootCoordinator.log - Provides information about the process for coordinating system restarts on client computers after software update installations.
ScanAgent.log - Provides information about the scan requests for software updates, what tool is requested for the scan, the WSUS location, and so on.
ScanWrapper - Provides information about the prerequisite checks and the scan process initialization for the Inventory Tool for Microsoft Updates on Systems Management Server (SMS) 2003 clients.
SdmAgent.log - Provides information about the process for verifying and decompressing packages that contain configuration item information for software updates.
ServiceWindowManager.log - Provides information about the process for evaluating configured maintenance windows.
smscliUI.log - Provides information about the Configuration Manager Control Panel user interactions, such as initiating a Software Updates Scan Cycle from the Configuration Manager Properties dialog box, opening the Program Download Monitor, and so on.
SmsWusHandler - Provides information about the scan process for the Inventory Tool for Microsoft Updates on SMS 2003 client computers.
StateMessage.log - Provides information about when software updates state messages are created and sent to the management point.
UpdatesDeployment.log - Provides information about the deployment on the client, including software update activation, evaluation, and enforcement. Verbose logging shows additional information about the interaction with the client user interface.
UpdatesHandler.log - Provides information about software update compliance scanning and about the download and installation of software updates on the client.
UpdatesStore.log - Provides information about the compliance status for the software updates that were assessed during the compliance scan cycle.
WUAHandler.log - Provides information about when the Windows Update Agent on the client searches for software updates.
WUSSyncXML.log - Provides information about the Inventory Tool for the Microsoft Updates synchronization process. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.

-윈도우 업데이트 에이전트 로그 파일-
WindowsUpdate.log - Provides information about when the Windows Update Agent connects to the WSUS server and retrieves the software updates for compliance assessment and whether there are updates to the agent components.

Client Spy - 소프트웨어 배포, 인벤토리, 소프트웨어 미터링 트러블슈팅
Policy Spy - 정책 뷰어, 정책 관련 트러블슈팅
Trace32 - Configuration 서버/클라이언트의 로그 뷰어(분석)
Security Configuration Wizard Template for Configuration Manager 2007 - SCW Template
DCM Model Verification - Desired Configuration Management 검증 및 아이템 테스트
DCM Digest Conversion - SMS 2003에서 생성한 DCM을 SCCM 2007 용으로 변환

invalid-file

getProcessNUM.vbs
arguement => Process1.exe,Process2.exe,Process3.exe......

Object : Process
Counter : NumberOfProcess
Instance : $Data/Property[@Name='ProcessName']$
Value : $Data/Property[@Name='PerfValue']$

--------------------------------------------------------------------------------------------------

strProcess = Split(oArgs.Item(0), ",")
For Each sProcess In strProcess
getProcessNUM(sProcess)
Next
oAPI.ReturnItems

Sub getProcessNUM(ProcessName)
Set cProcessResult = GetObject("winmgmts://./root/cimv2").ExecQuery("SELECT * FROM Win32_Process WHERE name = '" & ProcessName & "'")
perfValue= 0.0
perfValue= cdbl(cProcessResult.count)
Set propertyBag = oAPI.CreatePropertyBag()
propertyBag.AddValue "ProcessName", ProcessName
propertyBag.AddValue "PerfValue", PerfValue
oAPI.AddItem(propertyBag)
Call oAPI.Return(propertyBag)
Set cProcessResult = Nothing
End Sub