Machine: Asus UX303

OS: Windows 8.1 64-but

Status as at 2020-05-25:  fail to solve

1. sfc /scannow returns this message — “Windows Resource Protection found corrupt files but was unable to fix some of them. “
2. Run “DISM” as follows:
   1. Type “cmd” in windows search bar
   2. Right click on “Command Prompt”
   3. Select “Run as Administrator”
   4. Type “DISM /Online /Cleanup-Image /CheckHealth” without quote and press ENTER
   5. Type “DISM /Online /Cleanup-Image /ScanHealth” without quote and press ENTER
   6. Type “DISM /Online /Cleanup-Image /RestoreHealth” without quote and press ENTER
      (source: https://answers.microsoft.com/en-us/windows/forum/all/sfc-scannow-found-errors-but-couldnt-fix-all-of/663ec1fa-a215-41b8-abbb-2aa1cca703e2)
3. If “DISM /Online /Cleanup-Image /RestoreHealth” return this message — “The source files could not be downloaded. Use the “source” option to specify the location of the files that are required to restore the feature.”
   then
   1. mount the “iso” file of the Windows
      (the “iso” file is mounted as “E:\” drive)
   2. Type “DISM /Online /Cleanup-Image /RestoreHealth /Source:E:\” without quote and press ENTER
      (source: https://www.thewindowsclub.com/dism-fails-source-files-could-not-be-found/ )
4. Same error message appeared — “The source files could not be downloaded. Use the “source” option to specify the location of the files that are required to restore the feature.“

Note: the report has been revised and moved from http://survey.dosh.gov.my/laporanhariancovid19/ to https://notification.miti.gov.my 

you can view the latest and updated video demonstration here …

Continue reading →

1. Open Windows PowerShell and copy below command into it

   # Create Keys for TLS 1.2 if not exist
   
   new-item -path "HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols" -Name "TLS 1.2"
   
   new-item -path "HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2" -Name "Server"
   
   new-item -path "HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2" -Name "Client"
   
   new-itemproperty -path "HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client" -Name "Enabled" -Value 1
   
   new-itemproperty -path "HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client" -Name "DisabledByDefault" -Value 0
   
   new-itemproperty -path "HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server" -Name "Enabled" -Value 1
   
   new-itemproperty -path "HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server" -Name "DisabledByDefault" -Value 0

2. Reboot server
3. To check whether TLS 1.2 is configured, open Registry Editor and go to this path:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols

   

   in this picture, it shows that Windows has “SSL 2.0” and “TLS 1.2” security protocol installed.

Problem: mp4 video, “vcom-showing-connected-then-disconnected.mp4”,  in https://mobitek-system.com/blog/2017/11/vcom-showing-connected-then-disconnected/ cannot be playbacked.

Cause: encoding used is not supported by web browser even though the “vcom-showing-connected-then-disconnected.mp4” video can be played in Windows Media Player.

Suggestions: for HTML5 in general, the optimized video encoding would be H.264 for .MP4 or WEBM for .webm (refer to https://help.encoding.com/knowledge-base/article/html5-video-format-conversion-support/)

2 Solutions:

1. use VLC to convert, refer to the guide in http://www.pavtube.com/vlc-convert-avi-to-mp4.html; or
2. use https://video.online-convert.com/convert-to-mp4  to convert “vcom-showing-connected-then-disconnected.mp4” using “H.264” codec

After conversion, the video can be playbacked in web browser.

1. db_owner role should only be given to the administrator who responsible for the database because this role can DROP the database
2. db_datareader and db_datawriter is the minimum access that should be given to normal user to do the basic SELECT, UPDATE, INSERT and DELETE operation to the database

Source:

1. https://docs.microsoft.com/en-us/sql/relational-databases/security/authentication-access/database-level-roles?view=sql-server-ver15
2. https://www.mssqltips.com/sqlservertip/1900/understanding-sql-server-fixed-database-roles/

1. Create an user account on the computer that act as a server, the username and password must used exactly like the account used in client computer
2. In SQL Server Management Studio:
   • Expand “Security” -> expand “Logins” -> “New Login”
     
   • Click “General” -> select “Windows authentication” -> click “Search”
     
   • Type the account name that has been created on server computer, click “Check Names”
     
   • Alternatively you can do this step by clicking “Advanced” button -> “Find Now” -> find the account name in the search results -> click “OK”
     
     
   • Click “Server Roles” -> check for sysadmin
     
   • Click “User Mapping” -> choose database -> check for db_datareader and db_datawriter
     

Note: You do not need to enter the password as SQL Server will ask Windows to validate the user password. (source: https://www.virtual-dba.com/differences-windows-sql-server-authentication/)

1. You can choose what type of login activity that you want the SQL Server to log. By default, SQL Server will log the “Failed logins only” activity only. To choose the login activity, right-click at your “Server <instance name>” -> “Properties”. In Server Properties, click “Security” and choose the activity in Login auditing area:
   • None
   • Failed logins only
   • Successful logins only
   • Both failed and successful logins
     
2. To view the MS SQL Server log files, expand “Management” -> expand “SQL Server Logs“, click any log date that you want to view:
   
3. All the login activities can be viewed in the Log file summary area: