電腦有2個ip 但dns只有一筆記錄

 網域電腦透過dhcp，留到有線與無線網路的IP，但在DNS上，都只有出現一筆，而且是出現比較晚抓到IP的那一筆。

查了一下才發現是DHCP的設定中，DNS動態更新選項，預設是選"只有在DHCP用戶端要求時才動更新dns記錄"，這個就會讓你兩個IP都在DNS上註冊。

但如果選"一律動態更新DNS記錄"，就只會出現最新的那一筆IP記錄。

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

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

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

重灌電腦 出現 "選取的磁片具有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.

Pixel 臉部解鎖後 不用確認 直接進入畫面

 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 開機一直進BIOS

  環境:

ASUS ESC700 G3

WIN7

異常狀況:

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

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

解決過程:

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

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

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

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

1111 買 Google pixel

 八月底發行的pixel手機，等到1111時，momo跟pchome大概折扣5500元。

但沒想到1112，pchome折扣6000元，還比1111便宜。

後來價格又調回了，折扣沒了。

但過了兩三天，折扣又回來了，所以之後要買pixel，希望有大一點的折扣，就是選1111之後，不一定要只在1111那天下標完成。

commvault Auxiliary Copy輔助複製的工作記錄查詢

 commvault 平常備份的記錄，都可以從用戶端電腦裡面去點選。

但Auxiliary Copy輔助複製的工作記錄查詢卻不在裡面，要先去排程策略，找到輔助複製的排程，從排從去查看工作記錄。

將來銀行 連線銀行 樂天銀行 信貸資訊

 將來銀行:

2024年年底申請，100萬，7年，利息3%，開辨費$588，綁約一年。

 

連線銀行:

2025年下半年申請轉增貸，158萬，10年，利息2.88%，開辨費$1288，綁約一年。

樂天銀行:

2025年下半年申請73萬(無轉增貸選項)，10年，利息2.72%，開辨費$0，綁約二年。

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的密碼，就可以排除這個問題。

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

1. Added a new Windows Server 2022 domain controller and transferred all five FSMO roles to it.

2. Removed the Windows Server 2012 R2 domain controller.

3. Upgraded the domain and forest functional levels to Windows Server 2016.

4. 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.

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，就可以正常進入到系統了。

netapp 建立iscsi 並掛載到windows

 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分享出來的空間。

NetApp (8.2.3P3) iSCSI Disk Creation Steps (Web Console) and Mounting on Windows Server

1. Create a Volume on NetApp

   • Go to Storage → Volumes → Create

   • Select iSCSI during the creation process and set the desired capacity.

2. Enable iSCSI Service on NetApp

   • Go to Configuration → iSCSI → Enable iSCSI

   • Enter the Target Name, which will start with iqn.

3. 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.

4. 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.

5. Create a LUN on NetApp

   • Go to Storage → LUNs → Create

   • Link the new LUN to the Volume created in step 1.

6. 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.

7. 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.

8. 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

 原本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時，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.

SYNOLOGY 共用資料夾 誰在連線的資訊

 如果使用SYNOLOGY 當共用資料夾，想看目前誰有連線，開啟了什麼檔案:

開啟"資源監控"，進到"連線"，裡面就可以查看到相關訊息。

If you are using SYNOLOGY as a shared folder and want to see who is currently connected and which files are open:

Open Resource Monitor, go to Connections, and you will be able to view the relevant information there.

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

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

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

pixel6過保送修台灣大哥大

上上週我的 Pixel 6 突然掛掉，重開機後一直卡在「G」的開機畫面。
一開始照網路教學進 fastboot 重置，沒用；接電腦想重灌系統，也失敗。最後只好送去台灣大哥大直營門市。因為已經過保，店員提醒如果不修要收 300 元檢測費。

進度可以在官網查，速度蠻快的。星期三就接到電話，說是主機板壞掉，要換新的，費用 4400，打 9 折後大概 4000。有點貴，加上 Pixel 10 快出了，本來不太想修。沒想到維修人員還問我能接受多少，說可以幫忙爭取，於是我就回說能壓在 3000 以內最好。

後來回覆說最多只能打 8 折，約 3500。雖然還是超過預算，但整個過程人員都很客氣、處理也快，最後我還是決定修。星期五就通知取貨，從星期一送修到星期五拿回來，算是蠻有效率的。

整體感覺：服務態度很好，維修速度也快，感覺很不錯。

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.

手機投影電視 小米電視盒子勝過Terzomen

 

之前為了想把手機畫面直接投影到電視上，買了Terzomen AirLink，快要1900元。

最近又買了小米盒子3，比較一下差別。

Terzomen AirLink

優點:不用特別設定，接上去就可以用了。

缺點:居然只支援apple的產品，android的手機/平板都不支援。

         接在手機那端的連結器看久還蠻燙的。

         單純就是無線傳輸影像的功能，一定要搭配手機或電腦用。

         比較貴。

小米電視盒子3

優點:apple跟android的設備都支援手機投影。

         不需要手機也有一些串流app可以看片。

          比較便宜。

缺點:一開始設定有點難用。

         需要有wifi。

相比之下，配合自己使用的環境，用小米盒子就夠了。

outlook 郵件清單 不要顯示郵件內容

 

outlook 郵件清單，除了寄件人，主旨，時間之類的，還會在下一行顯示部分的郵件內容，

讓整個郵件清單看起來很雜。

可以在檢視的功能表中，在訊息預覽裡面，選擇關閉，就不會顯示那一行郵件內容了。

In the Outlook mail list, in addition to the sender, subject, and time, part of the email content is also displayed on the next line,
which makes the entire mail list look cluttered.

You can go to the View tab and, under Message Preview, select Off to stop showing that line of email content.

M365 outlook 底色亂跳

同一個M365帳號，在兩台電腦上都設定的outlook，但設定的底色不同，結果兩台電腦上的outlook底色都會一直亂跳。

是因為outlook設定，有一個"將我的outlook設定儲存在雲端中"被打勾了，所以兩台電腦的outlook設定會互相影響，只要把這個設定取消就恢復正常了。

The same M365 account was configured in Outlook on two different computers, but each had a different theme color. As a result, the background color in Outlook kept switching back and forth on both computers.

This happened because the Outlook setting "Store my Outlook settings in the cloud" was enabled, causing the settings on one computer to affect the other. Simply unchecking this option resolved the issue.

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.

excel 沒有任何頁籤

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

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

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

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).

1. 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.

2. 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.

3. 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:

1. 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.

2. 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.

m365 office 在哪些設備啟用

 如果要查詢m365 office 帳號在哪一台設備啟用了，就要先進到Microsoft 365 admin center。

在"作用中的使用者"，點選該帳號，左邊會出現相關資訊，在最下面就有一個"檢視 ‎Microsoft 365‎ 啟用"。

裡面就會顯示在哪些裝置上啟用了這個帳號。

Next Terminal 遠端電腦鍵盤問題

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

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

WIN7無法使用FORTI SSLVPN -5029

 最近Fortigate 升級firmware後，某些win7在使用sslvpn連線都會出現 mismatch in the TLS version的錯誤。

有到網際網路選項裡，確確TLS裡面的選項 都有打勾了，還是連不到。

後來才發現是win7的有一些windows update沒安裝造成的。但不確定是哪一支更新，因為沒有一支一支測試，就是全部都裝上，就沒問題了。

After upgrading the Fortigate firmware, we observed that some Windows 7 systems encountered a "mismatch in the TLS version" error when attempting to connect via SSL VPN.

We verified that all TLS-related options were enabled under Internet Options, but the issue persisted.
Upon further investigation, we discovered that the problem was caused by missing Windows Updates on the affected Windows 7 machines.
However, we were unable to determine exactly which specific update resolved the issue, as we did not test each update individually. Instead, after applying all pending Windows Updates, the SSL VPN connection was successfully established.

PYTHON發訊息到telegram

 照著下列這編要做PYTHON發訊息到telegram(https://vocus.cc/article/67ca97aefd8978000187e654)，

結果出訊錯誤訊自 "{'ok': False, 'error_code': 400, 'description': 'Bad Request: chat not found'}"

原來是你要先在telegram搜尋到自己剛建立的bot，傳個訊息給它，才可以用python發訊息給它。

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引擎"，找到執行失敗的策略，去"所有工作"，裡面有個"復原存放區"，執行這個工作。

HP ESXI 6.5 升級7.0 U3

原本的ESXI是HP專用6.5版，為了安裝比較新的win server os，要升級ESXI。

目前ESXI已無免費版，所以是去HP的官網下載裡面最新版本的ESXI(https://support.broadcom.com/c/portal/login?formDate=1742174666301&saveLastPath=false&redirect=%2Fgroup%2Fecx%2Fproductfiles%3FsubFamily%3DVMware%2520vSphere%26displayGroup%3DVMware%2520vSphere%2520-%2520Enterprise%2520Plus%26release%3D7.0%26os%3D%26servicePk%3D202621%26language%3DEN&idpEntityId=https%3A%2F%2Faccess.broadcom.com%2Fdefault)

升級方式

1.先把iso做成開機usb，插上server。

2.server重開機，讀取usb。

3.在安裝選項的地方，選擇升級esxi。

4.安裝完成重開機。

時間很快，不到15分鐘就好了，但有一個地方要注意的事，升級後，之前使用的6.5免費版授權序號就不能用了，登入esxi web console時，就會提示目前是60天試用版。

這時只要在輸入7.0免費版的esxi序號啟動就行了，這個序號沒有分是不是用在某一廠牌伺服器專用的esxi，只要是7.0都通用。

The original ESXi was an HP-specific version of 6.5. To install a newer Windows Server OS vm, an ESXi upgrade is required.

Since ESXi no longer offers a free version, the latest version was downloaded from HP’s official website:
HP ESXi Download.

Upgrade Process:

1. Create a bootable USB from the ISO and plug it into the server.
2. Reboot the server and boot from the USB.
3. In the installation options, select "Upgrade ESXi."
4. After installation, reboot the server.

The upgrade is fast, taking less than 15 minutes. However, one important thing to note is that after upgrading, the previous ESXi 6.5 free license will no longer work. When logging into the ESXi web console, it will indicate that the current version is a 60-day trial.

To resolve this, simply enter a free ESXi 7.0 license key to activate it. This key is not brand-specific and works for any ESXi 7.0 installation.

Covered Call賠賠賠

用週選做covered call，遇到這種一直殺的盤，沒適時停損，愈賠愈多，最後受不了，心態扛不住昨晚才停損，停損後就往上噴了.....

前幾個月賺的都沒了還倒賠，做期權，紀律真的太重要了。

查詢使用者帳號可以設定電腦加入網域次數

在ad環境中，每個使用者帳號可以設定電腦加入網域10次，如果要查這個帳號剩次數可以用，可以用下列這個powershell，它會顯示已經使用幾次，下圖就是某帳號已用掉3次，還剩7次。

$UserName = "account"  # 替換為你的帳號名稱

$UserSID = (Get-ADUser $UserName).SID

Get-ADComputer -Filter * -Property ms-DS-CreatorSID | Where-Object { $_.'ms-DS-CreatorSID' -eq $UserSID } | Measure-Object

IIS 站台啟動失敗-程序無法存取檔案，因為檔案正由另一個程序使用。(發生例外狀況於HRESULT:0x80070020)

 在iis上設定了一個新的站台後，卻無法啟動，錯誤訊息是"程序無法存取檔案，因為檔案正由另一個程序使用。(發生例外狀況於HRESULT:0x80070020)"

這是因為站台上設定的port已經被別的程序使用了，可以用tcpview去確認被什麼程序給佔用了。

看是要把站台改port，會把其他佔用port的程序關閉即可。

After setting up a new site on IIS, it fails to start with the error message:

"The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)"

This issue occurs because the port assigned to the site is already in use by another process. You can use TCPView to check which process is occupying the port.

To resolve this, you can either change the site's port or terminate the process that is using the port.

透過batch安裝msu更新檔失敗-Windows 安全性更新" 無法安裝，因為發生錯誤 2149842953 "

 因為某些win11電腦透過wsus安裝累績更新時，都會顯示"正在下載 0%"，放了好幾個小時也都沒動，所以打算先把更新檔(msu檔)下載到wsus一個共用資料夾，用gpo派送，讓這些電腦一開始登入後，就開始直接用batch檔來安裝，batch檔也是放在wsus共用資料夾。

安裝指令是"wusa.exe  "\\wsus_server\offline_install\11\kb5050021.msu" /quiet /norestart"

結果執行失敗，在事件檢視器裡找到下列錯誤: Windows 更新 "KB5050021：Windows 安全性更新" 無法安裝，因為發生錯誤 2149842953 "" (命令列: "wusa.exe  "\\wsus_server\offline_install\11\kb5050021.msu" /quiet /norestart")

後來就把batch檔先複製到本機，msu檔一樣是在wsus裡，然後執行本機上的安裝batch檔，就成功安裝了。

Due to some Windows 11 computers showing "Downloading 0%" when installing cumulative updates via WSUS, even after being left for several hours with no progress, I decided to download the update file (MSU file) to a shared folder on the WSUS server. Then, I used GPO to distribute it so that these computers would start running a batch file to install the update directly upon login. The batch file is also stored in the WSUS shared folder.

The installation command used is:

wusa.exe "\\wsus_server\offline_install\11\kb5050021.msu" /quiet /norestart

However, the execution failed. In the Event Viewer, I found the following error:

"Windows update 'KB5050021: Windows Security Update' could not be installed because of error 2149842953"

(Command line: wusa.exe "\\wsus_server\offline_install\11\kb5050021.msu" /quiet /norestart)

Later, I tried copying the batch file to the local machine while keeping the MSU file in the WSUS shared folder. After executing the batch file locally, the installation succeeded.

win11第一次設定 一定要有網路嗎

  一台新的win11筆電開機後，進入初始設定，過程中一定要求一定要連上外部網路，連不上的話就會卡在這一步，沒辦法略過。

解決方法就是 按下Shift+F10，就會跳出指令視窗，接著輸入這個指令 oobe\bypassnro

然後系統就會重開始，又回到進入初始設定，過程中連上外部網路這一個階段，就會多了一個略過的按鈕可以點選，繼續後面的設定。

When setting up a new Windows 11 laptop for the first time, during the initial setup process, you're required to connect to an external network. If you're unable to connect, the setup will be stuck at this step without an option to skip it.

To solve this issue, press Shift + F10, which will open the command prompt. Then, enter the following command: oobe\bypassnro.

The system will restart and return to the initial setup process. At the stage where it asks you to connect to an external network, there will now be a "Skip" button, allowing you to bypass this step and continue with the rest of the setup.

永豐證券質押第一次展延

 永豐證券質押三檔股票，利率2.6%，六個月要到期了，就在LINE上問了營業員怎麼展延，利率多少，是不是就照官網上公告的。

營業員查了一下，展延的話，利率變3.3%，比官網上公佈的差不多，確定要的話，他就會打來錄音確認我要展延，會在電話中說明展延的一些細節。

因為質押的數量不多，也沒看到有其他利率便宜很多的，就決定展延了。

平均起來還不到3%，還可以接受。

wsus 清除空間

  wsus 時間久了，資料愈來愈多，執行伺服器清理精靈，也清不了什麼東西。

這時就要把之前核准過，但已經被取代的老舊更新，通通設定拒絕，然後才執行伺服器清理精靈，才能清掉那些用不到的更新，清出磁碟空間。

Over time, WSUS accumulates more and more data, and running the Server Cleanup Wizard doesn’t effectively clean up much.

At this point, you need to set previously approved but superseded updates to "Declined." Then, run the Server Cleanup Wizard again to remove those unnecessary updates and free up disk space.

win11 安裝語言套件 擱置中

  重灌好的win11中文版，馬上改成英文版，語言套件安裝都很順利。

但切換別的帳號時，一樣還是中文版，需要重新安裝，可是這時語言套件這個項目一直顯示擱置中，沒辦法裝成功。

後來查了一下才發現，是windows defender搞的鬼，因為一開始改好英文版，有順便執行windows update，有更新的windows defender，之後別的帳號登入就沒辦法安裝語言套件。

這時就是把防火牆通通關閉，然後新增一個機碼，HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender\ 底下新增一個dword32位值，名稱是"DisableAntiSpyware"，值設成1，然後重開機。

再進行一次語言套件安裝，就成功了。

After reinstalling Windows 11 in Chinese, I immediately switched it to English. The language pack installation went smoothly.

However, when switching to another user account, the interface was still in Chinese, and I had to reinstall the language pack. At this point, the language pack installation kept showing as "Pending" and couldn’t be completed successfully.

After some investigation, I discovered that the issue was caused by Windows Defender. Initially, after switching to English, I also ran Windows Update, which included updates for Windows Defender. Afterward, other user accounts couldn’t install the language pack.

To fix this, I disabled the firewall completely and added a registry key under:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender\
I created a new 32-bit DWORD value named "DisableAntiSpyware" and set its value to 1, then restarted the computer.

Once I did this, I was able to successfully install the language pack.

Microsoft 365 商務標準版 (不含 Teams) outlook問題-無法傳送此邀請。因為文中的teams會議詳細資料與此會議不同。

 

使用Microsoft 365 商務標準版 (不含 Teams) 的outlook，雖然沒有teams授權，但發送會議通知時，預設會自動產生一個eams會議連結。

若把該連結刪除，換上其他teams帳號產生的會議連結上去，就會無法傳送，跳出下列錯誤"無法傳送此邀請。因為文中的teams會議詳細資料與此會議不同。您希望我們修正會議邀請嗎?"。

解決方法:

到outlook選項中的行事曆，裡面的行事曆選項，把"新增線上會議室所有會議"打勾取消。

之後在建立會議時，就不會自動產生teams連結，會議裡就可以放入別的teams帳號建立的連結了。