2022/12/29

WIN10 在EDGE 用IE模式開網頁

 有些網頁必須要用IE才能正常顯示,如果透過EDGE,就要啟用裡面的IE模式才行。

可以直接在EDGE設定中加入要用IE模式開起的網頁,但這有個缺點,要一台一台做,而且還有期限,預設30天,最長可以改到90天,不適合在公司裡這樣設定。



這時就可以用GPO來佈署,步驟如下:

1. 確認GPO裡有EDGE設定,因為DC都是2012版的,所以要自己下載ADMX檔來增加EDGE功能,方式可參考 https://www.anoopcnair.com/download-microsoft-edge-admx-group-policy-templates/

2. GPO裡有EDGE設定後,要啟用兩個設定

設定企業模式網站清單-這個先設定好檔案路徑跟檔名,例如

C:\ielist.xml,這個檔案在第3步會產生。

再來是要啟用設定InternetExplorer整合



3. 安裝Enterprise Mode Site List Manager,透過這個檔案把要用IE模式開啟的網站建成一個xml的清單,取名成ielist.xml,派送到使用者電腦C槽中,跟第2步GPO裡的設定配合。清單的設定方式一樣網路上很多教學,可參考https://www.anoopcnair.com/configure-enterprise-mode-site-list-using-intune/
4.上述都設定好後,GPO佈署下去就ok了。
當用EDGE開啟IE模式的網站,看一下網址例左邊有出現一樣IE的檔案,就表示現在已在IE模式下執行,設定成功。

機碼的位置可參考這篇
https://admx.help/?Category=EdgeChromium&Policy=Microsoft.Policies.Edge::InternetExplorerIntegrationLevel&Language=zh-tw


Using IE Mode to Open Websites in EDGE on Windows 10

Some websites require Internet Explorer (IE) to be displayed correctly. If you're using EDGE, you can enable the built-in IE mode to access these websites. While you can manually add websites to open in IE mode within EDGE settings, this method has its drawbacks. It requires configuring each device individually and has a time limit, typically set to 30 days (extendable up to 90 days), which is not ideal for company-wide settings.

To address this, you can deploy the settings using Group Policy Objects (GPO) with the following steps:

1.Ensure that the GPO includes the EDGE settings. Since the domain controllers are running the 2012 version, you'll need to download the ADMX files to add EDGE functionality. You can refer to the following link for the process: link to download ADMX files.

2.Once the EDGE settings are available in the GPO, enable two specific settings:

3.Configure the Enterprise Mode Site List: Set the file path and name, for example, C:\ielist.xml. This file will be generated in the next step.
Enable the Internet Explorer Integration setting.
Install the Enterprise Mode Site List Manager. Using this tool, create an XML list named ielist.xml that contains the websites to be opened in IE mode. Place the file in the C:\ directory of users' computers and align it with the settings from step 2. There are various tutorials available online on how to configure the list. You can refer to this link: link to configure Enterprise Mode Site List using Intune.

4.Once all the settings are configured, deploy the GPO to the desired devices.

To verify if a website is opened in IE mode using EDGE, check the URL. If you see the IE file icon on the left side, it indicates that the website is being accessed in IE mode, confirming the successful configuration.




2022/12/16

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.

2022/12/15

2022年最後一個月選擇權交易

 今年基本上就是慘,前11個月,好像只有一個月是有獲利,其他都賠錢。

12月開始把交易條件訂的比較高,所以交易次數不多,雖然前兩週都只做1口單賣當沖,但至少都有賺,第三週目前確定是沒交易機會了,希望剩下兩週也能順一點,至少讓我最後一個月也是獲利結束今年,把希望寄託在明年。

2022/12/13

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 TS-432XU(4.3.6)更換故障硬碟

 一台QNAP TS-432XU(4.3.6)有4顆硬碟做RAID5,最後一顆硬碟已出現警告建議更換,雖然還可以用,但這顆硬碟的讀寫速度慢很多,所以影響到一些日常作業。

原本同型號的硬碟停產了,所以就買一個同廠牌同容量,但轉速更快的來換。

雖然知道是熱插拔,但一開始還上網看一下是不是要在管理介面上做什麼操作,後來查到的畫面又跟自己的不同,就決定直接插拔更換了。

插上後系統就自己在重建了,蠻方便的,剩下就讓它跑完重建程序了。


Replacing a Faulty Hard Drive on QNAP TS-432XU(4.3.6)

On a QNAP TS-432XU(4.3.6) device with a RAID 5 configuration using four hard drives, the last drive started showing warning signs and advised replacement. Although it was still functional, its read and write speeds had significantly decreased, affecting daily operations.

Since the original model of the hard drive was no longer available, I purchased a higher-speed drive from the same manufacturer with the same capacity as a replacement.

While I knew that the device supported hot-swapping, I initially checked online to see if there were any specific actions required through the management interface. However, the instructions and screenshots I found were different from what I encountered, so I decided to proceed with a direct replacement.

Once I inserted the new drive, the system automatically initiated the rebuilding process. It was quite convenient, so I allowed it to complete the rebuilding procedure.



2022/12/09

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.

2022/11/21

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.

2022/11/16

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.

2022/11/04

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.


2022/11/03

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.

2022/10/31

7zip 壓縮檔案指令

為了想要定期把一些檔案壓縮成一個檔案,所以就想到要用batch加排程的方式。

7zip有提供相關的指令可以做

指令如下,

7z a d:\backup[%DATE:~0,4%-%DATE:~5,2%-%DATE:~8,2%].7z  @d:\list.txt 

第一欄(7z) - 就是執行程式的名稱,最好是用完整路徑

第二欄(a) - 就是要壓縮的意思

第三欄(d:\xxx) - 就是壓縮檔的名稱,上面的範例是檔名會自動產生當天的日期,後面的副檔名也可以改用zip

第四欄(@:xxx) - @後面要接一個文字檔,這個文字檔裡就列出要壓縮的檔案存放的路徑,所以有3個不同資料夾的檔案要壓在一起,就把三個路徑分三行存在文字檔裡就行了。

以上就是batch檔的內容。



7zip File Compression Command


In order to periodically compress files into a single archive, I decided to use batch scripting along with scheduled tasks. Fortunately, 7zip provides relevant commands to achieve this.

The command is as follows:

7z a d:\backup[%DATE:~0,4%-%DATE:~5,2%-%DATE:~8,2%].7z @d:\list.txt

Here is a breakdown of the command:

The first field (7z) represents the name of the executable program. It is recommended to use the full path to the program.

The second field (a) indicates the action of compressing.

The third field (d:\xxx) specifies the name of the compressed file. In the example above, the file name will be automatically generated based on the current date. You can also change the file extension to .zip if desired.

The fourth field (@:xxx) specifies a text file. This text file contains the paths of the files to be compressed. So, if you have files from three different folders that need to be compressed together, you can list the three paths on separate lines in the text file.

The above instructions can be included in a batch file to automate the process.

2022/10/19

發信通知AD帳號 密碼快到期的人

 windows系統內建的提醒實在太小了,就縮在右下角,而且預設兩週前會天天提醒,到剩一週後,就不會在顯示了,使用者早就忘了,所以需要一個比較顯示的提示。

 可以參考這個下列這個powershell,就可以執到此功能,裡面程式碼有夠多,但只要先把要搜尋的dc位置,mail server位置,管理者信箱這3個設定值,調成自己環境內的資訊,就可以執行測試了。

預設是測試模式,所以只會寄給管理者,測試ok後再關閉測試模式,通知信就會發給使用者了,不需要修改太多東西就可以用了,讚。

https://gist.github.com/meoso/3488ef8e9c77d2beccfd921f991faa64#file-example-com-password-expiration-notifications-ps1



Notifying Users of Expiring Passwords via Email in Active Directory

The default built-in password reminder in Windows is quite inconspicuous, residing in the bottom right corner. Additionally, it only displays reminders every day up to two weeks before the expiration date. Once there is only one week left, the reminder disappears, and users tend to forget about it. Therefore, a more prominent notification is needed.

You can refer to the following PowerShell script to achieve this functionality. Although the code may seem extensive, you only need to adjust three configuration values: the location of the domain controller (DC), the mail server, and the administrator's email address. Once you set them according to your environment, you can execute a test run.

By default, the script runs in test mode, sending notifications only to the administrator. After confirming that it works correctly, you can disable test mode, and the notifications will be sent to the users. It requires minimal modifications, making it easy to use.

You can find the PowerShell script at the following link:

https://gist.github.com/meoso/3488ef8e9c77d2beccfd921f991faa64#file-example-com-password-expiration-notifications-ps1

2022/10/07

outlook 收件都變成純文字格式

 outlook正常的話,收進來的信會是html格式。

如果信突然都變成文字格式,就是設定被調到,改回來就行了,就在信任中心裡有個以純文字讀取所有標準郵件,取消就行了。


















Outlook emails are appearing as plain text format.
In a normal Outlook setup, incoming emails are displayed in HTML format.

If suddenly all emails are appearing as plain text, it means that a setting has been changed. To revert back to the original format, follow these steps:

Open Outlook and go to the Trust Center.
Look for the option "Read all standard mail in plain text" within the Trust Center settings.
Uncheck this option to disable plain text reading for all standard emails.
Once you have made this change, Outlook will display emails in their original format again.

選擇權單賣 慘啊

 最近兩個月真的就是上下刷,做單賣當沖實在慘,一直打到停損,超累的。

還好都有控制好停損,至少都沒大賠。

2022/09/28

linux 掛載 windows 共用資料夾

 有一台centos要把windows的file server內的其中一個資料夾掛載上去。

先在windows主機192.168.1.1上,建立一個掛載專用的本機帳號abc,設定好密碼123。

接著就在cenotos上,執行下列指令就行了。

mount -t cifs -o username=abc,password=123 //192.168.1.1/documents /mnt/winshare



Mounting a Windows shared folder on Linux.

To mount a specific folder from a Windows file server on a CentOS machine, follow these steps:

On the Windows host with the IP address 192.168.1.1, create a local user account "abc" specifically for the mounting purpose. Set the password for this account as "123".

On the CentOS machine, execute the following command:

mount -t cifs -o username=abc,password=123 //192.168.1.1/documents /mnt/winshare


2022/09/27

Kaspersky Embedded Systems Security 病毒碼更新失敗 Error code: 0x02C2. Subsystem code: 0x4

有兩台裝有Kaspersky Embedded Systems Security3.0的主機病毒碼一直更新失敗,但還有四台都正常。

發信問廠商,回覆是說要做資料庫回溯,但做了也沒用,所以又給了另一個解法,就是升級到3.1。

如果升3.1才有用,那沒道理其他四台用3.0的都沒事啊,所以就覺得廠商的回覆蠻隨便的。

因為是server,也不能隨意重開機,所以就決定把防毒主程式重啟好了。

這版本比較鳥的是,沒有選項讓你直接關閉服務,要去裝kess console,然後裡面才有關閉跟啟用的服務。

重啟後,更新還是失敗,但再一次,就成功了。


原本的錯誤訊息如下

Internal task error occurred. Error code: 0x02C2. Subsystem code: 0x4 (General). For more details go to the Kaspersky Technical Support site: https://click.kaspersky.com/?hl=en-US&link=error&pid=wsee&version=11.0.0.0&error=B4X706X



Kaspersky Embedded Systems Security Virus Database Update Failure Error code: 0x02C2. Subsystem code: 0x4

We encountered issues with two hosts running Kaspersky Embedded Systems Security 3.0, as the virus database updates consistently failed. However, the other four hosts had no problems with the updates.

We reached out to the vendor for assistance, and they suggested performing a database rollback. Unfortunately, this solution did not resolve the issue. They then proposed upgrading to version 3.1 as an alternative resolution.

It seemed odd that only upgrading to 3.1 would solve the problem, considering the other four hosts running 3.0 were functioning fine. We found the vendor's response somewhat casual.

Since these were server systems, we couldn't simply restart them without careful consideration. Instead, we decided to restart the antivirus main service.

One drawback of this version is that it lacks an option to directly disable the service. Instead, we had to install the Kaspersky Endpoint Security for Business console, where we found options to enable and disable services.

After restarting the service, the update initially failed again, but upon a subsequent attempt, it succeeded.

The original error message received was as follows:

"Internal task error occurred. Error code: 0x02C2. Subsystem code: 0x4 (General). For more details, please visit the Kaspersky Technical Support site: https://click.kaspersky.com/?hl=en-US&link=error&pid=wsee&version=11.0.0.0&error=B4X706X"

2022/09/23

Fortigate VPN token有時後會沒用

 在fortigate上設定好ad帳號登入vpn,要啟用token驗證,才能連線。

但有些使用者設定好,手機上的程式也啟用了,登入vpn時就不會跳出要輸入token code,就直接登入成功了。

後來才發現是登入帳號大小寫的問題,有的人帳號是用大寫,就不需要輸入token code,用小寫才需要。

後來發現是我們在設定vpn的權限時,一開始是還沒用token時,直接把ad群組加入vpn的設定中。

現在因為要用token,需要把個別的ad帳號加到用戶名單,再加到vpn設定中。

所以vpn的設定裡就會有兩個不同的帳號來源,這時後只要把在vpn設定裡的ad群組拿掉,就行了。

user登入後,就只能接受跟用戶名單裡大小寫都要相符的帳號做登入。


Fortigate VPN Token Sometimes Doesn't Work

When setting up an AD account for VPN login on Fortigate, token authentication needs to be enabled to establish a connection.

However, some users have successfully configured their accounts and activated the token authentication on their mobile devices, but when they log in to the VPN, they are not prompted to enter the token code. Instead, they are logged in directly.

Later, we realized that the issue was related to the case sensitivity of the login credentials. Some users had their usernames in uppercase, which bypassed the need for a token code, while lowercase usernames required it.

We discovered that when initially setting up VPN permissions, before using tokens, we directly added the AD group to the VPN configuration.

Now, with the token requirement, individual AD accounts need to be added to the user list and then included in the VPN configuration.

As a result, the VPN configuration will have two different sources for account information. To resolve this, we simply need to remove the AD group from the VPN configuration.

After this change, users will only be able to log in with usernames that match the case sensitivity specified in the user list.

2022/09/22

fortiVPN 使用token登入錯誤 : fortitoken clock drift detected

 結果是安裝fortitoken mobile的手機時間錯誤,把時間調對就好了。


fortiVPN login error with token: fortitoken clock drift detected.

 The issue was caused by incorrect time settings on the mobile device where fortitoken mobile was installed. Simply adjusting the time resolved the problem.

2022/09/16

選擇權早盤當沖沒出掉 下午盤就會GG

當沖基本上就是早盤收盤要平倉,但有時後就是來不及,然後沒沖掉,就放到下午盤繼續等,但每次這樣子,就只會虧更多,唉!!!真的要照著計劃走,不能凹。

2022/09/01

選擇權做賣方要買保險

 做了幾個月的選擇權賣方,一直都記得做賣方要保險,不然遇到一次爆漲或爆跌,就會GG。

所以就一直做雙賣,想說至少有一邊能補一下,而且都做日盤當沖,頂多就價外1~2檔的位置,也流動性也還不錯,做的比較安心。

如果價格往其中一邊衝太多,還是會虧損,所以還是會設停損。

下單的策略並不是完全中立,是會先抓今天偏多或空,就會順勢往價外一兩檔做雙賣。

就算方向對了,賺的速度會比賠的快,所以還是會賺,但行情衝過頭,賠的速度就會比賺的快,反而會開始賠錢,等於是獲利有限,虧損無限大。

所以需要在好好想想,這策略應該要調整一下。

2022/08/09

Forti VPN連不上-- 'The server you want to connect to requests identification. Please choose a certificate and try again ( -5)'

 原本很舊的Forti防火牆升級後,有一些人的VPN就無法連線了,本來以為跟client端的vpn程式版本有關,因為公司內有4、5、6、7四種版本。

但後來發現這4個版本也都有不同的使用者可連上VPN,所以不是這個問題。

所以就用就錯誤訊息去查



後來是直接去IE的網際網路選項中,在進階設定裡把TLS1.1跟1.2打勾,就可以解決這個問題了。


Forti VPN cannot connect - 'The server you want to connect to requests identification. Please choose a certificate and try again (-5)'.
After upgrading an outdated Forti firewall, some people were unable to connect to the VPN. Initially, I thought it might be related to different versions of the VPN client software (versions 4, 5, 6, and 7) used within the company.
However, I later discovered that users with all four versions were able to connect to the VPN, so that wasn't the issue.
To troubleshoot, I investigated the error message further.
Eventually, I found that the solution was to go to the Internet Options in Internet Explorer and enable TLS 1.1 and 1.2 in the advanced settings. This resolved the problem.


2022/08/04

卡巴斯基安全管理中心資料備份和還原程式 無法備份

 在升級卡巴斯基安全管理中心前,官方文件建議要用內建的資料備份和還原程式(Program Files (x86) Kaspersky Lab Kaspersky Security Center klbackup .exe)先做備份。

但在按下備份時,程式就會直接關閉,無法備份,沒任何訊息。

然後在事件檢視器裡,就找到一個相關的錯誤訊,原因是因為在執行備份時,會需要連上db,但目前登入的帳號是網域帳號,但當初安裝時是用本機帳號,所以會連不上db做備份,這時只要改用原本安裝的帳號來執行就可以備份了。



Before upgrading the Kaspersky Security Center, the official documentation recommends using the built-in data backup and restore program (Program Files (x86) Kaspersky Lab Kaspersky Security Center klbackup.exe) to perform a backup.

However, when pressing the backup button, the program immediately shuts down without any error message, making it impossible to create a backup.

Upon checking the Event Viewer, an error message related to the issue was found. The reason for this error is that during the backup process, a connection to the database (db) is required. However, the current logged-in account is a domain account, while the initial installation was performed using a local account. As a result, the backup process fails to establish a connection to the database. To resolve this issue, it is necessary to execute the backup using the original account used during installation.


卡巴斯基防毒的相關文件

 http://i-services.info/kaspersky/

代理商有個網站上面有相關的教學分享,不錯用。

2022/08/03

Fortigate 免費的2個token刪除後無法加回..無法存取forti care

 Fortigate 本身就有含兩個token授權,可以指派其兩個帳號,做雙因子驗證使用。

在測試時,設備本身有簽維護,但版本很舊,在設定時發生一些狀況,後來就把它給刪了,想說應該可以重新加回來,上網找了一下,可以用全都是0的預設設號匯入就行了。

結果~不行,然後有一個按鈕是寫重新下載授權,按下去就跳出無法存取forti care,一整個搞不定。

明明就有維護,還不給我存取,最後就依廠商建議,系統太舊原廠不支援,升級到最新試試,就可以了。

After deleting the two free tokens on FortiGate, I couldn't add them back, and I couldn't access FortiCare.

FortiGate itself comes with two token licenses, allowing for the assignment of two accounts for two-factor authentication purposes.

During testing, the device had an existing maintenance agreement, but it was running on a very outdated version. While configuring it, some issues occurred, so I decided to delete it, thinking that I could add it back later. I searched online and found that I could import a default configuration with all zeros.

However, it didn't work. There was a button labeled "Re-download License," but when I clicked it, it showed an error message saying it couldn't access FortiCare. It was quite frustrating.

Despite having an active maintenance agreement, I was denied access. Finally, following the vendor's suggestion, I upgraded the system to the latest version, and that resolved the issue.

2022/07/27

連兩週結算日翻船啊

 連續兩周的OP週結算都來個V轉,本來當週都有機會賺錢,最後都賠了。

結算日雙賣,做錯邊,基本上就跟做小台差不多的賺賠啊。

2022/07/20

選擇權下單真是亂啊

 選擇權不像股票或期貨,今天你買了一張,如果又賣一張,帳戶就是0庫存。

但選擇權是可以同時存在買跟賣,所以下單前要先確認好現在是新倉還是平倉的選項,三不五時就會因為這個事情下錯單,真的很不爽,會因此產生不必要的虧損。

還有結算日時,明明要下結算日的合約,有時也會不小心下到新合約。

有時後就是因為這樣,原本當天要小賺的,就變小賠,白做工,真的要小心一點才行。

2022/07/11

Teams 登入失敗 Error Code caa20002

 突然多位user的Teams登入失敗,錯誤代碼都是caa20002。

這些登入失敗的電腦,都是win7,但又不是每一台win7都有這個問題,有點奇怪。

後來找了幾台不同的電腦測試後,才發現原因。

主要是因為IE的關係,要IE11才能正常登入Teams程式,其他比較低階的版本,都會失敗。

很討厭的問題,因為錯誤訊息根本跟IE沒關係,很難查原因。


Teams Login Failure with Error Code caa20002

Multiple users suddenly encountered login failures in Teams, with the error code caa20002.

Interestingly, these login issues were observed on computers running Windows 7, but not every Windows 7 device was affected, which seemed puzzling.

After conducting tests on several different computers, the root cause was identified.

The problem primarily stemmed from Internet Explorer (IE) compatibility. Teams application requires IE11 to function properly, and lower versions of IE would result in login failures.

This issue was frustrating because the error message provided no indication of an IE-related problem, making it difficult to identify the cause.

2022/07/05

CentOS 建立有root權限的帳號

 因為不想讓其他人有root的密碼,但又需要root權限工作,所以需要建立一個有root權限的帳號。

帳號建好後,執行下列指令,讓該帳號能用sudo,又不需要輸入任何root密碼,就可用root權限工作。做完在把該帳號停用就好了。

[root@test ~]# visudo

在裡面找到下列這行

root    ALL=(ALL)       ALL

在底下加入其他用戶

newuser     ALL=(root) ALL  

存檔離開,然後newuser就可以在不輸入密碼的情況下執行sudo指令,達到有root權限的目的。


Creating a Root-privileged Account on CentOS

To prevent sharing the root password with others while still needing root privileges, it is necessary to create an account with root privileges.

Once the account is created, execute the following command to allow the account to use sudo without entering any root password, enabling it to perform tasks with root privileges. Afterward, the account can be deactivated.

[root@test ~]# visudo

Find the following line within the file:

root ALL=(ALL) ALL

Add the desired user below it:

newuser ALL=(root) ALL

Save the changes, exit the file, and then the newuser can execute sudo commands without entering a password, achieving the goal of having root privileges.


HPE switch reset 重置

 最近買了HPE的switch,然後在設定時設定錯了,造成登入後沒權限做任何設定的調整,只能做設定的重置。

但現在的switch已沒有實體的reset鍵,只好透過官網提供的方式來reset。


首先,先重開switch,在重開的過程中會提示,可以按下Ctrl+B進入進階的開機選單中

進到進階開機選單後,就先選7,這是讓你下次重開機後,會跳過原本的設定檔,就像新機一樣,這時就可以重新建立一個新的帳號,給他最高的權限,然後存檔覆蓋原本的設定檔,再重開機,就可以用新建的帳號進去了。

下面是原廠提供的操作畫面,可以參一下。   


    BOOT  MENU    


1. Download application file to flash  

2. Select application file to boot  

3. Display all files in flash  

4. Delete file from flash  

5. Modify bootrom password  

6. Enter bootrom upgrade menu  

7. Skip current configuration file  

8. Set bootrom password recovery  

9. Set switch startup mode  

0. Reboot    


Enter your choice(0-9):      

Enter 7 (Skip current system configuration) and restart the switch (opcion 0). The switch reboots with empty configuration, and can log in through the console port without entering the password to check the configuration file for the user password.



Enter your choice(0-9): 7  

The current setting will boot with current configuration file when rebooted.  

Are you sure you want to skip current configuration file when reboot? Yes or No [Y/N] y  

Setting......done!              


    BOOT  MENU    


1. Download application file to flash  

2. Select application file to boot  

3. Display all files in flash  

4. Delete file from flash  

5. Modify bootrom password  

6. Enter bootrom upgrade menu  

7. Skip current configuration file  

8. Set bootrom password recovery  

9. Set switch startup mode  

0. Reboot    


Enter your choice(0-9): 0    


Starting......      

2022/06/23

選擇權操作-202206w5-沒想到還有w5

 本來想七月才重新開始,這周就可以來交易了。

沒想到這周只是6月w5~那就繼續忍吧,當作是在考驗自己的紀律。

2022/06/21

Fortigate 內部無法直接連線外部虛擬IP

 在防火牆設定好要對外服務主機的外部IP後。從外部網路連線時,沒問題。

但如果從內部網路去連線這個外部IP,卻是不通的。

原因就出在設定虛擬IP時,有一個欄位"介面",若沒有指定,就無法從內部做連線。

只要設定好這個虛擬IP所在的介面,就沒問題了。



Fortigate cannot directly connect to an external virtual IP internally.

After configuring the firewall to use an external IP for a specific service host, there is no issue connecting from an external network.
However, if an internal network tries to connect to this external IP, it will not work.
The reason for this lies in the configuration of the virtual IP. There is a field called "Interface" that needs to be specified. Without specifying the interface, internal connections cannot be established.
Once the interface for the virtual IP is properly configured, the issue should be resolved, and internal connections to the external IP will work correctly.

選擇權操作-202206w4-上週賠太多 這周空手

 上週賠太多了,要冷靜一下。

這週就空手,重新檢視一下交易策略,等七月在開工。

一直急著想交易,也只是愈賠愈多。

2022/06/20

EXCEL開啟出錯 "excel 部分內容有問題 您要我們盡可能嘗試復原嗎"

 有一個有多頁籤的excel檔,裡面只要是文字跟一些圖片。

之前都可以用,今天在開啟時突然跳錯誤



excel自行修復後,檔案可以開,但很多圖片卻不見了,而且每次開啟都會跳一樣的錯誤。
後來有查到一個不錯的解決方法,就是去安裝免費的open office,利用裡面的excel功能來開啟這個異常的檔案,就可以正常開啟了,接著在另存新檔,這個新檔就可以在微軟的excel裡正常執行了。

Excel error on opening: "Excel found unreadable content. Do you want to recover as much as we can?"

There is an Excel file with multiple tabs containing text and some images.

Previously, it was working fine, but today, when trying to open it, an error suddenly occurred.

After Excel attempted to repair the file, it could be opened, but many images were missing, and the same error message appeared every time it was opened.

Later, a helpful solution was found. By installing the free OpenOffice software and using its Excel functionality to open the problematic file, it could be opened successfully. Then, the file was saved as a new file, which could be opened and executed properly in Microsoft Excel.



2022/06/16

您的電腦遺失api-ms-win-crt-runtime-l1-1-0-dll

 有些電腦在執行某些程式時,時會出現"您的電腦遺失api-ms-win-crt-runtime-l1-1-0-dll",以致程式打不開。

重裝程式也沒用,因為這個.dll檔是其他程式提供的,就是微軟的c++可轉發套件。

去下載後重新安裝c++可轉發套件,就可解決此問題。




Your computer is missing api-ms-win-crt-runtime-l1-1-0.dll.

On certain computers, when running certain programs, an error message may appear stating "Your computer is missing api-ms-win-crt-runtime-l1-1-0.dll," causing the program to fail to launch.

Reinstalling the program does not resolve the issue because this .dll file is provided by another program, namely Microsoft's C++ redistributable package.

To resolve this problem, you need to download and reinstall the C++ redistributable package. This will ensure that the missing api-ms-win-crt-runtime-l1-1-0.dll file is properly installed on your computer.

2022/06/15

選擇權操作-202206w3-只做最後兩天雙買,被殺爆了

 最近 都是開低走高,所做做空方都被殺。

又賠了快130點,真的慘。

如果做賣方,反而都會賺錢....

休息一下好了,不順就要暫停一下,不能一直賠下去。

2022/06/09

OUTLOOK很舊的信變亂碼 比較新的信正常

因為換新電腦,所以把舊電腦的PST檔一起移到新電腦上。
但 在查詢一些信件時發現一個怪事,大概在2013年以前的信件,全變成亂碼。之後的信件,卻都正常。
在舊電腦上是完成正常的,所以就在找另外兩台電腦來測試,測試後發現,同一個PST檔,在某些電腦上都有這個問題,在另一些電腦卻沒事,跟OUTLOOK或WINDOWS的版本都沒直接關係。
最後才發現,原來是OUTLOOK裡面的編碼設定造成的。
編碼如果改成BIG5,就沒有亂碼的問題,調成UTF8就有。
但還是跟使用者說,因為都是很舊的信才有影響,平常還是建議用UTF8,有需要查舊資料,才用BIG5。




Old emails in Outlook are displayed as garbled characters, while newer emails appear normal. 
Due to a computer upgrade, the PST file from the old computer was transferred to the new computer. However, upon checking some emails, a strange issue was discovered. Emails dated before approximately 2013 appeared as garbled characters, while those after that period appeared correctly.

The emails displayed correctly on the old computer, so additional testing was conducted on two other computers. It was found that the same PST file exhibited this issue on certain computers but not on others, regardless of the version of Outlook or Windows being used. Eventually, it was discovered that the encoding settings within Outlook were causing the problem.

Changing the encoding to BIG5 resolved the issue and prevented the garbled characters. However, it is still recommended to use UTF8 encoding for general use, as it is more widely supported. The BIG5 encoding should be used only when accessing old data that is affected by this issue.

2022/06/08

選擇權操作-202206w2-上週賺的3千,本週全吐回

 本週做了三次雙買,只有今天結算這天小小賺,其他兩天都賠,而且多次IOC進場不順,都跟原本要進場的價格有一點差距了。

這周基本上震盪小,做雙買就是不順。

結果這天進場後一開始還不錯,誰知道下半場開始拉回,50多點的獲利一點一滴的消失。

很不順的一週啊。

2022/06/02

選擇權操作-202206w2-出師不利 雙買組合單多次IOC一直沒成交

 今天做雙買,結果盤勢不如預期,從反方向走,所以就註定要賠錢。

只是在多次IOC下單時,又一直沒成交,一直在那洗,最後又是又單獨下單才成交,然後再組合。

後來要停損,又是一樣的問題,就是洗不到成交,然後就先拆單,各別平倉,才出掉。

以後都分開下好了。

2022/06/01

選擇權操作-202206w1-本週只賺3千,但已經週獲利新高~~

 這週只交易兩天,做2次雙買1次雙賣。

賺3千左右,已是我獲利最高的一週了,太感動了。

策略本身還需要調整,看下週能不能有更好的獲利。

選擇權操作-202206w1-雙買買不到

 今天現貨開盤十多分鐘,就要在價內做雙買,掛多次IOC組合單,價格條件都有達到,但就一直沒成功成交,等了兩分多鐘都沒成功。

最後就放棄,直接各別下單,一下就成交了。

還好最好還是有進場,沒放棄,不然今天就沒賺到了。

2022/05/31

選擇權操作-202206w1-雙賣居然沒出掉

 今天是6月第一週第一次做單,有做雙買跟雙賣。

運氣不錯,理論算應該要賠錢,但下單時沒注意,做反了,結果賺錢了。

但是雙賣的部分13:44開始掛多次IOC要出掉,結果居家都沒成交,只能等下午開盤繼續,因為雙賣的部份是虧錢的,一定要趕快脫手。


2022/05/30

選擇權操作-202206w1-準備開始交易

 最近在想新的策略,這周前幾天就都沒做單,因為統計了一下,星期二跟三獲利的機會最高,所以要明天跟後天在來做。


2022/05/26

outlook信件有迴紋針,但信裡看不到附件

 偶爾都會有使用者反應,收到的信件,旁邊有迴紋針,表示信中有附件,但信打開,裡面卻只有內文,沒有任何附件。

後來仔細的查詢,當信件進來後,經過第一層的圾垃郵件過濾系統,信還是完整的,附件也都有。

之後進到Mail Server,信也是正常的,然後Outlook收信時,從Mail Server的log上看到,的確也是整封信傳過去,所以就判斷問題是在本機端產生,不是Mail Server的問題。

防毒軟體在安裝時,有另外在Outlook內插入一個增益集程式,做附件掃描的功能,後來在Outlook裡把這個功能關閉,有問題的信在重寄一次,附件就出現了。


Occasionally, users have reported receiving emails with paper clips indicating the presence of attachments, but upon opening the emails, they find only the body text and no attachments.

Upon further investigation, it was found that when the emails arrive, they pass through the initial spam filtering system intact, with all attachments included.

Subsequently, when the emails reach the Mail Server, they are still in their original state. However, while receiving the emails in Outlook, it was observed from the Mail Server logs that the complete emails were indeed being transmitted. This led to the conclusion that the issue originated on the local machine and was not a problem with the Mail Server.

During the installation of the antivirus software, an add-in was inserted into Outlook to enable attachment scanning. However, after disabling this functionality within Outlook, the problematic emails were resent, and the attachments appeared as expected.

2022/05/24

選擇權操作-202205w4-又賠錢了

 這周只做兩筆雙賣,星期五中午12點多做勒式,星期一中午也是12點多,做跨式。

其實進場點不好,因為如果想等時間價值流掉,12點多進,只剩1小時,太失敗了,不應該手癢亂下單的。

兩筆單含手續費大概虧時是2千,對一個還沒辦法賺錢的人來說,實在痛。

2022/05/18

選擇權操作-近期心得

操作選擇權5個多月了,主要是從Youtube找了兩個比較有名的選擇權頻道做學習,並還有購買過其中一個人的線上課程,也有訂閱另一個的Youtube會員頻道。

主要是價差組合單跟跨式雙賣,有幾個心得:

1.未實現損益還是要注意 : 不能因為你覺得結算當天,價格還是非常有機會回到你預期的地方,就不管現在已經被穿價,然後放著不管它,如果價格真的往反向走,會虧很慘。

2. 組合單還要在做保險部位 : 做成組合單,其實就已經同時有多空兩個部位了,可限制或減緩虧損的速度,如果還要在加個BP或BS,又增加了更多交易成本,有時後反而更難獲利。

3. 還是要停損 : 有看到一些人說做價差單就不用停損啊,因為最大虧損已固定,但如果會了勝率高,做比較價外的地方,損益比其實很差,賺很多次可能一次就賠光,除非對沖或調整部位的手法非常熟練,不然還是要適時停損,不要賠太多,才能繼續生活下去。

4. 部位不要太大 : 還不熟時,部位不要太多,不然到時行情突然不如預情,產生大量的帳面虧損,就會不知該怎麼做,部位調的亂七八糟。

大概就這些了。

選擇權操作-202205w3-雙賣賺錢了

 這週全做雙賣,從星五夜盤開始做,做了七組跨式,5組獲利,最後賺了24點,雖然只是賺了一點點,但跟之前一直賠錢相比,算是有進步了。

希望能繼續保持下去,能穩定,再來慢慢放大口數。

2022/05/12

Adobe reader開啟檔案錯誤 : 處理註解或連結時出錯。字型指定的編碼(CMap)遺失。

 今天收到一個PDF檔,上面有被加上一些註解,在用最新版的Adobe reader開啟時,就會跳出"處理註解或連結時出錯。字型指定的編碼(CMap)遺失"的錯誤。



內文本身可以看,但註解的部份就無法顯示。

電腦本身除了有裝Adobe reader,也有裝字型包,裡面的註解也都是中文,所以一開始也不知為何會有錯誤。

最後就是把Adobe reader跟字型包重裝,就沒事了。


Error opening file with Adobe Reader: Error processing annotations or links. The specified font encoding (CMap) is missing.

Today I received a PDF file with some annotations added to it. When I tried to open it using the latest version of Adobe Reader, an error message popped up saying, "Error processing annotations or links. The specified font encoding (CMap) is missing."

The main content of the document was visible, but the annotations were not displayed. My computer had Adobe Reader installed, and I had also installed a font package that included Chinese annotations. Therefore, initially, I was unsure why this error occurred.

In the end, I resolved the issue by reinstalling Adobe Reader and the font package, and the problem was fixed.


2022/05/10

啟動 office2010 錯誤 0x80070190

 在啟動office時,出現0x80070190的錯誤,這不是序號錯誤,也不用去改機碼。

只要在啟動office的程式時,選擇用"系統管理員身份執行",開啟程式後在去啟動office授權,就ok了。

When launching Office, an error with the code 0x80070190 appears. This is not a serial number error, and there is no need to modify the registry. To resolve this issue, simply launch the Office program with "Run as administrator" option. Once the program is open, proceed with activating the Office license, and the issue should be resolved.

選擇權操作-202205w2-測試雙賣當沖 還抓不到感覺

 這週都在做當沖測試,有做單方向的跟雙賣。

單方向的單,跟期貨差不多,選錯方向就是賠錢,只是賠錢的速度比較慢一點點,這就不是我想做選擇權目的。

再來就是雙賣,主要就可擇價平或上下一檔雙賣,本來想說時間價值的流失會比兩邊權利金的變化更快,要賺時間價值的錢。

但事情並非如此,只要大盤大漲或大跌,權利金反而會升的比時間價值消耗的更多,然後就打到停損了。

這就要繼續研究什麼時間盤比較不會動,才能做雙賣。

2022/05/05

選擇權操作-202205w1-繼續賠錢,但還行

 這周就一開始的雙買很失敗。

之後做了兩組價平的組合單,其中一組還是剛好最大虧損是0,很難得。最後結算日又做了雙賣。

搞到最後不算手續費,只賠幾點而已,個人覺得還行啊。

2022/04/28

OCS Inventory NG 2.9.2 很多頁面是空白的

 因為原本的OCS Inventory NG太舊了,agent已不支援最新版的win10,所以要來升級到最新的 2.9.2。

最新的OCS server只能裝在Linux上,所以就選欲centos7來安裝,安裝過程主要是照 https://kifarunix.com/install-and-setup-ocs-ng-inventory-server-on-centos-7/ 這篇來操作。

裝的過程都蠻順利的,agent也要裝到client上了,但最後產生兩個問題。

1. 有抓到client,但軟體清單都是0,這個是因為OCS上有一個整理軟體的程序並不會自動執行,要自己去把這程序設到排程裡,才會統計軟體清單,程序是  /usr/share/ocsinventory-reports/ocsreports/crontab/cron_all_software.php

2. 看到軟體清單後,又發現另一個問題,系統會統計所有軟體被多少電腦安裝的數量,點擊那個次數就可以秀出是哪些電腦,但點擊後卻是空白畫面。


查了兩天,試過升級OCS nightly最新版,OS重裝,關閉SELINUX,都沒用,然後突然發現一篇文章就是在說這個問題,原來是PHP的版本太舊了,只要把PHP的版本升到最新,OCS也不用重裝,網頁畫面就可以正常顯示了。


Due to the outdated version of OCS Inventory NG, the agent no longer supports the latest version of Windows 10. Therefore, it is necessary to upgrade to the latest version, 2.9.2.

The latest OCS server can only be installed on Linux, so CentOS 7 was chosen for the installation process. The installation was primarily performed following the steps outlined in the article: "https://kifarunix.com/install-and-setup-ocs-ng-inventory-server-on-centos-7/".

The installation process went smoothly, and the agent was also installed on the client. However, two issues arose at the end of the process.

The client was detected, but the software inventory showed as 0. This occurred because OCS has a software sorting process that does not execute automatically. To resolve this, it is necessary to manually set up the process in the scheduler. The process is located at "/usr/share/ocsinventory-reports/ocsreports/crontab/cron_all_software.php".

After the software inventory was visible, another issue arose. The system was supposed to track the number of installations of each software on different computers. Clicking on the installation count was expected to display which computers had the software installed, but it resulted in a blank page.

After two days of investigation, attempts were made to upgrade to the latest version of OCS nightly, reinstall the OS, and disable SELINUX, but none of these resolved the issue. Then, by chance, an article was found that addressed this problem. It turned out that the issue was caused by an outdated version of PHP. Upgrading PHP to the latest version resolved the problem, and there was no need to reinstall OCS. The web page now displays correctly.


選擇權操作-202205w1-試一下雙買 賠錢出場

 如果在權利金會比較快速下降時適合做雙賣,那剛開倉的時後權利金下降比較慢,應該可以來試試短線的雙買吧。

基於這麼理念,星期三晚上就來試一下,但發現,價格開始動的時後,虧損的那一邊,速度會大於賺錢的那一邊,大概是兩倍的差距,賠的比賺的還大很多,跟想像的完全不一樣啊。

實在是太慘了,賠太多了,決定先暫停一下,把要看的資料看完在來做吧。

2022/04/26

選擇權操作-202204w4-撐到星期二夜盤最後還是gg

 星期二夜盤狂殺,組合單最後全部停損出場,不想等到明天了,失血太嚴重,認賠殺出。

最後含手續費賠了9千多,非常失敗的一週。

組合單的賺賠比實在太不合理了,一個急殺,就會損失慘重,這種策略需要在好好調整才行。

2022/04/25

選擇權操作-202204w4-汲汲可危的一週啊

 星期五晚上美股狂殺,我的週選還有賣權空頭價差單 16500*2 +16600*1馬上就變的非常危險。

一直希望星期一開盤能開低走高....結果是開低走更低。

因為16600的組合單被穿價,而且是幾乎整個要被貫穿了,所以當下就決定停損,然後再做16300賣權空頭價差單*2,這樣如果之後沒跌破16500,那16600那組單的虧損就會從34點變6點。

而且16400還有一個空間留在那,16500如果又被貫穿,就停損,然後補上16400,把虧損壓低。


2022/04/20

選擇權操作-202204w3-第一次當周結算賺錢

 終於等到賺錢的一週了。

這週組合單都有順利出掉,而且最晚星期二的夜盤就都出掉了。

也都沒用到買call/put來當保險,所以就沒把組合單的利潤吃掉。

也做了很多裸賣單試試,最後扣手續費沒賺沒賠,就是在練習而已。

雖然最後只賺了1千塊吧,但感覺這週收獲蠻多的。

2022/04/18

選擇權操作-開倉平倉沒注意 容易下錯單

 最近在做賣方的單子時,常常會犯一個錯,就是下單沒注意要設定是開倉還是平倉。

以前下台指期,預設就是選自動,也不用管它。

但選擇權可以同時做買跟賣方,所以沒把自動調成開倉或平倉時,就通通都變成開倉,然後要手動平倉沒注意,就會變成又開了一個反向的新倉,傻爆眼。

不過通常下成反向,其實一買一賣兩口單會互抵,還沒造成大損失,就是多賠一次的手續費。

2022/04/14

選擇權操作-202204w3-第一次做裸賣

 很多人都說裸賣很危險,但也看到很多人專做裸賣,就一直在想這東西。

做賣方最大的好處應該就是覺得賣的點位不會到,就等結算收租。

壞處就是如果被穿價,虧損無上限。

所以如果我有設停損,然後只賣當週合約,流動性比較好的,然後只當沖,是不是就可以避掉這些風險。

星期三就裸賣1口16600put,因為方向對,所以最後就獲利出場。

晚上又試了一次,裸賣1口17600的call,這次方向不對,最後就停損出場。

因為要盡量歸避掉大賠的機會所以當沖,但這樣就無法放到結算賺到全部的權利金。

再來就是軟體的部份,因為之前做期貨可以用智慧下單,觸到指定的價位就市價進場、停利、停損。

但用在選擇權卻會失敗,會跳出不能用市價單,這倒是有點麻煩,要在試試是不是要指定+1檔才能正常運作。

最後就是,因為當沖不等結算,所以還是要看一下到底當天會漲還是跌,才決定做call還put,不然選錯邊,還是很容易賠錢。

2022/04/13

選擇權操作-202204w2-第一次賺錢...不算手續費的話

 這一週大區間的策略,不算手續費的話 終於賺錢了。雖然只賺了9點,但這是第一次結算是有賺,太開心了。

這次的操作,有一組17000的賣權多頭價差單週一被穿價,當下就在想幾個方法:

一 不管它。

二等跌到16900做空小台+買call。

三 價差單拆開,把sell put停損,賺錢的buy put留下。

四 把這組單停損平倉。


一的話,方法不是很好,因為如果繼續殺下去就慘了。

二的話,買call的成本有點高,除非之後狂跌或狂漲,不然這個應該也是要賠個兩三千

三的話,buy put留下來,還可以順便保護下面三組賣權多頭價差單,但sell put的虧損有點多,所以也不太想這麼做。

四的話,會賠一些,但其他組合單可以cover掉,之後盤不要跌破16900,我頂多小賠。

所以最後就決定用方法四。

不過今天結算大漲啊,所以其實什麼都不做,就直接賺個25點,只能下次繼續努力。

2022/04/06

選擇權操作-202204w1-下殺被穿價用小台對沖後又往上拉...就是要我賠錢

 上星期三週選建的3組put spread到了週五都還沒事,也還好的機會沒買進put避險。

到了星期一看美股大漲,想說這3組 put spread不錯哦,結算應該要賺錢了吧。

沒想到週二晚上美股大跌,今天早上台指一開就下殺,第一組put spread被穿價後,馬上用小台空單+買call,如果一直往下殺,還有可能有一點點機會賺錢。

結果後來居然又往上漲,最後就是又賠錢了,賠了2千左右。

這真的好難,怎麼這麼難賺,

2022/03/30

選擇權操作-202203w5-賠最少的一週

 這週是大區間策略賠最少的一次。

進場的Put Spread才5口,Put也買的很便宜,但可惜還是差一點,沒辦法兩邊完全打平。

雖然星期一有下殺很爽,感覺這週會賺錢了,誰知後來又拉上去,所以這週最後賠了500多塊。

買Put/Call的時間真的要盡量愈晚愈好,不然真的很難賺得到錢。

DELL R740 安裝esxi 6.7 找不到硬碟


在一台新買進來的DELL R740要安裝ESXI6.7時,居然一直找不到內建的硬碟。

已在IDRAC裡確認RAID5的虛擬硬碟已建立了,但在裝ESXI時就是找不到。

後來就上網亂找,發現DELL官網有出ESXI6.7的安裝檔,居然就可以了,實在有點麻煩。

可以在下列網站去下載:

 https://www.dell.com/support/home/zh-tw/drivers/driversdetails?driverid=j75ny


When attempting to install ESXi 6.7 on a newly purchased DELL R740, the internal hard drive couldn't be detected.

I verified in IDRAC that a RAID5 virtual disk had been created, but during the ESXi installation, it remained inaccessible.

Afterwards, I searched online and discovered that DELL's official website offered an ESXi 6.7 installation file, which surprisingly resolved the issue. It was a bit troublesome, though.

You can download it from the following website:

https://www.dell.com/support/home/zh-tw/drivers/driversdetails?driverid=j75ny

2022/03/25

OUTLOOK無法直接開啟PPT附件 另存也不行

 有一台電腦的OUTLOOK在收到PPT的附件時,都無法直接開啟附件,另存後,開啟也會跳錯誤,無法正常操作。



但同一封信在其他電腦上的OUTLOOK都可以正常開啟,所以PPT檔案是沒問題的,那就是個別電腦的問題了。

後來是去POWERPOINT的設定,把受保護的檢視取消就解決了。



On a particular computer, Outlook was unable to directly open PowerPoint attachments. Even after saving them and attempting to open, an error would occur, preventing normal operation.
However, the same email with the PowerPoint attachment could be opened without issues on other computers using Outlook. Therefore, the problem seemed to be specific to that individual computer.
Eventually, the issue was resolved by adjusting the settings in PowerPoint and disabling the protected view.


2022/03/21

本週有點感覺的選擇權策略操作-202203w4

 3月第四週還剩兩天結算,這週整個就是慘。

大區間的策略,主要是做Put Spread,但因為有買了1組Call Spread,要收集權利金來買Put,誰知就一直往上漲,Call Spread就GG了。

然後Put Spread一開始有50~80%左右就停利,但一直漲上去,沒機會在好的價位在進場做,所以最後這些獲利變的無法抵消Put的成本。

這週加個手續費大概會虧到6500吧。

下週要嚴守只做大區間的單邊就好,先單純一點,能穩定有獲利是現在最重要的目標。

2022/03/18

Forti SSLVPN 禁止特定IP連線

 Forti 防火牆上的SSLVPN連線功能,在GUI的設定介面裡,可以設定只允許特定IP連線,屬於白名單的方式。



可是公司的人會去其他國家出差,所以也無法確定到底哪些外部IP會連進來做SSLVPN的連線。 禁止特定IP連線。

然後又發現有特定的IP一直試著用不同帳密在TRY SSLVPN連線,實在有點擔心。

後來發現是有設定可以把白名單的限制方式,改成黑名單,但這要用指令來開啟

#config vpn ssl settings

     set source-address-negate enable

設定好之後,原本在GUI上啟用的白名單連線,就會變成是黑名單的效果了,只是在GUI的畫面上,上面還是一樣是寫允許清單,而不是禁止清單。



Forti SSLVPN Blocking Specific IP Connections

The SSLVPN connection feature on the Forti firewall allows you to set up a whitelist of specific IP addresses that are allowed to connect through the GUI configuration interface.

However, in our company, employees often travel to different countries, making it difficult to determine which external IP addresses will be used for SSLVPN connections. Therefore, we want to block specific IP connections.

We also noticed that there were certain IP addresses continuously attempting to connect through SSLVPN using different credentials, which raised some concerns.

Eventually, we discovered a configuration option that allows us to change the whitelist restriction to a blacklist, but it requires using commands.

#config vpn ssl settings

 set source-address-negate enable

After setting this up, the whitelist connections that were previously enabled in the GUI will effectively become a blacklist. However, in the GUI interface, it will still indicate "Allow List" instead of "Block List."


2022/03/17

Forti SSLVPN 程式離線安裝

 Forti防火牆上的sslvpn 連線程式,可以上forti的網站下載。

但下載下來的安裝程式並不是完整的,執行時才會再連上網下載真正的安裝程式到電腦的一個暫存資料夾,載完後才執行安裝,有點浪費時間,而且一定要有網路功能,才能進行安裝。

所以就想找能不能有一個實際的安裝檔,這時就要這麼做

一開始先找一台電腦,照上面的方式,下載最新的安裝程式,執行後會再下載真正的安裝程式,下載好後就會進行安裝,跳出安裝畫面。

這時請到本機的 %LocalAppData%\Temp directory 資料夾中,會看到sslvpn 連線程式的真正安裝檔,檔名會叫"FortiClientVPN...."之類的,蠻好找的,把這個檔案複製出來。

之後其他台電腦要裝,就直接用這個檔案來裝就行了。


Forti SSLVPN program offline install

The SSL VPN client program on the Forti firewall can be downloaded from Forti's website.

However, the downloaded installation program is not complete. It only connects to the internet during execution to download the actual installation files into a temporary folder on the computer. After the files are fully downloaded, the installation process begins. This method is time-consuming and requires an internet connection to complete the installation.

Therefore, the goal is to find an actual installation file. Here's how to do it:

Start by using a computer to download the latest installation program following the aforementioned steps. After executing it, the program will initiate the download of the actual installation files. Once the download is complete, the installation process will begin, and an installation window will appear.

At this point, navigate to the "%LocalAppData%\Temp" directory on your local machine. You will find the actual installation file for the SSL VPN client program there. It will have a filename similar to "FortiClientVPN...." and should be easily identifiable. Simply copy this file.

For installing on other computers, you can directly use this copied file for installation.

2022/03/16

本週有點感覺的選擇權策略操作-part3

 前兩次的週選策略都沒弄的很好,所以都賠蠻多的。

這週有小心一點,其實到星期四晚上就建的差不多,後來就沒什麼機會可以做調整,然後就一直保持最多虧損500塊的狀況。

今天結算本來下殺,有機會賺錢,結果快收盤又拉上去,最後就變賠,就是500塊,但連同手續費加進去,就1500塊左右。

很可惜還是沒賺錢。

重灌win10找不到硬碟

 今天把win10 iso做成安裝usb,重灌的時後,居然在過程中,找不到任何硬碟,換了不同的win10版本也是,這台筆電是這兩年出的,怎麼會這樣。

後來上網查了一下,居然是少了某個驅動,要去下載下來丟到隨身碟裡,重灌時要載入這驅動才看得到硬碟,方法就參考下列網址吧。

https://www.asus.com/tw/support/FAQ/1044458/


when creating a Windows 10 installation USB from an ISO file and attempting to reinstall the operating system, no hard drives were detected during the process. Even after trying different versions of Windows 10, the issue persisted. This laptop was released within the past two years, so it was unexpected.

After conducting an online search, it was discovered that a specific driver was missing. It was necessary to download the driver and save it to a USB drive. During the reinstallation process, the driver needed to be loaded in order to detect the hard drives. For detailed instructions, please refer to the following website:

https://www.asus.com/tw/support/FAQ/1044458/