ESXi 6.5 的windows 2012虛擬機傳送ctrl alt del沒反應

在ESXi 6.5架設了一台windows 2012虛擬機，開啟了遠端桌面連線的功能，都可以使用，接著安裝了vmtool重開機後，使用chrome透過esxi的web console要登入主機時，傳送ctrl alt del沒反應。

使用遠端桌面連線，輸入完帳號密碼後，也都連不上，非常奇怪。

查了一下google，vmware有一篇文章是說要升級esxi，這個就先不考慮。

在經過一些測試後發現，是透過windows update進行更新時，會有一個vmware的套件，安裝了這個後，才會有傳送ctrl alt del沒反應的問題，所以在做windows update時不要裝這個套件就好了。

I have set up a Windows 2012 virtual machine on ESXi 6.5 and enabled the Remote Desktop Connection feature, which was working fine. Then I installed vmtools and rebooted the virtual machine. After that, when I tried to log in to the host using Chrome via ESXi's web console and sent Ctrl+Alt+Del, there was no response.

I also tried using Remote Desktop Connection, but after entering the username and password, I couldn't connect, which is very strange.

After searching on Google, I found an article from VMware suggesting upgrading ESXi, but for now, I'm not considering that option.

After some testing, I discovered that when updating through Windows Update, there is a VMware package that, when installed, causes the issue with Ctrl+Alt+Del not working. So, when performing Windows Update, it's advisable not to install this package.

Excel 下方的分頁頁籤不見了

 EXCEL檔案不同的分頁，通常都在左下方可以做點選切換。

但某些檔案明明就有多個分頁，但下方卻都沒東西，無法切換。

這是設定的問題，只要在進階的設定裡，找到 顯示工作表索引標籤，將此功能打勾就會正常顯示其他分頁了。

Different worksheets in an Excel file are usually switchable by clicking on the tabs located at the bottom left.

However, in some cases, even though a file has multiple worksheets, there is no content displayed at the bottom, and switching between them is not possible.

This is a configuration issue. By going into the advanced settings and enabling the "Show sheet tabs" option, the other worksheets will be displayed correctly.

IBM x345 亮橘燈

 有一台非常老舊的IBM x345，前面面板出現了硬體故障的橘燈，但這台伺服器的面板沒有其他資訊，就只燈號可以看。

檢查了外觀，硬碟都正常，沒其他亮橘燈的地方，就查不到橘燈是什麼地方異常造成的。

查看原廠文件，有說明主機板上會有其他硬體的燈號，有問題的就會亮橘燈。

所以就關閉系統，但接著電腦線，將上蓋打開，果然看到記憶體插槽上有亮橘燈，終於找到問題。

更妙的時打開上蓋後，發現有一個小面板藏在裡面，上面就有顯示哪個硬體故障，實在想不通為何要把這個面板藏在裡面。

回去查原廠文件，裡面還真的有寫到這個診斷面板是在伺服器裡面。

There is an old IBM x345 server that has a hardware failure indicated by an amber light on the front panel. However, the server's panel does not provide any additional information, only the indicator light is visible.

Upon inspecting the physical appearance, the hard drives appear to be functioning properly, and there are no other areas with illuminated amber lights, making it difficult to determine the source of the issue.

Referring to the manufacturer's documentation, it mentions that there are other hardware indicator lights on the motherboard, which would illuminate if there were any problems.

Therefore, shut down the system, and the computer cables were connected. Upon opening the server's cover, it was discovered that there was indeed an illuminated amber light on one of the memory slots, finally identifying the problem.

Interestingly, upon opening the cover, a small panel was found hidden inside, displaying the specific hardware component that was experiencing the failure. It is weird why this panel was concealed inside the server.

Upon revisiting the manufacturer's documentation, it was confirmed that this diagnostic panel is indeed located inside the server.

FreeFileSync 同步檔案時出現 sync.ffs_lock的相關錯誤 code error 5: Access refuse [create file]

 在win2019透過freefilesync要把遠端win2003的檔案同步過來本機的時後，有些資料夾都會出現錯誤，內容都是在本機端的資料夾中 sync.ffs_lock有錯誤， code error 5: Access refuse [create file]。

照字面上的意思應該就是同步的過程程式要產生一個sync檔，但無法建立。

可是我在本機端自己建立檔案時，都沒什麼異狀，就覺得很怪。

後來就手動用複製貼上檔案的方式，發現有時後會跳出錯誤訊息，大概就是說沒有權限，要用系統管理者執行之類的，可是我就是用本機管理者帳號在執行啊。

這時突然想到，那執行freefilesync時，要用系統管理者身份去執行，有三四個在同步會跳錯誤的資料夾，就通通都沒問題了。

When using FreeFileSync on Windows Server 2019 to sync files from a remote Windows Server 2003 to the local machine, some folders encounter errors. The error message states that there is an issue with the "sync.ffs_lock" file in the local folder, with error code 5: Access refused [create file].

According to the literal meaning of the error, it seems that the sync process is unable to create the "sync" file.

However, I noticed that there were no issues when manually creating files on the local machine, which struck me as odd.

Later, while manually copying and pasting files, I encountered occasional error messages indicating a lack of permission and suggesting the need for administrator privileges. However, I was already using the local administrator account to perform the operation.

At this point, it occurred to me that when running FreeFileSync, it should be executed with administrator privileges. When I ran the program as an administrator, the folders that were previously causing errors during synchronization, about three or four of them, synced without any problems.

pyinstaller py轉exe出現錯誤:The 'pathlib' package is an obsolete

 在用pyinstaller把一個py檔要轉成exe執行檔時，出現下列錯誤

The 'pathlib' package is an obsolete backport of a standard library package and is incompatible with PyInstaller. Please remove this package (located in C:\Users\helloeveryone\Anaconda3\lib\site-packages) using  conda remove then try again.

這時就執行 pip uninstall pathlib ，把pathlib移除就好，移除後不需要再重裝一次。

之後執行pyinstaller，就可以成功把py轉成exe了。

When using PyInstaller to convert a .py file into an executable (.exe) file, the following error occurs:

"The 'pathlib' package is an obsolete backport of a standard library package and is incompatible with PyInstaller. Please remove this package (located in C:\Users\helloeveryone\Anaconda3\lib\site-packages) using conda remove then try again."

To resolve this, execute "pip uninstall pathlib" to remove the pathlib package. After removing it, there is no need to reinstall it.

Afterward, running PyInstaller should successfully convert the .py file into an .exe file.

安裝ocs agent 出現錯誤 api-ms-win-crt-heap-l1-1-0.dll

 64位系統安裝請安裝：

Visual C++ Redistributable for Visual Studio 2015 (Windows 64-bit)

32位系統安裝請安裝：

Visual C++ Redistributable for Visual Studio 2015 (Windows 32-bit)

When installing the OCS agent, an error occurs: api-ms-win-crt-heap-l1-1-0.dll.

For 64-bit systems, please install:

Visual C++ Redistributable for Visual Studio 2015 (Windows 64-bit).

For 32-bit systems, please install:

Visual C++ Redistributable for Visual Studio 2015 (Windows 32-bit).

透過瀏覽器(web)使用Teams 會議 聲音非常小

 使用teams程式開會音量正常，但用瀏覽器開會時，聲音超級小，喇叭已調到最大聲了，還是沒用，其他程式的聲音都正常，唯讀teams有問題。

原來是win10的音效設定，可以針對各別程式設定音量，所以要去音效裡做調整。

When using the Teams application, the volume during meetings is normal. However, when using a web browser for meetings, the sound is extremely low. Even with the speakers set to maximum volume, the issue persists. The sound in other applications is normal, indicating that Teams is the only program with this problem.

The cause of the issue lies in the audio settings of Windows 10, which allows for individual volume adjustments for each program. Therefore, it is necessary to adjust the settings in the sound configuration panel.

網域DC時間錯誤造成client電腦時間也錯了

 一台虛擬機DC的時間被設定成與底層hyperv系統同步，結果與正確的時間差了一分多鐘。

PDC的時間是正確的，所以並不是所有client電腦的時間都錯了，就看是抓到哪台DC做時間同步。

時間錯誤的DC一開始就直接用NTPCLOCK這個小工具調整成對的時間，但沒多久又變回錯的時間，在該伺服器執行"w32tm /query /configuration"，有看到有一區"VMICTimeProvider"的設定，enable=1，這就是設定成與底層hyperv系統同步的地方。

直接找到HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\VMICTimeProvider ，把enable改成0就好，不用重開機，然後在用NTPCLOCK調成正確時間就行了。

Client端如果不想等重開機做時間同步的話，可以下指令直接強制同步。

要用系統管理員執行cmd，然後輸入 w32tm /resync就可以開始同步了，時間不會馬上就變正確的，而且會慢慢的縮小與正確時間的差距，所以要等一下。

可以開啟client的時鐘，如果是client的時間是比較慢，就會發現秒數有時後會跳的比較快，然後慢慢跟上正確的時間。

Domain Controller Time Error Causing Incorrect Client Computer Time

The time of a virtual machine Domain Controller (DC) was initially set to synchronize with the underlying Hyper-V system, but it ended up being more than a minute off from the correct time.

The time displayed on PDC files was accurate, indicating that not all client computers had incorrect time settings. It depended on which DC the clients synchronized their time with.

Initially, the DC with the time error was adjusted using a small utility called NTPCLOCK to set the correct time. However, after a short while, it reverted back to the incorrect time. When running the command "w32tm /query /configuration" on the server, the configuration showed a section called "VMICTimeProvider" with enable=1, indicating synchronization with the underlying Hyper-V system.

To resolve this, the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\VMICTimeProvider was located, and the "enable" value was changed to 0. There was no need to restart the server. Afterward, the correct time could be set using NTPCLOCK.

For client computers that didn't want to wait for a reboot to synchronize their time, a command could be executed to force synchronization. By running cmd as an administrator and entering "w32tm /resync," the synchronization process would begin. The time wouldn't immediately become correct but would gradually narrow the gap with the accurate time. Patience was required.

Observing the client's clock, if the client's time was slower, one would notice that the seconds occasionally jumped ahead and slowly caught up with the correct time.

弱點掃描 Vulnerable' cipher suites 處理

在用弱點掃描軟體做伺服器弱點檢查時，有些主機有下列這個弱點被掃出: 

Vulnerable' cipher suites accepted by this service via the TLSv1.0 protocol:

TLS_RSA_WITH_3DES_EDE_CBC_SHA (SWEET32)

'Vulnerable' cipher suites accepted by this service via the TLSv1.1 protocol:

TLS_RSA_WITH_3DES_EDE_CBC_SHA (SWEET32)

'Vulnerable' cipher suites accepted by this service via the TLSv1.2 protocol:

TLS_RSA_WITH_3DES_EDE_CBC_SHA (SWEET32)

就是有3個TLS的連線協定用了不安全的密碼套件TLS_RSA_WITH_3DES_EDE_CBC_SHA。

網路上比較多的解決方法是用IISCrypto這套軟體，免安裝，直接在伺服器上執行，它會列出很多種連線協定跟密碼套件，把你不要的取消勾選按下套用，重開機，就好了。

也有人說要去改機碼，只是比較麻煩，用IISCrypto比較快。

所以我就在查了一下IISCrypto跟改機碼差在哪，結果是一樣的，IISCrypto背後的方式也是改機碼。

所以就決定自己用改機碼的方式在處理:

因為三個連線協定都是用同一個有問題的密碼套件，因此直接先停用這個密碼套件看看。

原本在Chiphers底下是沒有Triple DES 168，就直接新增，加入這段機碼

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\Triple DES 168]

"Enabled"=dword:00000000

好了之後不用重開，直接在掃一次，就沒有這三個弱點出現了。

When conducting a vulnerability scan to check for server weaknesses, some hosts may exhibit the following vulnerability:

Vulnerable cipher suites accepted by this service via the TLSv1.0 protocol:

TLS_RSA_WITH_3DES_EDE_CBC_SHA (SWEET32)

Vulnerable cipher suites accepted by this service via the TLSv1.1 protocol:

TLS_RSA_WITH_3DES_EDE_CBC_SHA (SWEET32)

Vulnerable cipher suites accepted by this service via the TLSv1.2 protocol:

TLS_RSA_WITH_3DES_EDE_CBC_SHA (SWEET32)

These vulnerabilities involve the usage of insecure cipher suites, specifically TLS_RSA_WITH_3DES_EDE_CBC_SHA, across all three TLS connection protocols.

One commonly suggested solution found online is to use a software called IISCrypto. It can be executed directly on the server without installation. IISCrypto provides a comprehensive list of connection protocols and cipher suites, allowing users to deselect undesired options, apply the changes, and then reboot the server.

Another approach involves modifying the registry, although this method is considered more cumbersome compared to using IISCrypto, which is faster.

After researching the differences between IISCrypto and registry modification, I discovered that they achieve the same result, as IISCrypto utilizes changes to the registry behind the scenes.

Therefore, I decided to handle the issue by modifying the registry myself:

Since all three connection protocols employ the same problematic cipher suite, the first step was to disable this specific cipher suite.

Initially, the "Triple DES 168" option was not present under the Chiphers section, so I added it directly by inserting the following registry key:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\Triple DES 168]

"Enabled"=dword:00000000

After applying this modification, there was no need to restart the system. Running another scan revealed the absence of the aforementioned three vulnerabilities.

Greenbone Security Assistant 掃描錯誤 : Interrupted at 0 %

之前建了一台 Greenbone Security Assistant做弱點掃描，都很正常，掃完就沒管它，過了快一個月，要在掃一些之前掃過的主機時，工作開始後沒多久就會出現"Interrupted at 0 %"的錯誤，重試幾次都一樣，也沒找到什麼資訊，直接重開機吧。

然後就好了!!!!

Greenbone Security Assistant Scanning Error: Interrupted at 0%

Previously, I set up a Greenbone Security Assistant for vulnerability scanning, and everything was working fine. Once the scans were completed, I didn't pay much attention to it. After almost a month, when I tried to scan some hosts that were previously scanned, I encountered an error shortly after starting the scan, stating "Interrupted at 0%". I retried several times, but the error persisted, and I couldn't find any helpful information. Eventually, I decided to restart the machine.

And guess what? The issue was resolved after the restart!

突然連不到共用資料夾 error code:0x8007003

 某電腦突然無法連線到任何共用資料夾，不管是windows分享的或nas分享的。

直接ping分享的主機名稱或ip都有通，但要連資料夾都會出現0x8007003的錯誤。

查了一下，原來是dns client這個服務被關閉了，預設應該要是自動才對，把這個服務在啟動後，問題就解決了。

Suddenly unable to connect to the shared folder error code: 0x8007003

A certain computer suddenly cannot connect to any shared folders, whether they are shared through Windows or NAS.

Directly pinging the hostname or IP of the shared host is successful, but when trying to connect to the folders, an error with the code 0x8007003 appears.

Upon investigation, it was discovered that the DNS client service had been disabled. It should be set to automatic by default. After starting this service, the issue was resolved.

OPENVAS(GVM)進行弱點掃描會造成網域帳號被鎖住

在使用 OPENVAS對內部電腦進行弱點掃描，發現一個問題，就是會造成一些AD帳號因輸入太多次錯號密碼被鎖住。

個人猜測是在做掃描時，可能會隨便找一些帳號做登入測試，剛好有人的帳號就是一樣的，所以就被鎖了。

帳號被鎖，可以參考下列這個網站的教學，來查是哪一台設備在在做登入驗證的行為。

https://evotec.xyz/active-directory-how-to-track-down-why-and-where-the-user-account-was-locked-out/

OPENVAS(GVM) Vulnerability Scanning Causing Domain Account Lockouts

During the use of OPENVAS for vulnerability scanning on internal computers, I encountered an issue where it resulted in some AD accounts getting locked due to multiple incorrect password attempts. My personal speculation is that during the scanning process, the tool may attempt to log in using random accounts, and if there happens to be a match with a valid account, it leads to the account being locked.

To determine the source of the account lockouts, you can refer to the tutorial provided on the following website. It explains how to track down the device responsible for the login authentication attempts:

https://evotec.xyz/active-directory-how-to-track-down-why-and-where-the-user-account-was-locked-out/

centos 8 yum 更新失敗 - 同步倉庫 'AppStream' 快取失敗，忽略這個 (Failed to synchronize cache for repo)

新架了一台Centos 8的主機，要用yum先做一些元件更新時，都會跳出同步baseos/appstream/extract 快取失敗的問題。

查了一下，原來是centos8的repo路徑有變，但設定檔裡的路徑還是舊的，所以要改掉。

設定檔的路徑在/etc/yum.repos.d/，裡面有很多xxx.repo檔，檔案裡都有一個baseurl=httpxxxxxxxxxxxxxxxxxxxxxx的路徑，要改掉。

大部分國外的網站都說是把原本的mirror.centos.org改到vault.centos.org，大陸那邊的網站則是說改到http://mirrors.cloud.aliyuncs.com。

後來研究了很久，自己是改到https://mirrors.aliyun.com/centos/8-stream/xxxxxxx，這個網站可以直接用瀏覽器連上，後面的xxxx是要看你的錯誤訊息，看你是哪個快取找不到，就去網站上找到相對應的路徑，貼到設定檔上，就行了。

如果出現下列訊息，也會有可能是提供的網站已不存在，所以會有403的錯誤碼。

搞了兩天才弄好，分享給大家看一下，另外就是防火牆要注意，因為後來發現設定沒錯，但還是連不上，是因為自己的防火牆有擋一些東西，所以如果設定改好還失敗，可以查檢一下防火牆。

CentOS 8 Yum Update Failure - Failed to Synchronize Cache for 'AppStream' Repository

I encountered an issue with my newly deployed CentOS 8 server where I couldn't perform component updates using Yum. Every time I tried, I received an error indicating the failure to synchronize the baseos/appstream/extract cache.

After investigating, I discovered that the repository paths for CentOS 8 had changed, but the configuration files still contained the old paths, requiring modification. The configuration files are located in /etc/yum.repos.d/ and contain multiple xxx.repo files. Within each file, there is a baseurl=httpxxxxxxxxxxxxxxxxxxxxxx path that needs to be updated.

Most foreign websites suggested replacing the original mirror.centos.org with vault.centos.org, while some Chinese websites recommended using http://mirrors.cloud.aliyuncs.com. After extensive research, I found that modifying it to https://mirrors.aliyun.com/centos/8-stream/xxxxxxx worked for me. This website can be accessed directly through a browser, and the xxxxxx part depends on the error message you receive. Look for the corresponding path on the website and paste it into the configuration file.

If you encounter the following message, it's possible that the provided website no longer exists, resulting in a 403 error code.

After spending two days troubleshooting, I wanted to share this solution. Additionally, be mindful of your firewall settings. In my case, even though my configuration was correct, I still couldn't establish a connection. It turned out that my firewall was blocking certain elements. So, if you've made the necessary configuration changes but are still experiencing issues, check your firewall settings.

win虛擬機無法正常運作 開機出現錯誤 0xC0000017

 今天把一台esxi的虛擬機做還原後，開機出現錯誤，錯誤代碼是0xC0000017，還說什麼系統檔案可能有錯誤，安全模式或回複到上次正常啟動都沒用。

最後就進設定看，發現，記憶體設定只有16m，好小啊，調成16g後，就可以正常開機了，虛驚一場。

Unable to Boot Win Virtual Machine - Error 0xC0000017

Today, after restoring a virtual machine on ESXi, I encountered an error during the boot process. The error code was 0xC0000017, indicating a possible issue with the system files. I tried starting in Safe Mode and even attempted to revert to the last known good configuration, but none of these options resolved the problem.

In a final attempt to troubleshoot, I accessed the settings and discovered that the memory allocation was set to a mere 16MB. It was a surprisingly low value. After adjusting it to 16GB, the virtual machine was able to boot up successfully. It turned out to be a false alarm, and the issue was resolved.

SQUID Proxy無法連線內部https網站-NONE/503 0 CONNECT

 用SQUID架好Proxy Server後，都蠻順利的，開網站，用LINE，SKYPE等外部的程式都正常。

但要開啟內部的https網站時，就會無法顯示，錯誤訊息會說"網頁可能暫時離線，或是已經遷移到另一個網址"。

在access log裡查到的紀錄都是 "NONE/503 0 CONNECT"。

然後就開始上網到處查，然後有看到有些人提到在squid.conf 裡要加入一行"dns_v4_first on"，雖然感覺這跟我的問題不相關，但就試試吧。

結果在conf裡先搜尋dns的字眼時，看到了這段，"dns_nameservers  8.8.8.8 208.67.222.222"。

DNS居然是指向外部，所以就把內部的DNS SERVER IP加到最前面，重啟服務，就解決這個問題了。

SQUID Proxy Unable to Connect to Internal HTTPS Websites - NONE/503 0 CONNECT

After setting up the SQUID Proxy Server, everything seemed to be working smoothly. Websites loaded fine, and external applications like LINE and Skype functioned properly. However, when trying to access internal HTTPS websites, they would not display, and an error message stating "The webpage might be temporarily down or may have moved to a new address" would appear.

Upon checking the access log, the recorded entries were "NONE/503 0 CONNECT."

I started searching online for a solution and came across a suggestion to add the line "dns_v4_first on" to the squid.conf file. Although it didn't seem directly related to my issue, I decided to give it a try.

While searching for the term "dns" in the configuration file, I came across the following line: "dns_nameservers 8.8.8.8 208.67.222.222."

To my surprise, the DNS servers were pointing to external addresses. So, I added the IP address of the internal DNS server to the beginning of the list, restarted the service, and the problem was resolved.

QNAP NAS無法發信 Failed to send a test message using SMTP Service.

在QNAP NAS設定好電子郵件設定，用來發送警告信給管理者，設定好後測試，卻都失敗，錯誤訊息就是示"Failed to send a test message using SMTP Service."。

從不同網段連到QNAP的管理web都正常，所以就覺得網路設定都沒問題。

後來就想用ssh連上QNAP，去ping在不同網段的mail server，卻是不通的，然後再執行route -n 顯示路由表時，卻沒有0.0.0.0的路由，這就妙了。

本來想直接用指令去加，但查到的指令route add default gw 192.168.24.1 br0有錯誤，所以就決定回管理web上看看是不是少設了什麼。

結果發現了一個東西，有一個系統預設閘道的設定，之前都沒去理它，後來進去這設定，在把gateway設定上去之後，回到ssh裡，route -n 顯示路由表時，就有0.0.0.0的路由，發送信件的功能也就正常了。

The QNAP NAS is unable to send emails.

When setting up the email configuration on the QNAP NAS to send alert messages to the administrator and testing it, all attempts fail with the error message "Failed to send a test message using SMTP Service."

Since accessing the QNAP management web interface from different networks works fine, it is believed that there are no issues with the network settings.

Later on, an attempt was made to connect to the QNAP using SSH and ping the mail server in a different network segment, but the connection was unsuccessful. Upon executing the command "route -n" to display the routing table, it was noticed that there was no route for 0.0.0.0, which was puzzling.

Initially, there was a plan to manually add the route using the command "route add default gw 192.168.24.1 br0," but it was found to be incorrect. Therefore, the decision was made to go back to the management web interface and check if anything was missing.

As a result, it was discovered that there was a default gateway setting that had been overlooked. Previously, it had not been addressed. After accessing this setting and configuring the gateway, upon returning to the SSH session and executing "route -n" to display the routing table, the route for 0.0.0.0 appeared, and the email sending functionality started working correctly.

AD查詢4776 登入失敗的電腦 來源工作站錯誤

 在AD查看被鎖定的帳號，用id 4776去撈出登入出敗的訊息，要找出是在哪台電腦做登入行為的。

結果在來源工作站的資訊，是一台沒看到的電腦名稱，也ping不到，覺得很奇怪。

就想到之前遇到來源工作站是空白的問題，那時就繼續在事件檢視器裡去找NTLM的log，可以找到相關的訊息。

這次也想說去NTLM裡面找找，就找到了，在NTLM裡記錄的登入失敗log裡，除了來源工作站，還多了一個安全通道名稱，這邊顯示的才是正確的電腦名稱。

至於為啥來源工作站是一個奇怪的名稱，目前也不知原因。

When checking the locked accounts in Active Directory, I used ID 4776 to retrieve the information about failed logins in order to determine the workstation where the login attempts originated.

The result showed an error in the workstation information, indicating a computer name that I couldn't find or ping, which seemed unusual.

I recalled a previous encounter where the workstation information was blank, so I continued searching for NTLM logs in the Event Viewer, as they often contain relevant details.

This time, I decided to check the NTLM logs and successfully found the failed login log. In addition to the workstation information, there was also a security channel name recorded. The computer name displayed in this section was the correct one.

As for why the workstation information appeared as a strange name, I am currently unaware of the underlying reason.

win7 chrome 播放線上影片 有聲音沒畫面

最近發現在透過chrome看一些線上課程影片時，影片會有聲音沒畫面。

win10的電腦都沒問題，只有win7的電腦會有這種狀況，所以排除影片本身的問題。

後來才發現竟是chrome裡面設定造成的，在win7電腦中，需要把chrome裡面有一個硬體加速的功能關閉，影片的畫面才能正常顯示。

No Video but Sound when Playing Online Videos in Chrome on Windows 7

Recently, I noticed that when using Chrome to watch online course videos, there would be sound but no video playback. This issue was specific to computers running Windows 7, as there were no problems on Windows 10 machines. Therefore, I ruled out any problems with the videos themselves.

Later, I discovered that the issue was actually caused by a setting within Chrome. On the Windows 7 computers, it was necessary to disable a feature called hardware acceleration in Chrome to enable proper video playback.

Teams JavaScript error the specified procedure could no be found

 突然有幾台電腦的teams開啟都會有這個錯誤，無法使用。

重裝teams也沒用。

查了一下，原來是可轉發套件的問題，處理流程如下。

1. 移除teams，並把%appdata%底下teams相關的資料夾全刪除。

2. 移除電腦內所有的visual c++可轉發套件，然後重開機。

3. 安裝最新的2015to2022，visual c++可轉發套件。

4. 安裝teams。

之後就可以正常開啟了。

Teams JavaScript error: "The specified procedure could not be found."

Suddenly, several computers are experiencing this error when opening Teams, rendering it unusable.

Reinstalling Teams did not resolve the issue.

Upon investigation, it was discovered that the problem lies with the redistributable package. The following steps can be taken to address it:

Uninstall Teams and delete all related folders under "%appdata%".

Remove all Visual C++ redistributable packages from the computer and restart.

Install the latest version of the Visual C++ redistributable package (2015 to 2022).

Install Teams.

After following these steps, Teams should open without any errors.

OUTLOOK編輯郵件貼圖沒東西

 outlook在編輯郵件時，要直接把圖貼在內文中，但貼上後，就是空白沒東西。

有時後在郵件的預覽內文視窗，在上下滾動畫面時，畫面也會很頓。

後來有查到，就是WIN10的DPI設定。

就是在解析度的設定上面，還有一個百分比可以調整畫面上字型與項目的大小，如果設定是超過100%，像是125%或150%時，就會造成在編輯郵件時的一些問題，只要調成100%，就可以排除這個怪問題，很奇特的一個問題。

There is nothing in the image pasted in the email while editing it in Outlook.

Sometimes, when scrolling up and down in the preview pane of the Outlook, the screen becomes sluggish. Later, it was found that it is due to the DPI (Dots Per Inch) settings in Windows 10. In the display settings, there is a percentage that can be adjusted to change the size of fonts and items on the screen. If the setting is above 100%, such as 125% or 150%, it can cause issues when editing emails. By adjusting it to 100%, this strange issue can be resolved.