Відео

You may need to allow system.run commands. Check our blog post on how to do that (link in description).

@@ReasonableITService Hi, Quick update - zabbix agent had to be restarted since the script I created loaded the config after installing the agent itself. Thank you

I know exactly what you're talking about, lol. Yah those things aren't packing a 1660ti..Ty for the kind words.

lol pretty much. We actually refurb and try to flip these guys for a profit: www.ebay.com/itm/204430830148

Please refer to video description.

I would start by running this command: top -u zabbix to identify processes consuming high CPU. You can also check the Zabbix server log file (/var/log/zabbix/zabbix_server.log) for any errors or warnings. Look for bottlenecks like SNMP trap queue is full or Timeout while receiving traps.

Great tip, thank you for sharing.

Additionally, I also discovered that if I'm attempting to copy the password from an existing user to a different user within "DB Browser for SQLite", I not only had to copy the "encrypted_password" value over, but also the "password_salt" value as well. It appears BOTH of those values are required to make a password function properly with copied from another Spiceworks user.

Gave you that warm fuzzy feeling inside too?

Recommend setting up a VPN connection to where your Dokuwik instance lives. After that, you can access it via browser the same way you would if you were sitting on the LAN of your Dokuwiki server.

This changes everything for me! I was watching reviews on launch and just came back to check if they updated and added nfs. thanks for the heads up!

Thank you for the feedback. You guessed correctly. However, adding a disclaimer about not having ‘early pre-release hands-on’ is irrelevant. You don’t need hands-on experience to conduct basic research and quickly determine a device’s limitations. Matter of fact, here are some additional limitations to consider and that were not covered in the video: - No cache support - No dual PSU redundancy - No SCSI protocol support If all these limitations don't concern you, the UNAS Pro could be a good fit. I’m not entirely surprised by these shortcomings either, it's a 1st gen model + UniFi is generally geared more towards tech enthusiasts rather than tech professionals. Hey it's quite possible that a future UNAS Pro 'Enterprise' edition could release and include many of these missing features. We'll see what happens.

​@@ReasonableITService It has power redundancy support.

@@realjoecast Power redundancy isn’t possible with a single power supply unit. A dual power supply configuration requires at least two separate power supply units. On the back of a UNAS Pro, you'll see only a single power socket, indicating that only one power supply is present-thus dual PSU support isn’t available at this time.

@@ReasonableITService Also on the back of the device you see the RPS connector, which is in effect a dual PSU system. The RPS connector would go into UI's RPS device which provides redundant power supply for up to six unifi devices. also like to point out, that no cloud account is needed, right in the setup menu it gives you the option of not using it and the option is not hidden in anyway. This is generally the same as every other unifi device. The extra app/vm support is really only an issue for enthusiasts or home labbers. Those in a medium to semi-large market would be using other solutions. Heck even in my home lab I'm not using most of that fluff on my synology instead using vmware and hyper-v. sure things like iSCSI support would be great but if you are going for that in a larger business setting you are probably looking at a more advanced solution like a powervault or nimble. this very well could be a perfect for a non-enterprise storage solution for those already in the unifi if they're looking for more storage in the future. But as typical UI, they're software needs to catch up. It is a solid first entry into the market. Not great, Not horrible just solid.

@@ReasonableITService hmm.. made another comment that disappeared. skipping all the other stuff i said. there is a RPS connector is for redundant power. It doesn't need cloud accounts either. the software stuff like vms, nvr, etc.. maybe supported at some point but really the target audience probably doesn't care about that.

Thank you for your input. Looks like the UNAS Pro can be setup and managed offline and supports local user account creation. However, that comes at a cost: - No remote management - No multi-factor Auth - No notifications - No cloud backups - No Teleport & site Magic VPN Also here are some more points to consider that were not included in the video: - No cache support - No dual PSU redundancy - No SCSI protocol support Obviously folks will have to make their own determination if they really need any of that stuff or can live without it. Cheers!

​@@ReasonableITService all valid points. Thank you for a less fanboy view on the product

We experimented with standard single-iteration hashing algorithms (SHA1 & MD5), but unfortunately, we had no luck. It appears that Spiceworks HDS uses a proprietary hashing algorithm for passwords, which makes sense from a security standpoint. I wouldn’t expect them to share any password hashing details either, as it could compromise their security. Plus, they want to push everyone off HDS and over to their newer cloud products. What better way to do that than by revoking the ability to create new users in HDS? Don’t get me started… Not recommended but if you must continue using deprecated Spiceworks HDS and need to create new users, you'll have to share passwords. You can either duplicate a user (as shown in the video) or use the default 'spiceworks' password. Here’s the correctly formatted hash for password 'spiceworks': 4ef8ae9b95e293fd1e883fe44fc4dcd0902e4abf If you use 'spiceworks' password hash above, make sure to leave the password salt blank in the database. Lastly, I’d be willing to trade a couple of pre-formatted working password hashes + salt if you have any to share. Let me know if you're interested. Thank you for watching.

I just battled with this myself until I ran DB Browser for SQLite "as admin". That allowed me to duplicate the desired user record and write the changes to the database.

same question here

same question here

Try this: - Ensure your .py file name is exactly: remove-threat.py - Stick your remove-threat.py file on your desktop - Run powershell as admin - Type and run this command: cd c:\users\yourusername\desktop (be sure to replace 'yourusername' with your actual username) - Type and run this command: pyinstaller -F emove-threat.py

@@ReasonableITService I am literally stuck in the same spot and having the same problem. I have deleted and recreated the python file 3x and still getting .spec output and not .exe....something wonky going on, it just doesn't make sense

​@@theOcsurfbum A successful conversion process should spit out one 'remove-threat.spec' file and two folders called 'dist' and 'build'. The converted remove-threat.exe file you need should be in the 'dist' folder.

I was having the same problem as you but I just found the solution. When you are copy-pasting scripts into the remove-threat.py file do not use the ctrl+v or right click paste to do so. Instead go to Edit -> Paste. I was having "unvalid syntax" error until I did it this way. For the next part I just wrote pyinstaller -F remove-threat.py to the powershell while I was in the Desktop directory and send it. I fixed it this way. I know it's silly... But it worked. Let me know if you try.