While Windows installed with Terminal Server role it does work without License for 120 Days on trail license, where within 120 days if the License server is not Connected the server will stop accepting connection with below error and event ID
The solution was to delete the REG_BINARY in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod
Only leaving the default.
|
1 2 3 4 |
for ($i=1; $i -le "3"; $i++) { "Loop" } |
@%SystemRoot%\System32\inetsrv\appcmd set config -section:staticContent -+”[fileExtension=’.’, mimeType=’text/plain’]”
Generally the recommended path for upgrading a High Availability cluster is to first upgrade the secondary node. After it comes back up, disable CARP on the primary node under Status > CARP, and run on the secondary for a period of time. If the secondary node is running comfortably as desired, upgrade the primary node and it will switch back to MASTER status after rebooting for the upgrade.
UPDATE users AS U1, users AS U2
SET U1.name_one = U2.name_colX
WHERE U2.user_id = U1.user_id
del /f/s/q foldername > nulrmdir /s/q foldernamePower/VCC sensor lead — Orange CAT-5/6 wire (pin 2)
Data sensor lead — Blue CAT-5/6 wire (pin 4)
GND (ground) sensor lead — White/Blue CAT-5/6 wire (pin 5
By default, the emonPi is set to the UTC time zone. You can set the time zone to match your location by connecting to the emonPi via SSH, and running :
|
1 2 3 4 5 6 7 8 9 10 |
To check current time on the emonPi $ date Enter read-write mode $ rpi-rw Run Raspberry Pi setup $ sudo raspi-config Select internationalization options > timezone Exir raspi-config Return to read-only mode $ rpi-ro |
If you want to erase all logged data, input processing and configuration from the local Emoncms on the emonPi, run the ‘factoryreset’ script in the emonpi directory:
$ rpi-rw
$ cd emonpi
$ sudo ./factoryreset
$ rpi-ro