Timothy Lam

A online website, check the email server issues

https://www.mail-tester.com/ 

https://www.nextofwindows.com/5-ways-to-generate-and-verify-md5-sha-checksum-of-any-file-in-windows-10

certutil -hashfile z:\desktop\lsr.exe SHA512

powershell 4.0

1 ) Add Registy Key to Windows 10 Client  Refer 如何在 Windows Vista 和 Windows Server 2008 中，於 NAT-T 裝置後方設定 L2TP/IPsec 伺服器

run Regedit in Windows 10 Client and go to below "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent"  add DWORD 32 Key name is "AssumeUDPEncapsulationContextOnSendRule" and Value is "2" and reboot PC to applied.

2) Create New VPN connection

On Windows 10 client -> start -> setting -> Vpn

create a VPN with correct login credential.

Modify network setting 

Because all internet traffic will go to VPN, if you want only some services via VPN then Change default gateway back to local gateway and add statics route destination ip address (optional)

Add statics route 

add statics route persistent command is  "route -p add 192.168.0.0 MASK 255.255.255.0 10.2.0.0"  (if ip address is 192.168.0.xxx will route to VPN)

Create a Shared Folder from control panel

click only "Hide sub-folders and files from users without permissions" under General Tab.

convert to Windows ACL

user File Station to grant permission as normal

You will receive notification via email  if harddisk crashed found in  Synology NAS, after you logon into Synology NAS panel and found degraded in Storage Manager.

Purchase a new HDD immediately for HDD replacement, if your Synology NAS is supported hotplug (shutdown is not necessary), remove the damaged one and replace a new one, after login Synology panel and then start to repair -> Storage Manager ->Volume -> Manage

Although it seems MS removed the Adapter and Bindings tab you can still change the priority order.  That tab was just setting a registry key which you can either update manually using regedit or write a script to change it.  

The registry key is here

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Linkage\Bind

In this key you will see the Id for each of your adapters. They are listed in priority order from top to bottom with the top being the highest priority. In order to figure out which one is which you can run these 2 commands in a command prompt using wmic to query the information for your adapaters.

This will give you the index and name of each adapter. Find the name you are looking for and note the Id.c:\wmic nic get Index,NetConnectionId

Now run this command to get the Index and Id

c:\wmic nicconfig get Index,SettingId

Go to Administration->Commands

startup scrips

# Save Startup WANIF=`get_wanface` ifconfig $WANIF:1 115.xxxx.xxx.11 netmask 255.255.255.248 broadcast 115.xxx.xxx.255 ifconfig $WANIF:2 115.xxx.xxx.12 netmask 255.255.255.248 broadcast 115.160.159.255 ifconfig $WANIF:3 115.xxx.xxx.13 netmask 255.255.255.248 broadcast 115.160.159.255 ifconfig $WANIF:4 115.xxx.xxx.14 netmask 255.255.255.248 broadcast 115.160.159.255

firewall scrips:

# Save Firewall

# WAN .11 -> LAN .65 iptables -t nat -I PREROUTING -d 115.xxx.xxx.11 -j DNAT --to 192.168.1.65 iptables -t nat -I POSTROUTING -s 192.168.1.65 -j SNAT --to 115.xxx.xxx.11 iptables -I FORWARD -d 192.168.1.65 -p tcp --dport 80 -j ACCEPT

iptables -I FORWARD -d 192.168.1.65 -j ACCEPT   <- forward all port to 192.168.1.65

scenario: Two standalone windows hyper-v replica connection was established and replication was enable between primary host (testhost.tplhk.local) and replica server (testreplica.tplhk.local).

Planned Fail over (Scenario: for example primary host need to shutdown for MA, all VMs in primary host switch to replica server and continue running on replica server until primary host resumed)

steps

stop VM in primary host (testhost.tplhk.local)

right click VM and select Planned Failover with Reserve and start VM in replica server selection (Now VM in testreplica.tplhk.local server with start automatically and replica role will swap each other testhost changed to replica server and testreplica changed to primary server)

When original host resumed(testhost.tplhk.local)

stop VM in replica host (testreplica.tplhk.local)

right click VM and select Planned Failover with Reserve and start VM in replica server selection (Now VM in testhost.tplhk.local server with start automatically and replica role will swap back). ** all change during in testreplica will still here , no data lost ****

UnPlanned Fail over (Scenario: for example primary host unplanned shutdown or damaged that unable to resume in short time. then run VM in replica server.)

steps

right click VM and select failover (on testreplica.tplhk.local , VM will start and running)

once primary host resumed, may be over a month and replica setting were applied.

shutdown VM (on testreplica.tplhk.local)

right click VM and select Planned Failover with Reserve and start VM in replica server selection (on testreplica.tplhk.local) - a inital copy will transfer from testreplica.tplhk.local to testhost.tplhk.local) and VM will start in testhost.tplhk.local.)

Scenario: You have two standalone Windows 2012 r2 with Hyper-V installed, you need to setup replica between each other. for DR propose.

Prerequisite:

FQDN Name both two standalone Windows 2012R2 server.

DNS Server records or add into hosts file in windows\system32\drivers\etc\hosts. add to hosts will be use at this posts

Makecert.exe download and install both two standalone server  in https://www.microsoft.com/en-us/download/details.aspx?id=8279

FQDN Name both two standalone Windows 2012R2 server. (you must FQDN name for example testhost.tplhk.local and testreplica.tplhk.local will be used.  *** only  netbios (testhost) name doen’t work ***)

To add FQDN name both two standalone server -> Right click Windows menus -> system -> advanced system settings -> computer name -> change -> more type Primary DNS suffix of this computer “tplhk.local” in this sample. so FQDN name will be “testhost.tplhk.local” in primary host , “testreplica.tplhk.local” in replica host. restart both windows server.

Modify hosts files both two standalone windows server. testhost.tplhk.local is primary hyper-v host in this sample testreplia.tplhk.local is replica hyper-v host in this sample

Makecert both primary and replica windows server 2012. (please refer to the below link for more detail)

https://blogs.technet.microsoft.com/virtualization/2013/04/13/hyper-v-replica-certificate-based-authentication-makecert/

=================== On Primary Host testhost.tplhk.local

===================

makecert -pe -n "CN=HostRootCA" -ss root -sr LocalMachine -sky signature -r "HostRootCA.cer"

makecert -pe -n "CN=testhost.tplhk.local" -ss my -sr LocalMachine -sky exchange -eku 1.3.6.1.5.5.7.3.1,1.3.6.1.5.5.7.3.2 -in "HostRootCA" -is root -ir LocalMachine -sp "Microsoft RSA SChannel Cryptographic Provider" -sy 12 testhost.cer

*** copy ReplicaRootCa.cer from testreplica.tplhk.local *******

certutil -addstore -f Root “ReplicaRootCA.cer”

reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization\Replication" /v DisableCertRevocationCheck /d 1 /t REG_DWORD /f

=================== On replica Host testreplica.tplhk.local

===================

makecert -pe -n "CN=ReplicaRootCA" -ss root -sr LocalMachine -sky signature -r "ReplicaRootCA.cer"

makecert -pe -n "CN=testreplica.tplhk.local" -ss my -sr LocalMachine -sky exchange -eku 1.3.6.1.5.5.7.3.1,1.3.6.1.5.5.7.3.2 -in "ReplicaRootCA" -is root -ir LocalMachine -sp "Microsoft RSA SChannel Cryptographic Provider" -sy 12 testreplica.cer

*** copy HostRootCa.cer from testhost.tplhk.local *******

certutil -addstore -f Root “HostRootCA.cer”

reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization\Replication" /v DisableCertRevocationCheck /d 1 /t REG_DWORD /f

Export testhost.tplhk.local and import to testreplica.tplhk.local run MMC and snap-in certification as the below

copy testhost.pfx to testreplica.tplhk.local

and double click testhost.pfx to import cert in testreplica.tplhk.local server.

Export testreplica.tplhk.local and import to testhost.tplhk.local run MMC and snap-in certification same as above.

copy testreplica.pfx to testhost.tplhk.local

and double click testreplica.pfx to import cert. in testhost.tplhk.local server.

“Your PC ran into a problem and needs to restart. We’re Just collecting some error infro, and then you can restart. (100% complete)”

You may got the above error message, when start a Windows 2012 AD guest VM which restored successfully from Windows server backup.

Scene:

restore a windows Hyper-V backup (backup from windows built-on application Windows Server Backup over 3 months for example backup date Jan 1 2016 ) to a new machine.

successfully restore via Windows server backup  (restored date is April 1 2016)

change Hyper-V config. setting in Hyper-V manager

start VM (Windows 2012 AD )

got error.

Solution:

change Windows Hyper-V Host machine date go back to Jan 3, 2016, close backup date as possible.

perform windows server backup again to restore the backup as normal.

change Hyper-V config. setting in Hyper-V manager.

start VM (windows 2012 AD) , you should start without any error

login to VM.

change guest system date to the real time (for example April 1, 2016).

reboot VM.

chnage Hyper-V host machine to the real time (for example April 1, 2016).

Description

You may got error “Sage 300 ERP UI Container .....” when printing any report in Sage Accpac. It is because failure during installation or unable to register crystal report dll. what you need to do is 1) download and reinstall .net 4.0 or the crystal reports runtime engine manually and than register the dll again.

Error Description from Support.na.sage.com

https://support.na.sage.com/selfservice/viewContent.do;jsessionid=3B2552B383510F117348A1F2FF66237A.worker1d?externalId=18397&sliceId=1

Crystal Report run-time download

You have to do the following steps:

Run defrag in the guest (Windows only)

With a Linux Guest run this:

sudo dd if=/dev/zero of=/bigemptyfile bs=4096k sudo rm -rf /bigemptyfile

Or:

telinit 1 mount -o remount,ro /dev/sda1 zerofree -v /dev/sda1

With a Windows Guest, download SDelete from Sysinternals and run this:

sdelete –z

Shutdown the guest VM

Now run VBoxManage's modifyhd command with the --compact option:

With a Linux Host run this:

vboxmanage modifyhd /path/to/thedisk.vdi --compact

With a Windows Host run this:

VBoxManage.exe modifyhd c:\path\to\thedisk.vdi --compact

With a Mac Host run this:

VBoxManage modifyhd /path/to/thedisk.vdi --compact

start virtualbox in terminal command is VBoxManage startvm VMName.

Create a shortcut in MacOS

run AppleScript Editor

type the below command  (WindowsXPSP3Testing is Virutal Machine Name)

do shell script "/Applications/VirtualBox.app/Contents/MacOS/VBoxManage startvm WindowsXPSP3Testing"

File -> Export..  to Application. and change file format to Application