變更目前 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

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

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.

Problem
=========
Not receiving alerts as configured SQL job fails

Action Plan
========
1. Create new Rules

2. NT Event Log (Alert)

3. check [Select]

4. check [OK]

5.check [Next]

6. check [Next]

7.check [Next]

8. check [Create]

Alert
===========

PROBLEM:
==========
SRS Server Validation error when installing OpsMgr Reporting


CAUSE:
========== 
Proxy issue

RESOLUTION:
==========
1.Checked the Internet Options > Connections > LAN Settings > and found that all requests were configure to go thru proxy.

2.Cchecked the box for Bypass proxy for local addresses and saved the changes



3.Running the setup now completed the installation successfully.

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