It turns out my new iPad removed PPTP since iOS10 due to outdated and unsecured protocol of PPTP, and there is no 3rd party app for PPTP VPN clients for iOS12.
So the only solution without jailbreak is to upgrading my old VPN gateway (running on Windows Server 2003) from PPTP to L2TP IPSec.
Simply select “Allow custom IPSec policy for L2TP connection” and type in a Pre-shared Key in the RRAS property.
On the VPN client side, all you need to do is to select L2TP and type in the Pre-shared Key under Security tab.
1. Menu press “e”
2. Find the line “linux16 vmlinuz…: at the end add “init=/bin/sh”, then Ctrl + x
3. mount -o remount,rw /
4. passwd root
5. touch /.autorelabel
6. exec /sbin/init (You will need to WAIT for a few minutes)
Today I found out one of the CentOS 7-1611 VMs has no GUI available and also there is no SSH login at the console.
Worst the screen indicates “[sda] Assuming drive cache: write through”, seems it’s hang at startup.
In fact it’s working fine, then I SSH into the server remotely, and issue “systemctl set-default multi-user.target” which set the default login interface to be text based SSH login, the SSH login screen appears after the reboot.
systemctl isolate multi-user.target to return to command mode
systemctl isolate graphical.target to return to graphical mode
Somehow, systemctl isolate graphical.target turns the screen into blank, still have no idea what’s causing this, nor startx works.
Finally, the vCenter VM Guest OS status changed from CentOS 4/5 64 bits to Other (32-bit) automatically everything after reboot, anyone knows why? Pls drop me a line, thx.
The trick is to create an extra environment variable PHPRC and point to the specific PHP version directory that contains php.ini.
* DO NOT put an extra \ at the end, ie, C:\Program Files (x86)\PHP 7.1.5 is the correct form without the ending \.
* Make sure you downloaded the Non-Thread Safe x86 version for PHP release
Extra Note:
For FastCGI on Windows Server 2003, the last supported binary Non-Thread Safe x86 version of PHP is 5.4.9. (ie, php-5.4.9-nts-Win32-VC9-x86.zip)
Enable the User-Defined INI files
If you want to allow Web application owners to control PHP settings themselves, you can enable a user-defined PHP configuration.
Add the following setting, which specifies the name to be used for user-specific INI files, to the main php.ini file. Setting this to an empty value disables the user-defined PHP configuration.
console
user_ini.filename = .user.ini
Create a file called .user.ini in C:\inetpub\website1.com\ folder, and add the following:
console
max_execution_time = 300
Add the following to the file .user.ini in C:\inetpub\website2.com\ folder:
console
upload_max_filesize = 12M
Note that if your main php.ini file has [PATH] sections that point to the root folders of these sites, then you need to remove those sections; if you do not remove those sections, the user-defined settings will not take effect.
Use phpinfo() or ini_get(”max_execution_time”) to check that the new settings have overwritten the default settings. Create a PHP file with the following text and save it in the Web root folder:
Note also that when you enable the user-defined INI files, the settings in those files are cached by the PHP engine to avoid re-reading those files for every request. This means that if the user makes a change to .user.ini file, then that change may not take effect right away. Instead it may take effect after the cache time to live (TTL) has expired. The cache TTL value is controlled by the php.ini setting user_ini.cache_ttl, which is set to 300 seconds (5 minutes) by default.