環境:
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.
環境:
用commvault 備份Oracle 資料庫，要還原時，在裡面都只看到dbf檔，無法顯示裡面的資料表。
解決過程:
commvault 備份Oracle 資料庫的設定，如果沒勾選"啟用表格瀏覽"，就看不到裡面的資料表，這邊的表格，就是指資料表Table的意思。
如果沒有勾選這個功能，還原就會變的很麻煩
若您過去的備份沒有啟用此功能，當有人誤刪資料時：
還原邏輯： 您無法在 Commvault 介面看到「表」的清單，只能看到「資料庫」。
必須全機還原： 您必須像現在一樣選擇 RMAN Duplicate DB，把整個資料庫（數百 GB 或 TB）還原，變成一個資料庫。
手動撈取： 您得自己連進資料庫，下 SQL 或用 expdp 撈出那張表，再手動匯入回 。
缺點： 極度消耗 磁碟空間，且還原時間很長（因為要搬動所有資料檔）。
如果您現在勾選並完成了一次新的完整備份：
還原邏輯： 在「瀏覽」視窗切換到 Table View，您可以直接看到裡面的所有使用者與資料表清單。
精準還原： 您只需要勾選「被誤刪的那張表」。
自動化輔助實例： Commvault 會自動在Staging Path 建立一個「最小化」的臨時實例。它只會還原必要的系統檔案和該表所在的 Tablespace，而不是整個資料庫。
優點： 節省大量磁碟空間（可能只需還原 10% 的資料量），且 Commvault 會自動完成匯出與匯入的動作。
Environment:
When using Commvault to back up an Oracle database, during restore operations only .dbf files are visible, and the tables inside the database cannot be displayed.
Resolution Process:
In the Commvault Oracle database backup settings, if “Enable Table Browse” is not selected, database tables will not be visible.
Here, “Table” refers to database tables.
If this option is not enabled, restoration becomes very complicated.
If past backups were performed without this option enabled and a table is accidentally deleted:
Restore logic:
You cannot see a list of tables in the Commvault interface. You can only see the database as a whole.
Full database restore required:
You must perform an RMAN Duplicate DB, restoring the entire database (hundreds of GBs or even TBs) as a separate database instance.
Manual data extraction:
You must manually connect to the database, run SQL queries, or use expdp to export the required table, then manually import it back.
Drawbacks:
Extremely high disk space consumption and very long restore times, since all data files must be restored.
If you enable this option now and complete a new full backup:
Restore logic:
In the Browse window, switch to Table View, and you can directly see all users and their tables.
Precise restore:
You only need to select the specific table that was accidentally deleted.
Automated auxiliary instance:
Commvault will automatically create a minimal temporary instance in the Staging Path.
It restores only the required system files and the tablespace containing the selected table, rather than the entire database.
Advantages:
Significant disk space savings (possibly restoring only around 10% of the data), and Commvault automatically handles the export and import process.
The following article provides a more detailed explanation:
https://itnoesis.com/2020/09/20/oracle-rac-table-restore-using-commvault/
環境:
網域中某台DC有狀況，已無法正常與其他DC同步提供服務，或無法在登入使用之類的狀況。
因無法以正常的方式降級DC角色(dc-a)，必須以其他方式移除該DC主機角色
解決過程:
假設五大角色並是在正常的DC主機(dc-b)中，我們就到該DC主機中做下列兩個步驟:
1. 開啟"Active Directory站台及服務" ，這邊會有每台DC，還有它跟哪些DC同步。
在裡面找到需移除的DC，都它們都刪掉，這樣正常的DC才不會去找它做同步。
2. 在DNS裡，正向對應區域裡，需移除的DC，通通移除掉(包含底下其他資料夾底下的資料)，這樣才能確認其他主機透過DNS要詢問資訊時，不會回應錯誤的資訊。
環境:
Linux 主機A，要設定排程，傳送特定檔案給Linux 主機B。
不想用帶有Linux 主機B的明碼帳號密碼 shell。
解決過程:
使用SSH Key-Based 身份驗證
A. 準備階段 (在 A主機 上)
Bash
cat
~/.ssh/id_dsa.pub
複製輸出的整行內容（從
ssh-dss 到最後的備註）。
B. 執行貼上與權限設定 (在 B主機上)
Bash
ssh
<B主機username>@<B主機IP>
Bash
mkdir
-p ~/.ssh
chmod
700 ~/.ssh
請務必使用雙引號 >> 進行追加，避免覆蓋：
Bash
echo
"[您複製的公鑰內容]"
>> ~/.ssh/authorized_keys
Bash
chmod
600 ~/.ssh/authorized_keys
安全性注意
手動方式的最大風險就是權限設定。如果 ~/.ssh 或
~/.ssh/authorized_keys 的權限設定不正確 (例如太寬鬆，允許其他使用者寫入)，SSH 伺服器會拒絕使用金鑰認證，並提示錯誤。
驗證階段 (無論使用哪個方法，必須進行)
在 A主機上執行：
Bash
ssh <B主機username>@<B主機IP>
如果設定成功，系統將不會要求您輸入密碼，而是直接顯示 B主機的命令列提示符。
如果連線成功，您可以輸入 exit 退出，然後繼續設定您的 Cron Job。
環境:
Google blogger + adsense
異常狀況:
多年前我的 blogger有申請adsense，想賺點廣告費，一開始的確也有看到有廣告收到，但大概在兩三年前，發現收入一直沒增加，點開網站才發現通通都沒廣告了。
但在adsense上的設定都沒去調整，狀態都是正常的，也設定了自動廣告，版面上也有設定廣告的視窗。
但就是沒廣告。
解決過程:
之前上網查都沒什麼有用的解決。
後來gemini出現了，就想說問它看看，結果gemini說要在主題裡，用html編輯，插入一段語法，結果插入存檔後。
直接重新開啟網頁，裡面廣告馬上就出現了，太神奇了。
gemini的說明如下:
檢查自動化廣告的程式碼（重要！）
在 Blogger 後台，進入 「主題」(Theme) 或 「範本」 設定。
點擊 「編輯 HTML」(Edit HTML)。
請檢查在 HTML 程式碼中，<head> 標籤之後，是否存在以下格式的 AdSense 程式碼片段：
<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:
(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.
環境:
重灌WIN11，m365 office，Solidworks
異常狀況:
Solidworks 有出現錯誤"字型 arial unicode ms 未被正確的安裝 在pdf檔案中的一或多個文字字串可能遺失"
解決過程:
Office 2016 版之後不再維護這字型，在另存 PDF 會出現此問題。
下載該字型進行安裝即可。
代理商也有提供教學影片與字型載點。
https://www.youtube.com/watch?v=jWgUT9Op2kU
Environment:
Fresh install of Windows 11, Microsoft 365 Office, Solidworks
Issue:
Solidworks displayed an error: "Font 'Arial Unicode MS' was not installed correctly. One or more text strings in the PDF file might be missing."
Solution:
This font is no longer maintained after Office 2016, which causes this problem when saving files as PDF. The issue can be resolved by downloading and installing the font. The authorized distributor has also provided a tutorial video and a font download link.
https://www.youtube.com/watch?v=jWgUT9Op2kU
網域電腦透過dhcp，留到有線與無線網路的IP，但在DNS上，都只有出現一筆，而且是出現比較晚抓到IP的那一筆。
查了一下才發現是DHCP的設定中，DNS動態更新選項，預設是選"只有在DHCP用戶端要求時才動更新dns記錄"，這個就會讓你兩個IP都在DNS上註冊。
但如果選"一律動態更新DNS記錄"，就只會出現最新的那一筆IP記錄。
A domain-joined computer obtains both wired and wireless IP addresses through DHCP, but only one record appears in DNS, and it is always the one obtained later.
After checking, I found that this is caused by the DHCP setting for dynamic DNS updates. By default, it is set to “Dynamically update DNS records only if requested by the DHCP client,” which results in both IP addresses being registered in DNS.
However, if you change it to “Always dynamically update DNS records,” only the most recent IP address will appear in DNS.
win11安裝solidworks 後，出現一些功能表中文是亂碼、有中文名稱的STEP檔無法開啟
要進到"選用功能"，把"台灣地區"這個選項解除安裝。
環境:
DEll筆電，要重灌WIN11
異常狀況:
用WIN11 USB重灌電腦時， 出現 "選取的磁片具有mbr磁碟分區表格....." 錯誤，裡面只有顯示USB磁碟，但電腦內的硬碟卻沒抓到。
解決過程:
進入到bios設定中，去storage裡面，原本是選擇raid on，改成ahci/nvme，在重開機，就可以正常重灌系統了。
Pixel 手機預設臉部解鎖後，還是會要你點選螢幕，做一個確認的動作。
如果要希望就直接進入操作畫面，不要這個確認的動作，就在臉部解鎖的設定裡面，有一個略過螢幕鎖定畫面，把它啟用就好了。
"By default, Pixel phones still require you to tap the screen to confirm after using Face Unlock. If you want to go straight to the home screen and skip this step, just go to your Face Unlock settings and enable Skip lock screen."
環境:
ASUS ESC700 G3
WIN7
異常狀況:
當機之後，開機就會一直直接進到BIOS，從BIOS裡的資訊看的出來有抓到硬碟。
但把線重新拔插，重開機後，還是一樣狀況
解決過程:
把該硬碟接到別台主機，可正常開機。
拿其他台電腦的硬碟來接上有問題的主機，也可正常開機。
所以判斷硬碟跟主機板都沒問題，應該就是BIOS設定問題。
BIOS設定裡面的"啟動"->"作業系統類型"，本來是選擇"windows uefi模式"，將它改成"其他作業系統"，然後重開機後就正常了。
八月底發行的pixel手機，等到1111時，momo跟pchome大概折扣5500元。
但沒想到1112，pchome折扣6000元，還比1111便宜。
後來價格又調回了，折扣沒了。
但過了兩三天，折扣又回來了，所以之後要買pixel，希望有大一點的折扣，就是選1111之後，不一定要只在1111那天下標完成。
commvault 平常備份的記錄，都可以從用戶端電腦裡面去點選。
但Auxiliary Copy輔助複製的工作記錄查詢卻不在裡面，要先去排程策略，找到輔助複製的排程，從排從去查看工作記錄。
將來銀行:
2024年年底申請，100萬，7年，利息3%，開辨費$588，綁約一年。
連線銀行:
2025年下半年申請轉增貸，158萬，10年，利息2.88%，開辨費$1288，綁約一年。
樂天銀行:
2025年下半年申請73萬(無轉增貸選項)，10年，利息2.72%，開辨費$0，綁約二年。
環境:
DC主機作業系統: win2022 & win2025
網域&樹系功能等級: 2016
異常狀況:
win2025dc剛登入系統後，連線任何dc的共用資料夾都是正常的，但大概半小時後，就無法連線，會跳出存取被拒的視窗，要求重新輸入帳號密碼。而且畫面右下角還會跳出"windows需要您目前的認證"
環境:
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小時後重設第二次，所有隔天有再重設一次。
Existing DC Operating System: Windows Server 2012 R2
Domain & Forest Functional Level: Windows Server 2003
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.
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.
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.
netapp(8.2.3P3 )建立iscsi磁碟步驟(web console操作)，並在windows server掛載:
1 在netapp的Storage -> Volumes ，執行Create，建立過程要選iscsi，並設定容量。
2 在netapp的Configuration-> iSCSI，啟用iscsi服務，要輸入目標節點名稱，會是iqn開頭的值。
3 在Windows 執行iscsi啟動器，輸入netapp的IP進行連線，連線成功，此時會在目標的頁籤看到netapp的節點名稱，如果剛剛在第二步沒找到節點名稱，就是輸入這個。
4 在設定這個頁籤，可以看到Windows 的啟動器名稱，也是iqn開頭的值，但跟netapp的節點名稱不一樣。
5 在netapp的Storage-> LUN，LUN管理裡執行Create一個LUN，這邊會連結到第一步建立的Volumes。
6 在netapp的Storage-> LUN，Initiator Group建立一個Group，建立時，會需要輸入第四步的Windows 的啟動器名稱。
7 在netapp的Storage-> LUN，LUN管理裡剛剛建立的LUN，連結到第六步建立的Initiator Group。
8 回到Windows 執行iscsi啟動器，重新連線，這時後再去磁碟管理中，就會看到多了一個新的磁碟，就是Netapp上iscsi分享出來的空間。
Create a Volume on NetApp
Go to Storage → Volumes → Create
Select iSCSI during the creation process and set the desired capacity.
Enable iSCSI Service on NetApp
Go to Configuration → iSCSI → Enable iSCSI
Enter the Target Name, which will start with iqn.
Connect from Windows using iSCSI Initiator
Open the iSCSI Initiator on Windows and enter the NetApp IP to connect.
Once connected, you will see the NetApp Target Name under the Targets tab.
If you couldn’t find the Target Name in step 2, enter the one displayed here.
Check Windows Initiator Name
In the Configuration tab of the iSCSI Initiator, you can see the Windows Initiator Name, which also starts with iqn but is different from the NetApp Target Name.
Create a LUN on NetApp
Go to Storage → LUNs → Create
Link the new LUN to the Volume created in step 1.
Create an Initiator Group (igroup) on NetApp
Go to Storage → LUNs → Initiator Groups → Create
Enter the Windows Initiator Name from step 4 when creating the igroup.
Map the LUN to the Initiator Group
In Storage → LUNs, select the newly created LUN and map it to the igroup created in step 6.
Mount the LUN on Windows
Go back to Windows and reconnect using the iSCSI Initiator.
Then open Disk Management, and you should see a new disk representing the iSCSI space shared from NetApp.
原本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.
網域的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.