SCCM versions

	RTM	CU1	CU2	CU3	CU4	CU5
CM07 SP2	4.0.6487.2000
CM12 RTM	5.0.7711.0000	5.0.7711.0200	5.0.7711.301
CM12 SP1	5.0.7804.1000	5.0.7804.1202	5.0.7804.1300	5.0.7804.1400	5.0.7804.1500	5.0.7804.1600
CM12 R2	5.0.7958.1000	5.0.7958.1203	5.0.7958.1303	5.0.7958.1401	5.0.7958.1501	5.0.7958.1604
CM12 SP2/R2 SP1	5.0.8239.1000	5.0.8239.1203
CM16
CU KBs
CM12 RTM		KB2717295	KB2780664
CM12 SP1		KB2817245	KB2854009	KB2882125	KB2922875	KB2978017
CM12 R2		KB2938441	KB2970177	KB2994331	KB3026739	KB3054451
CM12 SP2/R2 SP1		KB3074857

SQL Server 2008 R2 SP2升級到SP3 失敗

[請您參考以下的說明]   

1.       現階段暫時使用其他具有管理員權限的帳號登入後，已經可以正常安裝相關更新。

2.       針對Kerberos Token大小的問題建議可以透過底下方式將大小調整成48000以減少此類問題發生。

步驟：

1)      打開regedit.exe

2)      找到HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\Kerberos\Parameters , 並在右邊新增一個DWORD值 , 命名為 MaxTokenSize , 並設定其值為48000 (十進位)。

3)      設定完成後重新開機讓該值生效即可

KDC event ID 27 on Windows 2003 DC

You can also perform the following step to solve the problem on windows 2003 DC by adding the registry DWORD “KdcUseREquestedEtypesForTickets” under registry seeting

Hkey_local_Machine\System\CurrentControlSet\Services\KDC

Value Name : KdcUseREquestedEtypesForTickets
Value Type:  DWORD 
Value Data:  1 

Can not found APM Services after install scom agent ?

APM Server 需要檢查下面資訊，才會安裝APM

1. HKCR" Key="CLSID\{BBC3C76B-A765-4BC1-8150-4A20B24325B4

2. NETFRAMEWORK35 OR NET_VERSION_4_0

可以檢查安裝log

msiexec.exe /i C:\TEMP\MOMAgent.msi /qn /l*v C:\TEMP\MOMAgentinstall.log

DisableFirewall

reg add HKLM\SOFTWARE\Policies\Microsoft\WindowsFirewall\DomainProfile /v EnableFirewall /t REG_DWORD /d 0 /f

reg add HKLM\SOFTWARE\Policies\Microsoft\WindowsFirewall\StandardProfile /v EnableFirewall /t REG_DWORD /d 0 /f

reg add HKLM\SOFTWARE\Policies\Microsoft\WindowsFirewall\PrivateProfile /v EnableFirewall /t REG_DWORD /d 0 /f

reg add HKLM\SOFTWARE\Policies\Microsoft\WindowsFirewall\PublicProfile /v EnableFirewall /t REG_DWORD /d 0 /f

net stop MpsSvc

net start MpsSvc

SCOM - Email notification may not work as expected if a time range is configured only with an exclusion

When using Systems Center Operations Manager , if you configure Notification Recipients  or Subscribers with the option of "Only send notification during the specified times" and you configure it with only an exclude range (like "Except from" with a time range of, say 1:00am to 7:00am for example), email notifications fail altogether.

In the Operations Manager event log you will also see the event below:
Log Name:      Operations Manager
Source:        Health Service Modules
Date:          <date> <time>
Event ID:      31501
Task Category: Notification
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      <RMS Server Name>
Description:
No primary recipients were specified for the notification or all recipients are unavailable according to the schedules. Notification will not be sent
One or more workflows were affected by this. 
Instance name: Alert Notification Subscription Server
Management group: <Mgmt Group Name>


So to keep this from happening, or to fix it if you’ve already found yourself in this situation, you need to configure the Recipient or Subscriber first with an included time range, then configure your excluded time range.

For example, first configure you include Range like Date  | Range = Always | Time Range = All Day | Weekdays = Week days. then once you have that, configure your Exclude Range like Data Range = Always | Time Range = Excluding 1:00am to 7:00am | Weekdays = Week Days. The screen shot below shows this configuration.

Rebuild the performance counters on Windows Server 2008

1. Open Elevated Command prompt on Server

2. Navigate to C:\Windows\System32

3. Run the command lodctr.exe /S:Backup_Perfcounter.INI    

4. This command is to take a backup of the current performance counters
    on the server

5. After the backup is taken please verify if the file “Backup_perfcounter.INI”
    is available in C:\Windows\System32 on the server

6. Once confirmed, please run the following command
    to rebuild the performance counters      
    lodctr.exe /R:PerfStringBackup.INI    

7. Please reboot the server in order to make sure that
     all the registry changes are implemented.