問題：
當使用Windows 7+ IE8在網路上下載某些檔案時，會出現以下視窗，如果不小心將「開啟這類型檔案之前，一定要先問我」取消，想讓它再出現的話，可以這樣做。
1.找到 HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\AttachmentExecute 機碼。
2.在此機碼的下方，會看到類似{0002DF01-0000-0000-C000-000000000046}的機碼，右方會看到文件的類型。如下圖，如果我的doc或是xls類型的檔案下載時不會出現「開啟這類型檔案之前，一定要先問我」的視窗，請將{0002DF01-0000-0000-C000-000000000046} 刪除。
3.開啟IE，再嘗試下載該類型的檔案，即會出現詢問視窗。
PROBLEM
========
Getting alerts which says “data warehouse failed to request a list of management packs”
Here is the event that triggers the monitor
Data Warehouse SQL RS Deployed Management Pack List Request State
The properties of the monitor show that it is triggering on these events.
<Configuration>
<ListSource>SQL RS Server</ListSource>
<FirstEventId>31569</FirstEventId>
<SecondEventId>31570</SecondEventId>
</Configuration>
CAUSE
========
MP was sending more information to the data warehouse.
RESOLUTION
============
We had temporarily disabled the rule but after removing the disable override we no longer had the issue.
1. This error is cause by the Error Event 31569 below, Event 31570 shows that this workflow is finally finished successfully.
2. This fault in fact does not impact any SCOM reporting functionalities, and now SCOM reporting is working fine.
3. This error event maybe cause by the network connection, RMS workload, IIS and SRS performance, however it can be recovered soon in one minute by data warehouse report deployment rule mechanism and all the report deployment jobs are finished successfully.
4. So we suggest, we can ignore this fault, while the SCOM reporting are working
問題描述︰SBS 2003/WINDOWS UPDATE無法正常更新
說明與方法︰
- 自動更新服務無法正常啟動, 手動去啟動服務會發生存取被拒
- 執行IE進行 Windows Update 則會發生 0x80070005的錯誤
- 手動安裝 AU Agent 在註冊DLL檔案發生 0x80070041D的錯誤
[Compare the windows update file]
good one: (from VM machine)
2009-11-18 10:17:25:171 536 408 Setup Update NOT required for C:\WINNT\system32\cdm.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-18 10:17:25:171 536 408 Setup Update NOT required for C:\WINNT\system32\wuapi.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-18 10:17:25:203 536 408 Setup Update NOT required for C:\WINNT\system32\wuapi.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-18 10:17:25:203 536 408 Setup Update NOT required for C:\WINNT\system32\wuauclt.exe: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-18 10:17:25:203 536 408 Setup Update NOT required for C:\WINNT\system32\wuaucpl.cpl: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-18 10:17:25:203 536 408 Setup Update NOT required for C:\WINNT\system32\wuaucpl.cpl.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-18 10:17:25:218 536 408 Setup Update NOT required for C:\WINNT\system32\wuaueng.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-18 10:17:25:218 536 408 Setup Update NOT required for C:\WINNT\system32\wuaueng.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-18 10:17:25:218 536 408 Setup Update NOT required for C:\WINNT\system32\wucltui.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-18 10:17:25:234 536 408 Setup Update NOT required for C:\WINNT\system32\wucltui.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-18 10:17:25:234 536 408 Setup Update NOT required for C:\WINNT\system32\wups.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-18 10:17:25:250 536 408 Setup Update NOT required for C:\WINNT\system32\wups2.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
bad one: (which is SBS 2003)
2009-11-13 08:43:26:218 12224 244c Setup Update NOT required for C:\WINDOWS\system32\cdm.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-13 08:43:26:218 12224 244c Setup Update NOT required for C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wuapi.dll\7.4.7600.226\wuapi.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-13 08:43:26:218 12224 244c Setup Update NOT required for C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wuapi.dll\7.4.7600.226\wuapi.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-13 08:43:26:218 12224 244c Setup Update NOT required for C:\WINDOWS\system32\wuauclt.exe: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-13 08:43:26:218 12224 244c Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-13 08:43:26:218 12224 244c Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-13 08:43:26:218 12224 244c Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-13 08:43:26:218 12224 244c Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-13 08:43:26:218 12224 244c Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-13 08:43:26:218 12224 244c Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-13 08:43:26:218 12224 244c Setup Update NOT required for C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wups.dll\7.4.7600.226\wups.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-13 08:43:26:234 12224 244c Setup Update NOT required for C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wups2.dll\7.4.7600.226\wups2.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
在更新 AU Agent的時候, wuapi.dll也沒正確被複製到正常的資料夾
[windowsupdate.log]
2009-11-13 08:41:18:578 8244 2d7c Setup Starting file operations for section cdm
2009-11-13 08:41:33:640 8244 2d7c Setup Successfully copied source file C:\WINDOWS\SoftwareDistribution\WebSetup\cdm.dll to C:\WINDOWS\system32\cdm.dll.wusetup.2406118265.new
2009-11-13 08:41:33:796 8244 2d7c Setup Setup successfullly moved C:\WINDOWS\system32\cdm.dll.wusetup.2406118265.new to C:\WINDOWS\system32\cdm.dll
2009-11-13 08:41:33:796 8244 2d7c Setup File operations for section cdm completed successfully
2009-11-13 08:41:33:796 8244 2d7c Setup Starting file operations for section wuapi
2009-11-13 08:41:37:406 8244 2d7c Setup Successfully copied source file C:\WINDOWS\SoftwareDistribution\WebSetup\wuapi.dll to C:\WINDOWS\system32\wuapi.dll.wusetup.2406122015.new
2009-11-13 08:41:37:406 8244 2d7c Setup WARNING: Could not move C:\WINDOWS\system32\wuapi.dll to C:\WINDOWS\system32\wuapi.dll.wusetup.2406122031.bak due to 0x80070020
解決方法︰
1. 手動將以下檔案從 system32\SoftwareDistribution 資料夾複製到 C:\Winodws\System32 資料夾底下
- wuapi.dll
- wuapi.dll.mui
- wups.dll
- wups2.dll
2. 執行 regsvr32 filename 手動註冊以上的 dll 檔案
3. 把以下機碼手動刪除
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Setup\ServiceStartup]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Setup\ServiceStartup\wuapi.dll]
"TargetFile"="C:\\WINDOWS\\system32\\wuapi.dll"
"CacheFile"="C:\\WINDOWS\\system32\\SoftwareDistribution\\Setup\\ServiceStartup\\wuapi.dll\\7.4.7600.226\\wuapi.dll"
"RegistrationFlags"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Setup\ServiceStartup\wups.dll]
"TargetFile"="C:\\WINDOWS\\system32\\wups.dll"
"CacheFile"="C:\\WINDOWS\\system32\\SoftwareDistribution\\Setup\\ServiceStartup\\wups.dll\\7.4.7600.226\\wups.dll"
"RegistrationFlags"=dword:00000001
"NoVersionCheck"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Setup\ServiceStartup\wups2.dll]
"TargetFile"="C:\\WINDOWS\\system32\\wups2.dll"
"CacheFile"="C:\\WINDOWS\\system32\\SoftwareDistribution\\Setup\\ServiceStartup\\wups2.dll\\7.4.7600.226\\wups2.dll"
"RegistrationFlags"=dword:00000001
"NoVersionCheck"=dword:00000001
4. 打開 IE執行Windows Update, 已可正常更新
5. 重新開機檢查以下服務, 正常執行中, Windows Update也可正常安裝更新
- Automatic Updates
- Background Intelligent Transfer Service
- Cryptographic Services
SYMPTOMS
=================
After you press CTRL+ALT+DELETE to log on to a Microsoft Windows Server 2003-based computer, the logon screen turns black. Although you cannot see what you are typing, you can successfully log on to the Windows Server 2003-based computer. Then, after you successfully log on, the screen becomes visible.
Note This symptom may occur on both the terminal server sessions and the local console. Additionally, this symptom occurs even if you start the computer in Safe mode.
CAUSE
=================
This issue occurs if all the values under the following registry subkey are set to "0 0 0":
HKEY_USERS\.Default\Control Panel\Colors
Note The value data "0 0 0" means black.
WORKAROUND
=================
To work around this issue, perform the following procedures.
Export the registry subkey from another Windows Server 2003-based computer
1. Click Start, point to Run, type regedit in the Open box, and then click OK.
2. Locate the following registry subkey:
HKEY_USERS\.Default\Control Panel\Colors
3. Right-click the Colors registry subkey, and then click Export.
4. In the File name box, type a name for the file.
5. Note the location where you will save the file, and then click Save.
Import the registry subkey into the affected computer
1. Click Start, point to Run, type regedit in the Open box, and then click OK.
2. On the File menu, click Import.
3. Double-click the .reg file that you want to import.
4. Quit Registry Editor, and then restart the computer.
REFERENCE
=================
906510 The logon screen turns black after you press CTRL+ALT+DELETE to log on to a Microsoft Windows Server 2003-based computer http://support.microsoft.com/kb/906510
Q. How to configure force tunneling for DA so that client are forced to use IP-HTTPS
A. To configure force tunneling, you must enable force tunneling on DirectAccess clients through Group Policy and add a special entry in the NRPT.
To enable force tunneling with Group Policy, enable the Computer Configuration\Policies\Administrative Templates\Network\Network Connections\Route all traffic through the internal network setting in the Group Policy object for DirectAccess clients.
For More Info: Choose an Internet Traffic Separation Design http://technet.microsoft.com/en-us/library/ee382262(WS.10).aspx
You can configure DirectAccess clients to send all of their traffic through the tunnels to the DirectAccess server with force tunneling. When force tunneling is configured, DirectAccess clients that detect that they are on the Internet modify their IPv4 default route so that default route IPv4 traffic is not sent. With the exception of local subnet traffic, all traffic sent by the DirectAccess client is IPv6 traffic that goes through tunnels to the DirectAccess server.
Enabling force tunneling has the following consequences:
- DirectAccess clients use only Internet Protocol over Secure Hypertext Transfer Protocol (IP-HTTPS) to obtain IPv6 connectivity to the DirectAccess server over the IPv4 Internet. IP-HTTPS-based connections have lower performance and higher overhead on the DirectAccess server than 6to4 and Teredo-based connections.
- The only locations that a DirectAccess client can reach by default with IPv4 traffic are those on its local subnet. All other traffic sent by the applications and services running on the DirectAccess client is IPv6 traffic sent over the DirectAccess connection. Therefore, IPv4-only applications on the DirectAccess client cannot be used to reach Internet resources, except those on the local subnet.
- Connectivity to the IPv4 Internet must be done through servers and devices on the intranet that translate the IPv6 traffic from DirectAccess clients to IPv4 traffic for the IPv4 Internet. If you do not have the appropriate servers or translators, your DirectAccess clients will not have access to IPv4 Internet resources, even though they are directly connected to the IPv4 Internet.
建議您先將IIS轉換為x64
Run IIS as 64 bit machine by changing the metabase key enable32bitapponwin64 to false(0)
1. Open a command prompt and navigate to the %windir%\Inetpub\AdminScripts directory.
2. Type the following:
"cscript.exe adsutil.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 0" and press Enter
3. Do an iisreset
Now the IIS processes would run under 64 bit version then try to reinstall WSUS SP2
WSUSetup.log error
2009-10-20 13:41:20 Error MWUSSetup InstallWsus: MWUS Installation Failed (Error 0x80070643: 安裝時發生嚴重錯誤。)
2009-10-20 13:41:20 Error MWUSSetup CInstallDriver::PerformSetup: WSUS installation failed (Error 0x80070643: 安裝時發生嚴重錯誤。)
2009-10-20 13:41:20 Error MWUSSetup CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: 安裝時發生嚴重錯誤。)
並且應用程式事件出現大量LoadPerf Error
事件類型: 錯誤
事件來源: LoadPerf
事件類別目錄: 無
事件識別碼: 3011
日期: 2009/10/20
時間: 下午 02:00:02
使用者: N/A
電腦: WSUS
描述:
解除載入服務 wsus: client web service methods (wsus: client web service methods) 的效能計數器字串時失敗。 錯誤碼是資料區段中的第一個 DWORD。
請在 http://go.microsoft.com/fwlink/events.asp 查看說明及支援中心，以取得其他資訊。
資料:
0000: f2 03 00 00 6e 05 00 00 o...n...
解決方法
若要重建所有效能計數器，包括 [Windows Server 2003 中的 [可延伸和第三方廠商計數器，請在命令提示字元輸入下列命令。 按 ENTER 鍵之後每個命令。
cd\windows\system32
lodctr /R
附註 /R 則為大寫。 必須有系統管理權限成功執行此命令在電腦上。
參考
How to manually rebuild Performance Counter Library values
http://support.microsoft.com/kb/300956/en-us
磁碟機右鍵內容
進入到磁碟機後全選包含隱藏檔案右鍵內容所看到的檔案大小不一致
Technical Background
==================
1. Usually, our customer use Explorer to get disk space usage information. For example, select all the folders and then click Properties. It shows the space being used by those folders. However, the value shows in the size on disk cannot reflect the real disk space usage.
Here are the common reasons why some disk space usage is not counted by explorer.
a. Explorer will not count the folder/file which the logon user does not have permission to access.
b. Hidden folder/files are not counted if Show hidden and system files is not selected in Folder Option.
c. Explorer will not count file’s second data attribute (or in some document, we called it alternative data stream). In NTFS file system, everything is an attribute. File’s data is also an attribute. By default, one file has one data attribute, but we can create multiple data attribute for one file.
d. Explorer does not count the disk space being used by file system metadata file like $MFT, $Secure.
$MFT contains all the file records. Each file record is 1K. NTFS use at least one file record to describe a file or a folder. NTFS will not shrink the $MFT file size. If huge amount of files have ever been created, even if the files are deleted later, the size of $Mft could be very large with lot of unused file records.
$Secure is a NTFS metadata file which contains all the security descriptors (NTFS permission) and necessary indexes for the security descriptor and its hash value. Each security descriptor will have a corresponding ID (security ID). In each file record, it has the security ID. NTFS gets the security ID and find the corresponding security descriptor for a particular file or folder.
2. In the NTFS file system level, there are three additional reasons which will cause the disk space usage is more than what customer expects.
a. File system corruption. Some free disk space are incorrectly marked as allocated which will cause unexpected disk space usage.
b. Reserved disk space. NTFS driver could reserve clusters for specific purpose. One typical situation is: If a NTFS compressed file is opened as memory mapping file, NTFS will reserve additional clusters until the cached data tear down. The reserved clusters will be released after a reboot.
c. Many small files. For file system, the allocation unit is what we called Cluster. Cluster size is 4K in most of the cases (8 sectors). If the disk has many small files which size is like 1K or 2K, NTFS will still allocate one cluster for each file. So, disk space might be wasted. We can run the command line “fsutil fsinfo ntfsinfo <drive letter>” to get the size of cluster. In the sample below, you can see the size of a cluster is 4K.
Issue:
======
data encryption error in RDP
遠端桌面已中斷連線
因為資料加密錯誤，這個工作階段將結束。請嘗試重新連線到遠端電腦。
Remote Desktop Disconnected
Because of an error in data encryption, this session will end. Please try connecting to the remote computer again.
Cause:
=====
Broadcom Advanced Control Suite property of IPv4 large send offload
Solution
========
To resolve it open the Broadcom Advanced Control Suite and disable IPv4 Large Send Offload and your problem will be solved.
Problem
=========
無法修改Licensing Mode to Per User
Cause
=====
GPO
Solution
=======
After change the GPO setting, this issue was fixed.
設定終端機伺服器授權模式
To configure the Terminal Server Licensing mode
Using Group Policies (best practice)
1. 開啟 [群組原則]。
2. 在 [電腦設定]、[系統管理範本]、[Windows 元件]、[終端機服務] 中，連按兩下 [終端機伺服器授權模式] 。
3. 按一下 [啟用]。
4. 按一下 [每個使用者] 或 [每一裝置]，再按 [確定]。
每一裝置 CAL 對每一個執行 Windows Server 2003 的用戶端電腦或裝置授與存取終端機伺服器的權利。每個使用者 CAL 對一位使用者授與從不限數量之裝置存取終端機伺服器的權利。
![clip_image002[4]](http://blogs.technet.com/blogfiles/csstwplatform/WindowsLiveWriter/CannotchangeLicensingModefromPerDeviceto_A14A/clip_image002%5B4%5D_thumb.jpg "clip_image002[4]")
當在WLM中嚐試要和聯絡人進行視訊或是音訊通話時，會發生以下的錯誤訊息：
Messegner 服務暫時無法啟用，請稍候再試(0x8ac70013)
解決方案：
滑鼠右鍵點選Windows Live Messenger->內容->相容性
取消勾選"以相容性模式執行這個程式"
重新啟動Windows Live Messenger
在Windows Vista裏，只要點選「開始」，直接輸入關鍵字的話，即可以蒐尋硬碟裏的檔案以及使用IE的搜尋直接在Internet上尋找，但在Windows 7裏，各位會發現此功能消失了。以下的方式是讓該功能再從Windows 7上新增進來。
1.執行gpedit.msc。
2. 找到「使用者設定」>「系統管理範本」>「『開始』功能表和工作列」。
3.在右方找到新增「搜尋網際網路」連結到「開始」功能表，將它改成啟動。
4.之後，在左下角的「開始搜尋」裏輸入關鍵字，即會出現「搜尋網際網路」。
Problem:
==========
While trying to install agents in SCOM SP1 setup we were getting error as “SPN error: event id 21001 and 20057 with source OPS mgr connector”
Cause:
=====
Duplicate SPN’s was causing this issue.
Resolution:
=========
We manually deleted the duplicate SPN’s.
You can refer to the Method 1 listed in the following KB article:
http://support.microsoft.com/kb/321044
Method 1: Use the LDP support tool
Note If you do not have the Windows 2000 support tools installed, install them from the Windows 2000 CD-ROM before you continue. The Setup executable file for the support tools is located on the CD-ROM in the Support\Tools folder. The installation does not require that you restart the computer. However, you may have to restart the computer to update the environment variables.
- Click Start, click Run, type LDP, and then click OK.
- Click Connection, and then click Connect.
- Leave the default settings, and then click OK.
Note If you do not receive the expected result, try another search by using the Global Catalog Port (3268) instead of the default setting (389).
- Click Connection, and then click Bind.
- Leave the default settings, and then click OK.
- Click View, and then click Tree.
- In the Tree View dialog box, type DC=YourDomain,DC=com in the BaseDN box, where YourDomain is your domain.
- Click Browse, and then click Search.
- In the Search dialog box, type DC=YourDomain,DC=com in the BaseDN box.
- In the Search dialog box, type (serviceprincipalname=HOST/mycomputer.mydomain.com) in the Filter box. If the service principal name that is referred to in the error in the System log differs from this example, type the service principal name to which the error refers.
Note If you do not receive the expected result, try searching for " HOST/" as opposed to searching only for the exact SPN in the event ID.
- Under Scope, click Subtree.
- Click Run.
PROBLEM:
============
Move Operations Manager 2007 RMS to new server.
RESOLUTION:
===========
Following are the steps to promote Management Server to RMS:
1. On the Management Server to be promoted, copy SecureStorageBackup.exe and ManagementServerConfigTool.exe from SupportTools folder of the installation media to the install directory (by default, C:\Program Files\System Center Operations Manager 2007).
2. Open a Command Prompt window and change directory to C:\Program Files\System Center Operations Manager 2007
3. Type the command: C:\Program Files\System Center Operations Manager 2007>SecureStorageBackup.exe Restore filename This file is the backed up Root Management Server encryption file required by this procedure.
4. Provide password as required.
5. On the Management Server, type the command: C:\Program Files\System Center Operations Manager 2007>ManagementServerConfigTool.exe PromoteRMS
If you get an error that this Management Server is configured for multiple management group and its not supported.
Check the following registry key HKLM\Software\Microsoft\Microsoft Operations Manager\3.0\Server Management Groups Parent Health Service Send Priority VHA SCOM
We backup the "Parent Health Service" and "Send Priority" Keys and deleted them.
Run the same command again, and it should work
6. If the original Root Management Server is to be demoted to being a Management Server, on the original Root Management Server, type the command: C:\Program Files\System Center Operations Manager 2007>ManagementServerConfigTool.exe UpdateDemotedRMS
7. Go to the promoted Root Management Server, open the services snap-in, and stop the MOM HealthService.
8. Go to the installation directory (default: %ProgramFiles%\System Center Operations Manager 2007) and delete the Health Service State folder.
9. Start the MOM Health Service.
10. When you open the Operations Console the first time, specify the name of the new Root Management Server to connect to.
Reference:
============
How to Promote a Management Server to a Root Management Server Role in Operations Manager 2007
http://technet.microsoft.com/en-us/library/cc540401.aspx
根據Userenv log
Found file system path of: <\\msft.com\sysvol\topsnmq.chtn.com.tw\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}>
USERENV(154.3c8) 10:12:20:687 ProcessGPO: Couldn't find the group policy template file <\\msft.com\sysvol\msft.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>, error = 0x35.
USERENV(154.3c8) 10:12:20:718 ProcessGPO: ==============================
USERENV(154.3c8) 10:12:20:718 EvalList: ProcessGPO failed
USERENV(154.3c8) 10:12:20:718 GetGPOInfo: EvaluateDeferredGPOs failed. Exiting
USERENV(154.3c8) 10:12:20:734 GetGPOInfo: Leaving with 0
USERENV(154.3c8) 10:12:20:734 GetGPOInfo: ********************************
USERENV(154.3c8) 10:12:20:734 ProcessGPOs: GetGPOInfo failed.
USERENV(154.3c8) 10:12:20:734 LeaveCriticalPolicySection: Critical section 0x428 has been released.
USERENV(154.3c8) 10:12:20:734 ProcessGPOs: Computer Group Policy has been applied.
徵狀
-由用戶端嘗試存取Server仍出現錯誤 "Windows 找不到檔案或項目"
-\\電腦名稱 可以正常存取,但是\\msft.com 存取會失敗
解決
檢察DC上的 TCP/IP netbios help service 沒有啟動, 啟動服務後 sysvol即可以正常存取,並且GPO可以套用成功
當 DB & Transaction Log 檔占滿硬碟空間時，您可以使用以下步驟壓縮資料庫:
-- How to Shrink OperationManagerDW Database
--1. Check the OperationManagerDW Database Properties and DBID, for example this database is DBID 18
sp_helpdb
--2. Check the OperationManagerDW(DBID 18) Database Log File ID / name (OperationManagerDW_Log)
select * from master..sysaltfiles where dbid=18
--3. Truncate Trnsaction Log
Backup Log OperationManagerDW With Truncate_Only
--4. Shrink Whole Database
DBCC SHRINKDATABASE(OperationManagerDW)
--5. Srink Log File Again to reduce file size
USE OperationManagerDW
GO
DBCC SHRINKFILE(OperationManagerDW_Log)
您可以參考 KB 256650 來避免 SQL Server 資料庫的交易記錄檔超出預期大小:
- 像是固定執行 DB 備份
- 設定維護計劃
- 變更復原模式
- etc...
By default, in SQL Server 2000 and in SQL Server 2005, the recovery model for a SQL Server database is set to the Full recovery model. With the full recovery model, regular backups of the transaction log are used to prevent the transaction log file size from growing out of proportion to the database size. However, if the regular backups of the transaction log are not performed, the transaction log file grows to fill the disk, and you may not be able to perform any data modification operations on the SQL Server database.
You can change the recovery model from full to simple if you do not want to use the transaction log files during a disaster recovery operation.
Change the recovery model. If a disaster or data corruption occurs, you must recover your database so that the data consistency and the transactional integrity of the database are maintained. Based on how critical the data in your database is, you can use one of the following recovery models to determine how your data is backed up and what your exposure to the data loss is:
- Simple recovery model
- Full recovery model
- Bulk-logged recovery model
By using the simple recovery model, you can recover your database to the most recent backup of your database. By using the full recovery model or the bulk-logged recovery model, you can recover your database to the point when the failure occurred by restoring your database with the transaction log file backups.
In addition, the Operations Manager databases do not need maintenance tasks as it has its own internal maintenance processes. Some table/index are dropped and created again. That is why your maintenance job is failing re-indexing an index that does not exist
REFERENCE
================
INF: Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE http://support.microsoft.com/kb/272318/en-us
INF: 如何將 SQL Server 交易記錄檔壓縮 http://support.microsoft.com/kb/256650/zh-tw
如何避免 SQL Server 資料庫的交易記錄檔超出預期大小 http://support.microsoft.com/kb/873235/zh-tw
INF: SQL Server 中的 Autogrow 及 Autoshrink 設定考量 http://support.microsoft.com/kb/315512/zh-tw
Maintenance Plans http://msdn.microsoft.com/en-us/library/ms187658.aspx
Maintenance Tasks http://msdn.microsoft.com/en-us/library/ms140255.aspx
Recovery Model Overview http://msdn.microsoft.com/en-us/library/ms189275.aspx
