IT Log & 期權賠錢全記錄: 問題處理

顯示具有 問題處理 標籤的文章。顯示所有文章

2026/01/22

Windows 資料夾透過FASTCOPY同步到NAS共用資料夾權限並沒有同步

環境:

Windows 資料夾透過FASTCOPY，同步到NAS共用資料夾

異常狀況:

資料夾開始建立進行同步時，發現權限並沒有同步過去

解決過程:

研究了很久，發現測試的資料夾正常，正式要同步的資料夾會有問題。

原來是資料夾第一次在同步時，還沒全部完成前去查看資料夾權限時，不會是最後的結果，所以要等同步完再檢查，就會發現資料夾的ACL權限有全部同步過去了。

Environment:

Windows folders synchronized to a NAS shared folder using FastCopy.

Issue:

When the folder creation and synchronization start, the folder permissions (ACLs) do not appear to be synchronized to the NAS.

Resolution / Findings:

After extensive investigation, it was found that test folders behaved normally, while the production folders showed this issue.

The root cause is that during the initial synchronization, if you check the folder permissions before the sync process has fully completed, the permissions shown are not the final result.
Once the synchronization finishes completely and you recheck the folder permissions, you will see that the ACL permissions have been fully and correctly synchronized.

2026/01/12

筆電安裝win10/11 找不到ssd硬碟

環境:

ASUS or ACER筆電

異常狀況:

重灌win10 or win11系統時，在選擇要安裝在哪個磁區，不會顯示ssd硬碟的磁區。

解決過程:

1.下載irst這個驅動程式，asus網站上有提供。

https://www.asus.com/tw/supportonly/irst/helpdesk_download/

2.將該程式放入win10 or win11的安裝usb中。

3.安裝win10 or win11系統時，在選擇要安裝在哪個磁區的步驟，選擇載入驅動程式，然後選擇irst。

4.ssd磁碟就會正常顯示出來。

Environment:

ASUS or ACER laptops

Issue:

When reinstalling Windows 10 or Windows 11, the SSD drive does not appear during the disk selection step of the installation process.

Resolution / Troubleshooting Steps:

Download the IRST (Intel Rapid Storage Technology) driver (available on the ASUS website).
Copy the driver to the Windows 10 or Windows 11 installation USB drive.
During the Windows installation, at the step where you choose the disk to install the OS, select Load driver, then choose the IRST driver.
The SSD drive will then be displayed correctly.

2026/01/07

點選右下角的日期時間不會跳出月曆

環境:

WIN 11點選右下角的日期時間，不會跳出月曆

解決過程:

1.windows鍵+ r鍵，輸入 regedit

2.找到HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Windows\Explorer\

3.把DisableNotificationCenter設成 0

Environment:

On Windows 11, clicking the date and time in the bottom-right corner does not display the calendar.

Resolution :

1.Press Windows key + R, then type regedit.

2.Navigate to:

HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Windows\Explorer\

3.Set DisableNotificationCenter to 0.

2025/12/09

Blogger裡面的廣告突然都沒了

環境:

Google blogger + adsense

異常狀況:

多年前我的 blogger有申請adsense，想賺點廣告費，一開始的確也有看到有廣告收到，但大概在兩三年前，發現收入一直沒增加，點開網站才發現通通都沒廣告了。

但在adsense上的設定都沒去調整，狀態都是正常的，也設定了自動廣告，版面上也有設定廣告的視窗。

但就是沒廣告。

解決過程:

之前上網查都沒什麼有用的解決。

後來gemini出現了，就想說問它看看，結果gemini說要在主題裡，用html編輯，插入一段語法，結果插入存檔後。

直接重新開啟網頁，裡面廣告馬上就出現了，太神奇了。

gemini的說明如下:

檢查自動化廣告的程式碼（重要！）

在 Blogger 後台，進入 「主題」(Theme) 或 「範本」 設定。
點擊 「編輯 HTML」(Edit HTML)。
請檢查在 HTML 程式碼中，<head> 標籤之後，是否存在以下格式的 AdSense 程式碼片段：
HTML
<script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-您的發布商 ID" crossorigin="anonymous"></script>
（ca-pub-您的發布商 ID 應替換為您自己的 ID）
如果找不到這段程式碼， 這就是問題所在。您需要從 AdSense 後台重新取得**「自動化廣告」**的程式碼，並將其貼到 Blogger 的 <head> 區塊內。

Environment:

Google Blogger + AdSense

Issue:

Many years ago, I applied for AdSense on my Blogger site to earn some ad revenue. At first, I did see ads and some earnings coming in. However, around two or three years ago, I noticed that my revenue had stopped increasing. When I opened the site, I realized that all the ads had disappeared.

I hadn’t changed any settings in AdSense; everything still showed as normal. Auto ads were enabled, and ad slots were configured on the layout.

But no ads were showing.

Troubleshooting Process:

I previously searched online but couldn’t find any helpful solutions.

Later, when Gemini came out, I decided to ask it. Gemini suggested editing the theme’s HTML and inserting a specific code snippet. After inserting the code and saving the changes…

I refreshed the site, and the ads appeared immediately. It was amazing.

In the Blogger dashboard, go to “Theme” and click “Edit HTML.”

Check whether the following AdSense code snippet exists right after the <head> tag:


<script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-YourPublisherID" crossorigin="anonymous"></script>

(ca-pub-YourPublisherID should be replaced with your own publisher ID.)

If this code is missing, this is the root cause.
You need to go to the AdSense dashboard, retrieve the Auto Ads code again, and paste it into the <head> section of your Blogger theme.

2025/12/01

solidworks功能表中文亂碼中文名稱的STEP檔無法開啟

win11安裝solidworks 後，出現一些功能表中文是亂碼、有中文名稱的STEP檔無法開啟

要進到"選用功能"，把"台灣地區"這個選項解除安裝。

2025/11/28

重灌電腦出現 "選取的磁片具有mbr磁碟分區表格....." 錯誤，沒有顯示電腦內的硬碟

環境:

DEll筆電，要重灌WIN11

異常狀況:

用WIN11 USB重灌電腦時，出現 "選取的磁片具有mbr磁碟分區表格....." 錯誤，裡面只有顯示USB磁碟，但電腦內的硬碟卻沒抓到。

解決過程:

進入到bios設定中，去storage裡面，原本是選擇raid on，改成ahci/nvme，在重開機，就可以正常重灌系統了。

Environment

Device: Dell laptop

Goal: Reinstalling Windows 11

Problem/Error Description

When attempting to reinstall Windows 11 using a Windows 11 USB installation drive, the following error message appeared: "The selected disk has an MBR partition table..."

The system only displayed the USB drive as an available disk, but the internal hard drive (or SSD) was not detected by the installation program.

Solution

Enter the BIOS/UEFI Setup menu.

Navigate to the Storage or SATA Operation settings.

The original setting was RAID On (or Intel VMD/RST).

Change the setting from RAID On to AHCI/NVMe.

Save the changes and restart the computer.

The system installation (reinstallation) can now proceed normally, as the internal drive is detected.

2025/11/19

ASUS ESC700 G3 開機一直進BIOS

環境:

ASUS ESC700 G3

WIN7

異常狀況:

當機之後，開機就會一直直接進到BIOS，從BIOS裡的資訊看的出來有抓到硬碟。

但把線重新拔插，重開機後，還是一樣狀況

解決過程:

把該硬碟接到別台主機，可正常開機。

拿其他台電腦的硬碟來接上有問題的主機，也可正常開機。

所以判斷硬碟跟主機板都沒問題，應該就是BIOS設定問題。

BIOS設定裡面的"啟動"->"作業系統類型"，本來是選擇"windows uefi模式"，將它改成"其他作業系統"，然後重開機後就正常了。

2025/10/21

WIN2025DC 開啟其他DC的共用資料夾存取被拒 KDC不支援所要求的加密類型

環境:

DC主機作業系統: win2022 & win2025

網域&樹系功能等級: 2016

異常狀況:

win2025dc剛登入系統後，連線任何dc的共用資料夾都是正常的，但大概半小時後，就無法連線，會跳出存取被拒的視窗，要求重新輸入帳號密碼。而且畫面右下角還會跳出"windows需要您目前的認證"

所有的win2025dc都有這個問題，但win2022dc都沒這個問題。

後來有做一個測試:

1.在dc上執行klist purge，清除所有票證

2.接著執行klist get krbtgt。

沒問題的dc就可以抓到票證，但有問題的dc就會出現KDC不支援所要求的加密類型。

經調查，是administrator密碼很久沒變更，使用的是rc4的加密協定，但win2025dc預設會不支援。

所以就是把domain administrator帳號裡，勾選支援aes 128跟256位元加密類型，然後再重設administrator的密碼，就可以排除這個問題。

2025/10/13

DC作業系統網域功能等級樹系功能等級升級-win2025 dc無法登入

環境:

DC主機作業系統: win2012r2

網域&樹系功能等級: 2003

升級流程:

1. 新增win2022 DC主機，設定5大角色

2. 移除win2012r2 DC主機

3. 網域&樹系功能等級升級到2016

4. 新增win2025 DC主機，出現異常

異常狀況:

不管新增幾台win2025 DC主機，升級成DC角色重開機後，win2025 DC主機遠端桌面或本機無法登入，都會出現帳號密碼有錯，安裝最新的windows更新，使用不同的domain admin帳號登入都一樣無法登入

解決過程:

上網查詢相關解法，可以先在win2022DC主機上，用ps session連到win2025DC主機，把KDC服務關閉，就可以登入win2025DC，但登入後，就算把KDC服務開啟，也是無法正常與其他DC主機同步。

試過ChatGPT提供的很多方法，都無法解決，但在一些文件上有看到重設krbtgt這個系統帳號的密碼，就可以解決問題了，很多人建議去下載一個重設krbtgt密碼的powershell，做重設密碼。

先請微軟連線確認問題，收集完相關log，也是判斷KDC服務的一些加密協定不支援，造成登入失敗，DC同步失敗等問題，因此建議重設krbtgt這個系統帳號的密碼，用ADUC去重設，沒有提供powershell來做重設。

在第一次重設krbtgt密碼後，新建的win2025主機升成DC後，就可正常登入運作了，不用等第二次重設。

但微軟有建議，要在10小時後重設第二次，所有隔天有再重設一次。

Environment

Existing DC Operating System: Windows Server 2012 R2
Domain & Forest Functional Level: Windows Server 2003

Upgrade Procedure

Added a new Windows Server 2022 domain controller and transferred all five FSMO roles to it.
Removed the Windows Server 2012 R2 domain controller.
Upgraded the domain and forest functional levels to Windows Server 2016.
Added a new Windows Server 2025 domain controller — issue occurred.

Issue Description

After promoting any Windows Server 2025 machine to a domain controller and rebooting, it becomes impossible to log in either locally or via Remote Desktop.
The system reports that the username or password is incorrect.
Installing the latest Windows updates or using different domain administrator accounts does not resolve the problem — all attempts to log in fail.

Troubleshooting Process

Based on online findings, a temporary workaround was discovered:
From the Windows Server 2022 DC, use PowerShell remoting (PSSession) to connect to the affected Windows Server 2025 DC and stop the KDC service.
After stopping the KDC service, login becomes possible.
However, once logged in, re-enabling the KDC service does not restore normal replication or synchronization with other domain controllers.

Multiple potential solutions provided by ChatGPT and other sources were tested but did not resolve the issue.
Several documents mentioned that resetting the “krbtgt” system account password could resolve similar problems. Many users recommended using a PowerShell script to perform the reset.

Microsoft was then engaged for remote troubleshooting. After reviewing the collected logs, Microsoft determined that the issue was caused by unsupported encryption protocols within the KDC service, which led to authentication and replication failures.
Microsoft advised resetting the krbtgt account password using Active Directory Users and Computers (ADUC), rather than via PowerShell.

After performing the first krbtgt password reset, newly promoted Windows Server 2025 DCs were able to log in and operate normally.
A second reset was not immediately required for functionality.

However, Microsoft still recommended performing a second krbtgt password reset after 10 hours, which was carried out the following day as advised.

2025/10/01

redhat 備份虛擬機還原開機後出現錯誤 fsck.ext3: memory allocation failed while retrying to read bitmaps for /p1

一台redhat 備份虛擬機，在還原到其他硬體，開機後出現錯誤

fsck.ext3: memory allocation failed while retrying to read bitmaps for /p1

an error occurred during the file system check dropping you to a shell the system will reboot when you leave the shell

這時就先去查/p1是掛在哪個硬碟後，用root密碼登入，執行下列指令

fsck -y /dev/sda1

完成後在執行 reboot，就可以正常進入到系統了。

2025/09/16

WINDOWS11連線WINDOWS2003共用資料夾錯誤碼:0x80004005

原本WINDOWS11連線WINDOWS2003共用資料夾都正常，但突然有一天卻無法連線，錯誤碼:0x80004005 。

利用WINDOWS7, 10, 2008, 2025都可以，非常奇怪。

最後解決方法是把WINDOWS11裡的SMB1.0 用戶端移除後重新安裝一次，就好了。

Originally, Windows 11 could connect to the Windows 2003 shared folder without any issues, but suddenly one day it stopped working, showing error code: 0x80004005.

Strangely, Windows 7, 10, 2008, and 2025 could all connect normally.

The final solution was to remove the SMB 1.0 client feature on Windows 11 and reinstall it, which fixed the problem.

2025/09/08

DNS 有不同主機對應相同IP

網域的DNS主機中，發現有一些電腦已取到其他IP，但DNS上還會保留舊記錄，不會自動清除，其他電腦後來取得該IP時，DNS上就有兩台電腦對應同一個IP。

這就會造成連線電腦時，會連錯電腦。

檢查過DHCP，已經設定成動態更新DNS了，還是不會更新DNS記錄，後來查發現，DNS的設定中，也要把啟用動清除過時的記錄打勾，DNS裡的舊記錄才會被清除。

On the domain DNS server, it was found that some computers had already obtained new IP addresses, but the DNS still kept their old records without automatically clearing them. When another computer later obtained that same IP, the DNS ended up showing two computers mapped to the same IP address.

This caused connection issues, as attempts to connect to one computer could actually connect to the wrong one.

After checking the DHCP settings, it was confirmed that dynamic DNS update was already enabled, but the DNS records were still not being updated. Further investigation revealed that in the DNS settings, the option “Enable scavenging of stale records” must also be checked; only then will outdated DNS records be cleared.

2025/08/28

synology active backup for business 還原虛擬機需保持原設定

synology active backup for business 備份虛擬機後，還原時如果需保持原設定，就需要在還原後，虛擬機第一次開機時，選擇"我已將其移動"。

通常會選這個，是因為裡面有裝一些軟體是會綁定硬體資訊，所以還原時，必須保持所有相關的設定資訊。

2025/08/12

outlook傳送接收失敗出現"未提供"

outlook突然無法收發信，按下傳送接收時，都會跳出一個"未提供"的錯誤訊息。

重設outlook profile也沒用。

進到控制台，對outlook執行修復就正常了。

Outlook suddenly couldn’t send or receive emails. When clicking Send/Receive, it would always show an error message saying “Not Specified.”

Resetting the Outlook profile didn’t help.

Going into Control Panel and running a repair on Outlook fixed the issue.

2025/07/04

WINDOWS2019 執行windows update離線安裝檔無反應

在WINDOWS2019下載windows 的更新檔要進行安裝，但執行後都沒任何反應，或是要等很久才會跳出smart screnn的警告視窗。

這是因為系統設定中，有做安全性控管，設成警告。

只要先把它調成關閉，重新登入一次系統，這時後在點選安裝，視窗就會正常跳出，讓我們點進下一步進行安裝。

When attempting to install Windows updates on Windows Server 2019, nothing happens after execution, or it takes a long time before the SmartScreen warning window appears.

This is due to a security control setting in the system, which is currently set to "Warn."

Simply change the setting to "Off" and log in to the system again. After that, when you click the installer, the window will appear normally, allowing you to proceed with the installation.

2025/06/04

excel 沒有任何頁籤

有一份excel編輯到一半時當掉了，重開啟啟後，裡面完全沒任何東西，沒任何頁籤。

所以就用修復的方式再開啟一次，但還是沒效，想說沒救了。

結果就查了一下excel沒有任何頁籤，沒想到還真的有這個設定，去檢視裡面，取消隱藏頁籤，檔案裡的資料就全部出現，恢復正常了。

2025/05/21

ad帳號鎖定查修

偶爾都會遇到ad帳號一直被鎖的問題，就要去查明原因，下面就列出清查的方式。

事情準備 : dc主機上相關log功能一定要開。

1. 在gpo->domain controllers policy裡，要啟用下列三個稽核功能，這樣在事件檢視器裡的安全性事件裡，才能找到登入失敗的相關訊息。

2. 在gpo->domain controllers policy裡，NTLM的稽核也要開啟，這樣在事件檢視器裡的NTLM裡面，才能找到更準確的登入失敗訊息。

3. 要設定帳號鎖定的log產生時，發信通知相關人員，這樣才會知道是否有某帳號一直被鎖定的異狀發生。

清查流程 : 當發現某帳號一直被鎖定時

1. 先查安全性事件，找4625，4771，4776，如果能在這裡面找到來源的ip，那就趕快找到該電腦做處理。

2. 如果在安全性事件裡的log，找不到來源電腦，就要去NTLM的log裡，那邊也會顯示來源電腦。

最近遇到比較特別的狀況是a網域的帳號被鎖定，但從NTLM的log查到的安全通道名稱，是另一個信任網域b的dc主機，但上面顯示的工作站名稱，在b網域裡都查不到，而且會變來變去。

這時後就再去b網域的dc主機上，查詢NTLM log。結果log裡安全通道名稱，是顯示一台網域內的電腦。

後來發現是這台電腦有開放對外服務，有一些來自外部的異常連線，關閉服務後，帳號被鎖定的問題就解除了。

We occasionally encounter issues where an AD account keeps getting locked, and we need to investigate the cause. Below are the steps for troubleshooting.

Preparation:
Make sure the relevant logging features are enabled on the domain controller (DC).

In GPO -> Domain Controllers Policy, enable the following three audit policies. This will allow you to find failed login information under the Security events in Event Viewer.
Also in GPO -> Domain Controllers Policy, enable NTLM auditing. This helps you locate more accurate failed login details under the NTLM section in Event Viewer.
Configure alerts to notify relevant personnel via email when an account lockout log is generated. This ensures you're aware when an account is repeatedly getting locked.

Troubleshooting Process:
When you discover that a certain account keeps getting locked:

First, check the Security event logs for event IDs 4625, 4771, and 4776. If you can find the source IP there, locate the corresponding computer and take action.
If the source computer cannot be identified in the Security logs, check the NTLM logs. These also show the source machine involved in the failed login.

A recent unusual case:
An account from domain A was being locked, but the NTLM log showed that the secure channel name was a domain controller from trusted domain B. However, the workstation name shown could not be found in domain B and kept changing.

In this case, we checked the NTLM logs on the domain controller in domain B. The secure channel name in the logs pointed to a computer within the domain.

We later found that this computer was running a public-facing service, and there were some abnormal external connection attempts. After shutting down the service, the account lockout issue was resolved.

2025/05/19

Next Terminal 遠端電腦鍵盤問題

利用Next Terminal，遠端連線到其他台windows電腦時，按某些鍵時，並不會出現正確的字，會變成其他快捷鍵功能。譬如說按下t，會跳出檔案總管之類的。

這時後就是把那台windows重開機，就會正常了。

2025/04/08

COMMVAULT備份工作失敗-錯誤碼： [32:399]

主機在意外當機後，有一個備份工作一直無法正常運作，會出現下列錯誤

錯誤碼： [32:399] 描述： Deduplication Database (DDB) access path [D:\xxx_dedup]

on MediaAgent [commvault] is offline for Storage Policy Copy [VMBackup_Policy / xxx ].

Offline Reason: The active DDB of current storage policy copy is not available to use. 請啟動重複數據刪除DB重建作業。

查了一下原廠網站說明，我們就是因為ddb程序意外中斷的關係造成這個問題。

對照下面的解決方法，我們必預要手動執行復原 Deduplication Database的工作。

方法就是從"儲存資源"->"DeDup引擎"，找到執行失敗的策略，去"所有工作"，裡面有個"復原存放區"，執行這個工作。

2024/09/09

Synology手動更新韌體失敗更新檔毀損

下載了synology的韌體更新檔後，要手動更新，結果都會跳出更新擋毀損的錯誤。

其原因是NAS主機上的韌體版本跟要更新的版本差太多，(要從6.3升到7.2)。

解決方法就是先去下載7.0.1版來手動升級，升級成功後，再手動升級最新版，就可以了。

After downloading the Synology firmware update file and attempting a manual update, an error message stating that the update file is corrupted always appears.

The reason for this is that the firmware version on the NAS is too far behind the version you're trying to update to (upgrading from 6.3 to 7.2).

The solution is to first download version 7.0.1 and manually upgrade to it. Once the upgrade is successful, you can then manually update to the latest version without issues.

訂閱：意見 (Atom)