Welcome, Guest |
You have to register before you can post on our site.
|
Forum Statistics |
» Members: 139
» Latest member: NtenQag
» Forum threads: 215
» Forum posts: 433
Full Statistics
|
Online Users |
There are currently 45 online users. » 0 Member(s) | 45 Guest(s)
|
Latest Threads |
Cobra 148GTL Versions
Forum: Hardware - Manuals, Mods etc.
Last Post: admin
07-04-2022, 04:26 PM
» Replies: 0
» Views: 136
|
CRT6900N V6 Service Manua...
Forum: Hardware - Manuals, Mods etc.
Last Post: admin
28-09-2021, 02:59 PM
» Replies: 0
» Views: 496
|
CRT6900N and PTT for QRM ...
Forum: Hardware - Manuals, Mods etc.
Last Post: admin
27-09-2021, 05:52 PM
» Replies: 0
» Views: 570
|
Cashbook Complete - Insta...
Forum: General Discussions
Last Post: admin
09-07-2021, 05:38 PM
» Replies: 1
» Views: 1,127
|
Server 2019 Unplanned Shu...
Forum: General Discussions
Last Post: admin
28-10-2020, 08:18 AM
» Replies: 0
» Views: 1,262
|
Ping with Timestamp
Forum: Networking
Last Post: admin
18-09-2020, 01:59 PM
» Replies: 0
» Views: 1,396
|
V-79-57344-862 - Backup E...
Forum: Backups and Data Recovery
Last Post: admin
16-07-2020, 03:16 PM
» Replies: 0
» Views: 2,087
|
MRT and RCT Files with Hy...
Forum: Virtualisation (Hyper-V and VMware)
Last Post: admin
06-05-2020, 06:33 PM
» Replies: 0
» Views: 2,727
|
Reolink 2Mp Cameras & DVR
Forum: Home Automation
Last Post: admin
12-02-2020, 07:05 PM
» Replies: 0
» Views: 1,913
|
Disable Windows 10 Screen...
Forum: General Discussions
Last Post: admin
10-02-2020, 01:23 PM
» Replies: 0
» Views: 2,283
|
|
|
Server 2019 Unplanned Shutdown Event at every Reboot |
Posted by: admin - 28-10-2020, 08:18 AM - Forum: General Discussions
- No Replies
|
 |
After initial Server "unplanned" Shutdown (BSOD/Crash, hang or power failure), Windows creates Registry flags which are used to prompt the User/Users after a reboot for reason of unplanned reboot.
In a normal situation, after the User acknowledges the prompt, those Registry flags are removed/reset.
In many situations the Registry flags are not removed/reset even after acknowledging the prompt which leads Windows to perpetually prompt after every clean reboot.
Some say that that recent Security Updates are to blame and some with a focus on .NET.
The actual cause is insufficient Permissions on the Registry keys that are flagged - only Local Administrator has the Permission to successfully acknowledge the Prompt to clear the Registry flags.
You need to provide the correct Permissions to the Registry Key: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Reliability
In this case, we have given Domain Administrator's Full Control of this Key (not just Local Administrator). As this Server is also an RDS (Terminal) Server, we have given Domain Users Full Control too but that is your personal choice and may not be desirable if only you, the Domain Administrator, want to acknowledge/see this Prompt.
To manually clear the Registry Flags remove (delete) the Registry Values DirtyShutdown, LastAliveStamp, TimeStampInterval under the above Registry Key (or reboot the Server and acknowledge the Prompt again)
|
|
|
Ping with Timestamp |
Posted by: admin - 18-09-2020, 01:59 PM - Forum: Networking
- No Replies
|
 |
The native Windows Ping command can't record timestamps in the results without a lot of fussing around.
Use PowerShell and bang-out the following command to get timestamps on the ping results (replace COMPUTERNAME with either the Host Name or IP Address).
ping.exe -t COMPUTERNAME|Foreach{"{0} - {1}" -f (Get-Date),$_}
To send your results to a text file, pipe the results by appending the following.
ping.exe -t COMPUTERNAME|Foreach{"{0} - {1}" -f (Get-Date),$_}>c:\temp\pingresults.txt
|
|
|
V-79-57344-862 - Backup Exec Agent for Exchange not used for last full backup |
Posted by: admin - 16-07-2020, 03:16 PM - Forum: Backups and Data Recovery
- No Replies
|
 |
Full Error Message when backing up Exchange with GRT enabled:
V-79-57344-862 - Backup Exec Agent for Exchange not used for last full backup of this database. You must use the Exchange Agent to run a full backup before you run a differential or incremental backup.
Completed status: Failed
Final error: 0xe000035e - The Backup Exec Agent for Microsoft Exchange was not used to create the last full backup of this database. You must use the Exchange Agent to run a full backup before you run a differential or incremental backup.
Final error category: Resource Errors
For additional information regarding this error refer to link V-79-57344-862
I have seen this on all Versions of Backup Exec when using Incremental backups on Hyper-V and other Data using separate Backup Jobs.
Although, indeed, other types of Backups will cause this (Windows Backup or other Backups performed by other Software).
Full Backup Jobs are not affected by this error.
Incremental Backups rely on the Attribute set on a file to determine if it has been backed up since modified/created. These Attributes are then flagged (unflagged) during the Backup process. If other Backups of the same Data are run prior to your Backup Exec Job then Backup Exec will get confused and throw this error.
For us, we run separate Incremental Backup Jobs for Hyper-V and Data.
Turns out that, if we first run the Hyper-V Job then the Data Job, the Backup will fail with this error on the Data Backup.
If we first run the Data Job and then the Hyper-V Job then the Backups "usually" go through without this error.
Backup Exec somehow "thinks" that the previous Hyper-V Backup Job was to blame - not sure how but we have been able to reproduce it.
The problem still lays with the next Incremental Backup (second Incremental Backup after the Full Backup) - some sites, using different Windows Server and Hardware Versions, have unpredictable results - some work flawlessly and others throw these errors.
At some sites where there is ample storage available on the destination media and time-slot available, we do Full Backups instead of Incremental and lengthen the retention period.
|
|
|
Reolink 2Mp Cameras & DVR |
Posted by: admin - 12-02-2020, 07:05 PM - Forum: Home Automation
- No Replies
|
 |
This CCTV system is a step above the cheap Chinese ones that I have been using over the past 15-years. Cost has always been a factor in my decisions (isn’t that the same with everyone?).
The initial installation did not go as planned.
Initial setup was positive as we used 0.5M Network Patch Cables to each Camera to test before replacing existing Cameras.
It was a simple plan: to remove the existing PoE Cameras and DVR and replace them with the Reolink Cameras and DVR.
This plan soon turned to custard after days of trying to figure out why none of the 6 Cameras would connect but the old ones would continue to work OK.
It turned out that these new Reolink Cameras demand CAT6 Cabling – all would work OK with CAT5 as long as the cable runs were not longer than 5M.
So, mission accomplished; replaced all CAT5 cabling with CAT6 (400M in total) and all Cameras working as expected.
I’ve been running CCT since day zero but always limited to the cost-factor and ending up with cheap Chinee crap – forever upgrading hoping that things would get better but never did.
I had two simple demands.
1) be able to identify number plates and
2) provide Video evidence to the police without stuffing around.
My biggest peeve was always having to apologise to the Police that it took so long to firstly download the footage and then convert the Video from some weird and bizarre CRAP Video Format to something they could actually use without losing quality.
The Reolink system “partially” solved these issues as I will explain here:
Downloading Video footage directly to MP4 file format is a saviour (no more of that crap H264 to deal with)!
No more having to dick-around with third-party programs to convert while loosing quality.
The downloading of Video takes a long time and not what I expected from a brand with high score marks but still quicker than having to dick-around by converting H264 crap afterwards.
The Video Quality (compared to my previous 1024--resolution HD H264) is not that amazing and I was disappointed in that number plates were still not decipherable when they should be.
What pissed me off was:
1) Reolink 5Mp Cameras came on to the market (Amazon) two weeks after I received my 2Mp Cameras AT THE SAME PRICE!
2) That the Reolink Cameras you purchase are dedicated to their own DVR – meaning you cant use the Reolink Cameras on a non-Reolink DVR – or even use Reolink 4Mp Cameras on a Reolink 2Mp DVR!
3) The CPU usage is mostly maxed out (using 6 of the 8 supported cameras) - seriously underpowered CPU.
4) Response at switching quickly to the Software (Reolink Client) to check on something is sluggish and if left for more than 30-minutes or so shows all feeds as blank (white) screens until one is double-clicked to bring into the foreground. I suppose this would not affect some users who have the Software open all the time on a dedicated monitor but, for me, by the time you have messed around you have missed the live action.
Edit: Tried downloading footage today for an incident. The Software (Reolink Client) kept crashing after the first few video clips. It took multiple attempts to download one or two clips at a time.
Still experiencing...
|
|
|
|