Problem
=========
Windows 2003/Event 3083 window search Mapi2Handler.1 cannot be loaded
EventID:3083
Category: Gatherer
Description:The protocol handler Search.Mapi2Handler.1 cannot be loaded. Error
description: Class not registered
Desktop Search Version 4

Analyze
========
The background on this issue is that there are two processes that can index on 64-bit machines. One process is 64-bit and can load 64-bit protocol handlers and the other is a 32-bit process, which can load 32-bit protocol handlers. In this case, since mapi (which is used to index outlook email) is 32-bit only when the 64-bit protocol handler process starts it tries to load the 64-bit version of the non-existent mapi protocol handler. It should call into the WOW64-32 layer to determine that this handler is correctly registered in the other CLSID hive and not display the error. For some reason this check is not passing most likely due to some incompatible vista only flag we are using when calling to WOW64.32 bit applications use [HKEY_CLASSES_ROOT\Wow6432Node\CLSID64 bit applications use [HKEY_CLASSES_ROOT\CLSID


Solution
=======
Remove Windows Desktop Search or add the following registry entry

=====
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\CLSID\{9E175BAF-F52A-11D8-B9A5-505054503030}]
@="Windows Search Service Office Outlook Protocol Handler"
[HKEY_CLASSES_ROOT\CLSID\{9E175BAF-F52A-11D8-B9A5-505054503030}\InprocServer32]
@=hex(2):25,00,73,00,79,00,73,00,74,00,65,00,6d,00,72,00,6f,00,6f,00,74,00,25,\
  00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,73,00,\
  73,00,70,00,68,00,2e,00,64,00,6c,00,6c,00,00,00
"ThreadingModel"="Both"
[HKEY_CLASSES_ROOT\CLSID\{9E175BAF-F52A-11D8-B9A5-505054503030}\ProgID]
@="Search.MAPI2Handler.1"
[HKEY_CLASSES_ROOT\CLSID\{9E175BAF-F52A-11D8-B9A5-505054503030}\VersionIndependentProgID]
@="Search.MAPI2Handler"
=====

變更目前 SystemRoot Drive Letter 做法如下:

修改HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices內的  \DosDevices\D: 為\DosDevices\C:

修改以下幾個機碼:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

請您確認 Userinit 機碼.已經為 C:\WINDOWS\system32\userinit.exe,

修改以下幾個機碼:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion

PathName 及SystemRoot 已經為 C:\windows

檢視 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
每一個機碼內的 ProfileImagePath 已經為 C:\Usersusername or %SystemDrive%\Users\username

完成以上設定後.請您重新開機

Problem
=============
Discovered Windows 2000 network card names incorrect

Root Cause  
===========
By This is caused by the script where we use win32_NetworkAdapter class to get details about the network adapter, however this class doesn't have any field NetConnectionStatus on Windows 2000 servers although it does exist on the Windows 2003 servers.

Action Plan
===========
Please disable this Monitor

Please refer the following steps for firewall setting of IIS RPC:

1. RPC dynamic port range:

*這是 Windows Server 2008 和 Windows Vista 中的範圍。

2. Steps of setting RPC dynamic port:
You can view the dynamic port range on a computer that is running Windows Vista or Windows Server 2008 computer by using the following netsh commands:
netsh int ipv4 show dynamicport tcp

     You adjust this range by using the netsh command, as follows:

      netsh int <ipv4|ipv6> set dynamic <tcp|udp> start=number num=range

     This command sets the dynamic port range for TCP. The start port is number, and the total number of ports is range. The following are sample commands:
netsh int ipv4 set dynamicport tcp start=50000 num=1000

3. Steps of firewall (For Windows Server 2008 R2)

For Windows Server 2008
Here is the following command that helps you do this:

Type in the following where the range is specified in ( ) and the name of the firewall entry is in " ".

FOR /L %I IN (5000,1,5100) DO netsh firewall add  portopening TCP %I "RPC PORTS"%I

Each port in the range will be added with an "OK" confirmation.

In my case I wanted to add ports from 5000 - 5100.

We can add or delete both TCP and UDP ports, to do this we need to make a slight change in the above command:

instead of TCP we need to specify UDP and instead of "add" specify "delete" .
Ref:

=====

Windows Server 系統的服務概觀和網路連接埠需求

http://support.microsoft.com/kb/832017/zh-tw

How to configure RPC to use certain ports and how to help secure those ports by using IPsec

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

在 Windows Vista 和 Windows Server 2008 中，TCP/IP 的預設動態連接埠範圍已變更

http://support.microsoft.com/kb/929851/zh-tw

Symptom:

Windows 2003新增超過1000個以上的Schedule時,出現錯誤代碼:0x8007007a : 傳遞到系統呼叫的資料區太小.

Cause:

This happens when reach the limit of the number of tasks that can be registered with Task Scheduler 1.0 (which is about 1000 tasks)

Resolution:

it is a by design behavior. Using Server 2008 or 2008 R2 can overcome the design limitation of Task Scheduler 1.0

Q: Maximum number of tasks that can be scheduled?

A: About 1000

Q: Is this information documented?

A: Yes http://msdn.microsoft.com/en-us/library/bb756979.aspx

Q: Is there any way to increase this limit in Windows 2003?

A: No, since this is by design. Using Server 2008 or 2008 R2 can help since it uses Task Scheduler 2.0.

Workaround:

Combine multiple tasks into one batch file or script to avoid 1000 tasks limitation.