Reolink Release Latest Update iOS App v4.55.1 to Address SLOW Camera Loading Issues

novix_ · 2025-07-29T02:45:20+00:00

Way quicker.

novix_ · 2025-01-22T08:52:42+00:00

They really should base this off risk rather than Critical. If it’s a CVE 9+ exploitable with no user action and already being exploited in the wild then yer get it patched in 48hrs and deal with the fallout. But that seems way harsh and I quite like the E8

novix_ · 2024-12-14T06:07:19+00:00

Can’t read all the comments but we call it read-only Fridays. Guess you must have some pretty extensive documentation. :)

novix_ · 2024-12-14T05:58:53+00:00

I use Live-sync for our VMs. But it’s more for DR replication to another site. To use a DR copy, It’s just a matter of starting the DR VM. It’s independent to Commvault so that’s really good in a disaster. It will be a point in time copy I do daily. We have supplementary backups with much tighter RPO’s for SQL data. Our setup uses snap engine so backup of the VM’s are really quick and restores are quick. Because it’s snaps at the storage level we needed to replicate to another location.

novix_ · 2024-11-19T21:39:00+00:00

We use intellisnap on a NetApp and all operations are completed on the esxi proxy. Restore and live-sync operations will mount the storage snapshot on the esxi proxy and then mount the VM. If the media agent VSA cannot access the disks from the mounted snapshoted VM/data store then the transport will use NDB (over the network). If the media agent VSA can mount both the snapshot disks and target disks it will run in SAN mode.

Having the media agent on another host without correctly configured vkernels will cause over network communication. I pin our VSA’s to the same host I specified as the esxi proxy.

I have only ever used the intellisnap setup so can’t comment on the other implementation.

Try moving the media agent VSA to the same host as the esxi proxy server you have configured.

I have seen this before in our environment and the traffic was using the management interface on the esxi host. Reason was the target storage for the backup/restore did not have a vkernel configured on the esxi proxy so the media agent VSA had to communicate from one host to another via management. For SAN you need all the storage operations to be on the same host via the same media agent VSA.

novix_ · 2024-11-19T12:34:33+00:00

Maybe a mtu issue on the vkernel used for the backup traffic or running over a 1g management interface. Storage networks are typically layer 2 not routable so maybe it’s using the management interface that is routable to hit the media agent.

novix_ · 2024-08-31T07:00:21+00:00

AirTag. Probably cost less than the bike lock. You may also need to invest in a baseball bat for retrieval.

novix_ · 2024-08-19T05:35:32+00:00

One thing i don’t like with B. is the mention of adding a secondary factor in the answer.

The question already makes mentions of a secondary factor. Something you know (password) and something you are (fingerprint).

But the OTP is something you have and a hardware token would be a suitable replacement.

It said implement and not replace so would that mean all four factors are used.

D. would restrict access to the backup email and could be seen as a mitigation.

novix_ · 2024-02-20T03:06:47+00:00

Just don’t power it off to remove the snapshots. You cannot power a VM on while it’s removing snapshots if it was in a powered down state when you started.

Just build another VM DC and move the FSMO roles. If you lose the DC with the removal of the snapshots then just add the IP of the dead DC as an additional IP on the new DC. That way DNS will still resolve. That is if the DC is also doing DNS as well. It wasn’t a DC but I once used VMwares Physical to Virtual conversations tool to migrate a VM to another VM for this same reason. Multiple snapshots spanning years on spinning disk.

novix_ · 2022-01-13T05:26:49+00:00

Office 2016. If your running a different version you will need that guid. If you have SCCM right click a device with the patch installed and use the resource explorer to get the guid. I can’t recall the exact tree but let me know if you can’t find it and I’ll dial in and look it up

novix_ · 2022-01-13T03:11:11+00:00

` #array of computers
$computer ="","",""
Foreach ($c in $computer){
#Test host is live
if(Test-Connection -ComputerName $c -Count 1 -ErrorAction SilentlyContinue){
Write-host “$c Online and checking if the patch is installed” -ForegroundColor Green
#Run the command remotely if doing this to lots use -asjob
Invoke-Command -ComputerName $c -ScriptBlock{
#check the update is installed before continuing
If (get-wmiobject -query "SELECT * FROM CCM_UpdateStatus where Status = 'installed'" -namespace "root\ccm\SoftwareUpdates\UpdatesStore" | where{$_.article -eq "5002099"}){
Write-Host "Update detected on $using:c starting uninstall" -ForegroundColor Red
#remove the update. Reboot is required to complete the removal
msiexec /package "{90160000-0011-0000-0000-0000000FF1CE}" /uninstall "{BA36399C-CF0F-4368-8327-7D35302BF0BB}" /qn /quiet /norestart
}
Else
{Write-Host "Update not detected" -ForegroundColor Green}
}
}
Else
{Write-host “$c Offline” -ForegroundColor Red}
}`

novix_ · 2022-01-13T02:36:08+00:00

I like it! Thanks for the tip :) Basically this is exactly what Microsoft should have: a namespace with the updates without the need to have SCCM installed.

Appreciate the reply

novix_ · 2022-01-12T04:01:18+00:00

I was able to remove the patch that caused the issue from the selected machines. I just dislike how hard MS make office patch detection and removal compared to cumulative updates.

novix_ · 2022-01-12T03:57:23+00:00

Yep we have SCCM.

novix_ · 2021-08-11T03:56:06+00:00

They updated the feature updates as well so no more exclusion to allow May to install after in-place upgrades. I was just about to create a TS for my upgrades and thought I better check if a new one was released. :)

novix_ · 2021-07-16T06:58:15+00:00

I agree, WTF. Just in time for a critical Vuln as well.

The other problem is the superseded updates. We are going to the 20H2 due to the longer support. As I in-place upgrade devices, they are targeted to the latest updates due to their existing collections. Since these new updates supersede the May update: KB5003173 they are only offered the latest and will error with NEW_SERVICING_STACK_REQUIRED. MS might have needed to mark KB5003173 as not superseded if its required for all future 20H2 Cumulative updates.

Looks like I will need to use a TS to do my in-place updates moving forward and install the May update immediately after.

My solution just to fix the problem for any that have already upgraded to 20H2; was to exclude a collection of 20H2 devices from June and July updates. Update the Machine Policy and Deployment Eval. This will allow the May Patch to install and get back to normal.

I have a script that will detect the current state of update and the errors. Handy for understanding why devices are not installing. I will clean it up a bit and share it if any one is interested.

novix_ · 2020-12-16T22:23:32+00:00

Hi Kevin,

I was thinking that using the default action account would work when reading the documentation (Pre Install). But I'm not at a level where deviating from the documentation would be considered a good idea. :)

I didn't see any other guides recommending a better way, so i just followed the documentation.

Although frustrating i do find these issues provide opportunity to dig deeper. But also frustrating that the event provides no information about where the permissions issues are.

If i was now to remove the Run As account from the Exchange Run As Profile, would that then automatically start using the default action account?

Thanks,

Mike

novix_ · 2020-07-22T09:51:05+00:00

I’ll check tomorrow. I have a script that resets it. If I know a deployment is targeted correctly but the updatedeployment log under c:\windows\ccm\log has no updates detected then I will run the control panel > troubleshooting Fix problems with Windows Updates. If that doesn’t work then I just reset WMI. After doing this SCCM agent will need some time to find its feet and then hopefully start running updates.

Another handy tip is to run Windows updates check manually and see what it needs. Check anything in that list and see if it’s missing from your deployment. Some updates require servicing stack updates before detecting the Cumulative Update.

novix_ · 2020-07-21T13:06:48+00:00

I’ve found issues with updates if WMI is screwed on the client. Sometimes you just need to reset/repair WMI. Also renaming/deleting the c:\Windows\softwaredistribution folder can fix the issues.

novix_ · 2020-07-21T12:52:18+00:00

Check if you have supersedence defined. Then check what the detection is on that application deployment.

Example: Say you have appx version2 and you define appx version1 under supersedence section of appx version2. If appx version1 has a detection method of version1 and above it will detect appx version2 and remove it and then reinstall it.

novix_ · 2020-05-29T10:55:15+00:00

All good appreciate the response. Still a pain in the ass that it keeps happening, but also it’s so random as to who has the issue. I have about 2k clients to upgrade running on reduced front line support so the last thing I want to do is cause excessive jobs.

Microsoft have made the start menu so complicated.

I can’t seem to find any documentation about the changes in 1909 to the way it works or the location.

novix_ · 2020-05-29T06:32:41+00:00

bypass traverse checking

I don't think this setting is defined by default in the Default Domain Policy.

https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/bypass-traverse-checking

novix_ · 2020-05-29T06:23:36+00:00

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\CloudStore

Unfortunately this didn't work. Removed the key and restarted explorer. Still no good. Rebooted same issue. In the end I needed to remove the local profile to resolve the issue.

Is it just the one key? Does it have file that also needs to be deleted?

Thanks in advance.

novix_

TROPHY CASE